Module history for Sage X3

Version 18.2
e-InvoiceLink

Sage X3 fixes

Notes in this version: 14

All versions Public history — PDF

Version contents · 14

Footer discounts and VAT in France UBL XML
France UBL unit prices rounded to six decimal places
Resending an original e-reporting report with confirmation
E-reporting VAT totals converted to euros
E-reporting function closes after success
Complete correction report and summary in the native log
Entering missing references before sending a credit note
Saving the full identifier returned by the e-reporting API
Resolving PDF attachments through Sage X3 volumes
France e-reporting — Identity from electronic addressing
Automatic transmission after posting
Entry capacities for French electronic addresses
CDAR 210 — Enabling table selection
Electronic addressing — Supplier support

Fix1

Footer discounts and VAT in France UBL XML

Issue

For French sales invoices with footer discounts or charges, UBL XML did not include these elements. The transmitted VAT could also correspond to the amount before they were applied.

Impact

Line amounts, VAT bases, and document totals could be inconsistent, causing Avalara to reject the invoice.

Fix

Footer discounts and charges are now included in the XML with their tax breakdown. Final VAT and tax-exclusive, discount, and charge totals take footer elements into account. Lines and their prices remain unchanged.

Expected result

UBL XML reflects the invoice's footer discounts and charges, along with consistent taxable bases, VAT, and totals, to avoid rejections caused by these differences.

Fix2

France UBL unit prices rounded to six decimal places

Issue

Unit prices in French invoice and credit-note XML could contain more than six decimal places.

Impact

This excessive precision could cause the document to fail the BT-146 check.

Fix

Transmitted unit prices are now rounded to six decimal places. In-memory calculations, quantities, net amounts, VAT, and totals remain unchanged.

Expected result

Unit prices in France XML comply with the six-decimal-place limit to avoid rejections caused by exceeding it, without changing other amounts.

Fix3

Resending an original e-reporting report with confirmation

Issue

The presence of a report in the Sage X3 history blocked another submission in original mode, even when that history did not prove receipt of the report.

Impact

Users could not rerun the requested original for the relevant period and scope.

Fix

Resending an original is now possible after interactive confirmation. Declining cancels the run before collection; agreeing retains original mode. Each attempt is recorded separately without overwriting previous attempts. Batch processing remains dialog-free.

Expected result

An original can be explicitly resent while retaining previous attempts and without automatically switching to correction mode.

Fix4

E-reporting VAT totals converted to euros

Issue

VAT totals for a foreign-currency invoice could be included in e-reporting without conversion to euros.

Impact

Declared VAT amounts could be incorrect and cause the report to be rejected.

Fix

The relevant totals are converted to euros at the exchange rate stored on each invoice. For B2C groupings, conversion takes place before aggregation and amounts are rounded to the nearest cent. A missing or invalid rate is not replaced with an arbitrary rate.

Expected result

VAT totals are expressed in euros using the invoice exchange rate; the document currency, bases, and subtotals are retained.

Fix5

E-reporting function closes after success

Issue

The e-reporting function could remain open after a successful run had finished.

Impact

Users had to close the window manually even though processing was complete.

Fix

Closure is now requested after the summary only when execution succeeded. If an error occurs, the window remains open.

Expected result

The function closes normally after success and remains accessible when an error requires intervention.

Fix6

Complete correction report and summary in the native log

Issue

A correction report could be generated using only valid lines while another line in the same flow was blocking processing.

Impact

The submitted report risked replacing only part of the expected data for the period.

Fix

A blocking anomaly now prevents generation and transmission of the relevant correction report. Existing and new lines continue to be included together. The summary is retained in the log without automatically opening a final dialog.

Expected result

A correction report covers the entire corrected data set for the relevant flow; no valid subset is sent while any line in that flow still blocks processing.

Fix7

Entering missing references before sending a credit note

Issue

When manually sending an individual French credit note, mandatory references could be missing without the existing entry window being offered correctly.

Impact

Users could not complete the required information during the sending process.

Fix

