SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
FATAL Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BG-17, BG-19

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

Fixture ID: cardPlusTransferAndDebit · XPath: /ubl:Invoice/cac:PaymentMeans/cac:PayeeFinancialAccount

1. Why This Rule Triggers (Diagnostic Message)

The payment means type code (BT-81) is "48", which XRechnung treats as a card payment (codes 48, 54 and 55), so the CREDIT TRANSFER (BG-17) and DIRECT DEBIT (BG-19) groups must not be present — but they are. A payment instruction that names one settlement method and then supplies the account details of another is not merely redundant: the payer's system reads the code, looks for the matching group, and has no rule for what to do with the extra one. XRechnung closes that ambiguity by forbidding it outright.

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

Remove payment.iban and payment.directDebit, keeping only payment.card (BG-18). If you meant the other method, change payment.meansCode to match it instead — the code is what decides which group is required.

3. Valid Code / Payload Example

"payment": { "meansCode": "48", "card": { "primaryAccountNumber": "4111111111" } }
Test & Validate XML / JSON in Live SchemaGuard Validator →