BR-DE-24-a:Payment code 48, 54, or 55 (card payment) requires Card Payment details...
Payment code 48, 54, or 55 (card payment) requires Card Payment details (BG-18). You specified card payment but didn't include card information.
Engine Classification
Ensure debited account ID is present for SEPA direct debit (code 58)
Confidence: 80% · Applied automatically in pipeline
What is BR-DE-24-a?
BR-DE-24-a is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the ID element under PaymentMandate > PayerFinancialAccount in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: //cac:PaymentMeans[cbc:PaymentMeansCode='58']/cac:PaymentMandate/cac:PayerFinancialAccount/cbc:ID
Why This Error Matters
Invoice rejected. Card payments need card information for reference.
BR-DE-24-a is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by XRechnung endpoints
- ·Error returned: BR-DE-24-a
- ·Specification: XRechnung (Germany)
Before / After
<cac:PaymentMeans> <cac:CardAccount>INVALID_CODE</cac:CardAccount> </cac:PaymentMeans>
<cac:PaymentMeans> <cac:CardAccount>VALID_CODE</cac:CardAccount> </cac:PaymentMeans>
Technical Reference
//cac:PaymentMeans[cbc:PaymentMeansCode='58']/cac:PaymentMandate/cac:PayerFinancialAccount/cbc:IDCommon Causes
- ·Card payment code used but BG-18 missing
- ·PaymentMeansCode 48/54/55 without PAYMENT CARD section
- ·Card payment selected but card details not exported
- ·Template missing BG-18 for card payment types
- ·Payment method mismatch with card information
Seeing this in production? The API handles BR-DE-24-a automatically. See the fix response →
Related Errors
Last updated: 27 February 2026
Handle BR-DE-24-a Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.