EInvoiceLabTools · Formats
74 · View all countries
Technical reference

Electronic invoice standards

Separate the semantic model, XML syntax, exchange profile and national rules before deciding whether an invoice is technically ready.

Semantic standard

EN 16931

The European semantic data model for core electronic invoice elements and business rules.

Open reference
XML syntax

UBL 2.1

OASIS Universal Business Language syntax widely used by Peppol and national invoice profiles.

Open reference
XML syntax

UN/CEFACT CII

Cross Industry Invoice syntax used by profiles including Factur-X and ZUGFeRD.

Open reference
Exchange profile

Peppol BIS Billing

Business interoperability specification for invoice and credit note exchange over Peppol.

Open reference
International model

Peppol PINT

International invoice model with country specifications and local restrictions.

Open reference
Country profiles

National CIUS and fiscal formats

Country-specific restrictions, extensions, schemas, identifiers, reporting and clearance requirements.

Open reference

How the layers fit together

  1. Semantic model: defines business terms, cardinalities and rules.
  2. Syntax: binds those terms to UBL, CII, JSON or a national structure.
  3. Country profile: adds local restrictions, identifiers, tax and routing requirements.
  4. Transmission: defines how the file reaches a tax authority, network, public body or customer.
  5. Acceptance: is determined by the receiving authority or platform, not by a local browser check.