Verifactu vs e-invoicing: the difference
Verifactu and B2B e-invoicing are separate obligations that add up: Verifactu (RD 1007/2023) requires invoicing software to generate tamper-proof records and, in the VERI*FACTU mode, send them to the AEAT; B2B e-invoicing (RD 238/2026) requires invoices between businesses to be issued and received in a structured electronic format. A company in common territory that invoices other businesses will have to comply with both.
Each has its own guide: Verifactu and B2B e-invoicing.
Dates of each obligation
| Who | Date | Status | Rule |
|---|---|---|---|
| Corporate Income Tax payers | 1 Jan 2027 | Published in the BOE, future date | RDL 15/2025 |
| Everyone else, including the self-employed | 1 Jul 2027 | Published in the BOE, future date | RDL 15/2025 |
| Postponement of the pending obligations The note does not specify the scope for businesses invoicing over €8M. | Oct 2028 | Announced, no rule published | Nota de Hacienda, 5 oct 2026 |
| 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.
Verifactu and e-invoicing side by side
| Verifactu | B2B e-invoicing | |
|---|---|---|
| What it regulates | How the software that issues invoices works: tamper-proof, chained invoicing records. | The structured format of the invoice and its exchange between businesses. |
| Who | Companies and self-employed people in common territory who invoice with a computer system, except SII and foral territories. | Every business or professional in domestic B2B transactions, across Spain. |
| What is sent, and to whom | In the VERI*FACTU mode, each invoicing record to the AEAT. | The invoice to the customer, through a private platform or the public solution; without the public solution, a true copy to the AEAT. |
| Format | Invoicing record in XML with the AEAT format. | Structured electronic invoice under the European EN 16931 model. |
| QR | Yes. An e-invoice only needs the QR URL as its own field, not the image (Order HAC/1177/2024, art. 20.2). | Not a requirement of e-invoicing itself. |
| Dates | 1 Jan 2027 (CIT) and 1 Jul 2027 (others), published in the BOE; postponement to Oct 2028 announced with no rule. | 6 Oct 2027 (over €8M) and 6 Oct 2028 (others), published in the BOE. |
| Rule | RD 1007/2023 and RDL 15/2025 | Law 18/2022, RD 238/2026 and Order HAC/1028/2026 |
Do you have to comply with both?
They add up. B2B e-invoicing applies to every business or professional in their transactions with other businesses, and being in Verifactu does not exempt anyone from it. A company in common territory that invoices other businesses with a computer program falls under both rules: each invoice generates its Verifactu record and is also issued as an e-invoice.
RD 238/2026 itself links them: a mandatory e-invoice has to be produced by a computer system adapted to article 29.2.j) of the General Tax Law and its implementing regulation, which is what regulates Verifactu (art. 2.d).
This is not advice: each taxpayer determines what applies to them with their adviser.
How their dates relate
The Verifactu dates published in the BOE come before the e-invoicing ones. The Ministry of Finance note of 5 October 2026 announces the postponement of Verifactu to October 2028 and links it to e-invoicing for businesses with a turnover up to €8M; it does not specify the scope for those above that figure. It is an announcement with no rule published: until it appears in the BOE, the Verifactu dates in force are those of RDL 15/2025.
What about the SII and TicketBAI?
SII. Whoever keeps their books through the Immediate Supply of Information (SII) is outside Verifactu, but not outside e-invoicing. More in SII and Verifactu.
TicketBAI. In Álava, Bizkaia and Gipuzkoa, TicketBAI replaces Verifactu, not e-invoicing. More in Verifactu in the Basque Country.
Both with the same provider
With the Verifactu API you send the invoice as JSON today and get the QR straight away. If you already use the NIF management API for Verifactu, it will also serve for e-invoicing: you will only add the sending integration of the E-invoicing API (coming soon, with no date or price yet).
Questions about Verifactu and e-invoicing
Is Verifactu e-invoicing?
Do I have to comply with Verifactu and e-invoicing?
What does the Crea y Crece Law have to do with Verifactu?
I already have Verifactu integrated through an API. Does it work for e-invoicing?
Does an e-invoice carry a QR like Verifactu?
AdditionalDocumentReference with urn:aeat:names:specification:schema:QR).Create your free account
Try the Verifactu API 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.