What Is an E-Invoice? XRechnung, ZUGFeRD & Peppol Explained
An e-invoice is structured data, not a PDF. Learn how EN 16931, XRechnung, ZUGFeRD/Factur-X and Peppol fit together, Germany's deadlines and how to create one free.
Published by Best Free Invoice GeneratorEdited by Jayant PathariyaPublished
AI-assisted writing with illustrative examples and linked official sources. General guidance; no professional tax or legal review is claimed. How these guides are prepared.
An e-invoice is an invoice issued, sent and received as structured data that software can read without a person retyping it. A PDF emailed to a customer is an electronic document, but under most e-invoicing rules it is not an e-invoice: the buyer’s system cannot reliably tell which number is the total and which is the VAT.
Several European countries now require e-invoices between businesses, and many public-sector buyers already insist on them. This guide explains the formats, what changes in practice and how to create one from an ordinary invoice.
PDF invoice or e-invoice?
Both versions can carry exactly the same facts. The difference is who, or what, is expected to read them.
In an e-invoice, each fact has a defined place and meaning. The European standard numbers them as “business terms”: BT-1 is the invoice number, BT-112 the total including VAT, BT-84 the payee’s account. Because every field is defined, the recipient can validate the invoice automatically and post it to the right accounts.
EN 16931: the common standard
The European standard EN 16931 defines the content of an electronic invoice: which fields exist, which are mandatory and the business rules that connect them. For example, every line must have exactly one VAT category and rate, and the VAT breakdown must add up to the VAT total.
EN 16931 can be written in two XML syntaxes:
| Syntax | Used by | Typical file |
|---|---|---|
| UBL 2.1 | Peppol BIS Billing 3.0, many national systems | Invoice or CreditNote XML |
| UN/CEFACT CII | XRechnung (CII variant), ZUGFeRD and Factur-X | CrossIndustryInvoice XML |
National formats add their own rules on top of EN 16931. These are called CIUS (core invoice usage specifications).
The formats you will meet
XRechnung is Germany’s national CIUS. Federal and state public-sector buyers require it, and it is widely accepted for business-to-business invoices. It adds rules such as a mandatory buyer reference (the Leitweg-ID for public bodies), seller contact details and a postcode and city for both parties.
ZUGFeRD / Factur-X is a German-French standard that combines a PDF for people with embedded EN 16931 CII XML for software. The PDF must be a PDF/A-3 archive file, with the XML attached as factur-x.xml. Its EN 16931 profile contains the same data as an XRechnung in CII syntax, without the extra German rules.
Peppol BIS Billing 3.0 is the UBL-based format exchanged over the Peppol network, which connects businesses through certified access points. It is used across much of Europe; countries such as Australia, New Zealand and Singapore also use Peppol, with their own national specifications. Each participant has a Peppol ID such as 0088:5790000435968.
Germany’s timeline
Germany’s rules are a good example of how a mandate is phased in:
- From 1 January 2025, all businesses must be able to receive e-invoices for domestic B2B supplies.
- From 1 January 2027, businesses with prior-year turnover above €800,000 must issue e-invoices.
- From 1 January 2028, the obligation applies to the remaining businesses.
There are exceptions, including invoices up to €250 and certain other cases, and transitional rules for EDI. Read the text of § 14 UStG and current guidance from the Federal Ministry of Finance, or ask a tax adviser, to confirm what applies to you. Other countries publish their own timelines; check your tax authority’s guidance before relying on a summary.
What you need before creating one
E-invoices are stricter than PDFs. Have these ready:
- Your VAT number (or, if you do not charge VAT, your tax number). Every e-invoice must identify the seller.
- Full addresses with the postcode and city on the last line, and both parties’ countries.
- One VAT rate per line. Split a line in two if parts of it are taxed differently.
- An exemption reason for any line without VAT, such as “Kleinunternehmer gemäß § 19 UStG” or “Reverse charge”.
- A due date or payment terms, and your IBAN if the customer pays by bank transfer.
- For XRechnung, the buyer’s reference or Leitweg-ID. For Peppol, both Peppol IDs.
How to create an e-invoice for free
- Open the e-invoice generator or any invoice page and fill in the invoice as usual.
- Add your IBAN to the payment instructions, or set up a SEPA payment QR code.
- Choose More → Export e-invoice (XML) and pick XRechnung, ZUGFeRD / Factur-X or Peppol.
- Fix anything the exporter lists. It checks the EN 16931 rules it can verify from your invoice before it lets you download.
- Download the XML file and send it the way your customer requests: by email, upload to a portal, or through a Peppol access point.
For ZUGFeRD / Factur-X you can also choose Download Factur-X PDF: a PDF/A-3 file of your invoice with the XML embedded inside, so one file works for both people and software. Everything is created in your browser; nothing is uploaded. The tool does not send invoices through Peppol or government portals. Check the result with your recipient’s validator, especially the first time.
Common rejection reasons
- Totals that do not reconcile. E-invoices calculate VAT per rate across the whole invoice; per-line rounding can produce a different total. Applying taxes to the whole document avoids this.
- Missing identifiers. No VAT number, no buyer reference, or the wrong Peppol scheme.
- Free-text addresses. The postcode and city could not be separated.
- Two taxes on one line. EN 16931 has no concept of combined taxes such as GST plus PST on a single line.
Fix the invoice itself, then export again, so your PDF and XML always match.
Put it into practice
Free, no sign-up, no watermark. Create and export in your browser.
Create an e-invoice →