All 220 guides
Every guide opens with a route check: the stage, the data, the validation to expect, and the first check to make. Page 1 of 11, guides 1 to 20.
E-invoicing explained: structured invoices, mandates, formats and software
A practical introduction to e-invoicing, including structured invoice data, mandate models, invoice formats, delivery networks, validation, tax reporting, accounting workflows and software.
A brief history of structured invoicing, without a mandate calendar
From EDI to EN 16931 to Peppol and real-time reporting, as a sequence of ideas, not a list of deadlines.
B2B, B2G and B2C invoicing in one view
Three transaction types, three different obligation patterns, and why a format that works for one may fail for another.
Data in motion: why the invoice is a record, not a file
The thesis of this guide: an invoice travels as data through systems, and every stage can change what the next system can do.
E-invoicing glossary in plain language
Semantic model, syntax, profile, access point, validation and status, each defined by what it does in an exchange.
E-invoicing myths that waste implementation time
A PDF is enough, one format works everywhere, and validation is a single pass, each tested against what actually happens.
Invoice anatomy: reading a structured invoice field by field
Document id, parties, lines, totals and status, read in the order a receiving system checks them.
Questions to ask before any implementation
Scope, buyer, format, route and evidence, asked in that order, before any software is chosen.
Structured invoice vs PDF: what a system can do with each
How a structured e-invoice differs from a PDF, and why searchable text is not the same as machine-readable data.
What does not automatically count as a structured e-invoice
A PDF made on a computer, a scanned image and an emailed spreadsheet are not structured invoices by themselves.
Who participates in an exchange, and what each party owes
Seller, buyer, provider, network and tax authority, and the hand-off each one is responsible for.
Structured vs readable documents explained: PDF, hybrid and structured compared
The pillar for document forms: what each form carries, what a system can do with it, and where each one breaks.
Accessible readable invoices for people, not only systems
Readable views that work for people with different needs, and why accessibility belongs in the view, not as an afterthought.
Choosing a document form by receiver
A decision sequence: receiver requirement, format, route, then document form, in that order.
Converting PDFs to structured invoices: a careful method
Extraction, mapping, validation and human review, with a rejection rule for low-confidence fields.
Document form and audit evidence
What an auditor needs from each form, and why the structured layer plus status evidence is stronger than a PDF alone.
Document form checklist before sending
A short pre-send check: form, data, validation, route and readable view, each signed off in order.
Human-readable views of structured invoices
A structured invoice can still be shown to a person, and the view must be generated from the data, not typed beside it.
Hybrid invoices: a PDF view with structured data attached
Factur-X and similar hybrids, how the two layers relate, and which layer wins when they disagree.
PDF invoice limits: what a readable invoice cannot guarantee
Layout, searchable text and visual totals, and the three ways a PDF fails as machine-readable data.