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

Corporate Income Tax payers1 Jan 2027
Published in the BOE, future date
Everyone else, including the self-employed1 Jul 2027
Published in the BOE, future date
Postponement of the pending obligationsOct 2028
The note does not specify the scope for businesses invoicing over €8M.
Announced, no rule published
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.

Verifactu and e-invoicing side by side

Verifactu and B2B e-invoicing compared
VerifactuB2B e-invoicing
What it regulatesHow the software that issues invoices works: tamper-proof, chained invoicing records.The structured format of the invoice and its exchange between businesses.
WhoCompanies 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 whomIn 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.
FormatInvoicing record in XML with the AEAT format.Structured electronic invoice under the European EN 16931 model.
QRYes. 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.
Dates1 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.
RuleRD 1007/2023 and RDL 15/2025Law 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).

Test environment and test NIF included

Questions about Verifactu and e-invoicing

Is Verifactu e-invoicing?

No. Verifactu regulates the software and its invoicing records; e-invoicing regulates the invoice format and its exchange between businesses.

Do I have to comply with Verifactu and e-invoicing?

They add up: whoever is in Verifactu and invoices other businesses will have both obligations.

What does the Crea y Crece Law have to do with Verifactu?

They are different rules. Law 18/2022 (Crea y Crece) establishes B2B e-invoicing; Verifactu comes from Law 11/2021 against tax fraud.

I already have Verifactu integrated through an API. Does it work for e-invoicing?

NIF management, yes. E-invoicing will have its own sending integration: the E-invoicing API, coming soon.

Does an e-invoice carry a QR like Verifactu?

The QR is a Verifactu requirement; B2B e-invoicing does not require it as such. If an e-invoice is issued by a system subject to Verifactu, the QR image is not needed: its URL is included as its own field (Order HAC/1177/2024, art. 20.2). The AEAT’s official UBL invoice example carries the Verifactu QR URL in its own field (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.

Test environment and test NIF included