XRechnung mandatory fields: all required data with BT number and validation rule
Which fields must an XRechnung contain to pass validation? This page lists all mandatory fields under EN 16931 and XRechnung 3.0 with the BT number and the rule that fires when one is missing. It also covers the fields that become mandatory only under a condition, and the particulars that tax law requires but validation does not enforce.
Where the obligation comes from
The mandatory fields of an XRechnung have three sources. For validation this makes no difference: if one is missing, the invoice is invalid.
- EN 16931, the European standard. Its rules are called
BR-01toBR-65andBR-CO-…. They apply to every e-invoice under the standard, so also to ZUGFeRD from the profile EN 16931. - XRechnung, the German implementation. Its rules are called
BR-DE-…. They make some fields mandatory that are optional in the standard: buyer reference, contact details, city and postal code, payment details. - Peppol rules, which XRechnung 3.0 adopted. Two of them concern the obligation: the electronic address of seller and buyer.
The BR-DE rules apply only if the invoice identifies itself as an XRechnung (BT-24, see below). A ZUGFeRD invoice in the profile EN 16931 therefore does not have to contain a telephone number or buyer reference. But if your recipient requires XRechnung, for example an authority, the whole list applies.
Invoice header
| BT | Field | Rule | Note |
|---|---|---|---|
| BT-1 | Invoice number | BR-02 | unique per invoice |
| BT-2 | Invoice date | BR-03 | format YYYY-MM-DD in UBL, YYYYMMDD in CII |
| BT-3 | Invoice type code | BR-04, BR-DE-17 | only certain codes, e.g. 380 invoice, 381 credit note, 384 correction (guide: invoice type code) |
| BT-5 | Currency | BR-05 | EUR, not “€” |
| BT-10 | Buyer reference | BR-DE-15 | for authorities the Leitweg-ID (German public-sector routing ID, guide: Leitweg-ID), otherwise a reference of the buyer |
| BT-24 | Specification identifier | BR-01, BR-DE-21 | for XRechnung 3.0: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0 |
Seller
| BT | Field | Rule | Note |
|---|---|---|---|
| BT-27 | Name | BR-06 | |
| BG-5 | Address | BR-08 | the group itself |
| BT-37 | City | BR-DE-3 | |
| BT-38 | Postal code | BR-DE-4 | |
| BT-40 | Country code | BR-09 | DE, two letters |
| BT-34 | Electronic address | PEPPOL-EN16931-R020, BR-62 | with scheme, e.g. schemeID="EM" for an e-mail address |
| BG-6 | Contact | BR-DE-2 | the group itself |
| BT-41 | Contact person | BR-DE-5 | name or department |
| BT-42 | Telephone | BR-DE-6, BR-DE-27 | at least three digits |
| BT-43 | BR-DE-7, BR-DE-28 | exactly one @ | |
| BT-29, BT-30 or BT-31 | Identifier, registration number or VAT ID | BR-CO-26 | at least one of them |
| BT-31 or BT-32 | VAT ID (USt-IdNr.) or tax number (Steuernummer) | BR-DE-16 | for VAT category S, Z, E, AE, K, G, L or M (so almost always); alternatively a tax representative (BG-11) |
Buyer
| BT | Field | Rule | Note |
|---|---|---|---|
| BT-44 | Name | BR-07 | |
| BG-8 | Address | BR-10 | the group itself |
| BT-52 | City | BR-DE-8 | |
| BT-53 | Postal code | BR-DE-9 | |
| BT-55 | Country code | BR-11 | |
| BT-49 | Electronic address | PEPPOL-EN16931-R010, BR-63 | for authorities often the Leitweg-ID with schemeID="0204"; if in doubt, ask the recipient |
Payment
| BT | Field | Rule | Note |
|---|---|---|---|
| BG-16 | Payment instructions | BR-DE-1 | even if it is already paid |
| BT-81 | Payment means type code | BR-49 | e.g. 58 SEPA credit transfer, 59 SEPA direct debit |
What is added per payment means is listed below under the conditional fields and in detail in the guide on payment details.
Totals and VAT
| BT | Field | Rule | Note |
|---|---|---|---|
| BT-106 | Sum of line net amounts | BR-12 | |
| BT-109 | Total amount without VAT | BR-13 | |
| BT-112 | Total amount with VAT | BR-14 | |
| BT-115 | Amount due for payment | BR-15 | |
| BG-23 | VAT breakdown | BR-CO-18 | at least one, one per VAT category and rate |
| BT-116 | VAT category taxable amount | BR-45 | |
| BT-117 | VAT category tax amount | BR-46 | also 0.00 |
| BT-118 | VAT category code | BR-47 | (guide: VAT categories) |
| BT-119 | VAT category rate | BR-DE-14 | always in XRechnung, also 0; the standard lets it be omitted only for transactions outside the scope of VAT (BR-48) |
That the totals are present is one half. They must also fit together; that is checked by the rules BR-CO-10 to BR-CO-16 (guide: rounding and discounts).
Invoice line
Every invoice needs at least one line (BR-16). Every line needs:
| BT | Field | Rule | Note |
|---|---|---|---|
| BT-126 | Line number | BR-21 | |
| BT-129 | Quantity | BR-22 | |
| BT-130 | Unit of measure | BR-23 | as a code, e.g. H87 piece, HUR hour, C62 unit |
| BT-131 | Line net amount | BR-24 | |
| BT-146 | Net price | BR-26 | |
| BT-151 | Line VAT category code | BR-CO-04 | |
| BT-153 | Item name | BR-25 | the service description belongs in the XML, not only in an attached PDF |
Fields that become mandatory under a condition
| If … | then mandatory | Rule |
|---|---|---|
| Payment means 30 or 58 (credit transfer) | BG-17 with IBAN or account number (BT-84); with 58 a valid IBAN | BR-DE-23-a, BR-61, BR-DE-19 |
| Payment means 59 (direct debit) | BG-19 with creditor ID (BT-90) and debited account (BT-91) | BR-DE-25-a, BR-DE-30, BR-DE-31 |
| Payment means 48, 54 or 55 (card) | BG-18 with truncated card number | BR-DE-24-a |
| Invoice type 384 (correction) | Reference to the original invoice (BG-3, BT-25) | BR-DE-26, BR-55 |
| Deliver-to address (BG-15) given | City, postal code, country code (BT-77, BT-78, BT-80) | BR-DE-10, BR-DE-11, BR-57 |
| Payee is not the seller | Payee name (BT-59) | BR-17 |
| Tax representative (BG-11) given | Name, address with country code, VAT ID (BT-62, BG-12, BT-69, BT-63) | BR-18, BR-19, BR-20, BR-56 |
| Document-level allowance (BG-20) | Amount, VAT category, reason as text or code | BR-31, BR-32, BR-33 |
| Document-level charge (BG-21) | Amount, VAT category, reason as text or code | BR-36, BR-37, BR-38 |
| Attachment (BG-24) | Identifier of the attachment (BT-122); unique file names | BR-52, BR-DE-22 |
| Skonto (early-payment discount) agreed | the Skonto line in BT-20 exactly as specified | BR-DE-18 (guide: Skonto) |
What the validation does not enforce
A passed validation means: the invoice is technically complete. It does not mean that all mandatory tax particulars are in it. Two examples that are often overlooked:
- Delivery or service date. The German VAT Act (UStG) requires it (§ 14 (4) UStG). XRechnung reports its absence only as information (BR-DE-TMP-32); the invoice stays valid. You can state it as delivery date (BT-72), as invoicing period of the invoice (BG-14) or per line (BG-26).
- Street and house number. No rule requires BT-35 (seller) or BT-50 (buyer). For tax purposes, however, the complete address belongs on the invoice.
Which particulars your invoice needs for tax purposes, clarify with your tax adviser. Which mandatory particular belongs in which field is described by the mapping table of KoSIT and FeRD, which the BMF (German Federal Ministry of Finance) recommends in its letter of 15.10.2026 (guide: e-invoicing from 2027).
Checked ourselves
We took the valid sample invoice (XRechnung 3.0, UBL), removed one field at a time and validated with the same rules the validator on this website uses (KoSIT XRechnung 3.0.2). Result on 26.10.2026:
| Removed | Reported |
|---|---|
| Invoice number (BT-1) | Schema error, BR-02 |
| Invoice date (BT-2) | Schema error, BR-03 |
| Buyer reference (BT-10) | BR-DE-15 |
| Electronic address of seller (BT-34) | PEPPOL-EN16931-R020 |
| Electronic address of buyer (BT-49) | PEPPOL-EN16931-R010 |
| Telephone (BT-42) | BR-DE-6, BR-DE-27 |
| E-mail (BT-43) | BR-DE-7, BR-DE-28 |
| Postal code of seller (BT-38) | BR-DE-4 |
| Payment instructions (BG-16) | BR-DE-1 |
| VAT ID of seller (BT-31) | BR-S-02, BR-DE-16 |
Specification identifier changed to xrechnung_2.0 | no rule, but “no matching validation configuration”: the invoice does not count as validated |
The last case shows a trap: an outdated identifier in BT-24 produces no error message about a field, but prevents the XRechnung validation altogether. In the validation report, therefore, look at the detected scenario.
How to check your invoice
- Open the invoice in the free validator. It runs in your browser; the file is not uploaded. For a new invoice: Create an XRechnung asks for all mandatory fields.
- Every message names the field with its BT number. For the frequent codes there is an explanation with the path in UBL and CII.
- Add missing fields in the template or the master data of the invoicing software, not by hand in the XML.
If your own software or an automation creates invoices, you can build in the same check before sending via the API; for each message the response gives the rule code, the level, a text with the field names and the location in the XML.
Technical notes on the data format, not tax or legal advice. Whether VAT rate, supply and amounts are correct in substance is a question for your tax adviser. eRechio is not an offering of KoSIT.