Spain E-Invoicing: VeriFactu, SII, TicketBAI & Crea y Crece Guide

Spain doesn't have one e-invoicing system. It has six, running simultaneously, each triggered by different criteria: how large your company is, where it's tax-resident, and what type of transaction you're issuing invoices for. No other EU member state has fragmented its invoicing compliance obligations to this degree.

If you operate in Spain or transact with Spanish businesses, you need to understand which of these six systems apply to your situation, because the answer is rarely just one.

SII (Suministro Inmediato de Información) requires companies with annual turnover above EUR 6 million to report invoice data to the Agencia Estatal de Administración Tributaria (AEAT) in near real-time, within four days of issuance. VeriFactu (Verificación de Facturas), the nationwide certified invoicing software mandate, becomes obligatory for corporate tax payers from January 2027 and for all remaining businesses by July 2027. TicketBAI is the Basque Country's own anti-fraud invoicing system, already mandatory across Bizkaia, Gipuzkoa, and Araba, replacing VeriFactu entirely for businesses tax-resident in those provinces. NaTicket serves the same function in Navarra, operating under that region's separate tax authority. FACe and Facturae govern electronic invoicing with Spain's public sector, requiring structured XML invoices submitted through a centralized government portal. And Crea y Crece, the forthcoming B2B e-invoicing mandate, will extend mandatory electronic invoicing to all business-to-business transactions, with implementation expected between 2027 and 2028 depending on company size.

The practical consequence: a mid-sized company headquartered in Bilbao that supplies both government agencies and private-sector clients could be subject to TicketBAI, FACe, and Crea y Crece simultaneously, each with its own technical format, submission channel, and deadline structure.

Spain's push toward digital tax enforcement is part of a broader European response to the VAT compliance gap. EU Member States lost EUR 89 billion in VAT revenue in 2022, a figure that has driven governments across the continent toward real-time digital reporting as the primary enforcement mechanism. Spain has been more aggressive than most, layering national mandates on top of regional systems that were already in place rather than consolidating into a single framework.

The sections that follow break down each system individually: what it requires, who it applies to, the technical specifications involved, and the deadlines you need to track. The goal is to give you a single reference point for Spain's e-invoicing requirements so you can map your specific compliance obligations based on your business size, location, and transaction types.

Which System Applies to Your Business?

Determining which of Spain's e-invoicing systems apply to your business requires working through three sequential criteria: where you are tax-resident, how much revenue you generate, and what types of transactions you conduct. The critical point most guides miss is that these systems are not mutually exclusive — a single business can be subject to multiple systems simultaneously.

Step 1: Where Is Your Tax Residence?

Your geographic tax residence within Spain is the first and most decisive factor.

Basque Country (País Vasco). If your business is tax-resident in Álava, Bizkaia, or Gipuzkoa, you fall under TicketBAI, the region's anti-fraud invoicing system. Bizkaia adds an additional layer called Batuz, which includes the LROE (Libro Registro de Operaciones Económicas) — a local bookkeeping ledger requirement on top of TicketBAI. TicketBAI operates independently from Spain's national systems, so your obligations here are governed by the Basque provincial tax authorities, not the Agencia Tributaria.

Navarra. Navarra has legislated its own system called NaTicket, modeled on TicketBAI. Initial rollout is planned across 2025 and 2026, though specific sector-by-sector timelines are still being finalized. Businesses tax-resident in Navarra should monitor developments from the Hacienda Foral de Navarra.

Rest of Spain. If your tax residence is anywhere else in Spain — Madrid, Catalonia, Andalusia, Valencia, or any other common territory — proceed to Step 2.

Step 2: What Is Your Annual Turnover?

For businesses in common territory (outside the Basque Country and Navarra), turnover determines which anti-fraud invoicing system applies.

Above EUR 6 million annual turnover (or you are a member of a VAT group, or registered in REDEME — the monthly VAT refund register): SII (Suministro Inmediato de Información) is mandatory. You must report invoice records to the Agencia Tributaria within four calendar days of issuance or receipt. Under Royal Decree 254/2025, SII-obligated businesses are explicitly exempt from VeriFactu — you will not need to implement VeriFactu-certified software.

