E-invoice requirements and how to issue one
A valid B2B e-invoice is a structured message following the European EN 16931 model (in UBL, CII, EDIFACT or Facturae syntax) that carries the data of an ordinary invoice and is exchanged through the Spanish Tax Agency (AEAT) public solution or through interconnected private platforms, with a true copy to the AEAT and reporting of its status and payment (RD 238/2026).
What the obligation is and who it applies to: B2B e-invoicing.
From when these requirements apply
| Who | Date | Status | Rule |
|---|---|---|---|
| B2B e-invoicing: turnover over €8M | 6 Oct 2027 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
| B2B e-invoicing: all other businesses and professionals Invoice statuses optional until 6 October 2029 for individuals and pass-through entities up to €8M. | 6 Oct 2028 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
This is not advice: each taxpayer determines what applies to them with their adviser.
Requirements of a B2B e-invoice
| Requirement | What it means | Rule |
|---|---|---|
| Structured format | European EN 16931 semantic model in an accepted syntax. See E-invoice format. | RD 238/2026 |
| Invoice content | The data of an ordinary invoice. | RD 1619/2012 |
| Exchange | Through the AEAT public solution or a private platform interconnected with the others. | RD 238/2026 |
| True copy | Whoever does not issue through the public solution also sends the AEAT a true copy of each invoice, in UBL syntax and the EN 16931 model. | RD 238/2026, art. 6.2; Order HAC/1028/2026, art. 4 |
| Statuses and payments | The recipient reports acceptance or rejection and payment. See E-invoice status tracking. | RD 238/2026 |
| Unique identification | Each invoice is identified by the issuer’s NIF, the series and number, and the issue date. | RD 238/2026, art. 7.5; Order HAC/1028/2026, art. 6 |
| Entry point | If you receive through a private platform, publish it in your communications and on your website; if you do not, your entry point is the public solution. | RD 238/2026, art. 6.3 |
| Simplified invoices | Outside the obligation, except qualified simplified invoices. | RD 238/2026, art. 4.1 |
What data it must contain
The same as an ordinary invoice under the Invoicing Regulation (RD 1619/2012): what changes is that the data sit in the fields of a structured format, not in a document meant to be read.
How to issue and send an e-invoice
The system is mixed. An invoice can travel in three ways:
- The AEAT public solution, free of charge.
- A private exchange platform, interconnected with the others and with the public solution; in this case the true copy is also sent to the AEAT.
- A mix of both.
Interconnection and interoperability between platforms are free.
Which program or platform do I need?
To choose one, check that the program or platform:
- issues and receives invoices in a structured format (EN 16931 in an accepted syntax);
- interconnects with the other platforms and with the public solution;
- sends the true copy to the AEAT when the public solution is not used;
- handles invoice statuses and payments.
The AEAT offers a free option: The AEAT public e-invoicing solution. A PDF is not an e-invoice, even if it is sent by email.
Does it have to be signed?
Yes, if it is issued through a private platform: it carries an advanced electronic signature, the issuer’s or a delegated one (RD 238/2026, art. 7.3). If it is issued or exchanged through the public solution, the AEAT’s own procedures guarantee authenticity and integrity (art. 11.7).
If you have your own software: connect it through an API
Keep your ERP or invoicing program and add the compliance layer through an 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.
Proven reliability
Hundreds of companies and software vendors in production with Verifacti. Data hosted in the EU and an SLA in the terms of use.
AEAT social collaboratorSpecialists in Spain
Common and foral territory: Verifactu, TicketBAI and SII with one provider.
TicketBAI guarantor software in Álava, Bizkaia and GipuzkoaBuilt for developers
Public documentation with examples for every call, quick start guide, Postman collections, llms.txt and a free account with a test environment.
Typical integration: one to three developer daysQuestions about the requirements
How is an e-invoice filed with the tax authorities?
Is it safe to use online invoicing software?
Are there programs authorised or certified by the AEAT?
Does a PDF invoice meet the requirements?
Official sources
Create your free account
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.