Peppol BIS Billing 3.0 · rule
UBL-CR-445
What does UBL-CR-445 mean? A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount PaymentNote
Why did my invoice fail UBL-CR-445?
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:PaymentMandate/cac:PayerFinancialAccount/cbc:PaymentNote element, which has no corresponding business term in EN 16931, so a compliant invoice should not include it. For direct debit (BG-19), EN 16931 supports only the mandate reference (BT-89) and the debited account identifier (BT-91); other mandate details are outside the model. Only the debited account identifier (cbc:ID, BT-91) is allowed under PayerFinancialAccount.
Official rule text
A UBL invoice should not include the PaymentMeans PaymentMandate PayerFinancialAccount PaymentNote
Common causes
- SEPA mandate data exported in full instead of only the mandate reference and debtor IBAN
- 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.