Spain's Ministry of Finance has announced that it plans to move pending VERI*FACTU obligations to October 2028, but the announcement of 5 October 2026 is not, in itself, an approved change to the law. If you invoice using software, you need to tell apart the legal calendar, the political forecast and your technical readiness before changing provider or stopping a rollout. This guide is for businesses and freelancers who issue invoices in Spain, including foreign companies and expats operating there.
What did the Ministry of Finance announce, and which dates are still in force?
The note from Spain's Ministry of Finance, dated 5 October 2026, expressly speaks of a planned change to the deadlines. It proposes postponing until October 2028 certain pending obligations of the Regulation on invoicing computer systems, with the aim of bringing its calendar closer to that of business-to-business electronic invoicing. It does not state that the change has already been published in the official gazette (the BOE).
This nuance matters. A company should not reorganise its tax obligations on the basis of a headline that treats a still-announced change as approved. The Spanish Tax Agency (AEAT) keeps a published note with the adaptation deadlines arising from Royal Decree-law 15/2025: 1 January 2027 for entities that file Corporate Income Tax and 1 July 2027 for the other affected taxpayers. Until a later rule changes that framework, those are the dates to check with your tax adviser. Source: AEAT note on deadlines, accessed on 09/10/2026.
The ministry's own note says it intends to keep, in substantially equivalent terms, the guarantees of integrity, retention, accessibility, legibility, traceability and inalterability of the records. Therefore the idea that "VERI*FACTU is being cancelled" is not supported by the official documentation consulted.
Imagine an accountancy practice that is already migrating its invoices from an old program. Its provider sends an email saying it can now wait two years. Before putting the brakes on, it is worth asking in writing which part of the project depends on the legal deadline and which part solves problems the practice already had: duplicates, numbering, reconciliation or finding documents.
Source: Communication from the Ministry of Finance, 05/10/2026. Accessed: 09/10/2026.
How does VERI*FACTU differ from electronic invoicing?
They are not synonyms. VERI*FACTU is one mode of the invoicing computer systems regulated by Royal Decree 1007/2023. In that mode, the system sends invoicing records to the Tax Agency in line with the applicable specifications. There is also a non-VERI*FACTU system mode, with different retention and control requirements.
Electronic invoicing between businesses and professionals, by contrast, refers to the format and exchange of invoices in commercial relationships. The fact that both projects are related, and that the Ministry proposes bringing their calendars closer, does not turn their technical obligations into one.
In practice, a small business can have three different problems. The first is issuing invoices correctly. The second is keeping records and traces in line with the applicable rules. The third is exchanging electronic invoices with other operators where relevant. Buying a program that promises to "comply with everything" does not replace checking exactly what it covers.
The Tax Agency publishes frequently asked questions and technical documentation on invoicing systems. It is best to start from that information, not from undated commercial comparisons. An integration between sales and accounting, for example, can pass on order data, but that does not by itself prove that the final system complies with the regulation.
Source: Official FAQ on VERI*FACTU systems (in Spanish). Accessed: 09/10/2026.
What should you check in your invoicing software?
The useful question is not "does my program put VERI*FACTU on its home page?", but what it does with each invoice and what evidence it leaves. Ask the provider for a specific description of how it operates, its adaptation documentation and its update plan.
Review these points with whoever handles administration and with your tax adviser:
- Numbering and series. How they are assigned, what happens if an operation fails and how corrections are documented.
- Event log. Which actions are traced and who can consult them.
- Export. Whether you can recover invoices, customers and records in usable formats when you change tool.
- Permissions. Who can create, correct, consult or download information.
- Continuity. Which procedure is followed if the internet or the service goes down.
- Integrations. How shop, CRM, point of sale and accounting connect without generating duplicate invoices.
Do not accept as your only answer a commercial screenshot with a compliance badge. Ask for technical documentation, contractual terms and the scope of the adaptation. If your company uses several programs that take part in invoicing, identify which one actually issues the invoice and which only supplies data.
A common mistake is to confuse automating the transfer of information with automating a tax decision. An order having an amount does not always determine by itself how the invoice must be issued. There are corrections, different regimes and circumstances that require tested rules and professional review.
Is it worth automating invoicing while the deadlines change?
It can be, but because of the operational problem it solves, not out of fear of a date. If someone copies order data to a spreadsheet every afternoon, then re-enters it in the invoicing program and finally sends a manual email, there is a process that can be simplified.
Start by drawing the real journey. Where does the data originate? Who validates it? Which system creates the document? Where is it stored? What happens if the customer changes their address or the order is cancelled? The answer reveals more than a software demonstration with a perfect invoice.
A prudent workflow could receive an order, check that it contains the necessary fields, leave it ready for validation and record the result of issuing. The automation can detect duplicates and flag incidents. It should not invent missing tax data nor hide errors to keep up an appearance of automatic operation.
The saving in administrative work is a hypothesis that is measured after rollout. Before that, record how many interventions each invoice needs, which exceptions appear and how long the team takes to resolve them. You do not need to promise percentages to decide whether the process is worth studying.
Nor does everything have to change at once. A pilot with a limited set of operations lets you observe errors, design retries and agree who authorises the move to production. If your current tool already works, an integration may be enough; at other times the problem is in the system itself and requires replacement.
How do you prepare a migration without blocking the business?
An invoicing migration affects information that you need to keep and consult. The plan must include inventory, tests, owners and a way back. Make a verifiable copy of the data before transforming formats or replacing the program.
Split the project into three stages. First, document the series, customers, historical documents and active connections. Second, test a circuit with normal cases and exceptions: a return, a corrective invoice, a network failure, a customer missing a mandatory field. Third, validate with your tax adviser how each scenario is treated and agree a cut-off date.
Pay attention to access. An integration account with excessive permissions can modify information it should not touch. A file exported to a shared folder can leave customer data exposed. Security is not an afterthought; it is part of the design.
Before signing, ask who is responsible if an update fails, how records are recovered and what happens when the contract ends. Vendor dependence is reduced when the data can be exported, the integrations are documented and the business keeps control of its credentials.
Do not confuse a longer calendar with unlimited time. The messier the current process, the more testing any change will need. Preparing with a margin reduces the pressure of deciding in a hurry.
How have we approached it at meiika?
At meiika we work on custom systems starting from the flow of information and the decisions a company needs to control. In invoicing, that means separating the business process from the tax obligations and not presenting an integration as legal certification.
We can study how orders, customer records, approvals and existing tools relate to each other. The specific tax compliance must be validated with the system provider and with competent professionals. We do not claim to have an officially approved tax product, nor do we promise that automation will replace your tax adviser's review.