EN 16931 describes the meaning of e-invoice data. UBL provides the XML syntax and Peppol BIS Billing specifies the rules for using them. When exporting, confirm both the specific profile and the rules release in force.
What does Peppol BIS Billing mean?
Peppol BIS Billing 3.0 is a specification for the exchange of invoices and credit notes. It sets out how data and rules are used so that different systems can process the documents. The documentation contains the UBL Invoice and CreditNote syntax, code lists and validation rules. You will find them on the official BIS Billing hub.
So ask your software supplier for the name of the supported profile. The answer “we export XML” is too general to judge whether the resulting file meets the requirements of a specific exchange.
How are EN 16931, UBL and XML related?
XML is a way of writing structured data. EN 16931 defines the semantic model, i.e. the meaning of an invoice's business data. UBL 2.1 is the syntax in which this data is written; BIS Billing sets the rules for its use in the relevant profile. The relationships are explained in the BIS Billing specification.
| Layer | What it covers | What to check in the software |
|---|---|---|
| EN 16931 | The meaning of business data and its relationships | Whether the export transfers the correct values and tax situations |
| UBL 2.1 | Writing data into XML elements | Whether the document conforms to the Invoice or CreditNote schema |
| Peppol BIS Billing 3.0 | Use of data, code lists and exchange rules | Whether the export passes the current validation rules |
| Peppol eDelivery | Looking up the recipient and transfer between providers | Whether the service delivers the supported document to the right addressee |
The last layer has its own network specifications. Therefore verify the correct document format and working delivery separately.
In practice, first clarify what a piece of data means in the accounting process, and only then where it belongs in the export. For example, the invoice number, the order reference and the recipient identifier have different roles. Mixing them up can cause a problem even in a file that is readable XML.
We explain the basic difference between a visual document and structured data in the article PDF or XML.
Which data should be checked in the export?
To check your own software, we recommend preparing a data map. The following table is an aid for your conversation with the supplier, not a complete list of mandatory fields.
| Area | Question when checking the software |
|---|---|
| Document | Where are the number, issue date and currency taken from? |
| Partners | Which fields belong to the company, taxes and electronic address? |
| Lines | How are quantity, unit, price and discount transferred? |
| VAT and totals | How are the tax categories, tax bases and resulting amounts put together? |
| Payment and references | Where are the due date, account and matching reference taken from? |
The customer's electronic address has its own element in UBL, EndpointID, with the attribute schemeID; the details are in the definition of this element. We discuss the Slovak context of the address in the Peppol ID guide.
In the document header, also distinguish CustomizationID, which identifies the specification used, and ProfileID, which identifies the business process. They are neither recipient addresses nor invoice numbers. You will find the specific values and their placement in the annotated XML sample and in the official invoice syntax.
How should credit notes and more complex invoices be approached?
In the BIS Billing documentation, the invoice and the credit note are described separately. So do not test with just one simple invoice. Prepare the documents your business actually issues: a discount, multiple lines, different tax situations or a correction of an original document.
For each scenario, compare the source data with the export and the result at the recipient. Record which cases the software supports and which need further configuration. Use a supplier's sample to understand the export; do not copy its numbers and identifiers into your own documents.
Which version of the rules should the software use?
The label BIS Billing 3.0 by itself does not tell you which release of the rules the software uses. Follow updates and the validity of releases on the official hub.
We recommend keeping a record of the exporter version, the rules used and the test date. When the software is updated, repeat your typical scenarios and agree with the supplier how they will announce a change in format or validation.
At the time of this check, the current release is 3.0.21 (May 2026), mandatory from 17 August 2026. The date and the changes are given in the release notes. The Slovak mapping is at version 1.11; you will find it in the transposition by the Financial Administration of the Slovak Republic (Finančná správa SR). With every further update, check the national requirements too, not just the BIS Billing name.
What should you confirm before going live?
Ask the supplier for a specific export of your document, the validation result and an explanation of any errors. Check the supported document and process with the delivery provider. After a test with a partner, compare the data in their application too.
We go through checking the XML step by step in the article E-invoice validation. When preparing for the Slovak obligations, continue with the overview of the legislation and the FS SR FAQ.
If you want to connect invoicing or ERP with a delivery service, continue with designing an API integration. Transferring data into XML, calling the service and processing confirmations each have their own check steps.
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 1/10/2026. Check technical details and the validity of a release in the current Peppol BIS Billing documentation.