What the regulation requires
Every invoice generates an issuing record, and every cancellation a cancellation record. Records are chained by a hash that includes the previous record's, so deleting one breaks the chain.
It also requires an electronic signature on the record, a QR code on the invoice, an event log for the system itself and a responsible declaration from the software maker.
The two modes
In Verifactu mode the system forwards records to the Tax Agency as they are generated. In exchange, local retention requirements are lighter.
In non-Verifactu mode the records stay at the company, but the system must guarantee tamper evidence, traceability and retention for the limitation period on its own.
The deadlines
Software producers had to offer compliant products from 29 July 2025.
RD 254/2025 originally set 1 January and 1 July 2026, but Royal Decree-law 15/2025 pushed them back a year: before 1 January 2027 for corporate income tax payers and before 1 July 2027 for everyone else.
What an auditor usually asks for
- Invoicing software with the maker's responsible declaration
- Documented choice between Verifactu and non-Verifactu mode
- Verifiable chaining of records
- QR code present on issued invoices
How the circuit is checked with Kimobox
- 1Identify which program issues each invoice series: sometimes there is more than one.
- 2Check that the document archive keeps the invoice exactly as issued, QR included.
- 3Keep a trail of who consulted or downloaded each invoice and when.
Kimobox does not issue invoices: it stores, indexes and gives access to the ones your invoicing system issues.