Spanish billing-system compliance · phased

VERI*FACTU

Spanish requirements for billing software records, hash chaining, event records and QR-supported verifiability.

Billing recordsQR payloadsEvent records

Current version and implementation status

Version noteVerify current AEAT technical order and implementation dates
Statusphased
Reviewed2026-08-02
FamilySpanish billing-system compliance
Open official technical source

How to recognize the profile

Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.

  • QR verification URL
  • Chained record hash
  • Billing-system event data

Production validation stack

  1. 1
    Record structure

    Confirm that the document is well formed and structurally compatible with the intended VERI*FACTU syntax.

  2. 2
    Hash-chain consistency

    Apply semantic and business-rule checks rather than accepting a file merely because it parses.

  3. 3
    QR structure

    Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.

  4. 4
    Software and event-log requirements

    Apply the national, network or authority restrictions that narrow the base syntax.

EInvoiceLab’s browser tools provide detection, inspection and technical preflight. A profile is only production-valid after applying the correct official artefacts and obtaining the required network or authority outcome.

Common errors and corrective action

!
Broken hash chain

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Missing QR data

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Incorrect record type

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Clock or sequence inconsistency

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

Countries using or referencing this profile

Questions people ask

What is VERI*FACTU?

Spanish requirements for billing software records, hash chaining, event records and QR-supported verifiability.

How is VERI*FACTU validated?

A production check normally applies Record structure, Hash-chain consistency, QR structure, Software and event-log requirements. Local browser preflight cannot replace the official validation artefacts or authority outcome.

Which version should I use?

The current research note is: Verify current AEAT technical order and implementation dates. Confirm release notes at the official source before production deployment.

Practical tools

Inspect and prepare VERI*FACTU files