UBL-SR-03:UBL element order incorrect
UBL elements must follow schema-defined order.
Engine Classification
Requires user confirmation before application
What is UBL-SR-03?
UBL-SR-03 is a fatal validation rule defined in the ubl-2.1 specification. It validates the DespatchDocumentReference element in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: /Invoice/cac:DespatchDocumentReference
Why This Error Matters
Invoice will be rejected by EN16931 validators. These structural constraints ensure consistent processing by receiving systems.
UBL-SR-03 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Fails UBL schema validation
- ·Error returned: UBL-SR-03
- ·Specification: ubl-2.1
How to Fix It
Check schema
UBL defines strict element order
Reorder elements
Match schema sequence
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Required block is missing --> <!-- <cac:DespatchDocumentReference> ... </cac:DespatchDocumentReference> -->
<!-- Add the required block --> <cac:DespatchDocumentReference> <!-- child elements --> </cac:DespatchDocumentReference>
Technical Reference
/Invoice/cac:DespatchDocumentReferenceCommon 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-03 automatically. See the fix response →
Frequently Asked Questions
UBL elements must follow schema-defined order.
Reorder elements according to UBL 2.1 schema. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, UBL-SR-03 is a critical error that will cause invoice rejection. It must be fixed before submission.
Related Errors
Last updated: 21 February 2026
Handle UBL-SR-03 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.