This changelog provides an overview of the changes introduced to the API for release 9.6.8.
Release calendar
| Environment | UAT Release | PROD Release |
|---|---|---|
| NL | 2026-08-07 | 2026-08-14 |
| EU1 | 2026-08-11 | 2026-08-20 |
| UK | 2026-08-11 | 2026-08-20 |
| US | 2026-08-11 | 2026-08-20 |
Invoice API
Invoice REST API Payment: Improved ISO 8601 Date and Time Support.
With this release, we have improved the Invoice REST API Payment endpoint so that payment date values can be provided with time zone inclusion using commonly used ISO 8601 date and time formats.
Before this update, some date and time values including time zone values were not accepted by the endpoint, which could prevent invoice payment updates from being processed successfully.
The endpoint now accepts additional ISO 8601 date and time formats for invoice payment dates, including values that include time zone offsets.
Supported payment date formats: The Invoice REST API Payment endpoint now supports the following payment date formats:
- yyyy-MM-dd'T'HH:mm
- yyyy-MM-dd'T'HH:mm:ss
- yyyy-MM-dd'T'HH:mm:ssZ, (New with this release)
- yyyy-MM-dd'T'HH:mm:ssXXX, for example 2026-06-24T10:30:00+08:00 (New with this release).
No action is required if your integration already sends payment dates using one of the supported formats. If your integration previously transformed payment dates to remove seconds or time zone information, you may be able to simplify that logic after this update.
Receipt API
Receipt comments now supported in REST API import and export.
With this release, we have enhanced receipt processing in the REST API so that receipt comments can now be included when receipts are imported or exported. This helps preserve important contextual information on receipts and supports feature parity with existing BizTalk-based integrations.
When importing receipts through the REST API, a single comment can be provided in the receipt header comments section. If a comment is included, it is stored on the receipt created. If no comment is provided, the receipt is created successfully without a comment.
When exporting receipts through the REST API, existing receipt comments are now made available to external systems. If multiple comments are present, they are exported together in the comments section, separated by line breaks. Receipts without comments continue to export successfully.
This update improves integration consistency, reduces the risk of losing receipt-related notes during API-based processing.