Spain is in the middle of the most significant change to business invoicing in a generation, and it is arriving in two waves that are routinely mistaken for one. Both have now slipped, which has produced a second mistake to sit alongside the first: founders who conclude that because nothing binds them today, nothing needs doing. The work these rules require is software and process work, and it does not compress into the last month.
The distinction matters because the two regimes have different legal sources, different affected parties, different technical requirements and different penalties. A typical Spanish company will end up complying with both, in parallel, on separate timetables.
The two obligations, side by side.
From January 2027
Verifactu — how your software must behave
Your billing system must produce records that are traceable, unalterable and verifiable by the tax authority. It governs the software, and it applies to invoices you issue to anyone, including consumers. Source: anti-fraud legislation and its implementing regulation.
Clock not yet running
B2B e-invoicing — how invoices are exchanged
Invoices between businesses and professionals must be issued and received in a structured electronic format, with status reporting. It governs the exchange, and it applies only to B2B. Source: Ley 18/2022 "Crea y Crece", developed by Real Decreto 238/2026.
| | Verifactu | B2B e-invoicing |
| What it regulates | Your invoicing software and its records | The format and exchange of B2B invoices |
| Who is covered | Companies and autonomos issuing invoices | Businesses and professionals, B2B transactions |
| Applies to B2C? | Yes | No |
| Companies from | 1 January 2027 | 12 months after the ministerial order, above €8M turnover |
| Autonomos and the rest from | 1 July 2027 | 24 months after the ministerial order |
| Who is out of scope | Companies already under the SII, and the Basque Country under TicketBAI | B2C invoicing entirely |
| Core requirement | Unalterable, traceable, hashed records; optional real-time submission to the AEAT | Structured format, delivery, and reporting of invoice status |
| Reported penalty exposure | Up to €50,000 per year for non-compliant software | Up to €10,000 for refusing to issue or accept |
Where the dates actually come from
Two instruments, and only one of them gave a date.
Real Decreto-ley 15/2025 moved Verifactu by a year, to 1 January 2027 for corporate income tax payers and 1 July 2027 for everyone else. That is a fixed calendar date and you can plan against it. Real Decreto 238/2026, in force since April 2026, developed the B2B regime but did not start its clock: the countdown runs from a ministerial order regulating the public invoicing platform, and only then do the 12-month and 24-month phases begin. Anyone quoting you a firm B2B date today is quoting an expectation, not a rule.
What Verifactu actually requires of your system.
Verifactu is not a filing you submit. It is a set of properties your invoicing software must have, enforced by making non-compliant software itself unlawful to use and to sell.
01
Unalterable recordsEach invoice generates a record that cannot be modified or deleted after the fact. Corrections happen through documented rectifying entries, not by editing history. 02
Traceability by chainingRecords are linked to one another with a hash, so that removing or altering one breaks the chain visibly. This is the mechanism that ends silent deletion of sales. 03
VerifiabilityInvoices carry a QR code allowing verification, and the software either submits records to the AEAT automatically or keeps them in a compliant, non-modifiable state. There are two operating modes. In Verifactu mode, records are transmitted to the tax authority automatically as invoices are issued, which relieves the company of certain retention duties. In non-Verifactu mode, records stay with the company but must meet stricter integrity, signature and retention requirements and be available on request. Most standard commercial software defaults to the first.
What to check with your provider — this week
- Is the software declared compliant? Providers must issue a responsible declaration confirming the system meets the requirements
- Which mode does it use — automatic submission or compliant local retention
- Does it cover every invoice stream — including e-commerce, POS, subscriptions and any secondary system
- Do invoices carry the QR code and required identification
- How are corrections handled — rectifying invoices, not edits
- Is your foreign group ERP in scope for the Spanish entity's invoicing, and has it been adapted
- Who retains the records and for how long
The trap specific to foreign-owned companies.
A Spanish subsidiary of a foreign group usually invoices from the group's existing ERP or billing platform, configured for the parent's home market. That system may be excellent and entirely lawful where it was built — and still fail Spanish requirements, because the requirements are about record integrity in a specific technical form that non-Spanish vendors have had no reason to implement.
Common setup
Group ERP, unmodified
Invoices issued from headquarters' system for the Spanish entity, no Spanish adaptation module, no QR code, editable records, and nobody in the group aware the Spanish rules reach the software rather than the filings.
Compliant setup
Adapted module or local system
Either a Spain-certified module within the group ERP, or a compliant Spanish invoicing system for the local entity, with a provider declaration on file and every invoice stream covered.
The same logic will repeat in 2027 with B2B e-invoicing, which adds a structured-format and status-reporting requirement that group systems will again need to be adapted for. Companies that resolve the invoicing stack properly now generally find the second wave is a configuration change rather than a project.
Where this becomes our work
Invoicing system, filings and deadlines as one file.
We check whether your Spanish entity's invoicing meets current requirements, fix what does not, and carry the ongoing filing calendar — so the 2027 wave is a configuration change, not an emergency.
Tax & compliance ↗ The sequence to follow.
Step 01
Inventory every invoice streamMain ERP, e-commerce platform, point of sale, subscription billing, manual invoices from spreadsheets. Each one is separately in scope, and the forgotten stream is usually the manual one. Step 02
Obtain the provider declarationAsk each software vendor for written confirmation of compliance. If a vendor cannot produce one, that is your answer about the system. Step 03
Decide the modeAutomatic submission to the AEAT or compliant local retention. The first is simpler operationally for most companies; the second requires more of your own controls. Step 04
Retrain on correctionsStaff who are used to editing an invoice must switch to issuing rectifying invoices. This is the process change that causes the most friction and the most accidental non-compliance. Step 05
Ask about the second wave tooConfirm with your provider how the structured B2B format and status reporting will be delivered when that clock starts, and whether it is included or a separate module. A vendor who has only solved Verifactu has solved half of it. What the window is for.
Verifactu binds companies from 1 January 2027. That is close enough to plan against and far enough that nothing about it is urgent this week — which is exactly the condition under which it gets forgotten until December. The work is not filling in a form; it is changing the system you invoice from and the habits of the people who use it.
Why the deferral happened
Because the software was not ready, not because the rules softened.
Two reasons were given for moving the dates: developers needed more time from the publication of the final technical specifications, and the government wanted Verifactu and the B2B regime to land in an order that did not force small businesses to change systems twice in one year. The technical requirements themselves — unalterable chained records, hashing, the QR code on every invoice — were not relaxed.
This quarter
Ask your provider one question in writingWill the system you invoice from be certified, and by when. A marketing page is not an answer; the declaracion responsable is. A vendor who cannot commit to a date in 2026 is telling you to start looking. This quarter
Count your invoice streamsMain system, e-commerce platform, point of sale, subscription billing, and the manual invoices somebody issues from a spreadsheet. Each is separately in scope. The forgotten one is almost always the manual one. Before mid-2026 ends
Decide the modeAutomatic submission to the AEAT, or compliant local retention with your own controls. This is a real choice with operational consequences, and making it early means the migration is planned rather than rushed. Autumn 2026
Migrate, and retrain on correctionsStaff used to editing an issued invoice must switch to issuing rectifying invoices. This is the change that causes the most friction, and it is far better learned while nothing depends on it. From January 2027
Run it for realWith the vendor declaration on file and the transition date recorded. If a question is ever asked, that is the evidence that answers it. The sensible reading
A year of runway, used deliberately
Migrate while the stakes are zero. Companies that switch in 2026 get to discover their edge cases — credit notes, partial refunds, multi-currency, the odd manual invoice — without a penalty regime attached to the discovery.
The expensive reading
"It moved once, it will move again"
It may. It also may not, and the cost of being wrong is asymmetric: penalties reported at up to 50,000 euro a year attach to using or holding non-compliant invoicing software, and your accountant will be fully booked in the last quarter before the date.
Check this before you assume it applies to you
Some companies are outside Verifactu entirely.
Businesses already reporting under the SII immediate information supply regime are out of scope, as is the Basque Country, which runs TicketBAI on its own timetable. If either describes you, the Verifactu date is not your date — and confirming that now saves paying for a migration you never needed.
Terminology you will meet
- Verifactu
- The regime governing invoicing software integrity, and the name of the mode in which records are sent to the AEAT automatically.
- SIF
- Sistema informatico de facturacion — the invoicing system the rules apply to.
- Ley Crea y Crece
- Ley 18/2022, which introduces mandatory structured B2B electronic invoicing between businesses and professionals.
- Factura rectificativa
- Rectifying invoice — the only lawful way to correct an issued invoice under an unalterable-records regime.
- Declaracion responsable
- The responsible declaration a software provider issues confirming its system meets the requirements. Ask for it in writing.
- AEAT
- Agencia Estatal de Administracion Tributaria — the Spanish tax authority.
- Factura simplificada
- Simplified invoice, used for smaller consumer transactions; still within the software requirements.
Frequently asked
Is Verifactu in force right now?
No. Real Decreto-ley 15/2025 deferred it by a year: 1 January 2027 for corporate income tax payers, 1 July 2027 for autonomos and everyone else using invoicing software. Earlier dates of January and July 2026 circulated widely and are still quoted on a great many websites, including by advisers. If you were told you are already in breach, check the source against the current text.
So can we do nothing until December 2026?
You can, and it is a poor plan. What the rules require is a change of invoicing system and a change of habit for whoever issues invoices, and both surface edge cases — credit notes, refunds, manual invoices, platform billing. Discovering those in 2026 costs nothing. Discovering them in January 2027 costs something, and your accountant will have a queue.
Is Verifactu the same as mandatory electronic invoicing?
No, and this is the central confusion. Verifactu regulates how your invoicing software creates and keeps records, and applies to B2C as well as B2B. Mandatory structured B2B e-invoicing comes from the Crea y Crece law, applies only between businesses and professionals, and runs on its own clock — its implementing regulation is in force but the countdown starts with a pending ministerial order, followed by 12 months for companies above 8 million euro of turnover and 24 months for the rest. Most companies will end up complying with both.
Can we keep invoicing from our group's ERP abroad?
Only if that system has been adapted to Spanish requirements for the Spanish entity's invoicing. Many international platforms now offer a Spain module; others do not. The practical test is whether the vendor will issue a written declaration of compliance. If they will not, the Spanish entity generally needs a compliant local solution.
What if we only invoice a handful of clients?
Volume does not exempt you. The requirements attach to the act of issuing invoices, not to scale, and low-volume companies invoicing from spreadsheets or generic templates are among the most exposed precisely because they never considered themselves a software case.
Do these rules apply if our company is dormant?
If you are not issuing invoices, the software requirements have nothing to attach to — but a dormant Spanish company still has annual filing and accounting obligations that continue regardless of activity, and those are a separate and frequently neglected exposure.
What are the penalties once it does apply?
Reported at up to 50,000 euro a year for using or holding non-compliant invoicing software, and up to 150,000 euro a year for developers marketing systems that do not meet the requirements. Note what the first one attaches to: possession and use of the software, not each individual invoice. That is why the question to settle is which system you invoice from, and settling it is cheaper before the date than after.
Position as at September 2026. Verifactu dates reflect the deferral enacted by Real Decreto-ley 15/2025: 1 January 2027 for corporate income tax payers and 1 July 2027 for others. The B2B regime reflects Ley 18/2022 as developed by Real Decreto 238/2026, whose phase-in periods run from a ministerial order on the public invoicing platform that had not taken effect at the date of writing. Penalty figures are those reported publicly. Dates in this area have moved more than once; verify against the current official text before acting. General information, not legal or tax advice.