Briefing document & Podcast: Spain – E-Invoicing and E-Reporting

Last update: September 24, 2026

Slide deck

 

---

1. Executive Summary

Spain is a frontrunner in digital VAT compliance, characterized by an “aggressive digitaliser” approach, implementing a complex array of overlapping mandates. The country’s e-invoicing landscape is unique within the EU, primarily driven by a focus on late-payment control for its B2B mandate, rather than the VAT fraud prevention seen in most other jurisdictions. This document reviews Spain’s multifaceted digital compliance regimes, including the new B2B e-invoicing mandate under Law 18/2022 (“Crea y Crece”), the VERI*FACTU billing-software regulation, and the long-standing SII (Suministro Inmediato de Información) real-time VAT ledger reporting, alongside B2G e-invoicing via FACe and regional initiatives like TicketBAI. The upcoming Ministerial Order is a critical, yet unpublished, component that will finalize implementation dates.

2. Spain’s Digital Compliance Landscape: An Overview

Spain’s digital compliance ecosystem is built on several parallel, legally distinct regimes, meaning “Complying with one does not exempt a taxpayer from the others.”

• Sequential Digitalization: Spain began its journey with mandatory B2G e-invoicing via FACe in 2015, followed by near-real-time VAT ledger reporting (SII) in 2017. More recently, regional anti-fraud systems (TicketBAI/Batuz) emerged in the Basque provinces, and the VERI*FACTU billing-software regulation was introduced. The latest is the mandatory B2B e-invoicing exchange under Law 18/2022.
• Primary Drivers:
• B2B E-Invoicing (Crea y Crece): “Uniquely in the EU, the primary driver of the B2B mandate is late-payment control, not VAT fraud.” This aims to gather reliable data on payment periods, as Spain’s average B2B payment period is “roughly 80 days against a 60-day legal maximum.” Secondary objectives include SME digitalization, administrative efficiency, and transparency.
• VERI*FACTU and SII: These are explicitly “anti-fraud/VAT-gap instruments.” VERI*FACTU stems from the Anti-Fraud Law 11/2021.
• Positioning: Spain is an “early mover on reporting (SII since 2017…among the first real-time VAT ledger systems in the EU) but a late mover on invoice exchange,” with the B2B mandate slipping to 2027/2028. Its chosen architecture for B2B e-invoicing is a hybrid/decentralised CTC model featuring “accredited private platforms plus a public AEAT solution acting as universal repository.” This is “closer to the French PPF/PDP split than to Italy’s single clearing house SdI.”
• Supranational Authorization: No EU derogation was required for the domestic B2B mandate, as the ViDA Directive (EU) 2025/516, in force since April 14, 2025, amended Articles 218 and 232 of the VAT Directive, allowing Member States to mandate domestic e-invoicing without prior Council authorization or buyer consent.

3. Mandatory B2B E-Invoicing (Crea y Crece)

This is the newest and most impactful mandate, outlined in RD 238/2026.

3.1. Regulatory Framework

• Primary Legislation: Key laws include Ley 56/2007 (Article 2 bis) which defines the obligation to issue, transmit, and receive e-invoices B2B and report statuses, and Ley 18/2022 (“Crea y Crece”), which inserts/amends Article 2 bis.
• Implementing Regulations: Real Decreto 238/2026, de 25 de marzo, is the core B2B e-invoicing regulation, in force since April 20, 2026, though its application is deferred. It amends RD 1619/2012 (Invoicing Regulation).
• Pending Order: A Ministerial Order regulating the Public E-Invoicing Solution (SPFE) is pending, anticipated for publication and entry into force on October 1, 2026. Until then, “the go-live dates are projections, not legal deadlines.”

3.2. Scope of the Mandate

• Transactions In Scope:Domestic B2B: Mandatory for transactions between “entrepreneurs or professionals having in Spain their seat, permanent establishment or…domicile or habitual residence.” This means “PDFs sent by email, paper, Word or images cease to constitute valid invoices for in-scope transactions.”
• Self-billing: “In scope and expressly supported,” with AEAT confirming support in the semantic model.
• Special VAT Regimes: “No specific exclusion exists in RD 238/2026.”
• Transactions Out of Scope:Domestic B2C: “Out of scope of the Crea y Crece mandate,” though covered by VERI*FACTU/TicketBAI.
• Cross-border B2B (Intra-EU outbound), Exports, Imports, Intra-EU acquisitions: These are “out of scope” because the mandate is “limited to Spain-established issuer and Spain-established recipient.”
• Simplified invoices: Excluded, “except ‘qualified’ simplified invoices under Art. 7.2,” which remain in scope.
• Specific exclusions for regulated activities of electricity/gas market operators and IATA clearing systems.
• Taxable Persons in Scope:Established Domestic Entities: “All entrepreneurs and professionals…established in Spain who are obliged to issue an invoice, where the recipient is also a Spain-established entrepreneur/professional.” Turnover above €8m determines timing, not scope. VAT-exempt entities and income-attribution regimes are included.
• Non-established Entities: Those with a “Fixed establishment in Spain” are in scope. However, “VAT-registered but no fixed establishment” are generally “outside the mandate,” though practitioners await further clarification. “No Spanish VAT registration: excluded.”
• Foral Territories: The Basque provinces operate TicketBAI/Batuz instead of VERIFACTU for their taxpayers, determined by tax domicile. Navarra falls under the state VERIFACTU framework.

3.3. Implementation Timeline (Projected)

• Legislative Milestones: RD 238/2026 entered into force on April 20, 2026. The Ministerial Order is the next critical step.
• Mandatory Go-Live (Projected):October 1, 2026: Ministerial Order enters into force (pending publication).
• August 1, 2027: Public solution (SPFE) available.
• October 1, 2027: Mandatory for businesses with turnover >€8m in the preceding calendar year, and private platforms must interconnect.
• October 1, 2028: Mandatory for all remaining entrepreneurs, professionals, and autónomos.
• October 1, 2029: Payment-status reporting extends to smaller entities / income-attribution regime entities.
• Crucial Point: “a wave-2 SME will have to be able to receive (and report statuses on) invoices from wave-1 suppliers from October 2027 — the single most under-appreciated planning point in the regime.”
• Grace Periods: A “transitional PDF requirement” for the first 12 months for large companies, and a “four-business-day grace period” for system unavailability. No explicit penalty-free “educational” period has been announced.
• Postponements: VERI*FACTU has already been postponed twice, and the B2B mandate itself slipped from an earlier 2024/2025 projection.

3.4. How It Works – The Operating Model

• Model Type: “Hybrid / decentralised interoperability model with a mandatory central repository.” It utilizes “private e-invoice exchange platforms and the public e-invoicing solution (SPFE) run by AEAT.”
• No Pre-Clearance: “It is not a pre-clearance system.” However, “every invoice must reach the public solution” either directly or via a private platform, where a “faithful electronic copy in UBL syntax must be transmitted simultaneously to the SPFE.” The SPFE acts as the “universal, mandatory repository.”
• Invoice Lifecycle: Involves creation in EN 16931 format, submission (via SPFE or private platform using an ebXML-based transport layer), validation, unique coding (NIF + series/number + issue date), delivery to the buyer, retrieval, and archiving in the SPFE.
• Buyer-Side Workflow: The recipient “must inform the issuer of commercial acceptance or rejection and its date, and of full effective payment and its date, and must communicate payment/rejection to the SPFE.” Absence of rejection means the invoice is “presumed accepted.”
• QR/Verification Codes: Not required for the B2B mandate itself, but mandatory under VERIFACTU (QR + “VERIFACTU” wording) and TicketBAI (TBAI code + QR).

3.5. Acceptable E-Invoice Formats

• Mandatory Formats: The “invoice must conform to the EN 16931 semantic model” in one of four admitted syntaxes: UBL, CII, EDIFACT, and Facturae. “UBL is mandatory for the public solution and for the faithful copy transmitted to the SPFE.”
• Relationship to Standards: “Fully anchored in EN 16931,” meaning Peppol BIS 3.0 payloads are syntactically compatible, but “Spain has not adopted Peppol as the transmission network.”

3.6. Technical & Functional Requirements

• E-invoice Specifications: Must include mandatory content from RD 1619/2012 (e.g., NIF, dates, descriptions, VAT details) expressed through the EN 16931 semantic model. Mandate-specific fields include the unique invoice code and “faithful copy” indicator.
• E-reporting Specifications: Three distinct streams:
• Invoice-status/payment reporting (B2B): Recipient reports acceptance/rejection and full effective payment within four days (potentially business days, pending Order confirmation). The payment date is when the supplier “actually receives the funds.”
• SII: “Electronic supply of invoicing records…within four days…of issue or of accounting registration.”
• VERI*FACTU: “SIF generates a billing record…at the moment of issuance, containing a hash/fingerprint…chained to the previous record.”
• Digital Signature: The B2B mandate does not impose a per-invoice qualified signature, relying on platform/SPFE architecture for integrity. B2G (FACe) requires XAdES-EPES. VERIFACTU requires integrity, unalterability, traceability, and conservation, with electronic signatures for records in non-VERIFACTU mode.
• Real-time Characteristics: B2B mandate is “near-real-time on the issuing side” and “T+4 on the status/payment side.” SII is T+4 business days, and VERI*FACTU records are immediate.

3.7. Correction of Errors

• E-invoice Corrections: Follows the ordinary Spanish corrective-invoice regime (factura rectificativa), identifying the corrected invoice, reason, and data. Corrections are made via “business groups rather than UBL extensions” (a late change). Erroneous invoices can be de-registered while maintaining an audit trail.
• E-reporting Corrections: SII errors are corrected by submitting modification records. “Late or incorrect SII submission is sanctioned under Article 200 LGT at 0.5% of the invoice amount, with a €300 minimum.”

3.8. Transmission & Workflow

• Central Platform: The Solución Pública de Facturación Electrónica (SPFE), run by AEAT, serves as a free issuing tool, interconnection node, and “universal mandatory repository.”
• Transmission Channels: AEAT web services, web application, query forms, and private exchange platforms. “Peppol Access Points are not a designated channel.”
• Accredited Service Providers: Optional private platforms must meet Art. 13 requirements, support format transformation across all four syntaxes, and “interconnect with other platforms on customer request free of charge.”

4. Other Key Mandates

4.1. VERI*FACTU

• Purpose: Anti-fraud/VAT-gap instrument based on Ley 11/2021.
• Scope: Applies by reference to the obligation to issue invoices under Spanish rules and the use of computerized invoicing systems. SII filers are exempt from VERI*FACTU.
• Requirements: Requires computerised invoicing systems (SIF) to generate billing records with a hash/fingerprint, chained to previous records, and transmitted to AEAT in “VERIFACTU mode.” Invoices must carry a QR code and, where applicable, the wording “VERIFACTU.”
• Timeline: Postponed to January 1, 2027 for corporate income tax payers and July 1, 2027 for self-employed and others.

4.2. SII (Suministro Inmediato de Información)

• Purpose: “Near-real-time VAT ledger reporting.”
• Scope: Mandatory for large businesses (>€6m turnover), VAT groups, and those in REDEME. Voluntary opt-in is available.
• Mechanism: Electronic supply of invoicing records (alta, modificación, anulación) via XML web service or web form, “within four days” (excluding weekends/holidays) of issue or accounting registration.
• Benefits: SII filers are exempt from Modelos 347, 340, and 390, and get an extended monthly filing deadline.

