Spain’s eInvoicing reform is more than a mandate, it’s a shift to full invoice lifecycle control.

With the publication of Royal Decree 238/2026 on 31 March 2026, Spain has taken a decisive step towards mandatory B2B eInvoicing. However, reducing this reform to “just another eInvoicing mandate” would be a mistake.

The Spanish model goes significantly further. It introduces a layered compliance framework that combines invoice exchange, reporting, system control and payment monitoring – effectively moving toward full invoice lifecycle visibility.

The new rules define who must issue electronic invoices, which transactions are covered, the technical formats that must be used and when the obligations will apply. For businesses trading in Spain, this is a clear signal: B2B invoicing processes will need to change

A hybrid eInvoicing model with reporting elements.

The new obligation applies to domestic B2B transactions where both parties are established in Spain or have a permanent establishment there. Simplified invoices remain out of scope unless the customer requests a full invoice.

Spain allows businesses to exchange invoices via private or public platforms. However, even when using a private provider, companies must simultaneously transmit a structured electronic copy of each invoice to the state platform, typically in UBL format.

This creates a hybrid model:

  • Not a pure clearance system
  • Not a simple post-audit model
  • But a combination of invoice exchange and indirect reporting

From invoicing to lifecycle monitoring

One of the most distinctive features of the Spanish framework is the obligation to report invoice lifecycle events.

Recipients must communicate:

  • Acceptance or rejection of the invoice
  • Payment status (full or partial)
  • Payment date

These updates must generally be reported within four calendar days (excluding weekends and public holidays).

This requirement effectively shifts the system beyond invoicing into real-time monitoring of payment behaviour, something still relatively unique within the EU.

Spain’s eInvoicing formats and interoperability

Spain accepts multiple formats aligned with the European standard EN 16931, including:

  • Universal Business Language (UBL)
  • Cross Industry Invoice (CII)
  • Electronic Data Interchange for Administration, Commerce and Transport (EDIFACT)
  • Facturae (Spain’s national eInvoicing format – XML)


However, interoperability is mandatory. Platforms must be capable of transforming invoices into different formats, ensuring seamless communication across the ecosystem.

Reporting deadlines

Invoice status updates must be reported:

  • Within a maximum of four calendar days of the status change
  • Saturdays, Sundays and national public holidays are excluded from the calculation

Both public and private eInvoicing platforms must support these reporting requirements and comply with the technical specifications set out in the Decree

When the rules enter into force

The Decree formally enters into force:

  • 20 days after publication in the Official State Bulletin.

However, effective application is deferred until the Regulation governing public eInvoicing platform enters into force under Law 18/2022. Until that happens, businesses are not yet required to comply operationally.

Phased timeline dependent on the public platform

Although the decree formally entered into force in April 2026, its application depends on the launch of the public eInvoicing platform. Once live, the rollout will follow a phased approach:

Phase 1: Large businesses
  • Applies within 12 months of effective application
  • Covers companies with turnover exceeding €8 million in the previous year

During this phase:

  • eInvoices are mandatory
  • PDF copies must accompany electronic invoices where the recipient is not yet in scope.

Phase 2: All remaining businesses
  • Applies within 24 months of effective application
  • Covers all other businesses subject to the invoicing rules

At this point, mandatory B2B eInvoicing becomes universal for in‑scope Spanish transactions. During the transition period, invoices must also be provided in PDF format to ensure readability for recipients not yet in scope.

VeriFactu: The parallel layer

In parallel with eInvoicing, businesses must comply with Royal Decree 1007/2023, which focuses on invoicing system integrity rather than invoice exchange.

VeriFactu introduces strict requirements for:

  • Data immutability and traceability
  • Electronic signatures
  • Hash chaining of records
  • Inclusion of a QR code on invoices

Companies can choose between:

  • A VeriFactu mode, where invoice records are automatically transmitted to the tax authority, or
  • A non-VeriFactu mode, where records remain local but must meet stricter control and audit requirements

Deadlines have been postponed to:

  • 1 January 2027 for companies
  • 1 July 2027 for self-employed individuals

Non-compliance: Not just technical risk

The Spanish framework introduces significant penalties. Under the General Tax Law, companies using non-compliant invoicing systems may face fixed fines of up to €50,000 per year.

Importantly, the risk is not limited to active use:

  • Merely possessing a non-compliant invoicing system capable of issuing invoices may trigger sanctions
  • Legacy systems must be properly decommissioned or made incapable of issuing invoices

Common mistakes companies are making

Many businesses are underestimating the scope of the reform. The most frequent misconceptions include:

“This is just another eInvoicing mandate.”
In reality, Spain introduces invoice lifecycle reporting and payment tracking, significantly expanding compliance obligations.

“We are already compliant because of real-time reporting.”
Systems like Suministro Inmediato de Información (SII) serve a different purpose. Compliance with SII does not ensure readiness for e-invoicing or VeriFactu.

“PDF invoicing or existing tools will be sufficient.”
Structured data exchange, platform integration and system certification are now required.

“We only need to focus on eIvoicing.”
In reality, two separate layers must be addressed:

  1. eInvoice exchange and reporting
  2. Invoicing system compliance (VeriFactu)

What this means for global businesses

Spain is not simply introducing eInvoicing – it is redefining how invoices are created, exchanged and monitored.

Businesses that treat this as a standard compliance exercise may face significant operational and regulatory challenges. Those that approach it strategically can turn it into an opportunity to modernise their processes and reduce long-term risk.

Although key deadlines have been deferred, the complexity of the Spanish model means that waiting is a risk.

Companies should:

  • Assess their current invoicing landscape
  • Identify gaps across both eInvoicing and VeriFactu requirements
  • Plan system upgrades or platform integrations
  • Review legacy systems and decommission non-compliant tools

Businesses that prepare early will be best placed to manage compliance, reduce manual effort and avoid disruption as the deadlines approach.

Work with indirect tax experts

At Fintua, we help businesses navigate regulatory changes with clarity and confidence. From VAT compliance to multi-jurisdictional tax processes, our experts and technology keep you ahead of change.

Subscribe to our newsletter

Stay informed about the latest VAT news, trends and topics from around the globe with our monthly newsletter. Each month, we deliver insightful updates straight to your inbox, helping you stay ahead of the curve.

Authors

101094Spain sets rules for mandatory B2B eInvoicing

Lisa Dowling

Chief Tax & Compliance Officer at Fintua

Specialising in International VAT Compliance solutions, Lisa brings a wealth of knowledge and insight in her dealings with a host of international clients ranging from start-ups through to multinationals. With 24 years VAT experience behind her, Lisa has managed VAT compliance issues and solutions globally for over 14 years. Fintua have 12,000 + corporate clients in over 109 countries and many of these are members of the Fortune 500.