SearchStart a task
Formats›EN 16931
European semantic standard · active

EN 16931 semantic invoice model

The European semantic data model for core electronic invoice business terms. National CIUS profiles and Peppol rules add restrictions on top of the core model.

UBL Invoice/CreditNote XMLUN/CEFACT CII XML

Current version and implementation status

Version noteValidation artefacts maintained independently from the published standard
Statusactive
Reviewed2026-08-02
FamilyEuropean semantic standard
Open official technical source

How to recognize the profile

Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.

  • urn:cen.eu:en16931:2017
  • CustomizationID
  • Business terms BT-*
  • Business rules BR-*

Production validation stack

  1. 1
    XML schema validity

    Confirm that the document is well formed and structurally compatible with the intended EN 16931 syntax.

  2. 2
    EN 16931 Schematron rules

    Apply semantic and business-rule checks rather than accepting a file merely because it parses.

  3. 3
    Code-list validation

    Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.

  4. 4
    National CIUS or extension rules

    Apply the national, network or authority restrictions that narrow the base syntax.

EInvoiceLab’s browser tools provide detection, inspection and technical preflight. A profile is only production-valid after applying the correct official artefacts and obtaining the required network or authority outcome.

Common errors and corrective action

!
Missing mandatory business terms

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Totals do not reconcile

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Invalid code-list values

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Profile rules stricter than the core model

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

Countries using or referencing this profile

DEGermanyXRechnung, ZUGFeRD / Factur-XFRFranceFactur-X, UBL, CIIITItalyFatturaPA / Sistema di InterscambioESSpainFacturae, VERI*FACTU, SIIPTPortugalCIUS-PT, SAF-T(PT), QR / ATCUDBEBelgiumPeppol BIS Billing, Belgian CIUSNLNetherlandsNLCIUS, Peppol BIS BillingDKDenmarkOIOUBL, Peppol BIS BillingNONorwayEHF, Peppol BIS BillingFIFinlandFinvoice, TEAPPSXML, PeppolSESwedenPeppol BIS Billing, SvefakturaATAustriaebInterface, Peppol BIS BillingIEIrelandPeppol BIS BillingLULuxembourgPeppol BIS BillingRORomaniaRO e-Factura / RO_CIUSPLPolandKSeF FA(3)GRGreecemyDATA, Peppol B2GHRCroatiaeRačun / Fiscalization 2.0SISloveniae-SLOG, PeppolSKSlovakiaIS EFA / PeppolCZCzechiaISDOC, EN 16931 / PeppolEEEstoniaEstonian e-invoice, PeppolLVLatviaLatvian e-invoice / PeppolLTLithuaniaSABIS, Peppol BIS BillingCYCyprusEN 16931 / PeppolMTMaltaPeppol / EN 16931ISIcelandPeppol BIS Billing

Questions people ask

What is EN 16931?

The European semantic data model for core electronic invoice business terms. National CIUS profiles and Peppol rules add restrictions on top of the core model.

How is EN 16931 validated?

A production check normally applies XML schema validity, EN 16931 Schematron rules, Code-list validation, National CIUS or extension rules. Local browser preflight cannot replace the official validation artefacts or authority outcome.

Which version should I use?

The current research note is: Validation artefacts maintained independently from the published standard. Confirm release notes at the official source before production deployment.

Practical tools

Inspect and prepare EN 16931 files

Tools

Technical invoice preflight

Check parseability, core fields, identifiers and arithmetic before submission.

Open tool
Tools

Invoice error explainer

Explain recognized EN 16931, Peppol and national rule messages.

Open tool
Tools

Invoice code-list checker

Check common currency, country, tax-category and payment-means codes.

Open tool
Readiness wizard

E-invoice schema and version finder

Find the country system, structured format family, likely active version markers and official technical source.

Open tool