Below EUR 6 million annual turnover: VeriFactu applies. Starting in 2027, your invoicing software must meet the certification and reporting requirements established by Royal Decree 1007/2023 and refined by Royal Decree 254/2025. The Spain e-invoicing 2027 deadlines vary depending on your tax regime — corporate taxpayers face a January 2027 start, while other taxpayers begin in July 2027.

Businesses below the EUR 6 million threshold may also voluntarily opt in to SII during November of the preceding year, committing for a minimum of one calendar year. Opting in brings the same real-time reporting obligations but exempts the business from VeriFactu.

Step 3: What Types of Transactions Do You Conduct?

Regardless of which anti-fraud system applies from Steps 1 and 2, two additional e-invoicing layers may apply based on your transaction types.

Invoices to Spanish public sector bodies. If you supply goods or services to government entities and the invoice exceeds EUR 5,000, you must submit structured electronic invoices through FACe (the central e-invoice submission portal) using the Facturae XML format. This B2G (business-to-government) requirement already applies today and is independent of VeriFactu, SII, or TicketBAI.

Domestic B2B transactions. The Crea y Crece law (Ley 18/2022) mandates structured e-invoicing for all B2B transactions between Spanish businesses. Implementation regulations are still pending, with current estimates pointing to 2027–2028 for phased rollout. When active, this will layer on top of whichever anti-fraud system your business already uses.

How Systems Overlap in Practice

Consider a concrete scenario: a company headquartered in Madrid with annual turnover above EUR 6 million that invoices both government agencies and private Spanish businesses. This company would be subject to SII (real-time VAT reporting due to turnover), FACe/Facturae (structured e-invoices for its public sector clients), and eventually Crea y Crece (structured e-invoicing for its domestic B2B sales) — three systems running concurrently, each with its own format, submission channel, and timeline.

The key interactions to understand:

SII and VeriFactu are mutually exclusive. If you are on SII, Royal Decree 254/2025 exempts you from Spain VeriFactu requirements. You do not need VeriFactu-certified software.
TicketBAI is entirely separate. It is governed by the Basque provincial authorities and does not interact with SII or VeriFactu. Basque businesses follow TicketBAI regardless of turnover.
FACe and Crea y Crece are additional layers. They apply based on transaction type, not as alternatives to your anti-fraud system. A business subject to VeriFactu, SII, or TicketBAI may also need to comply with FACe, Crea y Crece, or both.

Quick Reference: All Six Systems at a Glance

System	Who It Applies To	Current Status	Primary Function
SII	Companies with turnover above EUR 6M, VAT groups, REDEME registrants	Active since 2017	Real-time VAT invoice reporting to Agencia Tributaria
VeriFactu	All other common-territory businesses (under EUR 6M turnover)	Mandatory from Jan/Jul 2027	Certified invoicing software with optional real-time reporting
TicketBAI	Businesses tax-resident in Álava, Bizkaia, or Gipuzkoa	Active (phased by territory)	Anti-fraud invoice chaining and reporting to Basque tax authorities
Batuz/LROE	Businesses tax-resident in Bizkaia specifically	Active	TicketBAI + local bookkeeping ledger (LROE)
FACe/Facturae	Any business invoicing Spanish public sector (above EUR 5,000)	Active since 2015	B2G structured e-invoice submission in Facturae XML format
Crea y Crece	All businesses conducting domestic B2B transactions	Pending (estimated 2027–2028)	Mandatory structured B2B e-invoicing between Spanish businesses

SII: Real-Time VAT Reporting for Large Companies

Spain's Suministro Inmediato de Información, or SII, is the country's real-time VAT reporting framework administered by AEAT. Mandatory since July 2017, it stands as the longest-established of Spain's digital invoicing compliance systems and has served as a reference point for similar initiatives across the EU.

Who Must Comply with SII

SII applies to a defined set of taxpayers whose scale or registration status places them under heightened VAT oversight:

Companies with annual turnover exceeding EUR 6 million — the primary threshold that captures most large enterprises operating in Spain
VAT groups (grupos de entidades en IVA) regardless of individual member turnover
REDEME registrants — businesses enrolled in Spain's monthly VAT refund scheme (Registro de Devolución Mensual del IVA), who trade faster refund cycles for real-time reporting obligations
Non-resident businesses exceeding the EUR 6 million turnover threshold from Spanish operations

