Top Up Credits →
InvoiceSpec / Rules Registry / xrechnung-3-0 / BR-DE-02
fatal ASSERTION · BR-DE-02 XRechnung 3.0 (UBL-2.1) Jurisdiction: DE

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

Official XRechnung 3.0 Spec ↗
01. 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.

Evaluated XPath Location:
/ubl:Invoice/cac:AccountingSupplierParty/cac:Party
Deterministic Remediation Steps

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.

02. Side-by-Side UBL-2.1 Payload Diff (Rejected vs. Compliant)
--- a/invoice-rejected.xml (BR-DE-02) FAIL
1 <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">
2 <!-- ... other invoice elements ... -->
3 <cac:AccountingSupplierParty>
4 <cac:Party>
5 <!-- ... PartyName, PostalAddress, PartyTaxScheme, PartyLegalEntity ... -->
6 <cac:Contact>
7 <cbc:Name>John Doe</cbc:Name>
8 <!-- Missing cbc:Telephone and cbc:ElectronicMail -->
9 </cac:Contact>
10 </cac:Party>
11 </cac:AccountingSupplierParty>
12 <!-- ... rest of invoice ... -->
13 </ubl:Invoice>
+++ b/invoice-compliant.xml (EN 16931 VALID)
PASS
1 <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">
2 <!-- ... other invoice elements ... -->
3 <cac:AccountingSupplierParty>
4 <cac:Party>
5 <!-- ... PartyName, PostalAddress, PartyTaxScheme, PartyLegalEntity ... -->
6 <cac:Contact>
7 <cbc:Name>John Doe</cbc:Name>
8 + <cbc:Telephone>+49 123 456789</cbc:Telephone>
9 + <cbc:ElectronicMail>[email protected]</cbc:ElectronicMail>
10 </cac:Contact>
11 </cac:Party>
12 </cac:AccountingSupplierParty>
13 <!-- ... rest of invoice ... -->
14 </ubl: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: 3 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>.

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

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

fix: 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
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 →