BR-DE-1
XRechnung requires payment instructions, and the invoice has none.
Why it happens
The invoice says what is owed but not how to pay it. EN 16931 treats BG-16 as optional; XRechnung does not.
How to fix it
Add cac:PaymentMeans (UBL) or ram:SpecifiedTradeSettlementPaymentMeans (CII) with at least a payment means code (BT-81). For a bank transfer use code 30 or 58 and include the credit transfer group with the account identifier.
The official rule
XRechnung, official German wordingEine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten.
Our English rendering: An invoice must contain PAYMENT INSTRUCTIONS (BG-16).
Technical detail — where the rule is evaluated and the exact test
| Syntax | Context and assertion |
|---|---|
| UBL | /ubl:Invoice | /cn:CreditNote |
cac:PaymentMeans | |
| CII | /rsm:CrossIndustryInvoice |
rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans |
Check your own invoice
Paste or drop your UBL or CII file into the free validator. It runs the official EN 16931 ruleset plus the German XRechnung layer and lists every rule that fires, BR-DE-1 included — no signup, no limit.
Validate an e-invoice freeFixing the data at source instead? The CSV converter builds a compliant invoice from a spreadsheet export.