EU · EN 16931: e-invoice formats and rules
Use this page to choose the EU · EN 16931 check, identify the fixed package and follow diagnostic examples before sending an invoice to its recipient.
Formats and syntax
EN 16931 separates the meaning of invoice fields from their XML representation. The European Commission lists UBL 2.1 for Invoice and CreditNote and UN/CEFACT CII D16B as the two required syntax bindings. A supplier therefore needs an actual structured document, rather than a renamed PDF. Mapping a buyer identifier into the wrong namespace can make an otherwise readable invoice unusable to its recipient.
Rules XSDHub applies
XSDHub first parses the document and applies the corresponding official XML schema. It then runs the fixed EN 16931 validation artefacts 1.3.16. This package checks business terms, code lists and arithmetic relationships implemented in those rules. It does not automatically add the German, Romanian or Croatian national restrictions. Select the relevant country package when the recipient requires a CIUS; an EN-only pass cannot stand in for a national-profile result.
Who this affects
Directive 2014/55/EU concerns electronic invoicing in public procurement, commonly called B2G: a business invoices a public authority. The Commission explains the receiving obligation for the listed syntaxes. This European base does not, by itself, define every domestic B2B obligation. For invoices between businesses, use the applicable national source and the receiver’s requirements to establish scope. The directive and the Commission syntax list are linked below.
Common errors to investigate
- BR-CO-10: line-net sum — Recalculate the total of invoice-line net amounts before changing the header total; allowances and taxes belong to their own totals.
- BR-S-08: VAT taxable amount — Group taxable lines by the same VAT rate and include the relevant charges and allowances in that category.
- BR-01: invoice number — Supply the invoice identifier in the business term required by the selected syntax, rather than only in a rendered attachment.
| Check | XSDHub coverage |
|---|---|
| XML structure and fixed rules | EN 16931 validation artefacts 1.3.16; UBL 2.1 and CII D16B XSD |
| Certification and legal acceptance | Not provided |
| Government portal submission | Not provided |
| Peppol | Not supported yet |
Working with the result
Keep a copy of the original XML and compare a failing result with the linked worked example. Fix the source in your invoicing system, export again and rerun the same package so that results remain comparable. The rule links are diagnostic starting points, not a ranking of errors observed among customers. For a batch or an integration, review the existing account limits and API documentation before uploading documents.