Veri*Factu for bars & restaurants: the 2027 deadlines explained

If you run a bar, café or restaurant in Spain, Veri*Factu is coming — but you have more breathing room than you may have heard. In December 2025 the government pushed the deadlines back by a year, so most hospitality businesses now have until mid-2027. That's not a reason to ignore it; it's a reason to get sorted early, calmly, instead of scrambling at the last minute. Here's the whole thing in plain English — what the law says, when it applies to you, and what your till has to do about it.

What is Veri*Factu?

Royal Decree 1007/2023 (the Reglamento de Requisitos de los Sistemas Informáticos de Facturación, often called the anti-fraud or SIF regulation) sets technical rules for any software that issues invoices or tickets in Spain. The goal is simple: make it impossible to quietly delete or alter a sale after the fact.

The decree defines two ways to comply:

• Veri*Factu mode: your POS sends every billing record to the AEAT in real time, as the ticket is issued.
• Non-Veri*Factu mode: records stay on your system, but must be cryptographically signed, hash-chained and ready for inspection at any moment.

Either way, the receipt carries a QR code that anyone — a customer or an inspector — can scan to check the ticket against the AEAT.

The deadlines (extended to 2027)

The original dates were in 2026. Royal Decree-Law 15/2025, of 2 December, extended them by a year:

• 1 January 2027 — companies that pay corporate tax (Impuesto sobre Sociedades) must use compliant invoicing software. If your bar is an SL, this is your date.
• 1 July 2027 — everyone else, including autónomos, the legal form behind a huge share of Spanish hospitality. If you're self-employed and ring up sales, this is your date.

The period before those dates is an official testing period: you can already run a Veri*Factu system and send test records to the AEAT to make sure everything works, with time to settle in before it's mandatory. In practice that's the smart window to switch — get it bedded in long before the deadline.

Software vendors have their own obligation: anything sold as invoicing software must be built to comply. So if a TPV dealer is still quoting you a system "with the Veri*Factu module coming soon", treat that as a red flag.

What happens if you ignore it?

Once the deadlines bite, the General Tax Law (article 201 bis) makes simply possessing non-compliant invoicing software a sanctionable offence — fines for users can reach €50,000 per financial year, separate from any penalty for the manufacturer. Inspections in hospitality are not hypothetical; cash-heavy sectors are exactly where this regulation is aimed. The extension buys time to prepare — not a reason to do nothing.

What a compliant POS actually does

Behind the acronyms, a compliant system has to:

1. Record every ticket in an unalterable, hash-chained log. Each record includes a fingerprint of the previous one, so removing or editing a sale breaks the chain visibly.
2. Print the AEAT QR code on every receipt, with the record ID, hash, issuer NIF and date.
3. Keep a signed event log of significant software actions.
4. Submit records to the AEAT in real time (VeriFactu mode) or keep signed records available for inspection (non-VeriFactu mode).
5. Come with a declaración responsable — the manufacturer's formal declaration that the software meets RD 1007/2023. There is no government certificate or approved-software list; compliance is self-declared, so this document is what proves your till is legitimate. Ask any vendor for theirs.

Corrections don't disappear either: a mistake is fixed with a new rectifying record, never by editing history. Good systems make this invisible to staff — you void a line or reprint a ticket the way you always did, and the fiscal machinery does the right thing underneath.

How brasio handles it

brasio runs in Veri*Factu mode: every receipt is submitted to the AEAT in real time through Verifacti, a specialised submission platform, and the QR is printed on the ticket automatically. It's a fully Veri*Factu-compliant SIF under RD 1007/2023 — there's nothing to configure, no module to buy and no end-of-day batch to remember, and it's included in the €35/month price.

Two honest notes:

• Real-time means online. Because records are submitted as tickets are issued, issuing fiscal receipts needs an internet connection. Plan for solid venue Wi-Fi and ideally a 4G backup router. This is a property of real-time Veri*Factu, not a brasio quirk.
• The toggle exists, but it's not for you. brasio can disable Veri*Factu per venue for the rare business genuinely outside the rules' scope (for example, certain territories or regimes). If you run a normal bar or restaurant in mainland Spain, assume you're in scope.

What to do now

1. Ask your current TPV vendor, in writing, whether your system complies with RD 1007/2023 — and ask for their declaración responsable.
2. Don't wait for 2027. Use the testing period to switch on your own terms: migrating a menu and training staff takes days, not months, and doing it calmly now beats doing it under deadline pressure (or during an inspection).
3. If you want to see real-time Veri*Factu working, start a free brasio trial — the full picture of what else a modern till should do is in our restaurant POS guide for Spain, and there's a deeper dive on the Veri*Factu page.

This article is a plain-language summary, not legal advice. For your specific situation, talk to your gestor — and check aeat.es for the current official calendar.