# What is VeriFactu and how does it affect your invoices?

URL: https://melso.ai/en/blog/what-is-verifactu-spain
Published: 2026-10-12 · Updated: 2026-10-12

What VeriFactu is, how the system works under the hood (record, hash, QR code and submission to the AEAT), what changes on your invoices, who it applies to and which date holds in October 2026, with a worked example.

## What is VeriFactu?

What is VeriFactu? It is the Spanish regulation that requires invoicing software to record every invoice as it is issued, chained to the previous one, with no way to delete it. In the system's VERI*FACTU mode, the software sends each record to Hacienda (the AEAT, Spain's tax agency). As of 12 October 2026, the legal date for the self-employed is 1 July 2027.

> [!RESUMEN]
> - VeriFactu is the Regulation on invoicing software systems, approved by Royal Decree 1007/2023.
> - Every invoice issued with software generates a record with a SHA-256 hash chained to the previous one, plus a QR code.
> - There are two modes: VERI*FACTU sends every record to the AEAT; non-VERI*FACTU keeps them signed, with an event log.
> - Date in force as of 12 October 2026: 1 January 2027 for companies and 1 July 2027 for everyone else, including the self-employed. The delay to October 2028 is only an announcement.
> - The channel does not change: you can still send invoices as a PDF or on paper.

Behind the name sits a specific rule: [Royal Decree 1007/2023](https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840), which approves the Regulation on the requirements for invoicing software systems (in Spanish, Reglamento de requisitos de los sistemas informáticos de facturación, which Hacienda shortens to RRSIF). "VeriFactu" comes from *factura verificable* (verifiable invoice) and is, strictly speaking, the name of one of the two ways to comply. In everyday use it stands for the whole system, and that is how we use it here.

Below you will find how it works under the hood, what changes on your invoices, who it applies to, which date counts and a worked example. If you are after an action plan for your own situation, see [VeriFactu for the self-employed](/blog/verifactu-autonomos) (in Spanish), and if you would like someone to issue your invoices for you, see how [Melso invoicing](/en/facturas) works.

## Where the VeriFactu regulation comes from

VeriFactu is the last link in a chain of rules:

1. **Law 11/2021 on measures against tax fraud.** It added letter j) of article 29.2 to the [General Tax Law](https://www.boe.es/buscar/act.php?id=BOE-A-2003-23186) (Ley General Tributaria): anyone carrying on a business activity who uses accounting, invoicing or management software must use systems that ensure "the integrity, preservation, accessibility, legibility, traceability and unalterability of the records". The same law created the penalty in article 201 bis, covered further down.
2. **Royal Decree 1007/2023.** This is the VeriFactu regulation proper. It says who is required to comply, what the software must do and what data each record holds.
3. **Order HAC/1177/2024.** [Order HAC/1177/2024](https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138) sets the technical details: record format, hash algorithm, QR code size and how the data is sent. It came into force on 29 October 2024.
4. **Invoicing Regulation.** [Royal Decree 1619/2012](https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696) was amended to add the QR code and the VERI*FACTU label to invoices.

The AEAT (Agencia Estatal de Administración Tributaria) runs the system and receives the records.

The aim is to stamp out so-called dual-use software: programs that let you issue an invoice to the customer and then delete it or reduce it in the books, so as to declare fewer sales. With VeriFactu, every change leaves a trace.

## How VeriFactu works, step by step

When you issue an invoice with adapted software, this is what happens:

![Five VeriFactu steps: the software creates the issuance record, calculates the SHA-256 hash chained to the previous one, puts the QR code on the invoice, sends the record to the AEAT in VERI*FACTU mode and, if something needs correcting, creates a new record without deleting the original.](https://storage.googleapis.com/albert-489117-melso-blog-media/diagrams/en/que-es-verifactu/1-steps-fe7a411f3a.png?w=1600&h=1034&m=1&mw=1080&mh=1746 "What the software does every time you issue an invoice")

### 1. An issuance record is created

[Article 9 of the regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840) requires the software to generate a record "at the same time as, or immediately before, the issue of each invoice". You do not create it yourself: the software does it on its own.

Under article 10, that record includes, among other data, your NIF (tax ID) and name, the invoice number and series, the date, the invoice type, the total amount, the VAT breakdown and the date, hour, minute and second when it was generated.

### 2. The hash is calculated and chained

Each record carries a digital fingerprint, or hash: a code that summarises its contents. [Order HAC/1177/2024](https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138) specifies the SHA-256 algorithm. The key point is that each record's hash includes the hash of the record before it. If someone changes an amount on a March invoice, its hash changes and the chain stops matching for every invoice that follows.

### 3. The invoice carries a QR code

The invoice includes a QR code with part of its contents. [Article 21 of the order](https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138) requires it to measure between 30x30 and 40x40 millimetres. What it allows depends on the mode: in VERI*FACTU, whoever receives the invoice can scan it and check on the AEAT's website that the record was sent; in non-VERI*FACTU, the recipient can report the invoice details to the AEAT, but the invoice is not verifiable. A structured e-invoice does not need the QR image: including its URL as a field is enough (article 20.2 of the order). If the software works in VERI*FACTU mode, the invoice adds the wording "Factura verificable en la sede electrónica de la AEAT" (invoice verifiable on the AEAT's website) or simply "VERI*FACTU", as set out in [article 6 of the Invoicing Regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696) for full invoices (article 7 does the same for simplified ones).

### 4. The record is sent to the AEAT (if you choose VERI*FACTU)

In VERI*FACTU mode, the software sends the records to the AEAT automatically. [Article 16 of the technical order](https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138) allows up to 1,000 records per submission and sets an initial waiting time of 60 seconds between submissions, which the AEAT can adjust. What travels is the invoicing record, not the invoice PDF.

### 5. If something needs correcting, another record is created

No record is ever deleted or rewritten. If the invoice has the kind of mistake that requires a correction, you issue a [corrective invoice](/en/blog/corrective-invoice-spain) (factura rectificativa) with its own issuance record. If an invoice should never have been issued (for example, you issued it twice), [article 11 of the regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840) provides for a cancellation record, as long as neither a corrective invoice nor another procedure under the Invoicing Regulation applies. If the error is only in the record's data and not on the invoice, a correction record (a *subsanación*, in the AEAT's terms) is sent. Both rules are explained in section 17 of the [AEAT's FAQs for developers](https://sede.agenciatributaria.gob.es/static_files/AEAT_Desarrolladores/EEDD/IVA/VERI-FACTU/FAQs-Desarrolladores.pdf). In every case the original record stays there, untouched.

## VERI*FACTU and non-VERI*FACTU systems

The regulation lets you comply in two ways. Under its [article 16](https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840), software that sends every record to the AEAT counts as a verifiable invoice issuing system, officially a "Sistema de emisión de facturas verificables" or "Sistema VERI*FACTU".

| | VERI*FACTU system | Non-VERI*FACTU system |
| --- | --- | --- |
| Sending records to the AEAT | Automatic, as each invoice is issued | Not sent; you hand them over when the AEAT asks |
| Electronic signature on each record | Not needed | Mandatory |
| Preservation and traceability requirements (article 8) | Presumed to be met by design (article 16.2) | Must meet them all, including the event log |
| Wording on the invoice | QR code + "VERI*FACTU" or "Factura verificable en la sede electrónica de la AEAT" | QR code only |

For a self-employed person, a VERI*FACTU system is almost always the simplest choice. The software does the work and you do not have to keep signed records or an event log. In exchange, Hacienda receives the records of your invoices in near real time.

## How VeriFactu affects your invoices

On paper, little changes; what changes is how the software works behind the scenes.

| | Before VeriFactu | With VeriFactu software |
| --- | --- | --- |
| Mandatory invoice details | Those in the Invoicing Regulation | The same, plus the QR code |
| Correcting a mistake | No specific technical requirements for the software | Corrective invoice, cancellation or correction record; the original record is kept |
| Numbering | Consecutive within each series | Consecutive within each series; each record is also chained by its hash |
| How you send it to the customer | PDF, paper or electronic | Unchanged: PDF, paper or electronic |
| Hacienda's checks | Tax returns, information filings and audits | The same, plus verifiable records and, in VERI*FACTU, records already sent |

### The three types of invoice under VeriFactu

Under VeriFactu, the three main types all generate a record:

- **Full (ordinary) invoice.** The usual one, with the details required by article 6 of the Invoicing Regulation.
- **[Simplified invoice](/blog/factura-simplificada)** (the receipt, or *ticket* as it is usually called in Spain). Under [article 4 of the Invoicing Regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696), it can be used, among other cases, when the amount is no more than 400 euros VAT included, when it is a corrective invoice, or up to 3,000 euros VAT included in certain sectors such as retail. Some transactions are excluded, such as intra-EU supplies of goods. The AEAT confirms in its [FAQs](https://sede.agenciatributaria.gob.es/Sede/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes/cuestiones-generales-ambitos-aplicacion.html) that receipts issued with software are also covered by VeriFactu.
- **Corrective invoice.** The one that corrects another. [Article 15 of the same regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696) requires it, for example, when the original does not meet some requirement or the VAT was calculated wrongly.

### What "invoice verification" means

In VERI*FACTU mode, the customer scans the QR code and the AEAT's website tells them whether it holds the record for that invoice. In non-VERI*FACTU mode, the answer "Factura no verificable" (invoice not verifiable) is normal and does not mean non-compliance, as the [AEAT's FAQs on the QR code](https://sede.agenciatributaria.gob.es/Sede/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes/posibilidad-remision-informacion-factura-parte-receptor.html) explain. Only if the invoice carries the VERI*FACTU label and, after a while, the check cannot find the record is it worth asking the supplier.

### And if your gestoría issues your invoices

You can ask a third party, such as a gestoría (tax and accounting firm), to issue your invoices. According to the [AEAT's FAQs](https://sede.agenciatributaria.gob.es/Sede/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes/cuestiones-generales-ambitos-aplicacion.html), if that third party uses an invoicing system, it is the one that generates the records when issuing them. But delegating does not let you off the hook: the obligation to invoice is still yours, so it is worth confirming that their software complies.

## Worked example: a day of invoicing under VeriFactu

Javier repairs computers in Seville. He mostly invoices private customers at his workshop and a few local businesses. He uses software in VERI*FACTU mode. To keep things simple, the example leaves out IRPF (income tax) withholding. He charges the standard 21% VAT ([article 90 of Law 37/1992](https://www.boe.es/buscar/act.php?id=BOE-A-1992-28740)).

**Step 1. A receipt in the morning.** A private customer pays for a cleaning and a thermal paste replacement on their computer. As it comes to less than 400 euros, Javier issues a simplified invoice, T-2026-118:

| Item | Amount |
| --- | --- |
| Taxable base | €50.00 |
| VAT at 21% | €10.50 |
| Total | €60.50 |

The software creates the issuance record, calculates its hash using the last record from the day before and sends it to the AEAT. The receipt comes out with a QR code and the word "VERI*FACTU".

**Step 2. A full invoice for a language school.** Javier sets up five computers for a language school. He issues F-2026-045:

| Item | Amount |
| --- | --- |
| Taxable base (5 computers x €60) | €300.00 |
| VAT at 21% | €63.00 |
| Total | €363.00 |

A new record, chained to the receipt's.

**Step 3. A mistake in the NIF.** The school gets in touch: one digit of its NIF is wrong. Correcting the recipient's NIF already required a corrective invoice before VeriFactu ([article 15 of the Invoicing Regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696)); what is new is that the software will not let him edit F-2026-045 and records the correction instead. He issues a corrective invoice, R-2026-004, which replaces the original with the right NIF, identifies F-2026-045 as the invoice it corrects and keeps its transaction date. The amounts do not change, but there is now a third record pointing to the corrected invoice.

**Step 4. A duplicate invoice.** In the afternoon, Javier checks the terminals at a clothes shop and invoices a taxable base of 120.00 euros. By mistake he issues the same invoice twice, F-2026-046 and F-2026-047. The second should never have existed and a corrective invoice does not apply, so the software generates a cancellation record for F-2026-047. F-2026-046 stands and F-2026-047 is cancelled, so the shop's VAT is only charged once:

| Item | Amount |
| --- | --- |
| Taxable base | €120.00 |
| VAT at 21% | €25.20 |
| Total | €145.20 |

This is the day's chain (hashes shortened and made up):

| Order | Record | Invoice | Previous hash | Own hash |
| --- | --- | --- | --- | --- |
| 1 | Issuance | T-2026-118 | 7c1e… | a3f9… |
| 2 | Issuance | F-2026-045 | a3f9… | 51d0… |
| 3 | Issuance (corrective) | R-2026-004 | 51d0… | e88b… |
| 4 | Issuance | F-2026-046 | e88b… | 0b47… |
| 5 | Issuance | F-2026-047 | 0b47… | 9a2c… |
| 6 | Cancellation | F-2026-047 | 9a2c… | c615… |

**What it means for the quarter's VAT.** From these transactions, Javier will declare as output VAT (the VAT he charges his customers) 10.50 euros from the receipt, 63.00 euros from the language school and 25.20 euros from the shop: 98.70 euros in total, on a taxable base of 470.00 euros. Corrective invoice R-2026-004 adds nothing, because it only changes the NIF, and the cancelled F-2026-047 does not count. The records sent match what he will declare.

![Output VAT for the day: 10.50 euros from the receipt, 63.00 euros from the language school and 25.20 euros from the shop add up to 98.70 euros on a taxable base of 470.00 euros. The corrective invoice and the cancelled invoice add nothing.](https://storage.googleapis.com/albert-489117-melso-blog-media/diagrams/en/que-es-verifactu/2-breakdown-dc3605adaf.png?w=1600&h=950&m=1&mw=1080&mh=1677 "Illustrative example. Standard 21% VAT, no IRPF withholding.")

> [!MELSO]
> Keeping corrective invoices, cancellations and the VAT you actually owe in order is exactly what gets complicated when you invoice on your own. Melso issues your invoices with your approval and keeps them alongside your income, your expenses and your upcoming taxes: see [Melso invoicing](/en/facturas).

## Who VeriFactu applies to and when it becomes mandatory

The AEAT sums up who is required to comply with its "rule of the 4 NOs" in its [FAQs](https://sede.agenciatributaria.gob.es/Sede/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes/cuestiones-generales-ambitos-aplicacion.html). It applies to you if:

![VeriFactu applies to you if you issue invoices with software, you are not on the SII and you are not taxed under the foral rules of the Basque Country or Navarre, unless the AEAT has exempted you by a resolution.](https://storage.googleapis.com/albert-489117-melso-blog-media/diagrams/en/que-es-verifactu/3-decision-3a2b54e9d4.png?w=1600&h=1868&m=1&mw=1080&mh=2979 "Does VeriFactu apply to you?")

1. You do **not** invoice only by hand. If you use an invoicing software system (SIF) as defined in the regulation, you are in. A Word or Excel file used only to type, print and save invoices does not count, according to the same AEAT page.
2. You are **not** on the SII (Suministro Inmediato de Información, Immediate Supply of Information), which sends the VAT books in near real time. According to the [AEAT](https://sede.agenciatributaria.gob.es/Sede/ayuda/manuales-videos-folletos/manuales-practicos/folleto-actividades-economicas/5-impuesto-sobre-valor-anadido/5_11-suministro-inmediato-informacion/5_11_1-quien-se-aplica.html), it is mandatory for:
   - large companies;
   - VAT groups;
   - businesses on the REDEME (the register for monthly VAT refunds);
   - certain holders of tax warehouses for fuels and those who take those fuels out of the warehouses.

   For everyone else it is voluntary.
3. You are **not** taxed under the foral rules of the Basque Country or Navarre. In the Basque Country, TicketBAI applies, under the rules of each provincial council (diputación).
4. You do **not** have an AEAT resolution exempting you.

The Canary Islands, Ceuta and Melilla are included, with IGIC or IPSI instead of VAT.

When it comes to the date, it pays to separate what is confirmed from what has only been announced:

![VeriFactu dates: the original text set July 2025; Royal Decree 254/2025 moved them to January and July 2026; Royal Decree-law 15/2025 set 1 January 2027 for companies and 1 July 2027 for everyone else; in October 2026 Hacienda announced a delay to October 2028 that is not yet in the BOE.](https://storage.googleapis.com/albert-489117-melso-blog-media/diagrams/en/que-es-verifactu/4-timeline-01dec90d19.png?w=1600&h=892&m=1&mw=1080&mh=2040 "From July 2025 to the date in force in 2027")

| Situation | Source | Date | Status as of 12 October 2026 |
| --- | --- | --- | --- |
| Companies (paying Corporate Income Tax) | [Royal Decree-law 15/2025, first final provision](https://www.boe.es/buscar/doc.php?id=BOE-A-2025-24446) | 1 January 2027 | In force |
| Everyone else, including the self-employed | [Royal Decree-law 15/2025, first final provision](https://www.boe.es/buscar/doc.php?id=BOE-A-2025-24446) | 1 July 2027 | In force |
| Hacienda announcement | [Information note of 5 October 2026](https://www.hacienda.gob.es/sgt/gabsehacienda/nota-informativa-verifactu.pdf) | October 2028 | Planned, no rule in the BOE |

The Ministry of Finance's note says it will proceed with "postponing the obligations of Royal Decree 1007/2023 still pending application [...] until October 2028", to make them coincide with e-invoicing for businesses and professionals "whose annual turnover does not exceed 8 million euros". It also warns that the integrity, preservation, traceability and unalterability requirements will be kept "in substantially equivalent terms".

> [!IMPORTANTE]
> A press note does not change a rule. As of 12 October 2026, the consolidated text of the regulation in the BOE still sets 1 July 2027 for the self-employed: plan around that date.

The delay will only take effect when the rule changing the deadlines in Royal Decree 1007/2023 comes into force, which could be a royal decree or a royal decree-law, as already happened with [Royal Decree-law 15/2025](https://www.boe.es/buscar/doc.php?id=BOE-A-2025-24446). Until then, the fourth final provision of the [consolidated text of the regulation](https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840) applies, in the wording given to it by that royal decree-law. Do not confuse it with [Order HAC/1028/2026](https://www.boe.es/buscar/doc.php?id=BOE-A-2026-20587), published in the BOE on that same 5 October: that order is in force, but it regulates e-invoicing between businesses, not VeriFactu. You will find every date and its history in [when does VeriFactu start](/en/blog/when-does-verifactu-start-spain).

If you want to get started now without paying, the AEAT offers a [free invoicing app](https://sede.agenciatributaria.gob.es/Sede/ayuda/consultas-informaticas/presentacion-declaraciones-ayuda-tecnica/aplicacion-gratuita-verifactu-aeat.html) in VERI*FACTU mode, with no limit on invoices. Be aware, according to that same AEAT page: it does not issue receipts, allows only one recipient per invoice and does not let you export the records to other software.

## What happens if you do not comply

[Article 201 bis of the General Tax Law](https://www.boe.es/buscar/act.php?id=BOE-A-2003-23186) sets out the offences, all of them serious:

| Who | What is penalised | Fine |
| --- | --- | --- |
| Whoever uses the software | Having software that does not comply when it is not certified and should be, or whose certified devices have been altered (section 2) | Flat €50,000 per tax year |
| Whoever makes or sells it | Software that allows records to be hidden or altered, or that does not meet the specifications (section 1) | €150,000 per tax year with sales and per type of software |
| Whoever makes or sells it | Selling software without the mandatory certification | €1,000 per program sold |

For you, as a user, the obligation starts on the date that applies to you.

> [!CONSEJO]
> Before signing up for any software, ask for its declaración responsable (statement of compliance): the document in which the manufacturer declares that it complies with Royal Decree 1007/2023 and Order HAC/1177/2024. Article 13 of the regulation requires the manufacturer to issue it; your job is to check that it exists.

## VeriFactu, TicketBAI, SII and e-invoicing: the differences

These are four things that often get mixed up:

| | What it governs | Who it applies to | Date |
| --- | --- | --- | --- |
| VeriFactu | The software that issues the invoice | Anyone invoicing with software in the common tax territory | July 2027 in force for the self-employed |
| TicketBAI | The same, in the Basque Country | Basque foral taxpayers | Each provincial council's own calendar |
| SII | The VAT record books, sent in near real time | Large companies, VAT groups, REDEME, certain holders of fuel tax warehouses, those who take fuels out of them and anyone who opts in | Already running |
| B2B e-invoicing | The format and exchange between businesses | Businesses and professionals invoicing other businesses in Spain, with exceptions such as most simplified invoices | 6 October 2028 for most |

[Royal Decree 238/2026](https://www.boe.es/eli/es/rd/2026/03/25/238/con) sets the scope and exceptions (articles 3 and 4) and the deadlines (fourth final provision): 12 months from the ministerial order coming into force for anyone whose turnover (calculated under article 121 of the VAT Law) exceeded 8 million euros in the previous calendar year, and 24 months for everyone else. That order is [Order HAC/1028/2026](https://www.boe.es/buscar/doc.php?id=BOE-A-2026-20587), published in the BOE on 5 October 2026 and in force since the following day. The resulting dates, 6 October 2027 and 6 October 2028, are confirmed by the [AEAT](https://sede.agenciatributaria.gob.es/Sede/todas-noticias/2026/octubre/7/solucion-publica-facturacion-electronica.html). It is all explained in [mandatory e-invoicing](/en/blog/mandatory-e-invoicing-spain).

## Common mistakes

- **Thinking VeriFactu forces you to send e-invoices.** It does not. You can still send a PDF or a paper invoice. The software changes, not the channel.
- **Assuming it is already October 2028.** That is a Hacienda announcement. Until it appears in the BOE, the legal date for the self-employed is 1 July 2027.
- **Working from old dates.** The original text set July 2025, and [Royal Decree 254/2025](https://www.boe.es/buscar/doc.php?id=BOE-A-2025-6600) moved it to January and July 2026. Royal Decree-law 15/2025 pushed those dates back a year.
- **Deleting an invoice you got wrong.** Under VeriFactu you correct it with a corrective invoice or, if it should never have existed and a corrective invoice does not apply, with a cancellation record. The original record never disappears.

## How Melso helps

Melso is your AI tax agent, with human professionals behind it: an online gestoría (tax and accounting firm) for the self-employed that works with you over WhatsApp. Melso issues your invoices only with your approval (see how in [invoicing](/en/facturas)). The returns included for your activity and tax profile are prepared and reviewed by Melso and its professionals, you approve the exact draft in the app and, with the necessary authorisation, the professional files the approved version with the AEAT. See the plans on [pricing](/en/pricing) and [get started at melso.ai](https://melso.ai) or tap **Message us on WhatsApp**.

> This article is for information only and does not replace professional advice for your case. Last reviewed: 12 October 2026.

## Frequently asked questions

### What is VeriFactu?

VeriFactu is the popular name for Spain's Regulation on invoicing software systems, approved by Royal Decree 1007/2023. It requires the software you invoice with to create, at the moment each invoice is issued, a chained record that cannot be deleted or altered without leaving a trace. In VERI*FACTU mode, the software also sends every record to the Agencia Tributaria (the AEAT, Spain's tax agency).

### How does VeriFactu work?

When you issue an invoice, the software generates an invoicing record with your NIF (tax ID), the invoice number, the date and the amounts. It calculates a digital fingerprint (hash) with the SHA-256 algorithm that includes the hash of the previous record, so every record is chained to the last. The invoice carries a QR code and, in VERI*FACTU mode, the record is sent to the AEAT automatically.

### What is the difference between a VERI*FACTU and a non-VERI*FACTU system?

A VERI*FACTU system sends every invoicing record to the AEAT as the invoices are issued, so it faces fewer internal requirements: it does not have to sign the records. A non-VERI*FACTU system keeps them on your computer or in the cloud, must sign them electronically, keep an event log and hand them to the AEAT when asked.

### When does VeriFactu become mandatory?

As of 12 October 2026, the legal date is 1 January 2027 for companies and 1 July 2027 for everyone else, including the self-employed. It was set by Royal Decree-law 15/2025 of 2 December (BOE-A-2025-24446), which amended Royal Decree 1007/2023. On 5 October 2026 Hacienda (the Ministry of Finance) announced in a press note that it will push those dates back to October 2028, but that delay needs a new rule that has not yet been published in the BOE, Spain's official gazette.

### Does VeriFactu apply to simplified invoices or receipts?

Yes. If you issue receipts with invoicing software, each simplified invoice generates its own record just like a full invoice, carries its QR code and, in VERI*FACTU mode, is sent to the AEAT, as the Agencia Tributaria's FAQs confirm. A simplified invoice can be used, among other cases, up to 400 euros or, in certain sectors, up to 3,000 euros, VAT included (article 4 of the Invoicing Regulation).

### Can I change an invoice issued under VeriFactu?

The original record is never altered. If the mistake requires a correction under the Invoicing Regulation, you issue a corrective invoice (factura rectificativa) with its own record. If the invoice should never have been issued, for example because you duplicated it, and a corrective invoice does not apply, a cancellation record is generated. If the error is only in the record's data, a correction record (subsanación) is generated. Other mistakes do not generate a new record.

### What is the QR code on VeriFactu invoices for?

In VERI*FACTU mode, the QR code lets whoever receives the invoice check on the AEAT's website that its record was sent. In non-VERI*FACTU mode it lets the recipient report the details to the AEAT, but the invoice is not verifiable. It measures between 30x30 and 40x40 millimetres (Order HAC/1177/2024). On a structured e-invoice it is enough to include the QR code's URL as a field.

### What is the fine for not complying with VeriFactu?

Under article 201 bis of the General Tax Law (Ley General Tributaria), having software that does not comply with the rules and is not certified when it should be, or whose certified devices have been altered, carries a flat fine of 50,000 euros per tax year. Whoever makes or sells software that allows records to be altered or does not meet the specifications pays 150,000 euros per tax year with sales and per type of software.

### Is VeriFactu the same as mandatory e-invoicing?

No. VeriFactu governs the software you issue each invoice with, so records cannot be altered. Mandatory e-invoicing requires businesses and professionals to exchange the invoices between them in a structured format, with exceptions such as most receipts. For most of the self-employed it starts on 6 October 2028: 24 months after Order HAC/1028/2026, already published in the BOE, under Royal Decree 238/2026.

### Does VeriFactu apply to me if I do my invoices in Excel?

It depends on how you use it. According to the AEAT, a spreadsheet used only to type, print and save invoices is not an invoicing system. If it also produces the invoice register, the accounts or other tax results, for example with macros, it is one, and it will have to comply with the VeriFactu regulation when your date arrives.

## Sources

- [Royal Decree 1007/2023 of 5 December (Regulation on invoicing software systems), consolidated text](https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840), BOE, accessed 2026-10-12
- [Royal Decree-law 15/2025 of 2 December (amends the deadlines in Royal Decree 1007/2023)](https://www.boe.es/buscar/doc.php?id=BOE-A-2025-24446), BOE, accessed 2026-10-12
- [Order HAC/1177/2024 of 17 October (technical specifications for invoicing systems)](https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138), BOE, accessed 2026-10-12
- [Law 58/2003 of 17 December, General Tax Law (articles 29.2.j and 201 bis), consolidated text](https://www.boe.es/buscar/act.php?id=BOE-A-2003-23186), BOE, accessed 2026-10-12
- [Royal Decree 1619/2012 of 30 November (Invoicing Regulation), consolidated text](https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696), BOE, accessed 2026-10-12
- [Law 37/1992 of 28 December on Value Added Tax (article 90)](https://www.boe.es/buscar/act.php?id=BOE-A-1992-28740), BOE, accessed 2026-10-12
- [Information note of 5 October 2026: planned change to the deadlines in Royal Decree 1007/2023](https://www.hacienda.gob.es/sgt/gabsehacienda/nota-informativa-verifactu.pdf), Ministerio de Hacienda, accessed 2026-10-12
- [SIF and VERI*FACTU FAQs: general questions and scope of application](https://sede.agenciatributaria.gob.es/Sede/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes/cuestiones-generales-ambitos-aplicacion.html), AEAT, accessed 2026-10-12
- [The AEAT's free VERI*FACTU invoicing app](https://sede.agenciatributaria.gob.es/Sede/ayuda/consultas-informaticas/presentacion-declaraciones-ayuda-tecnica/aplicacion-gratuita-verifactu-aeat.html), AEAT, accessed 2026-10-12
- [Royal Decree 238/2026 of 25 March (mandatory e-invoicing between businesses and professionals), consolidated text](https://www.boe.es/eli/es/rd/2026/03/25/238/con), BOE, accessed 2026-10-12