In brief: the direct answer
The UN/CEFACT CII message, its header and line structure, and where it is the expected syntax. Cross industry invoice (cii) syntax is best approached through CII as another binding of the same model. For cross industry invoice (cii) syntax, the CII header and line structure decides the outcome. For cross industry invoice (cii) syntax, the CII header and line structure missing means rejection. For cross industry invoice (cii) syntax, the CII header and line structure wrongly mapped means wrong meaning. This guide keeps returning to one check for cross industry invoice (cii) syntax: confirm CII is the expected syntax before mapping it.
The route stage for cross industry invoice (cii) syntax is Map. At Map, the CII header and line structure is what follows next. For cross industry invoice (cii) syntax, a Map decision cannot be repaired later. For cross industry invoice (cii) syntax, a Map decision cannot be repaired cheaply. Check the CII header and line structure for cross industry invoice (cii) syntax before moving on.
The record at this stage
Follow the invoice as a record through cross industry invoice (cii) syntax. At Map, the record for cross industry invoice (cii) syntax carries the CII header and line structure. Answer the CII header and line structure for cross industry invoice (cii) syntax with evidence. Then the rest of syntaxes and formats becomes easier. Then the rest of cross industry invoice (cii) syntax becomes easier to check.
Describe the record before the system for cross industry invoice (cii) syntax. Systems change, but the CII header and line structure for cross industry invoice (cii) syntax stays. Providers change, but the CII header and line structure for cross industry invoice (cii) syntax stays. Formats change, but the CII header and line structure for cross industry invoice (cii) syntax stays. For cross industry invoice (cii) syntax, ask what record a system produces. For cross industry invoice (cii) syntax, ask what record a system accepts. For cross industry invoice (cii) syntax, ask what status evidence it returns.
What the data must carry
The data that matters most for cross industry invoice (cii) syntax is the CII header and line structure. That is not a slogan for cross industry invoice (cii) syntax. It is what the next cross industry invoice (cii) syntax check looks at. If the CII header and line structure for cross industry invoice (cii) syntax is missing, expect rejection. If the CII header and line structure for cross industry invoice (cii) syntax is ambiguous, expect rejection. If the CII header and line structure for cross industry invoice (cii) syntax is wrongly formatted, expect rejection.
Check the CII header and line structure as the receiver reads cross industry invoice (cii) syntax. For cross industry invoice (cii) syntax, screen correctness is not enough. For cross industry invoice (cii) syntax, file correctness is not enough. For cross industry invoice (cii) syntax, mapping correctness matters too. Use the mapping table for cross industry invoice (cii) syntax first. Use the receiver test for cross industry invoice (cii) syntax second. Use a sample invoice for cross industry invoice (cii) syntax third.
Validation and evidence
For cross industry invoice (cii) syntax, validation has three gates. Cross industry invoice (cii) syntax structure comes first. Cross industry invoice (cii) syntax business rules come second. Cross industry invoice (cii) syntax receiver rules come third. Each cross industry invoice (cii) syntax gate has its own failure message.
A cross industry invoice (cii) syntax rejection should name its rule. A cross industry invoice (cii) syntax rejection should name its field. A cross industry invoice (cii) syntax rejection should name the value sent. A cross industry invoice (cii) syntax rejection should name the value expected. Without those facts, a cross industry invoice (cii) syntax rejection is a delay. Return a cross industry invoice (cii) syntax rejection with that request.
Evidence for cross industry invoice (cii) syntax is what remains afterwards. Keep the cross industry invoice (cii) syntax invoice as exchanged. Keep cross industry invoice (cii) syntax status messages with it. Keep any cross industry invoice (cii) syntax correction linked to it. An auditor for cross industry invoice (cii) syntax asks for that set.
Where it breaks, and the check to make first
The common cross industry invoice (cii) syntax break is simple. For cross industry invoice (cii) syntax, confirm CII is the expected syntax before mapping it was skipped. For cross industry invoice (cii) syntax, the receiver found the problem. For cross industry invoice (cii) syntax, the sender must now correct it. For cross industry invoice (cii) syntax, the sender must resend it. For cross industry invoice (cii) syntax, the sender must explain it.
Illustration, with round numbers only, for cross industry invoice (cii) syntax: A seller sends 20 invoices for cross industry invoice (cii) syntax. 1 fail on the CII header and line structure for cross industry invoice (cii) syntax. Checking the CII header and line structure first for cross industry invoice (cii) syntax costs minutes. A cross industry invoice (cii) syntax receiver rejection costs days. Sometimes a cross industry invoice (cii) syntax rejection costs a payment cycle. That is why cross industry invoice (cii) syntax repeats one check: confirm CII is the expected syntax before mapping it.
What to verify before acting
Before acting on cross industry invoice (cii) syntax, verify three things. First, jurisdiction and transaction for cross industry invoice (cii) syntax. First, buyer and country for cross industry invoice (cii) syntax. Second, European Commission: Compliance with the eInvoicing standard for cross industry invoice (cii) syntax today. Third, the cross industry invoice (cii) syntax buyer requirement in writing.
A guide on cross industry invoice (cii) syntax organises those questions. A guide on cross industry invoice (cii) syntax cannot answer a specific transaction. This guide on cross industry invoice (cii) syntax gives general information only. This guide on cross industry invoice (cii) syntax is not advice for a specific invoice. For a specific invoice about cross industry invoice (cii) syntax, check European Commission: Compliance with the eInvoicing standard. For a specific question about cross industry invoice (cii) syntax, 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: format, network, validation, tax, accounting, lifecycle, evidence, direct intent, transaction, jurisdiction, obligation, data. 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
- 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.
- 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.
- National formats and when they apply - Why some countries keep a national format, and how to handle a national format beside a European profile.
Back to the pillar guide: Syntaxes and formats explained: UBL, CII and national formats.
In this topic
- Syntaxes and formats explained: UBL, CII and national formats
- Choosing a syntax with a trading partner
- Factur-X and ZUGFeRD hybrid formats
- Format testing with sample invoices
- Format version migration without breaking live exchange
- JSON and API invoice formats
- National formats and when they apply
- Syntax conversion between UBL and CII
- UBL invoice syntax: structure and common elements
- XML validation and schema checks
Primary sources and further reading
These official resources support the standards and regulatory context. Check their current versions before implementation.
- European Commission: Compliance with the eInvoicing standard - Semantic model and UBL/CII syntax bindings
- OpenPeppol: Peppol BIS Billing 3.0 - Billing profile, information elements and validation