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

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

1. Why This Rule Triggers (Diagnostic Message)

The payment means type code (BT-81) is "59", which XRechnung treats as a direct debit (code 59), so the CREDIT TRANSFER (BG-17) group must not be present — but it is. 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-25-b

Remove payment.iban, keeping only payment.directDebit (BG-19). 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": "59", "directDebit": { "mandateReference": "MANDAT-2026-01", "creditorIdentifier": "DE98ZZZ09999999999", "debitedAccount": "DE98700500001234567890" } }