E-Invoicing in Spain: We Adapt Your ERP, Online Store or SaaS to B2B E-Invoicing
E-invoicing between businesses is becoming mandatory in Spain: around October 2027 for companies invoicing more than €8 million a year and around October 2028 for everyone else. We prepare the software your Spanish business already invoices with to issue and receive structured invoices, track their status and work alongside Verifactu in a single layer.
- 2027 October: businesses invoicing over €8M a year
- 2028 October: all other businesses and freelancers
- 1 layer E-invoicing and Verifactu together
- 01 · Inventory Systems, data and risks
- 02 · Risk Classification and thresholds
- 03 · Controls Technical and organisational
- 04 · Evidence Records that prove it
- 05 · Audit Internal and external
- 06 · Accountable A person answers for it
- Every finding updates the controls
Definition
What Is Mandatory B2B E-Invoicing in Spain?
It is the obligation for businesses and professionals in Spain to issue and receive the invoices they exchange in a structured format that software can read without human intervention, instead of a PDF or paper. It is introduced by Law 18/2022 (the Spanish ‘Create and Grow’ law) and implemented by Royal Decree 238/2026.
Summary
Executive Summary
What changes, when, and why it pays to do it only once.
On 6 October 2026 Order HAC/1028/2026, which regulates the public e-invoicing solution, came into force. It started the clock set by Royal Decree 238/2026: 12 months for businesses invoicing more than €8 million a year and 24 months for everyone else. That puts the dates around October 2027 and around October 2028. Nobody has published the exact day the count ends, so it is wise not to leave it to the last minute.
The work is not about generating a file. It is about your ERP, your online store or your SaaS being able to issue the invoice in a structured format, receive your suppliers’ invoices, know the status of each one and reconcile everything with accounting, without anyone typing anything twice. And it is about not doing it twice: on 5 October 2026 the Ministry of Finance announced that it plans to move Verifactu to October 2028 so that it coincides with e-invoicing for businesses invoicing €8 million or less. It is an announcement, not yet in the BOE (Spain’s Official State Gazette), but it shows the direction.
The hard part for international groups is usually the system, not the rule: a Spanish subsidiary invoicing from the group ERP, a SaaS used by customers in Spain, an online store run by a Spanish company. Whether the obligation applies to your entity is the first thing we check in the diagnosis. That is why we design a single invoicing layer: the same invoice data feeds the Verifactu record and the e-invoice sent to your customer. We adapt the software you already have (custom ERP, WooCommerce, PrestaShop, Magento, Shopify or your own SaaS) or build a new platform when adapting is not worth it. And if you first want to know where you stand with Verifactu, our free checker tells you in a minute.
- 12 months From 6 Oct 2026, over €8M
- 24 months From 6 Oct 2026, everyone else
- ISO 27001 And ENS: certified in 2026
Timeline
Spain’s E-Invoicing Timeline as of 31 October 2026
What the BOE says and what the Ministry of Finance has announced. We update it when it changes.
- 01
6 October 2026: The Clock Starts
Order HAC/1028/2026 (BOE of 5 October), which implements the public e-invoicing solution, comes into force. The deadlines of Royal Decree 238/2026 run from here.
- 02
October 2027
Mandatory e-invoicing between businesses for those invoicing more than €8 million a year: 12 months from the order.
- 03
October 2028
For all other businesses and professionals: 24 months from the order.
- 04
October 2028: Verifactu Aligns
The Ministry of Finance plans to postpone the pending Verifactu obligations to October 2028 so that they coincide with e-invoicing for businesses invoicing €8M or less, followed by a convergence amendment with ViDA, the EU initiative. Until it appears in the BOE, Verifactu keeps its 2027 deadlines.
Key points
What We Do
Depending on what you invoice with today.
- 01
Custom ERP or Invoicing Software
We add structured invoice issuing, receipt of your suppliers’ invoices and status tracking to your system, on top of your database and without changing how your team works. In Laravel, Symfony, Node.js or Python.
- 02
B2B Online Stores
If you sell to businesses in Spain from WooCommerce, PrestaShop, Magento or Shopify, the invoice your store issues will also have to be electronic. We solve what usually breaks: corrective invoices for returns, several stores under one tax ID and orders coming in from marketplaces.
- 03
Integration With Your Commercial ERP
When the invoice is created in the store or the CRM and booked in the ERP, the problem is the connection. We make both systems share the same invoice data, as we explain in ERP and ecommerce integration and SAP Business One integration.
- 04
SaaS and Software Vendors
If your customers in Spain invoice with your product, all of them will need e-invoicing. We review your product, implement issuing, receipt and statuses, and prepare it to invoice on behalf of many tax IDs.
- 05
Invoice Receipt and Reconciliation
Receiving is half the rule. We make your suppliers’ invoices enter your system in structured form, match them to the order or delivery note and pass them to accounting without typing anything.
- 06
New Platform With Verifactu and E-Invoicing Built In
When adapting is not worth it (legacy systems, invoicing spread across several tools, groups with several tax IDs), we build a new invoicing platform with both obligations solved from day one.
What's included
What Your System Has to Do
What we review in the assessment and leave working.
- Issue the invoice in a structured format, with the data that goes in your PDF today, generated from the same record as the invoice
- Receive your suppliers’ invoices in a structured format and bring them into your system without retyping them
- Track the status of every invoice: issued, delivered, accepted, rejected or paid, visible to whoever handles it
- Validate before sending: tax IDs, amounts, taxes and series, so no invoice goes out that the recipient cannot process
- Corrective invoices and credit notes that travel just like the original invoice, with a reference to the one they correct
- Connection with accounting and the ERP, so an issued or received invoice is never entered twice
- The same layer as Verifactu: one piece of invoice data for the hashed record, the QR code and the electronic delivery
- Retention and export of issued and received invoices, even if you change software tomorrow
- A log of every delivery and receipt, with its response, so you know what happened to each invoice
Why
Verifactu and E-Invoicing: Two Regulations, One Layer
Why you should not adapt your software twice.
Verifactu faces the tax authority: every invoice generates an unalterable record with the hash of the previous one, a QR code and, in its main mode, a submission to the AEAT. B2B e-invoicing faces your customer and your supplier: the invoice travels between businesses in a format software can read. Both start from the same data (issuer, recipient, series, number, tax breakdown, amount) and both penalise the same thing: invoices edited after they have been issued. Build them separately and you maintain two corrective-invoice logics, two numbering schemes and two places where things can stop adding up. So we design them together: the invoice is issued once, locked, and both the Verifactu record and the e-invoice come from it. Everything about Verifactu (dates, modes, the responsible declaration and prices) is on our Verifactu compliance page.
- Oct 2027 Over €8M
- Oct 2028 Everyone else
- 1 Adaptations
How we work
How We Do It
From the first analysis to the first e-invoice issued and received.
- 01
Assessment
We review how your business invoices and receives invoices in Spain today: software, series, corrective invoices, stores, ERP and who issues on behalf of whom. We tell you what your system is missing, whether and when the obligation applies to your entity, and whether to adapt or replace it, with a fixed quote.
- 02
Invoicing Layer Design
Where the invoice is created, how it is locked, how it is issued and received in a structured format, how its statuses are tracked and how it connects to Verifactu and to accounting.
- 03
Development With Tests
Issuing, receipt, statuses, validations and corrective invoices, with automated tests on real (anonymised) invoices from your business on every code change.
- 04
Testing With Customers and Suppliers
Before your deadline, we test the exchange with a few real customers and suppliers and reconcile what reaches accounting.
- 05
Go-Live and Maintenance
You go live before it is mandatory, without rushing. And when the rules or formats change, we keep it up to date.
Who it is for
Is It for You?
It fits when your invoicing in Spain runs on your own systems, stores or a SaaS, not on a commercial program that will handle it for you.
Who it's for
- Businesses invoicing more than €8 million a year: their deadline comes around October 2027.
- Companies with a custom-built ERP or invoicing software.
- Online stores selling to businesses that issue many invoices and corrective invoices.
- Software vendors and SaaS providers whose customers in Spain invoice with their product.
- Foreign companies operating in Spain whose central ERP does not know Spanish regulations.
Who it's not for
- Freelancers and small businesses using a commercial invoicing program: their vendor will normally adapt it.
- Those who only need Verifactu: we explain it on our Verifactu page.
- Those looking for tax advice: we coordinate with your tax adviser, but we do not replace them.
Deliverables
What You Get
What is included and what is not.
Included
- Assessment report with what is missing, your deadline and the decision to adapt or replace
- Structured invoice issuing from your system
- Receipt and import of your suppliers’ invoices
- Status tracking for every issued and received invoice
- Connection with your accounting or ERP and with the Verifactu layer
- Technical documentation and automated tests for your team
Not included
- Tax advice on your transactions (we coordinate it with your adviser)
- Third-party software licences or fees of exchange providers
The proof
What Backs the Service
B2B e-invoicing is not yet mandatory for anyone in Spain, so we will not show you projects for a rule that has not started. We show you what supports it. At Fleurop we sync orders from their store with their ERP through asynchronous queues, with retries and an audit of every transfer: the pattern any invoice exchange between systems needs. We built Nexo, our own management platform, with synchronised invoicing and an immutable hash-chained audit trail. We have been certified in ISO 27001 and Spain’s National Security Framework (ENS) since September 2026, which is what you want from whoever handles your tax data. And our Verifactu hash calculator reproduces the AEAT’s official examples character for character: you can check it yourself.
- 2009 Building software since
- 3 of 3 Official hash examples we reproduce
- 2 Certified security standards
- 5.0 Clutch rating
For the CTO
Summary for the CTO
How we build it under the hood.
The invoice is issued once and then locked: it is corrected with a corrective invoice, never with an UPDATE. Both outputs come from that record, the Verifactu record and the structured e-invoice, so there are no two sources of truth that can drift apart. Format generation is kept separate from business logic, so the format or the exchange channel can change without touching how your system invoices.
Sending and receiving are decoupled into queues, with retries, a log of every response and alerts when something does not arrive. Each invoice keeps its status history. Received invoices are validated before they come in and matched to the order or delivery note. Everything is covered by automated tests on every deployment, under the same controls we are certified for in ISO 27001 and ENS: personal access and encrypted credentials.
Technologies
- Laravel
- Symfony
- Node.js
- Python
- PostgreSQL
- Redis
- RabbitMQ
- Facturae
- UBL
- REST APIs
- One invoice, one record: Verifactu and e-invoicing come from the same data
- Immutable invoices: corrections and cancellations, never edits
- Sending and receipt in queues with retries and a response log
- Status history per invoice, issued and received
- Format separated from logic, to change channel without rebuilding
Risks and how we cover them
The Risks We Avoid
What we see in rushed adaptations.
- 01
Adapting to Verifactu now and rebuilding it in 2028 for e-invoicing
MitigationA single invoicing layer for both obligations, following the convergence the Ministry of Finance has announced.
- 02
Thinking only about issuing and forgetting that you also have to receive
MitigationWe design receipt from the start: structured intake, validation, matching with orders and hand-off to accounting.
- 03
Invoices edited after they have been issued
MitigationIssued invoices are locked and corrective invoices handle everything else, with tests that check it on every deployment.
- 04
Cutting it close when the exact day has not been published
MitigationWe plan to be ready before October 2027 or 2028, with room to test with real customers and suppliers.
Technologies
Platforms and Technologies
The ones we already work with and adapt or build on.
- WooCommerce
- PrestaShop
- Magento / Adobe Commerce
- Shopify
- Odoo
- SAP Business One
- Laravel
- Symfony
- Node.js
- Python
- PostgreSQL
- Facturae and UBL
- Verifactu
- Stripe
FAQ
E-Invoicing in Spain FAQs
Answers checked against the BOE and the Ministry of Finance’s notes.
When does B2B e-invoicing become mandatory in Spain?
Royal Decree 238/2026 makes it mandatory 12 months after its implementing order for businesses invoicing more than €8 million a year and 24 months after it for everyone else. That order is Order HAC/1028/2026, in force since 6 October 2026, which puts the dates around October 2027 and around October 2028. The exact day the count ends has not been published.
What is the ‘Create and Grow’ law and how does it relate to e-invoicing?
It is Law 18/2022, Spain’s law on the creation and growth of companies (Ley Crea y Crece). It introduces the obligation to issue and receive invoices between businesses in a structured electronic format. Royal Decree 238/2026 implements it and sets the deadlines.
Are Verifactu and e-invoicing the same thing?
No. Verifactu (Royal Decree 1007/2023) requires your software to record invoices in an unalterable way and, in its main mode, send them to the AEAT. B2B e-invoicing requires businesses to issue and receive invoices between them in a structured format. They are two different regulations, but the Ministry of Finance has announced it will align their timelines in October 2028. Verifactu is covered on our Verifactu page.
If I have already adapted to Verifactu, is e-invoicing done?
Not necessarily. Verifactu generates a record for the tax authority; the e-invoice is what travels to your customer in a structured format, and you also need to be able to receive your suppliers’ invoices. If your Verifactu adaptation was designed with a single invoicing layer, adding e-invoicing is much simpler.
Has Spain postponed e-invoicing?
What the Ministry of Finance announced on 5 October 2026 is that it plans to postpone Verifactu to October 2028, so that it coincides with e-invoicing for businesses invoicing €8 million or less. The e-invoicing deadlines come from Royal Decree 238/2026 and Order HAC/1028/2026, which are in the BOE.
Do I also have to receive e-invoices?
Yes: the rule requires businesses to issue and receive invoices between them in a structured format. That is why we adapt both directions: invoices going out to your customers and invoices coming in from your suppliers, all the way to accounting.
What is the public e-invoicing solution?
It is the solution regulated by Order HAC/1028/2026, whose entry into force on 6 October 2026 started the clock on the deadlines. How your system fits with it and with private exchange channels is one of the decisions we make with you in the assessment.
Does it apply to my company if it is in the SII or taxed in the Basque Country or Navarre?
Those situations keep you out of Verifactu, but B2B e-invoicing is a different regulation with its own scope. We review it in the assessment for your specific case and, if needed, with your tax adviser.
How much does it cost to adapt my software to e-invoicing in Spain?
It depends on how many systems, series, stores and tax IDs you have, and on whether you also need Verifactu. After the assessment we give you a fixed quote. If we build a new invoicing platform with Verifactu and e-invoicing built in, the published price starts from €24,000. Prices for Verifactu adaptation are on its page.
Do you work with companies outside Spain?
Yes. If your company invoices in Spain with a central ERP or SaaS that does not know Spanish regulations, we adapt that system or build the Spanish layer that connects to it. We work in Spanish, English, Catalan, French, German, Dutch and Portuguese.
Sources
Sources
The official regulations and documents behind every fact on this page.
- Royal Decree 238/2026, B2B e-invoicing 12- and 24-month deadlines depending on turnover.
- Order HAC/1028/2026, public e-invoicing solution In force on 6 Oct 2026: starts the count for those deadlines.
- Ministry of Finance information note of 5 October 2026 Planned postponement of Verifactu to October 2028; pending regulation.
- Royal Decree 1007/2023, Regulation on invoicing software systems (Verifactu) The other regulation affecting the same software.
Next step
Tell Us What You Invoice With and We’ll Tell You What It Needs for E-Invoicing
A 30-minute video call with the person who will build it. If your commercial program is going to handle it, we will tell you and not sell you anything.
- No commitment
- Response in 24h
- Custom proposal
Let's talk.
Initial technical consultation
AI, security and performance. Diagnosis with phased proposal.
- NDA available
- Response <24h
- Phased proposal
Your first meeting is with a Solutions Architect, not a salesperson.
Talk to an architect