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 3 of 11, guides 41 to 60.
EN 16931 checklist for a first invoice
A short check for a first core-model invoice: terms, rules, syntax, profile and receiver test, in order.
Semantic model vs syntax vs transport: three layers that must not be confused
Meaning, encoding and delivery are three separate decisions, and confusing them causes most format arguments.
Using EN 16931 outside public procurement
B2B use of the same model, where it helps, and where a private agreement must add what the standard leaves open.
Versioning and change in EN 16931
How the standard changes, how a profile version is named, and how to plan a migration without breaking live exchange.
Syntaxes and formats explained: UBL, CII and national formats
How the same semantic model is encoded in different syntaxes, and how to choose without confusing syntax with meaning.
Choosing a syntax with a trading partner
A short agreement: profile, syntax, version, validation rules and test invoice, before live exchange.
Cross Industry Invoice (CII) syntax: structure and use
The UN/CEFACT CII message, its header and line structure, and where it is the expected syntax.
Factur-X and ZUGFeRD hybrid formats
A PDF with embedded structured data, the profiles that govern it, and the rule for which layer is authoritative.
Format testing with sample invoices
Sample invoices that test lines, allowances, tax, references and edge cases, not only the happy path.
Format version migration without breaking live exchange
Running two versions in parallel, testing the new version, and retiring the old version with a date both sides agree.
JSON and API invoice formats
When an API payload is an invoice record, when it is only a transport form, and how to keep the two apart.
National formats and when they apply
Why some countries keep a national format, and how to handle a national format beside a European profile.
Syntax conversion between UBL and CII
Converting between bindings without losing business meaning, and the fields that need a human decision.
UBL invoice syntax: structure and common elements
The UBL invoice document, its parties, lines and totals, and the elements most often mapped wrongly.
XML validation and schema checks
Schema validation as the first gate, what it catches, and what it cannot catch about business meaning.
Networks and access points explained: how an invoice is routed
Direct exchange, providers, platforms and the Peppol network, compared by addressing, acknowledgement and responsibility.
Access points: choosing a provider without losing control
What an access point does, what it must not own, and the questions to ask before signing.
Direct exchange vs network exchange
When a direct interface is simpler, when a network is safer, and what each choice costs in onboarding.
Government platforms and portals as routes
When a government platform is the route, what it checks, and how its status messages differ from a network.
Message status and acknowledgements across a network
Transport acknowledgement, delivery and business acceptance are three different statuses, and confusing them hides failures.