The essentials

Validation checks a file against specific rules. A successful result alone does not confirm delivery, approval by the customer or the correctness of all business and tax circumstances.

What is checked when an e-invoice is validated?

Validation compares a document with a specific set of rules. The Peppol BIS Billing documentation distinguishes checks of the syntax, of the EN 16931 semantics and of the Peppol profile rules, including country-specific rules.

Before comparing the results of two validators, therefore, write down which profile and rules release they used. A result without this information may be of little use to support. Also find out whether the application carried out all the checks or stopped at the first error.

What does the XML and XSD check reveal?

First, the XML must be written correctly: elements closed, attributes correct and the structure readable. The check against the XSD schema then verifies the permitted structure, data types and other syntax requirements.

If the report flags an unknown element or the wrong order, send the exporter's supplier the exact message and the location of the error. Do not confuse a one-off manual fix of the file with a fix of the software: the original error could recur in the next export.

We explain the relationship between syntax and the meaning of data in the article BIS Billing and XML.

What are business rules and Schematron for?

The next layer checks the relationships between data: for example mandatory information or matching totals. The official BIS Billing package makes available both the rules and the Schematron validation artefacts.

When reporting an error, you need not only its text but also the rule code. This helps to find the exact condition in the documentation. When the report mentions a missing electronic address, check the partner's source field following the Peppol ID guide.

For internal support purposes, we recommend noting for each recurring error in which field of the application it should be fixed. The accountant then does not have to look up the technical name of the XML element for every document.

Example: the BR-CO-10 line total error

Rule BR-CO-10 requires the sum of invoice line net amounts (BT-106) to equal the sum of the net amounts of the individual lines (BT-131).

Imagine two lines with net amounts of 100 and 50 euros. Their sum is 150 euros. If the export gives a different value in place of BT-106, the transfer or calculation of this data needs to be checked. This example concerns the line total; it does not explain the final amount due or all the VAT rules.

When fixing it, compare the specific values in the report with the data in the software. If you cannot determine the cause of the difference, do not adjust the amount by guesswork just so that the check passes. Send the example to the supplier.

How do you read a validation report and fix an error?

We recommend this workflow:

  1. Save the document identification, the time of the check, the profile and the rules version.
  2. Read the rule code, its severity and the flagged location in the file.
  3. Distinguish between a problem with the source data, the settings and the exporter itself.
  4. Fix the cause in the software and create a new export.
  5. Repeat the validation and compare the result with the original report.

Ask to have the meaning of labels such as fatal or warning and their effect on sending explained for the specific application. Give support only the data needed to resolve the problem; use agreed test documents for tests.

What does a successful validation not confirm?

A “no errors” result applies to the checks carried out. In your workflow, therefore, record validation, delivery of the document and its processing by the partner separately.

The validator will not judge for you, for example, whether the invoiced service was actually supplied in accordance with the contract. Verify tax obligations according to the applicable rules and the Slovak context; guidance is provided by the legislation and the FAQ of the Financial Administration of the Slovak Republic (Finančná správa SR).

For learning, you can use the annotated XML sample with a saved check result. In an API integration, record the validation result separately from the acceptance of the request and the delivery of the document.

Materials you can come back to

Verified sources

We rely on official materials. You will find the original documents under the links below. When the rules change, we update this guide too.

Content verified 30/9/2026. Assess the validation result together with the profile name, the rules release and the scope of the checks carried out.