XML-005:XML schema validation failed
Document does not conform to XSD schema.
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 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: XSD validation
Why This Error Matters
Schema validation ensures structure.
XML-005 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: XML-005
- ·Specification: ubl-2.1
How to Fix It
Check error location
Schema validator shows position
Fix element
Match schema requirements
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <XSD validation></XSD validation>
<!-- Corrected --> <XSD validation>VALID_VALUE</XSD validation>
Technical Reference
XSD validationCommon 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. Invoice Navigator can help identify and fix this issue.
Yes, XML-005 is a critical error that must be fixed.
Related Errors
Last updated: 19 January 2026
Handle XML-005 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.