Spain: The Crea y Crece Compliance Clock Has Not Started, Because the Implementing Ministerial Order Is Still Unpublished
Country Update — Spain | 25 August 2026 | Topic: E-Invoicing / Legislative Status
As at August 25, 2026 the Ministerial Order that starts the Spanish B2B e-invoicing compliance clock has still not been published in the Boletín Oficial del Estado. Royal Decree 238/2026 of March 25, 2026 was published on March 31, 2026, but its phase-in periods of twelve and twenty-four months do not run from that publication. They run from the entry into force of a separate implementing Order, which was submitted to public hearing on April 17, 2026 and has not been adopted since. Every calendar date currently circulating for Spanish B2B e-invoicing is therefore a projection, not a deadline.
Background
Spain is building two separate obligations at once, and they are routinely confused. The first is Verifactu, the certified billing-software regime under Royal Decree 1007/2023, which governs how invoicing software must record and, in the Verifactu mode, transmit billing records. The second is the Crea y Crece B2B electronic invoicing obligation, which governs the invoice itself and the network over which it travels. They have different legal bases, different scopes and different timetables, and a Spanish entity will in most cases be subject to both.
Royal Decree 238/2026 of March 25, 2026 develops the B2B e-invoicing obligation. It was published in the Boletín Oficial del Estado on March 31, 2026 under reference BOE-A-2026-7295, and the AEAT published an accompanying notice on its Sede electrónica the same day. That publication is what most commentary treated as the starting gun. It was not.
The reason is in the royal decree's own final provisions. Royal Decree 238/2026 does not set calendar dates for the obligation at all. It sets periods, and it attaches those periods to an instrument that did not yet exist when the decree was published.
The Legislative Change
This is a legislative development in the negative: the significant fact is that an expected instrument has not been adopted, and that the consequences of its absence are widely misunderstood.
Under the fourth final provision of Royal Decree 238/2026, effective application is deferred by twelve months for taxable persons whose turnover in the immediately preceding calendar year exceeded EUR 8 million, determined under Article 121 of Law 37/1992, and by twenty-four months for everyone else. Both periods are counted from the entry into force of the Ministerial Order foreseen in the third final provision, paragraph 1. The second paragraph of the same final provision defers the obligations falling on platforms and solution providers — Articles 6, 8, 9 and 13, covering the faithful copy (copia fiel), interconnection and operating requirements — by twelve months from that same trigger.
As at August 25, 2026 the consolidated text of Royal Decree 238/2026 on the BOE shows a last update of March 31, 2026, a single redaction, and no block of subsequent references. The implementing Order has not been published. The twelve-month and twenty-four-month clocks have not started.
A draft of the Order does exist. The Ministry of Finance submitted it to public hearing and information on April 17, 2026, and the document remains available on the Ministry's website. Its sole final provision states that the Order will enter into force on October 1, 2026. That is a provision of a draft, and it has no legal effect unless and until the Order is adopted in that form and published.
Scope
Under Article 11.1 of Royal Decree 238/2026, the AEAT is the body responsible for developing and managing the public electronic invoicing solution, the Solución Pública de Facturación Electrónica (SPFE). Article 11.2 makes UBL syntax mandatory for those who use the SPFE — a point that matters for any group planning to rely on the public solution rather than a private platform.
The fifth additional provision requires that the SPFE be available at least two months before the first effective application of the royal decree. That is again a relative rule rather than a date. It means the public solution is guaranteed to appear only shortly before the first cohort must comply.
The draft Order, as submitted to public hearing on April 17, 2026, would require the EN 16931 semantic model together with UBL syntax; would define the unique invoice code as the combination of the issuer's NIF, the invoice number, the series and the issue date; would allow a four-day grace period in the event of technical incidents; and would provide access through Cl@ve or electronic certificates. All of this is draft content and may change before adoption.
Two points frequently reported as Spanish policy are not supported by any official source and are not stated here as fact. The first is a phase-in of October 1, 2027 and October 1, 2028. Those dates are simply October 1, 2026 plus twelve and twenty-four months — arithmetic performed on a draft provision, not an official calendar. The second is an SPFE sandbox or pre-production environment said to open on October 1, 2026; neither Royal Decree 238/2026 nor the draft Order mentions a sandbox or any calendar availability date, and the October 1, 2026 date belongs to the draft Order's entry into force.
Timeline
- March 25, 2026 — Royal Decree 238/2026 approved; published in the BOE on March 31, 2026 as BOE-A-2026-7295, with an AEAT notice the same day.
- April 17, 2026 — draft Ministerial Order submitted by the Ministry of Finance to public hearing and information.
- August 25, 2026 — the Ministerial Order remains unpublished; the twelve-month and twenty-four-month clocks have not started.
- Trigger plus twelve months — effective application for taxable persons with turnover above EUR 8 million in the immediately preceding calendar year, and for the platform obligations in Articles 6, 8, 9 and 13.
- Trigger plus twenty-four months — effective application for all other taxable persons.
- At least two months before first effective application — the SPFE must be available (fifth additional provision).
- Before January 1, 2027 — Verifactu: taxpayers within Article 3.1(a) of Royal Decree 1007/2023 must have adapted systems, as set by Royal Decree-Law 15/2025 of December 2, 2025.
- Before July 1, 2027 — Verifactu: all remaining taxpayers within Article 3.1.
Businesses Affected
Every business issuing B2B invoices in Spain is in scope of the Crea y Crece obligation, with the EUR 8 million turnover test splitting the population into a first and a second cohort. Because the test looks at the immediately preceding calendar year, an entity close to the threshold can move between cohorts, and the cohort is not fixed at the date the Order is published.
Platforms, solution providers and software vendors carry their own obligations under Articles 6, 8, 9 and 13, on the twelve-month clock rather than the twenty-four-month one. Groups that have contracted with a provider should know which of those obligations the provider must meet and on what trigger.
Separately and more urgently, essentially every Spanish business using billing software is affected by Verifactu, whose dates are in force and are not contingent on any further instrument.
Required Actions
- Remove projected calendar dates from your Spain plan and replace them with the trigger. The correct planning statement is “twelve months from publication of the Ministerial Order”, not a date.
- Monitor the BOE for the Order itself rather than following the news cycle. That single publication is what converts the Spanish programme from contingent to dated, and it will start a twelve-month clock immediately.
- Determine which cohort each Spanish entity falls into using Article 121 of Law 37/1992 turnover for the immediately preceding calendar year, and identify entities close to the EUR 8 million threshold that could move.
- Separate Verifactu from Crea y Crece in your programme governance. The Verifactu dates of January 1, 2027 and July 1, 2027 are real, in force, and nearer than anything in the e-invoicing regime.
- If you intend to use the SPFE rather than a private platform, plan for UBL as mandatory under Article 11.2 and for a very short integration window, since the public solution need only be available two months before first application.
- Complete design and vendor selection now and hold execution. Twelve months from an unpredictable trigger is not enough time to begin design work in a group of any size.
- Treat the draft Order's content — EN 16931 with UBL, the NIF-plus-number-plus-series-plus-date invoice code, the four-day technical-incident grace period — as a design assumption to be confirmed on adoption, not as a specification.
Practical Implications
The most common planning error in Spain at present is treating October 1, 2027 and October 1, 2028 as deadlines. They are not deadlines; they are arithmetic performed on a draft provision. If the Ministerial Order is published in January 2027 rather than taking effect on October 1, 2026, every downstream date moves by three months. If it slips further, so does everything else. A programme plan anchored to those dates will be wrong in a direction nobody can predict.
The right way to read Spain is as a trigger-driven programme rather than a date-driven one, and that changes the risk profile rather than reducing it. A twelve-month clock that starts without warning is harder to manage than a long fixed deadline, because the point of maximum uncertainty is also the point at which execution must begin. Groups that wait for the Order before starting design will spend the first three or four months of a twelve-month window on analysis they could have done in 2026.
There is also a resourcing distortion worth naming. Attention in Spain has concentrated on B2B e-invoicing, which is contingent, while Verifactu is certain, in force, and falls due on January 1, 2027 for the first cohort. In our experience the groups most exposed in Spain today are those that have a detailed e-invoicing roadmap and an underspecified Verifactu position.
Finally, the SPFE availability rule deserves attention from anyone planning to use the public solution as a cost-saving alternative to a private platform. A solution guaranteed to exist only two months before the obligation bites is not a solution a large group can integrate against on a controlled schedule, and Article 11.2 removes format flexibility by making UBL mandatory for its users. For most multinational groups the practical answer remains a private platform, with the SPFE as a fallback rather than a primary route.
Expected Next Steps
Publication of the Ministerial Order in the Boletín Oficial del Estado is the single event to watch, and it should be treated as a standing monitoring item rather than an expected date. Adoption in the form put to public hearing would also confirm the EN 16931 and UBL baseline, the invoice code construction and the four-day incident grace period.
The AEAT also runs technical sessions for developers through its Desarrolladores portal, and a session concerning the SPFE is listed there for September 10, 2026. KGT was unable to open that page to confirm when it was announced or its current content, so readers should check the portal directly rather than rely on secondary reports of its agenda.
How Can KGT Support You?
KGT is a specialist indirect tax technology firm working exclusively inside the SAP landscape. We deliver SAP-integrated e-invoicing add-ons for countries where a local mandate outpaces the standard SAP roadmap, and we implement and run SAP Document and Reporting Compliance (SAP DRC) where the standard solution is the right answer. Because we build and operate both, our advice on which route to take for a given country is not a sales position.
For the development described above, KGT typically helps clients in four ways: assessing the impact on the existing SAP configuration and interface build; carrying out the mapping and regression work against the current official specification version; managing the platform, provider or registration dependency; and running the resulting flows as a managed service, so that each release, schema version and validation change is absorbed for you rather than by you. To discuss what this means for your SAP landscape, contact KGT at
This publication is provided for general informational purposes only and does not constitute tax, legal, or professional advice. Please consult your advisor before acting on any information contained in this update.
