Verifactu modes: VERI*FACTU and the NO VERI*FACTU system
The RRSIF (RD 1007/2023) behind Verifactu allows two modes: VERI*FACTU, where the invoicing system sends each record to the Spanish Tax Agency (AEAT) straight away, and NO VERI*FACTU, where nothing is sent and the system must sign the records, keep an event log and store them to hand over if the AEAT asks. Both require an invoicing record with a hash and a QR on the invoice.
Both modes have the same dates:
| Who | Date | Status | Rule |
|---|---|---|---|
| Producers and resellers of invoicing software RDL 15/2025 did not change this date. | Since 29 Jul 2025 | In force | RD 1007/2023 · Orden HAC/1177/2024 |
| Corporate Income Tax payers | 1 Jan 2027 | Published in the BOE, future date | RDL 15/2025 |
| Everyone else, including the self-employed | 1 Jul 2027 | Published in the BOE, future date | RDL 15/2025 |
| Postponement of the pending obligations The note does not specify the scope for businesses invoicing over €8M. | Oct 2028 | Announced, no rule published | Nota de Hacienda, 5 oct 2026 |
This is not advice: each taxpayer determines what applies to them with their adviser.
What the VERI*FACTU and NO VERI*FACTU modes are
VERI*FACTU (system issuing verifiable invoices): the system sends the AEAT, online, every invoicing record for the invoices it issues. The AEAT holds the records and the user no longer has to keep them.
NO VERI*FACTU (system issuing non-verifiable invoices): the system does not send the records; it stores them and must guarantee their integrity, preservation, accessibility, legibility, traceability and unalterability for the whole tax limitation period.
Source: arts. 15 and 16 of the RRSIF, as explained in the AEAT FAQ. Who Verifactu applies to is covered on the hub: who Verifactu applies to.
Differences between VERI*FACTU and NO VERI*FACTU
| Aspect | VERI*FACTU | NO VERI*FACTU |
|---|---|---|
| Submission of records to the AEAT | Each record, immediately (subject to the AEAT flow control: wait between submissions or maximum batch, art. 16 of Order HAC/1177/2024) | No; only if the AEAT requests it |
| Invoicing record with chained hash | Yes | Yes |
| Electronic signature of records | Not required: the hash is enough (RRSIF, art. 16.3) | Yes |
| Event log | Not required | Yes |
| Detection of traceability failures | Not required | Yes |
| QR on the invoice | Yes, with the verifiable invoice legend | Yes, without the legend |
| Storage | The AEAT holds the records | The taxpayer keeps them |
| Covered by the Verifactu API | Yes | No |
Sources: RD 1007/2023, Order HAC/1177/2024 and the AEAT FAQ. In VERI*FACTU, arts. 6.b–f, 7.f, h, i, j, 8 and 9 of the Order do not apply (art. 3).
What the NO VERI*FACTU mode requires
Since it does not send the records, the system has to step up its controls. According to the AEAT, it must include, among other measures: an event log, electronic signature of invoicing and event records, export of those records, checks on hash, signature and chaining, and alarm handling.
It also has to detect chaining failures and warn when they occur, and the user is responsible for the record timestamps being accurate to within one minute (AEAT). The records are handed to the AEAT only if it asks for them.
The event log
It is the function by which the system automatically detects and records, as they happen, certain interactions with it, operations carried out with it or incidents during its use, and keeps their data so they can be consulted from the system itself. It is only mandatory in the NO VERI*FACTU mode; it is not needed in VERI*FACTU. It is set by art. 8.3 of the RRSIF and developed in Order HAC/1177/2024 (AEAT).
Under art. 9 of Order HAC/1177/2024, it records at least the start and end of operation as NO VERI*FACTU, the anomaly detection processes, restoring backups and exports; it also generates a summary record for every 6 hours of operation and before shutting down.
Switching modes
According to the AEAT, a company can join VERI*FACTU whenever it wants and, once it has, must stay at least until the end of the calendar year. Whoever starts the year in NO VERI*FACTU can switch to VERI*FACTU at any time, with the same minimum stay. The AEAT bases this on arts. 15 and 16.5 of the RRSIF and art. 17 of Order HAC/1177/2024.
Opting for VERI*FACTU is tacit: it is enough to start sending the records (art. 16.5 RRSIF). To leave it, the system states in a submission the last date it will operate as VERI*FACTU, and that first notice must arrive before the end of the year in which the waiver is to take effect (art. 17.3 of the Order).
This is not advice: each taxpayer determines what applies to them with their adviser.
System issuing non-verifiable invoices: where the name comes from
As opposed to the RRSIF's «systems issuing verifiable invoices» (VERI*FACTU, art. 16 of RD 1007/2023), the AEAT calls the systems that do not send their records «sistemas de emisión de facturas no verificables» (systems issuing non-verifiable invoices); Order HAC/1177/2024 says «NO VERI*FACTU». They are names for the same thing. Both are SIF: What a SIF is.
The Verifactu API works in the VERI*FACTU mode
The Verifactu API sends each record to the AEAT (VERI*FACTU), returns the QR to print next to the legend and tells you the AEAT’s response. It does not offer the NO VERI*FACTU mode, so your system has no signature or event log to manage.
Questions about the Verifactu modes
What is the difference between VERI*FACTU and NO VERI*FACTU?
Which is better, VERI*FACTU or NO VERI*FACTU?
What is a system issuing non-verifiable invoices?
Does a NO VERI*FACTU invoice carry a QR?
What is the Verifactu event log?
Try the Verifactu API in the test environment
Create your free account and send your first invoice in the VERI*FACTU mode.