Peppol BIS Billing 3.0 · rule
UBL-CR-420
What does UBL-CR-420 mean? A UBL invoice should not include the PaymentMeans CardAccount CV2ID
Why did my invoice fail UBL-CR-420?
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:CardAccount/cbc:CV2ID element, which has no corresponding business term in EN 16931, so a compliant invoice should not include it. EN 16931 limits payment card information (BG-18) to the account number, network and holder name; sensitive or technical card fields are excluded. The CV2 security code must never travel on an invoice.
Official rule text
A UBL invoice should not include the PaymentMeans CardAccount CV2ID
Common causes
- Payment gateway data copied wholesale into the CardAccount block
- ERP or e-invoicing software exports the full UBL 2.1 schema instead of the EN 16931 subset
- A mapping template copies every source field into UBL without filtering to the EN 16931 element list
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.