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

Last update: June 4, 2026

 

---

 

Click on the logo to visit the website

1. Scope of the Mandate

1.1. Overview of Obligations

Spain’s e-invoicing framework rests on three complementary regulatory pillars that together define the full scope of obligations for businesses:

• Crea y Crece (Law 18/2022) and Royal Decree 238/2026: Govern the format, transmission, exchange, and status reporting of B2B invoices between trading partners. Royal Decree 238/2026, published in the BOE on 31 March 2026, establishes the legal architecture of the B2B e-invoicing system. [rtcsuite.com]
• Veri*factu (Royal Decree 1007/2023): Regulates how invoicing software generates invoices, requiring certified billing systems to produce tamper-proof, sequentially chained invoice records with a digital fingerprint, QR code, and timestamp. Businesses under SII are exempt from Veri*factu. [marosavat.com]
• SII (Suministro Inmediato de Información): A near-real-time VAT data reporting obligation for large taxpayers (turnover above €6,010,121.04), VAT groups, and businesses under the REDEME scheme, operational since July 2017. SII requires structured XML submission of invoice data to AEAT within four calendar days of issuance or receipt. [rtcsuite.com]

1.2. Applicable Transactions

• Domestic B2B: The core scope of the Crea y Crece mandate. All transactions between businesses and professionals (empresarios y profesionales) established in Spain are covered, where the recipient is a business or professional with its headquarters, permanent establishment, or habitual residence in Spain. Invoices must be issued in a structured electronic format; PDF alone will no longer suffice. [taxnews.ey.com], [vertexinc.com]
• Domestic B2C: Explicitly excluded from the B2B e-invoicing mandate under Crea y Crece. Simplified invoices directed at final consumers remain outside scope. [taxnews.ey.com], [vertexinc.com]
• Domestic B2G: Mandatory since 1 January 2015 under Law 25/2013 for all invoices to Spanish public administrations, using the Facturae XML format submitted via the FACe platform. This obligation is separate from and unaffected by the Crea y Crece B2B mandate. [globalvatc…liance.com], [ec.europa.eu]
• Intra-EU Acquisitions and Supplies: Cross-border transactions are currently out of scope for the Crea y Crece B2B e-invoicing mandate. However, intra-EU transactions must still be reported under SII (for businesses subject to SII) within four calendar days. [vertexinc.com], [avalara.com]
• Imports and Exports: Not covered by the B2B e-invoicing mandate under Crea y Crece. Standard VAT reporting rules apply (SII for large taxpayers). [vertexinc.com]
• Cross-border B2B Transactions: Explicitly excluded from the current Crea y Crece scope. Future scope expansion may follow broader EU digital VAT developments, notably the ViDA initiative (effective 1 July 2030 for intra-Community reporting). [vertexinc.com], [rtcsuite.com]

1.3. Inclusion of Special Transaction Types

• Self-billing: The obligation to issue, transmit, and deliver electronic invoices extends to cases in which the invoice is issued by the recipient of the transaction or by third parties, in accordance with Article 5 of the Invoicing Regulations (RD 1619/2012). [cuatrecasas.com], [stripe.com]
• Simplified invoices: Transactions documented by means of simplified invoices under Article 4 of the Invoicing Regulations are excluded. However, “qualified” simplified invoices (Article 7.2 of RD 1619/2012) — where the recipient is identified as a business or professional for VAT deduction purposes — are included. [blnpalao.com], [cuatrecasas.com]
• Triangulation and chain transactions: The B2B mandate applies to domestic transactions where both parties are established in Spain. Cross-border legs of triangular or chain transactions fall outside the current Crea y Crece scope. Reporting under SII continues to apply for intra-EU elements where relevant. [vertexinc.com]
• Special VAT regimes (margin schemes, travel agents): No specific exclusion for special VAT regimes has been published in the Royal Decree or the draft Ministerial Order, except for sectors specifically excluded by the Second Additional Provision of RD 238/2026 (e.g., regulated electricity and gas market operators, IATA clearing-house settlements — CASS, BSP, SIS-ICH). The Ministry of Economy may grant temporary sector-specific exclusions where compliance would materially disrupt an industry’s functioning. [rtcsuite.com]

2. Taxable Persons in Scope

2.1. Established Entities

• All businesses and professionals (empresarios y profesionales) as defined in Article 5 of Law 37/1992 (Spanish VAT Law) who are required to issue and deliver invoices under the Invoicing Regulations (RD 1619/2012) for transactions where the recipient is another business or professional established in Spain. [cuatrecasas.com], [assets.kpmg.com]
• This includes all legal entities subject to Corporate Income Tax, sole traders (autónomos), microenterprises, and self-employed professionals. The €8 million turnover threshold governs only the sequencing of the phased rollout — every entity must comply by the final deadline. [rtcsuite.com]

