Module history for Sage X3

Version 19
e-InvoiceLink

Sage X3 fixes

Notes in this version: 13

All versions Public history — PDF

Version contents · 13

Incomplete message when reading the AED exchange rate fails
Delivery date missing from the German document
Unanswered UAE fields interpreted as No
Invoice classified as an error after only entering additional information
Inconsistent unit handling between countries
Complete status retained after an error is returned
Missing delivery information for category K
Incorrect tracking of partial receipts and matching changes
Total VAT in euros missing for foreign-currency invoices
Contract reference ignored outside type 262
Electronic address not refreshed after changing VAT or NIP
Country fields and addressing levels displayed in the wrong place
Slovakia missing from the list of available countries

Fix1

Incomplete message when reading the AED exchange rate fails

Issue

When an AED exchange-rate request failed, the message did not include the available technical information about the failed request.

Impact

Users did not have the information needed to provide their support team with a precise diagnosis.

Fix

The message now includes the requested exchange-rate date, the error code, and the message returned by the service when available. Failure still blocks processing: no replacement rate is invented.

Expected result

Support receives a more precise message to investigate why the exchange rate could not be obtained.

Fix2

Delivery date missing from the German document

Issue

Some German invoices and credit notes had no delivery date in the XML, particularly when no delivery was linked to the document.

Impact

The document could be rejected by a check requiring a delivery date or an invoicing period.

Fix

The document now uses the date of the latest linked delivery. If there is no delivery, it uses the invoice's accounting date. A delivery reference that cannot be found or a missing date is reported before generation.

Expected result

The expected date is transmitted for the relevant invoices and credit notes, without creating a delivery or changing the accounting date.

Fix3

Unanswered UAE fields interpreted as No

Issue

When entering UAE additional information, an unanswered field could appear as No.

Impact

Users could believe that an explicit answer had been saved even though no choice had been made.

Fix

All eight answers now start as Undetermined. Each answer must be explicitly entered before validation; incomplete entry is rejected.

Expected result

Saved transaction facts match the user's explicit choices; an unanswered field does not become a No.

Fix4

Invoice classified as an error after only entering additional information

Issue

Saving additional invoice information could cause the document to appear in the error list even though neither generation nor transmission had begun.

Impact

The To transmit list no longer accurately reflected invoices still to be sent, and the classification could suggest that a transmission had failed.

Fix

The cockpit now distinguishes simply entering additional information from processing that has begun. Classification depends on the invoice's actual status, regardless of its country or flow.

Expected result

An invoice with only additional information entered remains in the list appropriate to its status; entry alone does not create a transmission error.

Fix5

Inconsistent unit handling between countries

Issue

The same Sage X3 unit could be mapped in some countries and rejected in others. An unknown unit could also be replaced with a default unit.

Impact

Generation could be blocked for a unit already supported elsewhere, or could transmit a unit that did not match the invoice data.

Fix

The France, Belgium, Poland, Germany, Slovakia, and UAE generators use the same unit mappings. A recognised unit is retained or mapped; an unknown unit blocks generation instead of receiving a replacement value.

Expected result

Units are handled consistently in the countries concerned, without changing invoice quantities, prices, or amounts.

Fix6

Complete status retained after an error is returned

Issue

The manual global status read did not query invoices already marked Complete. When a new Error status was obtained, protection of the Complete status could also prevent it from being saved.

Impact

The cockpit could retain Complete even though the platform subsequently reported an error on the document.

Fix

The global Read statuses button now includes Complete invoices that meet the existing checks. A recognised Error response can replace Complete, and the log distinguishes the received status from the status actually saved. Automatic reads retain their selection criteria.

Expected result

After a manual read, the cockpit can reflect a newly reported error for an invoice previously marked Complete, within the authorised scope.

Fix7

Missing delivery information for category K

Issue

French invoices and credit notes containing a category K transaction could fail to transmit the required delivery country and date.

Impact

These documents could be rejected because the expected delivery information was missing.

Fix

The delivery country is taken from the relevant address and transmitted using its ISO code. The date is that of the latest linked delivery or, when there is no delivery, the accounting date. Missing or inconsistent required data is reported before generation.

Expected result

Category K documents carry the expected country and date, without adding delivery information to other categories.

Fix8

Incorrect tracking of partial receipts and matching changes

Issue

Receipt tracking did not correctly reflect successive partial payments and corrections related to unmatching or reallocation.

Impact

Declared amounts could fail to reflect each receipt and its allocation to the invoice.

Fix

Each allocated payment is tracked separately on the matching date, with allocation in proportion to amounts including tax. Unmatching and reallocation corrections are taken into account; rerunning without a change does not declare the same payment again.

Expected result

Receipt tracking distinguishes successive payments and their corrections, without waiting for the invoice to be fully settled or repeating an unchanged payment.

Fix9

Total VAT in euros missing for foreign-currency invoices

Issue

For a French invoice in a currency other than the euro, the XML did not provide the expected additional VAT total in euros.

Impact

The document could be rejected even though VAT amounts in the invoice currency were present.

Fix

The total VAT in euros is now added using only the exchange rate stored on the invoice for the main general ledger. Amounts in the document currency are retained. No exchange rate from master data replaces the invoice's rate.

Expected result

The document contains VAT in its currency and its additional total in euros; a structural inconsistency or zero divisor is reported before generation.

Fix10

Contract reference ignored outside type 262

Issue

A contract reference supplied by a customisation was not included for all French document types; its processing remained limited to type 262.

Impact

An available contract number could be missing from the transmitted document, or prior entry could prevent the customisation from supplying it.

Fix

Contract reference population now runs for all types that reach France generation. The supplied value takes precedence. For type 262, the saved reference is used if no value was supplied, and an empty final reference still blocks processing.

Expected result

A supplied reference is transmitted regardless of the document type concerned; for types other than 262, the absence of a contract adds neither an empty tag nor a new requirement.

Fix11

Electronic address not refreshed after changing VAT or NIP

Issue

Changing the German VAT number or Polish VAT/NIP identifiers did not always trigger the expected electronic address update.

Impact

The address could retain an old identifier despite the change displayed in the record.

Fix

Entry events now update the address and its scheme according to the country. In Germany, the address uses the full VAT number; in Poland, a new VAT number takes precedence over the previous NIP, and changing the NIP triggers recalculation. The normalised value is retained after leaving the field.

Expected result

The derived address matches the latest identifier entered; identifiers entered directly for Slovakia and the UAE remain separate and are preserved.

Fix12

Country fields and addressing levels displayed in the wrong place

Issue

Some country-specific fields remained displayed outside their country, while the addressing level appeared for Poland without a useful choice. Slovak legal notices were placed among the common parameters.

Impact

Users could confuse country-specific information with common parameters or enter a choice that had no effect.

Fix

The common address and scheme fields are reused. The display adapts national fields to the country, hides the level for Poland, and groups legal notices in the Slovakia block. Entity information and parameters remain accessible.

Expected result

Entry screens show information relevant to the selected country without duplicating common addressing fields.

Fix13

Slovakia missing from the list of available countries

Issue

The published list used by the addressing screen did not offer Slovakia even though its definition already existed.

Impact

Users could not select this country in the addressing function.

Fix

Publication of the list has been corrected in the available languages, retaining the six existing options. An already open session may require logging in again after saving entries in progress.

Expected result

Slovakia is available as the seventh option in the electronic addressing country list.

Version 19e-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

No matching release notes.

Version 19
e-InvoiceLink