BR-DE-28: what it means and how to fix it
The seller's e-mail address should have exactly one @ with at least two characters on each side.
| Rule | BR-DE-28 |
|---|---|
| Standard | XRechnung 3.0 (the German CIUS of EN 16931, published by KoSIT) |
| Severity | Warning |
| Concerns | BT-43: Seller contact e-mail address |
How to fix it
Correct the e-mail address.
Where the field is in the XML
| Term | CII (XRechnung-CII, ZUGFeRD, Factur-X) | UBL (XRechnung-UBL, Peppol) |
|---|---|---|
| BT-43 Seller contact e-mail address | ram:SellerTradeParty/ram:DefinedTradeContact/ram:EmailURIUniversalCommunication/ram:URIID | cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail |
From your code
curl -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/xml" \
--data-binary @invoice.xml "https://agent-data-tools.revmesh2074.workers.dev/einvoice/validate"The answer lists every broken rule with its number, the field, a message with the figures from your file and the fix. E-invoice API: validate, convert to JSON, and create XRechnung or ZUGFeRD XML from JSON.
Questions
What does BR-DE-28 mean?
The seller's e-mail address should have exactly one @ with at least two characters on each side. It is a rule of XRechnung 3.0 (the German CIUS of EN 16931, published by KoSIT).
How do I fix BR-DE-28?
Correct the e-mail address.
Is BR-DE-28 an error or a warning?
A warning: the invoice is still conformant, but the value should be corrected.
Does BR-DE-28 apply to ZUGFeRD and Factur-X too?
Only when the file declares the XRechnung specification identifier (the ZUGFeRD profile "XRECHNUNG" does). Files in the plain EN 16931 profile are checked against the European rules, not the German additions.
Related rules
- BR-DE-7: The seller's contact e-mail address must be given.
Rule numbers are those of XRechnung 3.0 (KoSIT); the explanation is ours. Not tax or legal advice.