2.2. Non-Established Entities with VAT Registration

• Non-residents with a permanent establishment (PE) in Spain: Full compliance with all systems (B2G, SII, Veri*factu, B2B) is required. [globalvatc…liance.com]
• Non-established businesses with a Spanish VAT registration but no PE: The position has not been definitively clarified in the published texts. According to Marosa VAT, “businesses in this situation should monitor further guidance.” [marosavat.com]

2.3. Foreign Entities Without Fixed Establishments

• Non-residents without a PE: Only B2G obligations apply (if they supply goods/services to Spanish public administrations). They are currently not within scope of the B2B e-invoicing mandate. [globalvatc…liance.com]

2.4. Exemptions and Sector-Specific Rules

• Businesses already under the SII reporting system are exempt from Veri*factu (but not from Crea y Crece). [rtcsuite.com]
• The Basque Country and Navarre have their own fiscal regimes (TicketBAI and Batuz/specific regulations) and are outside the scope of the state-level Veri*factu obligation. [globalvatc…liance.com]
• Specific exclusions: regulated electricity and gas market operators, IATA clearing-house settlements (CASS, BSP, SIS-ICH), and certain provisions under the twenty-first Additional Provision of Law 56/2007. [rtcsuite.com]

3. Implementation Timeline

3.1. Legislative Adoption

• September 2022: Law 18/2022 (Ley Crea y Crece) enacted, introducing the B2B e-invoicing obligation (Article 12). [rtcsuite.com]
• December 2023: Royal Decree 1007/2023 approved, establishing Veri*factu technical requirements. [marosavat.com]
• 24 March 2026: Council of Ministers approves Royal Decree 238/2026 implementing the B2B e-invoicing system. [kpmg.com]
• 31 March 2026: Royal Decree 238/2026 published in the BOE. Entered into force on 20 April 2026 (20 days after publication). [rtcsuite.com], [e-invoice.app]
• 17 April 2026: Draft Ministerial Order published for public consultation (open until 8 May 2026), setting the technical specifications of the public platform (SPFE). [rtcsuite.com]

3.2. Mandatory Go-Live Dates (B2B E-Invoicing — Crea y Crece)

All compliance deadlines run from the entry into force of the Ministerial Order, expected to be 1 October 2026 (subject to final publication):

• 1 October 2027 (12 months): Mandatory for businesses with annual turnover > €8 million — issuance, reception, invoice status reporting, and private platform obligations all apply. [rtcsuite.com], [marosavat.com]
• 1 October 2028 (24 months): Mandatory for all remaining businesses and professionals — issuance and reception apply. Payment status reporting becomes mandatory for SME legal entities. [rtcsuite.com], [marosavat.com]
• 1 October 2029 (36 months): Payment status reporting becomes mandatory for natural persons and entities under the income attribution regime with turnover ≤ €8 million. Until this date, status reporting is voluntary for this group. [rtcsuite.com], [marosavat.com]
• By 1 August 2027: The public solution (SPFE) must be operational (at least two months before the first effective application date). [rtcsuite.com]

3.3. Veri*factu Deadlines (Certified Invoicing Software)

Following delays (most recently via Royal Decree-Law 15/2025):

• 1 January 2027: Corporate Income Tax taxpayers. [marosavat.com]
• 1 July 2027: All other taxpayers (sole traders and non-CIT payers). [marosavat.com]
• Software manufacturers must ensure availability of certified invoicing software from 29 July 2025. [marosavat.com]

3.4. Grace Periods and Transitional Measures

• During the first 12 months after each wave takes effect, issuers must accompany structured e-invoices with a PDF document ensuring legibility — unless the recipient expressly agrees to receive the structured format alone. [rtcsuite.com], [taxnews.ey.com]
• Subcontractors using the existing FACeB2B registry have 24 months to migrate to the new system. [rtcsuite.com]

Important caveat: The Ministerial Order has not yet been formally published in the BOE as of June 2026. All dates should be monitored as the Order progresses through the legislative process. [marosavat.com]

4. Technical & Functional Requirements

4.1. E-Invoice Specifications

4.1.1. Required E-Invoice Format

