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, BT-84

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

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

1. Why This Rule Triggers (Diagnostic Message)

The payment means type code (BT-81) is "58", which XRechnung treats as a credit transfer, so the CREDIT TRANSFER group (BG-17) must be present. In UBL that group is cac:PayeeFinancialAccount, and this library emits it only when you supply an account identifier. Core EN 16931 states the same requirement as BR-61; BR-DE-23-a is the German CIUS restating it against the group rather than the field, and both appear in a KoSIT report.

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

Set payment.iban to the account the buyer should transfer to. If you did not intend a credit transfer, change payment.meansCode — "59" for SEPA direct debit (then supply payment.directDebit), "48" for card (then supply payment.card), "97" for clearing between partners — but note each of those brings its own mandatory group.

3. Valid Code / Payload Example

"payment": { "meansCode": "58", "iban": "DE02120300000000202051", "accountName": "Acme GmbH" }
Test & Validate XML / JSON in Live SchemaGuard Validator →