E‑Rechnungs-StudioEN 16931 made simple: the standard behind XRechnung & ZUGFeRD
EN 16931 sounds like pure “standards talk”, but the idea is straightforward: it defines which invoice information must be present and how it relates so systems can exchange and process invoices consistently. If you want to understand XRechnung and ZUGFeRD, EN 16931 is the foundation.
EN 16931 in one sentence
EN 16931 defines a shared European invoice data model so e‑invoices can be exchanged and processed automatically across systems.
EN 16931 is not a file format
EN 16931 is the semantic model (fields + rules). Concrete technical formats implement it—commonly XML syntaxes such as UBL or CII (CrossIndustryInvoice).
What data is typically included?
- seller/buyer party data (name, address, identifiers)
- invoice number, date, service period (if needed)
- line items (description, quantity, unit, price, VAT category)
- VAT breakdown
- totals (net/VAT/gross)
- payment terms (due date, payment means, bank details)
How do XRechnung and ZUGFeRD relate?
- XRechnung is a German profile/specification based on EN 16931, with additional constraints.
- ZUGFeRD is a hybrid format: a PDF with embedded EN‑16931 XML.
So both are EN‑16931‑based e‑invoices—they just differ in packaging and profiles.
A tiny example: why validators are strict
Take one line item:
- net: 100.00
- VAT: 19%
- VAT amount: 19.00
- gross: 119.00
The invoice must be consistent across:
- line items → VAT breakdown → totals
- rounding must be explainable
- VAT categories/rates must be correctly coded
Validators enforce this because automation only works when the structured data is internally consistent.
What E‑Rechnungs‑Studio does with this
E‑Rechnungs‑Studio converts an existing PDF invoice into EN‑16931‑based XML (CII), validates it, and helps you correct issues until you can export a verifiable e‑invoice.
FAQ
Why do UBL and CII both exist?
They’re different technical syntaxes that can express EN‑16931 invoice data. Which one you need depends on your recipient and delivery channel.
Do all e‑invoices have to follow EN 16931?
In Germany, the common e‑invoice formats for many scenarios are EN‑16931‑based. Specific sector profiles or exceptions may apply—always follow your recipient’s requirement.
Next step
Once EN 16931 “clicks”, XRechnung/ZUGFeRD validation becomes much easier. The fastest path is hands‑on: upload a PDF, review, iterate.