Skip to main content

IFS application allows the addition of erroneous characters when creating manual supplier invoices, which can have an impact on successful SAF-T XML file generation.


Forum|alt.badge.img+2

Description:

The current behavior of the IFS application allows the addition of erroneous characters when creating manual supplier invoices. However, this can lead to issues with successful SAF-T XML file generation.

As an example, if we added an erroneous character (Ex: Unicode character without visual representation) as a part of an invoice number, when creating a manual supplier invoice. After that when attempting to generate the Norwegian SAF-T XML file for that specific period, the system does not allow successful creation due to the presence of the erroneous character in that invoice.

Steps to recreate the example:

  • Create manual supplier invoice including an erroneous character, when defining the invoice number. Here attached a snap of an external supplier invoice template including a Unicode character as erroneous character in Inv. No tab.  And update it to the GL.

 

 

  • After that, generate the Norwegian SAF-T XML file by using Audit Interface Assistant tool for the particular period.

 

  • SAF-T XML file will generate unsuccessfully with an error.

 

 

Workaround for successful SAF-T XML file generation:

  • Ensure that the system prevents the addition of characters that do not have visual representations when generating SAF-T XML files. In the current context, the system does not allow for successful SAF-T XML file generation if there are any files which include characters without visual representations.
  • If an erroneous character is mistakenly added, as in this scenario, as a workaround we recommend performing a data repair to remove that character from the file and then you can generate the XML file Successfully.

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings