The Clearance Model
Mandatory e-invoicing in Europe, read at document level
A structured invoice is not a PDF and it is not a spreadsheet. It is an instance of a data model, expressed in a syntax, validated against a set of rules, and constrained further by whatever national profile applies to the transaction. The European standard EN 16931 defines the semantic layer: a list of business terms, each with a cardinality and a data type, grouped into business groups. Two syntaxes bind that model to XML. Every national format in Europe is either one of those bindings, a restriction of one, or something older that a mandate is slowly replacing. This section takes the model apart term by term, explains what a core invoice usage specification does and does not permit, and shows why two invoices that both claim compliance can still be rejected by the same receiver.
A semantic model, two syntax bindings and a set of validation rules. Understanding what the standard fixes and what it deliberately leaves open is the difference between one integration and twelve.
The analysis underneath the anchor piece.
A shared vocabulary that lets a tax administration, a software vendor and an accounts payable manager argue about the same field. Learning to use it saves more time than any other single thing.
Automatic processing works because values come from published lists rather than from free text. Getting the lists right is unglamorous, cheap early, and ruinous late.
A profile narrows the European standard; an extension goes outside it. The distinction sounds academic until an invoice that conforms to the standard is rejected for conforming to the standard.
One file containing a human-readable PDF and a machine-readable invoice. It solves a real transition problem and creates one genuinely dangerous failure mode.
Italy's invoice format predates the European standard and was built for a clearance system. It works. It also shows what a country pays for not adopting the common model.
The most widely implemented European invoice profile is not a format. It is a restriction of the standard plus the rules that make delivery over a shared network possible.
One semantic model, two XML syntaxes, and a genuine architectural decision hiding behind what looks like a file-format preference.
A national profile of the European standard, maintained by a public body, versioned on a fixed cycle. It is worth understanding as a specimen as much as for its own sake.