Spain e-invoicing regimes: How they overlap and what finance teams should do for compliance

Zone & Co Team
Decorative header image for Zone & Co article on usage-based billing in Salesforce RCA and NetSuite, featuring overlapping circles on a navy background with the Zone logo.

Spain’s e-invoicing timeline can be more complex to pin down compared to other European mandates because it involves three overlapping regimes that affect different parts of finance operations:

  • The B2B e-invoicing mandate under Royal Decree 238/2026
  • VeriFactu’s software certification requirements under Royal Decree 1007/2023
  • The existing Suministro Inmediato de Información (SII) real-time VAT reporting system

Each of these regulations have their own scope, deadlines and technical requirements. Treating them as one generic, singular Spain e-invoicing project will likely result in finance teams ending up with fragmented tooling and missed deadlines.

The regulatory picture sharpened significantly in early 2026. Royal Decree 238/2026 was published on March 31, 2026, establishing the B2B framework. VeriFactu deadlines, after multiple postponements, are set for January and July 2027. And with software adaptation deadlines approaching, recipient-side obligations change how your accounts payable (AP) team works and payment-status reporting adds new data requirements.

Key highlights:

  • Spain e-invoicing involves three distinct compliance regimes, each with different scope, timelines and technical requirements.
  • The B2B mandate under Royal Decree 238/2026 requires structured invoice exchange through public or private platforms, plus mandatory invoice status and payment date reporting.
  • VeriFactu is an entirely separate software certification regime that ensures your billing system produces tamper-proof, traceable invoice records.
  • Finance teams need to plan for adoption together but implement them separately, mapping which obligations apply to their business before making technology decisions.

Spain e-invoicing timeline at a glance 

Spain’s B2B e-invoicing mandate, VeriFactu and SII all run on different clocks. Some are already finalized, while others are pending. 

Here’s where each one stands as of June 4, 2026, according to Boletín Oficial del Estado (BOE) and European Commission information:

Requirement What it covers Current status What teams should do now
B2B e-invoicing (Crea y Crece)
  • Structured invoice exchange between businesses
  • Invoice status reporting
  • Payment date reporting
  • Royal Decree 238/2026 published March 31, 2026
  • Implementation deadlines will be 12 months or 24 months after Ministerial Order publication
  • Monitor Ministerial Order publication
  • Begin platform evaluation and data readiness assessment
VeriFactu
  • Billing software certification
  • Tamper-proof records and hash chains
  • QR codes
Deadlines set:
  • Jan 1, 2027 for corporate taxpayers
  • July 1, 2027 for self-employed
  • Confirm your invoicing software vendor’s VeriFactu compliance roadmap
SII Real-time VAT data reporting to AEAT within four calendar days Mandatory since July 2017 for large taxpayers (€6 million or more turnover)
  • Already live, so ensure ongoing compliance
  • Assess overlap with new B2B requirements
B2G e-invoicing Electronic invoicing to public sector via FACe platform Mandatory since January 2015 using Facturae format
  • Already live, so maintain FACe compliance
  • Watch for format alignment with B2B mandate

What’s finalized for Spain e-invoicing

These regulations are already finalized: 

  • Royal Decree 238/2026 is published and in force
  • The B2B e-invoicing framework is legally established 
  • VeriFactu deadlines are set at January 1, 2027 for corporate taxpayers and July 1, 2027 for all other tax payers
  • SII and B2G obligations are already operational with businesses submitting e-invoicing through Punto General de Entrada de Facturas Electrónicas (FACe)

What’s still pending

Spain’s mandatory B2B e-invoicing regime is not yet in effect. While the underlying legislation (Law 18/2022 and Royal Decree 238/2026) is in force, the Ministerial Order that defines the public platform’s technical specifications — and formally starts the compliance clock — remains unpublished as of mid-2026. Businesses should not assume any specific deadline until that order is confirmed.

Based on the current draft, entry into force is targeted for October 1, 2026, which would give larger businesses (turnover above €8 million) until around October 2027, and smaller businesses until around October 2028. However, these dates are indicative only and subject to change pending final publication.

What finance teams can act on now