Any business below these thresholds may voluntarily opt in to SII during November of the preceding year. Opting in commits the business for a minimum of one calendar year and brings the same reporting obligations and deadlines as mandatory participants.

Companies already subject to SII are exempt from VeriFactu requirements. If your business reports through SII, you do not need to implement VeriFactu-certified invoicing software — the real-time reporting obligation is considered satisfied through SII's more rigorous bilateral reporting framework.

How Real-Time Reporting Works

SII requires the electronic submission of structured invoice data for both issued invoices (libro registro de facturas expedidas) and received invoices (libro registro de facturas recibidas) to AEAT's servers. This bilateral reporting — covering sales and purchase invoices alike — is a key distinction from VeriFactu, which addresses only issued invoices.

Rather than transmitting complete invoice documents, SII transmits invoice register data: identification fields, counterparty details, tax bases, VAT rates, and amounts. AEAT uses this data to pre-populate VAT returns and cross-reference transactions between buyers and sellers in near real time.

Reporting deadlines are tight. Issued invoices must be reported within 4 calendar days of the invoice date, excluding Saturdays, Sundays, and national holidays. When a third party issues invoices on behalf of the taxpayer, the window extends to 8 calendar days. In all cases, submission must occur before the 16th of the month following the taxable supply. These deadlines apply per invoice — there is no batching grace period that resets the clock.

Technical Requirements

SII submissions follow a specific technical architecture:

Format: XML documents conforming to AEAT's published schema specifications
Transmission: Web services (SOAP-based) connecting directly to AEAT's SII platform, supporting up to 10,000 invoice records per shipment. A web form alternative exists for lower-volume corrections or manual submissions, though it is impractical for obligated companies processing thousands of invoices monthly.
Authentication: A recognized digital certificate (certificado electrónico) is required for all submissions. This is typically a FNMT certificate for Spanish entities or an EU-qualified electronic certificate for non-residents.
Response handling: AEAT returns acceptance or rejection messages per record, requiring systems to process responses and resubmit corrected records within the original deadlines where possible.

Most ERP and accounting platforms serving the Spanish market have built SII modules or connectors, given the system's nearly decade-long operational history.

What SII Replaces

One tangible benefit of SII compliance is the elimination of several standalone reporting obligations. SII participants are no longer required to file:

Form 340 — the informative declaration of operations included in VAT books
Form 347 — the annual declaration of operations with third parties exceeding EUR 3,005.06
Form 390 — the annual VAT summary return

This consolidation reduces the separate reporting burden significantly, channeling what were periodic batch filings into the continuous real-time data stream that SII maintains.

Penalty Structure

AEAT enforces SII compliance through a graduated penalty framework:

Violation	Penalty
Late submission of invoice records	0.5% of the invoice amount per record, with a minimum of EUR 300 and a maximum of EUR 6,000 per quarter
Incorrect or incomplete data in submitted records	1% of the affected invoice amounts
Complete failure to report (non-submission of required books)	1% of annual turnover reflected in the unreported records

The quarterly cap on late-submission penalties provides some containment for businesses experiencing temporary system failures, but the per-record minimum of EUR 300 means even a small number of missed invoices can generate substantial exposure quickly.

SII in the European Context

Spain was among the first EU member states to implement real-time VAT reporting at scale, and SII's design has influenced subsequent systems across the continent. Italy's Sistema di Interscambio (SDI) launched mandatory e-invoicing in 2019 with a similar real-time philosophy. Hungary's RTIR system requires real-time invoice data reporting above certain thresholds. Portugal's e-Fatura real-time invoice reporting system shares SII's goal of closing the VAT gap through transaction-level visibility, though its technical implementation differs. Poland's KSeF mandatory e-invoicing rollout, Romania, and France are each advancing their own real-time reporting frameworks through 2026 and beyond.

For multinational businesses operating across several EU jurisdictions, SII compliance experience translates well — the core concepts of structured data submission, tight reporting windows, and digital certificate authentication recur throughout these systems, even where specific schemas and platforms diverge.

VeriFactu: Certified Invoicing Software Requirements

VeriFactu is the anti-fraud certified invoicing software system that will affect more Spanish businesses than any other compliance regime. If your company falls below the SII threshold of EUR 6 million in annual turnover, operates outside the Basque Country, and is not based in Navarra, VeriFactu applies to you. That scope covers the vast majority of Spanish businesses and self-employed professionals (autónomos).

