Web Development for the Spanish Market
Spain is the market that regulates the software, not just the invoice. If you are building a billing system for Spanish customers, that changes the design.
Most countries regulate what an invoice must contain. Spain went further and regulated the software that produces it. That single difference is the most important thing to understand before commissioning any system that bills Spanish customers.
Verifactu regulates your billing software, not just your invoices
Under the anti-fraud law and its implementing regulation, invoicing software must produce records that are unalterable, chained to one another, traceable and signed, with a QR code on the invoice. Deadlines have shifted, but the schedule points at January 2026 for corporate taxpayers and July 2026 for the self-employed, with software vendors required to comply earlier. Practically this means your invoice table cannot be a normal editable table. Records are append-only, corrections are new chained entries, and deletion is not an available operation. Retrofitting that into a finished system is not a feature addition, it is a rebuild of the billing core.
Bizum is at checkout now, not just between friends
Bizum started as person-to-person instant payment and has become a genuine e-commerce payment method with tens of millions of users. Spanish acquiring generally runs through Redsys, and Bizum sits alongside cards there. A checkout without it is increasingly noticeable.
Mandatory B2B e-invoicing is still coming
Separately from Verifactu, the Crea y Crece law provides for mandatory business-to-business electronic invoicing, awaiting its implementing regulation. A system designed today for structured invoice output will absorb that when it lands; one designed around PDFs will not.
Language is regional, and the AEPD is firm on cookies
Castilian Spanish is the baseline, but a business serving Catalonia, Galicia or the Basque Country often needs the regional language too — and that is an architecture decision, not a translation task. On privacy, the AEPD updated its cookie guidance in January 2024: cookie walls need a genuine equivalent alternative, and refusing must be as easy as accepting.
What you get
Tech stack
Why work with me
No Spanish client yet, and I say so rather than imply otherwise. My European work is UK, Switzerland and France. The relevant transferable experience is regulated invoicing: ZATCA Phase 2 for Saudi clients required exactly this kind of tamper-evident, authority-facing invoice design.
Verifactu is a data-model decision, and it is the one that matters. Append-only, chained, signed records are cheap if they are the design and enormously expensive if they are a change request. This is the single most valuable thing to get right before the first line of code.
Regional language is architecture, not translation. Deciding at the start whether Catalan or Galician sits in your routing costs nothing; adding a language later to a single-language build is one of the more expensive retrofits there is.
Same working day, and you own the code. Cairo is one hour ahead of Madrid. Repository in your name on delivery.
Related work
Real shipped projects in this space.
In-depth guides on this
Practical articles on the decisions and the costs, before you hire anyone.
Questions before you hire
What is Verifactu and does it apply to me?
Why does it change the database design?
Do I need Bizum at checkout?
What about mandatory B2B e-invoicing?
Do I need Catalan or Galician?
Are Spanish cookie rules different from the EU baseline?
Ready to start your project?
Send your brief. You will get a written quote and a clear plan within 24 hours. First consultation is free.