Spain releases first technical blueprint for public e-invoicing platform
Spain has published its first comprehensive technical documentation for the future Public Electronic Invoicing Solution (SPFE), marking an important shift from legislative planning towards practical implementation.
While recent updates primarily focused on timelines and legal requirements, the latest publications provide the first detailed view of how the SPFE will operate technically, how businesses will connect to the platform, and what software providers must prepare for before mandatory B2B e-invoicing begins.
The Spanish Tax Authority (AEAT) has released two documents covering both business processes and technical architecture. Together, they provide the most detailed guidance published so far on the infrastructure that will support Spain’s future B2B e-invoicing framework.
The publications build on several developments announced over the past year, including Spain’s confirmation of its phased rollout approach, the ongoing alignment with European e-invoicing standards and recent adjustments linked to the VeriFactu programme. Together, these initiatives are gradually shaping the country’s future compliance landscape.
Technical implementation moves into focus
Much of the discussion around Spain’s e-invoicing mandate has focused on deadlines, reporting obligations and the hybrid exchange model. The newly released documentation shifts attention to implementation.
For the first time, businesses, ERP teams and software providers can review how invoices will be transmitted, validated, routed and tracked within the SPFE environment.
The documents also provide greater clarity on how private platforms will interact with the public infrastructure, a critical element of Spain’s hybrid approach.
SPFE will validate, route and track invoices
The guidance explains the role of the SPFE within the future ecosystem.
The platform will receive electronic invoices, validate both their syntax and business content, and distribute them to recipients. It will also manage invoice lifecycle information, including status updates related to acceptance, rejection, payment confirmation and cancellation.
This means the platform will support not only invoice exchange but also the broader reporting and transparency objectives that form part of Spain’s e-invoicing strategy.
New insight into integration requirements
One of the most significant aspects of the publication is the level of detail provided around system integration.
The technical documentation confirms that organisations will be able to connect to the SPFE through secure machine-to-machine communication channels, including:
- REST APIs
- AS4 protocols
- Web services
These specifications provide software developers and integration teams with their first indication of the technologies that will be required to support compliance.
Security and authentication requirements defined
The documentation also introduces mandatory security requirements for platform access and data exchange.
Electronic certificates and digital signatures will play a central role in securing communications and verifying the identity of participating platforms and organisations.
This aligns with broader European efforts to ensure secure and trusted exchange of structured invoice data.
Support confirmed for future European standards
One of the most notable technical confirmations is Spain’s intention to support the upcoming EN 16931:2026 standard together with the future XML UBL 2.5 syntax.
Although UBL 2.5 is still being finalised, the reference provides an early indication of the direction Spain intends to take as European e-invoicing standards continue to evolve.
For multinational organisations, this alignment should help support consistency across multiple European compliance frameworks. Spain’s broader strategy of aligning its e-invoicing framework with evolving European standards was discussed in our previous article Spain aligns B2B e-invoicing standards with EU requirements.
Sandbox environment planned for October 2026
The guidance confirms that a dedicated testing environment will be made available before deployment.
The sandbox will allow software developers, service providers and businesses to test integrations, validate message exchanges and verify compliance requirements ahead of go-live.
According to the current planning, the environment will not become available before October 2026, which coincides with the expected publication of the Ministerial Order.
Additional developer documentation is still coming
The newly published specifications are only the first step in Spain’s technical rollout.
AEAT has confirmed that several additional technical documents will be released through its developer portal before the SPFE becomes operational.
Expected publications include:
- Service catalogues for companies and platforms
- Submission standards
- Authentication and representation requirements
- Error lists and service definitions
- XSD schemas and UBL references
- Validation documents and schematrons
- Examples of invoice, payment and cancellation messages
These publications will provide the detailed implementation guidance required by software vendors and businesses preparing for integration projects.
What this means for businesses
Spain’s implementation timeline remains unchanged, with mandatory B2B e-invoicing expected to begin in October 2027 for larger businesses. The phased approach and broader framework were previously outlined in Spain confirms B2B e-invoicing direction for 2027.
However, the latest publications are significant because they provide the first concrete view of the technical architecture behind the mandate.
For many organisations, preparation can now move beyond regulatory monitoring and towards practical planning, including ERP readiness assessments, integration design and platform strategy decisions.
Businesses should also continue monitoring related developments outside the SPFE programme itself. For example, recent changes affecting the VeriFactu framework and SII reporting obligations demonstrate that Spain’s broader digital tax landscape continues to evolve alongside the e-invoicing mandate, as discussed in Spain opens temporary SII renunciation window after VeriFactu delay.
Changes companies need to implement
- Review ERP readiness for EN 16931:2026 and future UBL 2.5 requirements.
- Assess API and integration requirements for connecting to e-invoicing platforms.
- Prepare for invoice lifecycle status reporting obligations.
- Evaluate authentication and digital certificate requirements.
- Monitor upcoming developer documentation and sandbox availability during 2026.
