Resolved issues

Some French domestic invoices failed clearance routing because supplier and buyer identity data (SIREN, VAT numbers, and electronic addresses) was taken from the routing infrastructure instead of the parties named on the invoice.

Resolved a set of circumstances in French clearance routing so supplier and buyer identity data now comes from the parties named on the invoice.

French addressing suffixes (suffixeAdressage) that contained a dot were rejected during onboarding on AP Inbound and AR Outbound endpoints.

Adjusted validation so addressing suffixes can contain a dot in any position.

The PA management screen showed non-French entities.

Some French invoices were rejected incorrectly, left unresolved, or delivered outside the French clearance flow. Suppliers also had to enter payment terms and preceding invoice codes manually, even when only one value was possible.

Fixed several French clearance and validation issues. Routing-error notifications from the compliance platform are now treated as a final rejection instead of being left unresolved. Invoices that can't enter the French clearance flow are now rejected with a clear reason instead of being delivered as standard invoices. Self-billed invoices are no longer rejected when the supplier has no network account. Invoices are now accepted when a party provides either a SIRET or a VAT number, and a SIREN on its own is accepted as the VAT reference. Payment terms and preceding invoice codes are now auto-populated when only one value is expected.

In Poland, invoices that didn't finish processing and later changed to Failed status after reprocessing didn't appear on the Invoice Status Service (ISS) page.

Fixed the ISS page so these invoices now appear with their current status.

Some users attempting to reset their password by selecting "Forgot password" were receiving two reset emails with different security codes at the same time, causing confusion and potential login failures.

Applied a fix to prevent multiple reset password emails from being dispatched simultaneously when a user triggers the "Forgot password" flow. Users will now reliably receive a single password reset email as expected.

Some Polish customers were experiencing processing issues, including improper field rounding, no automatic retry, and slow performance for large invoices.

• Updated invoice processing to preserve supplier-provided values by removing previous rounding behavior on selected KSeF fields.
• Added automatic retries for clearance invoices that remain in an "In Process" state for more than 24 hours.
• Improved notification retry handling, reduced unnecessary logging, and optimized performance for large invoices.

Some customers were experiencing issues where data on invoices created using PO Convert was misaligned or missing entirely when the Ship To address contained more than five lines.

Updated the portal to support all seven Ship To address lines during PO-to-Invoice conversion. Address line values are now correctly mapped to the corresponding invoice fields up to seven lines, whereby the customer will now see correct, complete address information on the resulting invoices.

The address information displayed on Tungsten's PDF for invoices retrieved from Polish government KSeF platform was truncated.

Tungsten PDFs generated for retrieved invoices will now display the complete address as available in the FA XML.

Some Polish customers were experiencing invoice submission or retrieval failures due to "timeout" issues where inbound/outbound volume limits enforced by the Polish government KSeF platform were being breached.

KseF introduced a batching mechanism to handle the volume of both inbound and outbound invoices, so Tungsten e-Invoice Network enhanced its processes to accommodate the same so that we do not get any throttling issues during clearance or retrieval actions. This enables more invoices to be received or sent within a period and reduces the risk of invoices failing due to "timeout" issues.

For invoices submitted with an attachment file name containing multiple spaces, the 'Invoice status' page showed inconsistencies between the displayed file name and the received file name.

• Identified and fixed an intermittent issue that caused users to be unable to save line items on the e-Invoice Network portal when creating some corrective invoices.
• Fixed an issue that prevented Web Form users from saving and then retrieving corrective invoices from a draft state.
• Made a minor adjustment to the business rule that generates Tax Rate Summary in Poland so that it works correctly with corrective invoices having negative lines only.

Two scenarios that should have been exempt were affected by a Belgian Continuous Transaction Controls (CTC) restriction implemented on domestic transactions processing in Belgium that prohibits the sending of invoices unless both parties are enabled to send transactions through the Peppol network.

Beginning January 1, 2026, Belgian suppliers attempting to invoice buyers VAT-registered in Belgium but established outside of Belgium were having the transactions rejected. Likewise, suppliers VAT-registered in Belgium but established outside of Belgium attempting to invoice Belgian buyers were having the transactions rejected.

An exclusion option has been added to this restriction to enable customers that are VAT-registered in Belgium but not established in Belgium to continue invoicing across Tungsten e-Invoice Network .