UBL-SR-16:Buyer identifier shall occur maximum once
Fix: Your invoice contains multiple Buyer identifier elements (AccountingCustomerParty/Party/PartyIdentification/ID). EN16931 allows only one buyer identifier.
Your invoice contains multiple Buyer identifier elements (AccountingCustomerParty/Party/PartyIdentification/ID). EN16931 allows only one buyer identifier.
Engine Classification
Requires user confirmation before application
What is UBL-SR-16?
UBL-SR-16 is a fatal validation rule defined in the EN16931 specification. It validates the ID element under Party > PartyIdentification in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID
Why This Error Matters
Invoice will be rejected by EN16931 validators. These structural constraints ensure consistent processing by receiving systems.
UBL-SR-16 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Fails EN 16931 business rule validation
- ·Error returned: UBL-SR-16
- ·Specification: EN16931
How to Fix It
Locate the duplicate entries
Search for multiple cbc:ID elements at /Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID. Only one instance is allowed per the specification.
Remove the duplicates
Your invoice contains multiple Buyer identifier elements (AccountingCustomerParty/Party/PartyIdentification/ID). EN16931 allows only one buyer identifier.
Re-validate your invoice
Upload the corrected invoice to confirm UBL-SR-16 is resolved.
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:ID error --> <cbc:ID></cbc:ID>
<!-- Provide the required value --> <cbc:ID>VALID_VALUE</cbc:ID>
Technical Reference
/Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:IDCommon Causes
- ·ERP system exports multiple references where only one is allowed in EN16931
- ·Data consolidation merged records that should have been deduplicated
- ·Template or mapping incorrectly configured to output duplicate elements
- ·Manual editing introduced extra elements
- ·Invoice conversion from another format did not merge duplicate entries
Seeing this in production? The API handles UBL-SR-16 automatically. See the fix response →
Frequently Asked Questions
Your invoice contains multiple Buyer identifier elements (AccountingCustomerParty/Party/PartyIdentification/ID). EN16931 allows only one buyer identifier.
Your invoice contains multiple Buyer identifier elements (AccountingCustomerParty/Party/PartyIdentification/ID). EN16931 allows only one buyer identifier. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, UBL-SR-16 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of UBL-SR-16 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for UBL-SR-16
Fix UBL-SR-16 with one click
Upload your invoice and we'll suggest a fix for your review before applying it.