EN 16931 / PEPPOL 3.0.17 ENGINE LIVE DE E-Rechnung (§ 14 UStG) & FR Factur-X 2026 Ready
InvoiceSpec Hub / Errors / XRechnung 3.0 / BR-DE-15
fatal SCHEMATRON RULE · BR-DE-15 Syntax: UBL-2.1 Jurisdiction: DE (Mandate: 2025-01-01)

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

Official XRechnung 3.0 Spec ↗

1. 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).

Canonical XPath Selector:
/ubl:Invoice/cbc:BuyerReference
Deterministic Engineering Fix

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.

2. Side-by-Side Payload Diff: Failing vs. Compliant UBL-2.1 XML

Compare the rejected payload triggering BR-DE-15 against the EN 16931 compliant structure.

✗ REJECTED PAYLOAD (TRIGGERS BR-DE-15) Schematron: FATAL
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2">
  <cbc:ID>XR-2026-882</cbc:ID>
  <cbc:IssueDate>2026-11-02</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <!-- ERROR [BR-DE-15]: OrderReference is provided, but XRechnung requires cbc:BuyerReference (BT-10) -->
  <cac:OrderReference><cbc:ID>PO-44910</cbc:ID></cac:OrderReference>
</Invoice>
✓ COMPLIANT UBL-2.1 PAYLOAD (PASSES BR-DE-15) EN 16931 VALID
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2">
  <cbc:ID>XR-2026-882</cbc:ID>
  <cbc:IssueDate>2026-11-02</cbc:IssueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:BuyerReference>991-12849-74</cbc:BuyerReference>
  <cac:OrderReference><cbc:ID>PO-44910</cbc:ID></cac:OrderReference>
</Invoice>

3. Interactive XRechnung 3.0 Validator & Auto-Remediation Sandbox

Pre-loaded with the failing BR-DE-15 snippet above, or drop your own UBL / ZUGFeRD PDF/A-3 invoice to test in-browser.

100% Client-Side Privacy
invoice-payload.xmlUBL-2.1
DETECTED SOURCECustom ERP / Billing Engine
LINE SUM (BT-131)0.00 EUR
HEADER NET (BT-106)0.00 EUR
2 FATAL SCHEMATRON ERRORS
Invoice ID: XR-2026-882 · Validated in 1ms
XRechnung 3.0 (UBL)
BR-01An Invoice shall have a valid EN 16931 Specification identifier (BT-24)
Fix Guide
XPath: /ubl:Invoice/cbc:CustomizationID

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

Remediation: 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
Fix Guide
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.

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

AP
Automate XRechnung 3.0 (UBL) directly in Custom ERP / Billing Engine

Try Certified Peppol Access Point & ZUGFeRD ERP Integration — Zero XML coding

Try Certified Integration

Related EN 16931 & XRechnung 3.0 Schematron Rules

Batch Validate 1,000+ XML Files →