Fehlercodes · XRechnung · Deutschland

BR-DE-17Im Rechnungssystem

Seller contact information (name, phone, email) required in XRechnung

So lautet die Ablehnung wörtlich: „[BR-DE-17] BR-DE-17 fires when an XRechnung invoice's seller party (cac:AccountingSupplierParty/cac:Party) does not carry a complete cac:Contact block containing the seller contact point name (BT-41, cbc:Name), telephone (BT-42, cbc:Telephone) and email (BT-43, cbc:ElectronicMail). XRechnung makes all three contact fields mandatory; Peppol BIS Billing 3.0 makes them optional, so an invoice that validates against Peppol can still fail KoSIT XRechnung validation with BR-DE-17.“

Common failure modes: (1) cac:Contact is missing entirely under the seller party — the source system never collects a contact for invoicing purposes. (2) cac:Contact exists but one of cbc:Name, cbc:Telephone, cbc:ElectronicMail is missing. The KoSIT schematron requires all three. (3) cbc:ElectronicMail contains an invalid value like 'noreply' (no @ sign) or whitespace. (4) cbc:Telephone is a free-text field with characters the validator does not accept (some validators enforce E.164-ish formats). (5) The invoice declares the Peppol BIS customisation but is sent to a German public-sector recipient that expects XRechnung — the KoSIT layer adds BR-DE-17 on top of EN 16931 and the rule fires. (6) Contact details are written under cac:PartyContact (the deprecated UBL element) instead of cac:Contact.

Was Sie bereithaltenNichts. Die Datei muss im Rechnungssystem neu erzeugt werden; wir prüfen sie danach erneut.
Was wir tunStep 1: Locate cac:AccountingSupplierParty/cac:Party in the Invoice or CreditNote. Step 2: Make sure a cac:Contact child exists. If not, create one — its position is after cac:PartyTaxScheme and before cac:PartyLegalEntity in UBL 2.1 canonical order. Step 3: Populate the three required children: • `<cbc:Name>Accounts Receivable</cbc:Name>` — a department, role or person name (BT-41). • `<cbc:Telephone>+49 30 1234567</cbc:Telephone>` — a usable phone number, with country code recommended (BT-42). • `<cbc:ElectronicMail>invoicing@example.de</cbc:ElectronicMail>` — a monitored email address (BT-43). Step 4: Validate each value: • Name must be a non-empty string with no leading/trailing whitespace. • Telephone should be at least 5 characters; many validators accept any digits and `+ - ( ) space` but reject letters. • Email must contain exactly one `@`, a non-empty local part and a domain with at least one dot. Use a deliverable address — the buyer's accounts payable team uses it to query the invoice. Step 5: Do not put contact data under cac:PartyContact (deprecated). The KoSIT validator only checks cac:Contact. Step 6: Re-validate against the KoSIT XRechnung 2.x or 3.x ruleset. BR-DE-17 should clear, and BR-DE-18 (cbc:ElectronicMail required) and BR-DE-19 (cbc:Telephone required) — its sibling rules — should also pass.
Wenn Sie es selbst im Rechnungssystem eintragen
Vorher
<cac:AccountingSupplierParty>
  <cac:Party>
    <cac:PartyName><cbc:Name>Muster GmbH</cbc:Name></cac:PartyName>
    <cac:PostalAddress>...</cac:PostalAddress>
    <cac:PartyTaxScheme>
      <cbc:CompanyID>DE123456789</cbc:CompanyID>
      <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
    </cac:PartyTaxScheme>
    <cac:PartyLegalEntity><cbc:RegistrationName>Muster GmbH</cbc:RegistrationName></cac:PartyLegalEntity>
    <!-- cac:Contact missing -->
  </cac:Party>
</cac:AccountingSupplierParty>
Nachher
<cac:AccountingSupplierParty>
  <cac:Party>
    <cac:PartyName><cbc:Name>Muster GmbH</cbc:Name></cac:PartyName>
    <cac:PostalAddress>...</cac:PostalAddress>
    <cac:PartyTaxScheme>
      <cbc:CompanyID>DE123456789</cbc:CompanyID>
      <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
    </cac:PartyTaxScheme>
    <cac:PartyLegalEntity><cbc:RegistrationName>Muster GmbH</cbc:RegistrationName></cac:PartyLegalEntity>
    <cac:Contact>
      <cbc:Name>Accounts Receivable</cbc:Name>
      <cbc:Telephone>+49 30 1234567</cbc:Telephone>
      <cbc:ElectronicMail>invoicing@muster.de</cbc:ElectronicMail>
    </cac:Contact>
  </cac:Party>
</cac:AccountingSupplierParty>

Die Reihenfolge ist Teil der Regel: steht das Element an der falschen Stelle, lehnt der Validator mit BR-DE-17 ab.

So sieht der Befund ausBeispiel
BefundAufbau fehlerhaft · BR-DE-17
Stelle//cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:Telephone
Von IhnenNeu exportierte Datei
DanachNeu exportieren
NachweisSHA-256 und /verify-Link nach der Prüfung
Tritt oft zusammen auf
BR-DE-18Invalid Skonto (Cash Discount) Format