July 10, 2026
The following Compliance Network updates were released to production between June 26, 2026 and July 9, 2026.
New and improved
- Croatia
-
We improved the document identification display in the Croatia product. You can now see the conversation ID associated with each document instead of the unique ID, making it easier to identify the document lifecycle and track all related messages and statuses.
We added a manual reconciliation operation for inbound documents. You can now poll documents within a specific date range to recover missing documents on demand, ensuring full visibility of all relevant inbound documents without relying on automatic polling.
- France
-
We improved the issuer identification process for outbound documents. The system now includes a SIREN-based lookup as an additional fallback step to more reliably identify document issuers.
We added lifecycle validation rules for the France V1.3 CDV flow. The system now validates lifecycle status messages for Flow 6 documents before transmission, ensuring full compliance with French e-invoicing requirements.
We added support for tax authority status notifications. Compliance Network now maps lifecycle data to CDAR, so clients receive real-time updates on tax authority responses for their submitted documents.
- United Arab Emirates
We updated the document transformation mapping rules for inbound e-invoicing. The system now processes inbound documents with the latest mapping configurations.
Bug fixes
- Credit notes
We fixed a problem that was causing credit notes with invoice notes to be incorrectly rejected during validation. Credit notes that include invoice notes are now accepted and processed as expected.
- Belgium
We fixed a problem with outbound document formatting that was incorrectly adding an attribute to the OrderReference segment. Outbound documents now conform to the expected Peppol BIS Billing 3.0 format as required by receiving parties.
- Brazil
We fixed a problem with NFSe notification responses that was returning an incorrect status code when the tax authority was unavailable and the retry limit was exceeded. The system now returns status code 501 as documented.
- France
-
We fixed a problem that was causing the Create Company API to return a product association error when creating companies with French e-invoicing products. You can now create companies with French product associations successfully.
We fixed a problem that was causing schematron warnings to be treated as validation errors during lifecycle processing. The system now correctly distinguishes between warnings and errors, allowing compliant documents to proceed through the lifecycle.
We fixed a problem that was causing the mandatory lifecycle status to not be transmitted to the French tax authority after successful document validation. The system now sends the required lifecycle messages to the tax authority as expected.
We fixed a problem that was causing an "Issuer is not client" error during outbound document transmission. The system now correctly identifies endpoints for outbound products without requiring a specific document type.
We fixed a problem that was causing missing intermediate validation notifications for lifecycle submissions. The system now correctly generates validation status updates during lifecycle processing.
- United Arab Emirates
-
We fixed a problem that was causing the government status code to display incorrect values in the Notification and Metadata API responses. The API responses now return the correct status codes.
We fixed a problem that was causing internal system fields to appear in the Notification API response. The response now returns only the expected fields.
We fixed a problem that was causing document artifacts to be missing from the Notification API response. You can now access all expected documents in the response, including the canonical invoice, legal XML, and outcome notice.
We fixed a problem that was causing duplicate and inconsistent delivery and reporting status values in the Notification and Metadata API responses. The API responses now return a single, consistent set of status values.
