Spain’s tax administration updated the market on the ministerial order governing its public invoicing platform at a technical briefing on 10 September. Every earlier document described the regime in policy terms. This one described interfaces: service names, envelope structures, batch ceilings, response codes and error semantics, which means the work can now be scoped rather than estimated.
The Calendar in One Place
| Milestone | Status |
| Public consultation on the draft order | Closed 8 May 2026 |
| European notification procedure (Directive 2015/1535) | Closed 6 August 2026 |
| Technical briefing on the revised draft | Held 10 September 2026 |
| Order signed and published in the state gazette | Targeted for 1 October 2026 |
| Integration test environment opens | Targeted for October 2026, only after publication |
| First wave: issuance and status reporting, above EUR 8 million in transaction volume | 1 October 2027 |
| Second wave: issuance for everyone else, status reporting for smaller legal entities | 1 October 2028 |
| Third wave: status reporting for individuals and income-attribution entities below the threshold | 1 October 2029 |
Every date below the signature line is derived, not decreed. The decree counts the transition periods from the day the order takes effect, so the three waves float with it.
The Baseline the Order Assumes
Much of the architecture predates September and was reconfirmed rather than announced.
- Legal chain. The 2022 growth statute created the duty. A royal decree published in the spring turned it into an architecture pairing private platforms with a state-run one. The order now in final draft is the last layer, running to eleven articles and two annexes, and covers only the platform’s components and access, the payment notification service, the syntax and coding scheme, and platform-to-platform traffic.
- Scope. Any business obliged to issue invoices under Spanish rules, where the recipient has its seat, fixed establishment or residence in Spain. Simplified invoices sit outside unless qualified; a few sectors are carved out.
- Threshold. Measured as volume of operations under Spanish VAT rules, not accounting turnover. Confusing the two puts a business in the wrong wave.
- Two routes. Private exchange, with a structured copia fiel (faithful copy) reaching the state platform at the moment of issuance rather than afterwards. Or issuance through the state platform itself, from the business’s own system or its free web form. The state platform can also sit between two private ones, and owes no copy where it already holds the original.
- Syntax. The state platform works exclusively in UBL 2.5, aligned to the European semantic standard. Private operators may use the other permitted syntaxes, but anything crossing into the state platform, original or copy, is UBL. This single constraint carries more cost than any other line in the order.
- Identity. Series and number, issue date and seller tax number, concatenated into one code and carried through either the VAT or the domestic tax identifier. Two live registrations cannot share it, so a lodged copy must be pulled before an original replaces it.
- The retrieval key. The platform returns an encrypted localizador for access to the stored file. It does not replace the invoice number, is not a condition of validity, and is not an authorisation identifier of the kind clearance regimes issue. It is a pointer, preferred by the authority over the invoice identity for retrieval, and therefore worth storing.
What Changed Since the Spring Draft
The invoice was rebuilt, not adjusted. The bespoke national construct for credit and debit notes has been withdrawn, and corrections now travel inside the European standard’s own referenced-document group, carrying reason, method and restated amounts through managed code lists. Seller identification splits across three terms covering the VAT number, the domestic tax number and the commercial registry number, the registry entry becoming compulsory wherever the domestic number is used, and buyer identification mirrors it. A marker separating originals from faithful copies is optional on the first and compulsory on the second. Charges and deductions gained header and line placements, with explicit provision for excise duties across fuels, alcohol, tobacco, vaping liquids, electricity, coal, single-use plastics and waste levies, while a group from the 2026 revision of the European norm absorbs third-party charges, withholdings and the vehicle registration levy. Self-billing was confirmed with its own document types, third-party issuance now triggers a mandatory data group, and VAT categorisation leans on the newest edition of the standard, although the country-specific exemption codes were requested through the European mechanism rather than minted nationally and do not yet exist.
Two revisions invite misreading. Certain supplier-regime keys were pulled from their code list because declaring those regimes is not compulsory invoice content, which does not license omitting the corresponding tax or surcharge amounts from the document. And the annex now maps where statutory mentions and notes belong without turning every note field into a mandatory one.
A withdrawal instrument appeared. Built on a standard response document, it identifies the invoice by series and number, issue date and seller data, clears the entry from ordinary consultation while leaving an internal trace, and frees the technical identifier for reuse when a copy is replaced by an original. It does not substitute for a credit note where one is legally required.
Transport was settled and the services were named. Messages travel inside a standards-based ebXML envelope rather than a proprietary wrapper, carrying message identification, party identification derived from the sender’s certificate, service and action indicators and payload references. The authority called the approach compatible with AS4 and supportive of the EU’s VAT in the Digital Age direction, but that alignment concerns transport alone: payload, service semantics, credentials and coding remain national, so an existing network connection elsewhere in Europe removes very little of the build. Items inside a batch are evaluated independently, so one malformed document does not force resubmission of the rest. Against that envelope sit named services for submission, cancellation, lookup by identifier or filter, retrieval by identifier or retrieval key, and buyer-side and seller-side event reporting with their reversals, capped at a hundred documents per submission, just over five megabytes each, a thousand records per lookup and a hundred per retrieval. Binary attachments are refused and may only be referenced by link.
Validation is three stacked gates. Structure against the schema, semantics against the European rule set, and national checks on tax logic, consistency and code lists. Clearing all three means admitted, not endorsed, and senders are expected to run the first two themselves rather than treating the service as a validation endpoint.
The payment layer gained a relief and a disclosure. Where an invoice or its copy already records settlement on or before issuance, matching the transaction or tax point, the buyer’s reporting duty is discharged unless the buyer declares otherwise. Separately, sellers may now flag early collection through financing, which explains a gap between their collection date and the buyer’s payment date without either side appearing to misreport.
What Held Firm
Three ways in, not one. A free invoicing application aimed at smaller operators, usable only in one’s own name or under a registered mandate. A consultation and status screen filtered on submission date, deliberately a different axis from the one used in the existing VAT reporting regime. And the synchronous services, which demand a qualified certificate but are open to any authorised business rather than reserved to a class of operator. Permissions across them are not uniform: own name or registered power of attorney opens everything, whereas a registered filing agent may submit invoices and status changes but can only retrieve what it submitted itself.
Status handling keeps its shape. An admitted invoice starts accepted by default, so no separate acknowledgement is owed by each recipient. Buyers report rejection with a reason or settlement in full with both actual and contractual dates, sellers may volunteer collection or default, the vocabularies are fixed and paired with reversals, the two sides cannot share a message, and reversing a status report remains distinct from withdrawing the invoice. Only payment in full is recognised, so instalments have no native representation, and none of this displaces the commercial reporting that buyers still owe their suppliers on private routes.
Two safety valves and two disclaimers. Unavailability of more than a day on the platform’s side opens a four-working-day window after resolution, and a rejected copy leaves a sound invoice standing with the fix confined to the copy. The platform is not an archive, so retention stays with the business and access to older records may be curtailed, and it does not replace the existing near-real-time VAT reporting obligation.
Is a Postponement Actually Coming?
The first wave was never postponed. October 2027 has been the arithmetic of the published draft since the spring. Anyone calling it newly slipped is measuring against the 2022 statute’s original ambitions, which never survived contact with the implementing regulations. The question to put to the claim is simple: postponed from which date, by which published instrument?
What can slip is the signature, and everything is anchored to it. Because the transition periods run from the effective date rather than a fixed calendar, a delay does not move the first wave alone. It shifts the entire sequence by the same interval, the test environment included.
The case for the target holding is stronger than it looks. Both external gates have closed, the consultation and the European notification with its mandatory standstill, which was the last approval the administration needed from outside itself. A ministerial order requires no parliamentary time, only a signature and a publication slot, and the date was still being presented as live at the briefing.
The case for slippage is technical, not procedural. The text was still a draft. The developer documentation, the service definitions and the validation artefacts remain unpublished, and the mapping specification underpinning the syntax was finalised only weeks earlier. That is an aggressive runway for standing up a national platform.
The honest position sits between the two, and the signal is not the gazette. Nothing has been postponed; a target is unmet, which is a different animal, so October 2027 deserves to be treated as a planning assumption with a known dependency. Because testing is gated behind publication, the test environment will expose slippage before the legal record does. No sandbox by year end means the first wave has moved.
What Comes Next, and Where to Start
The remaining sequence is strict and each step gates the next: the signed order is published, the developer documentation follows with separate service catalogues for businesses and for platforms alongside message examples, service definition files and validation artefacts, and only then does the test environment open, reachable with a qualified certificate and adequate authority over the represented party. One instruction aimed at providers has been underweighted since the session: platforms handling volume must use dedicated services and may not work against the public platform one invoice or one client at a time, which is a statement about tenancy, batching and error handling rather than a throwaway remark.
Three pieces of work are already specified well enough to begin. The invoice needs remapping at field level rather than patching, because corrections, the tripartite seller identification, excise and withholding placement, the self-billing and third-party markers and the copy flag all sit on code paths that most implementations populate differently today. The status layer is a second integration rather than an extension of the first, with its own document type, service pair and reversal semantics, and a settlement concept that recognises nothing but payment in full. And the failure paths deserve as much design as the happy one, because a copy can be rejected while the commercial invoice remains perfectly valid, and only one of those two remedies ever reaches the customer.
