Skip to main content

BR-DE-28 Seller contact email should contain exactly one at sign

BR-DE-28 of the German XRechnung rules checks the seller contact email address (BT-43) against a pattern, after leading and trailing spaces are removed: exactly one "@" with at least one character before it and no space anywhere, and after the "@" a domain with at least one dot, in which no dot stands at the start, at the end or next to another dot. The part before the "@" is not checked further, and the rule does not check whether the mailbox exists.

Problem Description

WARNING

German XRechnung rule (KoSIT, BR-DE) · XRechnung 3.0

Interactive pipeline

Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.

Try:

BR-DE-28 XRechnung rule (Germany)

Reported in stage 3: National rules (CIUS).

Level warning: on its own, the invoice is still accepted.

Stage 3 · What it checks

  • The specification identifier in BT-24 selects the rule set, for example XRechnung 3.0 or Peppol BIS Billing 3.0.
  • XRechnung adds the German BR-DE rules: buyer reference (BT-10), seller contact, payment instructions.
  • Peppol adds PEPPOL-EN16931 and country rules. XRechnung applies some PEPPOL-EN16931 rules too.

Example codes

Typical fix

Fill the fields the rule set requires in your master data, such as the Leitweg-ID in BT-10 or the seller contact.

A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. BR-DE-28: XRechnung rule (Germany), reported in the stage “National rules (CIUS)”. Rule sets: KoSIT validator 1.6.3 with the XRechnung configuration of 31 Aug 2026 (EN 16931 artefacts 1.3.16), Peppol BIS Billing 3.0.21.

Solution

In your invoicing or master data settings, verify that the contact email address is formatted correctly as a single valid address (e.g. "buchhaltung@unternehmen.de"). In UBL 2.1 syntax, populate <cbc:ElectronicMail> within <cac:AccountingSupplierParty><cac:Party><cac:Contact>. In UN/CEFACT CII syntax, populate <ram:URIID> within <ram:EmailURIUniversalCommunication> under <ram:SellerTradeParty><ram:DefinedTradeContact>. If multiple recipients need notification, configure email distribution lists or mail forwarding on your mail server instead of putting multiple addresses in BT-43.

Quick actions

Context and Significance

BR-DE-28 is a warning in the KoSIT configuration for XRechnung 3.0.2, so the validator does not reject the file for it alone. A missing email address is a different rule: BR-DE-7 is an error. Several addresses in one field, a missing "@" or a domain without a dot trigger BR-DE-28.

Valid Examples

  • BT-43 = "rechnungswesen@lieferant.de"
  • BT-43 = "billing.team@company.eu"

Invalid Examples

  • BT-43 = "rechnung@lieferant@de" (Malformed address containing multiple "@" characters)
  • BT-43 = "rechnung@lieferant, vertrieb@lieferant.de" (Multiple addresses separated by comma)
  • BT-43 = "rechnung.lieferant.de" (Address missing the "@" delimiter entirely)

Code Examples

Valid XML
<cac:Contact>
  <cbc:Name>Buchhaltung</cbc:Name>
  <cbc:Telephone>+49 30 1234567</cbc:Telephone>
  <cbc:ElectronicMail>buchhaltung@unternehmen.de</cbc:ElectronicMail>
</cac:Contact>
Invalid XML
<cac:Contact>
  <cbc:Name>Buchhaltung</cbc:Name>
  <cbc:Telephone>+49 30 1234567</cbc:Telephone>
  <cbc:ElectronicMail>rechnung@firma.de, vertrieb@firma.de</cbc:ElectronicMail>
</cac:Contact>

Affected Fields

Validation Tools