🇪🇸 OasisPro · Spain VeriFactu · Crea y Crece · AEAT · EU eInvoicing Gateway
Spain VeriFactu eInvoicing is live.
The B2B mandate is next. 5 things to know.
Spain VeriFactu eInvoicing requirements became mandatory on 1 January 2026 for corporate taxpayers and 1 July 2026 for the self-employed. That makes Spain one of the newest live compliance regimes in the EU right now. But VeriFactu is only half of the Spanish story. The separate B2B eInvoicing mandate under the Crea y Crece law is following behind it, and businesses that treat the two as one requirement are setting themselves up for a second compliance project they did not plan for.
This guide explains what Spain VeriFactu eInvoicing actually regulates, who is in scope, and how it differs from the Crea y Crece B2B mandate.
It also covers how the OasisPro EU eInvoicing Gateway handles Spain alongside every other EU mandate through one connection.
VeriFactu regulates your invoicing software. Crea y Crece will regulate your invoice exchange. Two different Spanish mandates, two different compliance projects, unless your gateway covers both.
The most common misunderstanding OasisPro encounters about Spain is the assumption that VeriFactu compliance means Spanish eInvoicing is done. It does not. VeriFactu is a software integrity regulation. The structured B2B invoice exchange mandate arrives separately under Crea y Crece. A gateway approach that tracks both means one integration effort instead of two.
What Spain VeriFactu eInvoicing actually requires
VeriFactu is a regulation about the invoicing software itself, established under Royal Decree 1007/2023 and the anti-fraud law.
It requires that computerised invoicing systems (SIF) used by Spanish taxpayers guarantee the integrity, conservation, accessibility, legibility, traceability, and inalterability of invoicing records.
In practice, VeriFactu compliance means invoicing software must generate a hash-chained record for every invoice and include a QR code on the invoice output.
The software must also either operate in VeriFactu mode, submitting invoicing records to the AEAT in real time, or in non-VeriFactu mode with stricter local integrity and audit obligations.
The AEAT VeriFactu portal is the authoritative source for the technical specifications, including the record formats, hash chain requirements, and the submission service for VeriFactu mode.
Hash-chained invoice records
Every invoicing record must be linked to the previous one through a cryptographic hash chain, making retrospective alteration detectable. Your invoicing software must generate and maintain this chain automatically for every invoice issued.
QR code on every invoice
Invoices must carry a QR code that allows the recipient or the tax agency to verify the invoice against AEAT records. The QR content and format are defined in the VeriFactu technical specification and must be generated at the point of invoice creation.
VeriFactu mode: real-time AEAT submission
Systems operating in VeriFactu mode submit invoicing records to the AEAT immediately upon issue. This is the mode the AEAT encourages, and invoices from VeriFactu-mode systems can display the VERI*FACTU indication.
VeriFactu is live now. If your Spanish entity issues invoices from software that does not meet the requirements, the exposure started in January 2026.
Penalties under the anti-fraud framework apply both to software providers selling non-compliant systems and to businesses using them. For businesses running ERP systems that were never designed around Spanish hash chain and QR requirements, the compliant route is a certified invoicing layer or gateway that sits between the ERP and the invoice output.
Spain VeriFactu eInvoicing versus the Crea y Crece B2B mandate: the difference that matters
The Crea y Crece law established the obligation for structured B2B electronic invoicing between Spanish businesses.
This is a completely separate requirement from VeriFactu, closer in nature to the mandates in France, Belgium, and Poland.
Under Crea y Crece, businesses will exchange structured electronic invoices through certified exchange platforms, with a public solution operated alongside private platforms.
Payment status reporting obligations are attached to combat late payment, which was the original policy driver of the law.
The implementing royal decree defines the phased timeline, with larger businesses obligated first and smaller businesses following.
Businesses with Spanish operations should treat the B2B mandate as a confirmed future requirement with a timeline that firms up behind VeriFactu.
| Aspect | VeriFactu | Crea y Crece B2B mandate |
|---|---|---|
| What it regulates | The invoicing software itself: integrity, hash chains, QR codes, AEAT submission | The exchange of structured electronic invoices between businesses |
| Status in August 2026 | Live and mandatory | Royal decree phase, timeline following |
| Who enforces | AEAT (Spanish tax agency) | AEAT and the Ministry of Economic Affairs |
| Invoice format impact | QR code and record obligations on existing invoice formats | Structured electronic formats exchanged via platforms |
| Comparable to | Portugal certified software rules, fiscalisation regimes | France, Belgium, Poland B2B eInvoicing mandates |
Businesses that build for VeriFactu alone will do a second Spanish compliance project when the Crea y Crece B2B mandate lands. A gateway that tracks both means one integration, not two.
The 5 things every business with Spanish operations should know now
- VeriFactu is live, not upcoming. Corporate taxpayers have been in scope since 1 January 2026 and the self-employed since 1 July 2026. If your Spanish entity's invoicing software has not been assessed against VeriFactu, that assessment is overdue rather than early.
- Standard ERP output is not automatically VeriFactu compliant. Hash chains, QR codes, and AEAT record submission are not native features of most ERP invoicing modules. A compliance layer between the ERP and the invoice output is the practical route for most international businesses.
- VeriFactu mode is the strategically better choice. Between VeriFactu mode (real-time AEAT submission) and non-VeriFactu mode (stricter local obligations), real-time submission aligns your business with the direction of Spanish and EU-wide reporting under ViDA.
- The Crea y Crece B2B mandate is confirmed policy, not speculation. The law is in force and the implementing decree defines the phases. Plan your Spanish invoicing architecture for structured B2B exchange from the start.
- One gateway covers Spain and everything else. Spain joins France, Belgium, Poland, Italy, Germany, and Romania in the list of EU countries with live or imminent mandates. The OasisPro EU eInvoicing Gateway covers all of them through one ERP connection with regulatory updates included.
The OasisPro EU eInvoicing Gateway tracks Spain across both VeriFactu and Crea y Crece.
One middleware connection from any ERP: SAP, Oracle, Odoo, IFS Cloud, Dynamics, NetSuite, or any other. OasisPro maintains the gateway against Spanish requirements as they phase in, alongside every other active EU mandate, so your ERP integration is built once and stays compliant as Spain's rules evolve.
Read about the OasisPro EU eInvoicing GatewaySpanish operations? Get VeriFactu handled and Crea y Crece planned in one conversation.
Talk to OasisPro about your Spanish invoicing footprint. We will assess your VeriFactu position, map your Crea y Crece exposure, and show you what one gateway connection covers across Spain and the rest of the EU.
What is Spain VeriFactu?
Spain VeriFactu is the certified invoicing software regulation established under Royal Decree 1007/2023. It requires billing systems used by Spanish taxpayers to guarantee the integrity, traceability, and inalterability of invoicing records through hash chains and QR codes, with optional real-time submission of records to the AEAT tax agency. It became mandatory for corporate taxpayers on 1 January 2026 and for the self-employed on 1 July 2026.
Is VeriFactu the same as the Spain B2B eInvoicing mandate?
No. VeriFactu regulates the invoicing software itself. The separate B2B eInvoicing mandate under the Crea y Crece law will require structured electronic invoices to be exchanged between Spanish businesses through certified platforms, with payment status reporting attached. The B2B mandate follows VeriFactu with its own phased timeline defined by royal decree. The two are separate compliance requirements.
Does VeriFactu apply to foreign businesses selling into Spain?
VeriFactu applies to taxpayers subject to Spanish corporate income tax and personal income tax, including permanent establishments in Spain, that use computerised invoicing systems. Foreign businesses without Spanish tax presence are generally outside VeriFactu scope. However, businesses with Spanish subsidiaries, branches, or establishment-level VAT obligations should assess their position carefully with their tax advisers.
How does the OasisPro EU eInvoicing Gateway handle Spain?
The OasisPro EU eInvoicing Gateway covers Spanish requirements across both VeriFactu and the upcoming Crea y Crece B2B mandate, alongside every other active EU eInvoicing mandate. One gateway connection from any ERP handles the format generation, compliance obligations, and submission requirements, with Spanish regulatory updates included in the service as the requirements phase in.
Spain VeriFactu eInvoicing is live. Crea y Crece is coming. One gateway covers both.
Spain has moved from planning to enforcement. VeriFactu obligations are active for the overwhelming majority of Spanish taxpayers, and the structured B2B exchange mandate is the confirmed next step.
Businesses that connect through the OasisPro EU eInvoicing Gateway handle Spain the same way they handle France, Belgium, Poland, Italy, and Germany: one connection, every mandate, updates included.
Talk to us about your Spanish footprint.