Module history for Sage X3

Version 19.1
e-InvoiceLink

Sage X3 fixes

Notes in this version: 6

All versions Public history — PDF

Version contents · 6

Error messages for credit notes outside the scope
Incorrect blocking during the payment accounting check
False conflicts for CDAR 212 declarations already accepted
Slow cockpit opening and searches
CDAR 210 rejection blocked by the receipt check
France document generation interrupted by a missing field in Sage X3 V9

Fix1

Error messages for credit notes outside the scope

Issue

When processing receipts, credit notes excluded from the scope could appear in the log with an anomaly message concerning their type, date, or currency.

Impact

These messages incorrectly reported an error on documents that were not meant to be processed, making the summary harder to read.

Fix

The document type is now checked before performing checks that are unnecessary for its processing. Credit notes that are normally excluded are skipped without a message. Missing data on an eligible invoice and inconsistencies in an existing event are still reported.

Expected result

Normal exclusions no longer generate false errors; genuine anomalies remain visible in the log.

Actual screenshot of the message: Invoice accounting type/date/currency unavailable: — Log excerpt before the fix: message concerning accounting data. Cropped screenshot, with the original message retained.

Fix2

Incorrect blocking during the payment accounting check

Issue

The normal end of reading a payment's entries could be interpreted as a failure, with the message “payment voucher line cursor failed”.

Impact

A receipt with consistent accounting reconciliation could be excluded from CDAR 212 processing.

Fix

Processing now recognises normal end-of-read return values. It retains payment consistency checks and still reports a failed read, a missing document, or an ambiguous reconciliation.

Expected result

A consistent payment can continue processing without being blocked by a false accounting read error.

Actual screenshot of the message: CDAR212 proof: payment voucher line cursor failed — Log excerpt before the fix: payment check stopped. Cropped screenshot, with the original message retained.

Fix3

False conflicts for CDAR 212 declarations already accepted

Issue

Rereading an older CDAR 212 declaration already transmitted and confirmed as “Accepted” could trigger unnecessary checks or a conflict message involving the existing record.

Impact

The log could suggest that a correctly processed declaration required intervention.

Fix

Processing first checks the declaration's identity, its context, and confirmation of its transmission. A historical declaration confirmed in this way is skipped without logging, resending, or creating a new event. Uncertain or inconsistent situations are still reported, and tracking of new events is retained.

Expected result

Simply rereading a CDAR 212 declaration already accepted no longer produces a false error message or triggers any resending.

Actual screenshot of the message: Legacy CDAR record or read conflict; event not created — Log excerpt before the fix: an older CDAR declaration reported as a conflict. Cropped screenshot, with the original message retained.

Fix4

Slow cockpit opening and searches

Issue

With a large volume of invoices, opening the cockpit and searching repeatedly read the same rules and references many times.

Impact

Users had to wait before viewing invoices and continuing their work.

Fix

A search now reuses common information during its execution and reduces repeated reads and preparation steps. Information is refreshed for each search, while preserving the criteria, access rights, order, and content of the results.

Expected result

Opening and searching are faster, with the same invoices and information displayed for the same criteria and access rights.

Fix5

CDAR 210 rejection blocked by the receipt check

Issue

Sending a CDAR 210 rejection could be blocked by a check intended for CDAR 212 receipts. The absence of a payment event could also be interpreted as tracking being unavailable.

Impact

The rejection could not continue to be sent even though this receipt check did not apply to it.

Fix

CDAR 210 rejection is now distinguished from receipt tracking. The normal absence of a payment event is recognised, and protections against duplicates or conflicts for CDAR 212 declarations are retained.

Expected result

A rejection can continue to be sent when its own checks are satisfied, without being incorrectly blocked by receipt tracking.

Message observed before the fix

Legacy CDAR send unavailable while PEV journal cannot be checked

Excerpt from the message reported for ticket 524105. The original screenshot is not reproduced.

Fix6

France document generation interrupted by a missing field in Sage X3 V9

Issue

Determining the delivery date could access a line-origin field that does not exist in Sage X3 V9, interrupting generation of the France document.

Impact

The invoice could not be generated, even when the required delivery references were available.

Fix

The line-origin check is now performed only when the field exists in the folder. Available delivery references are still used, and the planned fallback to the accounting date is retained when there is no delivery.

Expected result

France document generation is no longer interrupted by the absence of this field, while retaining the rules for determining the delivery date.

Version 19.1e-InvoiceLink

Error messages for credit notes outside the scope

Issue

Impact

Fix

Expected result

Incorrect blocking during the payment accounting check

Issue

Impact

Fix

Expected result

False conflicts for CDAR 212 declarations already accepted

Issue

Impact

Fix

Expected result

Slow cockpit opening and searches

Issue

Impact

Fix

Expected result

CDAR 210 rejection blocked by the receipt check

Issue

Impact

Fix

Expected result

France document generation interrupted by a missing field in Sage X3 V9

Issue

Impact

Fix

Expected result

No matching release notes.

Version 19.1
e-InvoiceLink