Peppol BIS Billing 3.0 · rule
UBL-CR-199
What does UBL-CR-199 mean? A UBL invoice should not include the AccountingSupplierParty AccountingContact
Why did my invoice fail UBL-CR-199?
This EN 16931 rule warns when the UBL element cac:AccountingSupplierParty/cac:AccountingContact is present: the invoice should not include an accounting contact on the supplier party wrapper. The core model allows only one seller contact (BG-6) under cac:Party/cac:Contact; an additional accounting-specific contact has no mapped 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 AccountingSupplierParty AccountingContact
Common causes
- The finance department's contact was mapped to AccountingContact instead of cac:Party/cac:Contact
- ERP exports multiple role-based contacts
- Template copied from a full UBL 2.1 sample
How do I fix it?
<!-- use the single seller contact under cac:Party (BG-6) -->
<cac:AccountingSupplierParty>
<cac:Party>
<cac:Contact>
<cbc:Name>Accounts Receivable</cbc:Name>
<cbc:ElectronicMail>ar@example.com</cbc:ElectronicMail>
</cac:Contact>
</cac:Party>
</cac:AccountingSupplierParty>
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.