In brief: the direct answer
What the directive requires of public buyers, and what it does not require of every seller. Directive 2014/55/eu and receiver obligations is best approached through obligation placed on the receiver. For directive 2014/55/eu and receiver obligations, the public buyer receiver obligation decides the outcome. For directive 2014/55/eu and receiver obligations, the public buyer receiver obligation missing means rejection. For directive 2014/55/eu and receiver obligations, the public buyer receiver obligation wrongly mapped means wrong meaning. This guide keeps returning to one check for directive 2014/55/eu and receiver obligations: check whether the buyer is in scope before assuming an obligation.
The route stage for directive 2014/55/eu and receiver obligations is Map. At Map, the public buyer receiver obligation is what follows next. For directive 2014/55/eu and receiver obligations, a Map decision cannot be repaired later. For directive 2014/55/eu and receiver obligations, a Map decision cannot be repaired cheaply. Check the public buyer receiver obligation for directive 2014/55/eu and receiver obligations before moving on.
The record at this stage
Follow the invoice as a record through directive 2014/55/eu and receiver obligations. At Map, the record for directive 2014/55/eu and receiver obligations carries the public buyer receiver obligation. Answer the public buyer receiver obligation for directive 2014/55/eu and receiver obligations with evidence. Then the rest of en 16931 and the semantic model becomes easier. Then the rest of directive 2014/55/eu and receiver obligations becomes easier to check.
Describe the record before the system for directive 2014/55/eu and receiver obligations. Systems change, but the public buyer receiver obligation for directive 2014/55/eu and receiver obligations stays. Providers change, but the public buyer receiver obligation for directive 2014/55/eu and receiver obligations stays. Formats change, but the public buyer receiver obligation for directive 2014/55/eu and receiver obligations stays. For directive 2014/55/eu and receiver obligations, ask what record a system produces. For directive 2014/55/eu and receiver obligations, ask what record a system accepts. For directive 2014/55/eu and receiver obligations, ask what status evidence it returns.
What the data must carry
The data that matters most for directive 2014/55/eu and receiver obligations is the public buyer receiver obligation. That is not a slogan for directive 2014/55/eu and receiver obligations. It is what the next directive 2014/55/eu and receiver obligations check looks at. If the public buyer receiver obligation for directive 2014/55/eu and receiver obligations is missing, expect rejection. If the public buyer receiver obligation for directive 2014/55/eu and receiver obligations is ambiguous, expect rejection. If the public buyer receiver obligation for directive 2014/55/eu and receiver obligations is wrongly formatted, expect rejection.
Check the public buyer receiver obligation as the receiver reads directive 2014/55/eu and receiver obligations. For directive 2014/55/eu and receiver obligations, screen correctness is not enough. For directive 2014/55/eu and receiver obligations, file correctness is not enough. For directive 2014/55/eu and receiver obligations, mapping correctness matters too. Use the mapping table for directive 2014/55/eu and receiver obligations first. Use the receiver test for directive 2014/55/eu and receiver obligations second. Use a sample invoice for directive 2014/55/eu and receiver obligations third.
Validation and evidence
For directive 2014/55/eu and receiver obligations, validation has three gates. Directive 2014/55/eu and receiver obligations structure comes first. Directive 2014/55/eu and receiver obligations business rules come second. Directive 2014/55/eu and receiver obligations receiver rules come third. Each directive 2014/55/eu and receiver obligations gate has its own failure message.
A directive 2014/55/eu and receiver obligations rejection should name its rule. A directive 2014/55/eu and receiver obligations rejection should name its field. A directive 2014/55/eu and receiver obligations rejection should name the value sent. A directive 2014/55/eu and receiver obligations rejection should name the value expected. Without those facts, a directive 2014/55/eu and receiver obligations rejection is a delay. Return a directive 2014/55/eu and receiver obligations rejection with that request.
Evidence for directive 2014/55/eu and receiver obligations is what remains afterwards. Keep the directive 2014/55/eu and receiver obligations invoice as exchanged. Keep directive 2014/55/eu and receiver obligations status messages with it. Keep any directive 2014/55/eu and receiver obligations correction linked to it. An auditor for directive 2014/55/eu and receiver obligations asks for that set.
Where it breaks, and the check to make first
The common directive 2014/55/eu and receiver obligations break is simple. For directive 2014/55/eu and receiver obligations, check whether the buyer is in scope before assuming an obligation was skipped. For directive 2014/55/eu and receiver obligations, the receiver found the problem. For directive 2014/55/eu and receiver obligations, the sender must now correct it. For directive 2014/55/eu and receiver obligations, the sender must resend it. For directive 2014/55/eu and receiver obligations, the sender must explain it.
Illustration, with round numbers only, for directive 2014/55/eu and receiver obligations: A seller sends 10 invoices for directive 2014/55/eu and receiver obligations. 1 fail on the public buyer receiver obligation for directive 2014/55/eu and receiver obligations. Checking the public buyer receiver obligation first for directive 2014/55/eu and receiver obligations costs minutes. A directive 2014/55/eu and receiver obligations receiver rejection costs days. Sometimes a directive 2014/55/eu and receiver obligations rejection costs a payment cycle. That is why directive 2014/55/eu and receiver obligations repeats one check: check whether the buyer is in scope before assuming an obligation.
What to verify before acting
Before acting on directive 2014/55/eu and receiver obligations, verify three things. First, jurisdiction and transaction for directive 2014/55/eu and receiver obligations. First, buyer and country for directive 2014/55/eu and receiver obligations. Second, European Commission: European legislation on eInvoicing for directive 2014/55/eu and receiver obligations today. Third, the directive 2014/55/eu and receiver obligations buyer requirement in writing.
A guide on directive 2014/55/eu and receiver obligations organises those questions. A guide on directive 2014/55/eu and receiver obligations cannot answer a specific transaction. This guide on directive 2014/55/eu and receiver obligations gives general information only. This guide on directive 2014/55/eu and receiver obligations is not advice for a specific invoice. For a specific invoice about directive 2014/55/eu and receiver obligations, check European Commission: European legislation on eInvoicing. For a specific question about directive 2014/55/eu and receiver obligations, ask a qualified adviser.
How this guide is layered
Every guide on this site is read through the same twelve layers, in the order that fits its topic: data, format, network, validation, tax, accounting, lifecycle, evidence, direct intent, transaction, jurisdiction, obligation. The layers are a reading method, not a claim about any single system.
Evidence basis: Primary sources named in the sources section, checked 2026-10-27; country guides are dated research routes, not mandate calendars. Scope: General educational information only; no individual legal, tax, accounting or compliance advice; jurisdiction and transaction specific checks remain with the reader.
Related guides
- 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.
- 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.
- 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.
Back to the pillar guide: EN 16931 semantic model explained: meaning before syntax.
In this topic
- EN 16931 semantic model explained: meaning before syntax
- Business rules and validation in EN 16931
- CIUS profiles and extensions: national and sector rules on top of the core
- Common EN 16931 misreadings
- Core invoice model: the business terms that matter
- EN 16931 and Peppol BIS Billing: how the profile implements the model
- EN 16931 checklist for a first invoice
- Semantic model vs syntax vs transport: three layers that must not be confused
- Using EN 16931 outside public procurement
- Versioning and change in EN 16931
Primary sources and further reading
These official resources support the standards and regulatory context. Check their current versions before implementation.
- European Commission: European legislation on eInvoicing - Directive 2014/55/EU and the European standard
- European Commission: Compliance with the eInvoicing standard - Semantic model and UBL/CII syntax bindings