The legal foundation rests on three pieces of legislation. Royal Decree 1007/2023 established the core technical requirements for certified invoicing systems. Royal Decree 254/2025 refined those requirements and formally confirmed that businesses already reporting through SII are exempt from VeriFactu obligations. RD-ley 15/2025, published in December 2025, pushed back the mandatory compliance dates from their originally planned schedule.

Mandatory Compliance Dates

The current timeline, as set by RD-ley 15/2025:

July 29, 2025 — Software developers must have certified VeriFactu-compliant software available for sale or distribution
January 1, 2027 — Mandatory for all Corporate Tax (Impuesto sobre Sociedades) payers
July 1, 2027 — Mandatory for all remaining taxpayers, including self-employed persons filing under IRPF

From these dates forward, businesses can no longer issue invoices using Word documents, Excel spreadsheets, generic PDF templates, or any uncertified invoicing tool. Every piece of software used to generate invoices must meet the technical certification standards defined in the regulation.

How VeriFactu Works: Core Technical Requirements

VeriFactu imposes three fundamental technical requirements on all invoicing software, regardless of which compliance mode a business selects.

Chained hash records (huella). Every invoice generates a cryptographic hash that links it to the previous invoice in an unbroken chain. This mechanism makes it technically impossible to modify, delete, or insert invoices after issuance without breaking the chain and leaving detectable evidence of tampering. The hash chain creates a tamper-proof audit trail that AEAT can verify at any time.

QR codes on every invoice. Each issued invoice must carry a QR code that enables verification. Both AEAT inspectors and invoice recipients can scan this code to confirm the invoice's authenticity and check whether it has been reported to the tax authority. This gives customers a direct way to verify that the invoices they receive correspond to legitimate, reported transactions.

Formal rectification invoices for corrections. Once an invoice is issued, it cannot be edited or deleted within the system. Any correction, whether for an error in amounts, tax rates, or customer details, requires issuing a formal rectification invoice (factura rectificativa) that references the original document. This eliminates the possibility of quietly altering invoice records after the fact.

One important distinction from SII: VeriFactu covers issued invoices only. Businesses are not required to report received invoices through this system, whereas SII mandates reporting on both sides of transactions.

Two Compliance Modes

Businesses subject to VeriFactu must choose between two modes of operation. Both require the same tamper-proof record-keeping infrastructure described above. The difference lies in how and when invoice data reaches AEAT.

VeriFactu mode (real-time reporting). Invoice records are transmitted to AEAT automatically at the time of issuance. This is the more transparent option and provides the closest parallel to SII's real-time reporting model. Businesses operating in this mode benefit from AEAT having immediate visibility into their invoicing activity, which can simplify future inspections and reduce compliance friction. Invoices issued under this mode can carry the designation "VeriFactu" on the document itself.

Non-VeriFactu mode (local storage with digital signature). Invoice records are stored locally within the certified software, secured with a digital signature rather than transmitted to AEAT in real time. The tax authority can request these records during an inspection, and the chained hash system ensures their integrity. This mode suits businesses that prefer not to share invoice data continuously but still must maintain the full tamper-proof record structure.

Both modes satisfy the legal obligation. However, businesses should consider that operating in VeriFactu mode with real-time reporting may reduce scrutiny during tax audits, since AEAT already holds the data.

Software Certification in Practice

Software vendors are responsible for building VeriFactu-compliant products and making them available by the July 29, 2025 certification deadline. AEAT is expected to publish guidance on how software compliance will be verified. In the interim, businesses should confirm directly with their invoicing software provider that a VeriFactu-certified update is planned before the applicable deadline. If your current provider has not announced VeriFactu support, begin evaluating alternatives now — the transition from uncertified tools to compliant software requires testing and workflow adjustment that should not be compressed into the final weeks before enforcement begins.

Penalties for Non-Compliance

The penalty structure targets both businesses and software providers separately:

Businesses using non-compliant invoicing software face fines of up to EUR 50,000 per fiscal year
Software developers and providers supplying invoicing software that does not meet VeriFactu technical specifications face fines of up to EUR 150,000 per client using their non-compliant product