You don’t need final dates to start preparing. Here’s what to do now: 

  • Map which of the three regimes apply to your business
  • Confirm your invoicing software handles VeriFactu requirements
  • Assess your data quality for B2B e-invoicing fields
  • Review your SII reporting workflows for overlap with new B2B status reporting
  • Evaluate platform options (including AEAT’s public solution or private interoperable platforms) before the Ministerial Order narrows your implementation window

Which businesses are affected by Spain’s B2B e-invoicing mandate

The B2B e-invoicing mandate under Royal Decree 238/2026 applies to businesses and professionals conducting B2B transactions in Spain. Company size determines your deadline, and recipient-side obligations change the operating model in ways most teams don’t initially expect.

Spain’s B2B e-invoicing mandate scope

All entrepreneurs and professionals operating in Spain must issue, transmit and receive structured electronic invoices for B2B transactions. The mandate covers:

  • Invoice exchange through AEAT’s public platform or certified private platforms
  • Mandatory reporting of invoice status
  • Payment date reporting

Crucially, PDF-only invoices will no longer satisfy B2B requirements once deadlines take effect. These are the deadlines based on business size, according to the BOE:

Business size Deadline What’s required
Large businesses (annual turnover greater than €8 million)
  • 12 months after Ministerial Order publication
  • Has not yet been published
  • Issue, receive and transmit structured B2B e-invoices
  • Report invoice status and payment dates
All other businesses
  • 24 months after Ministerial Order publication
  • Has not yet been published
Same obligations as large businesses

Recipient and payment-status obligations

This is where Spain’s mandate differs from some other European e-invoicing regimes. It’s not just about issuing invoices, as recipients have active obligations too. 

Under Royal Decree 238/2026, invoice recipients must communicate rejection, acceptance and the date of full payment electronically to the public platform. Recipients may also need to report the payment due date, and in some cases the date goods were received or services performed, where these are relevant to calculating payment periods under Spain’s anti-late-payment rules.

Payment date reporting is also mandatory. When you pay an invoice, that date must be transmitted through the platform. In addition to enforcing VAT compliance, this mandate seeks to combat late payments.

For AP teams, this means payment processing workflows need to connect to the e-invoicing platform so payment dates flow to AEAT automatically.

What is VeriFactu in Spain? 

VeriFactu Spain is one of the most misunderstood parts of the Spanish compliance landscape. It’s not an e-invoicing mandate; it’s a billing software certification regime designed to prevent tax fraud by ensuring invoice records are tamper-proof and traceable.

What VeriFactu is designed to do

VeriFactu (formally the SIF – Sistema Informático de Facturación) was introduced under Spain’s Anti-Fraud Law 11/2021 and specified by Royal Decree 1007/2023. It requires that the software you use to generate invoices produces records that are:

  • Sequentially chained with digital fingerprints (hash chains)
  • Timestamped
  • Including a QR code for verification 
  • Cannot be altered after issuance

The system gives AEAT a way to verify that no invoices have been deleted, modified or hidden after creation. Businesses can either submit billing records directly to AEAT (the “VeriFactu” option) or use certified billing systems that store records locally with the required integrity controls (the “SIF” option).

Software requirements that matter

VeriFactu’s deadlines are the most immediate, and your invoicing software needs to meet all of these:

  • Spain has intentionally begun phasing out non-compliant invoicing software 
  • Corporate taxpayers must use VeriFactu-compliant systems by January 1, 2027
  • Self-employed and other taxpayers must comply by July 1, 2027
  • Software must produce chained hash records, QR codes and timestamps for every invoice
  • Records must be unalterable once created

Businesses already complying with SII are exempt from VeriFactu’s software certification requirements. Since SII already provides AEAT with real-time invoice data, the anti-fraud protections VeriFactu addresses are already covered.

VeriFactu vs. B2B e-invoicing

These two regimes are complementary, not interchangeable. A single business may be subject to both simultaneously.

VeriFactu B2B e-invoicing (Crea y Crece)
What it regulates How your software generates and stores invoice records How invoices are exchanged between trading partners
Legal basis Royal Decree 1007/2023 (Anti-Fraud Law) Royal Decree 238/2026 (Crea y Crece Law)
Goals Prevent invoice fraud and manipulation Combat late payments and digitalize B2B transactions
What it requires Tamper-proof records, hash chains, QR codes, timestamps Structured invoice format, platform exchange, status reporting, payment date reporting
Deadlines Jan 2027 (corporate); July 2027 (self-employed) 12/24 months after Ministerial Order is published

