Spain
VERI*FACTU: an honest status.
Spain requires invoicing software to keep a tamper-evident record chain, print a QR code and, in VERI*FACTU mode, report each invoice to the tax agency. Rechvix is working toward this. It is not compliant yet, and this page says exactly how far along it is.
| Requirement | What it involves | Status |
|---|---|---|
| Chained record fingerprint (SHA-256 huella) | Fingerprint functions for invoice and cancellation records, reproducing the three worked examples in AEAT's hash specification v0.1.2. | Built, not yet wired into invoicing |
| QR verification URL | URL builder with AEAT's parameter encoding for the test and production hosts, checked against the encoding example in AEAT's QR document v0.5.0. | Built, not yet printed on documents |
| Append-only record chain in the database | A per-issuer chain written in the same transaction that finalizes or cancels an invoice, with no update or delete path. | Not built |
| AEAT XML records validated against the XSDs | Invoice and cancellation records, system information and installation number. | Not built |
| QR and legend on A4, compact and 80 mm thermal layouts | 30 to 40 mm, error-correction level M, with the required legend. | Not built |
| Submission to AEAT | Mutual-TLS submission with a qualified certificate, retries and handling of accepted, accepted-with-errors and rejected responses. | Not built; never run against AEAT |
| Declaración responsable | A legal statement by the software producer, made only after the above is built and tested. | Not issued |
The built parts are in the open-source repository, in docs/verifactu.md (opens in a new tab), with tests that reproduce AEAT's published examples. India GST is covered separately on the India GST page, and what Rechvix does for Spain today is on the accountant exports page.
FAQ
VERI*FACTU questions
Is Rechvix compliant with VERI*FACTU today?
No. Rechvix prepares IVA workpapers for your accountant, but it does not yet keep the chained record log, print the AEAT QR code or submit records to AEAT. Do not rely on it to meet the VERI*FACTU rules.
When will it be?
There is no committed date. AEAT's note, updated 13 October 2026, gives 1 January 2027 for corporate-income-tax payers and 1 July 2027 for other taxpayers; check the AEAT page for the current position. We will publish a date only when the remaining work has a tested plan.
Who signs the declaración responsable?
The producer of the software, NODEDR INFOTECH PRIVATE LIMITED, after the system has been built and tested against the requirements. It cannot be generated by the software and has not been issued.
What about NODEDR POS and OrderRestro?
They are separate products with their own code. The same chain, QR and submission work is needed for each and has not been done for them. Neither should be described as VERI*FACTU compliant.
What should a Spanish business do meanwhile?
Ask your gestor which VERI*FACTU-compliant invoicing system to use before your deadline. Rechvix remains useful for stock, purchasing, accounts and IVA workpapers, but not as your issuing system for Spanish invoices.
Check your own obligations
Deadlines and scope depend on your business. Confirm them with your gestor and AEAT.