InvoiceSpec / Rules Registry / xrechnung-3-0 / BR-DE-15
fatal ASSERTION · BR-DE-15 XRechnung 3.0 (UBL-2.1) Jurisdiction: DE

BR-DE-15: Buyer reference / Leitweg-ID (BT-10) is strictly mandatory in XRechnung

Official XRechnung 3.0 Spec ↗
01. Technical Specification & XPath Evaluation Context

While EN 16931 allows either a Buyer Reference (BT-10) OR a Project/Order Reference (BT-13), German XRechnung 3.0 rule BR-DE-15 mandates that BT-10 (cbc:BuyerReference) is ALWAYS populated (containing the buyer Leitweg-ID for B2G or cost-center reference for B2B).

Evaluated XPath Location:
/ubl:Invoice/cbc:BuyerReference
Deterministic Remediation Steps

Ensure <cbc:BuyerReference> (BT-10) is always populated in XRechnung 3.0 documents. For B2B invoices where no Leitweg-ID exists, populate the buyer cost center, department code, or PO contact identifier.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (BR-DE-15) FAIL
1 <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
2 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
3 xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2">
4 <cbc:ID>XR-2026-882</cbc:ID>
5 <cbc:IssueDate>2026-11-02</cbc:IssueDate>
6 <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
7 - <!-- ERROR [BR-DE-15]: OrderReference is provided, but XRechnung requires cbc:BuyerReference (BT-10) -->
8 <cac:OrderReference><cbc:ID>PO-44910</cbc:ID></cac:OrderReference>
9 </Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID)
PASS
1 <Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
2 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
3 xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2">
4 <cbc:ID>XR-2026-882</cbc:ID>
5 <cbc:IssueDate>2026-11-02</cbc:IssueDate>
6 <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
7 + <cbc:BuyerReference>991-12849-74</cbc:BuyerReference>
8 <cac:OrderReference><cbc:ID>PO-44910</cbc:ID></cac:OrderReference>
9 </Invoice>
03. Interactive XRechnung 3.0 Validation & Auto-Fix Workbench
1 CREDITS
invoice.xmlUBL-2.1
DETECTED SOURCECustom ERP / Billing Engine
BT-131 LINE SUM0.00 EUR
BT-106 HEADER0.00 EUR
SCHEMATRON: 2 FATAL· 1ms
XRechnung 3.0 (UBL)
BR-01An Invoice shall have a valid EN 16931 Specification identifier (BT-24)
Spec & Diff
xpath: /ubl:Invoice/cbc:CustomizationID

Missing <cbc:CustomizationID> or value does not declare EN 16931 CIUS compliance.

fix: Insert <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>.

BR-DE-15Buyer reference / Leitweg-ID (BT-10) is missing
Spec & Diff
xpath: /ubl:Invoice/cbc:BuyerReference

No <cbc:BuyerReference> (BT-10) found. Mandatory in XRechnung 3.0 (BR-DE-15) and required in Peppol BIS 3.0 (PEPPOL-EN16931-R003) when OrderReference is absent.

fix: Insert <cbc:BuyerReference>991-12849-74</cbc:BuyerReference> in the document header.

Automate Custom ERP / Billing Engine → XRechnung 3.0 (UBL) AP Delivery

Deploy certified Peppol Access Point & ZUGFeRD ERP connector

04. Adjacent XRechnung 3.0 Assertions Browse All Rules →