Home / E-Invoicing / Spain
Spain · Two separate obligations · Do not confuse them

E-Invoicing in Spain

Spain has two parallel obligations that are routinely conflated: Veri*factu, which governs your invoicing software, and Crea y Crece, which governs B2B invoice exchange. They have different rules and different dates.

Talk to us about Spain
In short

E-invoicing in Spain requires domestic B2B invoices to be issued as structured electronic documents through the Crea y Crece B2B framework, using Crea y Crece (Law 18/2022) — distinct from Veri*factu. On 24 March 2026 the Council of Ministers approved a Royal Decree activating the B2B e-invoicing obligation under Law 18/2022 (Crea y Crece); it was published in the BOE on 31 March 2026 and entered into force on 20 April 2026. A Ministerial Order is expected to start the compliance countdown, with companies above EUR 8 million turnover going live approximately one year later and all other in-scope businesses approximately two years later — reported as around 1 October 2027 and 1 October 2028 respectively. Separately, Veri*factu (Royal Decree 1007/2023) requires certified invoicing software guaranteeing invoice integrity and immutability; Real Decreto-ley 15/2025 postponed it by a year, with compliance now required by 1 July 2027. Whatever the local mechanism, the invoice still has to come out of your ERP correctly — and in our experience that is where projects actually succeed or fail. ROSTAN builds the integration into Oracle EBS and Fusion Receivables so compliance is generated from the invoice the business already raises.

The deadline
Two obligations, two timelines

Dates reported from published guidance. Confirm your own obligation with your tax adviser — ROSTAN implements the ERP integration and does not provide tax or legal advice.

What Spain requires

On 24 March 2026 the Council of Ministers approved a Royal Decree activating the B2B e-invoicing obligation under Law 18/2022 (Crea y Crece); it was published in the BOE on 31 March 2026 and entered into force on 20 April 2026. A Ministerial Order is expected to start the compliance countdown, with companies above EUR 8 million turnover going live approximately one year later and all other in-scope businesses approximately two years later — reported as around 1 October 2027 and 1 October 2028 respectively. Separately, Veri*factu (Royal Decree 1007/2023) requires certified invoicing software guaranteeing invoice integrity and immutability; Real Decreto-ley 15/2025 postponed it by a year, with compliance now required by 1 July 2027.

KPMG — Spain B2B e-invoicing mandate
What makes Spain different

The details that change the integration

Veri*factu and Crea y Crece are not the same thing

Veri*factu governs the SOFTWARE that issues your invoices — certified, tamper-evident, immutable records. Crea y Crece governs the EXCHANGE of invoices between businesses. You can satisfy one and still fail the other, which is why scoping a Spanish project as a single workstream usually goes wrong.

Veri*factu touches your ERP itself

Because it concerns how invoicing software records and secures invoices, Veri*factu is a question about your Oracle configuration and controls, not just an interface. It was postponed by a year and is now reported as required by 1 July 2027.

EUR 8 million splits the waves

Under Crea y Crece, companies above EUR 8 million turnover are in the first wave, roughly a year after the Ministerial Order; everyone else follows about a year later.

The countdown starts on an Order, not a fixed date

The go-live dates are anchored to publication of a Ministerial Order rather than being fixed in the decree, which is precisely why Spanish dates have moved before. Plan for the sequence and treat the dates as movable.

The portal is rarely the problem

Statutory e-invoicing is the single largest workload on our own Oracle service desk. These are the causes we see behind rejections, wherever the mandate is.

Tax or product master data that does not match what the schema expects — the most common single cause.
Party identifiers (VAT numbers, registration IDs, addresses) missing or formatted for a human rather than a validator.
A payload that validates in test and fails in production because a real invoice carries a case the sample never did.
No controlled retry path — a rejected invoice is not a valid invoice, and manual re-keying does not scale.
Nobody owning reconciliation: invoices issued in the ERP but never confirmed as accepted downstream.
The receiving side left out of scope, so supplier invoices arrive in a format Accounts Payable cannot process.
FAQ

E-invoicing in Spain

When does B2B e-invoicing become mandatory in Spain?
What is the difference between Veri*factu and Crea y Crece?
Has Veri*factu been delayed?
What does this mean for Oracle EBS or Fusion in Spain?
Free · No obligation

Get Spain e-invoicing working in your ERP

Tell us which entities are in scope and what you run — Oracle EBS, Fusion or something else — and we will tell you what the integration actually involves for your setup.

A named Oracle consultant replies — not a call-centre
We will tell you if you do not need us
Your details are never sold or shared

Your data is safe. We never share or sell your information.

Back to Top
ROSTAN Support
Online · Typically replies instantly
WhatsApp Chat directly, fastest response Call Us +91-9810958952 Email Us info@rostantechnologies.com Send a Message Fill the contact form
Chat with us