BR-DE-2fatal

How to fix BR-DE-2

Die Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden.

XRechnung rule from the KoSIT XRechnung 3.0 schematron (German CIUS of EN 16931). It applies only to invoices whose specification identifier (BT-24) is XRechnung. Such files are checked against EN 16931 and the KoSIT XRechnung rules instead of the full Peppol BIS rule set. Check your file with the XRechnung validator.

What this rule checks

XRechnung requires the SELLER CONTACT group (BG-6), which is optional in EN 16931. The contact must be complete: a contact point (BT-41, BR-DE-5), a telephone number (BT-42, BR-DE-6) and an email address (BT-43, BR-DE-7). In UBL it is cac:Contact under cac:AccountingSupplierParty/cac:Party; in CII it is ram:DefinedTradeContact under ram:SellerTradeParty.

Referenced business terms

This rule references the following EN 16931 business term. Click through for the full definition, the UBL XPath and the cardinality.

BG-6

How to fix it

Add cac:Contact under cac:AccountingSupplierParty → cac:Party with cbc:Name, cbc:Telephone and cbc:ElectronicMail. In CII, add ram:DefinedTradeContact under ram:ApplicableHeaderTradeAgreement → ram:SellerTradeParty with ram:PersonName, ram:TelephoneUniversalCommunication/ram:CompleteNumber and ram:EmailURIUniversalCommunication/ram:URIID.

Common causes

The seller contact block is not generated because it is optional in Peppol BIS and EN 16931.
The contact was added to the buyer (cac:AccountingCustomerParty) instead of the seller.
cac:Contact is present but only has a name, so BR-DE-6 and BR-DE-7 fail next.
In CII, ram:DefinedTradeContact was placed under ram:BuyerTradeParty.

Example: before (broken)

<Invoice xmlns="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">
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cac:PartyName><cbc:Name>Muster GmbH</cbc:Name></cac:PartyName>
      <!-- ... address, tax scheme, legal entity ... -->
      <!-- cac:Contact is missing -->
    </cac:Party>
  </cac:AccountingSupplierParty>
</Invoice>

Example: after (fixed)

<Invoice xmlns="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">
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cac:PartyName><cbc:Name>Muster GmbH</cbc:Name></cac:PartyName>
      <!-- ... address, tax scheme, legal entity ... -->
      <cac:Contact>
        <cbc:Name>Buchhaltung, Erika Mustermann</cbc:Name>
        <cbc:Telephone>+49 30 1234567</cbc:Telephone>
        <cbc:ElectronicMail>rechnung@muster-gmbh.de</cbc:ElectronicMail>
      </cac:Contact>
    </cac:Party>
  </cac:AccountingSupplierParty>
</Invoice>

Validate your invoice

Upload your corrected invoice to check it passes BR-DE-2 and all other EN 16931 and XRechnung (BR-DE) rules. Free, instant, no signup.

Open XRechnung validator All validation rules