errorsyntaxubl-2.1

UBL-SR-03:UBL element order incorrect

Fix: Reorder elements according to UBL 2.1 schema.

UBL elements must follow schema-defined order.

Severity
Fatal
Rule set
ubl-2.1
Country
All EU
Fix type
CONFIRM
Confidence
90%
Category
structural

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 rejected by Peppol access points and never reaches 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 — the invoice must be corrected and re-sent before it can reach the recipient.

Validator Behavior

  • ·Causes invoice rejection
  • ·Fails UBL schema validation
  • ·Error returned: UBL-SR-03
  • ·Specification: ubl-2.1

How to Fix It

1.

Check schema

UBL defines strict element order

2.

Reorder elements

Match schema sequence

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Required block is missing -->
<!-- <cac:DespatchDocumentReference> ... </cac:DespatchDocumentReference> -->
After
<!-- Add the required block -->
<cac:DespatchDocumentReference>
  <!-- child elements -->
</cac:DespatchDocumentReference>

Technical Reference

XPath/Invoice/cac:DespatchDocumentReference
Specubl-2.1
Operationremove_duplicates
StrategyRemove duplicate despatch document references, keeping the first occurrence

Common 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. Invoice Navigator can propose a fix for this error, which you review and confirm before it is applied.

Yes, UBL-SR-03 is a critical error that will cause invoice rejection. It must be fixed before submission.

Related Errors

Related Content

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for UBL-SR-03

Fix UBL-SR-03 with one click

Upload your invoice and we'll suggest a fix for your review before applying it.