Verifactu Aeat: This will be the jump to 2026 and what changes in your bills

From 2026 All issuing issuing invoices in Spain must operate with Billing computer systems (SIF) adapted. The frame admits two modalities: True * Facture (online remission of records to the Treasury) and not verifiable (safe custody without continuous shipping). In both cases, invoices will incorporate QR code and manipulations -proof traceability.

To plan with time, it should be understood What is and how verifactu aeat ​​fits in the daily operation; This guide summarizes the flow, dates and the minimum technical requirements, with a practical approach for SMEs and freelancers. If you are looking for an operational explanation step by step, here are a useful reference on Verifactu aeat in the First Compases of 2026.

What is verifactu aeat ​​(and what not)

Verifactu It is not a “new invoice template”, but a Standard of billing records which generates the SFA when you emit an invoice or ticket. Each record is Cryptographically chart with the previous one to guarantee integrity and inalterability; In addition, the system maintains a event registration (High, cancellations, configuration changes, incidents).

The Regulation (RD 1007/2023) contemplates two forms of compliance:

• Veri*Factual mode (verifiable): Sif Refer online The records to the Site of the AEAT continuously and safely.
• Non -verifiable modality: does not send continuously, but conserva y exports Records when required, maintaining the same technical integrity.

In both cases, all invoices within the scope of the Regulation must include QR code to facilitate rapid checks by the receiver or administration.

Dates and who affects

AEAT has clarified the calendar of implantation of verifactu, with differentiated references for societies y Autonomous/other companies throughout 2026after the modification of the Fourth final disposition of RD 1007/2023 by the RD 254/2025.

• Companies (Corporation Tax): effective adaptation from January 2026.
• Freelancers and rest of the obligors: Adaptation to July 2026.
  In addition, since 2025 it is required that manufacturers/marketers Put on the Software Market in accordance with.

Important: If you already work with SII (immediate information supply)you continue in that regime; Coordination with the SIF focuses on templates, exports and processes, avoiding duplication.

Territorial scope: in Basque Country and Navarra Foral systems govern (TicketBAI), more strict and local application. If you operate in several territories, check coexistence and rules of each farm.

The real flow of an invoice with verifactu

1) Issuance in a Sif in accordance with

The TPV, ERP or billing module It emits the invoice and the Sif generates the registration of high With standardized fields, chaining it by hash With the previous one. At the same time, the system notes events (High, errors, adjustments).

2) QR and (when apply) Veri*Legend

The template incorporates the QR code in legible position; If you operate in verifiable mode, add the * LEYENDA TRUE *. The QR speeds up returns, guarantee and checks in counter or post -sales.

3) Recision or custody of records

• Verifiable: Sif Refer The registration of the AEAT headquarters.
• Not verifiable: Sif custody the records and allows export them on demand.
  In both, integrity and inalterability are assured by design.

4) Incidents without stopping the sale

Yes Short Internet or there is a fall of the headquarters, the Sif does not stop billing: Mark the incidence y resume Shipping when connectivity returns (tails and reteeing configured).

What changes every day (key points)

• Templates: All must show QR And, where appropriate, the legend. Verify minimum sizes and position for thermal printing and PDF.
• Processes: There will be protocols Clear for cancellations and rectifications, with a trace in the event registration.
• Back office: In verifiable modality, the custody It falls to the administration, which lightens internal file and accelerates requirements.
• Multichannel: Coordinates TPV, online store and manual billing to avoid duplications (Order? Invoice).
• Territorial coexistence: If you combine operations in common and regional territory, your software must Know how to speak verifactu and ticketbai.

Minimum technical requirements that your software must meet

• Integrity: chained hash of records, inalterability controls.
• Event registration of the system (high, cancellations, incidents, configuration changes).
• Standardized exports of records and events, legible by third parties.
• QR support and of Legends visible in complete and simplified invoices.
• Safe remission to the headquarters (if you work in verifiable) and remission capacity even in non -verifiable for cases of requirement or change of modality.
• Responsible statement of the manufacturer or responsible for the software.

Practical advice: although today you opt for not verifiablerequires remission capacity and a plan of change of modality By sif. Avoid blockages if the strategy evolves.

How to choose modality by Sif (and not regret it)

Verificable (veri * * course) fits when:

• search Less load of internal custody,
• have Stable connectivity at the issuance points,
• worth the automation and evidence almost in real time.

Not verifiable makes sense yes:

• You operate with irregular coverage (Mobility stores, pop-ups, low network areas),
• Your advice already dominates Exports and documentary government,
• You want a deployment by phases starting with internal control.

Coexistence: You can have Various Sif In the organization and assign different modalities By business line or geography. What is not admitted is switch within the same Sif.

90 -day adaptation plan (roadmap)

1. Inventory of emission points (TPV, ERP, web, apps), with responsible and permits.
2. Process mapfrom order to the accounting seat: detect manual tasks and “black boxes.”
3. Modality decision by SF (Documented): Network, volume and support criteria.
4. Templates with QR and legends lists and tested in thermal and A4.
5. Pilot In a store/line: simulates incidents, cancellations and rectifications.
6. Exports and restoration: It generates a test set and verifies that a third party reads it.
7. Formation: short manuals for box, administration and support; closure with zero coats.
8. Governance: Responsible, internal slas and unique channel for incidents.
9. Supplier: Ask responsible statementTechnical Manual and Update Plan.

What happens in Foral Territories? (Ticketbai vs verifactu)

TicketBAI (Basque Country and Navarra) is a system statutory with own requirements and homologations, more strict and Local application. Verifactu It is the frame state. If you sell in both areas, the software must be homologated in foral and adapted to common in common, with Differentiated templates and flows When touching.

Common errors (and how to avoid them)

• Leave QR for the end: the size/position import; Printing and PDF test before deploying.
• Do not rehearse incidents: Network cuts occur; Configure queues and alerts Not to close with pending shipments.
• Think only about software: Without processes and roles, change is stuck in closures and returns.
• Forget SII or Ticketbai: Avoid duplicities and conflicts if you operate in those regimes.

Frequent questions

Will verifactu be mandatory for everyone?
He RRSIF applies to whom They issue invoices. It can be met in mode True * Facture (online shipping) or not verifiable (custody/ export). Give Keep your regime.

When are effective dates?
AEAT places the reference in 2026with staggered adaptation and regulatory changes via RD 254/2025 About the DF 4.ª of the RD 1007/2023.

Is QR mandatory in all invoices?
Yes, within the scope of the Regulation. In verifiable, in addition, the * LEYENDA TRUE *.

What happens if the Internet is cut?
The billing does not stop. The brand system incidence y resume Shipping when the connection returns, thanks to colas y Reintents.

Opero in León and Bizkaia: do I need two systems?
Your software must adapt a Verifactu in common territory and be homologated to TicketBAI In Bizkaia. Many solutions allow you to configure SIF differentiated by center or activity.

Closing: reach 2026 without shocks

The change does not only go from the program, but of processes and people. Who arrives with List templates, proven pilot y written protocols You will notice less friction in closures, returns and audits. The time to decide modality by SF, train equipment and ask your supplier for responsible statement es now.