• All e-invoices must conform to the EN 16931 semantic data model. [rtcsuite.com], [vertexinc.com]
• UBL (Universal Business Language) is the mandatory syntax for the public solution (SPFE) and for faithful copies (copias fieles). Peppol BIS messages are accepted where they employ UBL and comply with EN 16931. [rtcsuite.com]
• Four syntaxes are accepted for exchange via private platforms: UBL, CII (Cross Industry Invoice — UN/CEFACT XML), EDIFACT (retained under ISO 9735 for industries with legacy EDI infrastructure), and Facturae (Spain’s national XML format, mandatory for B2G via FACe since 2015). [rtcsuite.com], [vertexinc.com]
• Facturae remains valid for B2B exchange on private platforms but cannot be used for invoices or copies submitted to the public solution. [rtcsuite.com]
• PDF, Excel, and paper formats are not accepted as electronic invoices under the new mandate. [kpmg.com]

4.1.2. Mandatory Data Fields

• Each invoice must carry a unique identification code based on the concatenation of: the issuer’s NIF (tax identification number), the invoice number and series, and the issuance date. [rtcsuite.com], [marosavat.com]
• Mandatory content must satisfy the minimum requirements of Royal Decree 1619/2012 (the Invoicing Regulations), including: invoice number, date of issue, supplier and customer details (name, NIF, address), description of goods/services, taxable base, applicable VAT rate(s), VAT amount, and total amount. [rtcsuite.com]
• No attachments or embedded files are permitted in the public solution. [rtcsuite.com]

4.1.3. E-Invoice Validation

• E-invoices submitted to the public solution are subject to dual technical validation: syntax validation via an XSD validator (XML Schema Definition) checking UBL structure, and semantic validation via a Schematron model based on the EN 16931 standard (2026 version), published in public repositories on GitHub. [marosavat.com]

4.2. E-Reporting Specifications (Invoice Status Reporting)

4.2.1. Mandatory Status Reporting

A distinctive feature of the Spanish system is the mandatory reporting of invoice status throughout its lifecycle. Recipients (buyers) must report to the SPFE:

• Mandatory statuses (within 4 calendar days, excluding Saturdays, Sundays, and national holidays):
  • Commercial acceptance or rejection, with the date. [rtcsuite.com]
  • Full effective payment, with the actual payment date. [rtcsuite.com]
  • Payment due date. [marosavat.com]
• Optional statuses:
  • Partial acceptance or rejection.
  • Partial payment (with amount and date).
  • Assignment to a third party for collection or payment. [rtcsuite.com]
• Issuer (supplier) may report: Effective collection (cobro efectivo), non-payment (impago), and discrepancies with dates reported by the recipient. [marosavat.com]
• In the absence of rejection or a corrective invoice, the invoice is presumed accepted. [rtcsuite.com]
• The effective payment date is defined strictly as the date on which the supplier actually receives the funds — not the date a payment instruction is initiated. [rtcsuite.com]

4.2.2. Reporting Format and Mechanism

• Payment status communications must follow the UBL format (per Annex II of the draft Ministerial Order). [marosavat.com]
• Communications are made either via a web form (identifying the invoice by its unique code) or via web services, and each admitted communication receives an acknowledgement of receipt with a Secure Verification Code (CSV). [marosavat.com]

4.2.3. Digital Signature and Integrity

• All invoices exchanged via private platforms must carry an advanced electronic signature. [rtcsuite.com]
• Authenticity and integrity must be ensured through compliant technical mechanisms, which may include electronic signatures where appropriate. [vertexinc.com]
• Under Veri*factu, each invoice record must be secured with a chained hash system (huella) that prevents changes after issuance, and must include a QR code for verification. [blog.w-v.co.uk]

4.3. SII Reporting Requirements

• For businesses subject to SII (large taxpayers), invoice data must be submitted in structured XML format within four calendar days of issuance or receipt. [avalara.com]
• SII covers multiple VAT ledgers: issued invoices, received invoices, investment assets, and intra-EU transactions. [avalara.com]
• SII does not dictate invoice format; a business under SII may still use various formats and report the data separately. [rtcsuite.com]

5. Correction of Errors in E-Invoices and E-Reporting

5.1. E-Invoice Corrections

• If an invoice is incorrect, rejected, or does not correspond to the documented operation, the issuer may issue a credit note (to reduce or cancel the amount) or a debit note (to increase it). [rtcsuite.com]
• Both corrective documents must:
  • Reference the original invoice (by its unique identification code).
  • Be formatted in an accepted syntax (UBL, CII, EDIFACT, or Facturae for private platforms; UBL for the public solution).
  • Be digitally signed.
  • Follow the standard submission process through the platform or public solution. [rtcsuite.com]
• If a faithful copy of the original has already been submitted to the public solution, it may be cancelled through a “baja” (annulment) message with full traceability preserved. [rtcsuite.com]
• Under Veri*factu, once an invoice is issued, it cannot be altered or deleted. Corrections require a formal rectification invoice. [lextax.es]

5.2. E-Reporting Corrections (Invoice Status)

• Recipients who have reported incorrect status information (e.g., wrong acceptance or payment date) can submit updated status communications via the web form or web services on the SPFE. [marosavat.com]
• Issuers may report discrepancies with dates reported by the recipient through the SPFE. [marosavat.com]
• Under SII, late or corrected submissions carry automatic surcharges of 0.5%–1.5% of the invoice value, plus interest. [invostaq.com]
• Specific timelines for formal corrections under the B2B mandate will be confirmed in the final Ministerial Order (still pending publication as of June 2026). [vertexinc.com]

6. Transmission & Workflow

6.1. System Architecture

Spain uses a hybrid five-corner model combining private platforms with a government-operated public solution. The invoice lifecycle works as follows: [kpmg.com], [rtcsuite.com]

6.2. Transmission Routes

• Route A — Private Platform: The issuer’s platform routes the invoice to the recipient’s platform. If the two platforms are not yet directly interconnected, the public solution acts as the intermediary routing channel. At the moment of issuance, the issuer’s platform must simultaneously send a faithful electronic copy (copia fiel) of the invoice — in UBL syntax — to the public solution. [rtcsuite.com]
• Route B — Public Solution (SPFE): The issuer creates the invoice directly through AEAT’s web form (individual issuance) or web services (automated submission). The invoice is validated, assigned a Secure Verification Code (CSV), and made available to the recipient. No faithful copy is needed. [rtcsuite.com]
• A combination of both routes is permitted. Businesses that have not designated a private platform are presumed to use the public solution by default. [rtcsuite.com]

6.3. Authentication

• Access to the SPFE for submission requires authentication via electronic certificate. Where access is via the web form, the Cl@ve system may also be used. [marosavat.com]
• Businesses may access the SPFE directly or through an authorised representative or social collaborator (colaborador social). [marosavat.com]

6.4. Deadlines

• Invoice status reporting: Within 4 calendar days (excluding Saturdays, Sundays, and national holidays) of acceptance/rejection and payment. [rtcsuite.com]
• SII reporting: Within 4 calendar days of issuance or receipt for businesses under SII. [avalara.com]
• Faithful copy submission: Simultaneous with issuance when using private platforms. [rtcsuite.com]

6.5. Private Platform Requirements

Private electronic invoice exchange platform operators must satisfy Article 13 of Royal Decree 238/2026:

• ISO/IEC 27001 certification (or equivalent) for information security. [rtcsuite.com]
• AS2 or AS4 secure transmission protocols. [rtcsuite.com]
• eIDAS-compliant advanced electronic signature and seal capability. [rtcsuite.com]
• Ability to exchange and transform invoices across all four syntaxes while preserving authenticity and integrity. [rtcsuite.com]
• Business continuity plans proportionate to transaction volume. [rtcsuite.com]
• Free interconnection with all other platforms — operators must accept requests within one month, provide technical specs and a test environment, and may not charge fees. Interconnection may be established through direct links or network-based approaches such as Peppol. [rtcsuite.com]

6.6. Data Availability

• AEAT makes invoice and payment data available to the Ministry of Economy and the State Observatory of Private Late Payments for enforcement and public disclosure. [rtcsuite.com]
• Issuers and recipients may consult their own invoice and payment data through the public solution at any time. [rtcsuite.com]

7. Self-Billing

7.1. Permissibility

• Self-billing (autofactura) is permitted under Spanish law. A self-billing invoice is a document issued by the customer (or a third party) on behalf of the selling company to document a transaction. [stripe.com]

7.2. E-Invoicing Platform Requirements

• The scope of the B2B e-invoicing obligation extends to cases where the invoice is issued by the recipient of the transaction or by third parties, in accordance with Article 5 of the Invoicing Regulations (RD 1619/2012). Self-billing invoices must therefore use the e-invoicing platform. [cuatrecasas.com]

7.3. Prior Agreement and Approval

• Self-billing invoices can be used only if there is a prior agreement between the two parties. The selling party must expressly authorize the customer or third party to issue invoices, and this agreement must be formalized before sales take place. [stripe.com]
• The selling company must explicitly accept each self-billing invoice received. [stripe.com]

7.4. Mandatory Content Rules

• Self-billing invoices require a separate, dedicated numbering series for each recipient or third party that issues them. [stripe.com]
• If issued by the recipient (not a third party), the invoice must contain the legal statement“invoiced by the recipient” (facturación por el destinatario). [stripe.com]
• The issuer must provide a copy of the self-billing invoice to the selling party. [stripe.com]
• Although the invoice is physically issued by the buyer, the selling company remains responsible for ensuring the document complies with all legal and tax obligations. [stripe.com]

7.5. Veri*factu Implications

• When Veri*factu comes into force (January/July 2027), customers that issue self-billing invoices must generate them using software compliant with Veri*factu, unless they opt into the SII system. An earlier binding consultation (February 2025) that required self-billing invoices to be issued through Veri*factu even for SII companies was annulled by Royal Decree 254/2025. [stripe.com]

8. Triangulation & Special Scenarios

8.1. Triangulation Transactions

• The Crea y Crece B2B e-invoicing mandate covers only domestic transactions where both issuer and recipient are established in Spain. Cross-border legs of triangular transactions — including the intra-EU supply and acquisition — are out of scope for the Crea y Crece mandate. [vertexinc.com], [taxnews.ey.com]
• However, the SII reporting obligation still applies for businesses subject to SII. The SII system includes a specific ledger for intra-EU transactions, and triangulation-related data must be reported accordingly within four calendar days. [avalara.com]
• Standard EU VAT triangulation simplification rules (Article 141 of the VAT Directive) apply in Spain, allowing the intermediary to avoid VAT registration in the Member State of arrival under specific conditions. [marosavat.com]

8.2. Chain Transactions

• Where a chain transaction involves a domestic B2B leg between two Spanish-established entities, that leg falls within the Crea y Crece scope. Cross-border legs are excluded. [vertexinc.com]

8.3. Cross-Border Reverse Charge

• Reverse charge scenarios where the supplier is non-established and the recipient is established in Spain: the invoice from the non-established supplier is not within scope of the Crea y Crece mandate (as the issuer is not established in Spain). The Spanish recipient’s self-assessment under reverse charge is handled via standard VAT return procedures and, if applicable, SII reporting. [globalvatc…liance.com]

8.4. Zero-Rated and Exempt Supplies

• No specific exclusion for zero-rated or exempt supplies has been published. Where such transactions are documented by full invoices between Spanish-established entities, they fall within scope. Simplified invoices for exempt supplies that do not require full invoicing may be excluded. [rtcsuite.com]

8.5. Territorial Nuances

• The system applies across all Autonomous Communities, including Ceuta, Melilla, and the Canary Islands. The Basque Country and Navarre operate their own systems (TicketBAI and specific regulations). [globalvatc…liance.com]

9. Archiving & Retention

9.1. Retention Periods

• Tax purposes: Business owners and professionals must preserve invoices and supporting documents for the 4-year limitation period (Article 29.2(e) of Law 58/2003, General Tax Law, and Article 165.One of Law 37/1992). [sede.agenc…ria.gob.es]
• Commercial purposes: 6 years from the end of the fiscal year under the Commercial Code. [e-invoice.app], [rtcsuite.com]
• VAT deduction regularisation: When invoices relate to acquisitions for which VAT deduction is subject to a regularisation period, they must be kept during the corresponding regularisation period plus the following four years. [sede.agenc…ria.gob.es]
• Gold investment transactions: Copies of invoices must be kept for 5 years. [sede.agenc…ria.gob.es]

9.2. Archiving Formats

• Electronic invoices must be stored ensuring integrity, authenticity, legibility, and accessibility. [rtcsuite.com], [sede.agenc…ria.gob.es]
• Invoices must be stored in their original electronic format in accordance with Spanish tax law. [vertexinc.com]
• Storage through the public solution, certified private platforms, or internal systems is permitted. [rtcsuite.com]

9.3. Storage Location

• Storage by electronic means in a third country with which there is no legal instrument agreeing mutual assistance requires prior notification to the Tax Agency (AEAT). [sede.agenc…ria.gob.es]
• Storage within the EU is generally permitted without additional notification requirements. [sede.agenc…ria.gob.es]

9.4. Audit Accessibility

• Documents must be stored in a manner enabling immediate access by the Tax Agency, except for duly justified reasons. [sede.agenc…ria.gob.es]

10. Penalties & Enforcement

10.1. Crea y Crece Penalties

• Up to €10,000 per infraction for failure to issue or accept structured B2B e-invoices under Law 18/2022 (Crea y Crece). [e-invoice.app]

10.2. Veri*factu / Certified Software Penalties

• Up to €50,000 per fiscal year for businesses using invoicing software that does not meet mandatory e-invoicing requirements (Royal Decree 1007/2023, Article 201 of the Ley General Tributaria). [invostaq.com], [e-invoice.app]
• Up to €150,000 per year per product for software vendors selling invoicing systems that do not comply with mandatory standards. [e-invoice.app], [realtivo.com]
• Per-invoice fines of up to €10,000 for invoices generated without proper Veri*factu compliance (missing hashes, broken chain, absent QR codes) under Article 201 of the LGT. [invostaq.com]

10.3. Electronic Trust Service Violations

• Up to €10,000 under Article 19 of Law 6/2020 for electronic trust service violations affecting invoice authenticity or integrity. [rtcsuite.com]

10.4. Late Reporting and Platform Non-Compliance

• Late SII submissions carry surcharges of 0.5%–1.5% of the invoice value, plus interest. [invostaq.com]
• Additional administrative sanctions for failure to submit faithful copies, meet status reporting deadlines, or comply with platform interconnection obligations. [rtcsuite.com]
• Failure to report invoice records to AEAT within the required 4-business-day window triggers automatic surcharges. [invostaq.com]

10.5. General Tax Penalties

• Invoice errors: Fines of 1–2% of the transaction value; up to 75% for fraud. [globalvatc…liance.com]
• VAT deduction denial: Non-compliant invoices risk rejection of VAT deductions. [invostaq.com]

Note: Enforcement and penalty provisions for the B2B e-invoicing mandate specifically will be confirmed in the final Ministerial Order, still pending publication. [vertexinc.com]

11. Pre-Filled VAT Returns

11.1. Current Status

• Spain has introduced pre-filled returns for Modelo 303 (the periodic VAT Return), known as PRE303. This service has been available since 2020. [sovos.com], [sede.agenc…ria.gob.es]
• The PRE303 assistance service is available to all taxpayers according to their activity profile. [sede.agenc…ria.gob.es]

11.2. Data Sources

• Data for the pre-filled returns is taken from Spain’s SII (Suministro Inmediato de Información) system, to which invoices must be submitted within four days of issue or receipt. [sovos.com]
• As in Italy, the pre-filled returns are presented as drafts that facilitate filing; substantive figures can be amended by taxpayers. [sovos.com]

11.3. Dependence on E-Invoicing Data

• SII users benefit from pre-filled data because AEAT already has their transaction-level information. SII users are also exempt from filing several additional forms, including the annual customer/supplier listing (Form 347) and the annual VAT summary (Form 390). [blog.w-v.co.uk]
• As the Crea y Crece mandate rolls out and AEAT receives structured e-invoice data from all businesses (via the public solution and faithful copies), the scope and accuracy of pre-filled VAT returns is expected to expand significantly, though no official announcement has been made on timing. [blog.w-v.co.uk]

11.4. Fields Pre-Filled vs. Taxpayer Input

• The pre-filled Modelo 303 includes transaction data from issued and received invoices reported through SII. Taxpayers must verify and can amend all figures before submission. Fields requiring taxpayer input include adjustments, pro-rata calculations, regularisations, and any transactions not captured by SII. [sovos.com], [sede.agenc…ria.gob.es]

12. Impact on SMEs and Startups

12.1. Scope of Impact

• SMEs represent approximately 99% of Spain’s productive sector. The mandate is designed to drive broad adoption of structured invoicing, reduce manual processing costs, and improve data quality for both businesses and tax authorities. [rtcsuite.com]
• The primary policy driver is combating late payments: Spain’s average B2B payment period is approximately 80 days, well above the 60-day legal maximum, with only around 20% of large companies paying on time. [kpmg.com], [rtcsuite.com]

12.2. Phased Onboarding

• SMEs benefit from an additional 12-month grace period compared to large businesses: they must comply by 1 October 2028 (24 months after the Ministerial Order), while large businesses go live on 1 October 2027. [rtcsuite.com]
• Sole traders and entities under the income attribution regime with turnover ≤ €8 million have until 1 October 2029 for payment status reporting. [rtcsuite.com]

12.3. Free Public Platform

• AEAT will develop a free application or form available to all business owners and professionals, including those with low invoice volumes. This is specifically designed to minimize costs for SMEs and microenterprises that do not wish to invest in private platform subscriptions. [sede.agenc…ria.gob.es], [kpmg.com]

12.4. Transitional PDF Requirement

• During the first 12 months of mandatory compliance for large businesses, they will be required to accompany each e-invoice with a PDF document to ensure human readability for SME recipients not yet on the system. [rtcsuite.com]

12.5. Compliance Costs

• Platform access: The free public solution mitigates costs, but businesses using private platforms will bear subscription and integration fees. [rtcsuite.com]
• ERP adjustments: Businesses must ensure their systems can generate UBL EN 16931-compliant output, requiring potential ERP upgrades or middleware integration. [vertexinc.com]
• Certified software: Under Veri*factu, all invoicing software must be certified. Non-compliant software has been banned from sale since 29 July 2025. [rtcsuite.com]
• Digital certificates: Businesses need valid electronic certificates for authentication with the SPFE, adding a procedural requirement. [vertexinc.com]
• For foreign companies, obtaining a Spanish NIF and digital certificates can cost upwards of €2,000. [lawants.com]

12.6. Cash Flow and Administrative Effects

• Positive: Faster validation, earlier VAT error detection, reduced manual processing, projected annual savings for the Spanish economy exceeding €8 billion at full implementation, with the food retail, automotive, and travel agency sectors already demonstrating savings of approximately €2.7 billion. [peppol.nu]
• Positive: Real-time payment tracking is expected to significantly reduce late payments, directly benefiting SME cash flow. [kpmg.com]
• Burden: SMEs face the challenge of adapting legacy systems, training staff, and managing the transition from PDF/paper to structured electronic invoicing. [rtcsuite.com]

12.7. Government and EU Support

• Spain’s Kit Digital programme has previously provided subsidies for digitalisation of SMEs, though no specific subsidy has been announced for e-invoicing compliance under Crea y Crece as of June 2026. [peppol.nu]
• The free AEAT public platform is the government’s primary support mechanism for ensuring no SME is excluded from compliance due to cost. [sede.agenc…ria.gob.es]
• The EU’s ViDA (VAT in the Digital Age) framework assessment acknowledges the need for proportionate implementation for SMEs, and Spain’s phased approach is consistent with this principle. [vertexinc.com]

13. Official References

13.1. Government Portals and Tax Authority Publications

• AEAT — Mandatory Electronic Invoicing Announcement (31 March 2026): https://sede.agenciatributaria.gob.es/Sede/en_gb/todas-noticias/2026/marzo/31/facturacion-electronica-obligatoria.html [sede.agenc…ria.gob.es]
• AEAT — VAT: New Regulations 2026 (Royal Decree 238/2026): https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/novedades-iva/novedades-normativa-2026/real-decreto-238-2026-25-marzo.html [sede.agenc…ria.gob.es]
• AEAT — Veri*factu FAQ (Updated December 2025): https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/sistemas-informaticos-facturacion-verifactu/preguntas-frecuentes/sistemas-verifactu.html [sede.agenc…ria.gob.es]
• AEAT — VAT Portal (Modelo 303, PRE303, SII, Veri*factu): https://sede.agenciatributaria.gob.es/Sede/en_gb/iva.html [sede.agenc…ria.gob.es]
• AEAT — Duty to Preserve Invoices: https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/facturacion-registro/facturacion-iva/obligacion-conservar-facturas.html [sede.agenc…ria.gob.es]
• European Commission — eInvoicing in Spain (Country Fact Sheet): https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467108901/eInvoicing+in+Spain [ec.europa.eu]

13.2. Legislative Texts

• Royal Decree 238/2026 (BOE, 31 March 2026): Full text available via the BOE. [rtcsuite.com]
• Law 18/2022 (Ley Crea y Crece): Published September 2022. [rtcsuite.com]
• Royal Decree 1007/2023 (Veri*factu): Published December 2023. [marosavat.com]
• Royal Decree-Law 15/2025: Postponing Veri*factu deadlines. [marosavat.com]
• Law 25/2013: B2G e-invoicing mandate. [ec.europa.eu]

13.3. Big 4, Law Firm, and Advisor Publications

• EY — Spanish Government Approves Royal Decree (25 March 2026): https://taxnews.ey.com/news/2026-0726-spanish-government-approves-royal-decree-implementing-mandatory-b2b-electronic-invoicing [taxnews.ey.com]
• EY — Draft Regulation Updates (March 2025): https://www.ey.com/en_gl/technical/tax-alerts/spain-new-draft-regulation-updates-requirements-for-upcoming-mandatory-e-invoicing-for-b2b-transactions [ey.com]
• KPMG — Council of Ministers Approves E-Invoicing Mandate (March 2026): https://kpmg.com/us/en/taxnewsflash/news/2026/03/spain-e-invoicing-mandate-b2b.html [kpmg.com]
• KPMG Abogados — Tax Alert (April 2026): https://assets.kpmg.com/content/dam/kpmgsites/es/pdf/2026/04/tax-alert-approval-regulations-governing-b2b-electronic-invoicing.pdf [assets.kpmg.com]
• Cuatrecasas — Regulation Approved on Mandatory E-Invoicing (April 2026): https://www.cuatrecasas.com/en/spain/tax/art/regulation-mandatory-einvoicing-b2b-transactions [cuatrecasas.com]
• Vertex — Spain’s 2026 E-Invoicing Regulations Explained (27 May 2026): https://www.vertexinc.com/en-gb/resources/resources-library/spains-2026-e-invoicing-regulations-explained-scope-deadlines-and-penalties [vertexinc.com]
• Avalara — SII and VeriFactu in Spain (March 2026): https://www.avalara.com/blog/en/europe/2026/03/sii-verifactu-compliance-real-tme-invoicing.html [avalara.com]
• Marosa VAT — E-Invoicing in Spain: Complete Guide: https://marosavat.com/vat-news/spain-approves-b2b-electronic-invoicing [marosavat.com]
• Marosa VAT — Verifactu in Spain: Complete Guide: https://marosavat.com/vat-news/verifactu-spain-2026-guide [marosavat.com]
• RTC Suite — Royal Decree 238/2026 and Draft Ministerial Order (April 2026): https://rtcsuite.com/spains-mandatory-b2b-e-invoicing-takes-shape-royal-decree-238-2026-and-the-draft-ministerial-order/ [rtcsuite.com]
• Thomson Reuters — Spain E-Invoicing Compliance: https://europe.thomsonreuters.com/es/compliance/regulatory-updates/spain [europe.tho…euters.com]
• EDICOM — Mandatory Electronic Invoicing B2B in Spain (Updated May 2026): https://edicomgroup.com/blog/electronic-invoicing-will-be-mandatory-for-spanish-companies [edicomgroup.com]
• Stripe — Self-Billing Invoices in Spain (Updated May 2026): https://stripe.com/es/resources/more/self-billing-invoices-in-spain [stripe.com]
• Sovos — Pre-Filled VAT Returns: The Current Landscape: https://sovos.com/blog/vat/pre-filled-vat-returns-the-current-landscape/ [sovos.com]
• Global VAT Compliance — Spain Mandatory E-Invoicing: https://www.globalvatcompliance.com/globalvatnews/spain-mandatory-e-invoicing-2026/ [globalvatc…liance.com]

14. Summary

14.1. Scope

Spain’s e-invoicing framework applies to all domestic B2B transactions between businesses and professionals established in Spain. B2C transactions and cross-border transactions are currently excluded. B2G e-invoicing via FACe has been mandatory since 2015. The system is built on three complementary pillars: Crea y Crece (invoice exchange and status reporting), Veri*factu (certified invoicing software), and SII (near-real-time VAT reporting for large taxpayers).

14.2. Timeline

• 1 October 2027: Large businesses (turnover > €8M) — mandatory B2B e-invoicing.
• 1 October 2028: All other businesses and professionals.
• 1 October 2029: Payment status reporting for sole traders and small entities.
• Veri*factu: January 2027 (corporate taxpayers) / July 2027 (others).
• Critical dependency: All B2B deadlines are contingent on the Ministerial Order being formally published (expected entry into force: 1 October 2026).

14.3. Key Obligations

• Issue and receive invoices in structured electronic format (EN 16931 / UBL).
• Submit faithful copies to the AEAT public solution when using private platforms.
• Report invoice status (acceptance, rejection, payment) within 4 calendar days.
• Use certified invoicing software (Veri*factu) unless subject to SII.
• Archive invoices for 4 years (tax) / 6 years (commercial) ensuring integrity, authenticity, and readability.

14.4. Main Risks

• Penalties: Up to €10,000 per infraction (Crea y Crece), up to €50,000/year for non-compliant software, up to €150,000/year for software vendors.
• VAT deduction denial for non-compliant invoices.
• Operational disruption if ERP systems, private platforms, or software certification are not ready by go-live.
• Uncertainty: The Ministerial Order is still pending final publication; dates may shift.

14.5. SME Implications

• SMEs benefit from a 12-month additional grace period, a free public platform, and phased payment status reporting. However, they face significant adaptation costs in software certification, ERP adjustments, and digital certificate acquisition. The mandate is ultimately designed to benefit SMEs through faster payments, reduced late-payment exposure, and administrative simplification.

14.6. Critical Dates and Next Steps

• Now (June 2026): Monitor the formal publication of the Ministerial Order in the BOE.
• 1 October 2026 (expected): Ministerial Order enters into force; compliance countdown begins.
• By August 2027: AEAT public platform must be operational.
• 1 October 2027: First wave go-live for large businesses.
• Immediate actions for businesses: Assess system readiness across Crea y Crece, Veri*factu, and SII; engage with private platform providers or prepare for public solution use; ensure invoicing software is Veri*factu-certified; and establish internal processes for 4-day invoice status reporting.

---

• 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

---

 

---

---