
These are two different obligations. Veri*Factu governs how the software generates and stores invoices: companies must adapt it before 1 January 2027 and everyone else before 1 July. Business-to-business e-invoicing governs how invoices are sent, and arrives in 2027 or 2028. The Ministry of Finance (Hacienda) plans to postpone Veri*Factu to October 2028 (not yet law).
We declare our interest: BDR Group implements and supports Odoo, which includes invoicing. The rules are Spanish; if you are in Andorra, we cover that at the end.
Veri*Factu and e-invoicing are not the same thing
Veri*Factu is the name of the system that comes from Real Decreto 1007/2023 of 5 December (a royal decree on the requirements for invoicing computer systems). Mandatory e-invoicing between businesses and professionals comes from Article 12 of Ley 18/2022 of 28 September on the creation and growth of businesses (the Crea y Crece Act), developed by Real Decreto 238/2026 of 25 March. They get confused because they arrive at the same time and both go through the Spanish Tax Agency (AEAT), but they answer different questions.
| Veri*Factu | B2B e-invoicing | |
|---|---|---|
| What it regulates | How the software generates, stores and protects invoicing records | How an invoice is issued, sent and received between businesses |
| Visible change | QR code on the invoice and the till receipt | Invoice in a structured format, not a PDF |
| Current timetable | 1/1/2027 for companies; 1/7/2027 for everyone else | October 2027 (over 8 million euros) and October 2028 (everyone else) |
Veri*Factu timetable as at 25 October 2026
Real Decreto-ley 15/2025 of 2 December (a royal decree-law; BOE, Spain’s official gazette, of 3 December 2025) postponed the dates by a year. Entities that file Corporate Income Tax returns must have the system adapted before 1 January 2027; all other covered taxpayers, before 1 July 2027. Software producers must offer adapted products within nine months of the entry into force of the technical ministerial order, Orden HAC/1177/2024 (29 October 2024). By our calculation, that deadline ended on 29 July 2025.
On 5 October 2026, Hacienda published a note with a "forecast of amendment" of the deadlines: it wants to align Veri*Factu with e-invoicing for SMEs and the self-employed and postpone the pending obligations until October 2028. It adds that the requirements on integrity, retention, traceability and inalterability will remain in substantially equivalent terms.
This is an announcement, not a rule. As at 25 October 2026 we have not found any published provision that changes the dates, and the AEAT page (updated on 13 October) still shows 1 January and 1 July 2027. For planning, the date in force is the 2027 one; the postponement is a scenario to follow until it appears in the BOE.
Who is covered by Veri*Factu and who is not
Article 3.1 of Real Decreto 1007/2023 covers Corporate Income Tax taxpayers, personal income tax (IRPF) taxpayers with economic activities, Non-Resident Income Tax taxpayers with a permanent establishment and entities under the income attribution regime that carry on an economic activity. It also covers the producers and distributors of the software (Article 3.2).
Excluded, according to the regulation and the AEAT leaflet:
- Anyone who keeps their VAT record books through the Immediate Supply of Information system (SII), excluded by Article 3.3.
- Taxpayers whose tax domicile is in the Basque Country or Navarre, which fall under foral (regional) rules.
- Entities fully exempt under Article 9.1 of Ley 27/2014 (the Corporate Income Tax law); partially exempt ones are covered only for operations that generate taxable, non-exempt income.
Catalonia has no regime of its own: it is common-regime territory and the state regulation applies. We have not found any Generalitat rule that modifies this, or any exception by size: a micro-business or a self-employed person who invoices with a program is covered, with the deadline of 1 July 2027 if they are not a Corporate Income Tax taxpayer. Nor is it only about sales between businesses: the AEAT leaflet includes till receipts, so a shop with a point-of-sale terminal is covered too.
What it requires of the software
The regulation does not oblige anyone to send anything to Hacienda: it requires the program to guarantee that records cannot be altered without leaving a trace. For each invoice, the system generates a record at the moment of issue, chains it to the previous one through a hash (a fingerprint), stores it in an accessible and legible form, and logs events. Corrections are made with additional records, not by modifying the originals (Articles 8 to 12). The invoice also carries a QR code.
The business chooses between two modes, and the choice is voluntary:
- Veri*Factu: the system sends every record to the AEAT continuously and in full. The invoice carries the QR code and the legend "Factura verificable en la sede electrónica de la AEAT" or "VERI*FACTU", and the customer can verify it. The hash is enough, with no electronic signature (Article 16).
- Non-verifiable system: nothing is sent, and the program has to ensure inalterability by itself, with an electronic signature on the records.
The technical specifications are in Orden HAC/1177/2024 of 17 October. The producer must issue a responsible declaration (declaración responsable) stating that the system complies with the regulation, and must be able to show it to customers (Article 13). For small businesses and the self-employed, the AEAT offers a free application on its electronic office.
The most visible penalty is aimed at producers: Article 201 bis of the General Tax Act (Ley General Tributaria) sets 150,000 euros per financial year and per type of system for manufacturing or selling programs that do not comply. What happens to someone who merely uses one is a question for your tax adviser.
B2B e-invoicing: what the rule says now
The Crea y Crece Act established that all businesses and professionals must issue, send and receive electronic invoices between themselves, and left the timetable for when the regulation was approved. It has now been approved: Real Decreto 238/2026, published in BOE no. 79 of 31 March 2026. Effective application is counted from the entry into force of the order on the public e-invoicing solution, Orden HAC/1028/2026 of 2 October (BOE of 5 October), in force since 6 October 2026.
The fourth final provision of the decree sets 12 months from that order for those that exceeded 8 million euros of operations the previous year, and 24 months for everyone else. That puts the dates at October 2027 and October 2028 (this is our calculation; the rule does not write the dates).
What changes in practice:
- Format: a structured message following the European model EN16931, in CII, UBL, EDIFACT or Facturae syntax. A PDF stops being the invoice. During the first twelve months, businesses with more than 8 million must accompany it with a readable PDF.
- Ways of sending: a private platform or the AEAT’s public solution, which is free and in UBL. Private platforms send a faithful copy to the AEAT and sign with an advanced electronic signature.
- Invoice statuses: the recipient must report acceptance or rejection and full payment within a maximum of 4 calendar days (not counting weekends or public holidays). The law wants reliable information on payment periods and aims to combat late payment.
- Exclusions: simplified invoices, with exceptions, and some other operations, such as those in the electricity market.
What to do about your invoicing software
The first step is to know what you use: the ERP, a stand-alone invoicing program, the point-of-sale terminal, a tool in the online shop. Every component that issues invoices can be an invoicing computer system. Then ask the supplier in writing whether the product has the responsible declaration, which mode it supports and in which version.
If you work with Odoo, the official Odoo 18 documentation for Spain describes one Veri*Factu module for invoicing and another for the point of sale, which are installed manually, require an electronic certificate and add the QR code to the PDF. It also warns that it starts in test mode, with data that has no official validity until that mode is switched off. This describes standard Odoo: the version, the modules and the customisations determine what each installation has, and it is checked project by project. The same goes for any other program.
The October 2028 announcement invites waiting, but the producers’ deadline has already passed: asking the supplier does not depend on any postponement.
If you are in Andorra
Veri*Factu and B2B e-invoicing are Spanish rules. An Andorran company with no permanent establishment in Spain is not a Spanish taxpayer and is not subject to them just because it is Andorran. If it has one, or invoices customers in Spain, check with your adviser. We do not analyse the Andorran case here.
What to do now
- List every system you issue invoices or till receipts with.
- Check whether you are on the SII or under a foral regime: in that case Veri*Factu does not affect you.
- Ask each supplier for the responsible declaration, the mode and the adapted version, and keep the reply.
- Decide whether the verifiable or the non-verifiable mode suits you, and try it with invoices in a test environment.
- Check the BOE and the AEAT before fixing dates, and discuss it with your tax adviser.
Frequently asked questions
Does Veri*Factu oblige me to send invoices to Hacienda?
No. The obligation is for the program to generate unalterable records. Sending them is the Veri*Factu mode, which is voluntary.
Is a micro-business or a self-employed person covered?
Yes, if they issue invoices with a computer system and are not on the SII or under a foral regime. The deadline is 1 July 2027 for those who are not Corporate Income Tax taxpayers.
Will the dates change?
On 5 October 2026 Hacienda announced that it wants to postpone the pending Veri*Factu obligations until October 2028. Until the rule is published, 1 January and 1 July 2027 are in force.
Will a PDF invoice stop being valid?
For invoices between businesses, the PDF stops being the invoice once the obligation applies, because the invoice has to be structured. With Veri*Factu, however, the invoice can still be a PDF with a QR code.
Sources
- Ministerio de Hacienda y Función Pública. Real Decreto 1007/2023, de 5 de diciembre, por el que se aprueba el Reglamento que establece los requisitos que deben adoptar los sistemas y programas informáticos de facturación, Articles 1, 3, 4, 7 to 17 and fourth final provision (in Spanish). BOE of 6 December 2023. Accessed: 25 October 2026. https://www.boe.es/buscar/act.php?id=BOE-A-2023-24840
- Jefatura del Estado. Real Decreto-ley 15/2025, de 2 de diciembre (in Spanish). BOE no. 290, 3 December 2025. Accessed: 25 October 2026. https://www.boe.es/buscar/act.php?id=BOE-A-2025-24446
- Ministerio de Hacienda. Orden HAC/1177/2024, de 17 de octubre (in Spanish). BOE no. 260, 28 October 2024. Accessed: 25 October 2026. https://www.boe.es/buscar/act.php?id=BOE-A-2024-22138
- Ministerio de Hacienda. Previsión de modificación de los plazos de aplicación de las obligaciones pendientes derivadas del Reglamento de sistemas informáticos de facturación (RD 1007/2023) y convergencia con el sistema de factura electrónica. Press Office information note, 5 October 2026 (in Spanish). Accessed: 25 October 2026. https://www.hacienda.gob.es/sgt/gabsehacienda/nota-informativa-verifactu.pdf
- Agencia Tributaria. Billing Computer Systems (SIF) and VERI*FACTU (English version of the page, updated on 13 October 2026) and information note on the extension of the deadline. Accessed: 25 October 2026. https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/sistemas-informaticos-facturacion-verifactu.html
- Agencia Tributaria. Folleto VERI*FACTU (leaflet; in Catalan and Spanish). Accessed: 25 October 2026. https://sede.agenciatributaria.gob.es/static_files/Sede/Biblioteca/Folleto/VERIFACTU/Folleto_VERIFACTU_ca_es.pdf
- Jefatura del Estado. Ley 18/2022, de 28 de septiembre, de creación y crecimiento de empresas, Article 12 and eighth final provision (in Spanish). BOE no. 234, 29 September 2022. Accessed: 25 October 2026. https://www.boe.es/buscar/act.php?id=BOE-A-2022-15818
- Ministerio de la Presidencia, Justicia y Relaciones con las Cortes. Real Decreto 238/2026, de 25 de marzo, por el que se desarrolla el sistema de facturación electrónica obligatoria entre empresarios y profesionales (in Spanish). BOE no. 79, 31 March 2026. Accessed: 25 October 2026. https://www.boe.es/eli/es/rd/2026/03/25/238/con
- Ministerio de Hacienda. Orden HAC/1028/2026, de 2 de octubre, sobre la solución pública de facturación electrónica (in Spanish). BOE no. 247, 5 October 2026. Accessed: 25 October 2026. https://www.boe.es/buscar/doc.php?id=BOE-A-2026-20587
- Jefatura del Estado. Ley 58/2003, de 17 de diciembre, General Tributaria, Article 201 bis (consolidated text; in Spanish). Accessed: 25 October 2026. https://www.boe.es/buscar/act.php?id=BOE-A-2003-23186
- Odoo. Odoo 18 documentation, Spain fiscal localisation (Veri*Factu). Accessed: 25 October 2026. https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/spain.html
Want to review your invoicing software?
If you want to review how you invoice and what should change, start with the Odoo service page: Odoo ERP for businesses in Catalonia and the rest of Spain. For a company in Andorra, the specialist website is erpandorra.ad.



