Resolved issues
This topic lists previously reported issues that are resolved in this Tungsten e-Invoice Network update.
December 3, 2025
| Issue | Solution |
|---|---|
| On the Supplier Connect portal, some suppliers who answered "N/A" or "No" to certain questions still received an error message and were unable to proceed with their implementation past the "Questionnaire" step without uploading the contingent required invoice file. | Deployed updated metadata file so suppliers can now save the questionnaire without uploading a dummy file for any questions marked "N/A" or "No." |
October 16, 2025
| Issue | Solution |
|---|---|
| Onboarding users were unable to select zero-rated tax categories on the "Questionnaire" screen in the Supplier Connect portal. | Adjusted settings so that suppliers can now select zero-rated tax categories during their self-service implementation. |
| Following recent changes to the portal login screen, the page no longer accepted submission of a user's email address by pressing the Enter key. Users needed to select the "Sign In" button to proceed. | Corrected the issue so that users can submit their email address on the portal login screen by either selecting "Sign In" or pressing Enter. |
| When customers created a new account with a VAT number/Tax ID that consisted only of numbers (no letters), the VAT number/tax ID did not persist across the registration process. | Fixed the issue so that the VAT number/tax ID is preserved on all registration screens. |
August 21, 2025
| Issue | Solution |
|---|---|
| In Italy, when two suppliers used the same invoice number and the buyer retrieved both invoices from the government SdI platform, when the buyer used the "Find" option on the "Invoice status" page and clicked on the second instance of the invoice number, the system displayed the first invoice with that number. | Ensured that where an invoice number appears multiple times and the user selects an invoice to view, it is the selected invoice that is displayed. |
July 24, 2025
| Issue | Solution |
|---|---|
| The French translation for the Unit of Measure "Carton of 1" was missing from the database. This prevented suppliers from converting a Purchase Order with that Unit of Measure, as they received the following error message: "Impossible de convertir un bon de commande sans article" ("Unable to convert a purchase order without an item"). | Added the French translation for the Unit of Measure "Carton of 1" to the database. |
| In a previous deployment, we added a separate section for customers in Mexico to provide additional information required for invoice processing in Mexico. These fields were also incorrectly added to be visible on the "Company details" section for customers in Saudi Arabia. | Removed the section pertaining only to customers in Mexico from the "Company details" section for customers in Saudi Arabia. |
July 1, 2025
| Issue | Solution |
|---|---|
| Italian accounts were missing the "*" mandatory field indicator on the City and Post Code fields. | Added "*" mandatory field indicators to the City and Post Code fields on Italian accounts. |
May 27, 2025
| Issue | Solution |
|---|---|
Users were unable to change their preferred multifactor authentication method:
|
Resolved issue so new preference selected by a user on the "Update your MFA" screen now saves correctly. |
April 29, 2025
| Issue | Solution |
|---|---|
| Some suppliers received an error message when trying to acknowledge their buyer's purchase orders on the portal. | Adjusted settings to allow suppliers to successfully acknowledge purchase orders and proceed with converting the PO to an invoice. |
January 23, 2025
| Issue | Solution |
|---|---|
| Malaysian Web Form Suppliers submitting self-cleared invoices received errors when entering incorrect information into the Invoice UUID and Invoice long ID fields. | Added tooltips and system checks to ensure correct length and other requirements for input data for Invoice UUID and Invoice long ID fields when submitting self-cleared invoices. |
December 14, 2024
| Issue | Solution |
|---|---|
| When a customer had multiple "Remit to" details, the account page assumed the first one in the list was the default option and would not allow users to delete it. | Adjusted settings so suppliers have the option to delete any "Remit to" record, providing it is not the default option. The default "Remit to" details cannot be deleted. |
| The Supplier Connections page of Customer Connect failed to load more records if the page had already been re-sorted. | Fixed an issue related to the "load more" component, allowing the page to update the list of connections again after sorting. |
| Information about a buyer's fiscal representative was not appearing on generated PDFs. | Corrected the location where fiscal representative information was saved for buyers. Where a buyer has a fiscal representative in their account set-up, the generated PDF now correctly identifies the entity as being a fiscal representative. |
| When a VAT-registered supplier saved an invoice as a draft invoice, then updated their account details to indicate their account was not subject to VAT, the invoice in a draft status would still display VAT rates and amounts. | Updated code to correctly apply tax when the account configuration indicates a VAT-registered supplier and not apply tax when the account configuration indicates a supplier is not subject to VAT. |
Localization:
|
|
Reporting:
|
|
| Some invoices retrieved from the Romanian government’s ANAF platform had a timestamp that overlapped the invoice number. | Ensured that the timestamp on invoices retrieved from the Romanian government's ANAF platform is fully removed from the invoice number, so the invoice number now displays correctly in all scenarios. |
| Administrators received a message citing "unexpected error" when attempting to change a user email address to an email address that is already in use. | Updated error messaging so that, as an administrator, if you attempt to change a user email address to one that is already in use, you receive a message stating the email address is already in use. |