odoobarcelona
← Back to the blog
GUIDE

B2B e-invoicing in Spain: the rules are in force, the date isn't

Who will be covered, in which formats and through which channel — and why, as of 17 September 2026, there is still no firm date: it hinges on a ministerial order that has not been published.

There is an obligation to invoice electronically between companies and self-employed professionals in Spain, its regulation has been published in the official gazette since March 2026, and it still has no start date. All three things are true at once, and understanding why is what will save you from rushing to buy something you don't need yet.

The regulation is already published. The calendar isn't: the deadlines don't run from the royal decree, but from a ministerial order that, as of 17 September 2026, has still not appeared in the official gazette.

What mandatory e-invoicing is (and why a PDF isn't it)

The obligation comes from article 12 of Law 18/2022, on the creation and growth of companies — the «Crea y Crece» act — which rewrote article 2 bis of Law 56/2007: «All entrepreneurs and professionals must issue, send and receive electronic invoices in their commercial relations with other entrepreneurs and professionals». It adds that issuer and recipient must report on the invoice's statuses, which is the part almost nobody explains.

What the rules mean by «electronic» is not what most people mean: article 7.1 of Royal Decree 238/2026 requires a structured electronic message conforming to the EN 16931 semantic data model.

  • A PDF attached to an email is not an electronic invoice for these purposes, however well signed it is. It is a picture of an invoice: the recipient's computer cannot read it without interpreting it.
  • An electronic invoice is a file that another program reads and books without anyone retyping anything.
  • So the obligation isn't «email the invoice»: it is changing the format and the channel.

And the reason behind it is not tax collection. The law that imposes it is about business growth and its stated target is late payment: article 14 of the regulation says the tax agency will send, in the first quarter of each year, the information the State Observatory on Private Late Payment needs to compile the list of companies that missed their payment deadlines.

The dates: as of 17 September 2026 there is not a single firm one

Law 18/2022 set two conditions on its own entry into force. The first was an EU derogation from articles 218 and 232 of the VAT Directive, and it has already been met: Directive (EU) 2025/516 — the «ViDA» package — of 11 March 2025 allows member states to impose electronic invoicing without asking permission and without the recipient's consent. The second was the implementing regulation, and that one is half done.

MilestoneWhat it saysStatus on 17-09-2026
RD 238/2026, of 25 MarchDevelops the Spanish e-invoicing system; in force 20 days after publication (gazette, 31-03-2026)Published and in force
Order of the Ministry of Finance (3rd final provision, 1)Sets the technical details of the public solution; its entry into force starts the clockNot published in the gazette
12 months from that orderTurnover above €8M in the previous calendar year (4th final provision, 1.a)No date
24 months from that orderEvery other entrepreneur and professional (4th final provision, 1.b)No date

The draft of that order does exist: it went out for public consultation on 17 April 2026 and its sole final provision set its entry into force at 1 October 2026. If it were published as it stands, the dates would be 1 October 2027 and 1 October 2028. But it is a draft: the consultation closed on 8 May and the final text has still not reached the gazette.

A draft order is not an order. Until it is published, any date you read is a forecast, not a deadline.

The tax agency says as much itself: its note on mandatory electronic invoicing, last updated on 1 September 2026, still refers the count to the entry into force of that order, without giving any date.

Why every website gives you a different date

Because each one froze a different moment. Some still give 2024 or 2025, from when the regulation did not yet exist. Some give 1 October 2027 and 2028 as if they were firm, taking the draft for published law. And many give 2026 because they confuse this with VeriFactu. Always check the date of what you are reading, including this page's.

VeriFactu and B2B e-invoicing: two obligations that meet at one point

VeriFactu (RD 1007/2023)B2B e-invoicing (RD 238/2026)
What it governsHow your software generates and keeps each invoiceIn which format and through which channel you send it to another business
Where it hangs fromArt. 29.2.j) of the General Tax ActArt. 2 bis of Law 56/2007, as written by Law 18/2022
What forSo that an issued invoice cannot be erasedTo know when each invoice is paid and make late payment visible
When1 January and 1 July 2027No date: 12 or 24 months from an unpublished order
With consumersAlso coveredNo: only between entrepreneurs and professionals

The point where they meet is in the definition in article 2.d) of RD 238/2026: the mandatory electronic invoice must be produced by software «adapted to article 29.2.j) of Law 58/2003 [...] and, where applicable, to its implementing regulation». That implementing regulation is VeriFactu, and article 2 bis.6 of Law 56/2007 says the same thing on its own account.

You will not be able to comply with B2B e-invoicing using software that doesn't comply with VeriFactu. Two obligations, but a single program.

