Royal Decree 238/2026: e-invoicing rules for advisers
by Ivor Padilla
Co-Founder & Engineering Director
Royal Decree 238/2026: e-invoicing rules for advisers
If you advise Spanish SMEs from London, Dublin, or Madrid (or you sit on the compliance team of a European firm tracking the Spanish rollout), Royal Decree 238/2026 is the piece of legislation that turns three years of speculation into actual rules. It is the implementing regulation that finally puts technical detail behind Spain's Crea y Crece (Create and Grow) Act, and it landed in the Official State Gazette (BOE) on 31 March 2026.
The regulation is short by Spanish legal standards (twenty-three pages), but every paragraph has direct operational consequences for any professional who issues invoices to a business client based in Spain. This guide walks through what the decree actually says, what it does not say (the headlines this week are getting at least one important detail wrong), and what an advisory firm should be doing for itself and for its client portfolio in the months between now and the start of the compliance clock.
TL;DR: Royal Decree 238/2026, of 25 March, implements mandatory B2B e-invoicing in Spain under Article 12 of the Crea y Crece Act. Published in BOE no. 79 on 31 March 2026 and in force from 20 April 2026, but the 12-month (large firms) and 24-month (SMEs and self-employed) compliance clocks only start once a still-pending ministerial order is published. The decree pins the format to the European EN 16931 standard, accepts four syntaxes (CII, UBL, EDIFACT and Facturae), and sets up a mixed system where firms can use either a free public AEAT solution or an interoperable private platform. The free AEAT route exists; cost is not a blocker.
What Royal Decree 238/2026 actually does (and what it does not do yet)
Royal Decree 238/2026 is the implementing regulation for mandatory B2B e-invoicing in Spain. It defines the technical and operational framework (formats, public solution, private platform requirements, interoperability), but it does not, by itself, switch the obligation on. That part depends on a separate ministerial order that is still pending.
The obligation for B2B e-invoicing between Spanish businesses and professionals did not start with Royal Decree 238/2026. It started with Article 12 of Law 18/2022, of 28 September, on the creation and growth of companies, known in Spain as the "Crea y Crece" Act, which amended Article 2 bis of Law 56/2007 to require every entrepreneur and professional to issue, send and receive electronic invoices in their dealings with other businesses. Crea y Crece set out the what; Royal Decree 238/2026 now sets out the how.
The distinction matters because of the timing. The Crea y Crece Act was passed in September 2022 but its e-invoicing obligation has been suspended ever since, waiting for the implementing regulation that has now landed. RD 238/2026 fills that gap on the technical side. The remaining gap (between the regulation being on the books and the compliance clock actually starting) is the publication of a ministerial order. Until that order appears, the regulation is in force but the duties are not yet enforceable.
Scope: who is in and who is out
The first thing to determine for any client is whether they fall within scope. The test is purely about establishment in Spain plus the B2B nature of the transaction. There is no turnover threshold and no carve-out by tax regime.
Article 3 of Royal Decree 238/2026 sets out the scope of mandatory e-invoicing: any entrepreneur or professional who is already required to issue an invoice for their business operations must do so in electronic format whenever the recipient is itself a business or professional with a registered office, permanent establishment, domicile or habitual residence in Spain. In operational terms: if your client is a company or a self-employed worker operating from Spain, the invoice has to be electronic, with only the exceptions the regulation itself recognises (simplified invoices under RD 1619/2012 and residual edge cases).
A few practical consequences for cross-border advisers worth flagging early:
- Nationality is irrelevant. A British developer registered as autónomo in Madrid invoicing a Spanish tech company is in scope on the same basis as a Spanish national. So is an Irish consultant working on a permanent establishment basis in Barcelona.
- The recipient's location is the trigger. A Spanish firm invoicing a French or German client is not in scope of RD 238/2026. That is a cross-border transaction, governed by other rules.
- There is no €85,000 exemption. This figure is doing the rounds in expat groups and even some accounting newsletters. It does not appear anywhere in the BOE text. The only genuine exemption is for transactions that qualify as a simplified invoice under RD 1619/2012, which generally rules out B2B work.
The real timetable: in force, not yet enforceable
The most common mistake this week is reading "20 April 2026" as the date the obligation begins. It is not. Two clocks run in parallel: the regulation enters into force on that date, but the compliance deadlines for issuers only start ticking once a separate ministerial order is published.
Royal Decree 238/2026, of 25 March, was published in Spain's Official State Gazette (BOE) no. 79 on 31 March 2026, and came into force on 20 April 2026, twenty days after publication. Coming into force is not the same as being enforceable: Final Provision Four of the decree itself states that effective application is deferred until the ministerial order developing the AEAT's public e-invoicing solution is published. That is the detail most trade-press headlines are glossing over.
Once the ministerial order is published, the obligations under RD 238/2026 are phased in: 12 months for entrepreneurs and professionals whose turnover in the previous calendar year exceeded €8 million, and 24 months for everyone else. In practice: large firms get one year from the day the order lands; SMEs, the self-employed and most professional services firms get two.
As at the date this article is published, the ministerial order setting out the technical details of the AEAT's public e-invoicing solution has not yet been published. That order is, according to Final Provision Four of RD 238/2026 itself, the milestone that starts the 12- and 24-month clocks after which the obligation becomes enforceable. Until the order appears in the BOE, the regulation is in force but not yet enforceable. Check the AEAT's 2026 VAT regulatory updates page for the current status before finalising any rollout plan.
In tabular form, the calendar your clients should be looking at:
| Date / event | Who it affects | What it means |
|---|---|---|
| 31 March 2026 | Everyone | RD 238/2026 published in BOE no. 79 |
| 20 April 2026 | Everyone | RD enters into force; obligations deferred |
| Ministerial order published (pending, est. Q2–Q3 2026) | Everyone | 12- and 24-month compliance clocks start |
| Order + 12 months | Turnover > €8M | E-invoicing enforceable |
| Order + 24 months | SMEs, self-employed, all others | E-invoicing enforceable |
For the median Spanish SME and the median advisory firm advising it, the realistic enforceable deadline is mid-2028 at the earliest, assuming the ministerial order arrives mid-2026. There is genuine time to prepare, and the case for panic-purchasing software this quarter is weak. The case for systematic auditing of the client base now, however, is strong. More on that below.
The four formats: CII, UBL, EDIFACT and Facturae
Article 7 of the regulation pins the e-invoice to the European EN 16931 standard and recognises four valid syntaxes. Peppol BIS, often mentioned alongside these, is not a fifth independent format. It is recognised as valid in private platforms because it uses the UBL syntax and conforms to EN 16931.
Article 7 of RD 238/2026 pins the semantic model of the e-invoice to the European standard EN 16931 and accepts four syntaxes: CII, UBL (with adaptations for B2B), EDIFACT and Facturae. For private exchange platforms, the preamble also recognises messages in Peppol BIS format as valid, since they use the UBL syntax and conform to EN 16931. So Peppol BIS is not a fifth format but a specific UBL profile with its own addressing scheme. In practice, the two syntaxes an average Spanish firm will encounter are Facturae (the legacy format used for public-sector invoicing) and UBL/Peppol BIS (the European route).
For a UK or Irish adviser, the practical takeaway is that any client already using Peppol on the European market has a head start: the underlying syntax travels. For an English-speaking lawyer or consultant in Spain who has only ever issued PDF invoices through Holded, A3, or Contasimple, the question to ask the software provider is simple: "Will your tool export Facturae or UBL by the compliance deadline, and is that included in my current plan?" In most cases the answer will be yes.
The mixed system: AEAT public solution plus private platforms
RD 238/2026 sets up two parallel routes for issuing and receiving e-invoices: a free public solution operated by the Spanish Tax Agency (AEAT), and any private exchange platform that meets the regulation's technical requirements. Use of a private platform is optional; the copy to the public solution is not.
RD 238/2026 sets up what the market is already calling a "mixed system": every obligated business or self-employed worker can choose between using the public e-invoicing solution developed and run by Spain's Tax Agency (Article 11) on a voluntary basis, or any private exchange platform that meets the regulation's technical requirements. The public solution also plays a role no private platform can take on: it acts as a universal, mandatory repository for every electronic invoice issued in Spain, even those routed through private channels (Article 2, definitions). In other words: the private platform is optional; the copy to the public solution is not.
This dual nature is the part most market commentary glosses over. A Spanish firm cannot opt out of the public system simply by contracting a private platform. The private platform itself is required to forward a faithful copy of every invoice to the AEAT's solution. That makes the public solution the de facto registry of B2B invoicing activity in Spain, and it is a non-trivial design decision: it gives the tax authority a complete view of B2B trade flows that did not exist before.
Interoperability: no walled gardens
The regulation prevents the market from fragmenting into vendor silos by imposing strict transformation and interconnection duties on private platform operators. For advisers shopping for software on behalf of clients, this translates into a single contractual question.
Interoperability is the mechanism that prevents the market from fragmenting into walled gardens. RD 238/2026 requires private-platform operators to (a) transform invoice messages between admitted formats while preserving authenticity and integrity, and (b) interconnect with any other private platform on the client's request, without being allowed to refuse inbound connection requests. For a firm shopping for software, this boils down to a single practical question: "Does your platform contractually guarantee that it can transform Facturae to UBL and connect to my client's platform, whichever one it is?". If the answer is no, that platform does not meet the regulation.
What this means for advisory firms (and their own invoicing)
A professional services firm (a law firm, an accountancy practice, a consultancy) has a dual exposure to RD 238/2026 that pure-play SMEs do not. It is itself an obligated issuer because it bills B2B clients, and it is the technical adviser to a portfolio of pymes and autónomos who will also be obligated. Both roles need to be planned for.
For the firm's own invoicing, the to-do list is short:
- Audit your invoicing software. Confirm it supports Facturae or UBL export, ideally both. If it does not, start a procurement conversation now. There is no rush, but the longer the runway, the cheaper the switch.
- Map your B2B vs B2C split. The regulation only bites on B2B. If 80% of your invoices already go to business clients, the entire firm's billing flow needs to be e-invoice-ready. If your work is largely consumer-facing (rare for advisory firms, but possible for some niche practices), the impact is narrower.
- Confirm your record-keeping policy. The regulation does not change the underlying invoicing record-keeping rules (invoices still need to be kept for the legal retention period), but the retention now applies to structured electronic files, not paper archives.
For the firm's client portfolio, the work is qualitatively different, and harder.
The portfolio audit: heterogeneity is the real problem
A typical Spanish gestoría manages 200 to 400 SME and self-employed clients. Each one starts from a different place (different software, different volumes, different B2B ratios), and each one will need a different migration path. The work is not technical; it is operational segmentation at scale.
A UK or Irish accountancy firm advising a smaller portfolio of Spanish-resident clients faces the same problem in miniature. The questions are the same:
- Which clients are already equipped? Anyone on Holded, Contasimple, A3, or another Spanish accounting tool with Facturae support enabled is essentially ready. They need a single conversation confirming activation.
- Which clients need a tool switch? Anyone invoicing from Excel, Word, or a non-Spanish stack without UBL or Facturae export needs to choose a replacement. They do not need to choose it tomorrow, but they should start the evaluation before the ministerial order lands.
- Which clients need both a tool switch and a workflow change? Sole traders without a clear distinction between B2B and B2C invoicing (often the case in retail-adjacent services) need help separating their billing flows before the format change matters.
The scope of the rollout is essentially the entire Spanish SME population. The preamble to RD 238/2026 itself reminds readers that pymes account for roughly 99% of Spain's productive fabric, just over 62% of Gross Value Added and 66% of employment. That universe of companies (plus individuals and partnerships under direct estimation or income-attribution regimes) is what will have to adapt, with the more generous 24-month deadline applying to most of them.
In our pilots ingesting electronic invoices for Spanish firms, we have observed that 60–70% of the adaptation effort goes into mapping the heterogeneous formats clients send in, not into the firm's own outbound issuing. The receive side is the operational bottleneck.
How RD 238/2026 differs from VERIFACTU
A frequent point of confusion: VERIFACTU and RD 238/2026 are both 2026 obligations affecting invoicing, but they regulate different things and they are compatible, not in conflict. VERIFACTU (Order HAC/1177/2024) regulates the billing software that records issued invoices and the way they are transmitted to the AEAT. RD 238/2026 regulates the format of the invoice document itself in B2B exchanges. A Spanish firm in 2027–2028 will need to comply with both: VERIFACTU-compliant software issuing invoices in one of the four EN 16931 syntaxes. For the underlying VERIFACTU rules, see our complete guide to VERIFACTU compliance for 2026.
For broader context on the legislative chain that produced this regulation, the Crea y Crece Act guide walks through Article 12 in detail. For the framework guide aimed at firms generally, see our piece on Spain's mandatory B2B e-invoicing in 2026. And for the specific angle of the self-employed worker (the most common single client profile across most advisory practices), see our guide for autónomos on the e-invoicing mandate.
Frequently asked questions about Royal Decree 238/2026
What date did Royal Decree 238/2026 come into force?
The regulation was approved on 25 March 2026 and published in BOE no. 79 on 31 March 2026. Under Final Provision Four, it came into force on 20 April 2026, twenty days after publication. However, the obligation to issue B2B invoices in electronic format is deferred until a separate ministerial order is published.
When do my clients actually have to comply?
The 12-month deadline for businesses with turnover above €8 million and the 24-month deadline for everyone else only start running once the AEAT's ministerial order developing the public e-invoicing solution is published. As of the publication of this article, that order has not yet appeared. Check the AEAT's IVA 2026 regulatory updates page for the current status.
Does the regulation apply to invoices to clients outside Spain?
No. Royal Decree 238/2026 applies when the recipient is a business or professional with their economic activity, permanent establishment, or habitual residence in Spain. Cross-border invoices to other EU member states or to non-EU clients are not in scope of this regulation.
Which formats are admitted?
Article 7 of the regulation admits four syntaxes that conform to the European EN 16931 semantic model: CII, UBL (with B2B adaptations), EDIFACT and Facturae. Peppol BIS is recognised as valid in private platforms because it uses the UBL syntax and complies with EN 16931. It is a UBL profile, not a fifth independent format.
Will my clients have to pay for invoicing software?
Not necessarily. The AEAT will provide a free public e-invoicing solution that any obligated business or professional can use as an alternative to a private platform. Private platforms offer more features and integration but are not mandatory.
What is the difference between RD 238/2026 and VERIFACTU?
VERIFACTU regulates the billing software used to record and transmit invoices to the Tax Agency. RD 238/2026 regulates the format of the invoice document itself in B2B exchanges. They are complementary, not in conflict. Most Spanish firms will need to comply with both.
How we are approaching this at Gradion
Most of the conversations we are having this week with Spanish advisory firms start with the same question: "Do I need to do something about RD 238/2026 today?" Our answer is consistently: not today for compliance, but yes today for portfolio segmentation. The 24-month runway is real, and panic procurement of software in April 2026 is a poor use of budget when the realistic enforceable date is mid-2028.
The piece of work we are building for advisory firms is an anticipated ingestion audit. Rather than wait for the first real e-invoice to arrive at a gestoría's inbox in 2028 and discover that 30% of clients send Facturae files with structural errors, the audit simulates the expected traffic with synthetic invoices in each admitted syntax (valid Facturae, Facturae with common errors, European UBL, Peppol with and without signature) and produces a report telling the firm which client profiles will be processed automatically and which will require manual intervention. Done now, the audit costs a tenth of what it will cost to discover the same heterogeneity reactively.
The same approach works on the issuing side: the firm's own invoicing flow is run against the public solution and against the dominant private platforms, and the report identifies any gap before the ministerial order is even published.
Is your team losing hours every week to manual paperwork and document processing?
We resolve it in 10 days, with a fixed-price pilot.
Tell us about your case →