These penalties create dual-sided enforcement pressure. Software vendors have strong financial incentive to certify their products before the mandatory dates, and businesses face material consequences for failing to migrate away from non-compliant tools. For companies still generating invoices through spreadsheets or basic document editors, the transition to certified software is not optional — it is a regulatory requirement with significant financial exposure for non-compliance.

TicketBAI, Batuz, and NaTicket: Regional Anti-Fraud Systems

Spain's autonomous communities with independent tax authority — the Basque Country and Navarra — operate their own anti-fraud invoicing systems entirely separate from the national VeriFactu framework. Businesses in these regions follow different rules, different timelines, and different software certification requirements. Understanding which system governs your obligations depends entirely on where your tax residency falls.

TicketBAI: The Basque Country's Invoicing Framework

TicketBAI is the mandatory anti-fraud invoicing system across the Basque Country's three provinces: Araba/Álava, Gipuzkoa, and Bizkaia. The system requires all businesses and self-employed professionals to use certified invoicing software that produces tamper-proof records of every invoicing operation, transmitted to the corresponding provincial tax authority (Diputación Foral).

Each province has implemented TicketBAI on its own schedule:

Gipuzkoa has been fully mandatory since June 2023, making it the first province to complete rollout across all taxpayer segments.
Araba/Álava is mandatory, with all obligated taxpayers now required to comply.
Bizkaia is completing its phased rollout through 2026, with different sectors reaching their mandatory adoption dates progressively.

The technical requirements are specific and non-negotiable. Certified invoicing software must:

Generate XML records with digital signatures for every invoice issued, creating a verifiable audit trail that the tax authority can authenticate.
Maintain a hash chain linking each invoice to the previous one. This chain-link structure means any attempt to delete or alter an invoice breaks the cryptographic sequence, making tampering immediately detectable.
Produce a QR code (30 to 40mm) printed on every invoice. This QR allows the tax authority — and even the invoice recipient — to verify the invoice was properly registered.
Assign a TBAI identifier to each invoice, a unique code that serves as the invoice's fingerprint within the TicketBAI system.

Software used for TicketBAI compliance must be listed in the Approved Software Register maintained by each province. This is not a self-certification process — vendors must demonstrate their software meets the technical specifications before being included in the register.

One critical distinction from VeriFactu: TicketBAI's design assumes constant internet connectivity for real-time transmission of invoice data to the provincial tax authority. Unlike VeriFactu, which includes a structured "incident mode" allowing businesses to continue issuing invoices offline and synchronize later, TicketBAI does not provide the same formalized fallback mechanism. Businesses must plan their infrastructure accordingly.

Batuz: Bizkaia's Extended System

Bizkaia does not stop at TicketBAI. The province operates Batuz, a broader compliance framework comprising three components:

TicketBAI-compliant invoicing software — the base layer, identical in function to what Gipuzkoa and Araba require.
LROE (Libro Registro de Operaciones Económicas) — an electronic operations ledger where businesses report all economic operations to the Bizkaia tax authority. The LROE goes beyond invoices to capture a complete picture of business activity, including issued invoices, received invoices, and other financial transactions.
Pre-populated draft tax returns — the Bizkaia tax authority uses LROE data to automatically generate draft income tax and corporate tax returns. Taxpayers review and confirm or adjust these drafts rather than building returns from scratch.

Batuz effectively creates a closed loop: invoice data flows into the LROE, the LROE feeds draft tax returns, and the tax authority gains near-complete visibility into business transactions. For businesses operating in Bizkaia, compliance means satisfying all three components, not just the invoicing software requirement.

NaTicket: Navarra's Parallel System

Navarra, which maintains its own tax authority (Hacienda Foral de Navarra) separate from both the national government and the Basque provinces, is developing NaTicket as its independent anti-fraud invoicing system. The Navarra government approved the NaTicket roadmap in 2023, with rollout planned across 2025 and 2026.

NaTicket shares similar technical foundations with TicketBAI: mandatory QR codes on invoices, unique invoice identification files, and immediate communication of invoice data to the Navarra tax authority. The system aims to prevent unreported transactions and invoice manipulation through the same cryptographic and real-time reporting principles that TicketBAI employs.

