Regulatory updates - Spain

Spain's upper house has taken a notable, if symbolic, step toward simplifying the country's complex digital VAT landscape. The Senate approved a motion calling on the Government to fold three parallel initiatives: VERI*FACTU certified invoicing, mandatory domestic B2B e-invoicing, and the long-standing SII real-time reporting regime, into one coherent transaction reporting framework. 

Alignment with EU digital reporting requirements 

The driving concern is alignment with the EU's VAT in the Digital Age (ViDA) package, whose Digital Reporting Requirements take effect from 2030. Lawmakers want Spain's domestic rules built to match that European structure from the start, rather than forcing businesses through a second wave of costly system changes once ViDA lands. 

Procedural and legal implications 

Beyond technical alignment, the motion asks for what many businesses have long requested: a single public roadmap, stronger legal certainty, and a genuine transition period, with SMEs specifically in mind, given their typically thinner compliance capacity. 

Current legislative status 

Worth noting: the motion doesn't alter current VERI*FACTU or B2B e-invoicing deadlines, and it has no binding force on its own, turning intent into practice still depends on Government action. Still, it signals clearly where political momentum is heading. The full motion text is available in the Senate's official bulletin. 

The Spanish Ministry of Finance is finalizing a bill that will introduce targeted changes to VAT rules for e-commerce and cross-border transactions. The proposal forms part of Spain’s implementation of the EU’s latest VAT in the Digital Age (ViDA) package and is expected to be submitted to Congress after completing the government approval process.

At the heart of the reform is the expansion and clarification of the One-Stop Shop (OSS) framework established under the EU’s  VAT in the Digital Age (ViDA) initiative. The draft clarifies how the €10,000 threshold for intra-EU distance sales should be calculated, confirming that only sales originating from the Member State where a business is established will count toward that limit.

The proposal also updates the special VAT regime for businesses established outside the European Union. Under the draft, a wider range of services supplied by non-EU businesses could fall within the regime, while new obligations, such as the possible appointment of a fiscal representative, would strengthen oversight and compliance.

These measures are part of Spain’s transposition of Directive (EU) 2025/516, which seeks to streamline VAT administration across the EU while adapting the framework to the realities of digital and cross-border commerce.

AEAT has published two documents, giving the clearest picture yet of how the SPFE will operate. Document 1 covers what it does; Document 2 covers how to connect to it.

Document 1 (Ministerial Order Project for the Public Electronic Invoicing Solution), Functional, confirms the following aspects:

• Hybrid model: When the electronic invoice issuance and interconnection are not performed via the SPFE, private platforms must deposit a faithful copy (copia fiel) in the SPFE simultaneously with issuance, flagged via CopyIndicator;
• Each invoice carries a unique code (NIF + series-number + issue date) enabling automatic deduplication;
• Mandatory lifecycle statuses: rejection or acceptance (silence equals acceptance), full payment date, and due date;
• Platforms must aggregate traffic, hold formal Power of Attorney (SP. apoderamiento) per client, and retrieve invoices automatically; thin pass-through models are non-compliant.

Document 2 (Public Electronic Invoicing Solution (SPFE)), Technical aspects. The following technical baseline is defined:

• Syntax: UBL 2.5 exclusively, aligned to EN 16931:2026;
• Two-layer validation: XSD for syntax, Schematron for business rules, must be embedded by senders; no public online validator;
• Connectivity via synchronous web services with certificate-based authentication;
• Representation asymmetry: sending allows Power of Attorney (SP. apoderamiento) or social collaborator; retrieving requires Power of Attorney (SP. apoderamiento) only, automated retrieval without registered representation is blocked.

What is next

Once the Ministerial Order is published in the BOE (expected October 1, 2026), transitional periods begin, the sandbox opens, and developer portal documentation, XSD schemas, Schematrons, WSDLs, message examples, follows before go-live.

Large businesses face mandatory compliance in October 2027. The technical picture is defined enough to act now. Prioritise UBL 2.5 readiness, Power of Attorney (SP. apoderamiento) onboarding design, and embedding validation logic. October 2027 is manageable for those who start in October 2026.