How Spain e-invoicing relates to SII and B2G invoicing 

Venn diagram showing Spain's four overlapping e-invoicing compliance regimes: B2B e-invoicing (Crea y Crece), VeriFactu, SII, and B2G (FACe). Overlapping zones indicate shared obligations: B2B and SII require platform integration, B2B and VeriFactu require separate compliance, SII and VeriFactu share an exemption, and B2B and B2G require dual-format planning across EN 16931 and Facturae standards.

Spain’s overlapping compliance regimes create confusion because they use similar terminology but serve different purposes. Separating them by what they do and who they affect operationally makes the planning clearer.

Regime Purpose Who cares operationally
SII (Suministro Inmediato de Información)
  • Real-time VAT data reporting
  • Structured XML submission of invoice data to AEAT within four calendar days of issuance or receipt
  • Tax teams and IT at large businesses (€6M+ turnover) and VAT groups
  • Mandatory since July 2017
B2G (FACe) Electronic invoicing to public sector entities through a centralized government portal
  • AR teams at any business invoicing Spanish public administrations
  • Mandatory since January 2015 using Facturae format
B2B e-invoicing Structured invoice exchange between businesses with status and payment reporting
  • Finance, AP, AR and IT across all Spanish businesses
  • Will be phased in; dates not yet announced
VeriFactu Billing software certification ensuring tamper-proof invoice records
  • IT and software vendors for businesses not already under SII
  • January/July 2027

SII is already live. However, it doesn’t dictate invoice format. A business under SII can still issue PDF invoices and report the data separately. The new B2B mandate changes that by requiring structured formats for the invoices themselves.

Meanwhile, B2G invoicing through FACe uses the Facturae format, which differs from the EN 16931/UBL format the B2B mandate requires. As a result, finance teams should plan for format coexistence rather than assuming one solution covers both.

What finance and ERP teams should do before Spain deadlines tighten

Waiting for the Ministerial Order before starting preparation is one of the most common mistakes. VeriFactu deadlines are already set, data quality issues take months to resolve and platform evaluation requires understanding your transaction landscape.

Software and data readiness

When you’re getting your software and data ready for upcoming Spain deadlines, start with what you know. 

Your invoicing software needs to be VeriFactu-compliant by January 2027 (corporate) or July 2027 (self-employed). Confirm with your vendor that their compliance roadmap is on track. 

For B2B e-invoicing, your business needs to generate EN 16931-compliant structured invoices, connect to AEAT’s public platform or a certified private platform and handle invoice status reporting and payment date transmission.

Data readiness is where most teams underestimate the work. Customer and vendor master files need accurate tax identification numbers (NIF/CIF), your invoice templates need to support structured format fields and your payment workflows need to capture and transmit payment dates to the platform.

Workflow ownership

B2B e-invoicing in Spain touches more teams than typical compliance projects:

  • AR teams own outbound invoice accuracy, format compliance and status monitoring
  • AP teams must respond to incoming invoices (accept/reject) and ensure payment dates are reported
  • Tax teams manage SII reporting, VeriFactu compliance and the overlap between regimes
  • IT teams handle platform connectivity, software certification and integration between ERPs and the public or private e-invoicing platform

Readiness checklist

Use this checklist as a starting point for tracking your preparation across all three mandates:

  1. Map your regime exposure: Determine which of SII, VeriFactu, B2B e-invoicing and B2G apply to your business.
  2. Confirm VeriFactu software compliance: Verify your e-invoicing software vendor’s certification timeline against January/July 2027 deadlines.
  3. Audit master data quality: Validate NIF/CIF numbers, addresses and tax classifications in customer and vendor records.
  4. Evaluate platform options: Compare AEAT’s public solution against private platforms based on your invoice volume, trading partner landscape and ERP integration needs.
  5. Design status reporting workflows: Build processes for AP teams to accept and reject invoices and for payment dates to flow to the platform automatically.
  6. Plan for dual-format transition: If it applies to your business, prepare to send PDF copies alongside e-invoices during the period before smaller recipients are required to receive structured invoices.
  7. Coordinate across regimes: Ensure SII reporting, VeriFactu records and B2B e-invoicing don’t create duplicate or conflicting data submissions.

