Spain's Mandatory B2B E‑invoicing (late 2026): What Saas Platforms, Marketplaces & Tech Startups Must Do Now

Last reviewed: June 1, 2026

Spain is preparing to mandate B2B e‑invoicing for domestic transactions under a phased rollout that begins in late 2026 and extends through 2028. Rooted in Article 12 of Ley 18/2022, the Ley de Creación y Crecimiento de Empresas (Crea y Crece), the mandate replaces PDF and paper invoicing between businesses with structured, machine‑readable electronic invoicing in Spain. For SaaS platforms, online marketplaces and tech startups operating in or selling into the Spanish market, the change carries immediate implications across product architecture, customer contracts, tax reporting and vendor relationships.

This guide breaks down the legal framework, technical e-invoicing requirements Spain imposes, contractual adjustments every platform must make, and the step‑by‑step project plan that product, finance and legal teams should be executing right now.

What’s Changing: The Legal Basis for B2B E‑Invoicing Spain

Quick answer: Yes, once the implementing regulations take effect, a structured electronic invoice will be required for all domestic B2B transactions between entities established in Spain. PDF invoices sent by email will no longer satisfy the legal obligation.

Legal basis: Ley 18/2022 (Crea y Crece) and the draft Royal Decree

The legislative foundation is Article 12 of Ley 18/2022, published in the Boletín Oficial del Estado (BOE) on September 29, 2022. That article empowers the government to require all entrepreneurs and professionals to issue, transmit and receive structured electronic invoices in their commercial relationships with other businesses. The obligation extends to the entire lifecycle: generation, transmission, receipt and storage.

Implementing the mandate requires a Royal Decree, the detailed technical regulation, which was approved in draft form by the Council of Ministers in March 2026 and submitted for public consultation. Once the final text is published in the BOE, the clock starts on the compliance deadlines for each tranche of affected businesses. Meanwhile, Spain’s mandate aligns with the broader EU initiative known as VAT in the Digital Age (VIDA), which the European Commission has been developing to harmonise e‑invoicing and real‑time reporting across member states.

The practical shift is fundamental. Where businesses previously had discretion over invoice format, often exchanging PDFs via email, the new regime demands structured data files (primarily Facturae XML) transmitted through authorised channels. This is not simply a format upgrade; it changes the data model, the transmission architecture and the legal obligations attached to every invoice your platform generates or facilitates.

Timeline for Mandatory E‑Invoicing Spain: Who Is Affected and When

Quick answer: Mandatory e-invoicing Spain follows a phased rollout. Large enterprises (annual turnover above €8 million) face the earliest deadline, with smaller businesses given additional time. Final dates depend on the publication of the implementing order in the BOE.

The draft Royal Decree establishes a two‑phase approach pegged to annual turnover. The table below summarises the expected timeline, drawing on the draft text and widely reported vendor analyses. Because the final implementing order had not been published in the BOE as of this article’s review date, all dates should be treated as indicative and monitored for updates.

Industry observers expect the final BOE publication to arrive in the second half of 2026, triggering the Phase 1 countdown. SaaS platforms and marketplaces with Spanish operations or Spanish‑resident customers should treat the Phase 1 window as their hard deadline, regardless of their own turnover, because their enterprise clients will require compliant invoicing infrastructure from day one. Waiting for Phase 2 deadlines is a strategic risk if your largest customers are Phase 1 entities.

Scope of B2B E‑Invoicing Spain: Transactions and Entities

Domestic versus cross‑border rules

The Crea y Crece mandate applies to domestic B2B transactions, that is, transactions between entrepreneurs or professionals who are both established in Spain. Cross‑border transactions (where one party is established outside Spain) are not currently in scope of the national mandate, though they may be drawn into EU‑wide requirements once the VIDA framework is finalised and transposed.

For SaaS platforms serving international customer bases, this distinction is critical. If your platform generates invoices for a Spanish seller to a Spanish buyer, that invoice falls within the mandate. If either party is established abroad, the national obligation does not apply, though the platform may still need to support e‑invoicing for those parties under the laws of their home jurisdiction.

Turnover thresholds and exemptions

The draft Royal Decree uses an annual turnover threshold of €8 million to determine phasing. Businesses above this threshold must comply in Phase 1; those below it receive an additional compliance window (Phase 2). The draft does not create a blanket exemption for small businesses, all entrepreneurs and professionals conducting domestic B2B sales will eventually be required to issue structured electronic invoices.

A simple decision framework for platform operators:

