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.

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

BTFieldRuleNote
BT-1Invoice numberBR-02unique per invoice
BT-2Invoice dateBR-03format YYYY-MM-DD in UBL, YYYYMMDD in CII
BT-3Invoice type codeBR-04, BR-DE-17only certain codes, e.g. 380 invoice, 381 credit note, 384 correction (guide: invoice type code)
BT-5CurrencyBR-05EUR, not “€”
BT-10Buyer referenceBR-DE-15for authorities the Leitweg-ID (German public-sector routing ID, guide: Leitweg-ID), otherwise a reference of the buyer
BT-24Specification identifierBR-01, BR-DE-21for XRechnung 3.0: urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0

Seller

BTFieldRuleNote
BT-27NameBR-06
BG-5AddressBR-08the group itself
BT-37CityBR-DE-3
BT-38Postal codeBR-DE-4
BT-40Country codeBR-09DE, two letters
BT-34Electronic addressPEPPOL-EN16931-R020, BR-62with scheme, e.g. schemeID="EM" for an e-mail address
BG-6ContactBR-DE-2the group itself
BT-41Contact personBR-DE-5name or department
BT-42TelephoneBR-DE-6, BR-DE-27at least three digits
BT-43E-mailBR-DE-7, BR-DE-28exactly one @
BT-29, BT-30 or BT-31Identifier, registration number or VAT IDBR-CO-26at least one of them
BT-31 or BT-32VAT ID (USt-IdNr.) or tax number (Steuernummer)BR-DE-16for VAT category S, Z, E, AE, K, G, L or M (so almost always); alternatively a tax representative (BG-11)

Buyer

BTFieldRuleNote
BT-44NameBR-07
BG-8AddressBR-10the group itself
BT-52CityBR-DE-8
BT-53Postal codeBR-DE-9
BT-55Country codeBR-11
BT-49Electronic addressPEPPOL-EN16931-R010, BR-63for authorities often the Leitweg-ID with schemeID="0204"; if in doubt, ask the recipient

Payment

BTFieldRuleNote
BG-16Payment instructionsBR-DE-1even if it is already paid
BT-81Payment means type codeBR-49e.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

BTFieldRuleNote
BT-106Sum of line net amountsBR-12
BT-109Total amount without VATBR-13
BT-112Total amount with VATBR-14
BT-115Amount due for paymentBR-15
BG-23VAT breakdownBR-CO-18at least one, one per VAT category and rate
BT-116VAT category taxable amountBR-45
BT-117VAT category tax amountBR-46also 0.00
BT-118VAT category codeBR-47(guide: VAT categories)
BT-119VAT category rateBR-DE-14always 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:

BTFieldRuleNote
BT-126Line numberBR-21
BT-129QuantityBR-22
BT-130Unit of measureBR-23as a code, e.g. H87 piece, HUR hour, C62 unit
BT-131Line net amountBR-24
BT-146Net priceBR-26
BT-151Line VAT category codeBR-CO-04
BT-153Item nameBR-25the service description belongs in the XML, not only in an attached PDF

Fields that become mandatory under a condition

If …then mandatoryRule
Payment means 30 or 58 (credit transfer)BG-17 with IBAN or account number (BT-84); with 58 a valid IBANBR-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 numberBR-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) givenCity, postal code, country code (BT-77, BT-78, BT-80)BR-DE-10, BR-DE-11, BR-57
Payee is not the sellerPayee name (BT-59)BR-17
Tax representative (BG-11) givenName, 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 codeBR-31, BR-32, BR-33
Document-level charge (BG-21)Amount, VAT category, reason as text or codeBR-36, BR-37, BR-38
Attachment (BG-24)Identifier of the attachment (BT-122); unique file namesBR-52, BR-DE-22
Skonto (early-payment discount) agreedthe Skonto line in BT-20 exactly as specifiedBR-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:

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:

RemovedReported
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.0no 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

  1. 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.
  2. Every message names the field with its BT number. For the frequent codes there is an explanation with the path in UBL and CII.
  3. 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.