Last update: March 25, 2026
SUMMARY
INDEPTH ANALYSIS
- Scope of the Mandate
Overview of E-Invoicing and E-Reporting Obligations
Spain is implementing a dual-layer digital invoicing framework that combines mandatory structured electronic invoicing with anti-fraud software requirements. On March 24, 2026, Spain’s Council of Ministers officially approved the Royal Decree that establishes the legal framework for business-to-business e-invoicing under the Crea y Crece Law (Law 18/2022).This milestone represents the culmination of legislative efforts that began in September 2022 when the foundational law was enacted.
The Spanish framework operates through two complementary systems. The Crea y Crece B2B E-Invoicing Mandate requires all domestic business-to-business transactions between Spanish-established entities to be conducted using structured electronic invoices.Simultaneously, the VeriFactu Anti-Fraud System mandates that billing software used by businesses must meet specific certification requirements to ensure invoice integrity, traceability, and protection against post-issuance alterations.
This approach differs from models adopted by other European countries by combining centralized oversight with decentralized execution. While Spain provides a free public platform for invoice creation and submission, it also permits private certified service providers to operate their own e-invoicing systems, provided they maintain interoperability and submit duplicate copies of invoices to the tax authority’s central repository.
Applicable Transactions
Domestic Business-to-Business (B2B) Transactions
The core of Spain’s e-invoicing mandate applies to all domestic transactions between businesses and self-employed professionals established in Spain. The obligation is triggered when both the supplier and customer are business owners or professionals operating within Spanish territory.The mandate explicitly does not apply if either party lacks their primary economic activity headquarters within Spain or does not have a permanent establishment in the country.
This means that virtually all commercial transactions between Spanish VAT-registered entities conducting business activities in Spain will fall under the mandatory e-invoicing requirements once the phased implementation is complete. The scope is intentionally broad to maximize tax transparency and reduce the VAT gap, which has been a persistent challenge for Spanish tax authorities.
Domestic Business-to-Consumer (B2C) Transactions
Consumer-facing transactions remain outside the scope of Spain’s mandatory e-invoicing framework. There is currently no B2C e-invoicing mandate, and businesses are not required to issue structured electronic invoices to individual consumers.However, businesses may voluntarily choose to issue electronic invoices to consumers if they wish to modernize their invoicing processes comprehensively. The absence of a B2C mandate reflects the practical challenges of requiring consumers to receive and process structured XML invoices, as well as privacy considerations surrounding consumer transaction data.
Domestic Business-to-Government (B2G) Transactions
Business-to-government e-invoicing has been mandatory in Spain since January 1, 2015, predating the current B2B initiative by over a decade.All public sector entities in Spain are required to receive and process structured electronic invoices that comply with the European standard EN 16931.The FACe platform serves as the single-entry point for submitting e-invoices to Spanish public administrations, and suppliers to government entities must use this system.
The B2G framework operates on the Facturae format with XAdES digital signatures, and it functions independently of the newer B2B mandate, though businesses may integrate their systems to handle both B2G and B2B invoicing through unified platforms.
Intra-EU Acquisitions and Supplies
Transactions involving the acquisition of goods or services from suppliers in other EU member states, as well as supplies to customers in other EU countries, are currently exempt from Spain’s domestic B2B e-invoicing mandate under the Crea y Crece framework.The regulations specifically exempt transactions where either the supplier or customer is a non-resident entity, meaning cross-border intra-EU commerce does not trigger the structured e-invoicing obligation at this time.
However, these transactions remain subject to Spain’s Immediate Supply of Information (SII) system for companies with annual turnover exceeding six million euros.Large taxpayers must continue to report intra-EU transactions in near real-time through the existing SII infrastructure, which operates separately from the new e-invoicing mandate. Looking forward, the European Union’s VAT in the Digital Age (ViDA) initiative will introduce harmonized digital reporting requirements for intra-EU transactions beginning in July 2030, which will affect how Spain handles cross-border e-reporting.
Imports and Exports
Import and export transactions are excluded from the B2B e-invoicing mandate, as they fall under the non-resident exemption.When Spanish businesses import goods from non-EU countries, the import VAT is assessed through customs procedures, and these transactions are documented through customs declarations rather than commercial invoices subject to e-invoicing requirements. Similarly, when Spanish businesses export goods outside the EU, those transactions remain outside the scope of the domestic e-invoicing framework, though proper export documentation must still be maintained to support zero-rating for VAT purposes.
Cross-Border B2B Transactions
Cross-border business-to-business transactions with entities established outside Spain are exempt from the Crea y Crece e-invoicing mandate.The obligation specifically targets domestic transactions between Spanish-established businesses, reflecting the tax authority’s primary interest in domestic VAT compliance and the practical challenges of imposing Spanish e-invoicing requirements on foreign entities. Foreign suppliers to Spanish customers and Spanish suppliers to foreign customers will continue to use traditional invoicing methods or adopt e-invoicing voluntarily based on commercial preferences, unless they fall under SII reporting requirements due to having a Spanish permanent establishment.
Inclusion of Specific Transaction Types
Self-Billing Arrangements
Self-billing, where the customer issues an invoice on behalf of the supplier, is permitted under Spanish VAT law and will continue to be allowed under the e-invoicing framework.However, self-billed invoices must utilize the e-invoicing platform (either the public system or a private certified agent) when both parties are subject to the B2B mandate.
The draft regulations indicate that recipients of self-billed invoices must inform issuers about the invoice status within four working days of issuance.This status notification requirement ensures that suppliers who have delegated invoicing responsibility to their customers remain informed about the documentation of their sales for VAT purposes. Self-billing arrangements must be based on prior agreement between the parties, and the supplier must not issue a separate invoice for the same transaction to avoid duplication.
Triangulation Transactions
Triangulation involves three parties in different EU member states where goods move directly from the first supplier to the final customer, bypassing the intermediary’s location. These transactions are recognized within the Spanish VAT framework and will be subject to enhanced reporting requirements under the EU’s ViDA initiative from July 2030.
Under current rules, triangulation transactions are largely exempt from the domestic B2B e-invoicing mandate because they inherently involve non-resident parties.However, any domestic leg of a triangulation that involves two Spanish-established entities would fall within the e-invoicing scope. The ViDA framework will introduce a ten-day reporting deadline for header-level data on triangulation transactions, requiring both suppliers and customers to report unless their member state provides specific exemptions.
Chain Transactions
Chain transactions, where multiple parties are involved in the sale of the same goods with only one physical movement, require careful documentation to determine where each supply occurs for VAT purposes. Under the e-invoicing framework, each domestic leg of a chain transaction that involves two Spanish-established parties will be subject to the B2B e-invoicing mandate.Cross-border legs of chain transactions remain exempt from domestic e-invoicing.
Proper documentation of the transport arrangements is critical in chain transactions because it determines which supply is deemed to involve the movement of goods and which supplies are treated as occurring at rest. All parties in the chain must maintain clear records of the transaction structure, and VeriFactu integrity requirements apply to ensure the authenticity of the chained invoicing.
Special VAT Regimes
Businesses operating under special VAT regimes face specific considerations under the e-invoicing framework. The margin scheme, which applies to second-hand goods, works of art, and antiques, allows VAT to be calculated on the dealer’s margin rather than the full selling price. Transactions under margin schemes are expected to follow standard e-invoicing requirements, with invoices clearly indicating that the margin scheme applies.
The Travel Operators Margin Scheme (TOMS) used by travel agencies allows them to account for VAT on their margin rather than the full value of travel services. Travel agencies subject to the e-invoicing mandate must issue structured electronic invoices that properly reflect the TOMS calculation methodology.
Simplified invoices issued under Article 4 of Royal Decree 1619/2012 are exempt from the e-invoicing obligation, except for qualified simplified invoices as defined in Article 7.2 of the regulation.This exemption recognizes that simplified invoices are typically used for low-value transactions or retail scenarios where full invoicing details may be impractical, and these transactions often fall outside the B2B scope.
- Taxable Persons in Scope
Established Entities in Spain
The Spanish B2B e-invoicing mandate applies comprehensively to all resident businesses with a fixed establishment conducting business-to-business transactions within Spanish territory.This includes corporate taxpayers subject to Corporate Income Tax, regardless of their legal form—whether they are public limited companies (sociedades anónimas), private limited companies (sociedades limitadas), partnerships, or other corporate structures.
Self-employed professionals and freelancers, known as autónomos in Spain, are equally subject to the mandate.This represents a significant compliance population, as Spain has over three million registered self-employed individuals, many of whom operate as sole proprietors providing professional services, consulting, or skilled trades. The inclusion of autónomos reflects the tax authority’s comprehensive approach to closing the VAT gap across all business segments.
All Spanish VAT-registered entities fall within scope regardless of their size, sector, or annual turnover.While the implementation timeline is phased based on revenue thresholds, there is no permanent exemption for small businesses once their compliance phase arrives. This universal application ensures that the e-invoicing system captures the vast majority of commercial transactions in the Spanish economy.
Non-Established Entities with VAT Registration
Non-resident businesses that have obtained Spanish VAT registration face a more nuanced situation. The initial phase of the mandate specifically targets domestic transactions where both parties have Spanish establishments.This means that a foreign company with Spanish VAT registration but without a permanent establishment in Spain would not be immediately subject to the e-invoicing obligation for supplies to Spanish customers.
However, future regulatory developments may expand the scope to include certain non-resident VAT-registered entities, particularly those with significant commercial presence in Spain.The tax authority retains flexibility to broaden the mandate as the system matures and interoperability with other European e-invoicing systems improves. Non-resident entities should monitor regulatory guidance closely to understand when and if their obligations change.
Foreign Entities Without Fixed Establishments
Foreign entities that lack a permanent establishment in Spain and are not registered for Spanish VAT are explicitly exempt from the B2B e-invoicing obligation.When a foreign supplier provides goods or services to a Spanish customer, that transaction falls outside the domestic e-invoicing mandate, even if the Spanish customer is subject to reverse charge VAT accounting.
This exemption reflects practical and jurisdictional considerations—Spain cannot effectively impose invoicing format requirements on entities with no legal nexus to Spanish territory, and attempting to do so would create international compliance friction. The exemption focuses the mandate on transactions where Spain has clear enforcement jurisdiction and where both parties benefit from a standardized domestic invoicing infrastructure.
Exemptions and Special Categories
VeriFactu Exemptions
The VeriFactu anti-fraud software system, which runs parallel to the e-invoicing mandate, provides specific exemptions that indirectly affect e-invoicing obligations.
Taxpayers already subject to the SII (Immediate Supply of Information) system are exempt from VeriFactu requirements.Since SII applies to businesses with annual turnover exceeding six million euros, these large taxpayers are already providing near real-time transaction data to the tax authority through an established reporting channel, making the additional VeriFactu requirements redundant.
Businesses that use manual invoicing methods without any billing software are exempt from VeriFactu.This exemption acknowledges that requiring software certification for entities that issue handwritten or typewritten invoices without computer assistance would be impractical and disproportionate. However, such businesses must still comply with the Crea y Crece e-invoicing mandate once it becomes mandatory for their revenue category, which will effectively require them to adopt electronic systems.
Taxpayers legally exempt from invoicing obligations under special VAT regimes or those issuing only simplified invoices benefit from VeriFactu exemptions.This category includes certain small retailers and service providers operating under simplified VAT schemes where full invoicing is not required by law.
Taxpayers in the Basque Country and Navarre who use regional systems such as TicketBAI are exempt from VeriFactu.These autonomous regions have separate tax authorities with their own invoice verification systems that serve similar anti-fraud purposes. The exemption prevents duplicative compliance burdens and respects the fiscal autonomy of these historic territories.
Sector-Specific Rules
While the regulations do not establish broad sector exemptions, certain industries may receive tailored guidance on implementation. The financial services sector, healthcare providers, educational institutions, and other specialized industries that operate under unique VAT treatment or regulatory oversight may receive specific instructions on how to apply e-invoicing requirements to their particular circumstances. Such guidance typically emerges through tax authority publications and industry consultations as implementation approaches.
Optional Participation Models
Voluntary early adoption of e-invoicing is encouraged, particularly for businesses that fall into the second implementation phase but wish to gain competitive advantages through early digitalization.Companies below the SII threshold may voluntarily opt into real-time reporting if they believe the administrative efficiencies outweigh the earlier compliance burden. Similarly, businesses may choose to adopt VeriFactu-compliant software ahead of their mandatory deadline to test systems and train staff in advance.
Early adopters benefit from extended preparation time to resolve technical issues, the ability to learn from initial implementation challenges faced by larger companies, and the competitive advantage of offering modern, efficient invoicing to their trading partners. The tax authority views voluntary early adoption favorably as it smooths the overall transition and demonstrates business commitment to tax compliance.
- Implementation Timeline
Legislative Development and Adoption
The path to Spain’s mandatory e-invoicing system began with the enactment of Law 18/2022, known as the Crea y Crece Law, on September 28, 2022.This foundational legislation established the legal authority for the government to require structured electronic invoicing for business-to-business transactions and set the framework for subsequent regulatory development.
Following the law’s passage, the Ministry of Economic Affairs and Digital Transformation prepared draft implementing regulations. The first draft Royal Decree was published for public consultation on June 20, 2023, with the consultation period ending on July 10, 2023.This initial consultation allowed businesses, trade associations, technology providers, and other stakeholders to provide feedback on the proposed technical and operational requirements.
After incorporating feedback and making technical refinements, the Ministry submitted the draft regulation to the European Commission on February 2, 2024, as required under EU procedures for national e-invoicing mandates.The European Commission review process ensures that national e-invoicing requirements do not create unjustified barriers to cross-border trade within the Single Market.
A second public consultation phase opened in March 2025, with an updated draft regulation available for review until April 7, 2025.This second consultation reflected significant changes, including the decision to adopt UBL (Universal Business Language) as the mandatory format for the public platform instead of the Spanish Facturae format, better aligning Spain with broader European e-invoicing standards.
The culmination of this legislative process occurred on March 24, 2026, when Spain’s Council of Ministers officially approved the Royal Decree establishing the legal framework for B2B e-invoicing.This approval represents the final step in converting the Crea y Crece Law’s intentions into binding operational regulations that businesses must follow.
VeriFactu Anti-Fraud System Timeline
The VeriFactu system, which requires certified billing software to ensure invoice integrity, has experienced multiple postponements reflecting the practical challenges of implementing complex technical requirements across Spain’s diverse business population.
The original timeline called for implementation beginning January 1, 2026, for corporate taxpayers, with self-employed professionals and other entities following on July 1, 2026.However, recognizing that businesses and software vendors needed additional time to develop, test, and deploy compliant systems, the government postponed the implementation twice.
Royal Decree-Law 15/2025, approved on December 2, 2025, established the current VeriFactu timeline.Under this revised schedule, businesses outside the SII regime (primarily large companies and professionals already subject to real-time reporting) must implement VeriFactu-compliant software by January 1, 2027.Other companies and self-employed individuals using invoicing software must comply by July 1, 2027.
These postponements reflect the government’s pragmatic response to feedback from businesses and software vendors about implementation challenges, particularly regarding the technical complexity of the chained hash system (huella) that prevents post-issuance invoice alterations and the certification requirements for billing software developers.
Crea y Crece B2B E-Invoicing Phased Rollout
The B2B e-invoicing mandate operates on a carefully structured phased implementation designed to allow larger, more resource-rich companies to implement first while giving smaller businesses additional time to prepare. The implementation clock begins not with the Royal Decree’s approval but with the publication of a subsequent Ministerial Order that will define the technical specifications and operational details of the public e-invoicing platform.
This Ministerial Order is expected to be published before July 1, 2026, setting in motion the countdown to mandatory compliance.The decision to separate the Royal Decree approval from the Ministerial Order publication allows the government to finalize technical specifications based on the most current standards and technology capabilities while providing legal certainty about the mandate’s existence and scope.
Phase One of implementation targets large businesses with annual turnover exceeding eight million euros.These companies must comply with the B2B e-invoicing mandate twelve months after the Ministerial Order is published. If the Ministerial Order appears in June 2026 as anticipated, Phase One compliance would be mandatory by approximately July 2027. This group includes Spain’s largest corporations, which generally have more sophisticated IT infrastructure, dedicated tax compliance teams, and financial resources to invest in e-invoicing technology.
Phase Two extends mandatory compliance to all other businesses and freelancers with annual turnover at or below eight million euros.These entities receive twenty-four months from the Ministerial Order’s publication to achieve compliance, placing their mandatory deadline at approximately July 2028. This extended timeline acknowledges that small and medium enterprises typically face greater resource constraints, have less complex IT systems, and require more time to select, implement, and test e-invoicing solutions.
Phase Three addresses invoice status notification obligations, which require recipients to communicate acceptance, rejection, and payment information back through the e-invoicing system.Companies with turnover below eight million euros receive an additional year for this specific obligation, with a thirty-six-month deadline from the Ministerial Order’s publication. This staged approach to recipient obligations recognizes that receiving and processing incoming e-invoices represents a separate implementation challenge from issuing outgoing invoices.
Grace Periods and Transitional Provisions
The regulations include important transitional provisions to manage the shift from traditional to electronic invoicing. During the first twelve months of the Royal Decree’s effectiveness, companies required to issue electronic invoices must accompany them with PDF copies to ensure readability for companies not yet obligated to receive structured e-invoices, unless recipients explicitly agree to receive only structured formats.
This grace period addresses a fundamental challenge in phased implementation: suppliers may be required to issue e-invoices before their customers are required to receive them. By mandating PDF copies during the transition, the regulations ensure that smaller businesses not yet obligated to implement e-invoicing systems can still view and process invoices they receive. This parallel format requirement prevents commercial disruption while maintaining the compliance obligations of the issuing party.
Relationship to SII and Existing Reporting
For businesses with annual turnover exceeding six million euros, the SII (Immediate Supply of Information) system already requires near real-time transaction reporting.These taxpayers must submit invoice data within four working days of issuance, covering all transactions including B2B, B2G, B2C, domestic, and intra-EU commerce.
The new e-invoicing mandate operates alongside SII rather than replacing it. SII taxpayers remain exempt from VeriFactu requirements but must comply with the Crea y Crece e-invoicing mandate for B2B transactions.In practical terms, these large businesses will need to integrate their e-invoicing systems with their existing SII reporting infrastructure to avoid duplicative data entry and ensure consistency between the invoice data they transmit through e-invoicing channels and the transaction data they report through SII.
The coexistence of these systems reflects Spain’s layered approach to tax digitalization, where different initiatives target different aspects of the compliance ecosystem. While this creates some complexity, it allows the tax authority to leverage existing investments in SII infrastructure while extending structured invoicing benefits across the entire business population.
- Technical & Functional Requirements
E-Invoice Format Specifications
Spain has adopted a flexible approach to structured electronic invoice formats, permitting four internationally recognized XML-based standards to ensure broad compatibility with existing business systems and European interoperability initiatives.
The Universal Business Language (UBL) format, specifically version 2.1 conforming to ISO/IEC 19845:2015 for invoices and credit notes, has emerged as the mandatory standard for data exchange and copies submitted to the public platform.This represents a significant shift from earlier plans that emphasized the Spanish Facturae format. The adoption of UBL aligns Spain with the broader European e-invoicing ecosystem, particularly the PEPPOL network that uses UBL as its primary message format. The second public consultation in April 2025 confirmed that Facturae syntax is being de-emphasized in favor of UBL for the public billing solution, demonstrating Spain’s commitment to European harmonization under the ViDA initiative.
The Cross Industry Invoice (CII) format based on UN/CEFACT XML Schema (SCRDM-CII) remains an accepted standard.This format is widely used in certain industry sectors, particularly manufacturing and logistics, where UN/CEFACT standards have strong historical adoption. Businesses currently using CII in their international trade can continue leveraging these investments for Spanish domestic e-invoicing.
EDIFACT invoice messages compliant with ISO 9735 standard are recognized as valid structured e-invoice formats.EDIFACT has been used in electronic data interchange for decades, particularly in retail, automotive, and healthcare supply chains. Businesses with established EDIFACT infrastructure can maintain continuity with their existing systems while meeting Spanish e-invoicing requirements.
Facturae, the Spanish national XML format originally developed for B2G e-invoicing, remains an accepted format for B2B transactions during the transition period.While its role is diminishing in favor of UBL for new implementations, businesses that have invested in Facturae systems for government invoicing can continue using this format for their commercial invoicing, and approved e-invoicing platforms must support transformation between Facturae and other formats.
Mandatory Data Fields
Electronic invoices submitted through the Spanish e-invoicing framework must contain comprehensive data elements that satisfy both VAT compliance requirements and the technical needs of automated processing systems. These requirements build upon the baseline invoicing obligations established in Royal Decree 1619/2012 while adding elements specific to digital transmission and verification.
Core identification elements include the invoice number and series, which must be unique and sequential within the supplier’s numbering system.The date of invoice issuance must be recorded, establishing when the tax point occurs for VAT purposes.Both the issuer and recipient must be identified by their tax identification numbers (NIF or VAT ID), full legal names, and complete addresses. These identification elements enable the tax authority to match invoices with specific taxpayers and verify that transactions are properly reported by both parties.
Transaction details must comprehensively describe the goods or services supplied, including quantities, unit prices excluding VAT, and the applicable VAT rate for each line item. The invoice must clearly show the taxable base (the amount before VAT), the VAT amount calculated at each applicable rate, and the total invoice amount including VAT. For mixed transactions involving multiple VAT rates, each rate must be separately identified with its corresponding base and VAT amount.
Payment information has been enhanced under the April 2025 draft regulations, which now require invoices to include payment terms with specific start and end dates for payment periods.Bank account details for payment must be included to enable payment tracking and reconciliation. These payment elements support the invoice status notification requirements, where recipients must communicate payment status and dates back through the system within four working days.
Digital integrity elements are critical to the Spanish e-invoicing system’s anti-fraud objectives. Every invoice must include a QR code that enables verification by customers and tax authorities.This QR code links to verification systems where the invoice’s authenticity and current status can be confirmed. Digital signature metadata must be preserved within the invoice structure, documenting the electronic signature applied to authenticate the document.
For invoices generated through VeriFactu-compliant software, additional technical fields are mandatory. These include software identification details that specify which billing system generated the invoice, enabling the tax authority to verify that approved software was used.The date and time of invoice issuance must be recorded with precision. Each invoice must contain a cryptographic hash of the previous invoice issued by that taxpayer, creating a tamper-evident chain that prevents retroactive alteration or deletion of historical invoices.Digital signature metadata specific to VeriFactu requirements must be embedded, and the invoice must display text such as “Invoice verifiable on the STA website” or “VERIFACTU” to inform recipients of verification capabilities.
E-Reporting Data Model and Structure
The e-reporting framework follows the EN 16931 European standard semantic model for structured e-invoicing, ensuring interoperability within the European Single Market.The UBL format adopted by Spain natively implements this standard, providing a consistent data model that trading partners across Europe can process without custom mapping for each country’s unique requirements.
The reporting structure captures all invoice header-level data including the parties involved, dates, payment terms, and document references. Line-item details for each good or service are preserved, including descriptions, quantities, prices, and applicable tax rates. VAT breakdown by rate is maintained, showing the taxable amount, VAT rate, VAT amount, and total for each rate applied. Payment information and bank details are included to support payment tracking. Status updates regarding acceptance, rejection, and payment are structured data elements that flow through the system, enabling the tax authority to track the full lifecycle of each transaction from issuance through payment.
E-Reporting Format Requirements
E-reporting to the Spanish tax authority (Agencia Estatal de Administración Tributaria – AEAT) must utilize the structured XML formats described above. For taxpayers using private e-invoicing service providers, duplicate copies of all invoices must be transmitted to the public platform in addition to direct exchange between trading partners.This dual reporting ensures that AEAT maintains a comprehensive repository of transaction data regardless of which private platforms businesses choose to use.
Validation Rules and Data Quality
The e-invoicing platforms, whether public or private, implement automated validation rules to ensure data quality and compliance. These validations check that all mandatory fields are populated, that numeric values are properly formatted and mathematically consistent (for example, that line item totals equal the sum of line details), that VAT calculations are correct, that tax identification numbers are valid and properly formatted, and that date fields contain reasonable values.
Invoices that fail validation are rejected at submission, requiring the issuer to correct errors before the invoice can be successfully transmitted. This real-time validation prevents many of the errors that traditionally occurred with paper invoicing, where mistakes might not be discovered until VAT return preparation or tax audits.
Digital Signature and Integrity Requirements
Spanish law requires that electronic invoices be authenticated through one of two mechanisms. The first option is an advanced electronic signature compliant with the eIDAS Regulation (EU Regulation 910/2014), which establishes standards for electronic identification and trust services across the European Union.Advanced electronic signatures provide strong assurance of the signer’s identity and detect any subsequent changes to the signed document.
The second authentication option is Electronic Data Interchange (EDI) with procedures guaranteeing authenticity and integrity.This alternative recognizes that many businesses, particularly in sectors with established EDI implementations, use message-level authentication mechanisms embedded in their EDI protocols rather than document-level digital signatures.
For the VeriFactu system, additional integrity mechanisms apply. Businesses using VeriFactu-compliant software must implement either real-time transmission to AEAT (VeriFactu mode) or digitally signed invoices with chained hashes (Non-VeriFactu mode).The chained hash system creates a cryptographic link between sequential invoices, where each invoice contains a hash of the previous invoice’s content.This chain makes it computationally infeasible to alter or delete historical invoices without detection, as any change would break the hash chain.
QR codes serve as customer-facing verification tools.When a business receives an invoice with a QR code, they can scan it with a smartphone to access a verification portal that confirms the invoice’s authenticity, displays its current status, and shows whether it has been altered since issuance.
Real-Time and Near-Real-Time Processing
The Spanish e-invoicing system operates on a near-real-time model that balances immediate data availability with practical business process constraints. For businesses subject to the SII (Immediate Supply of Information) system with turnover exceeding six million euros, transaction data must be submitted within four working days following invoice issuance.This quasi-real-time reporting provides the tax authority with current visibility into business transactions while allowing businesses a narrow window to complete internal processing and quality assurance.
Under the Crea y Crece e-invoicing framework, transmission to customers and tax authorities is expected to occur on a near-real-time basis, with exact deadlines to be specified in the forthcoming technical regulations.When using the public platform, the billing process is considered complete when the customer accesses the invoice through the system, ensuring that recipients are promptly notified of new invoices.
VeriFactu systems implementing real-time transmission to AEAT (VeriFactu mode) send invoice data immediately upon issuance, providing the tax authority with the most current possible view of business activities.This real-time transmission eliminates any reporting lag and enables the tax authority to detect anomalies or potential fraud more quickly.
Recipients of e-invoices must communicate invoice status within four working days of receipt.This status update includes commercial acceptance or rejection with the date of the decision, payment status and date when payment is made, information about partial payments, and notification if the invoice has been assigned to a third party for collection. This rapid status feedback loop ensures that all parties maintain current information about transaction status and enables the tax authority to track payment patterns and identify potential collection issues.
Private e-invoicing agents must ensure their platforms can handle these timing requirements, transforming invoice messages between formats in real-time, preserving authenticity and integrity during transmission, connecting to other platforms upon request to enable interoperability, and attaching unique digital signatures containing the issuer’s tax identification number, invoice number and series, and issuance date before forwarding to recipients.
- Correction of Errors in E-Invoices and E-Reporting
E-Invoice Error Correction Procedures
Spanish tax law recognizes that errors in invoicing are inevitable and provides structured mechanisms for correction while maintaining the integrity of the VAT system. Royal Decree 1619/2012, which governs general invoicing obligations, requires corrective invoices (facturas rectificativas) when the original invoice fails to meet mandatory requirements, contains incorrect amounts or details, or needs adjustment for post-issuance events such as returns, discounts, or cancellations.
When a business discovers an error in an issued invoice, the appropriate response depends on the nature of the error. Material errors affecting the taxable base, VAT amount, or other mandatory data require issuance of a corrective invoice. Similarly, commercial events such as returns of goods, cancellation of services, discounts or rebates granted after invoice issuance, concursal situations where a customer enters insolvency proceedings, and non-payment or bad debts all trigger the need for corrective invoicing.
Credit Notes and Corrective Invoice Content
Credit notes (notas de crédito) serve to reduce or cancel the effect of an original invoice and are a standard tool for invoice correction in the e-invoicing environment. A properly constructed corrective invoice must contain several key elements beyond the standard invoice requirements.
The corrective invoice must include a clear reference to the original invoice, specifying the original invoice number, series, and date so that all parties can identify which transaction is being corrected. The document must explicitly indicate that it is a corrective invoice, typically through a specific document type code or clear labeling. The reason for the correction must be stated, explaining whether the correction addresses a billing error, a commercial event such as a return, or another circumstance.
The corrective amounts must be clearly presented, showing the adjustment to the taxable base and the corresponding VAT adjustment. Depending on the nature of the correction, the corrective invoice may show the corrected values directly or may show the incremental change that needs to be applied to the original invoice. All standard mandatory invoice fields must be completed, including party identification, dates, and digital integrity elements.
The April 2025 draft regulations clarified that credit and debit notes must include updated payment details, with specific start and end dates for payment periods.This ensures that payment tracking remains accurate even when invoices are adjusted.
Resubmission Through E-Invoicing Platforms
Corrective e-invoices must be transmitted through the same channels as original invoices, maintaining consistency in the audit trail. The process for issuing a corrective invoice through the e-invoicing framework follows a defined sequence.
First, the business creates the corrective invoice in structured format, choosing from UBL, CII, EDIFACT, or Facturae as appropriate for their system. The corrective invoice must include the reference to the original invoice as described above. The corrective invoice is then submitted through the same platform used for the original—either the public AEAT application or the business’s chosen private certified agent.
If the business uses a private e-invoicing service provider, a duplicate of the corrective invoice must be sent to the public platform to maintain the tax authority’s comprehensive repository.The recipient must acknowledge the status of the corrective invoice within four working days, just as with original invoices.
For businesses using VeriFactu-compliant software, corrective invoices must maintain the chained hash integrity that links all invoices in sequence.The corrective invoice becomes part of the chronological chain, ensuring that the correction itself cannot be retroactively altered or deleted. QR codes must be generated for corrective invoices to enable verification.In Non-VeriFactu mode, where digital signatures are used instead of real-time transmission, the corrective invoice must be properly signed according to the technical requirements.
E-Reporting Correction Procedures
For businesses subject to the SII (Immediate Supply of Information) system with turnover exceeding six million euros, correcting reporting errors requires specific procedures tailored to the SII infrastructure. When a business discovers an error in invoice data previously submitted through SII, they must submit amended invoice records through the SII web service.
The timing of corrections affects the approach. If the error is discovered within the four-working-day reporting window, the correction should be submitted immediately to ensure accurate reporting.If the error is discovered after the reporting window has closed, the correction should be submitted as soon as the error is identified, accompanied by documentation explaining the nature and reason for the correction.
Formal Correction Requirements and Timelines
The treatment of corrections for VAT purposes depends on whether the correction affects output VAT (on sales) or input VAT (on purchases). For output VAT corrections, the supplier must issue a corrective invoice and send it to the customer through the e-invoicing system. The VAT adjustment is then reflected in the VAT return for the period when the correction is made, or in a subsequent VAT return if the correction is identified after a return has been filed.
For input VAT corrections, the customer must request a corrective invoice from the supplier and adjust the input VAT deduction accordingly. If a customer has claimed input VAT based on an incorrect invoice, the correction may require repayment of excess input VAT credits.
Spanish law does not impose a specific short-term deadline for issuing corrective invoices, but good practice and commercial relationships typically demand prompt correction upon error discovery. The broader framework for VAT corrections is governed by the four-year statute of limitations for VAT assessments, meaning that corrections relating to periods within the past four years remain relevant for tax purposes.
Specific Forms and Declarations for E-Reporting Corrections
For SII corrections, businesses use the SII web service to submit amended invoice records without requiring separate correction forms.The SII system accepts amended submissions that replace previously submitted data, and the system validates and processes the corrections automatically.
For standard VAT return corrections not involving SII, businesses may need to file supplementary or amended VAT returns depending on the magnitude and timing of the correction. Modelo 303, the quarterly VAT return used by most taxpayers, can be amended or supplemented if corrections are identified after the return is filed. Modelo 390, the annual VAT summary return, similarly allows for correction through amended filing.
Documentation and Audit Trail Requirements
Maintaining comprehensive documentation of corrections is essential for VAT compliance and audit defense. Businesses must retain both the original invoice and the corrective invoice for at least four years.The audit trail should clearly show the reason for the correction, linking the original and corrective invoices. For businesses using VeriFactu-compliant systems, the chained hash structure automatically creates an immutable audit trail showing the sequence of original and corrective invoices.
The integrity of correction records must be preserved through the same mechanisms that protect original invoices, ensuring that the correction history itself cannot be tampered with. Tax authorities expect businesses to be able to explain and document any corrections during audits, with clear evidence of the business reason for the correction and the timeliness of the corrective action.
- Transmission & Workflow
Hybrid Continuous Transaction Control Model
Spain has adopted a hybrid, decentralized Continuous Transaction Control (CTC) model that combines elements of centralized clearance with interoperable private sector platforms.This architecture reflects a balance between government oversight objectives and practical recognition that a purely centralized system might struggle to scale across Spain’s millions of businesses with diverse technological capabilities.
Public Electronic Invoicing Solution
The centerpiece of Spain’s public infrastructure is the Public Electronic Invoicing Solution operated by the State Tax Administration Agency (AEAT).This platform functions as an invoice repository overseen by the tax authority, providing a centralized location where invoice data can be stored and accessed by authorized parties.
For smaller taxpayers without sophisticated IT infrastructure, AEAT provides a free application for creating and submitting e-invoices.This publicly funded tool ensures that businesses can comply with the mandate regardless of their ability to invest in commercial software or service providers. The application requires basic authentication and identification to access, ensuring security while maintaining accessibility.
When using the public platform, the billing process is considered complete when the customer accesses the invoice through the system.This access-based completion model differs from traditional invoicing where issuance alone suffices. The model ensures that customers are actively notified and can retrieve their invoices, reducing disputes about whether invoices were properly delivered.
The public platform initially utilized Facturae syntax, Spain’s national format developed for B2G e-invoicing. However, the April 2025 regulatory updates confirmed a strategic shift toward UBL (Universal Business Language) as the mandatory standard for the public platform.This transition aligns Spain with broader European e-invoicing standards and facilitates interoperability with the PEPPOL network and other member states’ systems.
Interoperability Framework
A distinguishing feature of Spain’s e-invoicing architecture is its strong emphasis on interoperability between platforms, preventing lock-in and ensuring that businesses’ choice of service provider does not limit their trading partners’ options.
Private e-invoicing agents approved to operate in Spain must meet comprehensive interoperability requirements. These platforms must be capable of transforming invoice messages between all supported formats—UBL, CII, EDIFACT, and Facturae—ensuring that an invoice issued in one format can be received and processed by a system using a different format.The transformation process must guarantee preservation of authenticity and integrity, meaning that the semantic content and legal effect of the invoice remain unchanged despite the format conversion.
Private agents must connect to other agents’ platforms upon request, enabling direct platform-to-platform exchange.This connectivity requirement prevents the fragmentation that could occur if each platform operated as a closed ecosystem. Instead, the Spanish market is designed to function as a network of networks, where any sender can reach any recipient regardless of which platforms they respectively use.
To achieve government approval, private e-invoicing agents must meet criteria related to interoperability, digital security, and business continuity planning.These standards ensure that private platforms provide reliability comparable to the public solution and that businesses depending on private services are not exposed to unacceptable operational risks.
The expected architecture follows a four-corner model: sender to sender’s platform (public or private) to receiver’s platform (public or private) to receiver.This model is well-established in European e-invoicing, particularly through the PEPPOL network, and Spain’s adoption of UBL format strongly suggests that PEPPOL infrastructure will play a significant role in Spanish e-invoicing interoperability.
Certified Service Providers
Private e-invoicing agents serve as certified service providers operating alongside the public platform. These entities must meet technical standards established by AEAT to ensure they can reliably perform the invoice transmission and transformation functions required by the framework.
Before forwarding invoices to recipients, certified agents must attach unique digital signatures to the invoice data.These signatures must contain the issuer’s tax identification number, the invoice number and series, and the issuance date.This signature layer provides an additional verification mechanism and enables the tax authority to confirm that invoices have passed through approved platforms without alteration.
The approval process for private agents evaluates security measures, continuity planning, and technical capabilities.Service providers must demonstrate that they can maintain operations even during disruptions, that they protect invoice data against unauthorized access or alteration, and that they can scale to handle their clients’ transaction volumes reliably.
VeriFactu Software Providers
Separate from the e-invoicing platform providers are the software vendors that supply VeriFactu-compliant billing applications to businesses. These vendors must submit a Declaración Responsable (responsible declaration) confirming that their software meets all technical and legal requirements.
VeriFactu software must implement the chained hash system that creates tamper-evident invoice histories, generate QR codes for verification, maintain accurate timestamps, and either transmit data to AEAT in real-time (VeriFactu mode) or apply digital signatures to invoices (Non-VeriFactu mode).
Software providers face substantial penalties—up to one hundred fifty thousand euros per year per product—for offering non-compliant software.This enforcement mechanism incentivizes vendors to invest in proper compliance and testing before marketing their solutions.
PEPPOL and API Integration
While not explicitly mandated in current regulations, Spain’s adoption of UBL format and emphasis on interoperability strongly indicate that the PEPPOL (Pan-European Public Procurement Online) network infrastructure will play a significant role.PEPPOL is a well-established European framework for electronic document exchange, widely used for B2G e-invoicing across multiple member states and increasingly adopted for B2B transactions.
PEPPOL uses UBL as its native message format and provides a four-corner network architecture identical to Spain’s planned model. Access points certified by PEPPOL authorities can exchange documents across the network regardless of which specific access point each trading partner uses, providing exactly the interoperability that Spain’s regulations require.
API gateways enable the technical connections that make the system function. These programmatic interfaces allow businesses’ ERP systems to connect to e-invoicing platforms, enable platform-to-platform communication for interoperability, facilitate data transmission to AEAT’s repositories, and support transformation services that convert invoices between different format standards.
Reporting Deadlines and Transmission Timing
SII Real-Time Reporting
For businesses with annual turnover exceeding six million euros, the existing SII (Immediate Supply of Information) system establishes the reporting timeline.These taxpayers must submit invoice data within four working days from the invoice issuance date. This quasi-real-time requirement covers all transaction types including B2B, B2G, B2C, domestic sales, and intra-EU transactions.
The four-working-day window provides businesses with sufficient time to complete internal invoice approval processes, perform quality assurance on invoice data, and handle batch transmission to the SII system, while still giving the tax authority near-current visibility into transaction flows.
Crea y Crece E-Invoicing Transmission
The Crea y Crece e-invoicing mandate calls for near-real-time transmission to both customers and tax authorities.While exact deadlines will be specified in forthcoming technical regulations, the system design anticipates rapid transmission comparable to the SII four-working-day standard.
For invoices transmitted through the public platform, the system creates an expectation of immediate availability to recipients, with the billing process completing when the customer accesses the invoice.For invoices exchanged through private platforms, near-simultaneous transmission to recipients and duplicate submission to the public repository ensures comprehensive tax authority visibility.
VeriFactu Transmission
VeriFactu systems implementing real-time transmission to AEAT (VeriFactu mode) send invoice data immediately upon issuance.This represents the most aggressive timeline in the Spanish framework, with zero delay between invoice creation and tax authority notification. The real-time transmission model provides AEAT with the earliest possible fraud detection capability, though it also imposes the most stringent technical requirements on businesses’ systems.
For VeriFactu systems using the Non-VeriFactu mode with digital signatures instead of real-time transmission, there is no specific reporting deadline beyond the general requirement to maintain digitally signed invoices with chained hash integrity and make them available for audit.
Invoice Status Notification Deadlines
Recipients of e-invoices face their own reporting obligation, independent of the supplier’s issuance requirements. Within four working days of receipt, customers must communicate invoice status through the e-invoicing system.
This status communication includes commercial acceptance or rejection of the invoice with the date of the decision, payment status and the date when payment is made or expected, information about partial payments if applicable, and notification if the invoice has been assigned to a third party for financing or collection purposes.
The four-working-day recipient deadline creates a complete transaction loop, where both issuance and acceptance occur within narrow timeframes. This rapid feedback mechanism helps suppliers manage accounts receivable more effectively and gives the tax authority visibility into both sides of each transaction.
Standard VAT Return Cycles
For taxpayers not subject to SII, traditional VAT return cycles remain in effect alongside the e-invoicing requirements. Most businesses file quarterly VAT returns using Modelo 303, with returns due approximately twenty days after the end of each calendar quarter. The annual VAT summary return, Modelo 390, consolidates the year’s VAT activity and must be filed in January following the tax year.
The e-invoicing system will capture transaction data more frequently than these quarterly filings, creating an environment where the tax authority has detailed invoice-level information well before taxpayers submit their periodic VAT returns. This information asymmetry enables AEAT to pre-populate returns and identify discrepancies between filed returns and underlying invoice data, significantly enhancing compliance enforcement capabilities.
- Self-Billing
Permissibility Under Spanish E-Invoicing Framework
Self-billing, known as auto-facturación in Spanish, represents an invoicing arrangement where the customer issues an invoice on behalf of the supplier for goods or services received. Spanish VAT law permits self-billing arrangements, and this permission continues under the e-invoicing framework. The practice is particularly common in certain supply chains, such as agricultural procurement where processors issue invoices to farmers, construction subcontracting where main contractors may invoice on behalf of subcontractors, and scrap metal and waste management where buyers document their purchases by issuing invoices to suppliers.
The fundamental requirements for valid self-billing under Spanish law remain unchanged by the transition to electronic invoicing. Self-billing requires explicit prior agreement between the supplier and customer specifying the scope and conditions under which the customer will issue invoices on the supplier’s behalf. The supplier must not issue a separate invoice for the same transaction, as this would create duplicate documentation and potential VAT discrepancies. Both parties must maintain clear records of the self-billing arrangement, which must be available for inspection during tax audits.
Integration with E-Invoicing Platforms
When both parties to a self-billing arrangement are subject to the B2B e-invoicing mandate, the self-billed invoices must be transmitted through the e-invoicing platform rather than through traditional paper or unstructured electronic methods such as PDF by email.This requirement ensures that self-billed invoices receive the same level of validation, transparency, and tax authority visibility as supplier-issued invoices.
Self-billed invoices must be created in one of the approved structured formats: UBL, CII, EDIFACT, or Facturae.The customer’s system must be capable of generating compliant structured invoices with all mandatory data elements, including proper identification of the supplier whose sale is being documented.
When a customer creates a self-billed invoice, the document must be transmitted through the customer’s chosen e-invoicing platform, whether that is the public AEAT application or a private certified agent. The invoice is then made accessible to the supplier through the e-invoicing system, ensuring that the supplier receives notification and can access the invoice that documents their sale.
If the customer uses a private e-invoicing platform, a duplicate copy of the self-billed invoice must be transmitted to the public repository, maintaining consistency with the treatment of all other B2B invoices.This ensures that AEAT’s central invoice repository contains complete transaction data regardless of whether invoices are issued by suppliers or by customers through self-billing arrangements.
VeriFactu Compliance for Self-Billing
Customers who issue self-billed invoices and are subject to VeriFactu obligations must ensure their billing software meets VeriFactu compliance requirements.This means the software used to create self-billed invoices must implement the chained hash system that prevents retroactive alteration of invoice records, generate QR codes for verification, and either transmit data to AEAT in real-time or apply proper digital signatures depending on the VeriFactu mode selected.
The chained hash requirement creates an interesting challenge for self-billing because the customer’s invoice chain includes invoices issued on behalf of multiple different suppliers. The hash chain reflects the customer’s chronological issuance sequence rather than any particular supplier’s sales sequence. This structure works correctly as long as the customer maintains the integrity of their own invoice chain and the system clearly identifies which supplier each self-billed invoice represents.
Supplier Validation and Acceptance Requirements
A critical safeguard in the e-invoicing framework’s treatment of self-billing is the explicit requirement for supplier notification and the opportunity for supplier validation. Draft regulations indicate that suppliers must be notified immediately when a self-billed invoice is issued on their behalf.The e-invoicing platform provides access to the invoice, allowing the supplier to review the details of how their sale has been documented.
Suppliers have four working days from receipt of a self-billed invoice to communicate acceptance or rejection.This timeline mirrors the general invoice status notification requirement applicable to all e-invoices. If a supplier believes the self-billed invoice contains errors—such as incorrect quantities, prices, or VAT amounts—they must reject it within this four-day window and work with the customer to issue a corrected self-billed invoice.
If the supplier does not reject the self-billed invoice within four working days, the invoice is deemed accepted. This deemed acceptance rule provides certainty about invoice status while protecting suppliers through the notification and review period. The acceptance mechanism balances the operational efficiency of self-billing with the supplier’s fundamental responsibility for accurate documentation of their own sales for VAT purposes.
Mandatory Content Requirements
Self-billed invoices must contain all standard mandatory invoice fields plus additional elements that identify the invoice as self-billed and reference the underlying authorization. The invoice must clearly indicate that it is a self-billed invoice, typically through explicit labeling such as “Self-billed Invoice” or “Auto-factura” and through appropriate document type coding in the structured data.
The supplier’s full details must be presented as if the supplier had issued the invoice, including the supplier’s tax identification number, legal name, and address. The customer’s details must appear as the recipient, though internally the system recognizes that the customer also created the document. A reference to the prior agreement authorizing self-billing should be included, though the agreement itself need not be attached to each invoice.
The invoice number comes from the customer’s numbering series rather than the supplier’s series. This is appropriate since the customer is responsible for ensuring the uniqueness and sequence of the invoices they issue, even when those invoices document purchases rather than sales. All transaction details must be complete, including descriptions of goods or services, quantities, prices, applicable VAT rates, and amount calculations.
Digital integrity elements required for all e-invoices apply equally to self-billed invoices. The invoice must carry a digital signature, either an advanced electronic signature under eIDAS or EDI-based authentication mechanisms.A QR code must be generated to enable verification.For VeriFactu-compliant systems, the chained hash linking this invoice to the customer’s previous invoice must be embedded.
Payment term information must be included following the April 2025 regulatory clarifications, specifying the start and end dates for the payment period and bank account details for payment.This information supports payment tracking even though in self-billing scenarios the customer has documented their obligation to pay.
Restrictions on Self-Billing
Certain transactions are not eligible for self-billing under Spanish e-invoicing regulations. Cross-border transactions with non-resident suppliers lacking Spanish establishments cannot use self-billing within the Spanish e-invoicing mandate because the non-resident supplier is not subject to the framework.If a Spanish customer wishes to document their international purchases, they must rely on the supplier’s invoice or use alternative documentation appropriate for cross-border transactions.
Simplified invoices, which are exempt from the e-invoicing mandate, cannot be self-billed.Simplified invoices are typically used for retail transactions or low-value sales where full invoicing requirements are relaxed. The self-billing process is inconsistent with the simplified invoice concept, as self-billing implies a structured arrangement between identified business parties.
Certain regulated sectors may impose additional restrictions on self-billing based on industry-specific requirements. For example, professional services subject to oversight by professional colleges or highly regulated industries such as pharmaceuticals may have rules about invoice issuance that limit self-billing applicability.
Notification Obligations
Beyond the technical transmission of self-billed invoices through platforms, parties have specific notification obligations to ensure transparency. The supplier must be notified immediately upon issuance of a self-billed invoice, with notification facilitated through the supplier’s access to the e-invoicing platform. The supplier must have full access to view the invoice details through the platform’s user interface or API integration, enabling them to verify the accuracy of the documentation.
Status updates must be communicated within four working days, with the supplier indicating acceptance or rejection.If the supplier rejects the self-billed invoice, the parties must resolve the discrepancy and issue a corrected self-billed invoice, with the corrective invoice properly referencing the rejected original.
From a tax authority perspective, self-billed invoices transmitted through the e-invoicing platforms are automatically visible to AEAT, providing the same level of transparency as supplier-issued invoices. For taxpayers subject to SII, self-billed transactions must be reported within the four-working-day SII deadline.The self-billing arrangement does not alter reporting obligations; it simply changes which party creates the invoice document.
Documentation of the self-billing agreement itself must be maintained and made available during audits.The tax authority needs to verify that self-billing arrangements are genuine business arrangements rather than attempts to manipulate VAT reporting, so evidence of prior agreement and ongoing acceptance of self-billed invoices is essential for audit defense.
- Triangulation & Special Scenarios
Triangulation Transactions
Triangulation represents a specific type of intra-EU supply chain arrangement involving three parties located in three different EU member states, where goods move directly from the first supplier in country A to the final customer in country C, physically bypassing the intermediary located in country B. Under normal EU VAT rules, this would create two taxable supplies: supplier A to intermediary B and intermediary B to customer C, with the goods movement potentially triggering intra-EU acquisition and supply treatment in multiple countries.
The EU VAT Directive provides simplification for triangulation under Article 141, allowing the intermediary in country B to avoid VAT registration in the country of arrival (country C) provided certain conditions are met. The intermediary must not be established in country C, must acquire goods that are directly dispatched from country A to country C, and must supply those goods to a VAT-registered customer in country C who is notified that they will be liable for VAT under the reverse charge mechanism.
Under Spain’s current domestic B2B e-invoicing mandate, triangulation transactions are exempt because they inherently involve non-resident parties.If a Spanish business serves as the intermediary (party B) in a triangulation, the acquisition from the supplier in another EU country and the supply to the customer in a third EU country both fall outside the Spanish domestic e-invoicing requirement. Similarly, if a Spanish business is either the first supplier or the final customer in a triangulation involving intermediaries and other parties in different member states, the Spanish domestic e-invoicing mandate does not apply to that transaction.
However, the European Union’s VAT in the Digital Age (ViDA) initiative will transform the reporting requirements for triangulation transactions beginning in July 2030.Under ViDA’s Digital Reporting Requirements (DRR), member states must implement a harmonized system for reporting intra-EU transactions, including triangulation. The reporting deadline will be ten days after the end of the month in which the transaction occurs, with both suppliers and customers required to report header-level transaction data unless the member state provides specific exemptions.
Chain Transactions
Chain transactions involve multiple consecutive supplies of the same goods where the goods are only transported once. Determining which supply in the chain is associated with the goods movement is critical for VAT purposes because that supply typically qualifies as an intra-EU supply or export (potentially zero-rated), while other supplies in the chain are treated as domestic supplies in their respective jurisdictions.
Under Spanish e-invoicing regulations, each domestic leg of a chain transaction involving two Spanish-established parties is subject to the B2B e-invoicing mandate.If Spanish company A sells goods to Spanish company B, which then sells the same goods to Spanish company C, with only one physical movement of goods, each of the two invoices (A to B and B to C) must be issued as a structured e-invoice if both parties in each transaction are established in Spain.
Cross-border legs of chain transactions are exempt from the domestic e-invoicing requirement.If the chain involves a Spanish party and a non-resident party, that particular supply does not trigger the Spanish e-invoicing obligation, though proper documentation of the chain structure and goods movement remains essential for VAT compliance.
The correct VAT treatment of chain transactions depends critically on transport documentation. Parties must clearly document who arranged transport, where goods were located when each sale occurred, and the destination of the goods. Commercial documents such as bills of lading, consignment notes, and delivery confirmations play a vital role in establishing which supply involves goods movement.
VeriFactu integrity requirements apply to chain transaction invoicing, with the chained hash system maintaining the sequence and authenticity of invoices within each party’s invoice series.The chronological integrity of chain transaction documentation helps demonstrate to tax authorities that the reported sequence of supplies genuinely occurred.
Call-Off Stock and Consignment Stock
Call-off stock arrangements, where goods are moved to another member state and placed in a warehouse for the customer to draw down as needed, have historically created VAT complexities. The ViDA initiative introduces new treatment for call-off stock situations beginning in July 2028, with such arrangements potentially benefiting from simplified reporting through the One-Stop Shop (OSS) mechanism.
Consignment stock within Spain, where a supplier places goods at a customer’s location for the customer to take into use as needed, falls within the scope of domestic supply subject to e-invoicing requirements. Each time the customer takes goods into use, triggering a taxable supply, an e-invoice must be issued documenting that supply.
Cross-Border Reverse Charge Scenarios
The reverse charge mechanism shifts VAT accounting responsibility from the supplier to the customer and is commonly used for cross-border transactions within the EU and for specific domestic transactions such as construction services or scrap metal trading.
When a Spanish business acquires goods or services from an EU supplier in an intra-EU acquisition scenario, the transaction is currently not subject to the Spanish domestic B2B e-invoicing mandate.The EU supplier issues an invoice without Spanish VAT, and the Spanish customer self-assesses VAT through the reverse charge mechanism, reporting both output VAT (on the acquisition) and input VAT (as a deduction, if the goods or services are used for taxable purposes) on the same VAT return.
While such transactions are currently exempt from e-invoicing requirements, they remain subject to SII reporting for businesses with turnover exceeding six million euros.Looking forward, ViDA’s Digital Reporting Requirements will mandate ten-day reporting of intra-EU acquisitions beginning in July 2030.
The ViDA initiative also includes harmonization of reverse charge application beginning in July 2028.Member states must apply the reverse charge when a non-resident supplier supplies goods to a VAT-registered customer in the member state, though member states retain some flexibility regarding exact conditions. Invoices documenting reverse charge transactions must be issued within fifteen days of the end of the reporting period to which they relate.
Margin schemes and transactions involving works of art are explicitly excluded from the harmonized reverse charge rules.These specialized scenarios retain their specific VAT treatments under existing national and EU provisions.
Zero-Rated and Exempt Supplies
Zero-rated supplies, primarily exports and intra-EU supplies, are exempt from Spain’s domestic B2B e-invoicing mandate due to their cross-border nature.When a Spanish business exports goods outside the EU, proper customs documentation must be maintained to support the zero-rating, but the export invoice itself is not subject to structured e-invoicing requirements under the current domestic mandate.
Similarly, intra-EU supplies to customers in other member states are currently outside the domestic e-invoicing scope. These transactions require valid customer VAT numbers and evidence of transport to another member state to qualify for zero-rating. While not subject to Spanish domestic e-invoicing, such transactions must be reported through SII for large taxpayers and will become subject to ViDA Digital Reporting Requirements from July 2030.
VAT-exempt supplies within Spain, such as financial services, insurance, education, healthcare, and certain cultural activities, are subject to the B2B e-invoicing mandate when supplied between Spanish-established businesses.The fact that a supply is exempt from VAT does not exempt the invoice from e-invoicing requirements. The structured e-invoice must clearly indicate the exemption and cite the legal basis, typically referencing the specific article of the Spanish VAT Law or EU VAT Directive that provides the exemption.
Simplified invoice exemptions may apply to certain small-value exempt supplies, potentially removing them from e-invoicing requirements.However, most B2B exempt supplies involve identified business customers receiving full invoices, which must comply with e-invoicing requirements once the mandate is effective.
Special VAT Regimes in Practice
The margin scheme for second-hand goods, works of art, collectors’ items, and antiques allows dealers to calculate VAT on their margin (the difference between purchase and selling prices) rather than the full selling price. Dealers operating under margin schemes are subject to e-invoicing requirements when supplying to other businesses. The structured invoice must clearly indicate that the margin scheme applies, typically through specific codes or text disclosures.
The Travel Operators Margin Scheme (TOMS) used by travel agencies allows them to account for VAT on their margin rather than the full value of the travel package, which may include services supplied by multiple providers in different countries. Travel agencies subject to e-invoicing requirements must issue structured electronic invoices that properly document TOMS application. The invoice should clearly show that TOMS applies and identify which components of the travel package are included in the margin calculation.
Regional Systems: Basque Country and Navarre
The Basque Country (País Vasco) and Navarre (Navarra) enjoy special fiscal autonomy within Spain, with their own tax authorities and systems operating alongside the national AEAT.These regions have implemented TicketBAI, a regional invoice verification system that serves purposes similar to VeriFactu for businesses subject to Basque or Navarrese tax jurisdiction.
Taxpayers in these regions using TicketBAI are exempt from VeriFactu requirements,preventing duplicative compliance with similar invoice integrity systems. However, the application of the Crea y Crece B2B e-invoicing mandate to these regions may involve coordination between regional and national authorities. Businesses operating in or with counterparties in these regions should monitor both national and regional guidance to understand their specific obligations.
Platform Economy Considerations
The ViDA initiative includes significant provisions affecting platform-based businesses, particularly in ride-sharing and short-term accommodation sectors. Beginning with a voluntary phase in July 2028 and becoming mandatory in January 2030, platforms facilitating certain services will be deemed suppliers for VAT purposes, becoming directly liable for VAT on transactions they facilitate.
Member states can opt out for up to ten years if the underlying service provider has a VAT identification number or uses the special SME scheme.Given Spain’s strong commitment to digital tax compliance and its adoption of e-invoicing and VeriFactu systems, Spain may choose to implement the platform economy rules aggressively, potentially opting into the voluntary phase beginning in July 2028.
Platform operators will need to integrate their systems with e-invoicing infrastructure, issuing structured electronic invoices for transactions where they are deemed suppliers. This will require significant technical development for platforms that have historically functioned as intermediaries rather than principals in transactions.
- Archiving & Retention
Mandatory Archiving Formats
The Spanish e-invoicing framework imposes strict requirements on how electronic invoices must be archived to ensure long-term authenticity, integrity, and accessibility. Electronic invoices must be retained in their original structured format—UBL, CII, EDIFACT, or Facturae—rather than converted to unstructured formats such as PDF for archiving purposes.
This requirement reflects the fundamental principle that the structured XML data constitutes the legal invoice, not any human-readable representation derived from it. While businesses may generate and retain PDF views of invoices for convenient human review, the structured XML file with its embedded metadata, digital signatures, and hash chains represents the authentic invoice that must be preserved.
Digital signatures that were applied to authenticate the invoice must be preserved throughout the retention period.These signatures enable verification that the invoice has not been altered since issuance and that it was indeed issued by the identified party. Integrity mechanisms such as cryptographic hashes and timestamps must remain intact and verifiable.
QR codes embedded in invoices must remain functional and verifiable throughout the retention period.When an auditor or trading partner scans the QR code years after issuance, it should still link to verification systems that can confirm the invoice’s authenticity and display its status.
VeriFactu-Specific Archiving Requirements
VeriFactu imposes differentiated archiving requirements depending on which implementation mode a business has selected.
For businesses implementing VeriFactu mode with real-time transmission to AEAT, no local retention of invoice records is strictly required because AEAT maintains the submitted records in its own systems.The tax authority serves as the primary archive, with businesses able to retrieve historical invoice data from AEAT systems if needed. This approach reduces storage burdens for businesses while ensuring comprehensive tax authority access.
For businesses implementing Non-VeriFactu mode with digitally signed and chained invoices rather than real-time transmission, four-year local retention is mandatory.These businesses must maintain local storage systems that preserve the chained hash integrity linking sequential invoices and ensure that digital signatures remain verifiable. The storage must be tamper-proof, preventing retroactive alteration or deletion of archived invoices.
Audit trails and system logs related to invoice creation, transmission, and modification must be retained alongside the invoice records themselves.These logs provide evidence of system operation and help demonstrate to auditors that the business maintained proper controls over invoice data throughout the retention period.
The chained hash integrity that links invoices in sequence must be preserved in archived records.Each invoice contains a hash of the previous invoice, creating a cryptographic chain. If historical invoices are altered or deleted, the chain breaks, providing evidence of tampering. Archives must maintain the complete chain to enable verification of the entire invoice history.
Retention Periods for VAT Purposes
Spanish VAT law establishes a four-year minimum retention period for invoice records and related documents.This period begins at the end of the year in which the VAT obligation arose. For example, an invoice issued in March 2027 must be retained until at least December 31, 2031.
The four-year period aligns with the statute of limitations for VAT assessments, giving tax authorities the ability to audit and assess VAT for any period within the prior four years. Businesses must be prepared to produce invoices and supporting documentation for any transaction falling within this four-year window.
Certain circumstances may require longer retention periods. If a tax assessment or audit is ongoing, the relevant records must be retained until the assessment is resolved, even if this extends beyond four years. When disputes or litigation involve specific invoices, those records must be preserved until the matter is finally concluded. Criminal investigations into tax fraud or other offenses may require retention well beyond the standard four-year period.
Many tax advisors recommend retaining invoice records for six years as a conservative practice, providing a buffer beyond the minimum requirement. For records with potential commercial relevance beyond tax compliance, such as warranty documentation or long-term supply agreements, even longer retention may be prudent. The Spanish Commercial Code imposes certain recordkeeping requirements that may extend up to ten years for some commercial documents, though the VAT-specific invoice retention obligation is four years.
Storage Location Regulations
Spanish regulations permit some flexibility regarding where archived invoice records are physically stored, balancing practical business needs with tax authority access requirements.
For businesses implementing Non-VeriFactu mode, local storage is required, meaning the business must maintain archives within its own control.This storage may be on-premises servers, private cloud infrastructure, or third-party data centers contracted by the business. The critical requirement is that the business maintains the ability to access and produce the records on demand for audit purposes.
Storage within the European Union is generally permitted without special restrictions, provided AEAT can access records electronically. A Spanish business may store invoice archives on servers located in Ireland, Germany, or any other EU member state, as long as the business can produce the records in response to audit requests without undue delay.
Third-country storage, meaning servers located outside the EU, is more complex but not prohibited. If a business wishes to store invoice archives in data centers outside the European Union, several conditions must be satisfied. AEAT must be granted real-time electronic access without delays or restrictions. Data protection requirements under GDPR must be met, typically through standard contractual clauses or other approved transfer mechanisms for personal data. The third country’s legal framework must not prevent or restrict AEAT access to the data. Businesses must disclose the storage location to AEAT if requested and demonstrate that access rights are preserved.
Cloud storage provided by commercial providers has become increasingly common and is fully permissible under Spanish regulations, provided the provider guarantees specific capabilities. The provider must ensure integrity and authenticity of archived invoices through technical measures such as immutability controls and access logging. Continuous accessibility for audits must be maintained, with service level agreements addressing uptime and recovery time objectives. Data security measures including encryption, access controls, and intrusion prevention must meet current standards. GDPR compliance is essential for any provider handling European business data. Geographic transparency regarding server locations must be provided to AEAT if requested, enabling the tax authority to assess whether any jurisdictional issues exist.
Requirements for Integrity, Authenticity, and Readability
Archives must maintain three critical properties throughout the retention period: integrity, authenticity, and readability.
Integrity means that invoice records have not been altered since their original creation and issuance. This is ensured through advanced electronic signatures compliant with eIDAS that make any post-signature modification detectable,EDI authentication procedures that verify message integrity,or chained hash systems under VeriFactu that link invoices in a tamper-evident sequence.Digital signature metadata must be preserved, enabling verification that signatures are valid and that the signer’s certificate was valid at the time of signing.
Authenticity means that the invoice genuinely originates from the claimed issuer and that the parties, amounts, and transaction details are accurate representations of the commercial event. Authentication is established through the same mechanisms that ensure integrity—digital signatures, EDI procedures, or VeriFactu hash chains—combined with the unique invoice identifiers that tie each invoice to a specific taxpayer and transaction.
Readability requires that archived invoices can be accessed and understood by humans and processed by machines throughout the retention period. Human-readable formats such as PDF views or HTML renderings must be available so that auditors, business personnel, and trading partners can review invoice content without specialized technical tools.Machine-readable structured data in the original XML format must be maintained as the primary archive so that systems can parse, validate, and analyze invoice data programmatically. Data quality must not degrade over time, with no corruption, loss of metadata, or formatting errors affecting the archived records.
Traceability represents an additional requirement encompassing the ability to follow the complete history of each invoice from creation through any corrections to final payment and archiving.A complete audit trail must exist, documenting who created the invoice, when it was issued, to whom it was sent, what status updates occurred, and what access has been made to the archived record. Timestamps must be accurate and verifiable, providing reliable evidence of when events occurred. Version history for any amended or corrected invoices must be maintained, showing both the original and corrected versions along with the reasons for changes. Linkage between related invoices such as original invoices, corrective invoices, and credit notes must be preserved, enabling anyone reviewing the records to understand the complete transaction history.
Conservation obligations require protecting invoice archives from unauthorized alteration or deletion through technical controls such as immutable storage, access controls, and audit logging.Backup systems must exist to prevent data loss from hardware failures, disasters, or cyber incidents. Disaster recovery capabilities ensure business continuity and preservation of compliance records even in worst-case scenarios.
Accessibility requirements mean that archived invoices must be searchable, exportable, and promptly retrievable.Search capabilities should enable finding invoices by invoice number, date range, trading partner name or tax ID, and amount ranges. Export functions should allow extracting invoice data in standard formats for analysis or transfer to other systems. Timely retrieval means that when AEAT requests specific invoices during an audit, they can be produced within hours or days rather than weeks, with immediate electronic access being the preferred standard.
Audit Accessibility Rules
The Spanish tax authority (AEAT) possesses broad rights to access archived e-invoices during audits and compliance reviews. These rights extend to on-demand access to all archived e-invoices falling within the retention period, electronic format access to facilitate efficient audit procedures, structured data exports for bulk analysis where auditors need to examine large populations of transactions, and comprehensive audit trails documenting the history of each invoice and its treatment in the business’s systems.
Taxpayers face specific obligations when tax auditors exercise these access rights. They must provide immediate electronic access to archived invoices, typically through secure portals or system access for auditors. Filtering and searching capabilities must be enabled according to audit criteria such as date ranges, customer or supplier selections, or amount thresholds. Audit trail documentation including system logs, access records, and change histories must be supplied. Technical demonstrations of integrity and authenticity must be provided, showing auditors how digital signatures can be verified, how hash chains prove invoice sequences, and how QR codes link to verification systems. If the business uses complex or customized systems, technical assistance must be provided to help auditors navigate and understand the archived data.
Failure to provide timely access to archived invoices during audits is treated as non-compliance with archiving obligations and carries serious consequences. If a taxpayer cannot produce invoices when requested, AEAT may apply presumptive tax assessments, estimating the taxpayer’s liability based on indirect evidence or industry benchmarks rather than actual transaction data. This typically results in higher assessments than would occur if proper records were available. Penalties for non-compliance with recordkeeping obligations can be substantial, potentially ranging from six thousand to sixty thousand euros for serious infractions. In cases where missing records prevent verification of substantial transactions, tax authorities may suspect fraud, triggering more intensive investigation and potentially criminal referrals.
Best practices for maintaining audit-ready archives include maintaining dual storage with both primary and backup copies of all invoice archives, ideally in geographically separate locations. Format longevity planning addresses the reality that technology evolves—businesses should ensure their archives remain readable as software and standards change, potentially through periodic format migration or maintaining legacy systems capable of reading older formats. Archiving procedures and system architecture should be documented in writing, enabling both internal personnel and external auditors to understand how the business manages its invoice records. Regular testing of retrieval processes helps identify and correct problems before an actual audit, with periodic test retrievals simulating audit scenarios. A detailed index of archived invoices should be maintained, potentially in a searchable database, enabling rapid identification and retrieval of specific invoices based on various criteria.
- Penalties & Enforcement
Penalties for E-Invoicing Non-Compliance
Spain’s e-invoicing framework establishes a comprehensive penalty structure designed to incentivize compliance while providing proportionate consequences for different types and severities of violations.
Failure to Issue E-Invoices
The Crea y Crece framework specifically addresses failures to comply with the B2B e-invoicing mandate. Businesses that fail to issue or accept structured electronic invoices as required face penalties of up to ten thousand euros per infraction.This penalty applies once businesses fall within the scope of the mandate based on their turnover category and the applicable phase-in timeline.
The per-infraction structure means that systematic non-compliance across multiple transactions could result in cumulative penalties substantially exceeding ten thousand euros. A business that continues issuing paper invoices or unstructured PDF invoices after the mandatory compliance date, potentially affecting hundreds or thousands of transactions, faces exposure to significant aggregate penalties.
Repeated violations trigger escalating enforcement measures. Beyond monetary penalties, persistent non-compliance may result in enhanced audit scrutiny, with AEAT dedicating more resources to examining the non-compliant taxpayer’s complete VAT compliance picture. Systemic compliance monitoring may be imposed, requiring the business to provide more frequent reporting or submit to ongoing oversight until compliance is demonstrated and sustained.
General invoicing obligation violations under Spanish VAT law continue to apply alongside the specific e-invoicing penalties. These violations are categorized by severity with corresponding penalty ranges. Minor infractions, which include formal errors in invoices or incomplete data that does not materially affect VAT liability, carry penalties from one hundred fifty to six thousand euros. Serious infractions, including complete failure to issue invoices or systematic non-compliance with invoicing requirements, result in penalties from six thousand to sixty thousand euros. Very serious infractions involving fraud, intentional evasion, or use of false invoices carry penalties from sixty thousand to six hundred thousand euros, and may also trigger criminal prosecution.
Late or Incorrect E-Reporting
For businesses subject to the SII (Immediate Supply of Information) system with turnover exceeding six million euros, late reporting beyond the four-working-day deadline constitutes a compliance violation. The severity of penalties depends on the length of delay and whether the late reporting affects VAT assessments. Administrative delays without tax impact typically result in minor infraction penalties of one hundred fifty to six thousand euros. If late reporting causes VAT assessment complications or prevents timely tax collection, more serious infractions may be charged with correspondingly higher penalties.
Systematic failures to meet SII reporting deadlines may trigger enhanced audit status, where the taxpayer receives closer ongoing scrutiny and may be required to implement remedial measures to improve their compliance systems.
Incorrect data reporting is treated differently depending on whether the errors appear intentional or negligent. Unintentional errors that are corrected promptly upon discovery generally result in minor infraction treatment with lower penalties. The tax authority recognizes that complex systems and high transaction volumes inevitably produce some errors, and responsive correction demonstrates good faith compliance efforts.
Negligent errors, where the taxpayer failed to implement reasonable quality control measures or did not exercise appropriate care in data preparation, constitute serious infractions with penalties proportional to the potential tax impact. If incorrect reporting led to underpayment of VAT, the penalty calculation considers the amount of tax at risk.
Intentional misreporting crosses from administrative violation into potential tax fraud. Material misreporting that appears designed to evade VAT liability is treated as very serious infraction or criminal tax fraud depending on amounts involved and evidence of intent. Criminal prosecution becomes likely when misreporting exceeds certain monetary thresholds and evidence indicates deliberate fraud rather than mere negligence.
Non-Compliance with Platform Requirements
The VeriFactu system imposes substantial penalties specifically targeting software compliance. Businesses using non-compliant billing software face penalties of up to fifty thousand euros per year.This penalty applies when a business continues operating with software that does not meet VeriFactu certification requirements, lacks the required chained hash system, fails to generate proper QR codes, or does not implement required digital signature or real-time transmission capabilities.
The annual structure of this penalty means ongoing non-compliance accumulates substantial costs. A business that delays implementing compliant software for two years could face one hundred thousand euros in penalties beyond any other consequences of improper invoicing.
Software developers and vendors offering non-compliant systems face even more severe penalties of up to one hundred fifty thousand euros per year per product.This enforcement mechanism targets the supply side of compliance, creating strong incentives for software vendors to invest in proper development and testing before marketing their solutions. A vendor offering multiple non-compliant products faces multiplied penalties, with exposure potentially reaching hundreds of thousands or millions of euros if multiple products remain non-compliant over extended periods.
Platform technical violations beyond software non-compliance are generally treated as failure to issue proper e-invoices, subjecting businesses to the ten-thousand-euro per infraction penalty structure.Using non-approved structured formats, failing to include required digital signatures, or omitting mandatory data elements such as QR codes all constitute failure to issue compliant e-invoices under the framework.
Archiving Violations
Failure to maintain invoice records for the required four-year retention period constitutes a serious infraction under Spanish VAT law, with penalties ranging from six thousand to sixty thousand euros. The severity within this range depends on the scope of missing records, whether the failure prevented tax assessment or audit, and whether the business can demonstrate any mitigating circumstances such as disaster or system failure beyond their control.
Inability to produce invoices during an audit creates particularly serious consequences beyond direct penalties. When a taxpayer cannot provide requested invoices, AEAT may apply presumptive tax assessment methodologies, estimating the taxpayer’s VAT liability based on indirect evidence such as bank deposits, industry benchmarks for similar businesses, or statistical analysis of available partial records. Presumptive assessments typically result in higher tax liabilities than would be assessed based on actual records, as the methodology necessarily incorporates conservative assumptions favorable to the tax authority.
Loss of archived invoices, whether through inadequate backup systems, cyberattacks, hardware failures, or other causes, places the burden on the taxpayer to prove their transactions and VAT treatment despite missing records. This burden is difficult to meet, and the taxpayer may face both penalties for recordkeeping failures and increased tax assessments due to inability to substantiate deductions or exemptions.
Integrity violations involving tampered or altered invoices raise the specter of fraud investigation and criminal liability. If archived invoices show evidence of post-issuance alteration, tax authorities will investigate whether the alterations were designed to evade tax or conceal improper activity. Broken chained hash systems indicating that VeriFactu invoice histories have been tampered with trigger non-compliance penalties of up to fifty thousand euros and may also lead to fraud investigations if the tampering appears purposeful. Inaccessible or unreadable archives due to inadequate system maintenance, format obsolescence, or data corruption result in administrative penalties for non-cooperation and potential presumptive assessments if the inaccessibility prevents audit verification.
Distinguishing Intentional and Negligent Errors
Spanish tax law differentiates between negligent errors (culpa) and intentional violations (dolo), with significantly different penalty structures and consequences.
Negligent errors result from failure to exercise reasonable care or implement appropriate controls but lack evidence of intentional wrongdoing. Penalties for negligent errors with tax impact range from fifty percent to one hundred percent of the evaded tax amount. For formal violations without direct tax impact, administrative fines of one hundred fifty to sixty thousand euros apply depending on severity. Correcting errors proactively before receiving audit notification significantly reduces penalties, sometimes eliminating them entirely if the correction occurs promptly and the taxpayer can demonstrate good faith.
Intentional errors involve deliberate action to evade tax obligations or fraudulently manipulate reporting. Penalties for intentional violations range from one hundred percent to one hundred fifty percent of the evaded tax amount. Criminal prosecution becomes possible when VAT evasion exceeds one hundred twenty thousand euros under general fraud thresholds or six hundred thousand euros for aggravated fraud cases. Prison sentences may be imposed, with up to five years for general tax fraud or up to six years for aggravated fraud involving large amounts, organized schemes, or use of shell companies and fraudulent structures. Accessory penalties may include professional disqualification preventing the individual from serving as company director or in certain professional roles, and loss of eligibility for public subsidies or government contracts.
Aggravating factors that increase penalties include use of false invoices or fabricated transactions to support fraudulent deductions, systematic and organized fraud involving multiple parties or complex schemes, large amounts involved where materiality indicates serious harm to public revenue, and recidivism with previous violations demonstrating a pattern of non-compliance.
Mitigating factors that reduce penalties include voluntary correction before receiving audit notification, demonstrating proactive compliance efforts, cooperation with tax authorities during investigations and audits, first-time violations where the taxpayer has no history of compliance problems, minimal tax impact where errors had little effect on actual VAT liability, and genuine technical errors or misunderstandings of complex requirements, particularly during initial implementation phases of new systems.
Relevant Legal References
Primary legislation governing the Spanish e-invoicing framework and associated penalties includes Law 18/2022 (Crea y Crece Law) enacted September 28, 2022, establishing the legal foundation for B2B e-invoicing.Royal Decree 1007/2023 defines VeriFactu anti-fraud invoicing software requirements.Royal Decree-Law 15/2025 approved December 2, 2025 postpones VeriFactu implementation to 2027.Royal Decree 1619/2012 establishes general invoicing obligations and requirements.Law 58/2003 (General Tax Law) provides the overall tax penalty and enforcement framework. Royal Decree 2063/2004 implements detailed penalty regulations under the General Tax Law.
At the European level, Directive 2014/55/EU governs B2G e-invoicing.The EU VAT Directive 2006/112/EC establishes general VAT obligations including invoicing rules. The VAT in the Digital Age (ViDA) Directive adopted March 11, 2025 with effect from July 2030 will harmonize digital reporting requirements across the EU.
Official References for Penalty Information
Businesses can access comprehensive information about penalties and enforcement through several official channels. The Spanish Tax Agency (Agencia Estatal de Administración Tributaria – AEAT) main portal is located at https://sede.agenciatributaria.gob.es.The VAT section of the portal contains detailed guidance on invoicing requirements and penalties. The SII information section explains real-time reporting obligations and consequences of non-compliance.
Legislative texts are published in the Official State Gazette (Boletín Oficial del Estado – BOE) at https://www.boe.es. Law 18/2022 can be found at https://www.boe.es/buscar/act.php?id=BOE-A-2022-15586.Royal Decree 1007/2023 is published at https://www.boe.es/buscar/doc.php?id=BOE-A-2023-24065.
Recent analysis and guidance from professional service firms provides practical interpretation of penalty provisions. KPMG published detailed analysis of the VeriFactu postponement including penalty implications in December 2025 available at https://kpmg.com/us/en/taxnewsflash/news/2025/12/tnf-spain-verifactu-invoicing-system-delayed-to-2027.html.
- Pre-Filled VAT Returns
Current Status of Pre-Filled Returns
Pre-filled VAT returns do not currently exist in Spain in a comprehensive, automated form available to all taxpayers.The Spanish VAT system currently requires taxpayers to manually prepare and file their periodic VAT returns based on their own records, without automatic pre-population of return fields by the tax authority.
For businesses subject to the SII (Immediate Supply of Information) system with annual turnover exceeding six million euros, the situation differs somewhat. These taxpayers are exempted from filing quarterly VAT returns using Modelo 303, the annual VAT summary return Modelo 390, and certain other periodic VAT reporting obligations.Instead, their SII data submissions, which must occur within four working days of each invoice issuance, serve as continuous real-time reporting to AEAT.
From the tax authority’s perspective, SII taxpayers’ compliance is monitored through the ongoing stream of transaction-level data rather than through periodic summary returns. AEAT has complete visibility into these businesses’ transactions as they occur, enabling immediate detection of anomalies or compliance issues. While this continuous reporting does not constitute a pre-filled return in the traditional sense, it represents an alternative compliance model where transaction-level transparency replaces periodic self-assessment.
For the majority of Spanish businesses below the six million euro SII threshold, manual VAT return filing remains the standard. These businesses must file quarterly VAT returns using Modelo 303 and an annual VAT summary return using Modelo 390. The returns must be manually prepared based on the business’s accounting records, with no fields pre-populated by the tax authority based on data AEAT has independently collected.
Planned Development of Pre-Filled VAT Returns
The implementation of comprehensive B2B e-invoicing under the Crea y Crece mandate creates the foundation for future pre-filled VAT returns. Once the phased rollout is complete by approximately 2028-2029, AEAT will have access to comprehensive structured invoice data for virtually all business-to-business transactions in the Spanish economy.
All B2B invoices will be transmitted through the public platform or duplicated to the public platform by private service providers.This creates a comprehensive central repository of transaction data covering sales (output VAT) and purchases (input VAT) for all businesses subject to the mandate. Real-time or near-real-time transmission means AEAT receives invoice data continuously rather than only at quarterly reporting intervals.The complete audit trail of invoice statuses including acceptance, rejection, and payment information provides additional verification of transaction legitimacy.
With this comprehensive data foundation, AEAT will possess all the information necessary to calculate output VAT from issued invoices and input VAT from received invoices for most transactions. The logical evolution is to use this data to pre-populate VAT returns, transitioning from taxpayer self-assessment to tax authority pre-assessment with taxpayer verification and adjustment.
The expected timeline for introducing pre-filled VAT returns follows the completion of e-invoicing implementation. During 2027-2028 as e-invoicing becomes mandatory for different business categories, AEAT will focus on data collection, system stability, and ensuring that the quality and completeness of submitted invoice data meet standards necessary for reliable return pre-population. In the post-2028 period once all businesses are submitting e-invoices, AEAT is likely to begin pilot programs for pre-filled returns, potentially starting with volunteer taxpayers or specific business segments where data quality is highest.
Alignment with the EU’s VAT in the Digital Age (ViDA) initiative provides additional impetus for pre-filled returns. ViDA, which takes effect in July 2030, encourages member states to leverage digital reporting data for automated VAT compliance.Spain’s e-invoicing infrastructure positions the country well to implement this vision, potentially establishing Spain as a leader in automated VAT compliance within the EU.
International models provide precedents for Spain to follow. Italy’s Sistema di Interscambio (SdI) e-invoicing platform, operational since 2019, provides AEAT with a relevant case study. Italian authorities use SdI data to pre-populate portions of VAT returns and to identify discrepancies between filed returns and underlying invoice data. Poland’s KSeF e-invoicing system integrates transaction data with VAT compliance monitoring. France’s planned PPF (Plateforme de dématérialisation Partenaire) and PDP (Portail Public de Facturation) systems are expected to support automated VAT reporting and pre-filling.
Dependency on E-Invoicing and E-Reporting Data
The feasibility and accuracy of pre-filled VAT returns depend entirely on the quality and completeness of data flowing through e-invoicing and e-reporting channels. Multiple data sources will contribute to future pre-filled returns.
Crea y Crece e-invoice data covering all B2B transactions submitted through the public platform or duplicated by private agents will form the primary foundation.This data captures the vast majority of commercial transactions by value and provides structured, validated information about taxable amounts, VAT rates, and VAT amounts for both sales and purchases.
SII real-time reporting for large taxpayers already provides comprehensive transaction data for businesses exceeding six million euros in turnover.This data stream will continue operating alongside e-invoicing, with potential integration to ensure consistency and completeness.
VeriFactu invoice records, whether transmitted in real-time (VeriFactu mode) or maintained locally with verification capability (Non-VeriFactu mode), provide an additional verification layer ensuring invoice integrity.The chained hash system prevents retroactive alteration of invoice data, giving AEAT confidence that the information received accurately reflects the invoices actually issued.
The technical feasibility of automated VAT calculation is well-established. AEAT’s existing digital infrastructure including SII, VeriFactu, and e-invoicing platforms provides the technological foundation. Machine-readable structured data in UBL, CII, EDIFACT, or Facturae formats enables automated parsing and VAT calculation without human interpretation.Digital signatures and QR codes ensure data integrity, making the information reliable for official return pre-population.
Expected Pre-Filled Fields
Based on the data that will be available through e-invoicing and the approaches adopted by other countries with similar systems, certain VAT return fields are highly likely to be pre-filled while others will require taxpayer input.
Output VAT from sales represents the most straightforward category for pre-filling. AEAT will have complete records of all B2B invoices issued by the taxpayer, enabling automatic calculation of total taxable amounts by VAT rate (standard rate, reduced rate, super-reduced rate) and corresponding output VAT amounts. The structured invoice data includes all necessary information to perform these calculations accurately.
Input VAT from purchases can similarly be pre-filled based on B2B invoices the taxpayer received. AEAT will have records of all invoices issued to the taxpayer by their suppliers, enabling calculation of total potentially deductible input VAT by rate. However, input VAT pre-filling may be more complex than output VAT because not all input VAT is necessarily deductible—businesses must determine whether purchases relate to taxable activities, exempt activities, or mixed use, with deductibility varying accordingly.
Domestic B2B transactions will be fully captured through the e-invoicing mandate, providing complete data for both output and input VAT calculation. Intra-EU supplies and acquisitions are currently reported via SII for large taxpayers and will become subject to ViDA Digital Reporting Requirements from July 2030, enabling pre-filling of these fields for cross-border EU transactions once ViDA implementation is complete.
Fields Requiring Taxpayer Input
Certain transaction categories and adjustments will remain outside automated pre-filling, requiring taxpayers to provide information.
Business-to-consumer (B2C) transactions are not subject to the e-invoicing mandate, meaning AEAT will not have structured invoice data for sales to consumers. Businesses operating retail locations, restaurants, or other B2C models will need to manually report their consumer sales on their VAT returns. Some B2C transaction data may be captured indirectly through VeriFactu systems if businesses use certified billing software that records all sales, but this data may not be automatically integrated into VAT returns.
Cash and retail sales that do not generate full structured invoices will require manual reporting. While point-of-sale systems may generate transaction records, these may not flow automatically into VAT return pre-population systems, particularly during initial implementation phases.
Imports and customs transactions are documented through customs declarations rather than commercial e-invoices, so import VAT will not appear in e-invoicing data. Businesses must manually report import VAT based on customs documentation.
Various adjustments and special calculations require taxpayer input. Bad debt relief, where businesses write off uncollectible receivables and adjust previously paid output VAT, requires the taxpayer to identify qualifying bad debts and calculate the adjustment. Corrections to prior periods, whether correcting errors or making adjustments identified through invoice corrections, must be manually reported. Special regime calculations such as pro-rata adjustments for mixed-use businesses with both taxable and exempt activities require the taxpayer to calculate the deductible proportion of input VAT. Reverse charge self-assessments where the business is both customer and VAT accountant require manual reporting of the reverse charge amount.
Taxpayer Verification Responsibilities
Even with extensive pre-filling, taxpayers will retain ultimate responsibility for the accuracy and completeness of their VAT returns. The pre-filled return model shifts the burden of initial data compilation to the tax authority while maintaining taxpayer accountability for final accuracy.
Taxpayers will need to carefully review pre-filled data for accuracy, comparing pre-filled amounts against their own accounting records to identify any discrepancies. Discrepancies might arise from timing differences if invoice dates and accounting recognition dates differ, from missing invoices if some transactions were not properly transmitted through e-invoicing channels, or from classification errors if invoices were submitted with incorrect VAT rates or transaction types.
Correcting errors and omissions remains the taxpayer’s obligation. If pre-filled output VAT is incorrect, the taxpayer must adjust it to reflect actual liability. If some input VAT was not captured in pre-filled amounts, the taxpayer must add it with supporting documentation.
Adding transactions not captured by e-invoicing requires manual entry. B2C sales, import VAT, and other categories outside e-invoicing scope must be entered by the taxpayer to complete the return. Adjustments and special calculations must be computed and entered manually.
After making any necessary adjustments to pre-filled amounts and adding any required information, the taxpayer must sign and submit the final return, accepting legal responsibility for its accuracy. Even though much of the data originated from tax authority systems, the taxpayer’s submission constitutes their formal declaration of VAT liability and remains subject to all compliance obligations and penalties for inaccuracies.
- Impact on SMEs and Startups
Effects on Small and Medium Enterprises
The Spanish e-invoicing and e-reporting framework creates significant implications for small and medium enterprises and startups, representing both compliance challenges and potential operational opportunities. The government’s phased implementation approach reflects recognition that smaller businesses face distinct constraints compared to large corporations, though ultimately the mandate applies universally across business sizes.
Phased Implementation for Different Business Sizes
The turnover-based phasing reduces the immediate compliance burden on smaller businesses by providing extended preparation timelines. Large companies with annual turnover exceeding eight million euros face a twelve-month compliance period from publication of the Ministerial Order, with mandatory compliance estimated around July 2027.
SMEs and startups with annual turnover at or below eight million euros receive a twenty-four-month compliance period, placing their mandatory deadline around July 2028.This additional year of preparation time provides several strategic advantages. Smaller businesses can observe how large companies navigate implementation, learning from early adopters’ successes and challenges. They gain additional time to assess technology options as the market matures and more solutions become available. Budget cycles can be aligned, allowing SMEs to allocate funds over multiple fiscal years rather than making large immediate investments. Staff training can be conducted more gradually, reducing disruption to ongoing operations.
Invoice status notification obligations, requiring recipients to communicate acceptance and payment information back through the system, receive an additional year for SMEs, with a thirty-six-month deadline from the Ministerial Order.This recognizes that building receiving and processing capabilities for incoming e-invoices represents a separate implementation challenge from issuing outgoing invoices.
Absence of Revenue-Based Exemptions
Despite the phased timeline, no permanent revenue-based exemption exists from the e-invoicing mandate.Once their compliance phase arrives, all businesses conducting B2B transactions must implement e-invoicing regardless of how small they are. Micro-enterprises and newly established startups will face the same fundamental requirements as mid-sized companies, though they may access simpler implementation options such as the free public platform.
This universal application reflects policy decisions prioritizing comprehensive tax transparency and VAT gap reduction over accommodation of the smallest businesses. From the tax authority’s perspective, exempting small businesses would leave significant transaction volumes outside the system and create compliance arbitrage opportunities where businesses structure operations to remain below exemption thresholds.
VeriFactu Exemptions Benefiting Some SMEs
While the e-invoicing mandate applies universally, certain VeriFactu exemptions may reduce compliance burden for specific small business categories.
Businesses issuing manual handwritten invoices without any billing software are exempt from VeriFactu requirements.This exemption recognizes the impracticality of requiring software certification for entities that do not use software. However, such businesses must still comply with Crea y Crece e-invoicing once mandated, which will effectively require them to adopt electronic systems, making the manual invoicing exemption temporary for most.
Certain small retailers and service providers issuing only simplified invoices for low-value transactions may qualify for exemptions under specific provisions.However, businesses conducting B2B transactions typically issue full invoices rather than simplified invoices, limiting the practical benefit of this exemption for most SMEs.
Taxpayers with turnover below six million euros are exempt from SII real-time reporting requirements.This exemption provides meaningful relief, as SII imposes four-working-day reporting deadlines and continuous compliance monitoring. SMEs can continue filing quarterly VAT returns through the simpler Modelo 303 process, though they must still implement e-invoicing for B2B transactions.
Simplified Regimes and Support Programs
The regulatory framework does not establish a dedicated simplified SME e-invoicing regime with reduced technical requirements. All businesses must use the same structured formats—UBL, CII, EDIFACT, or Facturae—and meet identical technical specifications.This uniform approach ensures interoperability, as any business’s invoices can be received and processed by any other business’s system regardless of size differences.
The primary simplification offered to SMEs is the free public platform application provided by AEAT.Small businesses without resources to invest in commercial software or service providers can use this government-provided tool to create and submit compliant e-invoices at no cost. The public platform handles all technical requirements including structured format generation, digital signature application, and transmission to recipients, enabling even the smallest businesses to comply without specialized IT investments.
Simplified onboarding is expected through technical guidance, tutorials, and support programs that AEAT and industry associations will provide as implementation approaches. These educational resources aim to reduce the knowledge barriers that SMEs face when adopting new technologies.
Potential tolerances during initial implementation may include grace periods for minor technical issues, reduced penalties for good-faith errors during the first year of compliance, and enhanced technical support from AEAT to help businesses resolve implementation problems.
At the EU level, the VAT in the Digital Age initiative includes a special SME VAT registration scheme available from 2025.This scheme simplifies cross-border VAT compliance for small businesses operating in multiple member states, though it cannot be combined with other special schemes such as the Import One-Stop Shop (IOSS).Spanish SMEs conducting cross-border business may benefit from this EU-level simplification even as they comply with domestic e-invoicing requirements.
Government Support and Subsidies
Currently announced support from Spanish authorities includes the free public e-invoicing application eliminating subscription costs for using AEAT’s platform, technical documentation and guidance with implementation resources provided by AEAT, and industry outreach including workshops and training sessions for business communities organized by tax authorities and trade associations.
No direct financial subsidies have been announced for software purchases, system integration costs, consultant fees, or technology upgrades. This absence of direct financial support means SMEs must fund their compliance implementation from operating budgets without government grants specifically for e-invoicing adoption.
Potential indirect support may be available through regional development funds, as some autonomous communities offer digitalization grants that might apply to e-invoicing investments. EU Digital Europe Programme funding supports digital transformation projects, though accessing these funds typically requires navigating competitive application processes. Chamber of Commerce programs often provide training and advisory services for members at reduced costs or free.
SMEs are advised to monitor regional and local support programs that may emerge as implementation approaches, engage with trade associations for collective guidance and potential group purchasing arrangements, explore group purchasing options where multiple small businesses collectively contract with service providers for better pricing, and leverage free government tools to minimize costs wherever feasible.
Compliance Costs for SMEs
Implementation of e-invoicing creates various cost categories that small businesses must address.
Platform access costs vary significantly based on implementation approach. The free AEAT public platform application requires no subscription fees, making it the most economical option for small businesses with straightforward needs. Private service providers charge subscription fees typically ranging from ten to one hundred euros or more per month depending on transaction volume and feature requirements. Integration costs for connecting ERP or accounting systems to e-invoicing platforms range from one thousand to ten thousand euros or more depending on system complexity and whether custom development is needed.
ERP and accounting system adjustments create additional expenses. Software upgrades to add structured e-invoicing capabilities to existing systems typically cost five hundred to five thousand euros depending on the vendor and complexity. New software purchases may be necessary for businesses currently using basic tools like Excel or Word for accounting, with dedicated accounting software costing three hundred to two thousand euros annually. VeriFactu compliance requires software certification or updates to meet technical requirements, with costs varying by vendor.
Certified service provider fees apply if businesses choose managed e-invoicing services. Service provider subscriptions range from twenty to two hundred euros or more per month depending on transaction volumes and service levels. Some providers charge per-invoice transaction fees of ten cents to one euro per invoice. Support and maintenance contracts for ongoing technical assistance add to recurring costs.
Professional services assist with various aspects of implementation. Consultancy to understand requirements and plan implementation typically costs one thousand to ten thousand euros depending on business complexity. IT services for system integration and testing range from two thousand to twenty thousand euros or more. Training for staff education on new processes costs five hundred to three thousand euros depending on staff size and training depth.
For a typical SME, total estimated first-year compliance costs range from three thousand to twenty-five thousand euros. The wide range reflects varying factors including current technology sophistication, with businesses using modern cloud accounting systems facing lower costs than those using legacy or manual systems, transaction volume affecting subscription and per-invoice fees, choice of implementation approach with free public platform substantially cheaper than comprehensive commercial solutions, and decision between in-house implementation versus outsourced managed services.
Cash Flow Effects
E-invoicing implementation creates both positive and negative cash flow impacts for small businesses.
Positive cash flow effects emerge primarily after implementation is complete. Faster invoice validation through automated processing reduces payment cycles as customers receive and process invoices more quickly.Early error detection through real-time validation catches mistakes before submission, avoiding delays from rejected invoices that require correction and resubmission.Improved collections benefit from structured invoicing and status tracking enhancing payment management, with better visibility into which invoices are accepted and which require follow-up.Reduced disputes occur because clear standardized invoices minimize commercial disagreements about what was ordered, delivered, or billed.
Negative cash flow impacts occur primarily during the transition period. Upfront investment in technology and implementation requires cash outlays before any benefits are realized. Potential operational disruptions during system changeover may temporarily slow invoicing processes while staff learn new systems. The learning curve creates temporary inefficiency as personnel adapt to new processes and troubleshoot unfamiliar systems.
The net cash flow effect is expected to be modestly positive once systems stabilize, driven by more efficient invoicing processes reducing time spent on manual invoice creation and handling, faster payment cycles as automated processing and improved tracking accelerate collections, and reduced administrative time on manual invoicing activities that can be redirected to revenue-generating activities.
Experience from Italy’s similar Sistema di Interscambio implementation suggests that businesses typically achieve twenty to thirty percent reduction in invoicing administrative time after completing the transition period, though the initial six to twelve months involve learning curves and process adjustments.
Administrative Burden Analysis
E-invoicing creates new administrative burdens during implementation and ongoing operation, while simultaneously eliminating or reducing other burdens once systems are operational.
New administrative burdens include system setup and maintenance requiring initial configuration, testing, and ongoing system management, staff training to learn new software and processes with associated time investment, compliance monitoring to ensure ongoing adherence to technical requirements and format specifications, format compliance efforts to generate and validate structured XML invoices rather than simple PDF or paper documents, and status management to track and respond to invoice status notifications within the four-working-day deadline.
Administrative simplifications that offset these burdens include elimination of paper handling with no printing, mailing, or physical storage of invoices reducing materials costs and physical space requirements, automated data entry as structured invoices can auto-populate accounting systems eliminating manual data entry, reduced manual VAT return preparation with future pre-filling expected to streamline quarterly filing processes, SII exemption benefits as SMEs avoid the more burdensome real-time reporting required of large taxpayers, and improved digital archiving making search, retrieval, and audit compliance easier compared to paper record systems.
The net effect on administrative burden is likely negative (meaning increased burden) in the short term during transition, with systems implementation and staff learning creating temporary overhead. However, long-term effects should be positive (meaning reduced burden) once systems become operational and familiar, with automation and streamlining delivering net time savings.
Studies from Italy where the SdI e-invoicing system has been mandatory since 2019 indicate that after the initial implementation period, businesses typically experience twenty to thirty percent reduction in invoicing administrative time due to automation of previously manual processes, reduction in invoice disputes requiring resolution, and streamlined VAT compliance through better record organization.
Market Impact and Competitive Dynamics
E-invoicing requirements are accelerating digital transformation across the Spanish business ecosystem with various market effects.
Increased digitalization requirements create competitive pressure as early adopters gain efficiency advantages over laggards. Technology adoption is being accelerated as businesses that might have continued with paper or basic PDF invoicing for years are forced to modernize. Digital skills become imperative for staff who must develop competency with new tools and technologies. The ecosystem of e-invoicing service providers and consultants is growing to serve business needs.
Advantages for early adopters create competitive differentiation. Operational efficiency gains from streamlined processes reduce costs faster than competitors who wait until mandatory deadlines. Customer satisfaction improves from professional timely invoicing that enhances business reputation. Better cash management results from improved visibility and control over receivables. Compliance leadership reduces risk and stress compared to last-minute implementation approaches. A modern tech-savvy image in the marketplace can attract progressive customers and partners.
Interoperability challenges require careful navigation. Format compatibility must be ensured across different systems used by trading partners. Platform connectivity between different private agents must function smoothly for seamless exchange. International complexity arises when cross-border customers have different requirements. Transition coordination requires aligning implementation timelines with key trading partners to avoid disruptions.
Market concentration risks exist in the software and service provider sectors. SME software choices are increasingly dominated by a few major providers such as SAP, Oracle, and Microsoft plus specialized Spanish providers. Lock-in concerns arise as switching costs may create dependencies on chosen platforms. Pricing power may shift to providers once businesses are dependent on their services, potentially leading to fee increases over time.
Positive market effects benefit all participants over time. Improved overall compliance reduces the VAT gap, potentially enabling lower tax rates or better-funded public services that benefit all businesses. A leveled playing field emerges as fraud reduction diminishes unfair competition from non-compliant competitors who previously undercut prices by evading VAT obligations. Spain’s economic modernization and digital economy transformation enhance competitiveness internationally.
SME Readiness Assessments
Spanish government and EU authorities have conducted various assessments of SME readiness for e-invoicing implementation.
Public consultations conducted in June 2023 and April 2025 included extensive SME stakeholder input, with trade associations, small business representatives, and accounting professionals providing feedback on draft regulations. The phased timeline with twenty-four months for SMEs reflects explicit recognition of readiness challenges and resource constraints faced by smaller businesses. The free platform provision demonstrates acknowledgment of SME cost sensitivities and commitment to providing no-cost compliance options.
The ViDA initiative at EU level includes specific SME considerations. SME exemptions in Platform Economy rules include a ten-year member state opt-out acknowledging implementation burdens for small platform operators. Flexibility provisions allow member states to tailor rules to protect SMEs from disproportionate compliance costs. Impact assessments conducted by the European Commission before adopting ViDA included extensive SME analysis examining costs, benefits, and implementation challenges.
Trade association feedback has raised various concerns about technological capacity of the smallest businesses, particularly those in rural areas or traditional sectors with limited IT infrastructure, implementation costs relative to turnover for micro-enterprises where several thousand euros represents a significant investment, regional disparities in digital infrastructure affecting ability to access cloud services and technical support, and training and education needs given variable digital literacy among small business owners and staff.
Recommendations from business representatives included extended timelines for micro-enterprises, which has been partially addressed through the twenty-four-month SME phase, enhanced government support and training programs to help businesses navigate technical requirements, simplified technical options for low-volume businesses to reduce complexity, and collaborative platforms for industry sectors enabling shared solutions within specific industries.
Readiness indicators provide mixed signals about SME preparedness. Software vendor preparedness is strong, with major accounting software providers like Sage, A3 Sistemas, and Wolters Kluwer actively developing compliant solutions. The service provider market is expanding with numerous e-invoicing specialists emerging to support SMEs. Training availability is growing through consultants, trainers, and educational programs. However, VeriFactu postponements with two delays pushing implementation from 2026 to 2027 suggest practical implementation challenges remain.
Remaining gaps in SME readiness include limited awareness among micro-enterprises, many of whom remain unaware of coming requirements and timelines, uneven rural and remote area access to digital infrastructure and support services, limited sector-specific guidance for specialized industries, and cost concerns absent direct subsidies to offset compliance expenses.
Recommendations for SME Preparation
Small businesses should take proactive steps to prepare for mandatory e-invoicing compliance.
Begin planning immediately even if in the second implementation phase with a 2028 deadline, as early preparation reduces stress and costs. Assess current systems to determine whether existing software can be upgraded or requires replacement. Engage with vendors by contacting accounting software and service providers to understand options, costs, and timelines. Join trade associations to leverage collective resources, training opportunities, and advocacy efforts. Monitor government guidance as AEAT will publish detailed technical specifications and frequently asked questions. Consider the free platform by evaluating whether AEAT’s public application meets business needs before purchasing commercial solutions. Train staff proactively to build digital skills and e-invoicing knowledge in advance of mandatory deadlines. Test with willing partners by voluntarily exchanging e-invoices with cooperative customers or suppliers before the mandate to identify and resolve issues in a low-stakes environment.
- Official References
Government Portals and Tax Authority Resources
The Spanish Tax Agency (Agencia Estatal de Administración Tributaria – AEAT) serves as the primary source for official information and guidance. The main AEAT portal is located at https://sede.agenciatributaria.gob.es. Specific sections within the portal address VAT information at https://sede.agenciatributaria.gob.es/Sede/en_gb/iva.html, Immediate Supply of Information (SII) guidance at https://sede.agenciatributaria.gob.es/Sede/iva/suministro-inmediato-informacion-sii.html, VAT invoicing requirements at https://sede.agenciatributaria.gob.es/Sede/iva/obligacion-de-facturar.html, and foreign trade transactions at https://sede.agenciatributaria.gob.es/Sede/iva/iva-operaciones-comercio-exterior.html.
The Ministry of Economic Affairs and Digital Transformation oversees e-invoicing policy development and public platform operations. The Electronic Administration portal is located at https://administracionelectronica.gob.es. This ministry coordinates the technical aspects of the e-invoicing infrastructure and publishes regulatory updates.
The Ministry of Finance through the General State Comptroller (IGAE) manages B2G invoicing standards and the FACe platform. The main IGAE portal is at https://www.igae.pap.hacienda.gob.es. The FACe Platform for submitting invoices to Spanish public administrations operates at https://face.gob.es. This platform has been operational since 2015 for mandatory B2G e-invoicing.
Legislative Texts and Royal Decrees
Official legislative texts are published in the Boletín Oficial del Estado (BOE), Spain’s Official State Gazette, accessible at https://www.boe.es.
Royal Decree-Law 15/2025 approved December 2, 2025 postponed VeriFactu implementation to 2027. This decree can be accessed at https://www.boe.es/buscar/doc.php?id=BOE-A-2025-24446.
Royal Decree 1007/2023 established VeriFactu anti-fraud billing software requirements. The official publication is at https://www.boe.es/buscar/doc.php?id=BOE-A-2023-24065.
Royal Decree 1619/2012 governs general invoicing obligations and has been periodically amended. It can be found at https://www.boe.es/buscar/act.php?id=BOE-A-2012-14696.
Law 18/2022, the Crea y Crece Law enacted September 28, 2022, established the legal foundation for B2B e-invoicing. The full text is at https://www.boe.es/buscar/act.php?id=BOE-A-2022-15586.
Law 58/2003, the General Tax Law, provides the overall framework for tax administration and penalties. It is available at https://www.boe.es/buscar/act.php?id=BOE-A-2003-23186.
Draft regulations for implementing the Crea y Crece e-invoicing mandate underwent public consultation in 2023 and 2025. The draft submitted to the European Commission on February 2, 2024 can be found through AEAT and Ministry portals. The second public consultation document from March-April 2025 is available through the Ministry of Economy portal.
Technical Specifications and Standards
The EN 16931 European Standard for electronic invoicing semantic models is documented at https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eInvoicing.
UBL 2.1 (Universal Business Language) specifications are maintained by OASIS and available at https://docs.oasis-open.org/ubl/UBL-2.1.html. Spain has adopted UBL as the mandatory format for the public e-invoicing platform.
CII (Cross Industry Invoice) specifications from UN/CEFACT are at https://unece.org/trade/uncefact/xml-schemas.
Facturae format specifications, Spain’s national XML format for B2G invoicing, are documented at https://www.facturae.gob.es.
PEPPOL network documentation including Business Interoperability Specifications is available at https://docs.peppol.eu/, providing standards expected to support Spanish e-invoicing interoperability.
European Union Resources
The European Commission provides comprehensive e-invoicing country information. The 2025 Spain eInvoicing Country Sheet updated August 14, 2025 is at https://ec.europa.eu/digital-building-blocks/sites/spaces/einvoicingCFS/pages/881983599/2025+Spain+2025+eInvoicing+Country+Sheet.
Directive 2014/55/EU on e-invoicing in public procurement is published at https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32014L0055.
The VAT in the Digital Age (ViDA) initiative information is at https://taxation-customs.ec.europa.eu/vat-digital-age_en. The Council Directive adopted March 11, 2025 establishing digital reporting requirements effective July 2030 can be accessed through EUR-Lex.
Professional Service Firm Publications
Major accounting and advisory firms publish regular updates and analysis of Spanish e-invoicing developments.
EY (Ernst & Young) published analysis titled “Spain | New draft regulation updates requirements for upcoming mandatory e-invoicing for B2B transactions” on March 27, 2025, available at https://www.ey.com/en_gl/insights/tax/spain-new-draft-regulation-updates-requirements-for-upcoming-mandatory-e-invoicing-for-b2b-transactions. This publication analyzes the second public consultation draft.
KPMG has published multiple resources including “Spain: VERI*FACTU invoicing system delayed to 2027” dated December 3, 2025. The TaxNewsFlash is at https://kpmg.com/us/en/taxnewsflash/news/2025/12/tnf-spain-verifactu-invoicing-system-delayed-to-2027.html. A detailed report on Royal Decree-Law 15/2025 is at https://assets.kpmg.com/content/dam/kpmg/es/pdf/2025/12/royal-decree-law-15-2025-verifactu.pdf. KPMG also hosted a webinar on November 7, 2023 titled “E-invoicing and digital reporting across the EU” covering Spain, Poland, Romania, Germany, Belgium, and France.
Deloitte provides Spain e-invoicing updates through its Tax Alerts publication series available to subscribers, with country-specific guidance on VeriFactu and Crea y Crece implementation.
PwC (PricewaterhouseCoopers) publishes Spain VAT and e-invoicing updates in its Tax Insights series at https://www.pwc.com/es/en/tax-legal-services.html.
Grant Thornton published “Verifactu postpones its entry into force to 2027” on December 3, 2025 at https://www.grantthornton.es/en/insights/tax-news/verifactu-postpones-its-entry-into-force-to-2027. An earlier publication “Spain’s steps towards e-invoicing” dated January 14, 2025 is at https://www.grantthornton.de/en/insights/articles-and-publications/spains-steps-towards-e-invoicing.
RSM Spain published “VeriFactu postponed until 2027” on December 4, 2025 at https://www.rsm.global/spain/en/insights/tax-news/verifactu-postponed-until-2027. An earlier alert “October 2025 VeriFactu: New Invoicing Obligations in Spain” is at https://www.rsm.global/spain/en/insights/tax-news/verifactu-new-invoicing-obligations-spain-2026.
BDO provides analysis including “Spain – E-Invoicing, Billing Systems and the ViDA Package” in its Indirect Tax News series at https://www.bdo.global/en-gb/insights/tax/indirect-tax/spain-e-invoicing-billing-systems-and-the-vida-package. An earlier publication “Spain – Draft regulations issued on mandatory B2B e-invoicing” from June 2023 is at https://www.bdo.global/en-gb/insights/tax/indirect-tax/spain-draft-regulations-issued-on-mandatory-b2b-e-invoicing.
Technology Provider and Industry Resources
Technology service providers offer practical implementation guidance and updates.
EDICOM published “Status of Mandatory Electronic Invoicing Between Companies in Spain” updated March 27, 2025 at https://edicomgroup.com/blog/electronic-invoicing-will-be-mandatory-for-spanish-companies.
VATCalc published “Spanish B2B Crea y Crece e-invoice approved July 2027-28” on March 24, 2026 at https://www.vatcalc.com/spain/spanish-b2b-crea-y-crece-e-invoice-approved-july-2027-28.
Taxually published “E-Invoicing Spain: Everything You Need to Know” dated December 17, 2025 at https://www.taxually.com/blog/e-invoicing-spain-everything-you-need-to-know.
Marosa VAT offers “E-invoicing in Spain: Complete Guide” at https://marosavat.com/e-invoicing-in-spain-complete-guide.
Global VAT Compliance published “Spain: Mandatory e-invoicing starts 2026” at https://www.globalvatcompliance.com/spain-mandatory-e-invoicing-starts-2026.
Avalara provides “Spain’s e-invoicing mandate: Latest updates and timeline” at https://www.avalara.com/eu/en/learn/guides/spain-e-invoicing-mandate.html.
All referenced links were verified as accessible in March 2026. For the most current information, businesses should regularly check official government portals and consult with qualified tax advisors to ensure compliance with evolving requirements.
- Summary
Scope of Spain’s E-Invoicing Framework
Spain has implemented a comprehensive two-tier digital invoicing framework combining mandatory structured electronic invoicing with anti-fraud software requirements. On March 24, 2026, Spain’s Council of Ministers officially approved the Royal Decree implementing the B2B e-invoicing mandate under the Crea y Crece Law (Law 18/2022), marking a critical milestone in Spain’s digital tax transformation.
The framework operates through two parallel systems. The Crea y Crece B2B E-Invoicing Mandate requires structured electronic invoicing for all domestic business-to-business transactions between Spanish-established entities. The VeriFactu Anti-Fraud System mandates certified billing software that ensures invoice integrity, traceability, and protection against retroactive alterations through chained hash systems and digital signatures.
The mandate covers domestic B2B transactions comprehensively while exempting business-to-consumer transactions, cross-border transactions with non-residents, intra-EU supplies and acquisitions, and imports and exports. Business-to-government e-invoicing has been mandatory since 2015 through the FACe platform and operates independently of the new B2B mandate.
Self-billing arrangements are permitted within the e-invoicing framework and must utilize structured formats when both parties are subject to the mandate. Triangulation transactions involving multiple EU member states are currently exempt but will face enhanced reporting under the EU’s ViDA initiative from July 2030. Special VAT regimes including margin schemes and travel operators must comply with e-invoicing requirements while applying their specific VAT calculation rules.
Implementation Timeline
The phased implementation reflects Spain’s pragmatic approach to balancing comprehensive tax compliance with business readiness.
VeriFactu anti-fraud software requirements, postponed twice from original 2026 deadlines, now mandate compliance beginning January 1, 2027 for businesses outside the SII regime and July 1, 2027 for other companies and self-employed individuals using invoicing software.
The Crea y Crece B2B E-Invoicing mandate approved on March 24, 2026 begins implementation following publication of a Ministerial Order expected before July 1, 2026. Phase One targets large businesses with annual turnover exceeding eight million euros, requiring compliance twelve months after the Ministerial Order, estimated around July 2027. Phase Two extends to all other businesses and freelancers twenty-four months after the Ministerial Order, estimated around July 2028. Phase Three addresses invoice status notification obligations thirty-six months after the Ministerial Order for smaller businesses, estimated around July 2029.
A grace period during the first twelve months requires businesses to provide PDF copies alongside structured e-invoices to ensure compatibility with trading partners not yet required to receive electronic invoices.
Key Technical Obligations
Businesses must comply with comprehensive technical requirements spanning invoice formats, transmission methods, and archiving practices.
Structured invoice formats include UBL (now mandatory for the public platform), CII, EDIFACT, and Facturae, with UBL emerging as the standard aligning Spain with European interoperability frameworks. Digital signatures using advanced electronic signatures under eIDAS or EDI-based authentication mechanisms ensure authenticity and integrity. QR codes must be embedded in all invoices enabling verification by customers and tax authorities. VeriFactu-compliant software implements chained hash systems linking sequential invoices to prevent retroactive tampering.
Transmission occurs through a hybrid model combining a free public AEAT platform with private certified service providers, likely leveraging PEPPOL network infrastructure for interoperability. Private exchanges must duplicate invoice copies to the public repository ensuring comprehensive tax authority visibility. Near-real-time transmission follows four-working-day deadlines aligned with existing SII requirements for large taxpayers.
Recipients must communicate invoice status including acceptance or rejection and payment information within four working days of receipt.
Archiving requires four-year retention in original structured formats with preserved digital signatures and hash chain integrity. VeriFactu mode with real-time transmission to AEAT eliminates local storage requirements, while Non-VeriFactu mode mandates four-year local retention with tamper-proof storage.
Compliance Risks and Penalties
Spain has established substantial penalties to enforce e-invoicing compliance.
Failure to issue e-invoices carries penalties up to ten thousand euros per infraction, with systematic non-compliance potentially resulting in cumulative penalties across multiple transactions. Businesses using non-compliant VeriFactu software face penalties up to fifty thousand euros per year, while software vendors offering non-compliant products face up to one hundred fifty thousand euros per year per product.
Archiving violations resulting in inability to produce invoices during audits can trigger presumptive tax assessments, penalties ranging from six thousand to sixty thousand euros, and increased tax liabilities due to inability to substantiate transactions. Tampering with archived invoices or breaking VeriFactu hash chains may lead to fraud investigations and potential criminal prosecution.
Penalties distinguish between negligent errors, which carry fifty to one hundred percent of evaded tax plus administrative fines, and intentional violations, which result in one hundred to one hundred fifty percent of evaded tax, potential criminal prosecution for evasion exceeding one hundred twenty thousand euros, and possible prison sentences up to five or six years depending on severity.
Operational risks include system failures disrupting invoice issuance, format errors causing platform rejection, integration problems with incompatible ERP systems, and trading partner coordination challenges during phased implementation. Financial risks encompass cash flow disruption during transition, implementation costs of three thousand to twenty-five thousand euros or more for typical SMEs, and significant penalty exposure for non-compliance.
SME-Specific Implications
Small and medium enterprises face distinct challenges and opportunities under the e-invoicing framework.
All SMEs are subject to the mandate regardless of size, with no permanent revenue-based exemptions, though phased implementation provides SMEs with twenty-four months versus twelve months for large companies, offering critical additional preparation time. The free AEAT public platform application reduces financial barriers for businesses unable to invest in commercial solutions. Extended timelines enable SMEs to learn from large company implementations and align budget cycles for technology investments.
First-year compliance costs for typical SMEs range from three thousand to twenty-five thousand euros covering platform access, ERP adjustments, software upgrades, and professional services. No direct government subsidies have been announced, requiring SMEs to fund implementation from operating budgets. Some indirect support may be available through regional digitalization grants and EU Digital Europe Programme funding.
Short-term administrative burdens include system setup, staff training, and process changes. Long-term benefits include twenty to thirty percent reduction in invoicing administrative time, faster payment cycles improving cash flow, reduced disputes through standardized invoicing, and enhanced digital capabilities improving competitiveness.
Market effects favor early adopters who gain operational efficiency and competitive advantages. Increased digitalization requirements force modernization across all business sizes. Interoperability challenges require careful platform and format selection to ensure compatibility with diverse trading partners.
Government and trade association readiness assessments reveal mixed preparedness, with strong software vendor development activity but significant awareness gaps among micro-enterprises, uneven digital infrastructure in rural areas, and ongoing concerns about costs and technical capacity.
Critical Dates and Immediate Actions
Businesses face several critical compliance milestones requiring proactive preparation.
March 24, 2026 marked the Royal Decree approval by the Council of Ministers, establishing the legal foundation for mandatory e-invoicing. Before July 1, 2026, the Ministerial Order defining technical specifications is expected, starting the implementation countdown. Throughout 2026, businesses should assess systems, select solutions, and begin preparations.
January 1, 2027 brings VeriFactu compliance requirements for large businesses outside SII. July 1, 2027 extends VeriFactu to other businesses using invoicing software. Around July 2027, Crea y Crece Phase One requires large businesses exceeding eight million euros turnover to implement B2B e-invoicing.
Around July 2028, Crea y Crece Phase Two mandates compliance for all other businesses and freelancers. Around July 2029, invoice status notifications become mandatory for SMEs.
July 2030 brings EU ViDA Digital Reporting Requirements for intra-EU transactions, requiring ten-day reporting of cross-border commerce. Beyond 2030, pre-filled VAT returns based on e-invoicing data are expected, significantly streamlining periodic VAT compliance.
Immediate recommended actions include conducting readiness assessments of current invoicing processes and system capabilities, determining applicable compliance phase based on turnover thresholds, budgeting for technology, services, and training costs, evaluating solution options comparing the free AEAT platform with commercial providers and ERP upgrades, engaging stakeholders across management, IT, finance, and operations, contacting software vendors to discuss upgrade paths and timelines, monitoring AEAT portal regularly for technical specifications and guidance, planning trading partner coordination to ensure mutual readiness, considering pilot testing through voluntary e-invoice exchange with cooperative partners, and seeking professional advice from tax advisors and IT consultants for tailored implementation strategies.
Spain’s e-invoicing transformation represents one of Europe’s most comprehensive digital tax initiatives, affecting millions of businesses from multinational corporations to individual freelancers. The March 24, 2026 Royal Decree approval marks the transition from planning to execution. Proactive preparation leveraging the phased timeline, available support resources, and lessons from other countries’ implementations will be critical for successful compliance and realization of the long-term benefits of streamlined, automated, and transparent invoicing processes that reduce VAT fraud, improve cash flow management, and position Spanish businesses for success in an increasingly digital European economy.
Spain’s regions of País Vasco (Basque Country) and Comunidad Foral de Navarra have autonomous tax systems and have introduced their own e-invoicing and e-reporting requirements, which differ somewhat from the state system.
- 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
- Join the Linkedin Group on Global E-Invoicing/E-Reporting/SAF-T Developments, click HERE
Latest Posts in "Spain"
- Spain Approves Mandatory B2B E‑Invoicing: Royal Decree Adopted on 24 March 2026, implementation July 1, 2027?
- IMF Urges Spain to Phase Out VAT Reductions in Broader Tax Reform Plan
- Oil Companies Face €6 Million Fines for Failing to Apply Fuel VAT Reduction Properly
- Spain Unveils €5 Billion Plan to Cut Energy VAT, Fuel Prices Amid Middle East Crisis
- Spain Plans to Cut Fuel VAT to 10% to Counter Price Surge Amid Middle East Conflict












