Peppol BIS Billing 3.0 · rule

UBL-CR-201

Layer en16931·Checked against Peppol BIS Billing 3.0 2026.5

What does UBL-CR-201 mean? A UBL invoice should not include the AccountingCustomerParty CustomerAssignedAccountID

Why did my invoice fail UBL-CR-201?

This EN 16931 rule warns when the UBL element cac:AccountingCustomerParty/cbc:CustomerAssignedAccountID is present: the invoice should not include a customer-assigned account ID on the customer party wrapper. Buyer identification in EN 16931 uses the buyer identifier (BT-46) under cac:Party/cac:PartyIdentification/cbc:ID; the wrapper-level CustomerAssignedAccountID is not mapped to any business term. 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 CustomerAssignedAccountID

Common causes

The buyer identifier was mapped to the wrapper element instead of PartyIdentification
Legacy UBL 2.0-style mapping carried forward
ERP exports its internal customer number into every available ID slot

How do I fix it?

<cac:AccountingCustomerParty>
  <cac:Party>
    <!-- BT-46: buyer identifier -->
    <cac:PartyIdentification>
      <cbc:ID>CUST-10042</cbc:ID>
    </cac:PartyIdentification>
  </cac:Party>
</cac:AccountingCustomerParty>

Check your invoice against this rule

Paste it into the live demo, or call POST /v1/validate. See the quickstart.