Go to validation portal directly…

You can validate your messages against all invoice formats that can be found in the documentation section of this site.  Message validation is performed by taking several aspects into account as being described as follows.

The onboarding process

The first time a sender is connected to the system of the invoice recipient is also called on-boarding. However, from the viewpoint of an invoice recipient, the on-boarding process should not take place as the last step. Instead, it is preferable to start with the potential analysis which business partners should be involved in the automation process.

Essential aspects of the on-boarding process are

• Making sure that an invoice sender may actually send invoices to the recipient (e.g. to prevent spam mails)
• Ensuring the correctness of the invoice content
• Ensuring the technical quality of the structured data:

The agreed data format has been complied with and the business rules are fulfilled.

Technical validation and testing of electronic invoices

The process of technical validation can be automated in essential points. Invoice.fans, with its validation functionality, offers the opportunity to check invoice documents against the different usage recommendations. The following aspects are taken into account:

• Is it a technically valid file?
• Does the data structure correspond to the selected standard?
• Mandatory information included?
• Encoded information (e.g. code lists) conforms to the standard?

If the specification provides appropriate business rules, these business rules can also be checked. These include, for example:

• Check the mathematical accuracy of an invoice
• Compulsory details according to VAT law are filled
• Calculation rules and rounding rules are taken into account

Result of the Validation:

• Check the invoices in the self-test and recognize whether the selected invoice corresponds to the selected invoice format and can therefore be processed without any problem
• View errors and problems by means of a clear error report and, if necessary, derive changes