Almost no English-language documentation exists for NaTicket at this stage. Businesses with operations or clients in Navarra should monitor announcements from Hacienda Foral de Navarra directly, as the implementation details and mandatory adoption dates are still being finalized.

How These Systems Relate to National Obligations

A point that causes frequent confusion: TicketBAI is completely separate from SII. Businesses tax-resident in the Basque Country are not part of the national SII real-time reporting system and will not be subject to VeriFactu when it becomes mandatory nationally. The Basque provinces operate their own tax administrations with independent authority over invoicing compliance.

The same principle applies to Navarra — NaTicket will govern invoicing obligations there, not VeriFactu.

This means a company with operations across Spain may face different invoicing compliance systems depending on where each entity is tax-resident. A subsidiary in Bizkaia follows Batuz. A subsidiary in Madrid follows VeriFactu. A subsidiary in Gipuzkoa follows TicketBAI. There is no single unified system, and compliance with one does not satisfy the requirements of another.

FACe, Facturae, and Crea y Crece: Public Sector and B2B E-Invoicing

Beyond the anti-fraud invoicing systems described above, Spain maintains separate e-invoicing obligations for public sector suppliers and is preparing a sweeping B2B e-invoicing mandate. These are not alternatives to SII, VeriFactu, or TicketBAI. They are additional layers that apply on top of whichever anti-fraud regime governs your business.

FACe: Mandatory B2G E-Invoicing Since 2015

Spain's Punto General de Entrada de Facturas Electrónicas (FACe) has required electronic invoicing for all invoices above EUR 5,000 submitted to Spanish public sector bodies since January 2015. This obligation applies equally to domestic suppliers and foreign businesses contracting with Spanish government entities.

FACe invoices must use the Facturae XML format (current version 3.2.2) and carry an XAdES advanced electronic signature. The format is compliant with the European standard EN 16931, ensuring interoperability across EU public procurement systems. Suppliers submit invoices either through the FACe web portal or via its web service API, which allows integration with existing ERP and accounting platforms.

All Spanish regions route public sector invoices through FACe with one exception: the Basque Country maintains its own entry point. For businesses already invoicing the Spanish public sector, FACe compliance is a settled obligation. For those entering Spanish public procurement for the first time, the Facturae format and digital signature requirements represent a distinct technical workstream from whatever anti-fraud system applies to the rest of their Spanish operations.

Crea y Crece: The Coming B2B E-Invoicing Mandate

Ley 18/2022, commonly known as Crea y Crece, will extend mandatory e-invoicing to all domestic business-to-business transactions in Spain. The rollout follows a phased timeline tied to company size:

Large companies (annual turnover above EUR 8 million): mandatory from approximately 2027
All other businesses: mandatory from approximately 2028

These dates remain approximate because the final implementing regulations have not yet been gazetted. The law requires a 12-month notice period after publication of those regulations before obligations take effect, so the exact activation dates will only become certain once the regulatory text is finalized.

Crea y Crece adopts a Y-scheme model for e-invoice exchange. Businesses can transmit invoices through certified private service providers or directly via the public SPFE (Solución Pública de Facturación Electrónica) platform. Accepted invoice formats include UBL, CII, EDIFACT, and Facturae, all of which must be EN 16931-compliant. One critical technical detail: the "copia fiel" (faithful copy) that must be submitted to the SPFE is required in UBL format, regardless of which format is used for the original exchange between trading partners.

The mandate introduces several operational requirements that will affect accounts payable and receivable workflows:

4-day acceptance or rejection window for received invoices
Mandatory payment status reporting through the platform
30-day default payment terms, extendable to a maximum of 60 days by written agreement between parties

These payment discipline provisions reflect one of the law's core objectives: reducing late payment practices that disproportionately affect smaller businesses.

Scope Boundaries and the EU Context

Crea y Crece covers B2B domestic transactions only. Cross-border B2B e-invoicing between EU member states falls outside its scope and will instead be addressed by the EU's VAT in the Digital Age (ViDA) initiative, which establishes mandatory cross-border e-invoicing and digital reporting from July 2030. Spain is far from alone in this trajectory. Countries across the EU are implementing or planning domestic e-invoicing mandates ahead of ViDA, as seen with Greece's myDATA e-invoicing requirements and similar programs in Italy, Poland, and France.

