UBL-SR-26:Payment reference shall occur maximum once
Fix: Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice.
Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice.
Engine Classification
Requires user confirmation before application
What is UBL-SR-26?
UBL-SR-26 is a fatal validation rule defined in the EN16931 specification. It validates the PaymentID element in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: //cac:PaymentMeans/cbc:PaymentID
Why This Error Matters
Invoice will be rejected by EN16931 validators. These structural constraints ensure consistent processing by receiving systems.
UBL-SR-26 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-26
- ·Specification: EN16931
How to Fix It
Locate the duplicate entries
Search for multiple cbc:PaymentID elements at //cac:PaymentMeans/cbc:PaymentID. Only one instance is allowed per the specification.
Remove the duplicates
Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice.
Re-validate your invoice
Upload the corrected invoice to confirm UBL-SR-26 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:PaymentID error --> <cbc:PaymentID></cbc:PaymentID>
<!-- Provide the required value --> <cbc:PaymentID>VALID_VALUE</cbc:PaymentID>
Technical Reference
//cac:PaymentMeans/cbc:PaymentIDCommon Causes
- ·ERP system exports multiple values where EN16931 only allows one
- ·Data consolidation merged records without deduplicating
- ·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-26 automatically. See the fix response →
Frequently Asked Questions
Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice.
Your invoice contains multiple Payment reference elements (PaymentMeans/PaymentID). EN16931 allows only one payment reference per invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, UBL-SR-26 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of UBL-SR-26 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-26
Fix UBL-SR-26 with one click
Upload your invoice and we'll suggest a fix for your review before applying it.