In practice: the first date that affects you is not the e-invoicing one — which does not exist — but the VeriFactu one, which is 2027. If your software is adapted for VeriFactu, the other obligation will arrive as an extension rather than a house move.

Who it will cover, and who is left out

Article 3.1 puts it like this: whoever is required to issue an invoice under the invoicing regulation must do so electronically when the recipient is an entrepreneur or professional with a business seat, permanent establishment or address in Spain.

  • Invoices to end consumers are not covered: the obligation is between entrepreneurs and professionals.
  • Simplified invoices — the till receipt — are not covered either, except for the qualified simplified invoices of article 7.2 of the invoicing regulation (art. 4.1).
  • A few very specific activities are left out (2nd additional provision): the electricity market operator, the organised gas market operator and the IATA clearing houses.
  • If a third party invoices on your behalf — an accountancy firm — the obligation is not transferred: whoever is required to issue the invoice «shall be responsible for complying with all the obligations» (art. 3.2).
  • In the Basque Country and Navarre, the public solution will be arranged through agreements between the regional tax authorities and the state tax agency (3rd additional provision).

Size does not decide whether it applies to you: it decides when. Twelve months if your turnover exceeded €8 million the previous year; twenty-four for everyone else. A self-employed professional is covered just the same, only later.

Which formats the rules accept

Article 7.1 accepts four syntaxes, all on top of the EN 16931 model: CII (the UN/CEFACT XML messages), UBL, the EDIFACT invoice message and the Facturae message, the one you already use if you invoice public bodies. On top of that there are two requirements you don't see but that decide whether your software is up to the job:

  • Every invoice issued through a private platform must carry an advanced electronic signature, either directly or through authorised delegated signing (art. 7.3).
  • Each invoice must be identified by a unique code that necessarily includes the issuer's tax number, the invoice number and series, and the issue date (art. 7.5).

The public solution only accepts UBL (art. 11.2); if your platform works in another syntax, the conversion is on your side (art. 11.6). And during the first twelve months, anyone above €8 million will have to send the invoice together with a PDF ensuring its legibility, unless the recipient expressly agrees to the original format — and that PDF is not sent to the public solution (2nd transitional provision).

Invoice statuses: the obligation almost nobody talks about

This is the part that turns the change into a process change and not just a format change. Sending the invoice is not enough: you have to say what happens to it, and that falls on whoever receives it.

  • Mandatory (art. 10.1): commercial acceptance or rejection of the invoice with its date, and full effective payment with its effective payment date.
  • Optional (art. 10.2): partial acceptance or rejection, partial payment, and assignment of the invoice to a third party.
  • Deadline: four calendar days, excluding Saturdays, Sundays and national holidays, from the moment the status occurs (art. 10.3).
  • Full payment or rejection is always reported to the public solution, whichever platform was used, along with the payment due date (art. 12). In the absence of a rejection, the invoice is presumed accepted.

There is some breathing room for the smallest: for natural persons and income-attribution entities not above €8 million, statuses stay voluntary until twelve months after the regulation takes effect for the second tranche (3rd transitional provision).

Invoicing will mean sending a file. Getting paid will mean declaring that you were paid, within four working days. The second part is the one that changes daily work.

The tax agency's public solution, and what a private platform cannot charge you for

The Spanish e-invoicing system is made up of the private platforms that meet the requirements plus the public solution, run by the tax agency, which also acts as a repository (art. 5). You can invoice through one route, the other, or a combination.

  • Access to the public solution and the uses the regulation provides for are free (art. 11.10), and the tax agency will build into it a free form for issuing invoices and reporting their statuses (1st additional provision).
  • It is the universal and mandatory repository of every invoice (art. 2.f): anyone issuing through a private platform must send it a faithful electronic copy in UBL simultaneously with issuance (art. 6.2).
  • If you have not expressly agreed to receive invoices through a private platform, or if you don't publish your entry point, your entry point is the public solution (arts. 6.1 and 6.3).
  • It must be available at least two months before the first effective application (5th additional provision). That will be the real signal that this is happening.

And one thing worth knowing before anyone sells you anything: a private operator is required to interconnect with any other platform when one of its clients asks, has a maximum of one month to make it work, and «in no case» may charge the requesting platform for doing so (arts. 8.1, 9.3 and 9.6). Article 2 bis.3 bis of Law 56/2007 adds that «the recipient of the invoice may not require its issuer to use a predetermined e-invoicing solution, platform or service provider».

If you invoice public bodies, that has been mandatory for years

