Implementing e-invoicing in Spain: steps for your company

Implementing B2B e-invoicing in a company means deciding how invoices will be issued and received (the AEAT public solution, a private platform or your own ERP connected through an API), adapting the software to the EN 16931 structured format, preparing reception and the reporting of statuses and payments, and testing it all before the dates set by RD 238/2026 and Order HAC/1028/2026: 6 October 2027 for businesses with a turnover over €8M and 6 October 2028 for everyone else.

This page is part of the B2B e-invoicing guide.

Your deadline

B2B e-invoicing: turnover over €8M6 Oct 2027
Published in the BOE, future date
B2B e-invoicing: all other businesses and professionals6 Oct 2028
Invoice statuses optional until 6 October 2029 for individuals and pass-through entities up to €8M.
Published in the BOE, future date

This is not advice: each taxpayer determines what applies to them with their adviser.

Companies with a turnover between €6M and €8M are already in the SII, but their e-invoicing date is 6 October 2028, not 2027.

Steps to implement e-invoicing

  1. Turnover and date. Last year’s turnover decides whether your date is 2027 or 2028.
  2. Systems inventory. Which programs issue invoices and which receive them: ERP, invoicing, POS, supplier portals.
  3. Choose the route. The public e-invoicing solution, a private platform or an API connected to your ERP. They can be combined.
  4. Format and master data. Adapt customer, product and tax data to the EN 16931 model. More in E-invoice format.
  5. Reception. Prepare your system to take in your suppliers’ invoices. Decide where you receive and publish your entry point; if you do not publish it, you receive through the public solution (RD 238/2026, art. 6.3).
  6. Statuses and payments. Prepare the reporting of acceptance, rejection and payment of the invoices you receive.
  7. True copy. If you do not issue through the public solution, send the AEAT a true copy of each invoice.
  8. Testing. Issue and receive test invoices with your main customers and suppliers. The AEAT already has web services and a validator on its external testing portal.
  9. Go-live. Move to production before your date.

What the rules require, point by point, in E-invoice requirements.

Issuing: what changes in your software

Your software has to generate each invoice to other businesses in a structured electronic format (EN 16931 model) and deliver it through the chosen route: a private platform or the public solution. If you issue through a private platform, a true copy of each invoice is also sent at the same time to the public solution, in UBL syntax (AEAT, analysis of 29 October 2026). Format details in E-invoice format.

If your turnover is over €8M, for the first twelve months you send a legible PDF with each e-invoice, unless the customer accepts the original format only (RD 238/2026, second transitional provision).

Receiving: invoices from your suppliers

The obligation is to issue and to receive. Your suppliers will send you e-invoices through their platform or the public solution, and platforms interconnect with each other free of charge. Your system has to be able to receive them and bring them into your accounts.

Statuses and payments

Whoever receives an invoice reports whether they accept or reject it and when they pay it in full, with the date. From when and within what period in E-invoice status tracking. Individuals and pass-through entities with up to €8M can report statuses voluntarily until 6 October 2029.

How long it takes

It depends on how many systems issue and receive invoices and on the route chosen: there is no figure that fits every company. If your turnover is over €8M, yours is the first date, 6 October 2027: it is worth starting now.

Finance (processes, master data, statuses and payments), IT (systems and integrations) and your software or platform providers all take part.

Implement it from your own software

If your turnover is over €8M, it reaches you before anyone else. Prepare it with a specialist in Spain and bring your SII too with the SII API.

The E-invoicing API is coming soon, with no date or price yet. If you already use the NIF management API for Verifactu, TicketBAI or SII, that integration carries over: the E-invoicing API will build on that common layer and will have a test environment in the free account, like the others. Today you can open the free account and read the documentation of the available APIs; NIF management is available with a subscription.

Test environment and test NIF included

Questions about implementation

Can I keep my ERP?

Yes. You can connect your ERP to a platform or an API, or use the AEAT public solution.

How is it integrated in SAP or Microsoft Dynamics?

Like any other ERP: with a connector to a platform or an API. See SAP and Business Central.

What about our customers’ legacy applications?

It depends on how they connect today. If they already use one of our APIs, the NIF management API is the common layer; the capabilities of the E-invoicing API have not been published yet.

Do I have to receive e-invoices even if I do not issue them?

Yes. The obligation is to issue and receive. If you have not published an entry point or agreed a private platform with your suppliers, you receive through the AEAT public solution (RD 238/2026, art. 6.1 and 6.3).

Create a free account for your tech team

Your team can try the available APIs today in the test environment, with a test NIF. The NIF management API, the common layer the E-invoicing API will build on, is available with a subscription.

Test environment and test NIF included