XML-006:Schematron validation failed
Fix: Fix business rule violations.
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 rejected by Peppol access points and never reaches the buyer.
Target path: Schematron rule failure
Why This Error Matters
Schematron enforces business rules.
XML-006 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
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. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, XML-006 is a critical error that must be fixed.
Related Errors
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for XML-006
Detect XML-006 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.