Topic 04 of 20
EN 16931 and the semantic model
The European semantic model, core invoice model, business rules and CIUS profiles, kept apart from syntax.
The pillar guide
EN 16931 semantic model explained: meaning before syntax - The European standard for the core invoice model, its business terms, business rules and the separation of meaning from encoding.
Working guides in this topic
- Business rules and validation in EN 16931 - How business rules turn the model into testable checks, and what a rule failure actually tells you.
- CIUS profiles and extensions: national and sector rules on top of the core - Core Invoice Usage Specifications, what they may restrict, and what they must not break.
- Common EN 16931 misreadings - Compliance with a syntax is not compliance with the model, and a valid file is not a valid business invoice.
- Core invoice model: the business terms that matter - The central business terms of EN 16931, grouped by party, line, total and tax, with what each term means.
- Directive 2014/55/EU and receiver obligations - What the directive requires of public buyers, and what it does not require of every seller.
- EN 16931 and Peppol BIS Billing: how the profile implements the model - How Peppol BIS Billing 3.0 implements the core model, and where its rules add to the standard.
- 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.