Veri*factu: What it is and how it affects your restaurant in 2026

Veri*factu is one of those regulatory changes that first seem distant, and then, when they arrive, feel urgent. If your restaurant issues invoices with any software (POS, management program, exportable Excel template, online platform), it affects you. And if you've heard about it but don't know exactly what it means, this article is for you.

We're going to explain it in practical, not legal, terms. If, after reading this, you need specific legal details, your tax advisor is the one who should guide you.

What is Veri*factu in a sentence

Veri*factu is the new set of technical requirements that the Tax Agency (AEAT) demands from computer systems that issue invoices in Spain. The State's objective is to reduce tax fraud by ensuring that when a business issues an invoice, that invoice is recorded completely, is non-manipulable, and, optionally, communicated to Hacienda in real-time.

In other words: until now, you could issue an invoice from any software and report it to Hacienda in the next periodic declaration. With Veri*factu, the invoicing system must meet a series of technical guarantees for that invoice to be valid.

Who it affects

The general rule: almost all self-employed individuals and companies that issue invoices with software. This includes:

Restaurants that issue invoices to business clients or for private events.
Restaurants that use POS systems with invoicing functionality.
Establishments that provide invoices to customers who request them.

Some cases are excluded or have specific treatment:

Businesses under the SII (which already report in real-time through another channel).
Certain special regimes.
Businesses in 'foral' territories (País Vasco, Navarra) with parallel regulations.

If your restaurant issues simplified tickets to the final customer (what many customers ask for when they request an "invoice" in a restaurant, but which is technically a ticket), the situation is nuanced and depends on exactly what your POS system does. Your advisor can clarify this specific point for you.

What changes technically

Systems that comply with Veri*factu must guarantee three things:

1. Integrity and unalterability of records. Once an invoice is registered in the system, it cannot be modified or deleted without leaving a trace. Changes are recorded as new events, not as an overwrite of the original.

2. Traceability and preservation. The system must preserve complete records for the applicable legal period. And it must allow the AEAT, upon request, to access that data in a comprehensible format.

3. Optional real-time communication. Here's the most visible novelty: the system can operate in "Verifactu" mode (immediate sending of each issued invoice to Hacienda) or in "non-Verifactu" mode (records remain local with integrity guarantees, but without immediate communication).

Verifactu mode sends the data. Non-Verifactu mode preserves it but does not communicate it unless required.

Which mode to choose?

This is a tactical, not technical, question. Both options are legal if the system meets the requirements. The choice has nuances:

Veri*factu mode (immediate sending). Greater transparency, less risk of discrepancies in inspections, and sometimes procedural benefits (Hacienda may offer advantages to those who opt for this mode, such as a reduction in the verification period). Downside: if the system occasionally fails and doesn't send something, there could be problems.
Non-Veri*factu mode (local preservation). More control over your data before sharing it. Useful if you have invoicing with many changes (corrective, cancellation invoices).

Most small and medium-sized restaurants will opt for Veri*factu mode for simplicity: you let the system handle it.

Important Dates

The exact mandatory dates have changed with successive regulatory modifications and have generated considerable confusion. What's important for you today:

The Veri*factu regulation is approved, and IT systems must adapt.
Software providers (POS, management, invoicing) have deadlines to certify that their products comply.
End-users (restaurants) must use certified software within the period established by the regulations in force at the time of reading.

Since specific dates can vary, it's advisable to confirm them with your tax advisor or consult the AEAT website for the current date.

What happens if you don't comply

The consequences of using a non-compliant system when the obligation is already in force may include:

Penalties for using unapproved software.
Specific penalties for manipulation or lack of integrity guarantees.
Increased likelihood and depth of inspections.

The specific amounts of penalties depend on the type of non-compliance. It's not worth the risk: using a compliant system is usually cheaper.

What to do step-by-step

1. Identify what software you use to issue invoices. Your establishment's POS, management program, manual Excel, online platform: whatever it is. Make a list.

2. Ask each provider about their Veri*factu adaptation status. Serious providers are already communicating whether they are certified, in process, or when they will be. If your provider can't give you an answer, that's a red flag — it's likely they are not complying, and you'll have to change.

3. If your current system won't adapt, plan the change. Better with time than in a rush. A well-executed change of POS or management software takes weeks: you need to migrate data, train the team, parameterize products, and connect with the tax system.

4. Confirm with your tax advisor. Every business has nuances: specific regimes, location, customer types. Your advisor will tell you what applies to your specific case.

5. Document compliance. When you use a certified system, keep the software's certificate or reference. If an inspection occurs, it can save you time to demonstrate conformity.

How it affects your daily operations

In practice, if everything works well, you shouldn't notice much. An invoice issued in a Veri*factu system is issued the same way: the customer receives their invoice, your system records it, and internally, the technical requirements are met.

What does change:

Invoice corrections are more formal. You cannot "delete and redo." You must issue a corrective invoice following the procedure.
Cancelled invoices leave a trace. They do not disappear.
Tax control is greater. If Hacienda ever requires data for a period, they can obtain it directly from the system.

For a restaurant that already invoiced correctly, Verifactu is transparent. For one with questionable practices (canceling and redoing invoices at convenience, falsifying sales), Verifactu is a significant change.

Veri*factu and Digitalization: Two Different Things

It's important not to confuse them: Veri*factu refers to the invoices that you issue. The digitalization of invoices that your suppliers send you is a different and compatible matter.

The first (Veri*factu) ensures that when a customer asks you for an invoice, that invoice is complete and reportable. The second (incoming digitalization) ensures that when a supplier sends you invoices, you can legally archive them in digital format.

Sincrio handles the second part: digitalization of invoices you receive from suppliers. It does not issue invoices (your POS or management system does that). But both systems coexist without overlapping: your POS/management system complies with Veri*factu for what you issue, and Sincrio organizes what you receive.

Conclusion

Veri*factu is a serious but manageable regulatory change. If you work with serious technology providers and your tax advisor is aware, the transition can be smooth. If you handle invoices haphazardly or use outdated software, now is the time to get organized.

The important thing is not to wait until the last minute: a well-executed adaptation takes weeks, and the cost of doing it in a rush (errors, failures, penalties) far exceeds the cost of doing it with time.

For everything related to invoices you receive from your suppliers, Sincrio organizes your digital archive with OCR and automatic reconciliation.

This article is for general informational purposes regarding the Verifactu framework in Spain as of its publication date. Electronic invoicing regulations are subject to changes, evolving deadlines, and nuances that depend on each case (tax regime, autonomous community, type of activity). It does not constitute tax or legal advice. Before making decisions about your invoicing system, consult with your tax advisor or usual manager.*