Electronic invoicing to the public sector is nothing new: Law 25/2013 has required it since 15 January 2015. It is not the same rule, nor the same circuit, nor the same people covered.

  • Covered are public limited and limited liability companies, legal persons and entities without legal personality that lack Spanish nationality, permanent establishments and branches of non-residents, temporary business partnerships and certain funds (art. 4.1). A self-employed professional may issue one, but the law does not require it.
  • Public administrations «may exclude by regulation» invoices of up to €5,000 (art. 4.1). It is a power each administration has, not a universal exemption.
  • Format: structured and signed with an advanced electronic signature based on a recognised certificate (art. 5.1). In practice, Facturae; the Catalan government requires version 3.2.
  • Channel: the relevant general entry point (art. 6). FACe for central government; e-FACT for the Catalan government and the Catalan bodies that have joined it.
  • The DIR3 codes — accounting office, managing body and processing unit — are what makes the invoice reach an actual person. Set wrong, the invoice isn't rejected: it gets lost, and you think it is being processed.

This will still exist when the business-to-business obligation arrives. They are two circuits for two different recipients, and the reason they should come out of the same place is obvious: so you don't keep two parallel sets of books for the same invoicing.

What your software has to be able to do

Five questions to your supplier, in writing, and you already know where you stand:

  • Which of the four syntaxes in article 7.1 it issues in, and whether it can convert between them or depends on a third party.
  • Whether it can send the faithful UBL copy to the public solution at the moment of issuing (art. 6.2), or whether that will be an overnight batch. The regulation says «simultaneously».
  • How it will handle statuses: who marks the payment, where the effective date comes from, and whether it fires automatically from the booked payment or has to be typed in invoice by invoice.
  • Whether it is already adapted to article 29.2.j) of the General Tax Act, that is, to VeriFactu. That date is 2027 and does not depend on any pending order.
  • What it costs: whether the adaptation is included in the maintenance fee or is a separate project.

We implement Odoo, and of the four editions there are two we build and maintain here: Community Plus and Agentic ship with VeriFactu and SII integrated and verified as standard. The business-to-business e-invoicing part we will close as the technical specification gets published; announcing it before it exists would be selling smoke, and there is plenty of that around.

What you can do today without waiting for the order

  • Adapt your software for VeriFactu. That is the date that does exist, and it is exactly the same program that will later have to do the other thing.
  • Clean up your master data: tax number, legal name and address for every customer. A structured invoice gets rejected over a mistyped tax number; a PDF said nothing and somebody just fixed it.
  • If you invoice public bodies, sort that circuit out now — Facturae, e-FACT or FACe, DIR3 codes. It is the dress rehearsal for what's coming.
  • Ask your three biggest customers which platform they plan to receive through. If they are above €8 million, they will start a year before you.
  • Don't sign anything «for mandatory e-invoicing» against an invented deadline: the technical specification that product will have to meet is not published yet.

The pressure will come from your big customer, not from the gazette: whoever is above €8 million starts a year earlier and will ask you for structured invoices from day one.

Frequently asked questions

When does mandatory B2B e-invoicing come into force?

There is no date. RD 238/2026 has been in force since 20 April 2026, but its effective application is counted from the entry into force of an order of the Ministry of Finance that, as of 17 September 2026, has not been published: twelve months later for those above €8 million and twenty-four for everyone else.

Does a signed PDF count as an electronic invoice?

For this obligation, no. It has to be a structured message in CII, UBL, EDIFACT or Facturae, conforming to the EN 16931 model (art. 7.1). The PDF in the second transitional provision accompanies the invoice during the first twelve months; it does not replace it.

Does it affect the self-employed?

Yes, if they invoice another entrepreneur or professional, and they will fall into the second tranche, at twenty-four months. Invoices to consumers and simplified invoices are out, and invoice statuses stay voluntary for them a while longer (3rd transitional provision).

Is it the same as VeriFactu?

No. VeriFactu governs how your software generates and keeps invoices, and its dates are 1 January and 1 July 2027. This governs the format and the channel between businesses and has no date yet. They meet at one point: the mandatory electronic invoice has to come out of a system adapted to article 29.2.j) of the General Tax Act, which is what VeriFactu develops.

What is the fine if I don't do it?

RD 238/2026 brings no sanctions regime of its own. The fine of up to €10,000 that gets quoted so often is the one in article 2 bis.9 of Law 56/2007, and it punishes something else: companies that are required to, and fail to, offer their users the option of receiving electronic invoices, or that deny access to their invoices to someone who is no longer a customer. The real risk, when the deadline arrives, is more mundane: without an electronic invoice you won't get paid by anyone required to receive one.

What if my customer uses a different platform?

It has to interconnect with yours if one of its clients asks, within one month at most and without charging your platform for it (arts. 8.1, 9.3 and 9.6). And it cannot force you to use theirs (art. 2 bis.3 bis of Law 56/2007).

Keep reading