DEFINITION
Information stored in clearly defined fields (number, date, amount, VAT) that software can read without guessing. E-invoicing relies on it, since the XML part of a Factur-X, UBL or CII invoice is structured data.
Structured or not: an example
A PDF invoice shows “Total incl. VAT: €1,248.00” somewhere on the page. You see it at once. Software has to guess where it is and what it means, and can get it wrong. In a structured file, the same amount sits in a field with a fixed name, defined by a standard, so every program reads it the same way.
In a UBL invoice, for instance, the amount to pay sits in a field called PayableAmount, with its currency. There’s nothing left to interpret.
Why e-invoicing depends on it
In France, an e-invoice is issued, sent and received in a structured form that follows the European standard EN 16931. A Factur-X is a readable PDF with an XML file inside, while UBL and CII are XML only. For tax purposes, the structured file is part of the invoice, so a Factur-X must be kept with its XML.
Not every structured file is a full invoice. The MINIMUM and BASIC WL profiles of Factur-X only carry the header, without the invoice lines, and don’t meet EN 16931.
What it changes for you
Structured data does away with retyping and misreading. Clivio reads a Factur-X, a recent ZUGFeRD or a UBL invoice straight from its XML and marks it “Factur-X certified data”. Other documents are read by the AI model, which can slip on a blurry photo, so their figures are worth a check.
Frequently asked questions
Is a PDF invoice structured data?
Not on its own. A plain PDF only shows the information as a page. A Factur-X is different: it’s a PDF that also carries the data in an XML file, so software reads it without guessing.
Which formats carry structured invoice data in France?
Three formats are accepted for e-invoicing: Factur-X, UBL and CII. All three follow the European standard EN 16931.