ES-R-002:Invalid FacturaE format
Spanish B2G invoices must use FacturaE 3.2.x format.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: Spanish B2G invoices must use FacturaE 3.2.x format. This requires generating the invoice in the correct FacturaE XML schema from your invoicing software. UBL/CII formats cannot be auto-converted to FacturaE.
What is ES-R-002?
ES-R-002 is a fatal validation rule defined in the facturae specification (ESP national rules). It validates the SchemaVersion element under fe:Facturae > FileHeader 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: XPath: /fe:Facturae/FileHeader/SchemaVersion
Why This Error Matters
Spanish FACe platform requires specific FacturaE version.
ES-R-002 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
- ·Error returned: ES-R-002
- ·Specification: facturae
How to Fix It
Check schema
Must be 3.2.x version
Validate format
Against official FacturaE schema
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <SchemaVersion></SchemaVersion>
<!-- Corrected --> <SchemaVersion>VALID_VALUE</SchemaVersion>
Technical Reference
XPath: /fe:Facturae/FileHeader/SchemaVersionCommon Causes
- ·Wrong schema version
- ·Using UBL instead of FacturaE
Seeing this in production? The API handles ES-R-002 automatically. See the fix response →
Frequently Asked Questions
Spanish B2G invoices must use FacturaE 3.2.x format.
Use FacturaE 3.2.1 or 3.2.2 schema version. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, ES-R-002 is a critical error that will cause invoice rejection. It must be fixed before submission.
Related Content
Last updated: 3 March 2026
Detect ES-R-002 Before Submission
This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.