Glossary
Structured invoice
Also known asstructured electronic invoicestructured e-invoiceXML invoice
A structured invoice is an invoice issued, transmitted and received as structured electronic data that software can process automatically, in a standard format such as Peppol BIS; a PDF, a scan or a Word file is not one, even when signed.
The difference lies in what the recipient’s software receives. A PDF is a page layout meant for people: someone retypes it, or a recognition tool guesses the fields from the layout. A structured invoice carries labelled fields, such as the parties, the lines, the VAT per rate, the totals, the due date and the payment reference, which are imported without retyping and checked against rules before sending.
The definition was added to the Belgian VAT Code by the Law of 6 February 2024. For invoices within the obligation that has applied since 1 January 2026, FPS Finance states that the structured invoice is the only legally required invoice: a PDF or paper copy may be sent voluntarily, and a customer cannot reject an invoice because no PDF is attached. If the data and the PDF disagree, no rule lets one override the other: the invoice is wrong and is corrected with a credit note and, if needed, a new invoice, not with a different PDF.
In practice
- Documents that support an invoice, such as a timesheet or a delivery note, legally form part of it and must travel through the same channel, embedded in the invoice or linked from it, not in a separate email.
- A credit note that corrects a structured invoice must itself be structured, in the same format.
- A hybrid format such as Factur-X or ZUGFeRD, a PDF that carries XML data, counts as the invoice in Belgium only by agreement with the customer, and its embedded XML must conform to EN 16931.
- The channel does not make a PDF structured: it stays a PDF whether it is emailed, posted or uploaded to a portal, and a customer cannot impose its portal without the supplier’s clear written consent.