For businesses operating in Spain, the practical consequence is straightforward: FACe and Crea y Crece obligations stack on top of your existing anti-fraud compliance. A company subject to SII reporting will also need to submit Facturae-format invoices through FACe for public sector contracts and exchange structured e-invoices with domestic B2B partners once Crea y Crece activates. The same layering applies to businesses under VeriFactu or TicketBAI. Planning for Crea y Crece readiness now, while the implementing regulations are still pending, means evaluating whether your current invoicing software can produce EN 16931-compliant UBL output and connect to the SPFE platform or a certified private service provider.

Key Compliance Deadlines: 2025 Through 2030

Spain's e-invoicing obligations involve overlapping timelines across multiple systems, and several dates have already shifted due to legislative delays. The following consolidated timeline captures every critical milestone from established mandates through upcoming requirements.

Date	System	Milestone
January 2015	FACe / Facturae	B2G e-invoicing mandatory for invoices above EUR 5,000 to public administrations
July 2017	SII	Real-time VAT reporting mandatory for companies with annual turnover above EUR 6 million
2020 — June 2023	TicketBAI	Phased rollout across Basque Country provinces, with Gipuzkoa reaching full mandatory status by June 2023
2025 — 2026	TicketBAI / Batuz / NaTicket	Bizkaia completing its Batuz rollout; Navarra phasing in NaTicket for regional taxpayers
July 29, 2025	VeriFactu	Software developers must have VeriFactu-certified invoicing software available on the market
January 1, 2027	VeriFactu	Mandatory for all Corporate Tax (Impuesto sobre Sociedades) payers
July 1, 2027	VeriFactu	Mandatory for all remaining taxpayers not already covered
~2027	Crea y Crece	B2B e-invoicing mandatory for companies with annual turnover above EUR 8 million (pending implementing regulations)
~2028	Crea y Crece	B2B e-invoicing mandatory for all remaining businesses
July 1, 2030	EU ViDA	Cross-border B2B e-invoicing and real-time digital reporting begin under the VAT in the Digital Age framework

A note on reliability of future dates. The VeriFactu deadlines listed above reflect the most recent postponement under RD-ley 15/2025, published in December 2025. Prior to that decree, the mandatory dates for taxpayers were set a full year earlier. The Crea y Crece B2B mandate carries even more uncertainty — the implementing regulations that would define the exact technical standards and rollout schedule have not yet been published. Approximate dates for Crea y Crece are based on the timelines outlined in Law 18/2022 and subsequent regulatory proposals, but they remain subject to change until the final royal decree is enacted.

The delays reflect a combination of factors: the complexity of coordinating national and regional systems, the time required for Spain's legislative process to produce detailed implementing regulations, and industry readiness concerns from software vendors and business associations. While further postponements cannot be ruled out, the July 2025 software certification deadline creates a structural forcing function — once certified software is available on the market, the primary justification for delay (technology readiness) falls away. The prudent approach is to treat published dates as planning targets rather than guaranteed enforcement dates, while monitoring AEAT communications and the BOE (Boletín Oficial del Estado) for updates.

The broader European trajectory. Spain's domestic systems will eventually operate alongside the EU ViDA framework, which introduces mandatory e-invoicing and real-time digital reporting for cross-border B2B transactions starting July 1, 2030. ViDA does not replace Spain's national systems — SII, VeriFactu, and Crea y Crece will continue to govern domestic transactions. However, businesses engaged in intra-EU trade will need their invoicing infrastructure to handle both Spanish domestic requirements and the EU-wide standard simultaneously. The convergence toward structured electronic invoicing across Europe means that investments in compliant software and processes today will serve businesses well beyond Spain's borders.

Practical next steps. If you are subject to VeriFactu, confirm your software vendor is on track for the July 2025 certification deadline — this is the earliest external milestone and a leading indicator of readiness. If you operate in the Basque Country and are not yet TicketBAI-compliant, you are already past the mandatory date in two of three provinces. For businesses watching Crea y Crece, the 12-month notice provision after final regulations means the earliest possible activation is roughly a year after gazette publication — monitor the BOE for that trigger event. In all cases, begin testing and internal process changes at least six months before your relevant compliance date. Waiting for regulatory confirmation before starting technical preparation is the most common cause of last-minute compliance failures.