Peppol BIS Billing 3.0 · rule

UBL-CR-200

Layer en16931·Checked against Peppol BIS Billing 3.0 2026.5

What does UBL-CR-200 mean? A UBL invoice should not include the AccountingSupplierParty SellerContact

Why did my invoice fail UBL-CR-200?

This EN 16931 rule warns when the UBL element cac:AccountingSupplierParty/cac:SellerContact is present: the invoice should not include a SellerContact on the supplier party wrapper. The seller contact (BG-6) must be placed under cac:Party/cac:Contact; the sibling cac:SellerContact element is not part of the EN 16931 mapping and receivers will not read it. 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 AccountingSupplierParty SellerContact

Common causes

Contact data mapped to the intuitively named SellerContact instead of Party/Contact
Template based on a full UBL 2.1 SupplierParty example
Generator emitting both contact locations

How do I fix it?

<cac:AccountingSupplierParty>
  <cac:Party>
    <!-- BG-6: the only place for the seller contact -->
    <cac:Contact>
      <cbc:Name>Jane Doe</cbc:Name>
      <cbc:Telephone>+386 1 234 5678</cbc:Telephone>
    </cac:Contact>
  </cac:Party>
</cac:AccountingSupplierParty>

Check your invoice against this rule

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