Attestwire › Rule reference › BR-DE-30

BR-DE-30 An XRechnung direct debit requires the SEPA creditor identifier

noun · XRechnung · fatal · BG-19 / BT-90

For a sample invoice, the library reports: The invoice carries a DIRECT DEBIT group (BG-19), so the bank assigned creditor identifier (BT-90) must be present.

Diese Regel auf Deutsch: BR-DE-30 — auf Deutsch erklärt.

Business term
BG-19 / BT-90
Severity
fatal

The fix

Set payment.directDebit.creditorIdentifier to your SEPA creditor identifier. Your bank issues it once, on application; it is not derived from your IBAN or your VAT number.

A passing value

the shape this field expects
"directDebit": { "creditorIdentifier": "DE98ZZZ09999999999" }

What the library returns

The full error returned by @attestwire/en16931. It includes the rule ID, affected field and suggested correction. Developers can use this object in their application:

TeachingError
{
  "rule": "BR-DE-30",
  "field": [
    "BG-19",
    "BT-90"
  ],
  "severity": "fatal",
  "message": "The invoice carries a DIRECT DEBIT group (BG-19), so the bank assigned creditor identifier (BT-90) must be present. This is your SEPA Gläubiger-Identifikationsnummer — in Germany a 18-character identifier issued by the Bundesbank, of the form DE98ZZZ09999999999 — and it is what the payer's bank uses to check the collection you are about to raise against the mandate they hold. A mandate reference with no creditor identifier names a permission without naming who holds it. Note where it goes in the XML: EN 16931's UBL binding puts BT-90 on the seller party as a cac:PartyIdentification with schemeID=\"SEPA\", not inside the payment group, which is why a document can look complete and still fail this rule.",
  "fix": "Set payment.directDebit.creditorIdentifier to your SEPA creditor identifier. Your bank issues it once, on application; it is not derived from your IBAN or your VAT number.",
  "example": "\"directDebit\": { \"creditorIdentifier\": \"DE98ZZZ09999999999\" }",
  "xpath": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID",
  "docsUrl": "https://attestwire.com/rules/BR-DE-30"
}

xpath is always a UBL path. On a CII invoice, look for the matching CII field instead.