4.3. B2G E-Invoicing (FACe)

• Purpose: Mandatory for B2G transactions.
• Scope: Mandatory since 2015 via FACe, for invoices above €5,000, and with no minimum threshold for the Central State Administration since 2017.
• Format: Facturae 3.2.2 XML with XAdES signature, plus mandatory DIR3 codes.
• Interaction: Invoices outside FACe are “rejected and payment withheld.”

4.4. TicketBAI/Batuz (Foral Territories)

• Scope: Applies to taxpayers domiciled in the Basque provinces (Álava, Bizkaia, Gipuzkoa).
• Requirements: Involves a TBAI alphanumeric code and QR on every invoice/ticket, along with XAdES-BES signature and SHA-256 hash chaining. This system operates instead of VERI*FACTU for these regions.

5. Archiving & Retention

• Central Archiving: The SPFE will be the “universal and mandatory repository” for B2B e-invoices, but this “does not relieve taxpayers of their own statutory conservation obligations.”
• Retention Period: Taxpayers must retain documents for 4 years (general tax rule), 9/14 years for capital goods, 6 years for commercial law, and potentially 10 years for administration verification under Art. 66 bis LGT.
• Format & Location: Documents must be kept in their original structured format (XML), with integrity, authenticity, and legibility guaranteed. Storage outside Spain is permitted, but requires prior notification to AEAT if in a non-EU country without comparable mutual assistance.
• Audit Accessibility: The AEAT and foral administrations will have “standing access to SPFE-stored invoice and payment data,” representing a “step-change in audit posture.”

6. Penalties & Enforcement

• No Penalty-Free Period: “No explicit penalty-free ‘educational’ period has been announced for the B2B mandate.”
• Penalties:Failure to issue B2B e-invoices / make them available (Crea y Crece): Fines “up to €10,000.”
• Use of non-compliant billing software (VERI*FACTU, Art. 201 bis.2 LGT): “€50,000 per tax year,” classified as a serious infringement, sanctioning “mere possession or use.” Manufacturers of non-compliant systems face “€150,000 per year and per type of system.”
• Late or incorrect SII submission (Art. 200 LGT): “0.5% of the invoice amount, minimum €300 per quarter.”
• Ordinary invoicing infringements remain applicable and cumulative.
• Penalties are often “fixed and objective,” not varying with turnover or damage to the Treasury.

7. Pre-Filled VAT Returns

• Current Status: Spain already operates pre-filled VAT return assistance through the Pre303 service.
• Mechanism: For SII filers, AEAT describes the service as enabling “automatic preparation of the VAT self-assessment (Pre303/LLAA) from the ledger records.” However, “Settlement figures still require taxpayer validation and input — Spain has an assisted return, not a fully determined one.”
• Future Potential: The B2B e-invoicing data in the SPFE is an “obvious future feed,” and the Senate has suggested this integration. In the Basque Country, TicketBAI/Batuz already pre-loads Modelos 303, 347, and 390.

8. ViDA Readiness & Implications

• Position Relative to ViDA: Spain is “ahead on domestic infrastructure, behind on convergence.” It has begun transposing the first wave of ViDA (OSS/distance-sales clarifications).
• Alignment:Semantics: Strong alignment, as EN 16931 is the mandatory semantic model.
• Syntax: Partial alignment (UBL, CII are ViDA-native; EDIFACT, Facturae are national accommodations).
• Transport: “Weak alignment on transport: ebXML into a national repository rather than a Peppol-style four-corner network raises interoperability questions for 2030.”
• Key Gaps:SII: Spain has until January 1, 2035, to conform SII to the EU standard.
• Purpose Mismatch: The Spanish B2B system is a “late-payment instrument,” while ViDA DRR is a “VAT-control instrument,” requiring significant legislative work to bridge.
• Cross-border B2B: Spain’s mandate excludes cross-border B2B, which ViDA DRR will capture from July 1, 2030.
• Implications for Businesses: Companies building for RD 238/2026 will have EN 16931-capable, structured, status-aware invoicing, which is “genuinely reusable for ViDA.” However, additional work will be needed for cross-border scope extension, DRR transmission channels, and the 10-day cross-border reporting clock. “the Spanish faithful-copy/status mechanics are strictly harder than ViDA’s baseline, so ViDA compliance is largely a subset for firms that have already built for Spain.”

9. Impact on SMEs and Startups

• Phased Onboarding: SMEs and autónomos are in wave 2 (projected October 1, 2028), a full year after large taxpayers. However, they “must be able to receive structured invoices from wave-1 suppliers from October 2027.”
• Government Support: AEAT must provide a “free application/form for issuing e-invoices, generating status information,” explicitly aimed at businesses without their own SIF. Kit Digital subsidies are available for those with existing vouchers, but no new call is currently open.
• Compliance Costs: “Generating XML is cheap; re-engineering processes, statuses, support, reconciliation and accounting around that XML is expensive.”
• Net Burden: “Short term clearly negative for SMEs: three overlapping regimes…with distinct timelines, formats and penalties.” Medium term, potential benefits from payment discipline and pre-filled returns, but “only if the convergence the Senate called for actually happens.”

10. Critical Dates & Next Steps

• Immediate Action (Now – October 2026): Monitor the BOE daily for the Ministerial Order. Upon publication, obtain technical specifications and register for the AEAT test environment. Re-baseline ERP mapping against recent changes (e.g., corrective invoices via business groups, updated EN 16931 VAT categories).
• By January 1, 2027 / July 1, 2027: Confirm VERI*FACTU status. SII filers are exempt, a crucial point for entity-by-entity verification.
• Through 2027: Decide on public vs. private platform usage. Ensure platform capability for four-syntax transformation and free interconnection. Build the status and payment-date reporting process, which is a new AP/treasury obligation.
• By October 1, 2027: Wave 1 issuing goes live; all counterparties must be able to receive and report statuses.
• By October 1, 2028: Full population live.

Open Items to Track:

• Clarity on the “calendar-versus-business-day” definition for the four-day status deadline.
• Treatment of VAT-registered but non-established entities.
• Any sectoral exclusion orders under Art. 4.2.
• The progress on the SII/VERI*FACTU/B2B convergence roadmap ahead of ViDA.

Click on the logo to visit the website

 

1. Introduction & Country Context

1.1. Digitalisation journey

• Spain has been an early and aggressive digitaliser of VAT compliance. The sequence is: mandatory B2G e-invoicing via FACe (Facturae XML) since 15 January 2015 under Law 25/2013; near-real-time VAT ledger reporting (SII) since 1 July 2017 under RD 596/2016; regional anti-fraud invoicing systems (TicketBAI/Batuz) in the Basque provinces from 2020–2024; the VERI*FACTU billing-software regulation (RD 1007/2023); and finally mandatory B2B e-invoice exchange under Law 18/2022 (“Crea y Crece”), now developed by RD 238/2026. [e-invoicing.org], [lido.app], [beply.es], [cleartax.com]
• The practical consequence is that Spain runs three parallel, legally distinct regimes — SII (VAT ledger reporting), VERI*FACTU (software integrity/anti-fraud), and Crea y Crece B2B e-invoicing (invoice exchange + payment-status reporting). Complying with one does not exempt a taxpayer from the others. [frihet.io], [cuatrecasas.com]

1.2. Rationale

• Uniquely in the EU, the primary driver of the B2B mandate is late-payment control, not VAT fraud. RD 238/2026 develops Article 2 bis of Law 56/2007 (as amended by Article 12 of Law 18/2022), whose purpose is to obtain reliable data on effective payment periods and to feed the State Observatory on Private Late Payment. Spain’s average B2B payment period is reported at roughly 80 days against a 60-day legal maximum. [hacienda.gob.es], [easysoft.es] [vertexinc.com]
• Secondary objectives: digitalisation of SMEs (99% of the productive fabric, ~62% of GVA, 66% of employment, per the RD’s preamble), administrative efficiency and transparency. [boe.es]
• VERI*FACTU and SII, by contrast, are explicitly anti-fraud/VAT-gap instruments — VERI*FACTU derives from the Anti-Fraud Law 11/2021 and Article 29.2.j) LGT. [sede.agenc…ria.gob.es], [beel.es]

1.3. Positioning

• Spain is an early mover on reporting (SII since 2017, among the first real-time VAT ledger systems in the EU) but a late mover on invoice exchange: the B2B mandate slipped from an originally expected 2024/2025 to 2027/2028. [lookuptax.com], [eu-einvoicing.com]
• The chosen architecture is a hybrid/decentralised CTC model (accredited private platforms plus a public AEAT solution acting as universal repository), closer to the French PPF/PDP split than to Italy’s single clearing house SdI. [eu-einvoicing.com], [devenga.es]
• Relative to ViDA, Spain is ahead of the 2030 DRR deadline for domestic invoice exchange but behind on convergence, since SII, VERI*FACTU and B2B e-invoicing remain unmerged — a point the Spanish Senate itself raised in a non-binding motion approved in August 2026. [europe.tho…euters.com], [dynatos.com]

1.4. Supranational authorisation

• No EU derogation was required. Since the ViDA Directive (EU) 2025/516 entered into force on 14 April 2025, amended Articles 218 and 232 of the VAT Directive allow Member States to mandate domestic e-invoicing without prior Council authorisation and without buyer consent. [taxation-c….europa.eu], [vatcalc.com], [kpmg.com]
• The draft Ministerial Order went through the EU technical-regulation notification procedure (TRIS), which has now closed. [europe.tho…euters.com]
• B2G obligations derive from Directive 2014/55/EU, transposed via Law 25/2013 and related rules; contracting authorities must accept EN 16931-compliant invoices above EU procurement thresholds. [e-invoicing.org]

2. Regulatory Framework

2.1. Primary legislation

• Ley 56/2007, Article 2 bis (Measures to Promote the Information Society) — the operative obligation to issue, transmit and receive e-invoices B2B and to report invoice statuses. [hacienda.gob.es]
• Ley 18/2022, de 28 de septiembre, de creación y crecimiento de empresas (“Crea y Crece”), Article 12 — inserts/amends Article 2 bis. BOE núm. 234, 29/09/2022; in force 19/10/2022. [boe.es], [cleartax.com]
• Ley 58/2003 (LGT), Article 29.2.j) — introduced by Ley 11/2021 (Anti-Fraud Law) — basis for billing-software requirements; Article 201 bis LGT contains the related penalty regime. [sede.agenc…ria.gob.es], [beel.es]
• Ley 37/1992 (VAT Law) — Article 121 (turnover computation for thresholds), Article 165 (record-keeping), Article 164 (invoicing). [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
• Ley 25/2013 — B2G e-invoicing and FACe. [e-invoicing.org]

2.2. Implementing regulations and decrees

• Real Decreto 238/2026, de 25 de marzo — the core B2B e-invoicing regulation; BOE núm. 79 of 31 March 2026, pages 47444–47466; ELI https://www.boe.es/eli/es/rd/2026/03/25/238; in force 20 April 2026, application deferred. Structure: Arts. 1–15, seven additional provisions, transitional provisions and four final provisions. [boe.es], [frihet.io] [noticias.j…idicas.com]
• Real Decreto 1619/2012 (Invoicing Regulation) — amended by RD 238/2026; governs invoice content, simplified invoices (Art. 4, Art. 7.2 qualified simplified invoices), corrective invoices (Art. 15), self-billing (Art. 5) and retention (Arts. 19–23). [supercontable.com], [supercontable.com]
• Real Decreto 1007/2023, de 5 de diciembre (RRSIF) — requirements for computerised invoicing systems (SIF) and VERI*FACTU. [sede.agenc…ria.gob.es]
• Orden HAC/1177/2024 — technical specifications for SIF/VERI*FACTU. [easysoft.es]
• Real Decreto 254/2025 — first postponement of VERI*FACTU (to 1 January 2026 / 1 July 2026) and confirmation that SII filers are outside scope. [docnova.ai], [easysoft.es]
• Real Decreto-ley 15/2025, de 2 de diciembre (BOE 3 December 2025; validated by Congress 11 December 2025) — second VERI*FACTU postponement to 1 January 2027 (corporate income tax payers) and 1 July 2027 (self-employed and others). [eu-einvoicing.com], [spun.es]
• RD 596/2016 / Orden HFP/417/2017 — SII legal and technical framework (Arts. 62–70 of the VAT Regulation, RD 1624/1992). [gestorialaso.es]
• Pending: Ministerial Order regulating the Public E-Invoicing Solution (SPFE) — draft published for public hearing 17 April 2026, consultation closed 8 May 2026; final text now comprises eleven articles, two additional provisions and two annexes; publication and entry into force anticipated 1 October 2026. As of late September 2026 it had not yet appeared in the BOE; until it does, the go-live dates are projections, not legal deadlines. [hacienda.gob.es], [copilotgestoria.com], [europe.tho…euters.com] [frihet.io]

2.3. Guidance, rulings and FAQs

• AEAT informative note on RD 238/2026 (“Nota informativa RD Facturación electrónica obligatoria”). [sede.agenc…ria.gob.es]
• AEAT SIF/VERI*FACTU FAQ compilation, last updated 21 July 2026, covering scope, hash/fingerprint, signature, responsible declaration (declaración responsable) of software certification, QR code and the “VERI*FACTU” wording. [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
• AEAT regulatory and technical seminar on the SPFE, 10 September 2026 — the most current official guidance: relaxed cardinality on the “faithful copy” indicator, refined duplicate-rejection logic, a new four-business-day grace period during system unavailability, and expanded payment-communication rules distinguishing commercial rejection from rejection for unrelated activity. [europe.tho…euters.com]
• SII: AEAT virtual assistant, SII deadline calculator, technical information pages and FAQ. [sede.agenc…ria.gob.es]
• No consolidated official FAQ on the B2B mandate has been published yet; technical documentation and a dedicated test environment are targeted for October 2026. [europe.tho…euters.com]

2.4. Supranational legal basis

• Directive (EU) 2025/516 (ViDA), Regulation (EU) 2025/517, Implementing Regulation (EU) 2025/518 — published OJ 25 March 2025. [taxation-c….europa.eu]
• Amended Arts. 218/232 VAT Directive (applicable from 14 April 2025) removed the need for a derogation. [vatcalc.com], [vatupdate.com]
• Directive 2014/55/EU for B2G. [e-invoicing.org]
• Spain has also announced it may seek a derogation to apply certain ViDA Pillar II (platform) rules before 1 July 2028, potentially as the first Member State. [kpmg.com]

3. Scope of the Mandate

3.1. Transactions in scope

• Domestic B2B — mandatory (phased). Applies where an entrepreneur/professional must issue an invoice and the recipient is another entrepreneur or professional having in Spain their seat, permanent establishment or, failing that, domicile or habitual residence, and the transaction is carried out for that recipient (RD 238/2026 Art. 3). PDFs sent by email, paper, Word or images cease to constitute valid invoices for in-scope transactions. [ruizballesteros.es], [tramitesju…idicos.com] [devenga.es], [taxnews.ey.com]
• Domestic B2G — mandatory since 2015, separate regime. Facturae 3.2.2 XML with XAdES signature, submitted via FACe; mandatory for invoices above €5,000 and, since 2017, with no minimum threshold for the Central State Administration. Invoices outside FACe are rejected and payment withheld. RD 238/2026 contains a transitional provision on transmission of e-invoices by subcontractors of public sector contracts, which is the main interface point between the two regimes. Beyond the shared use of Facturae as an accepted syntax, no formal technical merger of FACe and the SPFE has been announced. [invoicemonk.com], [docs.frihet.io] [noticias.j…idicas.com]
• Domestic B2C — out of scope of the Crea y Crece mandate. B2C transactions are nonetheless captured by VERI*FACTU (billing records, QR code on every invoice) and, for Basque-domiciled taxpayers, by TicketBAI (QR + TBAI code on tickets). [taxnews.ey.com], [vertexinc.com] [bdo.global], [beply.es]
• Cross-border B2B (intra-EU outbound) — out of scope. EY confirms that transactions with non-established counterparties fall outside RD 238/2026; the mandate is limited to Spain-established issuer and Spain-established recipient. They remain reportable under SII (and, from 1 July 2030, under ViDA DRR). [taxnews.ey.com], [ey.com] [cleartax.com]
• Exports and imports — out of scope of the B2B e-invoicing mandate for the same reason; export invoices and import documentation continue under ordinary invoicing rules and SII/VAT return reporting. [taxnews.ey.com]
• Intra-EU acquisitions / inbound invoices from foreign suppliers — not covered. A foreign supplier without Spanish establishment is not obliged to issue through the Spanish system, and a Spanish recipient has no obligation to report statuses for such invoices; the input side continues to be captured through SII ledger reporting (Libro de facturas recibidas) and the VAT return. [taxnews.ey.com], [cleartax.com]

3.2. Special transactions

• Self-billing — in scope and expressly supported. The AEAT’s September 2026 seminar confirmed support for self-billing and third-party billing in the semantic model (Annex I). See Chapter 11. [europe.tho…euters.com]
• Triangulation and chain transactions — in scope only where both legs are between Spain-established parties. The leg to or from a non-established party falls outside. RD 238/2026 contains no triangulation-specific rule, and at EU level the CEN schema has been criticised for lacking a triangulation code — an open issue in the ViDA Explanatory Notes. [vatcalc.com]
• Special VAT regimes (margin schemes, travel agents, second-hand goods, flat-rate farmers, investment gold) — no specific exclusion exists in RD 238/2026. They are therefore in scope whenever a full invoice must be issued between Spain-established businesses. The Ministry of Economy retains power under Art. 4.2 to exclude further operations sector by sector, but no such sectoral order has been issued to date. [supercontable.com]

3.3. Excluded transactions

• Simplified invoices (RD 1619/2012 Art. 4) are excluded — except “qualified” simplified invoices under Art. 7.2 of that Regulation, which remain in scope (RD 238/2026 Art. 4.1). [supercontable.com], [iberley.es]
• Regulated activities of the electricity market operator under Art. 29 of Law 24/2013 (Additional Provision 2.1). [supercontable.com]
• Functions of the organised gas market operator under Art. 65 ter of Law 34/1998, including its gas futures market subsidiary (AP 2.2). [supercontable.com]
• IATA clearing and settlement systems — CASS, BSP and SIS-ICH — provided payment is settled through one of those platforms in accordance with their calendars (AP 2.3). [supercontable.com]
• Future sectoral exclusions may be adopted by the Minister of Economy, Trade and Enterprise where a sector shows relevant adaptation difficulty; as a rule these will be temporary, and permanent exclusions require proof that the sector has no prolonged or abusive payment periods (Art. 4.2). [supercontable.com]
• Not covered by the RD: B2C, cross-border, and transactions with non-established recipients (by operation of Art. 3 rather than an express exclusion list). [taxnews.ey.com]
• No OSS/IOSS-specific exclusion is stated in RD 238/2026; those are B2C flows and therefore outside scope by definition.

4. Taxable Persons in Scope

4.1. Established domestic entities

• All entrepreneurs and professionals — legal persons and natural persons (autónomos) — established in Spain who are obliged to issue an invoice, where the recipient is also a Spain-established entrepreneur/professional. [ruizballesteros.es], [cuatrecasas.com]
• Threshold relevance is timing only, not scope: >€8m turnover (Art. 121 Ley 37/1992) in the immediately preceding calendar year enters in wave 1; everyone else in wave 2. [sede.agenc…ria.gob.es]
• VAT-exempt entities and entities under the income-attribution regime are within the system, with a one-year additional deferral of payment-status reporting for income-attribution entities. [europe.tho…euters.com]

4.2. Non-established entities

• Fixed establishment in Spain: in scope. The mandate turns on the recipient having a seat, permanent establishment, domicile or habitual residence in Spain and the supply being made to it — and EY confirms the measure impacts “Spanish-based companies and those with a permanent establishment in Spain.” [ruizballesteros.es], [ey.com]
• VAT-registered but no fixed establishment: outside the mandate. EY states expressly that cross-border transactions remain outside its scope and the rule targets established parties. A mere Spanish VAT number is not, on the face of RD 238/2026, sufficient to trigger the obligation — but this is precisely the point on which practitioners are awaiting confirmation in the Ministerial Order or subsequent AEAT guidance, and non-established VAT-registered groups should treat it as an open risk rather than a settled exemption. [taxnews.ey.com]
• No Spanish VAT registration: excluded.
• Note the contrast with VERI*FACTU, which applies by reference to the obligation to issue invoices under Spanish invoicing rules and to the use of computerised invoicing systems, and with SII, where non-established taxpayers filing monthly VAT returns/in REDEME are obliged. [sede.agenc…ria.gob.es]

4.3. Voluntary participation

• RD 238/2026 does not establish a formal voluntary-adoption scheme with incentives. In practice, wave-2 taxpayers may adopt early, and platforms/AEAT will offer a test environment from October 2026. [europe.tho…euters.com]
• Voluntary opt-in does exist for SII, via Modelo 036, with the December window for the following year; opting into SII also removes the VERI*FACTU obligation. [blog.taxea…ategies.es], [docnova.ai]

4.4. Sector-specific rules and exemptions

• Electricity market operator, organised gas market operator and IATA settlement flows (see 3.3). [supercontable.com]
• Foral territories: the Basque provinces (Álava, Bizkaia, Gipuzkoa) operate TicketBAI/Batuz instead of VERI*FACTU, under their own foral norms (e.g. Norma Foral 3/2020 and Decreto Foral 32/2020 in Gipuzkoa; Decreto Foral 8/2022 in Álava; Decreto Foral Normativo 5/2020 and Decreto Foral 82/2020 for Batuz in Bizkaia). Applicability is determined by tax domicile, not customer location. Navarra has not implemented TicketBAI; its taxpayers fall under the state VERI*FACTU framework. RD 238/2026 has a dedicated additional provision on foral tax administrations and the public e-invoicing solution, and another on their access to SPFE-stored data. [beply.es], [frihet.io] [ideiatek.net] [noticias.j…idicas.com]
• Financial services, healthcare, utilities and telecom: no general sectoral exemption has been legislated.

5. Implementation Timeline

5.1. Legislative history

• 28 September 2022 — Law 18/2022 adopted; in force 19 October 2022, application suspended pending regulation. [boe.es], [cleartax.com]
• 20 June 2023 — first draft Royal Decree to public information. [sede.agenc…ria.gob.es]
• 5 March 2025 — revised draft regulation published. [ey.com]
• 26 March – 9 April 2025 — prior public consultation on the Ministerial Order. [hacienda.gob.es]
• 24/25 March 2026 — Council of Ministers approves RD 238/2026. [taxnews.ey.com]
• 31 March 2026 — published BOE núm. 79. [boe.es]
• 20 April 2026 — RD 238/2026 enters into force. [frihet.io]
• 17 April – 8 May 2026 — public hearing on the draft Ministerial Order. [hacienda.gob.es], [copilotgestoria.com]
• 10 September 2026 — AEAT technical seminar; draft Order in final processing after closure of the EU TRIS notification. [europe.tho…euters.com]
• No EU derogation; validity period therefore not applicable. [vatcalc.com]

5.2. Voluntary/pilot phases

• No formal pilot or incentivised voluntary phase for the B2B mandate. A test environment plus full technical documentation is targeted for October 2026, giving roughly twelve months of sandbox time before wave 1. [europe.tho…euters.com]

5.3. Mandatory go-live (as projected by the draft Order)

• 1 October 2026 — Ministerial Order enters into force; all subsequent deadlines count from this date. [legaltoday.com], [europe.tho…euters.com]
• 1 August 2027 — the public solution (SPFE) must be available at least two months before first effective application (RD 238/2026, Final Provision Four). [sede.agenc…ria.gob.es], [legaltoday.com]
• 1 October 2027 — mandatory for entrepreneurs/professionals with turnover above €8 million in the preceding calendar year; also the date from which private platforms must interconnect and transmit faithful copies. [legaltoday.com]
• 1 October 2028 — mandatory for all remaining entrepreneurs, professionals and autónomos. [legaltoday.com], [eu-einvoicing.com]
• 1 October 2029 — payment-status reporting extends to smaller entities / income-attribution regime entities (one further year). [eu-einvoicing.com], [europe.tho…euters.com]
• Obligation to receive: RD 238/2026 imposes issuing and receiving through the system on the same dates for each cohort; in practice a wave-2 SME will have to be able to receive (and report statuses on) invoices from wave-1 suppliers from October 2027 — the single most under-appreciated planning point in the regime. [sede.agenc…ria.gob.es], [smart-einvoicing.com]

5.4. Grace periods and transitional provisions

• Transitional PDF requirement: during the first 12 months of application, large companies must accompany the structured e-invoice with a readable PDF copy, unless the recipient expressly agrees to receive the structured format only. [ey.com], [marimon-abogados.com]
• Four-business-day grace period where the platform/system is unavailable, allowing later transmission once the incident is resolved. [europe.tho…euters.com], [legaltoday.com]
• RD 238/2026 contains transitional provisions on public-sector subcontractors and on the regime for businesses above the turnover threshold. [noticias.j…idicas.com]
• No explicit penalty-free “educational” period has been announced for the B2B mandate.

5.5. Pre-mandate milestones

• October 2026: publication of the Order, technical specifications on the AEAT electronic headquarters, test environment and full documentation. [europe.tho…euters.com], [legaltoday.com]
• Authentication and representation mechanisms to be defined in the Order. [hacienda.gob.es]

5.6. Postponements and delay risk

• VERI*FACTU has already been postponed twice (1 July 2025 → 1 January 2026 via RD 254/2025; then → 1 January 2027 / 1 July 2027 via RDL 15/2025). [docnova.ai], [eu-einvoicing.com]
• The B2B mandate slipped from an originally anticipated 2024/2025. [lookuptax.com]
• Live risk: as at end-September 2026 the Ministerial Order was still unpublished; every date after it is conditional. Advisers are explicitly warning that draft-Order dates “are not currently legally binding deadlines.” [frihet.io]

6. How It Works — The Operating Model

6.1. Model type

• Hybrid / decentralised interoperability model with a mandatory central repository. The Spanish e-invoicing system comprises (a) private e-invoice exchange platforms and (b) the public e-invoicing solution (SPFE) run by AEAT. Businesses may use either or a combination. [sede.agenc…ria.gob.es], [marimon-abogados.com]
• It is not a pre-clearance system: the AEAT does not authorise the invoice before it can be issued. But every invoice must reach the public solution — when a private platform is used, a faithful electronic copy in UBL syntax must be transmitted simultaneously to the SPFE, which acts as the universal, mandatory repository. [sede.agenc…ria.gob.es], [devenga.es]
• The tax authority’s role is therefore repository, interconnection node, status registry and payment-period data collector, rather than clearing house. [marimon-abogados.com]

6.2. Invoice lifecycle

• Step 1 — Creation: the issuer’s ERP/billing system generates a structured invoice compliant with EN 16931 in one of the admitted syntaxes. [marimon-abogados.com]
• Step 2 — Submission: via the SPFE directly (web application, query forms, or web services, the latter expected to carry most volume), or via a private platform; a new ebXML-based transport layer has been introduced. [europe.tho…euters.com]
• Step 3 — Validation: automatic syntax and content validations, with acknowledgements of receipt and acceptance/rejection messages; duplicate-submission rejection logic has been refined in the final draft. Typical rejection causes flagged by advisers: invalid recipient NIF check digit, XSD-invalid XML, expired or wrongly formatted signature, and incoherent date formats. [legaltoday.com], [europe.tho…euters.com] [copilotgestoria.com]
• Step 4 — Unique coding: each invoice receives a unique code formed by concatenating the issuer’s NIF, the series and number, and the issue date. [legaltoday.com]
• Step 5 — Delivery to the buyer: via the SPFE or via interconnected private platforms; platforms must interconnect on customer request and interoperability must be free of charge. [devenga.es], [hacienda.gob.es]
• Step 6 — Retrieval by the buyer: through the SPFE’s retrieval services, using an encrypted invoice locator for efficient retrieval, or through the recipient’s own platform. [europe.tho…euters.com], [hacienda.gob.es]
• Step 7 — Archiving: the SPFE stores all invoices as universal repository; taxpayers nonetheless retain their own statutory conservation obligations (Chapter 13). [devenga.es], [sede.agenc…ria.gob.es]

6.3. Authentication and access

• The Order defines the “forms of authentication, identification and representation” for accessing the public solution. For AEAT services generally these are Cl@ve PIN, electronic DNI, qualified electronic certificate and eIDAS, with third-party access via apoderamiento (registered power of attorney) or the social-collaboration regime — the route gestorías and advisers will use on behalf of clients. [hacienda.gob.es] [www3.agenc…ria.gob.es], [sede.agenc…ria.gob.es]

6.4. Offline / contingency mode

• Where the system is unavailable, invoices may be transmitted within four days / four business days after the incident is resolved. [legaltoday.com], [europe.tho…euters.com]
• There is no offline QR-marked paper contingency invoice of the Italian/Indian type under the B2B mandate; the contingency is deferred transmission, not alternative issuance.

6.5. Buyer-side workflow

• The recipient must inform the issuer of commercial acceptance or rejection and its date, and of full effective payment and its date, and must communicate payment/rejection to the SPFE. [sede.agenc…ria.gob.es]
• In the absence of rejection, the invoice is presumed accepted — so buyer acceptance is not a validity condition, but silence has legal consequences for payment-period computation. [devenga.es]
• The final draft Order distinguishes commercial rejection from rejection on the grounds that the transaction relates to an unrelated activity. [europe.tho…euters.com]

6.6. QR / verification codes

• Not required under the B2B mandate — invoices carry a unique concatenated code (NIF + series/number + date), not a QR. [legaltoday.com]
• QR is required under VERI*FACTU: every invoice must carry a graphic QR representation and, where applicable, the wording“VERI*FACTU”, enabling the recipient to verify the record with AEAT. [sede.agenc…ria.gob.es], [bdo.global]
• TicketBAI requires a TBAI alphanumeric code and QR on every invoice/ticket in the Basque territories. [beply.es]

7. Acceptable E-Invoice Formats

7.1. Mandatory formats

• The invoice must conform to the EN 16931 semantic model (RD 238/2026 Art. 7.1) in one of four admitted syntaxes: UBL (OASIS), CII (UN/CEFACT), EDIFACT, and Facturae. [devenga.es], [marimon-abogados.com]
• UBL is mandatory for the public solution and for the faithful copy transmitted to the SPFE when a private platform is used. [eu-einvoicing.com], [sede.agenc…ria.gob.es]
• PDF, paper, Word, Excel and images are not valid e-invoices for in-scope transactions — with the transitional exception of the accompanying readable PDF during the first 12 months. [devenga.es], [ey.com]
• The Ministry of Economy may extend the list of syntaxes by order. [devenga.es]
• B2G: Facturae 3.2.2 XML with XAdES-EPES signature via FACe, plus mandatory DIR3 codes (oficina contable, órgano gestor, unidad tramitadora). [invoicemonk.com], [docs.frihet.io]

7.2. Relationship to international standards

• Fully anchored in EN 16931; Annex I of the Order incorporates updated EN 16931 content, including new VAT categories. [europe.tho…euters.com], [marimon-abogados.com]
• Both EN 16931 syntaxes (UBL 2.1 and CII) are accepted, so Peppol BIS 3.0 payloads are syntactically compatible — but Spain has not adopted Peppol as the transmission network for the B2B mandate; the transport layer is ebXML-based into the SPFE, alongside private-platform interconnection. [europe.tho…euters.com], [devenga.es]
• National deviations: the mandatory UBL faithful copy, the unique concatenated invoice code, the “faithful copy” indicator field, and the invoice-status/payment message set are Spain-specific extensions with no EN 16931 equivalent. Notably, corrective-invoice reporting is now handled through business groups rather than UBL extensions — a late change that materially affects ERP mapping. [europe.tho…euters.com]

7.3. Voluntary, legacy and transitional formats

• Facturae and EDIFACT function as legacy-friendly options between private platforms, which must be able to transform between all admitted formats on request. [devenga.es]
• Transitional PDF accompaniment for 12 months for large issuers (see 5.4). [ey.com]
• Hybrid formats (Factur-X/ZUGFeRD) are not among the four admitted syntaxes. [devenga.es]
• B2C invoices and cross-border invoices may continue in any format, subject to VERI*FACTU/TicketBAI software rules. [taxnews.ey.com]

7.4. Attachments

• RD 238/2026 does not establish a specific attachment regime. Facturae supports an attachments mechanism and has extended its list of admitted formats (HTML added in v3.2.2), and B2G invoices may carry contracting-authority-specific extensions. Treatment of attachments as formal invoice components versus supplementary documentation is one of the open issues being worked through at EU level in the ViDA Explanatory Notes rather than settled in Spanish law. [facturae.gob.es] [vatcalc.com]

8. Technical & Functional Requirements

8.1. E-invoice specifications

• Mandatory content remains that of RD 1619/2012 Arts. 6 and 7 (number and series, issue date, issuer and recipient full name/NIF/address, description of operations, taxable base, VAT rate(s), VAT amount, date of supply where different, and, where relevant, mandatory annotations such as “inversión del sujeto pasivo”, “régimen especial del criterio de caja”, margin-scheme wording, etc.), expressed through the EN 16931 semantic model. [supercontable.com], [marimon-abogados.com]
• Mandate-specific fields: the unique invoice code (NIF + series/number + issue date), the“faithful copy” indicator (cardinality now relaxed), and identifiers supporting self-billing and third-party billing. [legaltoday.com], [europe.tho…euters.com]
• Conditional fields: payment due date and payment terms (essential, since the entire regime is built to compute payment periods under Law 3/2004), references to the corrected invoice for corrective documents, and, in B2G, DIR3 codes and Leitweg-type references. [easysoft.es], [docs.frihet.io]
• Validation rules: XSD schema validation, EN 16931 business rules, NIF check-digit validation, date-format coherence, calculation consistency, duplicate detection. [copilotgestoria.com], [europe.tho…euters.com]

8.2. E-reporting specifications

• Spain has three distinct reporting streams:
  • Invoice-status/payment reporting (RD 238/2026 Arts. 10 and 12): the recipient must report acceptance or rejection with its date, and full effective payment with its date, within four days; the final draft treats these as four business days in the unavailability scenario and advisers read the general status deadline as four calendar days excluding Saturdays, Sundays and national holidays. This calendar-versus-business-day question is a genuine ambiguity in current commentary and should be confirmed against the published Order. Crucially, the payment date is the date the supplier actually receives the funds — not the agreed due date, not the debtor’s accounting entry; receivables-finance advances do not count as payment. [sede.agenc…ria.gob.es], [frihet.io], [devenga.es] [easysoft.es]
  • SII (Arts. 62–70 VAT Regulation): electronic supply of invoicing records forming the VAT ledgers, via XML web service or web form, within four days (excluding Saturdays, Sundays and national holidays) of issue or of accounting registration. Record types: alta (new), modificación, and corrective-invoice records. SII filers are exempt from Modelo 347, 340 and 390 and get an extended monthly filing deadline to the 30th of the following month. [sede.agenc…ria.gob.es], [blog.taxea…ategies.es], [gestorialaso.es]
  • VERI*FACTU billing records: the SIF generates a billing record (registro de facturación de alta, and anulación records for cancellations) at the moment of issuance, containing a hash/fingerprint of its data, chained to the previous record, and — in VERI*FACTU mode — transmitted to AEAT; in non-VERI*FACTU mode records are retained locally with an electronic signature and an event log. [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]

8.3. Digital signature and integrity

• B2B mandate: integrity is primarily assured by the platform/SPFE architecture, unique coding and the faithful-copy mechanism; RD 238/2026 does not impose a per-invoice qualified signature, though advisers list expired/incorrectly formatted signatures among rejection causes, so signature requirements at platform level must be verified against the final Order. [vertexinc.com], [copilotgestoria.com]
• B2G: XAdES-EPES qualified electronic signature is mandatory; FACe automatically rejects unsigned invoices. [docs.frihet.io]
• VERI*FACTU: RD 1007/2023 Art. 8.2 requires integrity and unalterability (corrections only by a subsequent record, never by deleting), traceability (hash chaining) and conservation, accessibility and legibility; electronic signature of records is required in the non-VERI*FACTU modality. [beel.es], [sede.agenc…ria.gob.es]
• TicketBAI: XAdES-BES signature plus SHA-256 hash chaining per invoice. [frihet.io]

8.4. Real-time characteristics

• B2B mandate: near-real-time on the issuing side (faithful copy transmitted simultaneously with issuance) and T+4 on the status/payment side. [sede.agenc…ria.gob.es], [marimon-abogados.com]
• SII: T+4 business days. [gestorialaso.es]
• VERI*FACTU: record generated at issuance; transmission immediate in VERI*FACTU mode. [sede.agenc…ria.gob.es]
• No published platform SLA (uptime, capacity, response times) has been released — only the contingency rule for unavailability. [europe.tho…euters.com]

9. Correction of Errors

9.1. E-invoice corrections

• Corrections follow the ordinary Spanish corrective-invoice regime (factura rectificativa, RD 1619/2012 Art. 15): a corrective invoice must be issued with its own series, identifying the invoice(s) corrected, the reason for correction, and the corrected data or the amount of the correction. Facturae 3.2.2 added the InvoiceIssueDate field specifically to identify the corrected invoice. [facturae.gob.es]
• Under the Order, corrective-invoice reporting is carried through business groups rather than UBL extensions — a design change from earlier drafts. [europe.tho…euters.com]
• The Order additionally provides for the de-registration (baja) of erroneous invoices while guaranteeing traceability — i.e. the erroneous record can be withdrawn from the repository, but the audit trail persists. [legaltoday.com]
• Resubmission follows the normal channel; duplicate-submission rejection logic has been tightened, so resubmission of an unchanged invoice will be rejected rather than silently duplicated. [europe.tho…euters.com]
• Under VERI*FACTU the principle is absolute: a correction is made by a subsequent record, never by altering or deleting the prior one (RD 1007/2023 Art. 8.2), with dedicated anulación record types. [beel.es], [sede.agenc…ria.gob.es]

9.2. E-reporting corrections

• Status/payment messages: RD 238/2026 provides the status message set; it does not set out a distinct formal correction procedure for an erroneous status message, beyond the general obligation to report accurately within four days. This is an area to confirm against the published Order. [sede.agenc…ria.gob.es]
• SII: errors are corrected by submitting modification records to the ledger; rejected records must be resubmitted. Late or incorrect SII submission is sanctioned under Article 200 LGT at 0.5% of the invoice amount, with a €300 minimum (commonly cited quarterly cap of €6,000). [blog.taxea…ategies.es]
• VAT return: since 2024 Spain uses the autoliquidación rectificativa mechanism within Modelo 303 rather than separate complementary/rectification requests, with AEAT technical guidance on rectifying to declare a higher payment, a higher refund or a lower payment. [www3.agenc…ria.gob.es]
• Modelo 390 annual summary remains for non-SII filers; SII filers are exonerated. [sede.agenc…ria.gob.es]

10. Transmission & Workflow

10.1. Central platform

• Solución Pública de Facturación Electrónica (SPFE), developed and operated by the Agencia Estatal de Administración Tributaria (AEAT) under the mandate of Additional Provision 21 of Law 56/2007. [sede.agenc…ria.gob.es]
• It is simultaneously a free issuing tool, an interconnection node, and the universal mandatory repository of all B2B e-invoices. [devenga.es], [marimon-abogados.com]
• It must be operational at least two months before first effective application (i.e. by 1 August 2027 on the projected calendar). [sede.agenc…ria.gob.es], [legaltoday.com]
• FACe (face.gob.es) remains the B2G general entry point, operated by the Ministry of Finance; note that FACe migrated to a new “FACe Proveedores” portal, with the legacy portal retaining historical consultation only for invoices submitted up to 27/02/2026. [face.gob.es], [invoicemonk.com]

10.2. Transmission channels

• AEAT web services (expected to carry the majority of volume), web application, and query forms — the three SPFE access channels. [europe.tho…euters.com]
• Free government form/application for issuing e-invoices and generating status information, available to all businesses and their authorised representatives (RD 238/2026, Additional Provision One). [sede.agenc…ria.gob.es], [noticias.j…idicas.com]
• Private exchange platforms meeting the Art. 13 requirements. [noticias.j…idicas.com]
• Peppol Access Points are not a designated channel of the Spanish B2B system.
• New ebXML-based transport layer for the SPFE. [europe.tho…euters.com]

10.3. Accredited service providers

• Use of a private platform is optional — a business may operate entirely through the public solution. [marimon-abogados.com]
• Platforms must satisfy Art. 13 requirements to operate, must support format transformation across all four syntaxes, must interconnect with other platforms on customer request free of charge, and must transmit the UBL faithful copy simultaneously to the SPFE. [devenga.es], [sede.agenc…ria.gob.es], [hacienda.gob.es]
• No public registry of accredited platforms has been published yet; the accreditation mechanics sit in the pending Order and AEAT technical documentation expected October 2026. [europe.tho…euters.com]
• Businesses must also publish their e-invoice entry point. [marimon-abogados.com]

10.4. Interoperability

• Mandatory, free interconnection between private platforms, plus mandatory routing of every invoice to the SPFE, is the backbone of the model. [devenga.es]
• Foral administrations have dedicated provisions on the SPFE and on access to the information it stores. [noticias.j…idicas.com]
• Interoperability with Peppol or foreign networks is not addressed in the current framework.

10.5. Deadlines

• Faithful copy to SPFE: simultaneous with issuance. [sede.agenc…ria.gob.es]
• Status (acceptance/rejection) and payment messages: four days from each event. [ey.com]
• Contingency upload: four business days after incident resolution. [europe.tho…euters.com]
• General invoicing deadline (unchanged, RD 1619/2012): at the time of supply, or by the 16th day of the month following the supply where the recipient is a taxable person.
• SII: four days. VAT return Modelo 303: monthly for SII filers, with the deadline extended to the 30th of the following month. [gestorialaso.es] [blog.taxea…ategies.es]

11. Self-Billing

• 11.1. Self-billing remains permitted under Spanish VAT law (RD 1619/2012 Art. 5 — invoices issued by the customer or by a third party on behalf of the supplier), and is expressly supported in the e-invoicing mandate’s semantic model: AEAT confirmed in September 2026 “confirmed support for self-billing and third-party billing” in Annex I. [europe.tho…euters.com]
• 11.2. Yes — where the underlying transaction is in scope, the self-billed invoice must travel through the system (private platform and/or SPFE) like any other e-invoice, and the UBL faithful copy must reach the SPFE. [sede.agenc…ria.gob.es], [europe.tho…euters.com]
• 11.3. The substantive authorisation requirement is the pre-existing VAT one: a prior agreement between the parties, with the supplier accepting each invoice, under RD 1619/2012 Art. 5. RD 238/2026 introduces no new notification form; platform-level registration/representation mechanics are defined by the Order’s authentication and representation rules. [hacienda.gob.es]
• 11.4. Content rules are those of an ordinary invoice, issued in the supplier’s name and series, with the self-billing flag. [europe.tho…euters.com]
• 11.5. Yes — self-billing and third-party billing are identified in the Annex I semantic model. [europe.tho…euters.com]
• 11.6. Because the mandate only bites where both parties are Spain-established, a foreign buyer without Spanish establishment self-billing a Spanish supplier is outside the RD 238/2026 obligation — though the Spanish supplier remains subject to SII and its ordinary invoicing obligations. [taxnews.ey.com]
• 11.7. The standard status regime applies: the party in the recipient role must communicate acceptance/rejection and payment; absence of rejection = presumed acceptance. [devenga.es]
• VERI*FACTU interaction: RD 254/2025 clarified that SII filers are exempt from the SIF/VERI*FACTU obligation even where they self-bill on behalf of suppliers who are themselves in VERI*FACTU scope — an important point that removed earlier ambiguity in hybrid self-billing chains. [docnova.ai]

12. Triangulation & Special Scenarios

• 12.1. Triangulation. No specific rule exists in RD 238/2026. The practical outcome flows from Art. 3: a leg between two Spain-established parties is in scope; a leg involving a non-established party is not. At EU level, delegations have flagged that the updated CEN schema still lacks a triangulation code, which remains unresolved in the ViDA Explanatory Notes. Spanish intermediaries continue to report triangulation via Modelo 349 and SII, with the customary “inversión del sujeto pasivo” annotation. [vatcalc.com]
• 12.2. Chain transactions. Not specifically legislated. Each invoice in the chain is assessed independently against the establishment test. Cross-border treatment of chain transactions — including which Member State’s rules govern — is explicitly listed among the unsettled ViDA DRR issues. [vatcalc.com]
• 12.3. Cross-border reverse charge. Outbound invoices to non-established customers are outside the mandate but carry the standard reverse-charge annotation and are reported through SII/Modelo 349. Inbound reverse-charge invoices from foreign suppliers are recorded in the received-invoices ledger under SII; there is no obligation to route them through the SPFE or to report statuses on them. [taxnews.ey.com] [cleartax.com]
• 12.4. Zero-rated and exempt supplies. Handled through EN 16931 VAT category codes and exemption-reason fields; Annex I of the Order has been updated to incorporate new VAT categories from the revised EN 16931. Domestic exempt B2B supplies requiring a full invoice remain in scope of the mandate; zero-rated intra-EU supplies and exports fall outside by virtue of the establishment test. [europe.tho…euters.com] [taxnews.ey.com]
• 12.5. Local nuances.
  • Foral territories: Basque-domiciled taxpayers apply TicketBAI/Batuz rather than VERI*FACTU; Navarra applies the state regime. Determination is by tax domicile. RD 238/2026 has dedicated provisions for foral administrations’ role in, and access to, the SPFE. [frihet.io], [ideiatek.net] [noticias.j…idicas.com]
  • Construction sector: RD 238/2026 has a specific additional provision on computing the payment period where the retention under Law 38/1999 (Ordenación de la Edificación) has been applied. [noticias.j…idicas.com]
  • Public-sector subcontractors: specific transitional provision on their transmission of e-invoices. [noticias.j…idicas.com]
  • Statistical computation: a further additional provision fixes the start date for payment-period computation for statistical purposes only — separate from the commercial-law computation in Art. 15. [noticias.j…idicas.com]
  • VAT groups, fiscal representatives, call-off stock, bailiff sales: no specific rules have been legislated under the e-invoicing mandate.

13. Archiving & Retention

• 13.1. Central archiving. The SPFE is the universal and mandatory repository of all B2B e-invoices and holds status and payment data, with access provided to the various tax administrations under dedicated additional provisions. Central storage does not relieve taxpayers of their own statutory conservation obligations, which continue to arise under Art. 165 Ley 37/1992, Art. 29.2.e) LGT and Arts. 19–23 RD 1619/2012. No published retention period for SPFE-held data has been identified. [devenga.es], [noticias.j…idicas.com] [sede.agenc…ria.gob.es], [supercontable.com]
• 13.2. Format. Documents must be kept with their original content, in order — meaning the original structured XML, not a PDF rendition. Electronic means are expressly permitted. [supercontable.com], [sede.agenc…ria.gob.es]
• 13.3. Retention period.
  • General VAT/tax rule: the limitation period of 4 years (Art. 66 LGT). [sede.agenc…ria.gob.es]
  • Capital goods subject to the adjustment period: the adjustment period plus 4 years — i.e. effectively 9 years for movables (5+4) and 14 for immovables (10+4). [sede.agenc…ria.gob.es], [supercontable.com]
  • Investment gold: 5 years. [www3.agenc…ria.gob.es]
  • Commercial law (Art. 30 Código de Comercio): 6 years from the last entry in the books — the practical safe floor. [invoisio.com]
  • Note Art. 66 bis LGT, which gives the Administration 10 years to verify and investigate (e.g. loss carryforwards), effectively extending prudent retention. [supercontable.com]
• 13.4. Storage location. Storage outside Spain is permitted. Where conservation is performed by a third party not established in the EU — other than in the Canary Islands, Ceuta or Melilla, or in a country with a mutual-assistance instrument comparable to Directive 2010/24/EU and Regulation (EU) 904/2010 — it is only possible after prior notification to the AEAT (RD 1619/2012 Art. 19.4). The same prior-notification condition applies to electronic conservation in such third countries. [supercontable.com], [sede.agenc…ria.gob.es]
• 13.5. Integrity, authenticity, legibility. Must be guaranteed by any means throughout the retention period, including electronic means; the invoice must be recoverable identical to the one issued or received. Under VERI*FACTU, conservation, accessibility and legibility of all billing records is a distinct regulatory requirement, backed by hash chaining and an event log. [sede.agenc…ria.gob.es], [invoisio.com] [beel.es], [sede.agenc…ria.gob.es]
• 13.6. Audit accessibility. Access by the tax administration must be possible without delay, save duly justified cause. In addition, the AEAT and the foral administrations will have standing access to SPFE-stored invoice and payment data — a step-change in audit posture, since the authority will hold the data before any request is made. [sede.agenc…ria.gob.es] [noticias.j…idicas.com]

14. Penalties & Enforcement

14.1. Grace period / transitional enforcement

• No penalty-free period has been announced for the B2B mandate. The only transitional softeners are the 12-month PDF accompaniment and the four-business-day contingency window. [ey.com], [europe.tho…euters.com]
• For VERI*FACTU, no infringement can arise before each cohort’s date — 1 January 2027 for corporate income tax payers and 1 July 2027 for the self-employed. [factucheck.com]

14.2. and 14.3. Penalties and amounts

• Failure to issue e-invoices / to make e-invoicing available when obliged (Crea y Crece regime): fines of up to €10,000, applying the sanctioning regime of Law 56/2007 to the Art. 2 bis obligation. This figure comes from advisory commentary rather than a provision of RD 238/2026 itself, which contains no autonomous penalty catalogue — the mandate leans on the pre-existing LISI sanctioning framework, and this is a point worth validating with Spanish counsel before relying on it in a risk assessment. [copilotgestoria.com]
• Use of non-compliant billing software (Art. 201 bis.2 LGT): €50,000 per tax year, as a fixed pecuniary fine, classified as a serious infringement. It sanctions mere possession or use — no actual evasion is required. [factucheck.com], [beel.es]
• Manufacture, production or marketing of non-compliant systems (Art. 201 bis.1 LGT): €150,000 per year and per type of system; €1,000 per system marketed without the required certification/responsible declaration. [beel.es], [factucheck.com]
• Ordinary invoicing infringements (Art. 201 LGT): remain fully applicable and cumulative — generally a percentage of the amount of the incorrectly documented transactions, escalating where false invoices are involved. [factucheck.com]
• Late or incorrect SII submission (Art. 200 LGT): 0.5% of the invoice amount, minimum €300 per quarter. Failure to keep ledgers correctly is separately sanctioned; some commentary cites up to 2% of unrecorded invoice value under Art. 170 Ley 37/1992. [blog.taxea…ategies.es] [gestorialaso.es]
• Archiving violations: sanctioned under the general Art. 200/201 LGT record-keeping and invoicing regime rather than a bespoke rule. [factucheck.com]
• Intentional versus negligent: the Art. 201 bis fines are fixed and objective — they do not vary with turnover, invoice count or damage to the Treasury. Escalation is essentially temporal (per fiscal year), so a multi-year lapse produces multiple independent fines. [cofactu.com], [flexfood.es]
• Basque territories apply their own foral sanctioning regimes for TicketBAI breaches. [beply.es]

14.4. References

• Art. 201 bis LGT (introduced by Art. 13.21 Ley 11/2021, in force since 11 October 2021); Art. 29.2.j) LGT (introduced by Art. 13.4 Ley 11/2021); Arts. 200–201 LGT; Art. 170 Ley 37/1992; Art. 12 Ley 18/2022 / Art. 2 bis Ley 56/2007. [beel.es], [gestorialaso.es]
• Official texts: https://www.boe.es/buscar/act.php?id=BOE-A-2022-15818 (Ley 18/2022) and https://www.boe.es/eli/es/rd/2026/03/25/238 (RD 238/2026). [boe.es], [boe.es]

15. Pre-Filled VAT Returns

• 15.1. Yes — Spain already operates pre-filled VAT return assistance, through the Pre303 service, available to all taxpayers according to their activity profile, with specific service sets for SII filers, non-SII filers, landlords, simplified-regime taxpayers and exclusively-foral taxpayers with deferred import VAT. [sede.agenc…ria.gob.es]
• 15.2. Pre-filling covers the“Ventana censal IVA”, auto-completed identification boxes, and access to the taxpayer’s census data so discrepancies can be resolved before they delay refunds or trigger audits. For SII filers, AEAT describes the service as enabling automatic preparation of the VAT self-assessment (Pre303/LLAA) from the ledger records. Settlement figures still require taxpayer validation and input — Spain has an assisted return, not a fully determined one. Ancillary tools include a Modelo 303 simulator and a ledger validation service. [www3.agenc…ria.gob.es] [sede.agenc…ria.gob.es] [www3.agenc…ria.gob.es]
• 15.3. Not applicable — the service exists. No announced plan to convert Pre303 into a binding fully pre-determined return has been identified.
• 15.4. Pre-filling is data-source dependent: SII ledger records for SII filers; imported electronic ledgers for non-SII filers. The B2B e-invoicing data in the SPFE is an obvious future feed — and the Senate’s August 2026 motion points in exactly that direction — but no legal linkage between SPFE data and Pre303 has been established. [sede.agenc…ria.gob.es] [dynatos.com]
• 15.5. In the Basque Country, TicketBAI/Batuz already pre-loads Modelos 303, 347 and 390 and draft IRPF/IS returns from submitted invoice data — a working preview of where the state system is heading. ViDA’s pre-filled-return ambitions are served by, but not yet formally connected to, the Spanish architecture. [guiafiscal.es], [frihet.io]

16. ViDA Readiness

16.1. Position relative to ViDA

• Spain transposed the first ViDA wave via an Anteproyecto de Ley approved by the Council of Ministers on 25 November 2025, published for public hearing on 1 December 2025 (comments to 23 December 2025), amending Ley 37/1992 — covering OSS/distance-sales clarifications, broader Non-Union OSS scope, and a representative requirement for certain non-EU businesses claiming refunds under Art. 119 bis. A second reading of the ViDA transposition bill was subsequently approved. [rtcsuite.com] [dynatos.com]
• Not yet transposed: platform deemed-supplier rules (EU date 1 July 2028 — though Spain has signalled it may seek a derogation to apply them earlier), cross-border B2B e-invoicing and the EU DRR (1 July 2030), and the alignment of SII with the EU model (1 January 2035). [rtcsuite.com], [kpmg.com]
• Overall: ahead on domestic infrastructure, behind on convergence.

16.2. Alignment of the national system

• Strong alignment on semantics: EN 16931 is the mandatory semantic model, with Annex I tracking updated EN 16931 content including new VAT categories. [europe.tho…euters.com], [marimon-abogados.com]
• Partial alignment on syntax: UBL and CII are ViDA-native; EDIFACT and Facturae are national accommodations whose long-term status depends on the unresolved EU debate about allowable formats and the status of EDIFACT. [devenga.es], [vatcalc.com]
• Weak alignment on transport: ebXML into a national repository rather than a Peppol-style four-corner network raises interoperability questions for 2030. [europe.tho…euters.com]
• Key gap — SII: because SII existed on 1 January 2024, Spain has until 1 January 2035 to conform it to the EU standard. [kpmg.com]
• Key gap — purpose mismatch: the Spanish B2B system is a late-payment instrument with tax-authority access, whereas ViDA DRR is a VAT-control instrument. Bridging the two will require legislative work Spain has not yet begun. [hacienda.gob.es]

16.3. Cross-border digital reporting

• Spain’s mandate excludes cross-border B2B, which is exactly the population ViDA DRR will capture from 1 July 2030, with 10-day e-reporting and the withdrawal of EC Sales Lists (Modelo 349). [vatcalc.com], [kpmg.com]
• No mechanism has been announced for feeding SPFE data into an EU-level exchange system.
• The third draft ViDA Explanatory Notes (June 2026) remain open on issuance/transmission/acceptance definitions, working-versus-calendar days, correction handling, attachments, the missing triangulation code and cross-border rule-of-which-Member-State — all of which bear directly on how Spain’s system must behave; completion is targeted for early 2027. [vatcalc.com]

16.4. Implications for businesses

• Companies building for RD 238/2026 will have EN 16931-capable, structured, status-aware invoicing — genuinely reusable for ViDA.
• But they will need additional work for: cross-border scope extension, DRR transmission channels, the 10-day cross-border reporting clock, Modelo 349 retirement, and any eventual SII/DRR convergence by 2035.
• Early adopters benefit mainly through sequencing — the Spanish faithful-copy/status mechanics are strictly harder than ViDA’s baseline, so ViDA compliance is largely a subset for firms that have already built for Spain.
• The Senate’s August 2026 motion urging a single, ViDA-compatible roadmap merging VERI*FACTU, SII and B2B e-invoicing is non-binding and changes no current date, but signals political recognition of the triple-reporting burden and asks for transition periods that avoid repeated technology investment, especially for SMEs. [dynatos.com], [europe.tho…euters.com]

17. Impact on SMEs and Startups

• 17.1. Phased onboarding. SMEs and autónomos sit in wave 2 (projected 1 October 2028), a full year behind large taxpayers, with payment-status reporting for income-attribution entities deferred a further year to 2029. The asymmetry is real but incomplete: an SME buying from a wave-1 supplier must be able to receive structured invoices and report statuses from October 2027, before its own issuing obligation bites. [legaltoday.com], [europe.tho…euters.com] [sede.agenc…ria.gob.es]
• 17.2. Government support and free tools. AEAT must provide a free application/form for issuing e-invoices, generating status information including full payment, and making it available to counterparties and the administration — explicitly aimed at businesses without their own SIF. A test environment and complete technical documentation are targeted for October 2026. AEAT also provides a last-resort free web application with VERI*FACTU status for businesses lacking billing software (RRSIF Art. 7.b), plus SII/VAT virtual assistants and the SII deadline calculator. [sede.agenc…ria.gob.es] [europe.tho…euters.com] [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
• 17.3. Simplified regimes and threshold exemptions. There is no turnover-based exemption — the €8m figure governs timing only. The real de minimis is the simplified-invoice exclusion (RD 1619/2012 Art. 4), which removes most small-ticket and retail documentation from the mandate — except qualified simplified invoices. SII remains reserved to >€6m turnover, VAT groups, REDEME registrants and (since 01/01/2025) holders of and extractors from fuel tax warehouses. [sede.agenc…ria.gob.es] [supercontable.com] [sede.agenc…ria.gob.es]
• 17.4. Subsidies. Kit Digital (Next Generation EU funds, managed by Red.es) includes an“factura electrónica” solution category. Status as at September 2026: the five original calls closed on 31 October 2025; Orden TDF/39/2026 (BOE 28 January 2026) amended the regulatory bases to allow reallocation of unspent remnant funds, keeping the programme alive until funds are exhausted rather than to a fixed date — but no call is currently open for new applications, and a new Red.es resolution with budget and deadlines would be required. Voucher amounts by segment: up to €12,000 (10–49 employees), €6,000 (3–9), €2,000–3,000 (0–2/autónomos), with higher brackets for medium-sized firms in segments IV/V. Holders of awarded vouchers must focus on justification within deadline and four-year document custody. [angelorteg…castro.com], [kitdigital-2026.com], [acelerapym…-aecim.com] [lisdatasolutions.com], [kitdigital-2026.com] [angelorteg…castro.com]
• 17.5. Compliance costs. One-time: ERP/billing upgrades to produce EN 16931-compliant XML, platform integration, NIF/schema validation logic, staff training. Ongoing: private platform fees (though interconnection between platforms must be free) or the free SPFE route, plus maintenance. The blunt practitioner point: generating XML is cheap; re-engineering processes, statuses, support, reconciliation and accounting around that XML is expensive. [devenga.es] [facturaok.es]
• 17.6. Cash flow and operational benefits. The regime is purpose-built to shorten payment cycles by making effective payment dates visible and auditable, which structurally favours SMEs as creditors. Secondary benefits: automated data capture, earlier error detection through platform validations, elimination of paper. SII adopters additionally gain exemption from Modelos 347, 340 and 390 and the extended monthly filing deadline. [easysoft.es] [blog.taxea…ategies.es]
• 17.7. Net burden. Short term clearly negative for SMEs: three overlapping regimes (B2B e-invoicing, VERI*FACTU from 2027, and TicketBAI/Batuz for Basque taxpayers) with distinct timelines, formats and penalties. Medium term, the payment-discipline effect and pre-filled-return trajectory should net positive — but only if the convergence the Senate called for actually happens. [frihet.io] [dynatos.com]
• 17.8. Market impact. A significant new market for platform providers and gestorías; advantage to early adopters through sandbox access from October 2026; interoperability risk concentrated in the obligation of platforms to interconnect on demand and transform between four syntaxes — a technically demanding requirement that will separate credible providers from the rest. [devenga.es], [europe.tho…euters.com]
• 17.9. Official assessments of SME readiness. No published government or EU assessment of Spanish SME readiness for the B2B mandate has been identified. The RD’s preamble contains descriptive SME statistics (99% of firms, 62% of GVA, 66% of employment) rather than a readiness evaluation. The Senate motion’s call for extra SME adaptation time is the clearest institutional acknowledgement of a readiness concern. Note also that the 2025 EC Country Sheet for Spain carries a “NO VERIFICATION” status, meaning its B2B mandate fields were not officially validated by Spanish national representatives — a caution flag on EU-level data. [boe.es] [dynatos.com] [e-invoicing.org]

18. Official References & Sources

18.1. Government portals

• AEAT mandatory e-invoicing news page: https://sede.agenciatributaria.gob.es/Sede/en_gb/todas-noticias/2026/marzo/31/facturacion-electronica-obligatoria.html [sede.agenc…ria.gob.es]
• AEAT 2026 regulatory novelties (RD 238/2026): https://sede.agenciatributaria.gob.es/Sede/iva/novedades-iva/novedades-normativa-2026/real-decreto-238-2026-25-marzo.html [sede.agenc…ria.gob.es]
• AEAT SII portal: https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/suministro-inmediato-informacion.html [sede.agenc…ria.gob.es]
• AEAT SIF/VERI*FACTU portal and FAQs (updated 21 July 2026): https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes.html [sede.agenc…ria.gob.es]
• Pre303: https://sede.agenciatributaria.gob.es/Sede/iva/pre-303.html [sede.agenc…ria.gob.es]
• FACe (B2G): https://face.gob.es/en — note migration to the FACe Proveedores portal. [face.gob.es]
• Facturae format portal: https://www.facturae.gob.es/formato/ultima-version [facturae.gob.es]
• Basque Government TicketBAI: https://www.euskadi.eus/ticketbai/ [euskadi.eus]
• European Commission ViDA: https://taxation-customs.ec.europa.eu/taxation/vat/vat-digital-age-vida_en [taxation-c….europa.eu]

18.2. Legislative texts

• RD 238/2026: BOE núm. 79, 31/03/2026, pp. 47444–47466 — https://www.boe.es/diario_boe/txt.php?id=BOE-A-2026-7295; ELI https://www.boe.es/eli/es/rd/2026/03/25/238; PDF https://www.boe.es/boe/dias/2026/03/31/pdfs/BOE-A-2026-7295.pdf [boe.es], [sede.agenc…ria.gob.es]
• Ley 18/2022: BOE núm. 234, 29/09/2022 — https://www.boe.es/buscar/act.php?id=BOE-A-2022-15818 [boe.es]
• RD 1619/2012 (consolidated, last updated 31/03/2026) — https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696 [boe.es]
• RD 1007/2023, Orden HAC/1177/2024, RD 254/2025, RDL 15/2025 (BOE-A-2025-24446). [easysoft.es], [spun.es]
• RD 596/2016 / Orden HFP/417/2017 (SII). [gestorialaso.es]
• ViDA: Directive (EU) 2025/516, Regulation (EU) 2025/517, Implementing Regulation (EU) 2025/518, OJ 25/03/2025. [taxation-c….europa.eu]

18.3. Technical specifications

• Draft Ministerial Order on the SPFE (17 April 2026): https://www.hacienda.gob.es/sgt/normativadoctrina/proyectos/16042026-proyecto-pom-factura-electronica.pdf [hacienda.gob.es]
• Executive summary / MAIN of the draft Order: https://www.hacienda.gob.es/sgt/normativadoctrina/proyectos/16042026-main-pom-factura-electronica.pdf [hacienda.gob.es]
• AEAT informative note on RD 238/2026: https://sede.agenciatributaria.gob.es/static_files/Sede/Actualidad/Novedades/2026/Nota_informativa_RD_Facturacion.pdf [sede.agenc…ria.gob.es]
• Facturae 3.2.2 XSD schema and field descriptions. [facturae.gob.es]
• SPFE technical specifications and test environment: pending, expected October 2026 on the AEAT electronic headquarters. [europe.tho…euters.com]

18.4. Tax authority guidance

• VERI*FACTU FAQ (21 July 2026); SII general/technical information and virtual assistants; Pre303 FAQs (v1.1, applicable from 23 April 2026). [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
• AEAT SPFE regulatory and technical seminar, 10 September 2026. [europe.tho…euters.com]

18.5. Advisory and technology publications

• EY: “Spanish Government approves Royal Decree implementing mandatory B2B electronic invoicing” (25 March 2026) — https://www.ey.com/en_gl/technical/tax-alerts/spanish-government-approves-royal-decree-implementing-mandatory-b2b-electronic-invoicing; and the earlier draft-regulation alert. [ey.com] [ey.com]
• Cuatrecasas: Legal Flash on RD 238/2026 plus a comparative table of B2B e-invoicing versus VERI*FACTU (1 April 2026). [cuatrecasas.com]
• KPMG Abogados: ViDA adoption tax alert (April 2025), including the SII/2035 alignment point. [kpmg.com]
• BDO: “Spain — E-Invoicing, Billing Systems and the ViDA Package”. [bdo.global]
• Thomson Reuters Regulatory Atlas — Spain: the most current rolling tracker, including the 14 September 2026 SPFE webinar summary — https://europe.thomsonreuters.com/compliance/regulatory-updates/spain [europe.tho…euters.com]
• Marimón Abogados, Ruiz Ballesteros, Legal Today (calendar and SPFE detail from the draft Order). [marimon-abogados.com], [ruizballesteros.es], [legaltoday.com]
• Vertex, Dynatos, RTC Suite, vatcalc, ClearTax for technology-advisor perspectives and ViDA interaction. [vertexinc.com], [dynatos.com], [rtcsuite.com], [vatcalc.com], [cleartax.com]

18.6. Link caveats

• FACe: the legacy portal now supports historical consultation only for invoices submitted up to 27/02/2026; live submission has moved to FACe Proveedores. Any bookmark to the old submission path is effectively stale. [face.gob.es]
• The draft Ministerial Order PDFs on hacienda.gob.es are consultation-stage documents superseded in substance by the final eleven-article text; they should not be treated as the operative source once the BOE version publishes. [europe.tho…euters.com]
• Beware of stale secondary sources. A large volume of online content still cites the superseded VERI*FACTU dates of 1 January 2026 / 1 July 2026, and some cites July 2026 as a general e-invoicing go-live — all incorrect following RDL 15/2025. Similarly, sources conflating VERI*FACTU with the Crea y Crece B2B mandate are common and wrong. [eu-einvoicing.com], [esimahora.com], [docs.frihet.io] [cuatrecasas.com]
• EC Country Sheet Spain 2025 carries “NO VERIFICATION” status — its B2B fields are not nationally validated. [e-invoicing.org]

19. Summary & Key Takeaways

• 19.1. Scope. Mandatory structured e-invoicing for domestic B2B where both issuer and recipient are established in Spain. Out of scope: B2C, cross-border B2B, exports/imports, intra-EU acquisitions, simplified invoices (except qualified ones), electricity and organised gas market operator regulated activities, and IATA CASS/BSP/SIS-ICH settled flows. B2G is a separate, already-live regime via FACe. [taxnews.ey.com], [supercontable.com], [supercontable.com]
• 19.2. Format. EN 16931 semantic model in UBL, CII, EDIFACT or Facturae; UBL mandatory for the public solution and for the faithful copy. PDF/paper cease to be valid for in-scope invoices, save the 12-month PDF accompaniment for large issuers. [devenga.es], [ey.com]
• 19.3. Timeline. RD 238/2026 in force 20 April 2026. Ministerial Order targeted for 1 October 2026 (still unpublished at the time of writing). Then: SPFE available by 1 August 2027; 1 October 2027 for >€8m turnover and for private-platform interconnection; 1 October 2028 for everyone else; 1 October 2029 for payment-status reporting by income-attribution entities. Separately, VERI*FACTU: 1 January 2027 (companies) and 1 July 2027 (autónomos). [europe.tho…euters.com], [legaltoday.com], [eu-einvoicing.com]
• 19.4. How it works. Hybrid decentralised model: private platforms and/or the AEAT public solution, with the SPFE as universal mandatory repository; no pre-clearance; simultaneous UBL faithful copy; unique invoice code (NIF + series/number + date); automatic syntax and content validation; ebXML transport; encrypted invoice locator for retrieval; four-business-day contingency window. [sede.agenc…ria.gob.es], [europe.tho…euters.com]
• 19.5. Key obligations. Issue and receive structured e-invoices; transmit the faithful copy; publish your e-invoice entry point; report acceptance/rejection and full effective payment with dates within four days; archive originals; and, in parallel, keep complying with SII (four days) and VERI*FACTU/TicketBAI software rules. [marimon-abogados.com], [sede.agenc…ria.gob.es], [frihet.io]
• 19.6. Main risks. Art. 201 bis LGT fixed fines of €50,000 per year for non-compliant billing software (possession alone suffices) and €150,000 for producers; up to €10,000 under the Crea y Crece/LISI regime for failing to provide e-invoices; 0.5% / €300 minimum for late SII; automatic rejection for NIF check-digit, XSD, signature or date errors; the buyer-side trap that silence equals acceptance and thus starts the payment clock; operational disruption from running three regimes simultaneously; and planning risk while the Ministerial Order remains unpublished. [factucheck.com], [copilotgestoria.com], [blog.taxea…ategies.es], [devenga.es], [frihet.io]
• 19.7. SME implications. One-year deferral to 2028 (2029 for some status reporting), a free AEAT issuing tool, free mandatory platform interconnection, and Kit Digital funding for those already holding vouchers — but no open Kit Digital call, no turnover exemption, and an obligation to receive structured invoices from wave-1 suppliers a year before their own issuing date. [legaltoday.com], [sede.agenc…ria.gob.es], [kitdigital-2026.com]
• 19.8. ViDA readiness. Semantically well aligned (EN 16931), structurally divergent (national repository, four syntaxes, ebXML rather than Peppol), and materially incomplete on cross-border — which ViDA DRR captures from 1 July 2030, with SII alignment due by 1 January 2035. The Senate has called for a single merged roadmap; nothing binding has followed. [europe.tho…euters.com], [kpmg.com], [dynatos.com]
• 19.9. Critical dates and next steps.
  • Now – October 2026: monitor the BOE daily for the Ministerial Order; it is the trigger for every downstream date, and the projected 1 October 2026 date is still a target, not law. [frihet.io]
  • October 2026: obtain the published technical specifications and register for the AEAT test environment; re-baseline the ERP mapping against the late changes — corrective invoices via business groups rather than UBL extensions, updated EN 16931 VAT categories, relaxed faithful-copy cardinality. [europe.tho…euters.com]
  • By 1 January 2027 / 1 July 2027: confirm VERI*FACTU status. If the entity is an SII filer it is exempt — verify this entity by entity, since it materially reduces scope. [docnova.ai]
  • Through 2027: decide public solution versus private platform (or both); confirm platform capability on four-syntax transformation and free interconnection; establish apoderamiento/social collaboration for advisers; build the status and payment-date reporting process, which is an AP/treasury change, not an AR change, and is the genuinely novel obligation. [devenga.es], [easysoft.es]
  • By 1 October 2027: wave-1 issuing live; all counterparties must be able to receive and report statuses.
  • By 1 October 2028: full population live.
  • Open items to track: the calendar-versus-business-day definition of the four-day status deadline; the treatment of VAT-registered but non-established entities; any sectoral exclusion orders under Art. 4.2; and the SII/VERI*FACTU/B2B convergence roadmap ahead of ViDA. [frihet.io], [supercontable.com], [dynatos.com]

---

• Basque Country – TicketBAI and Batuz:
  • TicketBAI (TBAI): This is a mandatory e-invoicing and instantaneous reporting system rolled out by the three Basque provincial tax authorities (Diputaciones Forales of Álava, Bizkaia, and Gipuzkoa). It aims to combat tax evasion by ensuring every invoice issued by a business is digitally reported to the tax authorities.
  • How it works: Businesses in the Basque Country must use certified billing software that is TicketBAI-compliant. Each invoice generated has an embedded TBAI code and a QR code, and the software automatically sends the invoice data (XML file with invoice details and a cryptographic hash) to the provincial tax authority’s server at the moment of issuance. This way, the tax office receives transaction data in real time, similar to SII but at the point of invoice creation. [bdo.global], [bdo.global]
  • Timeline:
    • Gipuzkoa was first: TicketBAI became mandatory for most taxpayers during 2022, with a phased schedule by sectors (starting with large companies and certain professionals) and full coverage by end of 2022.
    • Álava (Araba) closely followed and also had it mandatory by end of 2022 for virtually all businesses.
    • Bizkaia took a slightly different approach by integrating TicketBAI into a larger program called Batuz. Batuz includes TicketBAI + additional ledger reporting to Bizkaia’s Hacienda. Bizkaia made TicketBAI mandatory from January 2024 for all businesses (after a voluntary period in 2022–2023). However, during 2024 Bizkaia offered a grace period with no fines for those who show they are trying to comply. By 2025, compliance is expected to be strict. All three provinces now either have or are finishing the rollout of compulsory TicketBAI for 100% of companies and self-employed under their jurisdiction.
  • Scope: TicketBAI in Basque Country applies to all transactions (B2B, B2C, etc.) by taxpayers under the Basque income tax/VAT regimes. If a business pays its taxes to the Basque Hacienda, it must use TicketBAI for all its invoices, whether the customer is another business, a consumer, or a government entity. It’s not limited to certain sizes or sectors (only the rollout schedule was staged).
  • Data & Format: The TicketBAI XML includes detailed invoice data (similar to an invoice itself) plus additional fields like a unique TBAI identifier and digital signature computed by the software. The QR code on each printed or PDF invoice allows the client or tax inspector to scan and verify the invoice’s authenticity on the tax authority’s system. [bdo.global]
  • Use of data: The Basque tax authorities use TicketBAI data to cross-check declared income. Bizkaia’s Batuz system goes further by using TicketBAI inputs to pre-fill tax returns (VAT, corporate tax, income tax) for the taxpayer – a service that will start when Batuz is fully live.
  • Penalties: The Basque norms set hefty penalties to ensure compliance. For example, in Gipuzkoa and Álava, not adopting TicketBAI on time could result in a fine of 20% of the prior year’s turnover (minimum €20,000). Bizkaia set fines of €20,000 for failure to comply, with incremental penalties per each subsequent infringement. These were intentionally high to discourage any idea of risking non-compliance. However, tax credits (of up to 30% of software costs) were offered as incentives for early adopters, and initial enforcement was somewhat lenient. By now, though, businesses in those areas must be compliant or face sanctions.
  • Interaction with state system: If a Basque business is in SII (say a large company in Bilbao), it actually must do both SII and TicketBAI reporting. However, the state AEAT and the Basque Haciendas are working on data-sharing so that duplication is minimized. Still, formally, those businesses have to submit invoice data to both systems (one to AEAT for VAT SII, and one to their Diputación via TicketBAI). The new national VeriFactu system is separate; Basque taxpayers under TicketBAI are generally not subject to the national e-invoicing mandate as long as they don’t fall under state tax authority.
• Navarra – Digital Invoicing System:
  • Navarra, like the Basque provinces, has an autonomous tax authority. It has announced a plan for its own version of TicketBAI. Often referred to as “TicketBAI Navarra” or the Navarrese Electronic Invoice System, it will similarly require all businesses under Navarrese tax regime to issue invoices with secure, traceable software.
  • Timeline: Navarra’s government approved in 2023 the roadmap to implement mandatory e-invoicing. A voluntary phase started, and the intention is to mandate it by 2025 or 2026 for all sectors. The exact dates are being set by local law; the latest information suggests a target of 2025 for large companies and a bit later for smaller ones, but subject to confirmation. By 2026, Navarra aims to have every taxpayer issuing only electronic invoices. (Navarra needed to legislate this independently, and coordinate with the central government since many businesses operate across regions.) [docuten.com]
  • Technical aspects: Expected to be very similar to TicketBAI – unique invoice files with QR codes, immediate communication to Navarrese Hacienda. It may even use the same software certifications as TicketBAI (so that software developers don’t have to reinvent the wheel for Navarra).
  • Penalties and incentives: Navarra will likely mirror the Basque approach: strong penalties for non-compliance, possibly coupled with transitional incentives (like tax deductions for software costs). The goal is to eliminate the possibility of hidden sales by requiring every sale to be logged with the tax office in real time.
  • Until Navarre’s system is in force, businesses in Navarra continue with current requirements (which could include SII if they are in REDEME, etc., but not TicketBAI yet).
• Other Regions:
  • The Canary Islands (which have their IGIC tax) have an electronic invoice and ledger reporting system called DIVA IGIC (implemented around 2019) for certain transactions, but it’s not as extensive as SII. They may consider expanding digital reporting as well, but it is separate from the mainland VAT system.
  • Summary: Regional mandates like TicketBAI are additional layers of requirement but only apply to those under those jurisdictions. For companies operating nationally, the upcoming state e-invoicing (VeriFactu) and SII are the main ones to follow, but those in Basque/Navarra have to comply with local rules until perhaps a future harmonization occurs.

---

• See also
  • E-Invoicing/Real Time Reporting – What can you find on VATupdate.com
  • Worldwide Upcoming E-Invoicing mandates, implementations and changes – Chronological
  • Collection of E-Invoicing Guides – Worldwide – VATupdate
  • Briefing / Comprehensive Guides (incl. podcasts)

• Join the Linkedin Group on Global E-Invoicing/E-Reporting/SAF-T Developments, click HERE

---

 

---

---