BR-DE-24-a — E-Invoice Validation Rule & Fix

Fixture ID: cardMeansCode · XPath: /ubl:Invoice/cac:PaymentMeans/cac:CardAccount

1. Why This Rule Triggers (Diagnostic 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.

2. How to Fix BR-DE-24-a

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.

3. Valid Code / Payload Example

"payment": { "meansCode": "48", "card": { "primaryAccountNumber": "4111111111", "holderName": "M Mustermann" } }