Verifactu: what it is, who it applies to and how it works
Verifactu is the Spanish Tax Agency (AEAT) system that makes invoicing software generate tamper-proof invoicing records and, in the VERI*FACTU mode, send them to the AEAT in real time. It is regulated by RD 1007/2023 (RRSIF) and applies in common territory to companies and self-employed people who invoice with a computer program: the dates published in the BOE are 1 January 2027 (Corporate Income Tax) and 1 July 2027 (everyone else), and the Ministry of Finance has announced a postponement to October 2028 with no rule published.
Verifactu dates
| Who | Date | Status | Rule |
|---|---|---|---|
| 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 |
| 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 |
This is not advice: each taxpayer determines what applies to them with their adviser.
What Verifactu is and how it works
Verifactu is not a program or an AEAT service you connect to: it is the set of requirements that the invoicing computer system (SIF), the program used to issue invoices, has to meet. More in What a SIF is.
Tamper-proof invoicing records
For every invoice it issues, the SIF generates an invoicing record: a file with the invoice’s tax data, in the format set by the AEAT. What cannot be altered is the record, not the invoice: if an invoice has to be corrected, a corrective invoice is issued or the invoice is cancelled, and each operation generates its own record.
Hash and chaining
Each record carries a hash calculated from its data and from the hash of the previous record. The records are chained, and any change breaks the chain. Chaining is not the same as the sequential numbering of invoices: they are different things and both are kept.
The QR on every invoice
Invoices issued with a SIF carry a QR code with an AEAT URL, unique to each invoice. In the VERI*FACTU mode the recipient can use it to check that the invoice is on record at the AEAT; in NO VERI*FACTU the QR lets the recipient send the invoice data to the AEAT. Size, position and legend in Verifactu QR code.
Two modes: VERI*FACTU and NO VERI*FACTU
In the VERI*FACTU mode, the SIF sends each record to the AEAT when the invoice is issued. In the NO VERI*FACTU mode nothing is sent: the SIF keeps the records, with extra requirements for signatures and an event log. Differences in VERI*FACTU and NO VERI*FACTU modes.
The legal origin is Law 11/2021 on measures to prevent and fight tax fraud; the regulation is RD 1007/2023 (RRSIF), and the technical specifications are in Order HAC/1177/2024. A summary of each rule in Verifactu regulations (Royal Decree 1007/2023).
Who Verifactu applies to under the rules
RD 1007/2023 sets three criteria: who the taxpayer is, whether they invoice with a computer system and where they are taxed. It makes no distinction by sector or size, but it has specific exclusions.
| Criterion | What the rules say |
|---|---|
| Type of taxpayer | Corporate Income Tax payers, Personal Income Tax payers with an economic activity, Non-Resident Income Tax payers with a permanent establishment and pass-through entities (entidades en atribución de rentas). |
| Use of a SIF | It applies to whoever issues their invoices with an invoicing computer system. |
| Territory | Common territory, including the Canary Islands, Ceuta and Melilla. |
| Exclusion | What applies instead |
|---|---|
| Whoever keeps their record books through the SII | The Immediate Supply of Information (SII), while they remain in it. See SII and Verifactu. |
| Whoever is taxed in Álava, Bizkaia or Gipuzkoa | TicketBAI, from each foral treasury. See Verifactu in the Basque Country. |
| Whoever is taxed in Navarre | The Navarre Foral Treasury is preparing NaTicket, announced with no rule published. See NaTicket. |
| Whoever is not required to issue invoices, for the operations they do not invoice | No records are generated. If they issue invoices with a SIF, even voluntarily, it does apply. |
| Entities exempt from Corporate Income Tax (art. 9.1 of Law 27/2014) | They are not subject to it; partially exempt entities, only for their taxable, non-exempt income (art. 3.1.a RRSIF). |
| Whoever has an AEAT non-application ruling (art. 5 RRSIF) | Whatever the ruling says, which may be temporary or partial. |
The rule of the 4 NOs. This is the name the AEAT uses in its FAQ to summarise when the regulation applies. There are four conditions: using a SIF to invoice; not being in the SII; not having the tax domicile in the Basque Country or Navarre, and not having a non-application ruling.
Producers and resellers of invoicing software have their own obligation: offering adapted systems, in force since 29 July 2025.
This is not advice: each taxpayer determines what applies to them with their adviser.
Everything about Verifactu, topic by topic
The AEAT offers a free app to invoice with Verifactu, meant for low volumes and with no connection to your software. More in The AEAT Verifactu app.
Comply with Verifactu from your software, through an API
If you have your own software or make invoicing software, the Verifactu API receives the invoice as JSON, returns the QR straight away and generates, chains and sends the record to the AEAT. Your customer needs no digital certificate: Verifacti is an AEAT social collaborator. It covers the VERI*FACTU mode only.
Built for developers
Public documentation with examples for every call, quick start guide, Postman collections, llms.txt and a free account with a test environment.
Typical integration: one to three developer daysSpecialists in Spain
Common and foral territory: Verifactu, TicketBAI and SII with one provider.
TicketBAI guarantor software in Álava, Bizkaia and GipuzkoaProven reliability
Hundreds of companies and software vendors in production with Verifacti. Data hosted in the EU and an SLA in the terms of use.
AEAT social collaboratorVerifactu, SII, TicketBAI and e-invoicing
| Rule | Relation to Verifactu |
|---|---|
| SII | Whoever is in the SII is outside Verifactu while they remain in it. SII and Verifactu. |
| TicketBAI | In Álava, Bizkaia and Gipuzkoa, TicketBAI applies instead of Verifactu. Verifactu in the Basque Country. |
| NaTicket | In Navarre, NaTicket, announced with no rule published. NaTicket. |
| B2B e-invoicing | It adds to Verifactu, it does not replace it. Verifactu vs e-invoicing. |
Verifactu resources
Questions about Verifactu
Who is exempt from Verifactu?
Does Verifactu apply in the Canary Islands, Ceuta and Melilla?
What about the Basque Country and Navarre?
If I am in the SII, do I have to comply with Verifactu?
Is Verifactu the same as e-invoicing?
Building Verifactu into your software?
Try the Verifactu API with the free account: send an invoice as JSON and get the QR straight away.