BR-DE-02: Die Gruppe "SELLER CONTACT" (BG-6) muss in XRechnung übermittelt werden.
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.
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.
<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> <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.
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>.
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>.
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.
Related EN 16931 & XRechnung 3.0 Schematron Rules
Batch Validate 1,000+ XML Files →French Seller SIREN/SIRET identifier (BT-30) with schemeID 0002 is mandatory for Factur-X
Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110).
Buyer reference / Leitweg-ID (BT-10) is strictly mandatory in XRechnung
Invoice total amount without VAT (BT-109) = Σ Invoice line net amount (BT-131) - Sum of allowances on document level (BT-107) + Sum of charges on document level (BT-108).
An Invoice shall have an Invoice number (BT-1).