errorsyntaxubl-2.1

XML-005:XML schema validation failed

Fix: Fix elements to match schema definition.

Document does not conform to XSD schema.

Severity
Fatal
Rule set
ubl-2.1
Country
All EU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: The document structure does not match the required XSD schema. This indicates missing required elements, incorrect element order, or invalid data types. Review the specific validation errors and update your invoicing software template to generate schema-compliant XML.

What is XML-005?

XML-005 is a fatal validation rule defined in the ubl-2.1 specification. It validates the XSD validation 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: XSD validation

This error requires manual correction — financial fields are protected by policy.

Why This Error Matters

Schema validation ensures structure.

XML-005 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: XML-005
  • ·Specification: ubl-2.1

How to Fix It

1.

Check error location

Schema validator shows position

2.

Fix element

Match schema requirements

XML Example

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

Before
<!-- Triggers validation error -->
<XSD validation></XSD validation>
After
<!-- Corrected -->
<XSD validation>VALID_VALUE</XSD validation>

Technical Reference

XPathXSD validation
Specubl-2.1

Common Causes

  • ·Missing required element
  • ·Wrong element type
  • ·Invalid sequence

Seeing this in production? The API handles XML-005 automatically. See the fix response →

Frequently Asked Questions

Document does not conform to XSD schema.

Fix elements to match schema definition. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

Yes, XML-005 is a critical error that must be fixed.

Related Errors

Related Content

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for XML-005

Detect XML-005 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.