• Is the seller established in Spain? If no, the Spanish mandate does not apply to this transaction.
• Is the buyer also established in Spain? If no, the transaction is cross‑border and outside the current domestic scope.
• Is this a B2B transaction? B2C transactions are not covered by the Crea y Crece obligation (though other requirements, such as the Reglamento Verifactu anti‑fraud rules, may apply).
• Does the seller’s annual turnover exceed €8 million? If yes, the seller must comply from Phase 1. If no, Phase 2 applies, but marketplace invoicing Spain operators should plan for both phases simultaneously.

Technical and Format Requirements for B2B E‑Invoice Integration

The technical layer of B2B e‑invoicing Spain is where product teams, CTOs and engineering leads will spend most of their implementation effort. Understanding the required format, the transmission architecture and the available integration patterns is essential for building a compliant, and commercially practical, solution.

Facturae B2B: the required XML format

Quick answer: Facturae is the Spanish government’s structured XML format for electronic invoices. It is already mandatory for B2G (business‑to‑government) invoicing via the FACe portal and is the baseline format for the new B2B mandate.

The Facturae specification, maintained by the Spanish government and published via the official Facturae portal, defines mandatory fields including seller and buyer tax identification (NIF/CIF), invoice number, line items with tax breakdowns, total amounts and currency. Invoices must be digitally signed using an advanced or qualified electronic signature to ensure integrity and authenticity. Version 3.2.2 of the Facturae schema is the current standard, though platforms should monitor for updates tied to the implementing regulation.

The five‑corner model: who is responsible for what

Spain’s B2B e‑invoicing architecture follows a five‑corner model, in contrast to the simpler three‑corner (direct exchange) or four‑corner (network) approaches used in some other jurisdictions. The five actors are:

• Issuer (seller). Generates the structured invoice and submits it to the transmission channel.
• Issuer’s service provider / platform. The SaaS platform or aggregator that facilitates generation and submission.
• Public clearance / reporting node. A government‑operated or government‑authorised node that validates or registers the invoice (linked to the Agencia Tributaria’s existing SII, Suministro Inmediato de Información, infrastructure).
• Receiver’s service provider / platform. The system that ingests the cleared invoice on behalf of the buyer.
• Receiver (buyer). The end recipient who records the invoice in their accounting system.

For SaaS platforms and marketplaces, the key question is which corner(s) your product occupies and what obligations attach to each. If your platform issues invoices on behalf of sellers (common in marketplace models), you are effectively the issuer’s service provider and potentially the issuer of record, which carries direct liability for format compliance and data accuracy.

B2B e‑invoice integration options for platforms

Three primary integration patterns are available. The right choice depends on your platform’s scale, engineering capacity and appetite for ongoing maintenance of compliance logic.

Error handling, identifiers, signatures and retention

Regardless of integration approach, every platform must implement robust handling for:

• Unique invoice identifiers. Each invoice must carry a unique, sequential number traceable through the clearance node. Duplicate or out‑of‑sequence identifiers will be rejected.
• Digital signatures. Advanced or qualified electronic signatures (per eIDAS Regulation standards) are required to authenticate each Facturae document.
• Validation and error responses. The clearance node will return acceptance or rejection messages. Platforms must build automated retry, error‑logging and alerting workflows.
• Audit trail and retention. Spanish tax law requires invoice retention for a minimum of four years. Platforms should store both the original structured file and any clearance‑node acknowledgements, with timestamps, in tamper‑evident storage. This invoice reporting Spain obligation applies to both the issuer and the receiver.

Contracts, Terms and Commercial Steps: SaaS Compliance E‑Invoicing

Quick answer: SaaS providers and marketplaces must update customer agreements, marketplace terms of service and data processing agreements to reflect new invoicing obligations, allocate liability for non‑compliant invoices, and address GDPR considerations arising from structured invoice data.

Customer contracts (SaaS platforms)

If your SaaS product generates invoices for customers, whether as a billing platform, ERP, accounting tool or checkout system, your customer contract must now address who bears responsibility for format compliance, data accuracy and timely submission to the clearance node. The following clause structures are recommended as starting points (and should be adapted with jurisdiction‑specific legal advice):

Sample clause, invoice issuance and format:

“The Platform shall generate all B2B invoices for Customer’s domestic Spanish transactions in Facturae XML format (version 3.2.2 or as subsequently required by law), digitally signed in accordance with the eIDAS Regulation, and shall submit each invoice to the designated clearance node within the timeframe required by applicable Spanish law. Customer shall provide accurate and complete data necessary for invoice generation, including valid NIF/CIF and transaction details.”

Sample clause, data submission and remediation:

“In the event that a submitted invoice is rejected by the clearance node, the Platform shall notify Customer within [24/48] hours and use commercially reasonable efforts to remediate the error and resubmit. Where rejection results from inaccurate data provided by Customer, Customer shall be responsible for supplying corrected data within [timeframe] and shall indemnify the Platform for any penalties arising from the delay.”

Marketplace terms: marketplace invoicing Spain obligations

Marketplace operators face a more complex challenge. Depending on the commercial model, whether the marketplace issues invoices on behalf of sellers, or sellers issue their own invoices through the platform, liability for compliance sits in different places. The implementing regulation is expected to hold the invoice issuer primarily responsible, but marketplace operators who facilitate issuance carry significant exposure.

Sample clause, allocation of liability between marketplace and sellers:

“Seller acknowledges that all invoices issued through the Marketplace for domestic Spanish B2B transactions must comply with the format, signature and submission requirements of Ley 18/2022 and its implementing regulations. Seller shall ensure the accuracy and completeness of all invoice data provided to the Marketplace. Seller shall indemnify the Marketplace against any fines, penalties or claims arising from Seller’s failure to provide compliant data. The Marketplace reserves the right to withhold settlement payments where Seller’s invoices are rejected by the clearance node until compliant resubmission is confirmed.”

Marketplace operators should also update their data processing agreements (DPAs) to cover the personal data elements present in structured invoices, names, NIF numbers, addresses, and conduct a Data Protection Impact Assessment (DPIA) where invoice data flows involve new processing activities or cross‑border transfers.

Practical Implementation Checklist and Risk Matrix

Compliance with B2B e‑invoicing Spain demands coordinated action across product, finance and legal functions. The checklist below assigns ownership and suggested timeframes based on a Phase 1 deadline in late 2026.

• CTO / Head of Product (90 days out): Audit all invoice‑generation workflows; select integration pattern (direct, aggregator or hybrid); provision sandbox environment for Facturae validation testing; implement digital signature infrastructure.
• CFO / Head of Finance (90 days out): Map current invoicing flows to the new scope rules; assess SII reporting alignment; engage external tax adviser to review VAT treatment of e‑invoiced transactions; budget for vendor costs or development resources.
• General Counsel (60 days out): Draft updated customer contract clauses and marketplace terms; review DPAs for invoice data processing; assess indemnity and escrow provisions; prepare board‑level compliance briefing.
• Product Operations / Customer Success (30 days out): Prepare customer communications explaining the transition; build support documentation and FAQ; coordinate pilot rollout with key enterprise customers.

Risk matrix

Next Steps: Board, Investor and GC/CTO Compliance Checklist

For board‑level reporting and investor due diligence, the following one‑page action summary captures the critical milestones:

• Legal review: Confirm scope applicability; engage Spanish technology law counsel for contract drafting and regulatory interpretation.
• Contract updates: Amend SaaS customer agreements, marketplace seller terms and DPAs before Phase 1 enforcement.
• Product milestones: Complete Facturae integration (direct, aggregator or hybrid) with validated test suite; deploy digital signature capability.
• Vendor procurement: If using an aggregator, execute vendor contract with SLA guarantees on uptime, schema updates and sandbox access.
• Pilot testing: Run end‑to‑end invoice submission and clearance tests with at least three enterprise customers before go‑live.
• Customer communications: Notify all affected customers at least 60 days before the compliance deadline; provide migration guides and support channels.

Conclusion

Spain’s mandatory B2B e‑invoicing regime represents one of the most significant compliance shifts for technology businesses operating in the Spanish market in recent years. The convergence of legal obligation, technical specification and contractual risk means that SaaS platforms, marketplaces and tech startups cannot afford to treat this as a back‑office tax project. Product, legal and finance teams must work in parallel, now, to ensure that invoicing infrastructure, customer contracts and operational processes are ready well before the Phase 1 deadline. For businesses seeking specialist guidance on B2B e‑invoicing Spain compliance, contract drafting and technical integration strategy, the Global Law Experts lawyer directory connects you with experienced practitioners in Spanish technology law.

Sources

1. European Commission, eInvoicing in Spain / VIDA Context
2. EDICOM, Electronic Invoicing & Facturae Guidance
3. Tradeshift, B2B E‑Invoicing Mandate in Spain
4. BOE, Ley 18/2022 (Crea y Crece)
5. Agencia Tributaria, Official Administrative Guidance
6. Facturae, Official Technical Specification
7. Storecove, E‑Invoicing Compliance in Spain
8. Ecosio, E‑Invoicing in Spain