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

---

Executive Summary

---

---

INDEPTH ANALYSIS

1. Scope of the Mandate

1.1 E-Invoicing vs. E-Reporting Obligations: Spain’s current and forthcoming regulations distinguish between electronic invoicing (factura electrónica)—the obligation to issue invoices in a structured digital format—and electronic reporting of invoice data to the tax authorities. Today (as of April 2026), e-invoicing is compulsory for B2G (business-to-government) transactions only, under Ley 25/2013, which requires suppliers to issue structured invoices (in the national Facturae XML format with a qualified e-signature) to public administrations via the FACe platform. For B2B (business-to-business) and B2C (business-to-consumer) transactions, e-invoicing is not yet mandatory in general; businesses can still use paper or PDF invoices, except for certain large companies in regulated sectors that must offer e-invoices to consumers on request (per Law 56/2007).

However, major changes have been enacted for B2B e-invoicing but are not yet in effect. Article 12 of Ley 18/2022 (Ley “Crea y Crece”) mandates that all invoices in commercial transactions between entrepreneurs and professionals (i.e. B2B) must be electronic. This will apply broadly to domestic B2B dealings once the supporting regulations take effect (see Implementation Timeline below). The goal is to leverage e-invoicing to curb late payments and modernize business processes. Under the new system, e-invoices will also carry “invoice status” reporting obligations: recipients must report whether each invoice is accepted or rejected and when it is paid. Thus, Spain’s B2B e-invoicing mandate is intertwined with new requirements ensuring full traceability of the invoice lifecycle (from issue to payment) as a means to enforce payment discipline and to give tax authorities visibility into transactions. [kpmg.com], [kpmg.com]

In parallel, since 2017 Spain has operated the SII (Suministro Inmediato de Información), a well-established e-reporting system for VAT. Under SII, large taxpayers and certain others must upload details of each invoice (sales, purchases, etc.) to the tax agency’s servers within four days of issuance or receipt. SII is currently in force (applying to roughly 75,000 large taxpayers) and constitutes a form of near-real-time electronic reporting, though it does not require using specific invoicing formats (taxpayers can still issue PDFs or paper invoices while separately reporting the data). Now, Spain is expanding e-reporting through the VERIFACTU* system (part of the 2021 Anti-Fraud Law 11/2021) which targets all businesses not in SII. The VERI*FACTU regime (also called SIF for Sistemas Informáticos de Facturación) will require certified invoicing software that can create tamper-proof invoice records and transmit them to the Tax Agency in real time or on request. The legal basis for VERIFACTU is in force (via Law 11/2021 and Royal Decree 1007/2023), but its effect has been deferred to 2027 by subsequent decrees (see Timeline). When effective, VERIFACTU will obligate in-scope businesses to either send each invoice to the Tax Agency within seconds of issuance (online mode) or maintain an internal system that securely stores invoice data with digital signatures and periodic QR code generation (offline mode) for later verification. Importantly, companies already under SII are exempt from VERI*FACTU, as they are already reporting detailed invoice data continuously to the AEAT. In summary, Spain’s approach is evolving into a comprehensive CTC (continuous transaction control) environment: structured e-invoices will be mandatory for B2B exchanges, and electronic transmission of invoice data to the tax authority will be required either via SII or VERI*FACTU, ensuring the Tax Agency has timely access to transaction information. [vatupdate.com]

1.2 Transactions Covered: The B2B e-invoicing mandate (Ley 18/2022 and RD 238/2026) will cover **all invoices in commercial transactions where both issuer and recipient are established in Spain and acting as business persons or professionals (i.e. B2B). This includes domestic B2B supplies of goods or services of any amount – there is no lower threshold once the law is in effect. B2G (business-to-government) invoicing has been fully electronic since 2015, and remains governed by separate regulations (FACe platform and “Facturae” format). B2C (business-to-consumer) transactions are mostly excluded from the new mandatory e-invoicing regime. Consumers are not required to receive e-invoices, except that certain large companies in regulated sectors (utilities, telecoms, insurance, etc.) must offer e-invoices to customers who request them, as per existing law. For ordinary B2C sales, paper or PDF invoicing remains permissible, and the upcoming B2B e-invoicing mandate does not directly compel small B2C merchants to issue e-invoices to retail customers. (It’s worth noting, however, that if businesses upgrade their systems for B2B e-invoicing and compliance, they may incidentally start issuing more e-receipts or e-tickets to consumers as well, though that would be by choice or other legal requirements rather than by the Crea y Crece law itself.)

The B2B e-invoicing mandate is territorially limited to Spanish-established parties. Therefore, cross-border transactions are generally not subject to the Spanish e-invoicing obligation. Intra-EU B2B supplies (exports) from Spain and intra-EU acquisitions or imports by Spanish companies fall under EU VAT Directive rules requiring a VAT invoice but not a Spanish-specific e-invoice format. Similarly, B2B transactions where either the supplier or customer is not established in Spain are outside the domestic e-invoice mandate’s scope. For instance, a German company selling to a Spanish company need not issue a Spanish-format e-invoice; likewise, a Spanish company selling to France sticks to EU rules (until new EU-wide e-invoicing standards arrive with the VAT in the Digital Age (ViDA) reforms expected in 2028). However, Spanish businesses will still have to report many cross-border transactions through other means (e.g. via SII if they use it, or the EU’s forthcoming Digital Reporting Requirements for cross-border sales once implemented). [vatcalc.com]

Domestic chain transactions and triangulation are treated per general VAT rules. If multiple Spanish businesses participate in a chain of supplies within Spain, each B2B invoice in the chain must be electronic under the new mandate, even if the transaction is part of a larger sequence. If a chain involves cross-border legs (triangulation across countries), the Spanish part of the transaction (e.g. a Spanish company’s sale to a Spanish customer) is covered by the mandate, but the foreign parts are not. Imports and exports (transactions where goods enter or leave the EU) are not subject to Spanish e-invoicing requirements for the cross-border leg, since those invoices are typically issued under foreign jurisdiction. Nonetheless, Spanish importers and exporters must still comply with customs and existing VAT documentation rules, and report these movements in VAT returns or Intrastat, and if under SII, report import/export invoice data in their ledgers (SII has special codes for imports, exports, intra-EU sales/purchases, etc.).

1.3 Inclusion of Special Cases: Self-billing (facturación por el destinatario, where the buyer issues the invoice on the supplier’s behalf) is permitted under current VAT rules, subject to a prior mutual agreement and the supplier’s acceptance of each invoice. The invoice must state it was issued by the recipient (“Factura expedida por el destinatario”). Under the new e-invoicing regime, self-billed invoices remain allowable but will need to be in compliant electronic format. If the buyer (self-biller) is responsible for issuing the invoice, the buyer’s e-invoicing system must generate a structured invoice and deliver it to the supplier via the agreed platform, while also ensuring any required reporting to the tax authority is performed. The tax authorities have clarified how such cases are handled: if a supplier is an SII filer and legal provisions require the customer or a third party to issue the invoice, the supplier is exempt from duplicative VERI*FACTU reporting for that invoice. In general, though, self-billing does not exempt the transaction from e-invoicing or reporting – it simply shifts the issuance responsibility to the customer, who must then use an approved system to issue the e-invoice. [vatupdate.com]

Triangulation and chain transactions do not receive special exemptions apart from the territorial scope rules noted above. If a transaction is a purely Spanish domestic triangular transaction (multiple VAT-registered Spanish businesses involved in a supply chain for a single movement of goods), each inter-company sale is treated as a Spanish B2B supply requiring an e-invoice. If a transaction qualifies as EU triangulation (with an intermediate supplier in Spain and goods delivered from one Member State directly to another), the Spanish intermediary still must issue a VAT-compliant invoice (usually without Spanish VAT, referencing the EU triangulation simplification). That invoice to the final EU customer is not within the Spanish e-invoice mandate because the customer is not established in Spain. Chain transactions documentation (e.g. where multiple resellers are involved) must observe existing VAT invoice rules (like indicating any application of the domestic reverse charge on certain supplies, etc.), and the eventual e-invoice formats will support those details through proper coding or free-text fields.

Likewise, special VAT regimes (such as the margin scheme for second-hand goods, the travel agencies’ regime, or the Canary Islands IGIC for the Canary region) are generally not exempt from the obligation to issue e-invoices if the transaction is B2B within Spain. Invoices issued under these regimes will need to be electronic and contain the relevant informational elements (for example, margin scheme invoices should include an indication that VAT is charged on the profit margin and not deductible by the buyer). One caveat: businesses operating entirely under the simplified VAT regime or conducting only VAT-exempt activities are initially exempt from the VERI*FACTU software requirements, as noted in the regulations. But even those businesses, when transacting with other businesses, will eventually have to issue e-invoices under the Crea y Crece law (unless further exemptions are granted by regulation). So far, simplified invoices (tickets or invoices of a very small amount that don’t require full formalities) are exempt from the B2B e-invoicing mandate. Additionally, transactions where there is no legal obligation to issue an invoice (e.g. certain exempt healthcare or financial services to businesses) wouldn’t be drawn into the e-invoicing scope either. But whenever an invoice is legally required in B2B contexts, it will have to be electronic under the new regime. [kpmg.com] [vatcalc.com]

2. Taxable Persons in Scope

2.1 Businesses and Persons Covered: The e-invoicing and e-reporting requirements, both current and future, apply to taxable persons conducting economic activities in Spain. In practice, that means all “empresarios o profesionales” established in Spain (Spanish companies and self-employed entrepreneurs) are within scope. This includes Spanish companies (tax resident or with a fixed establishment in Spain) and Spain-resident sole traders (autónomos). The upcoming B2B e-invoicing mandate explicitly covers “empresas y profesionales” in Spain, so essentially any entity or individual with a Spanish tax ID who is obligated to issue VAT invoices for business transactions will have to comply. It also covers public-law entities when they act as businesses (though most B2G flows are already under existing e-invoicing rules).

The VERI*FACTU (SIF) system will apply to a very similar population. According to the law and regulations, all entities that are obligated to keep Spanish VAT records and are not using SII must adopt SIF-compliant invoicing systems. This includes Spanish corporate taxpayers (entities under Impuesto de Sociedades), Spanish permanent establishments of non-residents, and self-employed professionals who issue invoices. As noted, those already in the SII system are excluded from SIF, on the premise that their real-time VAT reporting is sufficient and they already meet high integrity standards. Foreign companies without a physical presence in Spain (no permanent establishment) are not explicitly required to comply with the new e-invoicing or SIF mandates, even if they are VAT-registered in Spain for certain transactions. For example, a non-established business that just has a Spanish NIF for VAT (without local establishment) can continue issuing invoices in paper/PDF (following general EU rules) and filing VAT returns as today, at least until any future EU-level mandate might apply. That said, if such a foreign company voluntarily uses a Spanish-certified billing system or partners with a local platform, they can certainly issue Spanish-compliant e-invoices; it’s just not a legal requirement for them under current Spanish law. [kpmg.com] [vatupdate.com]

2.2 Exemptions and Sector-Specific Rules: Some types of taxpayers and transactions are exempt or excluded from the new requirements, particularly for the SIF/VERI*FACTU regime:

• Small businesses under the Simplified VAT Regime (régimen simplificado, often small retailers or farmers paying flat-rate VAT) are initially exempt from the VERI*FACTU requirements. Likewise, businesses that conduct only VAT-exempt operations (and thus don’t charge VAT) are exempted from SIF until further notice. The rationale is that these businesses present lower VAT fraud risks. [kpmg.com]
• Entities in the Basque Country and Navarra (which have semi-autonomous tax regimes) are not subject to the national VERIFACTU system, since those regions have implemented their own electronic invoice control systems. For instance, the Basque provinces are rolling out the TicketBAI system, which is similar in concept to VERIFACTU (requiring certified invoicing software and reporting). [kpmg.com]
• The B2B e-invoicing mandate excludes invoices that are not legally required under VAT law (for example, certain very small cash sale receipts that qualify as “simplified invoices” do not need full invoice formalities and so wouldn’t need to be issued as structured e-invoices). [vatcalc.com]
• As mentioned, B2C transactions and purely cross-border B2B transactions are out of scope for mandatory e-invoicing. A Spanish business may choose to send e-invoices to foreign customers (many already do for efficiency), but it’s not enforced by Spanish law. This might change in the future if EU legislation (ViDA) comes into effect for cross-border dealings, but that would be via EU regulations, not the Spanish national law.
• Importantly, being below a certain size is not a permanent exemption for B2B e-invoicing. Unlike some countries that have thresholds for e-invoicing, Spain’s law will eventually cover even microenterprises and freelancers. The only size-related consideration is the timing (smaller firms have more time to comply). There was initial discussion about possibly exempting the very smallest businesses, but the law as enacted does not provide such an exemption.

2.3 Voluntary Participation and Pilot Programs: Prior to mandates taking effect, Spain encourages voluntary adoption. Businesses not yet obligated can choose to issue e-invoices and even to opt in to the SII real-time reporting system if they wish. While relatively few SMEs have joined SII voluntarily due to its complexity, the option exists and opting into SII would effectively exempt a company from the upcoming VERI*FACTU obligations (since SII and VERIFACTU are mutually exclusive reporting systems). To aid smaller companies, the government has rolled out support schemes like the “Kit Digital” vouchers (part of the EU-funded digital recovery program), which provide financial assistance for SMEs to acquire approved e-invoicing and bookkeeping software. Additionally, the AEAT has set up a test environment (in 2024–2025) for developers and early adopters to pilot the SIF/VERIFACTU system and ensure their tools are compatible. A voluntary pilot phase for the public e-invoicing platform is expected once the Ministerial Order is released, enabling businesses to register and experiment before the obligations kick in. Early adoption may allow businesses (especially startups and tech-savvy SMEs) to streamline their processes ahead of competitors, potentially giving them a head start in adjusting to the new normal of digital compliance. [vatupdate.com]

3. Implementation Timeline

3.1 Current State (Measures in Force):

• January 2015: B2G e-invoicing becomes mandatory via Ley 25/2013, requiring electronic invoices (Facturae format) for most invoices issued to public administrations.
• July 2017: Immediate Supply of Information (SII) enters into force as a voluntary/mandatory e-reporting system. It is mandatory for large companies (annual turnover over €6M), those in monthly VAT refund regime (REDEME), and VAT groups, affecting an initial ~75,000 taxpayers. SII requires sending invoice details to AEAT within 4 days of issuance/receipt. [vatupdate.com]
• October 2015 – ongoing: B2C e-invoicing offer in certain sectors. Per Law 56/2007 and related regulations, utilities, telecom operators, insurers, and other large service providers must accommodate consumers who opt into e-invoicing and preserve those invoices for 4 years. However, this is a right for consumers rather than a blanket mandate on B2C issuers.
• July 2021: Spain’s Anti-Fraud Law (Ley 11/2021) introduces the requirement for “integrity and inviolability” of electronic records, effectively outlawing the use of software that allows undeclared sales (“double sets of books”). This law laid the groundwork for the certification of invoicing systems (VERI*FACTU) and provided for fines up to €50,000 for companies and €150,000 for software vendors that violate these requirements. The details were to be established via regulations.
• December 2023: Royal Decree 1007/2023 is published, defining the Reglamento de Requisitos del SIF (billing software requirements). It specifies technical standards for invoice software (secure hashing of records, digital signatures, QR codes on invoices, data fields, etc.) and amendments to Spain’s invoicing rules to align with the coming e-invoicing mandate. While RD 1007/2023 took effect in January 2024, its key obligations were not immediately enforceable for taxpayers, pending defined transition dates.
• October 2024: Order HAC/1177/2024 is issued by the Ministry of Finance, publishing the technical specifications for SIF/VERI*FACTU. This includes data schemas (XML formats for invoice record submissions), details on the QR code generation, and specifics on the secure hashing and archiving requirements for compliant software. This order effectively allowed software developers to finalize their systems for VERI*FACTU compliance.
• April 2025: Royal Decree 254/2025 is approved (BOE 2 April 2025), making two key adjustments: (1) It postponed the initial SIF/VERI*FACTU deadlines by six months (shifting them from mid-2025 to the start of 2026), and (2) it clarified certain points in RD 1007/2023, such as excluding SII users from any duplicative requirements when invoices are issued by third parties or self-billed due to legal obligations. [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
• December 2025: Facing calls from business associations for more time, the government further delayed the VERI*FACTU mandate via Royal Decree-Law 15/2025 (2 December 2025). This set the new deadlines for SIF compliance to 1 January 2027 for companies (corporate income tax payers) and permanent establishments, and 1 July 2027 for all other covered persons (generally self-employed and others using Spanish VAT numbers). This one-year extension (from 2026 to 2027) was enacted to ensure businesses had sufficient time to adapt their software and processes. [kpmg.com], [kpmg.com]
• March 2026: Royal Decree 238/2026 is published (BOE 31 March 2026) after being approved by the Council of Ministers on 24 March 2026. This RD formally implements the Ley Crea y Crece B2B e-invoicing mandate. It reiterates the requirement of structured e-invoices for B2B transactions, mandates invoice status reporting, and defines a system of interoperable private platforms plus a central public platform to be regulated by a forthcoming Ministerial Order. The RD itself, however, does not specify exact dates – instead, it stipulates that the obligations will start after a Ministerial Order (from the Ministry of Finance) is issued to lay out technical and procedural details.

3.2 B2B E-Invoicing – Latest Timeline and Staged Rollout: As of April 2026, the precise start dates for mandatory B2B e-invoicing have been clarified through a draft Ministerial Order released for public consultation on 17 April 2026. According to this draft Order, it will enter into force on 1 October 2026, which will formally trigger the countdown periods specified in the law. This means the B2B e-invoicing mandate is expected to apply from the following dates (assuming the Order is finalized as drafted): [zerocoma.com], [docuten.com]

• From 1 October 2027: Mandatory e-invoicing for large companies with annual turnover above €8 million. [zerocoma.com], [docuten.com]
• From 1 October 2028: Mandatory e-invoicing for all remaining businesses and self-employed professionals (turnover up to €8 million). [zerocoma.com]

These dates represent the end of the 12-month and 24-month adaptation periods respectively, counted from the Order’s entry into force on 1 October 2026. It is important to note that as of April 2026 these dates are drawn from a draft Order under consultation – the final Ministerial Order (expected to be published by mid-2026) could potentially adjust the timeline, although the inclusion of a concrete start date in the draft suggests a high likelihood that 1 October 2026/2027/2028 will be the official schedule. This timeline is aligned with earlier government estimates (which anticipated an Order by mid-2026 and go-live by mid-2027 for large taxpayers), but the draft Order’s schedule now provides a specific reference date and a slightly later start (October rather than July, allowing a bit more time). [zerocoma.com], [zerocoma.com] [zerocoma.com], [docuten.com] [vatupdate.com], [vatupdate.com]

In practical terms, if the Ministerial Order is indeed published in Spain’s Official Gazette (BOE) with an effective date of 1 October 2026, then by 1 October 2027 the largest companies will be obliged to use e-invoices for B2B and comply with all associated requirements, and by 1 October 2028 every remaining VAT-registered business in Spain will have to do the same. These obligations will only start on those dates – until then (through September 2027/2028), e-invoicing remains voluntary (except for B2G and specific cases). The law also requires that during the first year after a business is required to e-invoice, it must, upon request, provide a paper or PDF copy to recipients who are not yet obliged to receive e-invoices. This transitional measure ensures that when the first wave (large companies) comes into mandate in Oct 2027, they can’t force their smaller clients to accept only e-invoices; they must supply a readable copy (unless the client agrees to purely electronic) until October 2028, when those smaller clients themselves become subject to the mandate. [zerocoma.com] [taxnews.ey.com]

3.3 VERI*FACTU (Anti-Fraud Software) Timeline: The rollout of the VERI*FACTU invoicing software requirements runs on a parallel track. The legal provisions in Law 11/2021 and RD 1007/2023 were technically effective from 2024, but enforcement was delayed to ensure readiness. As noted, a second deferral moved VERI*FACTU’s start to 2027: Companies subject to corporate tax (generally all incorporated businesses) and Spanish permanent establishments must comply by 1 January 2027, and all other in-scope taxpayers (primarily self-employed individuals and smaller entities) by 1 July 2027. These dates are now set in stone by Real Decreto-ley 15/2025 and will mark the end of the “grace period” for software adaptation. The interval before these deadlines is effectively a testing and transition period (“periodo de pruebas”), during which businesses can get their systems certified and running. The AEAT has stated that during the test phase, taxpayers can use the VERI*FACTU system on a voluntary basis (submitting test records) without being bound to stay in it until the mandatory date, and they may continue using their old invoicing systems in parallel up to the cut-off dates. By mid-2027, however, all affected companies must be fully compliant—i.e., using only certified software for invoicing and, if they choose the online mode, transmitting invoice records as required. Failure to meet this can trigger penalties (see Penalties & Enforcement). [kpmg.com], [kpmg.com] [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]

3.4 Grace Periods and Future Developments: While the main dates are now clearer, there is still some dependency on the final Ministerial Order. If the Order’s publication is delayed beyond 1 October 2026, the start dates for mandatory e-invoicing would shift accordingly. As of April 2026, 1 October 2027 and 1 October 2028 are the anticipated deadlines (based on the draft Order), but these should be confirmed once the Order is official. Spanish authorities are expected to provide further guidance as these dates approach, possibly including additional “soft landing” measures. Apart from the PDF-copy rule for the first year of B2B e-invoicing, there may be a relatively lenient enforcement posture in the initial months, focusing on education over sanctions. On the other hand, the government has been consistently signaling that businesses should not delay preparations. The public messaging (from official communications in March–April 2026) stresses that while the deadlines seem distant, companies need to use the lead time wisely to adapt and test systems so that they can comply smoothly when the time comes. [zerocoma.com], [docuten.com] [docuten.com], [zerocoma.com]

Looking further ahead, EU-level changes (ViDA) are on the horizon for the late 2020s. The Spanish timeline is designed to dovetail with EU plans to mandate electronic invoicing for cross-border EU transactions by 2028 and move toward harmonized digital reporting. If the EU Directive on VAT digital reporting is adopted in 2024–2025 as proposed, by 2028 Spanish businesses will also need to issue e-invoices for intra-EU B2B sales and report them to a central EU system. Spain’s early adoption of a domestic e-invoicing system by 2027 positions it well to integrate these requirements, likely requiring only minor adjustments to extend e-invoicing to cross-border transactions when the time comes. [vatcalc.com], [vatcalc.com]

4. Technical & Functional Requirements

4.1 E-Invoicing Specifications (Format and Content): The Spanish regulations require that electronic invoices be issued in a structured format that is machine-readable, not just as human-readable images or PDFs. The forthcoming Ministerial Order is expected to confirm that accepted e-invoice formats will align with European standards. Likely formats include:

• UBL 2.1 (ISO/IEC 19845:2015 UBL) – a widely used XML format for e-invoices in the EU, compatible with the EN 16931 semantic data model. [vatcalc.com], [vatcalc.com]
• UN/CEFACT Cross-Industry Invoice (CII) – an internationally recognized XML standard (also aligned with EN 16931) used in some European e-invoicing implementations. [vatcalc.com]
• EDIFACT invoice messages – the classic EDI format for electronic data interchange, accepted in structured invoicing. [vatcalc.com]
• Facturae (Spain’s national XML format) – currently used for B2G invoices; an updated version of Facturae (conforming to the European standard’s core elements) will continue to be supported, especially for compatibility with the government’s own platform and traditional Spanish systems.

All these formats correspond to the European e-Invoicing Standard (EN 16931) either directly or via an extension, ensuring that the required semantic data elements are present. This common semantic model permits interoperability. In fact, the emphasis on UBL by Spanish authorities suggests they may leverage the PEPPOL network (which relies on UBL) for cross-platform exchange, or at least ensure that private platforms can use PEPPOL BIS standards to communicate invoices to each other or to the public platform. [vatcalc.com], [vatcalc.com]

Every e-invoice must contain the mandatory fields set out in Spanish VAT regulations and the EU VAT Directive:

• Identification of the parties: Full name (or company name) and address of the supplier and customer; their Tax ID (NIF for Spanish entities, or CIF for certain entities, and EU VAT number for intra-EU); for foreign buyers/sellers, their tax ID as applicable.
• Invoice details: A unique sequential invoice number (following a designated series, which cannot have gaps), the date of issue, and if different, the date of the taxable supply.
• Line item information: Description of goods or services, quantity, unit price, and any discount or rebate.
• Tax details: The taxable amount for each applicable VAT rate, the rate(s) themselves (standard 21%, reduced 10%, super-reduced 4%, or 0%), the corresponding VAT amount, and any relevant indication of VAT exemptions or reverse charge. For example, if no VAT is charged due to an exemption, the invoice should state “Exento según Artículo XX de la Ley del IVA” or if the reverse charge applies, it should include “Inversión del sujeto pasivo” as required by Spanish rules.
• Totals and currency: Total amount payable including VAT (and optionally the net total before VAT), typically in Euros (or other currency if allowed for the transaction).
• Additional content for special cases: If the invoice is a credit note or debit note (correction invoice), it must clearly be marked as such (e.g., “Factura rectificativa”) and reference the original invoice being corrected. If it’s a self-billed invoice, it needs the phrase noted above (“expedida por el destinatario”). If issued under the margin scheme or other special regime, the relevant legend (like “Régimen de bienes usados – IVA margin scheme” or “Agencias de viajes – IVA incluido conforme RD 1624/1992” etc.) should be included to signal that special treatment. Spanish rules also require invoices under the travel agency regime to include a statement that VAT is included under the special scheme, for instance.
• New unique identifiers and codes: Under the VERI*FACTU technical rules, each invoice (when generated by certified software) must embed a Unique Invoice Identifier Code composed of the seller’s NIF, the invoice series and number, and a timestamp, often realized as a secure hash. This code (sometimes called “UUID” or “encadenamiento del registro”) helps ensure that each invoice is traceable and unalterable in sequence. Additionally, invoices issued from a certified system carry a two-dimensional barcode (QR code) that encodes key data (e.g., the unique ID and a verification link) so that anyone (including the recipient or a tax auditor) can scan the code to verify the invoice’s authenticity against the official records.

The above requirements build on existing rules in Spain’s Invoice Regulation (RD 1619/2012), which has already incorporated e-invoicing provisions. For example, RD 1619/2012 was modified by RD 1007/2023 to include the requirement that when using a “verifiable” billing system, a QR code and an alphanumeric identification code must be included on the invoice. Moreover, the Ley Crea y Crece added that recipients must be given access to their e-invoices for at least 4 years – meaning suppliers either must keep the e-invoice available for download or use a platform where the buyer can retrieve it, without charging the buyer for that access.

4.2 E-Reporting Specifications (SII and VERI*FACTU): Under the SII model (currently in force for large businesses), companies electronically submit specified fields from each invoice to the AEAT’s online system. The SII XML schemas define the data points such as supplier and customer Tax IDs, invoice number and date, product description (optional summary), taxable amounts and VAT breakdown, and special indicators for transaction type (e.g., domestic sale, intra-EU supply, import, etc.). Each invoice reported via SII is categorized in one of several ledgers: sales, purchases, intra-Community operations, investment assets, etc., and certain additional fields like invoice correction references or import document numbers are included when relevant. The reporting timeline for SII is generally within 4 calendar days of the invoice event (issue or receipt), which is significantly faster than the old system of reporting only in the monthly/quarterly VAT return.

The VERI*FACTU (SIF) system introduces its own data format (often called the Registro de Facturación format) which includes not only tax data but also cryptographic and audit data. The October 2024 technical Order defined the content of these records and the interface for transmission. Each record will contain:

• All the standard invoice data (as described above, akin to what SII requires).
• Additional fields for the hash of the invoice and the hash of the previous invoice’s hash (to form a chain).
• Metadata such as an internal record ID, timestamp of creation, and software identification.
• Indicator of whether the invoice is being reported in VERI*FACTU (online) mode or just stored (offline mode). In online mode, the record is sent immediately; in offline mode, the record stays in the taxpayer’s system but can be later uploaded.
• If the invoice is a correction or cancellation, references to the original invoice (original number, date, etc.) and the type of correction.

If operating in VERI*FACTU (real-time) mode, the process is essentially that the software sends each invoice record to AEAT within seconds of issuing the invoice. The AEAT validates the structure and data (for example, checking that NIF numbers are valid, that required fields are present, and that calculations match VAT rates). Upon acceptance, the system may return a unique identifier and the data needed to generate the QR code for that invoice. Only after obtaining this confirmation would the issuer finalize sending the e-invoice to the customer (in a pure clearance model, the tax platform might even forward the invoice, but Spain’s model seems to be more flexible where the invoice can be delivered either through the platform or directly, as long as the tax copy is filed). If the data is rejected, the invoice would be considered not successfully issued, and the company must correct the errors and resend. Common validation errors might include formatting issues, arithmetic discrepancies, or incorrect coding of transaction types; the technical documentation lists error codes and their meanings and requires software to handle these responses.

In non-real-time (offline) mode, a company’s software must still produce the same invoice record with all the security features (hashes, digital signature, etc.), but instead of transmitting immediately, it stores them. The business may then be required to transmit these records in batch form periodically or upon a tax authority’s request. For instance, the AEAT could demand a full submission of a company’s invoice records for an audit, or the company might choose to periodically transmit them even if not in real time. The law ensures that the Tax Agency has a right to access these records. In both modes, digital signature or seal requirements are emphasized: if not transmitting in real time, the invoice record must be electronically signed or sealed to guarantee that no tampering occurred after issuance. If operating in VERI*FACTU mode, the real-time transmission and the AEAT’s own secure receipt can serve as the guarantee of authenticity, but the system still uses hash chaining for internal control.

Data model and fields for e-reporting: The invoice record data model (for VERI*FACTU) is closely aligned with SII, but expands to accommodate the new elements (like hash, software ID, etc.). It likely maintains mandatory fields such as those needed to populate a VAT return or ledger: e.g., identifiers for the parties, invoice specifics, tax details, and importantly the “Clave de operación” (code for type of transaction, which in SII indicates things like self-invoice, intra-EU supply, etc.). The requirement to report invoice status changes within 4 days – i.e. when an invoice is paid or if the buyer rejects it – is an innovation of the B2B e-invoicing system and effectively extends e-reporting to cover not just invoice issuance but also post-issuance events. This is separate from SII (which only captures issuance/receipt data, not payment status). It means the e-invoicing platform (public or private) will likely be used to capture when an invoice is marked as paid or if a buyer disputes it. Such status updates will also be transmitted to the AEAT or at least stored for verification. This intertwining of e-invoicing with payment tracking is an innovative aspect aimed at tackling late payment culture.

In summary, the technical requirements in Spain comprise two layers: (a) the format and content standards for the invoice itself (compliant with European norms and Spanish VAT law), and (b) the digital reporting and integrity controls around the invoice data (through SII or VERI*FACTU). The former ensures interoperability and automated processing, while the latter ensures the tax authority gets the data and that the data is trustworthy (unaltered). Businesses and software providers must pay attention to both layers to fully comply.

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

5.1 E-Invoice Corrections: Spain’s VAT legislation requires that once an invoice is issued, any correction of VAT-relevant errors (such as incorrect amounts, VAT rate, or other mandatory particulars) must be done via a formal corrective invoice (factura rectificativa). In practice, this means if an e-invoice was issued with a mistake, the supplier cannot simply modify that original invoice in the system without leaving a trace. Instead, the supplier must issue a new electronic document that references the original invoice and states the changes. A credit note or debit note can serve as a correcting invoice, provided it meets the requirements (it must have its own unique number and date, and a reference to the invoice being corrected). Corrective e-invoices should clearly indicate they are such (for example, include the term “Rectificación de factura” or use the type code for credit note/debit note in the e-invoice format). The corrections can either be in plus or in minus (a debit note if more VAT is to be charged, or a credit note if VAT is being reduced due to an overcharge or discount, etc.). The net effect is that the original invoice remains as issued, and the correction amends the record.

Under the new e-invoicing workflow, issuing a correcting invoice remains essentially the same process but digitally executed. If an incorrect e-invoice was already sent and perhaps even reported to AEAT, the supplier should issue a corrective e-invoice electronically:

• The supplier’s system would generate a new e-invoice (credit or debit) with reference to the original invoice number and reason for correction.
• That corrective e-invoice is delivered to the buyer (likely through the same platform or channel as the original).
• If using VERI*FACTU real-time reporting, the system will transmit the corrective invoice record to AEAT immediately, just like any other invoice. If offline, it will store the record (with hash linking it to the prior invoice’s hash in sequence). From a tax perspective, a credit note will adjust the taxable amount and VAT accordingly (and this will reflect in the VAT return or SII report for the period).
• The Spanish rules also allow an “aggregate” corrective invoice that fixes multiple invoices at once (commonly used for minor VAT rate adjustments or year-end discounts). Such a summary credit note must reference all the original invoices it corrects, and it too would have to be electronic and reported.
• If an e-invoice is cancelled entirely, a typical approach is to issue a full credit note for the same amount (effectively negating the invoice). Additionally, the VERI*FACTU spec requires a special cancellation record to be generated, linking to the original invoice’s record, to ensure there is a logged event of cancellation in the system’s audit trail.

Because each invoice (and correction) is uniquely identified and possibly transmitted to the tax authority, a corrected invoice will be a separate record that the systems link to the original. The tax authority, upon seeing a corrective invoice in SII or VERI*FACTU, will understand that the original was amended. Provided the correction is done properly (within the legal time limits – usually, errors should be corrected no later than the deadline for the annual VAT return unless they were discovered by that point, in which case a special late adjustment is made), no penalties apply for the initial mistake. It is considered a normal part of business to correct invoices occasionally, as long as the process is transparent and in accordance with the rules.

5.2 Corrections in E-Reporting (SII and VERI*FACTU): For the SII system, correcting an error in a submitted invoice record requires sending an electronic modification record. SII has specific functionalities for this – for example, if an invoice was reported with the wrong amount or tax detail, the company can submit an “A0” (annulment) or “A1/A2” (modification) record to either void the original entry or amend specific fields, depending on the nature of the error. There are deadlines: modifications should be made by the next VAT return due date, generally, and certain types of corrections (like those affecting VAT amounts) have particular procedures in the VAT law. In practice, SII’s electronic ledger can be updated, but the taxpayer must remember that the actual VAT due still hinges on what is reported in the VAT return, so any discrepancy needs aligning via an amended return if the filing has already occurred.

With VERI*FACTU, since it is closely integrated with the act of invoicing, corrections are handled by the software as part of the issuance process:

• If an invoice record was sent to AEAT with an error and got rejected, the invoice is not considered issued; the error must be fixed and the data retransmitted (likely with a new sequential invoice number if the original number was already used – precise guidance on whether the same number can be reused after a rejection is expected in the technical rules).
• If an invoice was accepted and later the need for a correction is discovered, then as described above, a new corrective e-invoice must be issued. The VERI*FACTU platform would then also get a record of that corrective invoice (and possibly an annotation linking it to the original).
• If an invoice needs to be canceled (voided) after issuance, the draft rules suggest creating a special anulaciones record or simply issuing a full credit note. Each event – original issue, any correction, any cancellation – is captured in the sequence of records (the hash chain ensures no gap in the record chronology).
• The taxpayer may also be required to notify the tax authority of the cancellation if using the offline mode (since no real-time update would otherwise occur). This could be done by transmitting the cancellation record when back online or when submitting periodic data.

Notably, the obligation for buyers to report invoice payment status or rejection is itself a form of “e-reporting” new to Spain. If a buyer rejects an invoice or makes a payment, they must log that event (likely through the same platform or software), and that information flows to the tax authority within 4 days. If a buyer needs to correct a mistakenly reported status (say they marked an invoice as paid when it wasn’t), we expect the platform will allow a rectification of the status report. This is a new aspect and the exact mechanism will be described in the technical instructions, but it could involve sending an updated status message or a cancellation of the prior status. Since these requirements are not in effect yet, businesses will need to watch for the final Ministerial Order and guidance on how to handle status updates and corrections.

In essence, error correction under the new system will be governed by the existing VAT rules (issue corrective invoices for errors in tax base or tax amount) combined with the digital reporting rules (submit the corrected record through SII/VERI*FACTU). Taxpayers should implement processes in their systems to promptly identify and correct errors, and to ensure that any correction in the invoice or its status is mirrored in the data reported to authorities.

6. Transmission & Workflow

6.1 Channels for Sending E-Invoices and Data: Spain’s B2B e-invoicing model uses a “hybrid clearance” approach that involves both direct exchange between supplier and buyer and a central repository for tax data. Businesses will have two primary options to transmit e-invoices:

1. Accredited Private Platforms – Companies can use private e-invoicing service providers or in-house software that meets the interoperability and certification requirements. Such platforms must be capable of sending and receiving invoices in the approved formats and must interconnect with other platforms. An invoice issued on one platform should reach a buyer on another platform seamlessly, without forcing any trading party to use a specific provider. This likely entails use of common standards (e.g. PEPPOL access points or similar) and agreements among providers to exchange data.
2. Free Public Platform (AEAT’s system) – The Spanish Tax Agency is developing a central platform that any business can use at no cost. This public platform will serve both as a means to issue/receive e-invoices (particularly useful for small businesses that may not want a private provider) and as a central hub for collecting invoice data for the tax authority. In fact, even invoices exchanged via private platforms must be copied to the AEAT’s system: the RD 238/2026 introduced the concept of a “copia fiel” (faithful copy) of each invoice that the issuer must send to the central platform if a private channel was used. This ensures the tax authority obtains the core data of every invoice. (It’s not yet clear if the private platforms themselves will handle sending this copy to AEAT automatically on behalf of the taxpayer, or if the taxpayer must do it. The likely scenario is that certified platforms will be integrated with AEAT such that the copy is forwarded behind the scenes.)

This “clearance-like” mechanism means that even when using a private platform, the invoice data ends up in a government-controlled repository. It is analogous to models in countries like Italy, where all B2B invoices pass through a government system. However, Spain’s approach might not be purely centralized: the actual routing of the invoice could be point-to-point between businesses (especially via PEPPOL or email with attachments, etc.), as long as the data copy goes to AEAT. Details on the exact workflow will be in the technical Order, but the general principle is that the Tax Agency gets the data in near real-time, either directly from taxpayers’ software (VERI*FACTU) or via the “copia fiel” from platforms.

For e-reporting under VERIFACTU, the transmission is either integrated into the above workflow (for VERIFACTU mode, the invoice data goes straight to AEAT in real time), or done later (for offline mode, data is exported and transmitted on request). In either case, all systems must be able to communicate with the AEAT. The interface is expected to be via APIs or web services using XML/JSON payloads as defined by AEAT’s schemas, over secure internet connections. Spain’s AEAT already runs robust web services for SII and will extend similar services for VERI*FACTU. The public platform may also allow direct portal usage for very low-volume users (e.g., manually keying in invoice data into a web form that generates a compliant e-invoice).

6.2 Timing of Transmission (Real-Time vs Deferred): The new B2B e-invoicing rules introduce some specific deadlines for sending invoices and related data:

• Issuing & delivering the e-invoice to the customer: The law doesn’t explicitly change the fundamental rule that invoices should be issued at the time of the taxable supply or shortly thereafter (current VAT law mandates issuance by the 15th of the month following the month of supply at the latest, for most transactions). Under an ideal e-invoicing scenario, invoices will be issued and delivered essentially immediately in digital form. If using the public platform or a platform that acts as a delivery network, the transmission to the buyer should be near-instant once the invoice is finalized. Some sources suggest that Spain might implement a requirement akin to clearance for B2B: one early proposal in 2023 mentioned that the supplier might need to send the invoice to the tax authority first for validation, then the buyer receives it. However, the model described in the final decree and drafts leans toward a simultaneous or parallel submission (supplier sends invoice to buyer and a copy to AEAT around the same time). It’s clear that in any case, a copy of the invoice must reach the AEAT’s system within a short window. The VAT Law (as modified by Ley Crea y Crece) will likely deem an e-invoice as delivered when it’s accessible to the recipient on the platform, rather than when an email is sent, but the exact legal definition will be in the regulations. [marosavat.com]
• Real-Time Tax Reporting: If using VERI*FACTU online mode, the requirement is effectively real-time. The draft SIF regulations indicated an expectation that data be transmitted “in continuous, automatic, and immediate” fashion, with a tolerance of perhaps a minute or two after issuance. This is far more stringent than SII’s 4-day rule, moving to a true continuous control. (It is comparable to the approach in countries like Mexico or Italy where invoices pass through a government platform instantly.) [vatupdate.com]
• Near-Real-Time/Periodic Reporting: For those not in VERI*FACTU mode, the law does not yet impose a fixed periodic submission (aside from existing SII participants’ 4-day rule). It’s conceivable that if many choose the offline mode, the tax authority may establish a periodic upload requirement to avoid accumulating unsent data. But currently, the focus is on real-time or readiness for on-request submission. Therefore, aside from invoices and statuses (acceptance/payment) that must be reported within 4 days of the event, there isn’t a new monthly or quarterly “summary” report introduced for e-invoicing – since the entire point is that the invoice is the report (or generates the report to AEAT).
• Other periodic obligations: Traditional Spanish VAT obligations like the Modelo 347 (annual summary of transactions > €3,005 with each customer/supplier) might be rendered obsolete for those under complete e-invoicing and e-reporting, as the tax office would already have that info. Indeed, since the introduction of SII, taxpayers in SII were exempted from filing the 347 form. It is expected that once e-invoicing is universal, Spain will phase out some of these redundant declarations.

Sending to tax authorities vs to buyers: Under the upcoming regime, the act of sending an invoice to the buyer and to the tax authority can be separate or combined. In some designs, the central platform might act as a postbox: the supplier sends the invoice to the platform, which then forwards it to the buyer (this is closer to a clearance model). In others, the supplier sends to the buyer directly (or via its chosen platform) and just sends a copy to the tax authority’s system. Spain’s description suggests that as long as the data copy is lodged with AEAT, the actual delivery can be via any agreed channel. The critical requirement is that the tax authority isn’t left waiting until a VAT return to see the transaction – they will have near-immediate access to the data.

Deadlines for buyers (invoice status reporting): A new element is that buyers have to report back on the invoice’s status (accepted/rejected) and payment date. The law and RD indicate a general deadline of within 4 business days of the event (acceptance, rejection, or payment) for buyers to report these statuses. This mirrors SII’s 4-day window, but applied to events after invoice receipt. If, for instance, a buyer receives an e-invoice and disputes it, they would mark it as “rejected” on the platform within 4 days of the decision to reject; if they pay it on a certain date, they log the payment date within 4 days after payment. These reports, too, become part of the record accessible to the tax authority (and presumably visible to the supplier). This requirement will add a new dimension to invoice processing for businesses, who need to ensure their accounts payable or receivable teams update invoice statuses promptly on whatever system they’re using.

In summary, the Spanish system’s workflow is designed to ensure that every B2B invoice is recorded in a central data pool and that key post-issuance events are captured. Businesses can comply by either using a government portal or certified private solutions, but in all cases data flows to the AEAT. The system has elements of clearance (due to required data submission and the possibility that the central platform plays a role in delivery), but it is somewhat more flexible than a pure clearance system, since businesses can choose their platform and exchange method as long as interoperability and data submission rules are met.

7. Self-Billing

7.1 Permissibility and Requirements: Spain allows self-billing, which is when the invoice for a sale is issued by the customer (buyer) rather than the supplier, typically under a prior agreement. This is recognized by Spanish VAT law in line with EU rules. Self-billing is used in certain industries (e.g. agricultural cooperatives, construction subcontracting, or commission arrangements) and is also required in some cases (like reverse factoring situations or when a public body issues invoices on behalf of a supplier). Under current rules, self-billed invoices must contain all standard invoice data and must include a statement such as “Factura expedida por el destinatario” (invoice issued by the recipient) to clearly denote the self-billing scenario. The supplier must accept each invoice for it to be valid, which is often handled through the initial agreement or by confirming each self-billed invoice. [vatupdate.com]

When the e-invoicing mandate takes effect, self-billing will continue to be allowed but must itself be done electronically if the transaction is B2B and in scope. The responsibility for e-invoicing and reporting in a self-billing context falls primarily on the buyer (the issuer of the invoice). For example, consider a large retailer (buyer) who self-bills small suppliers for efficiency: the retailer’s e-invoicing system would generate the structured e-invoice and send it to the supplier (perhaps via the public platform or a chosen private platform) and, in parallel, ensure the invoice data is lodged with the AEAT (either via SII, VERIFACTU, or by sending the “copia fiel” to the central platform). The supplier, if also subject to e-invoicing, would not need to issue a duplicate invoice – the self-billed invoice suffices for both parties’ records. One challenge can be the buyer-side reporting of such invoices: under SII, the supplier (if under SII) reports self-billed invoices in its sales ledger; the buyer reports nothing in its purchase ledger because it issued the invoice instead of receiving one. Under VERIFACTU, a similar logic likely applies: only one side reports the invoice to the tax authority (to avoid double counting). The Spanish draft rules indicate that if a transaction is subject to legal third-party billing (including self-billing) and the supplier is already under SII, that supplier does not have to additionally adopt VERI*FACTU for those invoices. Conversely, if neither party is under SII, one of them will be responsible for ensuring the invoice is recorded in a SIF-compliant system (most likely the self-biller, since that party’s software actually creates the invoice). [vatupdate.com]

7.2 Use of the E-Invoicing Platform and Approvals: Self-billed invoices will be handled through the same e-invoicing platforms. The buyer (as issuer) might use the public platform or a private platform to issue the invoice. The supplier (as recipient) will receive the e-invoice via the platform and should acknowledge or “accept” it. The upcoming regulations on the public platform likely will include a mechanism for a seller to reject a self-billed invoice if it’s incorrect, akin to the general invoice status reporting. Because self-billing inherently requires supplier approval, the e-invoicing system’s “acceptance” flag may double as that approval mechanism – if the supplier does not accept a self-billed invoice, that could be indicated as a rejection on the platform, prompting a corrected self-billed invoice.

7.3 Special Content Rules and Notifications: The content of a self-billed e-invoice must comply with the standard fields and include the mention that it’s self-billed. No additional fields solely for self-billing have been specified in the technical schema, other than existing ones (the seller and buyer fields will essentially be reversed in a self-billing scenario, since the seller’s details will appear in the “customer” section and vice versa, or a flag might identify the invoice as self-billed). Spanish law doesn’t require prior notification to the tax authority to use self-billing; it’s a private arrangement, albeit one that must meet certain conditions. That remains the case – no new pre-approval is needed for self-billing under the e-invoicing rules. The main requirement is that the self-billing agreement must be in place, and both parties must comply with the e-invoice requirements. [vatupdate.com]

In summary, self-billing is compatible with Spain’s e-invoicing framework. The practical effect is simply that the buyer’s system issues the invoice. Both supplier and buyer benefit from this being electronic – the supplier gets the invoice data for their records, and the buyer can streamline its purchasing process. With the new systems, the buyer will likely fulfill the role of transmitting the invoice data to the tax authority as well. Businesses engaged in self-billing should ensure their agreements cover the new procedures (e.g., that the self-biller will use compliant software and handle the necessary reporting).

8. Triangulation & Special Scenarios

8.1 Triangulation and Chain Transactions: Spain’s e-invoicing rules apply to domestic transactions between Spanish businesses, including those that are part of a triangular or chain arrangement as long as each leg of the transaction is domestic. For example, consider a three-party chain in Spain (A sells to B, B sells to C, with one shipment from A to C). A must issue a Spanish e-invoice to B, and B must issue a Spanish e-invoice to C. Each invoice will be subject to the e-invoicing and reporting requirements once in effect. The law does not provide an exemption for these invoices. The treatment of triangulation in the EU context (where one leg of the transaction is cross-border) has already been mentioned: the Spanish part is subject (if any party is Spanish), but pure cross-border legs are not. Spanish companies participating in EU triangulations will continue to use existing VAT rules (issue an invoice without VAT to the EU buyer, with a note about Article 141 of the VAT Directive if applicable, etc.), and they will likely report these in SII or in their periodic returns as required, but not via the domestic e-invoice platform since the customer is foreign.

Chain transactions wholly within Spain (including drop shipment scenarios inside the country) are straightforward: each transfer of ownership needs an invoice, which must be electronic in B2B. If goods are delivered directly from the first supplier to the final buyer at the intermediate seller’s request (a domestic drop shipment), Spanish VAT law already treats the intermediate seller as making a supply to the final buyer (often with local VAT unless another rule like simplification applies), so that invoice from the intermediate to the final buyer will be an electronic invoice and reported.

8.2 Reverse Charge and Cross-Border Considerations: For cross-border B2B services or goods where Spanish VAT is accounted for via the reverse charge (e.g., a German company provides a service to a Spanish business, which must self-account for Spanish VAT), the invoice issued by the non-resident supplier is outside the Spanish e-invoicing system (the German supplier follows the invoicing rules of its country or the general EU rules). The Spanish recipient, however, is obliged under current law to create an internal document (self-invoice, autofactura) as evidence of the transaction for Spanish VAT purposes if the supplier is not established in Spain. If the Spanish company is on SII, it reports that self-invoice in the issued invoices ledger (with a special code indicating it is self-billed). Under VERI*FACTU, the Spanish recipient will similarly need to ensure that such self-invoices are recorded in their certified system; presumably, the software will allow issuance of self-invoices labeled accordingly, and their details will be part of the invoice records (with a flag for self-billing) either stored or transmitted. The key point is that incoming cross-border invoices do not need to be in Spanish e-invoice format. But the Spanish taxpayer’s interaction with that invoice (like deducting VAT or self-assessing VAT) is captured through domestic reporting (VAT returns, SII, etc.). [vatupdate.com]

Zero-rated and VAT-exempt supplies inside Spain (e.g., certain inter-city passenger transport at 0% VAT, exports at 0%, medical services exempt, etc.) are not carved out of the e-invoicing requirement if an invoice is issued between businesses. They will be e-invoiced and reported just like taxed supplies. The only difference is that the invoice will show a 0% rate or an “Exento” indication and cite the legal reason for no VAT. Systems and formats will accommodate these scenarios (for instance, EN 16931’s data model includes codes for VAT exemptions and reverse charges).

One special scenario: Intra-company transactions (between a parent company and its subsidiary) are generally subject to the same invoicing rules as any B2B transaction if a VAT-able supply occurs. Thus, if a Spanish parent company charges its Spanish subsidiary for a service, a VAT invoice is needed and would fall under the e-invoicing mandate. If it’s merely an internal movement of goods within the same legal entity (not a sale), that’s not an invoice scenario. The e-invoicing law does not change the definition of what needs an invoice; it only changes the format and process for those that already did.

Summary of special scenarios: Spanish regulations aim to ensure no major gaps: domestic B2B flows are covered. Cross-border and purely consumer-facing transactions remain outside this specific mandate, but other obligations cover them. Triangulations and chain transactions are dealt with through existing VAT rules, with their invoices being electronic if Spanish B2B. The framework is intended to be comprehensive yet avoid overlap: e.g., SII vs VERI*FACTU, B2B vs B2C vs cross-border, etc., each category has one system or rule that applies. Businesses should map out their transaction types to see which fall under which system.

9. Archiving & Retention

9.1 Mandatory Archiving Formats and Periods: Spain requires that invoices be archived in their original format for the legally required retention period. For tax (VAT) purposes, invoices must generally be kept for at least 4 years after the tax year in which they were issued or received, as this is the statute of limitations for tax audits. However, other regulations (e.g., commercial code) extend the general requirement to 6 years for accounting documents, and many companies use 6 years as a baseline to cover both tax and corporate record-keeping needs. In practice, companies tend to keep VAT records for 4+ years; for safety, many retain 6 years or more. Some specific cases demand longer retention: for example, invoices related to fixed assets or capital goods (which have multi-year VAT adjustment periods) and certain intra-Community supplies must be kept for 9 years in Spain, as adjustments could occur in that timeframe. The new e-invoicing law itself (Ley 18/2022) introduced a requirement that providers of e-invoices must ensure access for customers for 4 years, meaning practically they need to archive the e-invoice (or have it accessible via a platform) for that period.

For electronic invoices, the law stipulates they should be stored in their original electronic form. Simply printing them out and storing paper copies is not enough to satisfy legal requirements. The electronic archive should preserve the integrity and authenticity of the invoices. Typically, this is done by storing the exact original file (e.g., XML) along with any electronic signatures or hashes that were applied, and maintaining a system that prevents or detects any alteration. The RRSIF (billing software regulation) explicitly requires that the invoice records be kept with digital signatures or hash codes that link them in a sequential chain, and that any export of those records for audit must include verification of their integrity. In the VERI*FACTU online mode, since the data is sent to AEAT, the tax authority’s copy can serve as a reference. However, the business still needs to keep its own copy of the e-invoice.

9.2 Location of Storage (Local vs Cross-Border): Spanish companies can choose to store their e-invoices on local servers or use cloud storage, and they can also engage third-party archival services. If the storage is done outside Spain, EU regulations and Spain’s rules require that data storage in another EU country is acceptable as long as the data is accessible to the tax authorities online and without undue delay. Storing invoices in a non-EU country is more problematic; Spanish rules require that there be a reciprocal tax assistance arrangement with that country (or some form of notification to AEAT) if using servers outside the EU to store tax-relevant data. Many companies choose to store invoices within the EU to avoid legal uncertainty. The AEAT must be given access to the electronic archive upon request, typically by granting them user access to the system or by exporting the records in a standard format (like the XML ledger format) and providing them electronically. With the new systems, it’s likely that AEAT could remotely audit invoice records, especially if they have already been receiving them in real time. But the taxpayer’s duty to maintain their own records persists.

9.3 Ensuring Readability and Integrity: During the retention period, the invoices must remain readable (both in their raw form and to human-readable form on screen or paper if needed) and cannot be altered. The combination of digital signature requirements and hash chaining (for VERI*FACTU) is aimed at guaranteeing integrity. Authenticity is ensured by the use of the taxpayer’s digital certificates for signing or sealing the invoices, or by the controlled transmission via the tax authority (which can be seen as a form of clearance authenticity). Spanish law has for years recognized electronic storage with certain conditions: businesses must be able to reproduce the invoices in a legible format and ensure that the data they contain is complete and unmodified. The standard for e-signatures used (XAdES for Facturae, or other advanced/qualified signatures) provides a cryptographic seal that can be validated even years later as long as the certificate is valid or time-stamped. Companies should keep those validation tools in mind (or rely on third-party archiving services that manage signature validation over time).

Another aspect is audit accessibility: The tax administration can request specific invoices or entire datasets. With SII, they mostly already have the data but might request to see the actual invoices or any related documents during an inspection. Under VERI*FACTU, the authorities could potentially have a real-time mirror of the invoices (if sent online) or they might request an export of the records if not. The taxpayer is obligated to comply quickly. Typically, auditors might ask for the data on a CD, or secure transfer, or even direct system access. Given the high detail in e-invoice records, audits may become more focused on discrepancies rather than basic data gathering.

In conclusion, businesses must plan for long-term electronic archiving. Ensure your e-invoicing solution either includes an archiving module or integrates with a compliant archiving system. Check that it can store the original invoice files with all necessary metadata, that it supports retrieval and human readability on demand, and that it meets the requirements for security (no editing without trace) and location (preferably EU-based servers or duly notified alternatives).

10. Penalties & Enforcement

Spain’s legislation has set out a series of penalties to encourage compliance with both the e-invoicing mandate and the anti-fraud software requirements. While some of these penalties are already law, they will be applied once the respective obligations kick in (e.g., B2B e-invoice fines will apply after the mandate is effective, and software-related fines from 2027 onward for non-compliance). Key sanctions include:

• Failure to issue or provide e-invoices (B2B transactions): Under Ley 18/2022, if a seller that is obligated to use e-invoicing fails to do so, or if a recipient who is obligated to accept e-invoices does not comply (e.g., a buyer refuses to accept a valid e-invoice, or a supplier does not provide the required access to the e-invoice), the infringing party can be fined up to €10,000 per incident. This is targeted at ensuring compliance with the B2B e-invoicing requirement and the obligation to allow customers to download their invoices for four years. However, this fine will only be enforceable once the B2B mandate is active for the respective business (no one will be fined under this provision before 2027–2028 when the mandate phases in). The law also provides a 6-month “grace” from these particular fines after the mandate’s start, during which non-compliance should be rectified without penalty if it’s a first-time oversight.
• Using non-certified invoicing software (breaching VERI*FACTU rules): Under the General Tax Law (Article 201 bis introduced by Law 11/2021), any use of software or systems that allow keeping undetectable accounts or fail to comply with the SIF requirements is a serious violation. The penalties for this are significant: up to €50,000 per year for the company using such software, and up to €150,000 for the developer or vendor supplying non-compliant software. These fines reflect the importance of having all businesses use only approved, verifiable billing systems. Starting 2027, if a company continues using an old invoicing program that doesn’t meet the criteria (e.g., doesn’t generate the required hash or QR code, or allows deletion of invoices without trace), they could incur these fines. The tax authorities have been actively informing software developers of the certification requirements to prevent this scenario.
• Late or inaccurate reporting of invoices (E-Reporting penalties): The existing regime under SII treats late submissions or errors in submissions as infractions. The standard penalty is 0.5% of the invoice amount for each invoice not reported on time or correctly, with minimum €300 and maximum €6,000 per quarter for each ledger. If an invoice is missing entirely from SII, the fine can be 1% of its amount (with similar minimum/maximum caps). We expect a similar approach for VERI*FACTU: an invoice not transmitted in real time might be considered an “unreported” invoice if discovered by an audit, potentially subject to penalties. Also, not reporting the status of an invoice (acceptance/payment) within the required timeframe could be penalized, though this is a new area – the exact fines might be clarified in the Ministerial Order or subsequent tax regulation updates. Spanish tax law allows penalties for failure to comply with “formal obligations” such as bookkeeping or reporting; these can range from fixed fines to proportions of the omitted amounts, depending on severity.
• Failure to maintain proper archives or tampering with records: If a business does not keep its invoices (including e-invoices and their digital records) for the required period or if it is found to have altered or deleted invoice records in violation of the inviolability requirements, it can face penalties. Under Article 201 of the General Tax Law, a general failure to comply with invoicing obligations (like not issuing an invoice when required, or not keeping copies) is a minor offense with penalties starting around €150 per missing or flawed invoice, with an upper limit that can reach €60,000 per year for repeated defaults. More serious cases (like deliberately hiding sales) can qualify as tax evasion and lead to much larger fines or even criminal charges if tax is unpaid. The new e-invoicing system, by design, makes such fraud harder to conceal.

10.1 Enforcement Approach: Spanish authorities (AEAT and other relevant bodies) are expected to enforce these obligations through audits and automated checks. The AEAT’s immediate access to invoice data (via SII/VERI*FACTU) means discrepancies can be flagged quickly – for instance, if a buyer reports an invoice it received but the seller never reported issuing it, or if an invoice is declared in a VAT return but not found in the e-invoice repository, that could trigger a review. Also, the requirement for software certification might be checked during tax inspections or even via remote system audits. The government has indicated in press releases that these measures are meant to fight fraud, implying a serious stance on compliance. However, they also emphasize the benefits and are likely to give guidance and support in the initial phase. Notably, because the new rules are complex and require new technology, enforcement may initially focus on willful non-compliance (e.g., companies refusing to implement any system) rather than penalizing minor technical glitches. Still, by 2027–2028, businesses should be fully prepared; expecting leniency beyond the official grace periods would be risky. As always, maintaining good records of compliance efforts (e.g., documentation from software providers about compliance, records of invoices and their submission receipts) will be prudent in case of any disputes with the authorities.

11. Pre-Filled VAT Returns

11.1 Current Status of Pre-Filled Returns: Spain has introduced a system of draft (pre-filled) VAT returns for taxpayers, leveraging the data it collects through e-reporting. Currently, through the Pre303 program, the AEAT provides a proposed VAT return (Modelo 303) for each filing period, especially for those using SII or that have certain informative forms on file. This draft includes known information such as the taxpayer’s identification details, certain pro-rata or industry-specific adjustments, and aggregated totals of sales and purchase data if available. For large companies on SII, the AEAT already has detailed data of each invoice, so the Pre303 draft often pre-fills many fields (like total output tax, total input tax, etc.) based on the SII submissions. Taxpayers are expected to review and, if necessary, correct or complete these drafts before finalizing their returns. As of now, the Pre303 is an optional aid—taxpayers remain responsible for accuracy and can disregard the draft if they believe it’s incomplete.

11.2 Future Developments – “VAT return in draft” using E-Invoicing Data: The expansion of e-invoicing and e-reporting to all businesses will dramatically increase the data the AEAT holds, thus enhancing the scope of pre-filled returns. The Spanish Tax Agency has indicated that the e-invoicing mandate and VERI*FACTU data will feed into the Pre303 system, allowing more fields to be pre-populated. The vision is that eventually, the VAT return could be almost entirely pre-filled, and the taxpayer would just need to verify and submit it, much like the experience employees have with Spain’s drafted income tax returns. However, even in that scenario, certain fields might still require confirmation or manual input (e.g., adjustments for bad debt relief, pro-rata calculations for partial exemption, etc., which the tax agency might not automatically know).

At the moment, pre-filled VAT returns coexist with the traditional system:

• Taxpayers not in SII (which is the majority currently) only get limited pre-filling (mostly prior data carryovers).
• Taxpayers in SII get more extensive drafts, but still need to confirm them.

In the future, once all invoices are electronic and reported, Spain could possibly eliminate some manual VAT return tasks or even replace the periodic returns with continuous reporting plus a confirmation process. The initial step will likely be that for each quarter (or month for large businesses) in 2028 and beyond, the Modelo 303 will be pre-filled with totals of sales, purchases, import VAT, export data, etc. drawn from the e-invoice repository. Taxpayers would then only report things not captured by e-invoices (like certain import VAT adjustments or self-assessments) or confirm the numbers. There is no official commitment yet to eliminate the VAT return entirely, but pre-filling is already happening and will be extended. As of now, there is no direct link between e-invoicing and an “automatic” filing; it’s about assistance to the taxpayer. But some EU countries (e.g., Italy) have started using e-invoice data to populate periodic VAT reports, and Spain is heading in that direction as well, especially given the synergy with the EU’s plans for digital reporting.

The viability of pre-filled returns for all taxpayers is one of the selling points of e-invoicing: by reducing errors and administrative work for businesses, it partially offsets the burden of compliance. As early as 2020, Spanish tax officials launched projects to use SII data for draft returns (the “Pre303” system) and stated intentions to expand it broadly. By the time the B2B e-invoicing is fully rolled out, we can expect that almost every VAT registrant’s return will come pre-populated with data. Taxpayers will still need to review these pre-filled returns carefully, because any data not captured by an invoice (for example, certain adjustments or special scheme calculations) would have to be added manually.

11.3 Current vs Planned Pre-Filled Fields: At present, fields that can be pre-filled include identification info, previous period credits, and in some cases the total output VAT and input VAT based on SII data. Fields that typically require manual input include those related to special regimes, pro-rata adjustments, and any operations that were not reported through SII (e.g., transactions that are outside SII’s scope like simplified invoices, if any). With universal e-reporting, the aim is that the tax office will have virtually all the data points (normal sales, reverse charges, exempt sales, etc.), to pre-fill:

• Taxable bases and VAT amounts for each rate.
• Total VAT due, total deductible VAT, and resulting payment or refund.
• Perhaps details on intra-EU sales (which currently go into a separate form 349 but could be integrated).
• If invoice status reporting is robust, possibly an indication of which invoices are still unpaid (though that might be more for enforcement than return prep).

No pre-filled return system is in effect by law (i.e., taxpayers still have to file returns), but these initiatives show the trajectory.

12. Impact on SMEs and Startups

12.1 Affected Population and Phased Onboarding: Small and medium-sized enterprises (SMEs) and startups form the majority of businesses in Spain, and they are a key focus of the e-invoicing initiative. Policymakers see long-term benefits for SMEs (like faster payments and reduced admin costs), but they also acknowledge the short-term challenges. To ease the impact:

• The implementation of mandatory B2B e-invoicing gives SMEs an extra year compared to large companies. As discussed, while large businesses must comply by Oct 2027, smaller firms have until Oct 2028. This phased approach allows more time for SMEs to adjust. [zerocoma.com]
• The government is providing a free e-invoicing platform through AEAT, specifically to support small businesses and freelancers who might not want to invest in a private solution. This platform will enable basic invoice issuance and receipt at no cost.
• Financial support programs like Kit Digital provide subsidies for digital tools (including e-invoicing software) to companies below 50 employees, using EU recovery funds. This can offset the cost of acquiring or upgrading a compliant system.
• Extensive guidance and outreach are being undertaken. The government and industry associations are releasing guides, FAQs, and organizing seminars for SMEs. The importance of starting early has been emphasized in communications by both public officials and professional advisors. [docuten.com]

12.2 Compliance Costs and Operational Impact: SMEs will need to invest in technology and possibly training or consulting. Upfront costs could include:

• Purchasing or upgrading an accounting/billing software that is VERI*FACTU-certified.
• Adapting current ERP or billing processes to integrate with e-invoice formats and possibly the AEAT’s system.
• Implementing digital signature solutions if not already used (for example, obtaining a digital certificate from FNMT for sealing invoices, if needed).
• Employee training on new invoicing procedures and handling of incoming/outgoing e-invoices, including how to deal with status updates.

There will also be ongoing costs such as software subscription fees (if using a private platform or solution), and possibly fees for use of service providers or for outsourcing compliance. Some analyses from business groups have voiced concerns that these costs could be burdensome, especially for microenterprises. On the other hand, many vendors are offering low-cost solutions and even free tiers (with limited invoice volumes) anticipating the SME market.

Benefits and efficiencies: In the medium to long term, SMEs should see some benefits:

• Reduced payment times: Because the e-invoicing mandate is part of a broader push against late payments. The requirement for large companies to report when they pay invoices is intended to shame or penalize chronic late payers. SMEs may thus experience faster payment cycles from big customers once the system is monitored by authorities. Also, with an integrated e-invoice system, an SME can more easily track outstanding invoices and send reminders.
• Process automation: Using a digital invoicing system means data flows directly into accounting systems, reducing manual data entry and errors. This could save time on accounts payable/receivable processes. The Ministry of Economy highlighted potential cost savings of over €8 billion annually for Spanish businesses when e-invoicing is fully adopted, citing Italy’s experience in reducing processing costs per invoice. SMEs stand to gain a proportionate share of these savings in reduced administrative burden.
• Tax compliance simplification: With automatic reporting of invoices, SMEs may have less to compile for their VAT returns. Also, the risk of mistakes on VAT returns should decrease if the underlying data is consistently reported and validated. This can reduce the chance of audits or penalties for errors.

12.3 Challenges and Risks for SMEs: Despite the benefits, there are concerns:

• Readiness: Surveys as recent as 2025 indicated that many SMEs were either unaware of the upcoming requirements or had not begun preparations. If smaller businesses leave implementation until the last minute (mid-2028), they could face significant difficulties. This is why experts urge starting the transition now and using the extra year proactively. [docuten.com]
• Resource constraints: Unlike large companies, SMEs may lack IT departments or budgets for new software. They might rely on basic invoicing tools or even spreadsheets. Transitioning to a new system can disrupt operations. To mitigate this, many SME-targeted solutions are emerging that promise easy compliance (some are cloud-based with simple interfaces). The government’s free solution is also aimed at microbusinesses with minimal invoices.
• Interoperability issues: If an SME deals with a large number of trading partners, each possibly using different e-invoicing platforms, there could be initial confusion. The legal requirement for interoperability is meant to address this, but technical hiccups could occur during the early stages. Imagine an SME trying to send an e-invoice to a customer but not knowing which platform the customer uses; the law implies the invoice should find its way via the central platform or through inter-platform connectivity. Testing these connections will be important.
• Learning curve: Staff will need to learn how to operate the new systems, how to handle error messages from the tax authority, how to perform corrections and status updates electronically, etc. There could be temporary increases in workload or need for external support during the adjustment period.

12.4 SME-Specific Provisions: The regulatory design has considered SMEs in a few ways beyond timing and support:

• Simplified Regime Exclusion: As noted, very small businesses under the simplified VAT scheme aren’t required to implement VERI*FACTU initially. However, if they grow or leave that regime, they’d fall under the rules. [kpmg.com]
• No fees for using the basic infrastructure: Interoperability and the free platform ensure that an SME can comply without recurring costs. The law prohibits charging SMEs for the basic ability to send/receive invoices or to use the public system.
• Phased enforcement: The timeline itself is a key concession to SMEs. Also, authorities may introduce sector-specific outreach – for example, special attention is being given to industries where average company size is small (like hospitality, retail) to ensure they get the message and have the tools. There’s discussion in the press about whether microenterprises could even see a further extension if needed, though none is guaranteed yet.

12.5 EU and Government Assessments: At the EU level, impact assessments around e-invoicing (as part of ViDA) acknowledge that smaller businesses face higher relative costs to implement digital compliance. However, they also project long-term net savings and reduced VAT gap leading to fairer competition. The Spanish government’s estimation in the press release was that, once fully implemented, e-invoicing could save Spanish businesses billions of euros annually in reduced administrative costs and faster VAT refunds. For SMEs specifically, early adoption might yield some immediate advantages: for example, an SME that starts e-invoicing can integrate with accounting and perhaps avail itself of invoice financing or factoring more easily, since digital invoices can be shared with financial institutions to secure loans. The Ministry of Economy’s statements emphasize that this reform is pro-SME in its intent (curbing late payment which hits small businesses hardest, and reducing paperwork). Nonetheless, SME advocacy groups will be watching how the implementation proceeds and may lobby for adjustments if the burden becomes too high. The success of the rollout will depend on how well the tools function and how user-friendly they are for a non-technical business owner.

13. Official References

Below is a selection of authoritative sources that provide further detail and confirmation of the Spanish e-invoicing and e-reporting framework:

• Legislation and Official Gazette Publications:
  • Law 18/2022 (Ley “Crea y Crece”) – Article 12 of this law (in force since 19 Oct 2022) establishes the obligation for businesses and professionals to use electronic invoicing in B2B transactions, subject to future regulatory implementation. (BOE reference: BOE-A-2022-16207)
  • General Tax Law (Law 58/2003) as amended by Law 11/2021 – Introduced Art. 29.2.j) requiring the use of tamper-proof billing systems and disallowing software that permits data manipulation, as part of anti-fraud measures. Also introduced new penalty provisions (Art. 201 bis) for using non-compliant software.
  • Royal Decree 1619/2012 (Spanish VAT Invoicing Regulation) – Lays down detailed invoice content requirements and special invoicing regimes (e.g., simplified invoices, self-billing). It was amended by later regulations to accommodate e-invoicing (e.g., adding requirements from 2024 for QR codes on invoices generated by certified systems).
  • Royal Decree 596/2016 – Established the SII VAT immediate information supply system from 2017, making relevant changes to the VAT Regulation (Reglamento del IVA) to require electronic submission of invoice records by certain taxpayers. [vatupdate.com]
  • Royal Decree 1007/2023 (5 Dec 2023) – Enacted the Regulations on Billing Software Requirements (RRSIF) under Law 11/2021. It defines technical specifications for billing systems (SIF), and clarified that the VERI*FACTU system would offer both real-time and deferred modes for compliance. It also updated RD 1619/2012 to support the new e-invoicing environment (e.g., requiring additional info on invoices).
  • Ministerial Order HAC/1177/2024 (17 Oct 2024) – Issued by the Ministry of Finance, this Order provides the technical and functional specifications for the SIF/VERI*FACTU system. It includes schema definitions for the invoice record data, rules for generating the unique invoice identifier and QR code, and specifics on communication with AEAT’s systems.
  • Royal Decree 254/2025 (1 Apr 2025) – Delayed the initial VERI*FACTU deadlines to 2026 and confirmed that SII participants remain exempt from SIF obligations even when they issue invoices via third parties by legal mandate. [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
  • Royal Decree-Law 15/2025 (2 Dec 2025) – Further postponed the SIF/VERI*FACTU go-live to 2027. This decree-law (having immediate legal force) sets the adaptation deadlines: 1 Jan 2027 for corporate taxpayers (and PEs) and 1 July 2027 for others. [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
  • Royal Decree 238/2026 (approved 24 Mar 2026, published 31 Mar 2026) – Implements the B2B e-invoicing mandate of Law 18/2022. It outlines the main features of the system (scope, requirement of structured format, invoice status reporting, interoperability) and delegates to a coming Order the technical details.
  • Draft Ministerial Order on B2B E-Invoicing (circulated 17 Apr 2026) – In public consultation as of April 2026. Crucially, this draft Order proposes an effective date of 1 Oct 2026, which would activate the timeline for mandatory B2B e-invoicing on 1 Oct 2027 (large companies) and 1 Oct 2028 (others). The draft also confirms use of UBL, CII, EDIFACT, and Facturae formats and sets out the functioning of the public platform. (Once finalized and published in the BOE, this Order will have the force of law; the draft date signals what to expect, but it could be subject to minor changes before final issuance.) [zerocoma.com], [zerocoma.com] [docuten.com], [docuten.com]
• Tax Authority Resources:
  • AEAT “Informative Note: Extension of SIF adaptation period” (Dec 2025) – Official notice of the postponement of VERI*FACTU deadlines to 2027, confirming 1 Jan 2027 / 1 Jul 2027 dates and describing the test phase. Available on the AEAT’s website. [sede.agenc…ria.gob.es], [sede.agenc…ria.gob.es]
  • AEAT FAQs on Veri*Factu/SIF (updated 2024-2025) – A question-and-answer resource on the tax agency’s site explaining which taxpayers must comply, how the system works, and technical questions (e.g. how to handle power outages or system failures during real-time reporting).
  • AEAT SII Information Portal – Official documentation for the SII system including required fields, XML schemas, and user guides for using the SII online system (available on the AEAT’s “Sede Electrónica” website).
  • Facturae Website (Ministerio de Industria) – Provides downloads and documentation for the Facturae format and the FACe platform for B2G invoices, which is relevant background for understanding Spanish e-invoicing practices.
• Technical Documentation:
  • Order HAC/1177/2024 Annexes – These include the XSD schema definitions for the invoice record (called “Registro de Facturación”) and the rules for generating the QR code and the unique identification code (fields often referred to as “UUID” or Identificador único de factura in Spain). These are technical documents, mostly relevant to software developers. Summaries are provided in various tech blogs and by AEAT.
  • EN 16931 and EU Norm – The European standard on e-invoicing semantic content, which Spain’s system adheres to. The standard itself and its list of mandatory/core elements can be found via the European Commission or CEN websites.
  • PEPPOL BIS 3.0 – The PEPPOL Business Interoperability Specification for e-invoices (based on UBL 2.1) is likely to be one of the accepted standards. Documentation is available from PEPPOL authorities; this might be relevant if the Spanish public platform connects with the PEPPOL network.
• Recent Expert Commentary and News (2024–2026):
  • KPMG Tax News Flash (26 Mar 2026) – “Council of Ministers approves e-invoicing mandate for B2B transactions”. Confirms the approval of the RD in March 2026 and describes the scope and phased implementation. [kpmg.com], [kpmg.com]
  • KPMG Tax News Flash (3 Dec 2025) – “Spain: VERIFACTU invoicing system delayed to 2027”. Details the second postponement of the VERIFACTU requirements and the new deadlines. [kpmg.com], [kpmg.com]
  • EY Global Tax Alert (25 Mar 2026) – “Spanish Government approves Royal Decree implementing mandatory B2B electronic invoicing”. Provides an overview similar to KPMG, noting the separation from VERI*FACTU and highlighting the 12- and 24-month phase-in once the Order is published. [taxnews.ey.com]
  • VATupdate.com (25 Mar 2026) – “Spain Approves Mandatory B2B E-Invoicing…”. Summarizes the RD 238/2026 content and timeline, with references to Spanish media and official statements. (Another VATupdate article on 17 Apr 2026 noted the draft Order’s 1 Oct 2026 activation date, aligning large companies’ go-live to 1 Oct 2027 – confirming the timeline in the draft.) [vatupdate.com], [vatupdate.com]
  • VATcalc (vatcalc.com) analysis (Apr 2026) – “Spanish B2B Crea y Crece e-invoice & e-reporting approved July 2027-28”. Discusses the expected timeline and the technical model (formats, Peppol use, etc.), as well as confirming that invoice data (including payment status) must be reported within 4 days by both supplier and customer. [vatcalc.com], [vatcalc.com]
  • Spanish press coverage (El País, La Vanguardia, Cinco Días – March 2026) – broadly covering the government’s approval of the e-invoicing RD and its goals for SME competitiveness and payment term reduction (available in Spanish; e.g., El País headline on 24 March 2026: “El Gobierno aprueba la factura electrónica obligatoria entre empresas para frenar la morosidad”).
  • ZeroComa (tech provider) news post (17 Apr 2026) – confirms the draft Ministerial Order’s publication and the key date of 1 Oct 2026 as the beginning of the timeline, implying mandatory B2B e-invoicing from 1 Oct 2027 and 1 Oct 2028 for large and small companies respectively. [zerocoma.com], [zerocoma.com]
  • Docuten (e-invoicing provider) blog (17 Apr 2026) – provides an analysis of the draft Order, explicitly stating “the Order will enter into force on 1 Oct 2026… the mandatory B2B e-invoicing will be effective on 1 Oct 2027 for large companies”. This is a helpful confirmation from industry specialists closely following the regulatory process. [docuten.com]
  • BDO Global Indirect Tax News (April 2026) – Article “Spain – Regulation for Mandatory B2B E-invoicing Published” (likely referencing the RD 238/2026). Summarizes the content of the new regulation and timelines.
  • PwC “Periscopio Fiscal” blog (27 Mar 2025) – Discusses the draft RD (as of 2025) and notes changes like adopting UBL, and clarifies that “copia fiel” must be sent to the central platform, etc. Useful for understanding the direction of technical requirements.
  • Grant Thornton Alert (Dec 2025) – Confirms VERI*FACTU delay and encourages businesses to prepare for 2027 deadlines.

These references (laws, official releases, and expert analyses) provide a deeper dive into each aspect of the Spanish framework and are recommended for those seeking more detailed information or the original legal texts. All are publicly accessible and reflect the latest available information up to April 2026.

14. Summary

• Scope: Currently, mandatory e-invoicing in Spain applies to B2G invoices, while B2B e-invoicing remains generally voluntary (with certain large companies obliged to offer e-bills to consumers on request). In the near future, Spain will require all B2B invoices between Spanish businesses to be electronic (structured format, not PDF) as enabled by the Create and Grow Law (18/2022). Pure B2C and cross-border transactions are excluded from this mandate – only transactions where both parties are established in Spain and acting in business capacity are covered. Special cases like self-billing and certain triangulations are allowed but must conform to the e-invoice rules (with the self-billing customer issuing the e-invoice). Separately, Spain has an electronic VAT reporting system (SII) in force for large companies since 2017, and is introducing the VERI*FACTU invoicing software requirements (effective 2027) to ensure invoice integrity and real-time reporting for all other businesses. [vatupdate.com] [kpmg.com], [kpmg.com]
• Timeline: Key past and future dates – 2015: B2G e-invoicing mandate began. 2017: SII real-time reporting introduced for large taxpayers. 2021: Anti-fraud law (Law 11/2021) passed, leading to VERIFACTU rules (initially set for 2024–26, but then delayed). Sept 2022: Law 18/2022 (B2B e-invoicing mandate) enacted but pending implementation. Dec 2023: RD 1007/2023 (billing software rules) published. Oct 2024: Technical Order on SIF requirements published. Dec 2025: Government postpones VERIFACTU deadlines to 1 Jan/1 Jul 2027. Mar 2026: RD 238/2026 on B2B e-invoicing approved. Apr 2026: Draft Ministerial Order for B2B e-invoicing released, setting 1 Oct 2026 as the start of the clock. Planned go-live for mandatory B2B e-invoicing is 1 Oct 2027 for large companies and 1 Oct 2028 for all others – these dates are the latest expected schedule, contingent on the Ministerial Order being finalized as drafted. Affected businesses should be prepared for these deadlines, as further extensions are not anticipated. The first year of each phase will be transitional: businesses that are early adopters must accommodate trading partners not yet obliged (e.g., providing PDF copies). [vatupdate.com] [kpmg.com] [kpmg.com], [kpmg.com] [docuten.com] [zerocoma.com] [taxnews.ey.com]
• Key Obligations: Businesses in scope will be required to issue and receive invoices in a structured electronic format, ensuring the format meets Spanish/EU standards and contains all mandated fields. They must use certified invoicing software that guarantees the integrity and traceability of invoice records (with secure timestamping, hash chaining, and, if not reporting in real time, applying digital signatures to invoices). Invoice data must be reported to the Tax Agency either via the SII system (for those under its scope) or via the VERI*FACTU system (for others) – the latter can be done in real time (within seconds) or in a deferred mode with secured storage, but in all cases the data will be made available to the authorities. Customers must, upon receiving an e-invoice, use the platform to communicate its status (accepted/rejected) and later the payment date, within a few days of those actions. Invoices to public entities must still be routed through the government’s FACe platform (Facturae format), while invoices in the B2B sphere can be exchanged through any compliant platform but with a copy to the AEAT’s central system. Additionally, businesses have to archive electronic invoices electronically for at least 4 (generally 6) years, ensuring their integrity and accessibility for audits. They also must grant access to customers for their e-invoices for 4 years after issuance (e.g., via an online portal or downloadable copy).
• Main Risks and Compliance Challenges: Companies that fail to comply with the new rules once in effect face substantial risks. Penalties for non-compliance include fines up to €10,000 for failing to issue/accept e-invoices when required, and up to €50,000 (users) or €150,000 (developers) for using or creating non-compliant invoicing software that allows fraud (per Law 11/2021). Inaccurate or late reporting of invoices can also attract fines (e.g., 0.5% of invoice value for SII delays, with minimum €300). Beyond financial penalties, non-compliance could disrupt business operations – invoices not issued in the correct format might be considered invalid for VAT purposes, meaning customers could refuse to pay or reclaim VAT, and the issuer could be in breach of obligations. On the other hand, there are operational risks during the transition: companies will need to ensure continuity of their billing processes while migrating to new systems. Any technical downtime or integration issues could delay invoice issuance or reporting, potentially affecting cash flow or leading to inadvertent non-compliance. Another risk is data security and privacy, as more sensitive invoice data will be transmitted and stored digitally – businesses must safeguard this information and comply with data protection regulations.
• Impact on SMEs: Small businesses and startups need to prepare for the digital leap. In the short term, SMEs may face increased costs and complexity: purchasing new software or services, adjusting workflows, and training staff. Surveys and experts have noted that many SMEs are delaying preparation, which can be risky and may result in a last-minute scramble. The government’s phased approach and support measures aim to mitigate these challenges by giving SMEs extra time (until 2028) to comply and providing a free invoicing platform and subsidies for digital tools. In the long term, the mandate could yield benefits for SMEs: more timely payments from larger clients (due to payment transparency), simpler tax compliance (with pre-filled returns and fewer errors), and efficiency gains from automating invoice processing. SMEs that adapt early could gain a competitive advantage in dealing with larger customers who prefer electronic invoicing. Nonetheless, continuous monitoring of SME readiness is expected, and the government may calibrate its approach (through further guidance or support) to ensure that small businesses can comply without disrupting their operations. [docuten.com]
• Critical Dates & Next Steps: 1 October 2026 is anticipated as the start of the official transition period (pending the final Ministerial Order). From that date, the clock starts ticking for the mandatory e-invoicing deadlines: 1 October 2027 for large companies (>€8M turnover) and 1 October 2028 for all others. In the meantime, 1 January 2027 / 1 July 2027 are firm for the VERI*FACTU billing software mandate (for companies and for smaller businesses respectively). Companies should use the time leading up to these dates to: [zerocoma.com], [docuten.com] [zerocoma.com] [kpmg.com], [kpmg.com]
  • Assess and upgrade IT systems: Ensure your billing/invoicing software is or will be certified for VERI*FACTU and capable of producing and exchanging e-invoices in the required formats.
  • Participate in pilots or testing: Leverage any available test environments (the AEAT has provided one for SIF) to trial sending invoice data. Stay informed on the rollout of the public e-invoicing platform and consider testing it once available.
  • Train staff and adapt processes: Accounts payable/receivable teams should be trained on new procedures, such as handling electronic invoice files, using digital signatures, and managing the new requirement to report invoice statuses (acceptance, payment).
  • Engage with providers or advisors: Many software providers, consulting firms, and industry groups are offering resources for this transition. It may be beneficial to consult with them on best practices for implementation.
  • Monitor regulatory updates: Since some details (especially the Ministerial Order for e-invoicing) are pending, businesses should keep an eye on official communications from the Spanish Tax Agency (AEAT) and Ministry of Finance. Final technical specifications and exact compliance dates will be confirmed in those publications. The EU’s ViDA developments should also be watched, as they will complement national rules by 2028.

In conclusion, Spain’s e-invoicing and e-reporting reforms are transforming the tax compliance landscape. What is now a mainly voluntary practice for B2B will soon become compulsory, bringing Spain in line with pioneers like Italy and tying into a broader EU digital VAT strategy. While currently only certain segments (B2G invoices, large-taxpayer e-reporting) are covered, the next few years will see a comprehensive expansion to nearly all businesses. Companies that treat this proactively—by upgrading systems and processes—can not only avoid penalties but also reap benefits in efficiency and financial management. The legal framework is largely in place, and with the confirmation of a start date (expected 1 October 2027 for the first wave), the countdown has truly begun. Businesses should now focus on readiness and compliance, leveraging the available guidance and support to ensure a smooth transition into Spain’s new era of digital invoicing and reporting. [docuten.com]