How to avoid compliance risk when implementing e-invoicing in Spain 

Spain’s overlapping regimes create specific failure modes that finance teams should anticipate.These are the most common mistakes and how to avoid them when it comes to implementing Spain’s new e-invoicing mandates.

Mistake Consequence Stronger approach
Waiting for final B2B dates to start preparing
  • VeriFactu deadlines arrive first (Jan/July 2027)
  • Data cleanup and platform evaluation take months
  • Start VeriFactu and data readiness now
  • Treat B2B platform evaluation as parallel workstream
Treating VeriFactu and B2B e-invoicing as the same project
  • Misaligned timelines
  • Wrong software requirements
  • Gaps in whichever regime was deprioritized
  • Map each regime separately
  • Coordinate where they overlap
Underestimating recipient-side process change
  • AP teams miss the response window
  • Invoices auto-accept without review
  • Payment dates don’t reach the platform
  • Redesign AP workflows to include status response and payment date reporting as mandatory steps

Zone & Co is monitoring e-invoicing developments across Europe, including Spain, as requirements continue to evolve. Businesses with Spanish entities should begin assessing their invoice workflows, data readiness and compliance obligations now, while confirming final requirements with local tax advisors or official AEAT guidance.

FAQs

  • When does Spain e-invoicing become mandatory?
    • There are several Spain e-invoicing deadlines to keep in mind: 
      • VeriFactu: January 1, 2027 (corporate taxpayers) or July 1, 2027 (self-employed)
      • B2B e-invoicing (large businesses): 12 months after Ministerial Order publication for businesses with turnover > €8M
      • B2B e-invoicing (all others): 24 months after Ministerial Order publication 
      • SII: Already mandatory since July 2017 for large taxpayers (€6M+ turnover)
      • B2G: Already mandatory since January 2015
  • What is VeriFactu in Spain?
    • VeriFactu Spain is a billing software certification regime under Royal Decree 1007/2023 that requires invoicing systems to produce tamper-proof, sequentially chained records. These records must have digital fingerprints, QR codes and timestamps. 
    • The goal is to prevent invoice manipulation after issuance. This decree is separate from the B2B invoice exchange mandate, but businesses already under SII are exempt from software certification requirements.
  • Is VeriFactu the same as Spain’s B2B mandate?
    • No, VeriFactu and Spain’s B2B e-invoicing mandate are two separate regulations. VeriFactu regulates how your software generates and stores invoice records. 
    • The B2B e-invoicing mandate under Royal Decree 238/2026 regulates how invoices are exchanged between businesses, including format requirements, platform transmission and status reporting. A business can be subject to both simultaneously since they’re complementary and not interchangeable.
  • How is SII different from Spain e-invoicing regulations?
    • SII (Suministro Inmediato de Información) is a real-time VAT data reporting system that’s been mandatory since July 2017 for large taxpayers with €6M+ annual turnover. Businesses must submit invoice record data to AEAT within four calendar days, but SII doesn’t require structured invoice formats. This means you can issue PDFs and report the data separately. 
    • The B2B e-invoicing mandate, however, requires the invoices themselves to be structured and exchanged through certified platforms.
  • What should finance teams do first?
    • If Spain’s e-invoicing mandates affect you, don’t wait for the Ministerial Order. VeriFactu deadlines actually arrive first, and data cleanup often takes longer than expected. Here’s what you should do first: 
      • Map which regimes apply to your business – SII, VeriFactu, B2B e-invoicing, B2G or a combination
      • Confirm your software vendor’s VeriFactu compliance timeline
      • Audit your master data quality (NIF/CIF numbers, tax classifications)
      • Begin evaluating platform options for B2B e-invoicing

11 minute read

Get a Personalized Demo Today

Start a conversation with an expert who asks thoughtful questions and shows you how Zone & Co can solve your unique problem.

Book a demo