Anti-Fraud Law and VeriFactu: what they are, how they differ and why your business can't ignore them
The Anti-Fraud Law and the VeriFactu regulation form the new framework regulating how invoices are generated, stored and verified in Spain. Both pursue the same objective - to reduce tax fraud and improve traceability - but they they are not the sameThe Anti-Fraud Act sets out the general principles and obligations, and VeriFactu (the regulatory and technical implementation) details how these principles should be translated into invoicing programmes and processes.
Below we explain, in straightforward language and designed for tourism, activities, POS and booking companies, what each one entails, how they differ and what practical steps you should take into account.
Survey
What billing system do you currently use?
We want to better understand how our customers and other professionals in the tourism sector manage invoicing. Knowing the tools they use will allow us to develop more useful integrations adapted to their real needs, and thus offer solutions that really facilitate their daily work.
It will take you a second
Just answer a short survey about the billing system you use.
Your answer will allow us to:
What is what?
Why is it important for your business?
If you are not currently using an invoicing software you should consult the different options on the market as the Anti-Fraud Law aims to cover the following objectives:

Key dates (deadlines)
Risks and penalties (what to avoid)
Does it affect the tickets (simplified invoice) issued by a POS?
Yes: simplified invoices (tickets) generated by POS fall within the scope of the regulation. If the receipts contain minimum tax data (VAT number, date, amount, description) and serve as proof, the AEAT may consider them as simplified invoices and then the requirements (including QR and registration) will apply. It is therefore important to analyse how your booking/TPV system generates and stores receipts.
In order not to be considered as a ticket or simplified invoice, they must clearly contain the word "ticket". RECEIPT
Visual comparison (quick)
Anti-Fraud Law vs VeriFactu
|
Aspect 12670_de9c5d-66>. |
Anti-Fraud Law (principle/obligation) 12670_f537a4-95>. |
VeriFactu (technical development / how to apply it) 12670_84b9ba-cd> |
|---|---|---|
|
Nature 12670_46bde9-d5>. |
Legal and fiscal policy framework. 12670_6fb204-73>. |
Regulation and ministerial order with technical specifications. 12670_60fc20-15>. |
|
Target 12670_e17d42-d0> |
Prevent tax fraud; require integrity, traceability, retention. 12670_9c1da5-da>. |
Define formats (XML), chained hash, QR, sending/query to AEAT. 12670_5c5c66-31> |
|
Who regulates it 12670_e6175f-97> |
Legislation (Ley General Tributaria, BOE). 12670_172ac1-46>. |
RD 1007/2023 + Order HAC/1177/2024; updates (RD 254/2025). 12670_a626cf-2b> |
|
Application 12670_d1fc19-c4> |
To producers, traders and users of billing systems. 12670_883913-fc>. |
IT systems issuing invoices or simplified invoices; defines VeriFactu / non-VeriFactu modalities. 12670_afef4c-46>. |
|
Compliance requirements 12670_e8304a-3a>. |
Principles: inalterability, conservation 4 years, accessibility. 12670_07c0d9-4c>. |
Specifications: XML UTF-8, chained hash, event logging, QR with matching URL. 12670_50bb87-0b>. |
|
AEAT Access 12670_f2e2e2c5-d2>. |
Statutory right of inspection and injunction. 12670_9048f6-f2>. |
If VERIFACTU: AEAT already has records; if NO VERIFACTU: may request export or inspection. 12670_b5ea10-9c> |
|
Sanctions 12670_3e4df9-b1> |
It establishes liability and sanctions for non-compliance. 12670_1bba82-73>. |
Specific penalties to manufacturers and users for non-compliant systems. 12670_7b997b-68>. |
(Official citations: RD 1007/2023, Order HAC/1177/2024 and amendment RD 254/2025).
What to do now?
Practical checklist for companies using TuriTop
CONSULT AN EXPERT
Confirm with your advisor/specialist how the Anti-Fraud Law affects your specific case (self-employed vs. company; SII (Immediate Provision of Information), exceptions).
FROM TURITOP
We remind you that TuriTop is designed as a booking system, so for now it does not include billing functions. That said, you can connect TuriTop with your billing software in different ways. Before proceeding, please check with your billing software for available integration options.
Many of our users use Holded as their billing system, as it is Verifactu-compliant as they explain here. With Holded, you could automate the creation of invoices for each booking registered in TuriTop, ensuring compliance with the new legal requirements via API. TuriTopHolded connectivity via API will be available in 2026.
If your billing software is different from Holded, you can also connect via Webhooks, as long as your system allows you to receive data from external sources.
For this setup, you may need to use automation tools such as Zapier, Make or n8n, so the person in charge should ideally be familiar with these platforms.
In this case, we recommend that you contact your billing software provider to find out the implementation steps and costs.
With this configuration, every booking made on your website through WooCommerce will automatically generate an invoice in Holded, complying with the new law without the need for manual intervention.
Final message from TuriTop
At TuriTop we are closely following the regulatory and technical evolution of the Anti-Fraud Law to ensure that our platform complies with all applicable requirements and, above all, so that you don't have any surprises. Very soon we will share specific news about the status of our invoicing functionalities and the options available for your company to manage records in a secure and compliant way.
