XML-006:Schematron validation failed
Document failed business rule validation.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: The document failed one or more business rule validations. Check the specific error details in the validation report to identify which rules failed. Each business rule failure will have its own error code with specific fix guidance. Address each specific error individually.
What is XML-006?
XML-006 is a fatal validation rule defined in the en16931 specification. It validates the Schematron rule failure 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: Schematron rule failure
Why This Error Matters
Schematron enforces business rules.
XML-006 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 EN 16931 business rule validation
- ·Error returned: XML-006
- ·Specification: en16931
How to Fix It
Check rule
Which BR rule failed?
Fix content
Correct the data to match rule
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <Schematron rule failure></Schematron rule failure>
<!-- Corrected --> <Schematron rule failure>VALID_VALUE</Schematron rule failure>
Technical Reference
Schematron rule failureCommon Causes
- ·BR rule violation
- ·Cross-field validation failure
Seeing this in production? The API handles XML-006 automatically. See the fix response →
Frequently Asked Questions
Document failed business rule validation.
Fix business rule violations. Invoice Navigator can help identify and fix this issue.
Yes, XML-006 is a critical error that must be fixed.
See Also
Related Errors
Last updated: 19 January 2026
Handle XML-006 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.