PDF Invoice vs Structured E-Invoice
Why a PDF is not enough, and what "structured" really means.
Published · Last reviewed · 4 min read · By MYFUNDBOX
A PDF is a picture
A PDF shows an invoice to a person. Software has to guess what each number means, which is why manual entry and OCR are still common.
That is true even for a PDF exported straight from a billing tool rather than scanned. An amount at the bottom of the page might be the net total, the gross total or the amount still due. A person can tell from the label next to it; software has to infer it, and every inference is a chance for an error that someone then corrects by hand.
Structured means defined fields
A structured e-invoice carries each value in a defined field: invoice number, VAT category, net amount, due date. The recipient's software reads it without interpretation.
Those fields follow the European standard EN 16931, which defines the core content of an electronic invoice and the business rules it must pass: totals have to add up, every line needs a VAT category, and a reverse-charge invoice has to carry the right VAT IDs. Because sender and recipient use the same definitions, an invoice can be checked automatically before it is sent and booked automatically when it arrives.
What German law counts as an e-invoice
Since 1 January 2025, German VAT law defines an e-invoice as an invoice that is issued, transmitted and received in a structured electronic format that allows electronic processing and follows EN 16931. A PDF sent by email does not meet that definition. Like paper, it counts as an "other invoice", which is only allowed for domestic B2B sales during the transition periods.
Formats that meet the definition include XRechnung and ZUGFeRD (from version 2.0.1) in its EN 16931-compliant profiles. The ZUGFeRD MINIMUM and BASIC WL profiles do not carry enough invoice data and do not count as e-invoices.
Where ZUGFeRD fits
ZUGFeRD is a hybrid: a PDF/A-3 file that a person can read, with the structured XML embedded inside it. It looks like the PDFs your customers already receive, which makes it a gentle first step.
But it is the embedded XML that counts. If the visible PDF and the XML ever disagree, the XML takes precedence, so it has to be generated from correct, validated data rather than attached as an afterthought.
Why it matters beyond compliance
For the recipient, structured data removes retyping and OCR corrections: invoices can be matched to orders and booked without manual entry. For the sender, invoices that pass validation before they go out are rejected less often, which means fewer corrections and faster payment.
The structured file is also the original invoice for record-keeping. Archive the XML, or the ZUGFeRD file with its embedded XML, not a printout or an image of it.
How to tell what you send today
If your invoices come from a word processor, a spreadsheet or a plain PDF export, they are not e-invoices yet. To change that, use software that produces XRechnung or ZUGFeRD and validates each invoice against EN 16931 before it is sent.
E-Invoicing by MYFUNDBOX does both from one set of invoice data, and explains every validation error in plain language so you can fix it before your customer sees it.
See the compliance timeline for current dates and their review status