attestwireAttestwire › Rule reference › BR-DE-24-a
BR-DE-24-a A card payment code requires the payment card details
noun · XRechnung · fatal · BG-18
For a sample invoice, the library reports: The payment means type code (BT-81) is "48", which XRechnung treats as a card payment, so exactly one PAYMENT CARD INFORMATION group (BG-18) must be present.
Diese Regel auf Deutsch: BR-DE-24-a — auf Deutsch erklärt.
- Business term
BG-18- Severity
fatal
The fix
Set payment.card with the masked primary account number (BT-87) and, optionally, the cardholder name (BT-88). If the invoice is not settled by card, change payment.meansCode instead — "58" (SEPA credit transfer) with payment.iban is what most invoices want.
A passing value
"payment": { "meansCode": "48", "card": { "primaryAccountNumber": "4111111111", "holderName": "M Mustermann" } }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:
{
"rule": "BR-DE-24-a",
"field": "BG-18",
"severity": "fatal",
"message": "The payment means type code (BT-81) is \"48\", which XRechnung treats as a card payment, so exactly one PAYMENT CARD INFORMATION group (BG-18) must be present. BG-18 is not an invitation to put a card number on an invoice: BR-51 caps the primary account number (BT-87) at ten characters, which is the most the PCI Security Standards Council permits — the first six and the last four digits. What the group is actually for is letting the buyer reconcile this invoice against a card statement line they have already been charged for.",
"fix": "Set payment.card with the masked primary account number (BT-87) and, optionally, the cardholder name (BT-88). If the invoice is not settled by card, change payment.meansCode instead — \"58\" (SEPA credit transfer) with payment.iban is what most invoices want.",
"example": "\"payment\": { \"meansCode\": \"48\", \"card\": { \"primaryAccountNumber\": \"4111111111\", \"holderName\": \"M Mustermann\" } }",
"xpath": "/ubl:Invoice/cac:PaymentMeans/cac:CardAccount",
"docsUrl": "https://attestwire.com/rules/BR-DE-24-a"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.