BR-DE-7 XRechnung requires the element "Seller contact email address" (BT-43)
XRechnung requires the element "Seller contact email address" (BT-43). The seller contact group is present but incomplete — BR-DE-5, BR-DE-6 and BR-DE-7 each make one part of it mandatory, so supplying two of the three still fails.
This rule is implemented and its error payload below is real, but the long-form write-up — normative text, worked example, divergence note — is not written yet. Everything the library knows about this rule is on this page. Ask and we will prioritise it.
- Business term
BT-43- Severity
fatal
What the library returns
The exact object in result.errors when this rule fires.
Generated by running @attestwire/en16931, not transcribed:
{
"rule": "BR-DE-7",
"field": "BT-43",
"severity": "fatal",
"message": "XRechnung requires the element \"Seller contact email address\" (BT-43). The seller contact group is present but incomplete — BR-DE-5, BR-DE-6 and BR-DE-7 each make one part of it mandatory, so supplying two of the three still fails.",
"fix": "Set seller.contact.email to a monitored mailbox — this is where the authority sends invoice queries.",
"example": "\"contact\": { \"email\": \"rechnungen@example.de\" }",
"xpath": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail",
"docsUrl": "https://attestwire.com/rules/BR-DE-7"
}
xpath locates the element in the generated UBL document,
which is where a KoSIT or Peppol validator will report the same problem.
A passing value
"contact": { "email": "rechnungen@example.de" }The fix
Set seller.contact.email to a monitored mailbox — this is where the authority sends invoice queries.