Perspectives · Spain
Spain postponed VERI*FACTU. The control problem did not move.
Spain has extended the deadlines for adapting billing systems under the SIF and VERI*FACTU rules. Corporate Income Tax entities must be ready before 1 January 2027; most other affected taxpayers must be ready before 1 July 2027. The one-year postponement creates time, but it does not simplify the underlying control over billing records, software and entity identity. This perspective is general information, not Spanish tax or legal advice.
The delay
One year is an implementation window, not a cancellation
The new dates remove the immediate 2026 go-live pressure, but they also create a risk: a programme is paused because the deadline feels distant, then restarted with the same unresolved scope and data problems.
The better use of 2026 is controlled rehearsal. Identify affected entities, confirm which billing systems they use, understand whether those systems will operate in VERI*FACTU mode or another compliant mode, and test the events that are more difficult than a standard invoice: corrections, cancellations, credit notes, series changes and delegated billing.
The choice
VERI*FACTU is an operating model, not only a software feature
A VERI*FACTU system sends billing records to the Spanish Tax Agency as they are generated, creating a verifiable chain and enabling the customer-facing verification features. A non-VERI*FACTU compliant system retains the records itself under integrity, traceability, preservation and accessibility requirements.
The choice affects more than procurement. It determines the evidence model, outage procedure, permissions, reconciliation and how quickly the tax team can investigate a disputed record. Once an entity begins systematic VERI*FACTU submission, the operating choice should be managed deliberately rather than changed informally by a local user.
The distinction
VERI*FACTU is not the same reform as mandatory B2B e-invoicing
Spain's billing-system rules and the separate B2B electronic-invoicing reform are related but distinct. One governs how billing records are created, protected or sent to the tax authority; the other governs the format and exchange of invoices between businesses.
A group may eventually use the same vendor or data layer for both, but it should maintain separate scope, legal basis, dates and acceptance criteria. Combining them into one vague "Spain e-invoicing" project makes it harder to know which obligation has actually been completed.
The test year
Rehearse with real entity data while change is still cheap
Testing should use representative entities, not only the largest Spanish company. Include a holding company with few invoices, an operating company with high volume, an entity using self-billing or a third party, and an entity expected to merge or liquidate before 2027.
The test should also begin from the legal master data: NIF, registered name, establishment status, addresses, invoice series, authorised users and service-provider mandates. If those fields are wrong, a technically compliant billing system can still produce a poor record.
In Alethia
Use 2026 to clean the entity layer around the billing systems
Alethia is not billing software and does not submit VERI*FACTU records. It can provide the portfolio control: which Spanish entities are in scope, which system and operating mode each uses, who owns the implementation, what evidence has been obtained and which corporate event may change the answer.
That lets the tax and finance programme follow entity reality. A sale, merger, liquidation, name change or service-provider switch can trigger a review before it creates an invoice exception.
Questions
Spain's revised VERI*FACTU timetable, answered
What are the new deadlines?
Entities that file Corporate Income Tax must adapt their billing systems before 1 January 2027. Most other affected taxpayers must adapt before 1 July 2027.
Does the postponement prevent voluntary testing in 2026?
No. The Tax Agency provides information and test capability ahead of the mandatory dates. A controlled pilot can expose data, integration and process gaps while remediation is still manageable.
Is VERI*FACTU the same as Spain's B2B electronic-invoicing mandate?
No. They are separate reforms with different legal and technical requirements, even if a company's implementation architecture eventually connects them.
Use the postponement to remove the operating risk
Map every entity, billing system, owner and exception in 2026 so the 2027 deadline becomes a deployment date rather than a discovery exercise.