Photo: free stock photography (Unsplash licence) — see imprint
Structured means machine-readable
A compliant e-invoice carries the invoice data as structured XML — either embedded in the PDF (ZUGFeRD) or as pure XML (XRechnung). Your customer's system reads it without a human retyping anything. That is the whole point of the regulation.
Your data quality is now exposed
Structured invoices are validated. Missing VAT IDs, an unclear tax reason, a malformed address that a human would have shrugged at — all of these now cause a hard rejection. Most e-invoicing projects are really data-cleanup projects.
Decide who generates it
The shop, the ERP, or a service in between. Whichever it is, it must be the same system that owns tax — two systems producing invoices is how two different totals reach the same customer.
Archive properly, from day one
Retention rules apply to the structured document, not just the PDF rendering. Store the XML you actually sent, immutably, and be able to produce it years later.
- A PDF alone will not satisfy e-invoicing rules.
- Structured invoices expose every data-quality gap.
- Archive the XML you sent, not just the PDF.
Frequently asked questions
We will not put a date here, and you should distrust any agency page that does. Structured invoicing is being phased in across Europe in stages, and the dates, the transition periods and who each stage covers are set by legislation that keeps moving — a deadline copied from a blog post is how companies miss the real one. Your Steuerberater will tell you which date applies to your company. Ours is only to make the system ready before it.
Not in the sense the rules mean. A compliant e-invoice carries the invoice data as structured XML that the recipient's system reads without a human retyping anything — that is the entire point of the regulation. A PDF is a picture of an invoice; a person still has to read it and key it in. If your process is 'we email a PDF', that process is what has to change, not the mail template.
Both carry the invoice as structured data; they differ in packaging. ZUGFeRD embeds the XML inside a PDF, so a human sees a normal invoice and a machine reads the data underneath. XRechnung is pure XML with no rendering — built for recipients whose systems only want the data. Which one you send is usually dictated by who receives it, so ask your customers before choosing.
Because structured invoices are validated, and validation does not shrug. A missing VAT ID, an unclear tax reason, an address that is malformed in a way a human would never have noticed — each one now causes a hard rejection instead of a phone call. This is why most e-invoicing projects turn out to be data-cleanup projects wearing a compliance badge. Fix the master data first; the format is the easy half.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer