Spain Publishes Final Technical Rules and Confirms Timeline for Mandatory B2B E-Invoicing

Updated: October 6, 2026

---

---

Slide deck

---

Summary

• Spain published Order HAC/1028/2026 on 5 October 2026. The order entered into force on 6 October 2026 and triggered the implementation periods for mandatory B2B e-invoicing: 6 October 2027 for businesses exceeding EUR 8 million in annual turnover and 6 October 2028 for other in-scope businesses. [boe.es], [sede.agenc…ria.gob.es]
• The mandate requires structured, machine-readable electronic invoices. A PDF is not itself a compliant structured e-invoice. However, during the first 12 months of the large-business mandate, the structured invoice must generally be accompanied by a readable PDF unless the recipient expressly and voluntarily agrees to receive only the original structured format. [boe.es]
• The Spanish framework should be considered alongside SII and VERIFACTU, but the systems remain legally distinct. Spain has announced an intention to postpone and align VERIFACTU with the B2B regime and, subsequently, with ViDA, but that announcement does not change the current law until an amending measure is published. [europe.tho…euters.com], [vatcalc.com]

Extended article

Spain completes the technical framework

Spain has published Order HAC/1028/2026 of 2 October 2026, regulating the technical and functional elements of the public electronic invoicing solution operated by the Spanish Tax Agency, the AEAT. The order was published in the Official State Gazette on 5 October 2026 and entered into force the following day. [boe.es]

The order represents the final technical component required to activate the implementation periods established under Law 18/2022 and Royal Decree 238/2026. The underlying B2B obligation originates from Law 18/2022, while Royal Decree 238/2026 defines the architecture, scope and phased application of the mandatory system. [boe.es]

Confirmed implementation timeline

The resulting timeline is:

• 5 October 2026: Order HAC/1028/2026 published in the Spanish Official State Gazette.
• 6 October 2026: The order enters into force and the implementation periods begin.
• By 6 August 2027: The AEAT public solution must be available at least two months before the first effective application date.
• 6 October 2027: Mandatory B2B e-invoicing begins for businesses and professionals whose volume of operations, calculated under Article 121 of the Spanish VAT Law, exceeded EUR 8 million in the immediately preceding calendar year.
• 6 October 2028: Mandatory B2B e-invoicing begins for the remaining businesses and professionals within scope.
• 6 October 2029: The mandatory invoice-status reporting rules apply to qualifying individuals and entities under the income-attribution regime with turnover not exceeding EUR 8 million. Until then, their status reporting is voluntary. [boe.es], [sede.agenc…ria.gob.es], [boe.es], [europe.tho…euters.com]

The applicable turnover test is therefore not simply group revenue or accounting revenue. It refers to the volume of operations calculated under Article 121 of the Spanish VAT Law for the immediately preceding calendar year. Businesses should assess the deadline separately for each relevant Spanish entrepreneur or professional within the mandate’s scope. [sede.agenc…ria.gob.es], [boe.es]

Who and which transactions are covered?

The B2B mandate applies where a business or professional required to issue an invoice supplies another business or professional that has its place of business, a fixed establishment or, in the absence of those, its domicile or habitual residence in Spain, provided the transaction is directed to that Spanish establishment, fixed establishment, domicile or residence. Exceptions and special cases remain governed by Royal Decree 238/2026 and the legislation referenced in the order. [boe.es]

This means that a Spanish VAT registration alone should not automatically be treated as sufficient to determine scope. The location and involvement of the supplier and customer establishments, as well as the establishment to which the transaction is directed, must be examined. [boe.es], [pincvision.com]

Structured invoice required: a PDF is not enough

The new obligation concerns a structured, machine-readable electronic invoice. Merely generating or emailing a PDF invoice does not satisfy the structured B2B e-invoicing requirement. Electronic invoices issued or interconnected through the public solution must comply with the EN 16931 semantic data model and use UBL syntax. [boe.es], [bovemontero.com]

For private-platform exchanges, the Spanish framework also accommodates the syntaxes and formats established under Royal Decree 238/2026, including UBL, UN/CEFACT CII, EDIFACT and Facturae. Regardless of the original permitted format, a faithful copy sent by a private platform to the AEAT public solution must use UBL. [vatcalc.com]

Which invoice formats are permitted?

Is a PDF nevertheless required?

A temporary PDF requirement applies to businesses and professionals with annual turnover exceeding EUR 8 million. During the 12 months following the date on which the mandate becomes applicable to them, they must accompany each structured electronic invoice with a PDF document that ensures legibility for the recipient. Based on the confirmed starting date, this transitional period runs from 6 October 2027 through 5 October 2028. [boe.es]

The PDF is not required where the recipient voluntarily and expressly agrees to receive the invoice in its original structured electronic format without the accompanying PDF. The PDF may be sent to the recipient by any channel, but it must not be submitted to the AEAT public solution. [boe.es]

The PDF is therefore a temporary human-readable companion document, not the legally required structured invoice and not a substitute for it. Businesses should preserve evidence of any recipient’s express agreement to waive the PDF during the transitional period.

Public solution and private platforms

Businesses may use the AEAT public solution, a private electronic invoicing platform, or a combination of both. The public solution will provide invoice generation, interconnection, invoice retrieval, consultation, status reporting and payment-information services. Access to the public solution will be free of charge. [boe.es], [sede.agenc…ria.gob.es]

Invoices issued or interconnected directly through the public solution become immediately available to the tax administration. No additional faithful copy is required for those invoices. [boe.es]

Where a business uses a private platform rather than the public solution for issuance or interconnection, the platform must simultaneously transmit a faithful electronic copy of the invoice to the AEAT public solution. That copy must:

• use UBL syntax;
• contain the invoice information that has an equivalent semantic correspondence in the public solution;
• meet the minimum Spanish invoicing requirements;
• be identified as a copy through the designated “copy indicator”; and
• exclude embedded or integrated attachments. [boe.es]

The prohibition on embedded files is important for PDF handling. Neither invoices exchanged through the public solution nor faithful copies submitted to it may incorporate embedded attachments. The transitional readable PDF must therefore be sent separately to the customer and not embedded in, or transmitted to, the public solution. [boe.es], [boe.es]

Validation and technical error handling

Invoices and faithful copies transmitted through web services will be subject to syntactic, semantic and technical validation. The AEAT will respond by identifying accepted and rejected submissions and will specify the reason for rejection. It will also issue an acknowledgement containing a secure verification code. [boe.es]

A rejected faithful copy is treated as not admitted to the public solution. This does not in itself invalidate an original invoice already issued and delivered through a private platform, but the reporting party must correct the error and resubmit the faithful copy. If the problem originates in the original invoice, a corrected original may need to be issued before the copy is resubmitted. [boe.es]

Where the public solution is unavailable for more than 24 hours for technical reasons attributable to that system, the relevant invoices, copies and status information may be submitted during the four business days following resolution of the incident. [boe.es]

Invoice identification and lifecycle reporting

Each invoice will be identified through a unique code formed by concatenating the supplier’s Spanish tax identification number, invoice series, invoice number and issue date. This identifier supports duplicate controls, invoice recovery and the connection between an invoice and its subsequent status information. [boe.es]

The recipient must report, where applicable, the rejection of an invoice, its due date and the date of full effective payment. The recipient may also report the date of receipt of the goods or services or the invoice-receipt date where relevant under the Spanish late-payment rules. In the absence of a rejection or subsequent corrective invoice, an invoice is presumed to have been accepted. [boe.es]

The supplier may voluntarily communicate collection or non-payment information and report differences from payment dates communicated by the customer. These obligations mean that implementation must cover accounts receivable, accounts payable, payment matching and dispute management, rather than focusing only on invoice generation.

Relationship with VERI*FACTU, SII and FACe

The Crea y Crece B2B e-invoicing mandate must not be confused with VERIFACTU. The B2B regime governs the structured exchange of invoices between businesses and the reporting of invoice lifecycle information. VERIFACTU concerns the integrity, traceability and technical operation of invoicing software. A business may therefore need to address both frameworks. [vatcalc.com], [vatupdate.com]

The Spanish Ministry of Finance announced on 5 October 2026 that it intends to postpone the pending VERIFACTU obligations for businesses and professionals to October 2028 and subsequently align the system with B2B e-invoicing and ViDA. However, the announcement has no legal effect by itself. The existing VERIFACTU dates remain legally applicable until the required amendment is published in the Official State Gazette. [europe.tho…euters.com]

SII also remains a separate near-real-time VAT ledger-reporting system. The publication of the B2B e-invoicing order does not itself abolish or replace existing SII obligations. Similarly, the existing B2G framework, including FACe and the transitional arrangements for FACeB2B, should be treated as a distinct compliance stream. [pincvision.com], [vatupdate.com], [boe.es]

ViDA and possible future convergence

Spain’s B2B e-invoicing regime is based on the EN 16931 semantic standard, which provides an important connection with the EU’s wider digital invoicing direction. Nevertheless, compliance with the Spanish domestic mandate should not automatically be considered sufficient for future ViDA digital reporting requirements. [boe.es], [europe.tho…euters.com]

The Spanish Senate has called for greater convergence between VERI*FACTU, SII and mandatory B2B e-invoicing and for alignment with ViDA. That initiative is non-binding and does not alter the current requirements. Any consolidation or technical alignment will require further legislative or regulatory action. [europe.tho…euters.com]

What businesses should do now

Businesses potentially within scope should establish a coordinated Spanish readiness programme covering:

• entity and transaction scope, including Spanish fixed-establishment analysis;
• the Article 121 VAT turnover test for determining the applicable implementation wave;
• mapping invoice data to EN 16931 and the permitted Spanish syntaxes;
• selection of the AEAT public solution, a private platform or a hybrid architecture;
• generation and simultaneous transmission of faithful UBL copies;
• transitional PDF delivery and evidence of any customer waivers;
• invoice-status and payment reporting;
• integration with accounts payable, accounts receivable and payment-reconciliation processes;
• coordination with existing SII, FACe and VERI*FACTU workstreams; and
• monitoring of announced but not yet enacted VERI*FACTU and ViDA-alignment changes.

External sources

• • Order HAC/1028/2026 in the Spanish Official State Gazette
  • Official PDF of Order HAC/1028/2026
  • Royal Decree 238/2026 in the Spanish Official State Gazette
  • Spanish Tax Agency overview of mandatory electronic invoicing
  • Spanish regulatory timeline, including VERI*FACTU update

 

• VATupdate overview of SII, VERI*FACTU and Crea y Crece

---

 

---

1. Executive Summary

Spain has finalized the technical framework for its mandatory Business-to-Business (B2B) e-invoicing system, activating a phased implementation schedule. This new mandate requires structured, machine-readable electronic invoices and introduces significant changes for businesses operating in or with Spain. The framework is legally distinct from existing systems like SII and VERIFACTU, although there are intentions for future convergence. Businesses must prepare for a complex transition involving technical integration, process adjustments, and potentially new reporting obligations related to invoice lifecycle. The information presented here, sourced from a specialist in global tax compliance (VATupdate.com, “the ultimate hub for everything VAT and customs worldwide”), highlights the critical details for compliance.

2. Legal Basis and Regulatory Framework

The Spanish mandatory B2B e-invoicing obligation originates from Law 18/2022, with Royal Decree 238/2026 defining the system’s architecture, scope, and phased application. The final technical and functional elements were regulated by Order HAC/1028/2026, published on October 5, 2026, and entering into force on October 6, 2026. This order, issued by the Spanish Tax Agency (AEAT), completed the necessary framework to trigger the implementation periods.

3. Confirmed Implementation Timeline

The implementation of the mandatory B2B e-invoicing regime will occur in phases:

• October 5, 2026: Order HAC/1028/2026 published.
• October 6, 2026: Order enters into force, marking the start of implementation periods.
• By August 6, 2027: The AEAT public solution must be available.
• October 6, 2027: Mandatory B2B e-invoicing begins for businesses and professionals with an annual “volume of operations” exceeding EUR 8 million in the immediately preceding calendar year, as calculated under Article 121 of the Spanish VAT Law.
• October 6, 2028: Mandatory B2B e-invoicing begins for all other in-scope businesses and professionals.
• October 6, 2029: Mandatory invoice-status reporting rules apply to qualifying individuals and entities under the income-attribution regime with turnover not exceeding EUR 8 million (voluntary before this date).

It is crucial to note that “The applicable turnover test is therefore not simply group revenue or accounting revenue. It refers to the volume of operations calculated under Article 121 of the Spanish VAT Law for the immediately preceding calendar year.”

4. Scope of Application: Who and Which Transactions are Covered?

The B2B mandate applies where:

• A business or professional required to issue an invoice
• Supplies another business or professional
• That has its place of business, a fixed establishment or, in the absence of those, its domicile or habitual residence in Spain,
• Provided the transaction is directed to that Spanish establishment, fixed establishment, domicile or residence.

This means that “a Spanish VAT registration alone should not automatically be treated as sufficient to determine scope. The location and involvement of the supplier and customer establishments, as well as the establishment to which the transaction is directed, must be examined.”

5. Technical Requirements for E-Invoices

The core requirement is a structured, machine-readable electronic invoice.

• “A PDF is not itself a compliant structured e-invoice.”
• Invoices issued or interconnected through the public solution must comply with the EN 16931 semantic data model and use UBL syntax.
• For private-platform exchanges, permitted syntaxes include UBL, UN/CEFACT CII, EDIFACT, and Facturae.
• Regardless of the original format, “a faithful copy sent by a private platform to the AEAT public solution must use UBL.”

6. The Role of PDFs

A temporary, transitional PDF requirement applies for the first 12 months for businesses exceeding EUR 8 million in turnover (from October 6, 2027, through October 5, 2028).

• During this period, structured electronic invoices must be accompanied by a PDF for readability, “unless the recipient expressly and voluntarily agrees to receive only the original structured format.”
• The PDF is not the legally required structured invoice. It is a “temporary human-readable companion document, not the legally required structured invoice and not a substitute for it.”
• PDFs “must be sent separately to the customer and not embedded in, or transmitted to, the public solution,” as embedded attachments are prohibited for invoices submitted to the AEAT public solution.

7. E-Invoicing Platforms: Public vs. Private

Businesses have flexibility in how they connect to the system:

• AEAT Public Solution: Offered free of charge, it will provide invoice generation, interconnection, retrieval, consultation, status reporting, and payment information services. Invoices issued directly through this solution become immediately available to the tax administration, requiring no additional copies.
• Private Electronic Invoicing Platforms: If a business uses a private platform, that platform “must simultaneously transmit a faithful electronic copy of the invoice to the AEAT public solution.” This copy must:
• Use UBL syntax.
• Contain equivalent semantic invoice information.
• Meet minimum Spanish invoicing requirements.
• Be identified with a “copy indicator.”
• Exclude embedded or integrated attachments.

Invoices transmitted through web services are subject to syntactic, semantic, and technical validation, with rejections requiring correction and resubmission.

8. Invoice Lifecycle Management and Reporting

The mandate extends beyond mere invoice issuance:

• Each invoice will be identified by a unique code (supplier’s Spanish tax ID, invoice series, number, issue date).
• Recipient Reporting: The recipient must report, where applicable, the rejection of an invoice, its due date, and the date of full effective payment. They may also report receipt dates for goods/services or the invoice itself. If no rejection or corrective invoice is issued, acceptance is presumed.
• Supplier Reporting (Voluntary): The supplier may voluntarily communicate collection or non-payment information.
• Implication: “These obligations mean that implementation must cover accounts receivable, accounts payable, payment matching and dispute management, rather than focusing only on invoice generation.”

9. Distinction from Other Spanish Tax Systems

Spain’s B2B e-invoicing mandate remains distinct from other existing systems:

• VERIFACTU: Concerns invoicing software integrity and traceability. While the Ministry of Finance announced an intention to postpone VERIFACTU obligations to October 2028 and align with B2B e-invoicing and ViDA, “the announcement has no legal effect by itself.” The original VERIFACTU dates remain legally applicable until an amendment is published.
• SII (Immediate Supply of Information): This near-real-time VAT ledger-reporting system remains separate and is not abolished or replaced by the B2B mandate.
• FACe (B2G E-Invoicing): The existing Business-to-Government (B2G) framework is also a distinct compliance stream.

10. Future Outlook and EU Alignment (ViDA)

Spain’s B2B e-invoicing regime is based on the EN 16931 semantic standard, which is a key element of the EU’s wider digital invoicing direction. However, “compliance with the Spanish domestic mandate should not automatically be considered sufficient for future ViDA digital reporting requirements.” There have been calls from the Spanish Senate for greater convergence between VERIFACTU, SII, mandatory B2B e-invoicing, and alignment with ViDA, but “that initiative is non-binding and does not alter the current requirements.”

11. Recommendations for Businesses

Businesses potentially within scope should immediately initiate a coordinated readiness program, addressing:

• Entity and Transaction Scope: Conduct a thorough analysis, including Spanish fixed-establishment criteria.
• Turnover Test: Accurately apply the Article 121 VAT turnover test to determine the applicable implementation wave.
• Data Mapping: Map invoice data to EN 16931 and the permitted Spanish syntaxes.
• Platform Strategy: Decide on using the AEAT public solution, a private platform, or a hybrid architecture.
• “Faithful Copy” Transmission: Establish processes for generating and simultaneously transmitting faithful UBL copies to the AEAT for private platform users.
• Transitional PDF Handling: Plan for temporary PDF delivery and documentation of any customer waivers.
• Reporting Integration: Integrate invoice-status and payment reporting with existing Accounts Payable, Accounts Receivable, and payment-reconciliation processes.
• Existing Systems Coordination: Coordinate with ongoing SII, FACe, and VERIFACTU workstreams.
• Monitoring: Continuously monitor announced but not yet enacted changes regarding VERIFACTU and ViDA alignment.

---

---