BR-ES-02:Missing VeriFACTU hash chain
Spanish VeriFACTU invoices must include the hash chain for audit trail.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: VeriFACTU invoices require a cryptographic hash chain for audit trail. This must be generated by certified invoicing software that implements the Spanish VeriFACTU regulations. Update your invoicing system to a VeriFACTU-compliant solution.
What is BR-ES-02?
BR-ES-02 is a fatal validation rule defined in the verifactu specification (ESP national rules). It validates the XPath: VeriFACTU-specific hash elements 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: XPath: VeriFACTU-specific hash elements
Why This Error Matters
VeriFACTU requires chained hashes for tamper-proof audit trail.
BR-ES-02 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: BR-ES-02
- ·Specification: verifactu
How to Fix It
Calculate hash
SHA-256 of invoice data
Chain reference
Include previous invoice hash
Sign result
Electronic signature of hash
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <XPath: VeriFACTU-specific hash elements></XPath: VeriFACTU-specific hash elements>
<!-- Corrected --> <XPath: VeriFACTU-specific hash elements>VALID_VALUE</XPath: VeriFACTU-specific hash elements>
Technical Reference
XPath: VeriFACTU-specific hash elementsCode Example
<!-- VeriFACTU hash chain structure -->
<Huella>
<EncadenamientoFacturaAnterior>ABC123...</EncadenamientoFacturaAnterior>
<HuellaActual>DEF456...</HuellaActual>
</Huella>Common Causes
- ·Missing hash
- ·Broken chain
- ·Invalid signature
Seeing this in production? The API handles BR-ES-02 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Spanish VeriFACTU invoices must include the hash chain for audit trail.
Include required hash chain elements. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, BR-ES-02 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
BR-ES-02 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
BR-ES-02 is commonly seen in exports from Spanish VeriFACTU systems. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Content
Last updated: 3 March 2026
Detect BR-ES-02 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.