← All guides · EN 16931 & validation
Structured invoice fields: every field an EN 16931 invoice needs, checked
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
A complete structured invoice carries: invoice number (BT-1), issue date (BT-2), type code (BT-3), currency (BT-5); the seller's name (BT-27), address, country (BT-40) and VAT identifier (BT-31); the buyer's name (BT-44), address, country (BT-55) and — for cross-border reverse charge — VAT identifier (BT-48); at least one line (BG-25) with item name (BT-153), quantity (BT-129), net price (BT-146), VAT category (BT-151) and rate (BT-152); plus allowances, charges and prepaid amounts where they exist.
What fields does a structured invoice have?
The fields are the EN 16931 business terms (BT) and groups (BG) that the validator checks: header terms (BT-1 number, BT-2 issue date, BT-3 type code, BT-5 currency), party terms (seller BT-27/BT-31/BT-40, buyer BT-44/BT-48/BT-55, with city and postal code terms checked alongside), and line terms within BG-25 (BT-153 name, BT-129 quantity, BT-146 price, BT-151 category, BT-152 rate). The converter's form is organised in exactly these sections: §1 invoice, §2 seller, §3 buyer, §4 lines.
Header fields: identity of the document
BT-1, the invoice number, must be present — and in your own practice unique and sequential. BT-2, the issue date, must be present and a real ISO date; it drives payment terms and selects the mandate phase for the invoice. BT-3, the type code, must be 380, 381, 384 or 389 — the document's verb. BT-5, the currency, must be a supported ISO code (EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK or NOK in this engine). The due date completes the header's commercial picture.
These five are the fields a human glances at and a system keys on. Every downstream process — booking, matching, paying, auditing — joins on the number, dates by the issue date, and acts on the type code. Header sloppiness is therefore the most expensive kind: a wrong digit in BT-1 orphans the invoice in two systems at once.
Party fields: who, where, and under which tax identity
The seller block needs a name, street, city, postal code, country — and, for cross-border B2B, the VAT identifier (BT-31). The buyer block mirrors it: name (BT-44), address fields, country (BT-55) — and, when any line is reverse charge across borders, the buyer's VAT identifier (BT-48). The validator checks city and postal code with their own rules, because routing and booking systems build on complete addresses, not on 'the client knows where they live'.
The practical source of party data is the client record, not the invoice form: entered once at onboarding, verified once, reused forever. Invoices typed fresh each month re-roll the dice on every field. Treat party blocks as master data with a change process, and the per-invoice party check becomes a formality — the systems' favourite kind of check, the one that always passes.
Line fields: where the money is explained
BG-25, the lines group, must contain at least one line (BR-16). Each line needs its item name (BT-153) — a real description, not 'services'; its quantity (BT-129), positive; its net unit price (BT-146), never negative; its VAT category (BT-151) from the accepted list; and its rate (BT-152), agreeing with the category — above zero for S, exactly zero for Z, E and AE. Line extensions are computed (quantity × price), never declared by hand.
Line craft is invoice craft. One line per item and per tax treatment; quantities that mean something (days, hours, units, or 1 for a lump-sum engagement with the scope in the name); names a stranger at the client's firm can approve without emailing you. The client's approver and their system read the same lines: write for both readers at once.
Adjustment and total fields: the derived layer
Allowances, charges and prepaid amounts are fields in their own right — document allowance total, charge total, prepaid amount — feeding the computation that produces the totals block: line total, tax-exclusive amount, the tax breakdown per category-rate pair, tax total, and payable amount. In a generated UBL file those totals appear as the tax total and legal monetary total elements; in the data you enter, they are outputs, not inputs.
That inversion is the structured model's signature: the only totals you ever 'enter' are facts (an allowance you granted, a deposit you received). Everything else derives. When a legacy process demands you state totals — a portal asking for the payable figure — state the computed figure from the conversion result, and let the BR-CO comparison verify the agreement rather than your memory.
Fields people forget — and what each omission costs
The due date, forgotten, costs a payment cycle's clarity: the client's system schedules by the document, and an absent due date becomes a query. The buyer's VAT identifier, forgotten on a reverse-charge invoice, costs a validation failure — cheap here, expensive at the client's intake. The seller's identifier on cross-border work, forgotten, costs the same. A line name reduced to 'work', cost: the approver's confidence and a clarifying email thread. A currency typed as a word, cost: BR-04.
Run this page as a pre-flight once per template, not once per invoice: build a checklist invoice containing every field your billing ever uses, convert it, and keep the passing configuration as the template. Templates that have passed once, with all fields present and correctly sourced, make the per-invoice act a matter of changing values — the safest change there is.
The field checklist (use it per template)
- Header: number (BT-1), ISO issue date (BT-2), type code (BT-3: 380/381/384/389), ISO currency (BT-5), due date stated.
- Seller: name, street, city, postal code, country — and VAT identifier (BT-31) permanently in the template.
- Buyer: name, full address, country — and VAT identifier (BT-48) wherever cross-border reverse charge may apply.
- Lines (BG-25): at least one; each with name (BT-153), positive quantity (BT-129), non-negative price (BT-146), category (BT-151) and agreeing rate (BT-152).
- Adjustments as fields: allowances, charges, prepaid — with every total left for the engine to derive.
Worked example: a complete field set, one invoice
Invoice 2026-077: BT-1 '2026-077'; BT-2 2026-11-14; BT-3 380; BT-5 EUR; due date 2026-12-14. Seller: name, street, city, postal code, country DE, VAT identifier present. Buyer: name, address complete, country BE, VAT identifier present. Lines (BG-25): two lines — 'Integration consulting, 4 days', quantity 4 at EUR 800.00, category AE rate 0; 'Documentation pack', quantity 1 at EUR 350.00, category AE rate 0. No allowances or charges; prepaid EUR 0.00.
Computed: line total EUR 3,550.00; AE breakdown taxable EUR 3,550.00, tax EUR 0.00; payable EUR 3,550.00. Every field the validator looks for is present because the template was built from this checklist — the invoice passes on its first conversion, and the acceptance stamp (Belgium, 2026: structured required) tells the sender the UBL is the operative copy.
Frequently asked questions
Which fields are absolutely mandatory?
Number, issue date, type code and currency in the header; seller and buyer names, countries, cities and postal codes; at least one line with name, quantity, price, category and rate. Identifiers become mandatory under the cross-border rules.
Are totals fields I fill in?
No — totals are derived: line extensions, tax breakdown, tax-exclusive amount, tax total and payable amount are computed from lines, allowances, charges and prepaid. Supplying totals invites BR-CO mismatches.
What is BG-25?
The business group holding the invoice lines. BR-16 requires it to contain at least one line — an invoice of pure totals is not an invoice under the standard.
Do I need the buyer's VAT ID on every invoice?
The hard rule requires it when a cross-border line uses reverse charge (AE). Collecting it for every B2B client at onboarding is the practical policy — the need then never arises unprepared.
Which currencies does the validator accept?
EUR, USD, GBP, CHF, PLN, SEK, DKK, CZK, HUF, RON, BGN, HRK and NOK — real ISO 4217 codes; a currency written as a word fails BR-04.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- What is EN 16931 and why does your invoice need to follow it?
- EN 16931 business rules explained: what BR codes mean when validation fails
- Invoice numbers and dates on an e-invoice: the rules that keep your sequence clean
- Cross-border invoices: when seller and buyer VAT identifiers are required
- Convert your first invoice free: a walkthrough of the one-invoice job