Verifactu in Palma: get your invoicing ready before 2027
I build the signed invoicing record, the chaining and the filing with the Spanish tax agency into the application you already use. No change of tool and no monthly fee.
In short
- Mandatory on 1 January 2027 for companies
- And on 1 July 2027 for sole traders and everyone else
- Built into your application: no migration to another product
- A one-off cost, not a subscription for ever
What it is and why it affects you
Verifactu is the Spanish tax agency's way of making sure an invoice cannot be touched after it has been issued. Each invoice produces a record, signed and chained to the previous one: if somebody alters one, the chain breaks and it shows. The regulation is Royal Decree 1007/2023 and the dates were set by Royal Decree-Law 15/2025.
It affects you if you invoice in Spain, and it affects the software you invoice with rather than you personally. If you use a commercial product, its vendor has been obliged to sell a compliant version since 29 July 2025: ask them, and get it in writing. If you invoice from a spreadsheet, from a custom application or from your own management system, there is no vendor to ask. That is the case I solve.
And there is a decision worth taking on the evidence, because not everyone explains it: there are two ways to comply and they are not the same. In Veri*factu mode the software sends each record to the tax agency at the moment the invoice is issued, and in exchange what you declared is presumed correct. In the non-submission mode the records stay in your system, signed and chained just the same, and are only sent on request; it avoids depending on a connection for every invoice, but it puts the burden of keeping them properly on you.
What the integration covers
Everything the regulation requires, built inside what you already have.
- Invoicing record
- One record per invoice issued and per cancellation, with the fields the regulation asks for.
- Signature and chaining
- A fingerprint of each record linked to the previous one, so the chain cannot be broken unnoticed.
- Filing with the tax agency
- Automatic submission in Veri*factu mode, or compliant retention if you choose the non-submission mode.
- QR code on the invoice
- The mandatory QR on every invoice, so whoever receives it can verify it.
- Event log
- The internal trail the system has to keep: who did what, and when.
- No monthly fee
- It lives inside your application and it is yours. You do not pay to use your own software.
How we do it
First look at what you have; very often nothing needs throwing away.
See how you invoice today
Which product, which spreadsheet or which application, and how many invoices a month come out of it.
Choose the mode
Veri*factu with submission, or records without submission. I explain what each means for your volume and you decide.
Integrate and test
The record, the signature, the chaining and the QR get built, and tested against the tax agency's test environment.
Go live
It moves to production with room to spare before your date, not the week before.
Price and timeline
The price depends on where it has to go: an application I built myself is a bounded job; somebody else's application with the documentation long lost is another matter, and the first step is to look at it. As always, a fixed quote once I have seen your case.
On the deadlines: 1 January 2027 for companies and 1 July 2027 for sole traders. It sounds far away and it is not, because this touches real invoicing data and wants doing with margin and testing. These dates have also moved twice already; if they change again, I update this page.
Frequently asked questions about custom web and app developmentQuestions about this service
I invoice with a spreadsheet. Is that enough?
Not from your date onwards. A spreadsheet produces no signed or chained records and is not a compliant invoicing system. The options are moving to an adapted product, or building invoicing into an application of your own, which usually pays off if you already run a management system.
Do I have to change invoicing software?
Not necessarily. If your product is commercial, its vendor should already have adapted it. If you invoice from your own application, that application gets adapted. Changing tools only makes sense if the one you have was falling short for other reasons anyway.
What happens if I miss the deadline?
The penalty regime sits in Spain's General Tax Law and falls both on whoever uses a non-compliant system and on whoever builds or sells it. Beyond the fine, the practical problem is that the deadline catches you mid-season and the work gets done in a hurry, on live data.