Peppol BIS Billing 3.0 · rule
UBL-CR-202
What does UBL-CR-202 mean? A UBL invoice should not include the AccountingCustomerParty SupplierAssignedAccountID
Why did my invoice fail UBL-CR-202?
This EN 16931 rule warns when the UBL element cac:AccountingCustomerParty/cbc:SupplierAssignedAccountID is present: the invoice should not include a supplier-assigned account ID on the customer party wrapper. The seller's internal number for the buyer is not a wrapper-level field in EN 16931; buyer identifiers belong in cac:Party/cac:PartyIdentification/cbc:ID (BT-46). The element is not forbidden by UBL itself, but it lies outside the EN 16931 core invoice model, so remove it to keep the invoice fully conformant and interoperable.
Official rule text
A UBL invoice should not include the AccountingCustomerParty SupplierAssignedAccountID
Common causes
- The seller's customer number mapped to the wrapper element instead of PartyIdentification
- Legacy UBL 2.0-style mapping carried forward
- Template based on a full UBL 2.1 CustomerParty example
How do I fix it?
<cac:AccountingCustomerParty>
<cac:Party>
<cac:PartyIdentification>
<cbc:ID>CUST-10042</cbc:ID>
</cac:PartyIdentification>
</cac:Party>
</cac:AccountingCustomerParty>
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.