Authenticity of Electronic Invoices
Reading e-invoice material with incorrect structure or content into the application is not possible. For an e-invoice to be usable, its data content must meet both the Finvoice product description of the Central Association of the Financial Field and the XML standard.
If the downloaded e-invoice material contains incorrect Finvoice material, then the correct e-invoices in the material are read into the application during the reading of e-invoices and erroneous invoices are rejected.
On the read invoices, there can be two types of errors:
- Such a serious structural flaw is detected in the electronic invoice material, that the invoices cannot be separated into individual invoices. In this case, the entire material will be rejected. The rejected material is saved on the application server, and a notification is recorded in the Transfer log of the defects detected.
- While checking individual invoices, it is detected that the material is structurally correct, but does not conform to the Finvoice standard, for example required fields are missing, fields are missing required data etc. In this case, the invoice will be skipped in processing and the other invoices in the material will be read into the application. Information about the observed error is recorded in the Transfer log.
Transfer Log
The number and total sum of invoices successfully read during a particular reading session are recorded as one log entry in the transfer log (). Furthermore, a more detailed breakdown of each successfully read invoice is recorded. For the invoices read successfully, the name of the supplier, the invoice number, the invoice date, and the invoice total are reported. You can open the breakdown by clicking on the link on the Time column of the log event. If there are electronic invoices that could not be assigned to any company, the data on each unassigned electronic invoice is recorded as a separate event in the transfer log.
The number of faulty invoices during one reading session is recorded as a separate transfer log event. For each erroneous invoice, a separate specification is written. For erroneous invoices, the supplier name, invoice number, invoice date, invoice sum, and a description of the error are entered, as long as this data could be read from the erroneous invoice. If there are many mistakes, only the first one is shown.
The transfer log breakdown also contains a link to an invoice file, through which you can open or save successfully or unsuccessfully read electronic invoices from the application server. An XML file opens in the application with which the XML specification is associated. If the association is made to a browser, the browser does not show a structurally faulty XML file. However, it can be saved and then opened with some suitable application, for example, Notepad.
Clicking on the Invoice File link, you can easily inspect the invoice material, for example, when you want to know which error occurred or, for example, when the invoice was not associated with the correct buyer company or supplier and you want to check what kind of identification data the invoice contains. For more information on identification, see Identifying the Buyer Company of Electronic Invoices and Identifying the Supplier of Electronic Invoices.