Verifactu penalties: fines for non-compliance
Verifactu penalties are set out in article 201 bis of the General Tax Law: €50,000 per financial year for whoever holds an invoicing system without the required certification (the producer's responsible declaration) or that has been altered, and €150,000 per financial year with sales and per type of system for whoever makes or sells it. They are serious offences and apply from the date each obligation becomes enforceable.
Penalties can apply from the date each obligation becomes enforceable:
| Who | Date | Status | Rule |
|---|---|---|---|
| Producers and resellers of invoicing software RDL 15/2025 did not change this date. | Since 29 Jul 2025 | In force | RD 1007/2023 · Orden HAC/1177/2024 |
| 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 |
This is not advice: each taxpayer determines what applies to them with their adviser.
Which penalties the law sets
| Who | Conduct | Amount | Frequency | Severity |
|---|---|---|---|---|
| Software producers and resellers | Making, producing or selling systems that do not meet art. 29.2.j LGT (conducts in art. 201 bis.1) | €150,000 | Per financial year with sales and per distinct type of system | Serious |
| Software producers and resellers | Selling systems without the certificate a regulation requires (art. 201 bis.1.f) | €1,000 | Per system sold without the certificate | Serious |
| Users (companies and self-employed) | Having systems that do not meet art. 29.2.j LGT when they are not certified although they must be, or when the certified devices have been altered or modified (art. 201 bis.2) | €50,000 | Per financial year | Serious |
Source: art. 201 bis of Law 58/2003, General Tax Law (consolidated text), added by Law 11/2021.
Penalty for companies and self-employed people who use the software
€50,000 per financial year for having systems that do not meet the requirements of art. 29.2.j of the General Tax Law when they are not duly certified although they must be, or when the certified devices have been altered or modified. It is a serious offence.
The law refers to «certified» systems. For Verifactu, that certification is the producer's responsible declaration (art. 13 RRSIF, section «Certification of computer systems»): the AEAT does not issue it.
Whoever has already been penalised as a producer or reseller cannot also be penalised as a user.
Penalty for software producers and resellers
€150,000 per financial year with sales and per distinct type of system made, produced or sold that falls under the conducts of art. 201 bis.1. It is a serious offence. Their obligation has been in force since 29 July 2025 and the announced postponement does not change it.
Since when penalties can be imposed
From the date of each obligation, as shown in the dates table. Until the postponement to October 2028 is published in the BOE, the dates for users are 1 January 2027 (Corporate Income Tax) and 1 July 2027 (everyone else). More in When Verifactu comes into force.
This is not advice: each taxpayer determines what applies to them with their adviser.
Which conducts are penalised
Art. 201 bis.1 of the General Tax Law penalises making, producing or selling systems that support accounting, invoicing or management processes when they:
- allow separate sets of accounts to be kept;
- allow transactions carried out not to be recorded, in full or in part;
- allow transactions to be recorded that differ from the entries made;
- allow transactions already recorded to be altered in breach of the applicable rules;
- do not meet the technical specifications that guarantee the integrity, preservation, accessibility, legibility, traceability and unalterability of records;
- are not certified when a regulation requires it.
Systems that allow separate accounts, or hiding or altering records, are often called «dual-use software». TicketBAI and e-invoicing have their own regimes: TicketBAI penalties and e-invoicing penalties.
Comply with Verifactu in your software, through an API
The Verifactu API generates the tamper-proof invoicing record, chains it, returns the QR and sends it to the AEAT. Verifacti publishes its responsible declaration as an external component.
Questions about Verifactu penalties
How much is the fine for not complying with Verifactu?
Since when can I be penalised?
What is dual-use software?
Am I penalised if I use software that does not comply?
Does the postponement also delay the penalties?
Try the Verifactu API in the test environment
Create your free account and send your first test invoice.