UBL-SR-45:Due Date shall occur maximum once
Fix: Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
Engine Classification
Requires user confirmation before application
What is UBL-SR-45?
UBL-SR-45 is a fatal validation rule defined in the EN16931 specification. It validates the PaymentDueDate 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:PaymentDueDate
Why This Error Matters
Invoice will be rejected by EN16931 validators. These structural constraints ensure consistent processing by receiving systems.
UBL-SR-45 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-45
- ·Specification: EN16931
How to Fix It
Locate the duplicate entries
Search for multiple cbc:PaymentDueDate elements at //cac:PaymentMeans/cbc:PaymentDueDate. Only one instance is allowed per the specification.
Remove the duplicates
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
Re-validate your invoice
Upload the corrected invoice to confirm UBL-SR-45 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:PaymentDueDate error --> <cbc:PaymentDueDate></cbc:PaymentDueDate>
<!-- Provide the required value --> <cbc:PaymentDueDate>VALID_VALUE</cbc:PaymentDueDate>
Technical Reference
//cac:PaymentMeans/cbc:PaymentDueDateCommon 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-45 automatically. See the fix response →
Frequently Asked Questions
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice.
Your invoice contains multiple Due Date elements (PaymentMeans/PaymentDueDate). EN16931 allows only one due date per invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, UBL-SR-45 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of UBL-SR-45 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-45
Fix UBL-SR-45 with one click
Upload your invoice and we'll suggest a fix for your review before applying it.