Peppol BIS Billing 3.0 · rule
UBL-CR-426
What does UBL-CR-426 mean? A UBL invoice should not include the PaymentMeans PayeeFinancialAccount AccountFormatCode
Why did my invoice fail UBL-CR-426?
EN 16931 defines a fixed semantic model, and any UBL element outside that model must not be used. This rule flags the cac:PaymentMeans/cac:PayeeFinancialAccount/cbc:AccountFormatCode element, which has no corresponding business term in EN 16931, so a compliant invoice should not include it. For the payee bank account, EN 16931 supports only the account identifier (BT-84), account name (BT-85) and service provider/branch identifier (BT-86); other account details are outside the model.
Official rule text
A UBL invoice should not include the PaymentMeans PayeeFinancialAccount AccountFormatCode
Common causes
- Bank-master data exported in full instead of only IBAN/account number, account name and BIC
- A mapping template copies every source field into UBL without filtering to the EN 16931 element list
- Reusing an invoice template from a non-EN 16931 UBL profile that populated this element
Related rules
UBL-CR-001 · UBL-CR-002 · UBL-CR-003 · UBL-CR-004 · UBL-CR-005 · UBL-CR-006 · UBL-CR-007 · UBL-CR-008
Paste it into the live demo, or call POST /v1/validate. See the quickstart.