The references window now opens before sending when this information is missing: period and contract for type 262, original invoice number and date for the relevant types without a native origin. Manual references are preserved. Cancellation or incomplete entry blocks continuation; automatic and bulk modes remain dialog-free.

Expected result

Manual sending of the credit note resumes only after complete and consistent mandatory references have been saved.

Fix8

Saving the full identifier returned by the e-reporting API

Issue

The identifier returned for an e-reporting report was checked as an identifier limited to 36 characters.

Impact

A longer identifier, particularly one prefixed with “fr-”, could fail to be saved correctly, preventing reconciliation with the submitted report.

Fix

The full identifier is now read up to 100 characters, without removing its prefix or truncating its value. If a successful HTTP response contains no usable identifier, the report is flagged for reconciliation.

Expected result

Sage X3 tracking retains the full identifier received for the report and explicitly flags responses that do not allow automatic reconciliation.

Fix9

Resolving PDF attachments through Sage X3 volumes

Issue

A PDF attachment referenced through a Sage X3 volume could be looked up in a directory incorrectly inferred from the volume code.

Impact

The file could be considered missing even though it was accessible through its logical reference.

Fix

Volume references are now resolved through the standard Sage X3 mechanism. Names containing multiple dots, physical paths, attachment selection, and fallback printing are retained. An erroneous or empty resolution blocks use of the affected attachment.

Expected result

PDF attachments are looked up in the location actually corresponding to the configured Sage X3 volume.

Fix10

France e-reporting — Identity from electronic addressing

Issue

E-reporting could take identity information from the BP record instead of electronic addressing, or construct an issuer VAT number from the SIREN.

Impact

The XML could contain identifiers that did not match the selected addressing information; missing VAT outside the European Union could also block a legal identifier.

Fix

The name, VAT number, and relevant identifiers now come from the electronic addressing active in the correct environment. The legal identifier remains separate from the electronic address and depends on the geographical area. A VAT number is no longer required to form this identifier when none is available for a partner outside the EU.

Expected result

The report uses identity information from electronic addressing and handles partners in France, the EU, and outside the EU according to their context.

Fix11

Automatic transmission after posting

Issue

Processing launched after posting could start e-InvoiceLink checks even when automatic transmission was disabled or no active rule applied.

Impact

Posting triggered licence or transmission checks that were not expected for this invoice.

Fix

Automatic transmission enablement is now checked before licence checking, XML generation, and sending. If there is no active rule or automatic transmission is disabled, processing stops for that invoice without cancelling its posting or interrupting the batch.

Expected result

A posted invoice starts the automatic e-InvoiceLink flow only when its setup allows it.

Fix12

Entry capacities for French electronic addresses

Issue

French addressing entry formats and some processing routines limited routing, suffix, or full-address values below the expected capacities.

Impact

Long electronic addresses could be rejected or fail to be retained in full through to document generation.

Fix

Routing and suffix now accept up to 100 characters, with a 9-character SIREN and a 14-character SIRET. The full address is retained up to 125 characters; an address exceeding this limit is rejected before processing, without silent truncation.

Expected result

Entry, the cockpit, and France XML preserve valid addresses within the specified limits: 100 characters per component and 125 for the full address.

Fix13

CDAR 210 — Enabling table selection

Issue

The CDAR 210 supplier selection setup still used a limited list, despite the presence of paginated selection logic.

Impact

Native navigation could not use the intended pagination to find suppliers beyond the initial list.

Fix

Supplier selection has been connected to the table-selection model in the CDAR 210 screen.

Expected result

The supplier lookup uses the intended paginated selection, without remaining limited to the old list behaviour.

Fix14

Electronic addressing — Supplier support

Issue

Electronic addressing entry did not retrieve the BP name and VAT number for the Supplier type and did not check its code as intended.

Impact

A supplier record could be initialised without this information or with an unchecked BP code.

Fix

Retrieving the name and VAT number and checking that the BP exists now also cover the Supplier type.

Expected result

Creating a supplier electronic address populates the expected information from the BP record and checks that the entered code exists.

Version 18.2e-InvoiceLink

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

Issue

Impact

Fix

Expected result

No matching release notes.

Version 18.2
e-InvoiceLink