# BR-DE-2: Seller contact (BG-6) required

Source: https://veriport.io/einvoice-rules/br-de-2 (published 2026-11-17)

An XRechnung must contain the seller contact group, BG-6 (`cac:AccountingSupplierParty/cac:Party/cac:Contact` in UBL, `ram:SellerTradeParty/ram:DefinedTradeContact` in CII), so that the public buyer can reach a person about the invoice. Below: the message, the cause and the fix, and an invoice our validator checked, failing and fixed.

- **Specification:** [XRechnung 3.0 rules](/einvoice-rules/xrechnung), XRechnung 3.0.2 schematron 2.6.0
- **Severity:** error
- **Business terms:** BG-6
- **Reported by** `POST /einvoice/validate` and our free validators, with a link to this page

## The message validators print

BR-DE-2 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL and CII. It is an error (fatal): a validator rejects the invoice.

```text
[BR-DE-2] Die Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden.
```

## What it checks

An XRechnung must contain the seller contact group, BG-6 (`cac:AccountingSupplierParty/cac:Party/cac:Contact` in UBL, `ram:SellerTradeParty/ram:DefinedTradeContact` in CII), so that the public buyer can reach a person about the invoice. BR-DE-5, 6 and 7 then require its name, telephone and e-mail.

## Why invoices fail it

The seller record has an e-mail address on the company but no contact person, and no contact group is written.

## How to fix it

Write a seller contact with a name or department (BT-41), a telephone number (BT-42) and an e-mail address (BT-43).

## A failing invoice and its fix, checked

We start from our sample invoice (two lines at 19 %, Berlin to Stuttgart), written by our own generator as XRechnung 3.0 in UBL. The change below (`-` the failing version, `+` the fixed one) makes the rule fail. Both versions went through our validator on 2026-11-17 (the XML schema and the official rule files, as `POST /einvoice/validate` runs them): the fixed one is valid, the failing one reports BR-DE-2.

| Rule | Severity | Where | Message |
|---|---|---|---|
| **BR-DE-2** | error | `/ubl:Invoice/cac:AccountingSupplierParty` | Die Gruppe "SELLER CONTACT" (BG-6) muss übermittelt werden. |

```diff
  …
          <cbc:RegistrationName>Lena Hartmann — Webdesign</cbc:RegistrationName>
        </cac:PartyLegalEntity>
+       <cac:Contact>
+         <cbc:Name>Lena Hartmann</cbc:Name>
+         <cbc:Telephone>+49 30 1234567</cbc:Telephone>
+         <cbc:ElectronicMail>rechnung@hartmann-webdesign.example</cbc:ElectronicMail>
+       </cac:Contact>
      </cac:Party>
    </cac:AccountingSupplierParty>
  …
```

## The rule as published

Where the rule applies (`context`) and what must hold (`test`), unmodified from XRechnung 3.0.2 schematron 2.6.0. An `assert` fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

```xpath
context: /ubl:Invoice/cac:AccountingSupplierParty | /cn:CreditNote/cac:AccountingSupplierParty
test:    cac:Party/cac:Contact
```

```xpath
context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty
test:    ram:DefinedTradeContact
```

## Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator ([Peppol BIS](/tools/peppol-validator), [XRechnung](/tools/xrechnung-pruefen), [Factur-X](/tools/valider-factur-x)): each runs the same rule files and links every finding to its rule page. From your own code, `POST /einvoice/validate` ([reference](/docs/einvoice)) returns the same check as JSON, each finding with an `explanation` field pointing here (5 calls a check, anonymous within the daily allowance).

## Read next

- [BR-DE-1: Payment instructions (BG-16) required](https://veriport.io/einvoice-rules/br-de-1)
- [BR-DE-3: Seller city (BT-37) required](https://veriport.io/einvoice-rules/br-de-3)
- [BR-DE-4: Seller post code (BT-38) required](https://veriport.io/einvoice-rules/br-de-4)
- [All XRechnung 3.0 rules](https://veriport.io/einvoice-rules/xrechnung)
- [All e-invoice rules, search](https://veriport.io/einvoice-rules)
- [Check an e-invoice free (XRechnung prüfen)](https://veriport.io/tools/xrechnung-pruefen)
- [Create a valid e-invoice free (German form)](https://veriport.io/tools/e-rechnung-erstellen)

## Sources

- XRechnung — the German CIUS of EN 16931 (standard, versions and bundles; version 3.0.2 in force) — https://xeinkauf.de/xrechnung/ (2026-10-28)
- Validator configuration XRechnung v2026-08-31 (XRechnung 3.0.2, CEN schematron 1.3.16, xrechnung-schematron 2.6.0) — https://github.com/itplr-kosit/validator-configuration-xrechnung/releases/tag/v2026-08-31 (2026-10-28)
- XRechnung schematron (xrechnung-schematron) and the XRechnung validator configuration: licence, Apache License 2.0 (LICENSE files; NOTICE of the configuration: « Copyright 2020 Koordinierungsstelle für IT-Standards ») — https://github.com/itplr-kosit/xrechnung-schematron/blob/master/LICENSE (2026-11-17)
