PDF or structured invoice: choosing the right channel
Decision guide for Belgian B2B: when PDF alone fails, when a hybrid PDF plus structured file works, and how each choice hits bookkeeping.
Updated
- Belgium
A PDF is a page image people can read. A structured invoice is machine-readable data (typically EN 16931 in UBL) that software can book without retyping. Emailing a PDF is not Peppol delivery. When the Belgian B2B mandate applies, the structured file is the invoice; the PDF is a companion.
Example
Atelier Nord emails a pretty PDF to a Belgian SRL and thinks the job is done. The buyer’s AP never receives data. After they send the same amounts as Peppol BIS Billing, the invoice books from XML. The PDF stays as a reading copy.
One decision: channel and format
This article is about how you exchange the invoice, not whether the 2026 mandate applies. For who/when/scope, see the Belgian B2B e-invoicing obligation.
A PDF answers "can a human read this?" A structured invoice answers "can software book this without guessing?" Belgian in-scope B2B needs the second answer.
Decision table: when PDF alone fails
| Situation | PDF by email alone | Structured (typically Peppol) | Hybrid (structured + PDF) |
|---|---|---|---|
| In-scope Belgian B2B from 2026 | Fails the mandate channel | Meets the exchange requirement | Best of both worlds |
| Buyer AP wants auto-booking | OCR / re-keying | Direct field mapping | Structured drives books; PDF for approvers |
| Delivery disputes ("never received") | Weak email evidence | Network delivery status | Same as structured, plus human copy |
| Consumer (B2C) or other out-of-scope flow | Often still practical | Usually unnecessary | Optional |
Use PDF alone only when the flow is outside the structured B2B mandate. When the mandate applies, PDF alone is the wrong channel, even if the layout looks perfect.
What "structured" means here
- Structured invoice
An electronic invoice encoded as standardised data (for example EN 16931 in UBL), so systems can read parties, lines, VAT, and totals without interpreting a page image.
On Peppol, that usually means EN 16931 semantics, UBL syntax, and Peppol BIS Billing. Details: EN 16931 and UBL.
Hybrid PDF + structured (recommended pattern)
Most Belgian SMEs keep both:
| Role | File | Use |
|---|---|---|
| Source of truth | Structured e-invoice | Compliance, validation, ledger import, retention |
| Companion copy | PDF rendered from the same data | Approvals, attachments to cases, quick human review |
Generate the PDF from the structured data. Never invent a second invoice that disagrees with the XML.
Bookkeeping impact
| Process step | PDF-only world | Structured world |
|---|---|---|
| Capture | Manual entry or OCR | Import labelled fields |
| Exceptions | Layout and OCR errors | Schema / business-rule failures upstream |
| Matching | Fragile text compare | Stable identifiers and line data |
| Close speed | Scales poorly with supplier diversity | Scales with validated volume |
| Archive | PDF snapshot | Structured original + optional PDF |
OCR can help during transition, but it remains guesswork on presentation. Structured invoices move exceptions to before posting, which is where finance control belongs.
Practical channel checklist
- For each counterparty, decide: in-scope B2B or not (obligation scope)
- In-scope: send and receive structured; offer PDF as companion only
- Out of scope: PDF (or another agreed channel) may still be enough
- Archive the structured original when it is the legal/electronic invoice
FAQ
Is a PDF a structured invoice?
No. A PDF is a page image. A structured invoice is data software can process without retyping.
Does emailing a PDF count as Peppol?
No. Peppol delivers a structured document through Access Points, not an email attachment.
When is PDF still fine?
Out-of-scope flows such as many B2C sales, or as a human companion next to a structured B2B send.
Which file should I archive?
The structured original when it is the electronic invoice. Keep PDF as a reading copy from the same data.
Can I send both?
Yes. Structured for mandated B2B; PDF as companion only. Do not treat the PDF as a second source of truth.