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-02
fatal SCHEMATRON RULE · BR-DE-02 Syntax: UBL-2.1 Jurisdiction: DE (Mandate: 2025-01-01)

BR-DE-02: Die Gruppe "SELLER CONTACT" (BG-6) muss in XRechnung übermittelt werden.

Official XRechnung 3.0 Spec ↗

1. Technical Specification & XPath Evaluation Context

BR-DE-02 is a German XRechnung 3.0 CIUS rule (fatal severity) that mandates the presence of the SELLER CONTACT group (BG-6) within the AccountingSupplierParty/Party element. The Schematron context is /ubl:Invoice/cac:AccountingSupplierParty/cac:Party, and the test requires that the Contact element (cac:Contact) contains all three child elements: cbc:Name (BT-41), cbc:Telephone (BT-42), and cbc:ElectronicMail (BT-43). The rule enforces that the seller's contact information is fully provided, as required by the German CIUS for EN 16931. The XPath expression exists(cac:Contact/cbc:Name) and exists(cac:Contact/cbc:Telephone) and exists(cac:Contact/cbc:ElectronicMail) evaluates to true only if all three elements are present. If any is missing, the assertion fails, triggering the fatal error. This rule is specific to XRechnung and is not part of the base EN 16931 or Peppol BIS, but is a CIUS requirement for German public sector invoices.

Canonical XPath Selector:
/ubl:Invoice/cac:AccountingSupplierParty/cac:Party
Deterministic Engineering Fix

To resolve BR-DE-02, ensure that the seller's contact information (BG-6) is fully provided in the UBL invoice. Specifically: 1. Locate the cac:AccountingSupplierParty/cac:Party element. 2. Within it, ensure a cac:Contact element exists. 3. Inside cac:Contact, add the following child elements if missing: - cbc:Name (BT-41): The contact person's name. - cbc:Telephone (BT-42): A telephone number for the contact. - cbc:ElectronicMail (BT-43): An email address for the contact. 4. Verify that all three elements are present and contain non-empty values. 5. Re-validate the invoice against the XRechnung 3.0 Schematron rules to confirm the error is resolved.

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

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

✗ REJECTED PAYLOAD (TRIGGERS BR-DE-02) Schematron: FATAL
<ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <!-- ... other invoice elements ... -->
  <cac:AccountingSupplierParty>
    <cac:Party>
      <!-- ... PartyName, PostalAddress, PartyTaxScheme, PartyLegalEntity ... -->
      <cac:Contact>
        <cbc:Name>John Doe</cbc:Name>
        <!-- Missing cbc:Telephone and cbc:ElectronicMail -->
      </cac:Contact>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <!-- ... rest of invoice ... -->
</ubl:Invoice>
✓ COMPLIANT UBL-2.1 PAYLOAD (PASSES BR-DE-02) EN 16931 VALID
<ubl:Invoice xmlns:ubl="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <!-- ... other invoice elements ... -->
  <cac:AccountingSupplierParty>
    <cac:Party>
      <!-- ... PartyName, PostalAddress, PartyTaxScheme, PartyLegalEntity ... -->
      <cac:Contact>
        <cbc:Name>John Doe</cbc:Name>
        <cbc:Telephone>+49 123 456789</cbc:Telephone>
        <cbc:ElectronicMail>john.doe@example.com</cbc:ElectronicMail>
      </cac:Contact>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <!-- ... rest of invoice ... -->
</ubl:Invoice>

3. Interactive XRechnung 3.0 Validator & Auto-Remediation Sandbox

Pre-loaded with the failing BR-DE-02 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
3 FATAL SCHEMATRON ERRORS
Invoice ID: UNSPECIFIED-ID · 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>.

PEPPOL-EN16931-R020Seller electronic address (BT-34) MUST be provided with a valid EAS @schemeID
Fix Guide
XPath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

Missing <cbc:EndpointID schemeID="..."> inside <cac:AccountingSupplierParty>/<cac:Party>.

Remediation: Add <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID> as the first child of Seller <cac:Party>.

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 →