Identifying data
Checking uses essential invoice data such as issuer tax ID, invoice number, issue date, and amount.
VERIFACTU QRUpdated 2026 guide
VeriFactu QR: what it is and what the invoice must show.
The tax QR forms part of the invoice representation for invoicing systems covered by the RRSIF. In VERI*FACTU mode it lets the recipient access AEAT invoice checking.
The QR should not be independently rebuilt in every plugin. URL, wording, and state should come from a fiscal source consistent with the issued invoice.
VERIFACTU GUIDE
What the QR represents and why it matters.
The QR is not a decorative element: it connects the invoice representation to AEAT's checking service and must correspond to the actual fiscal data.
VERI*FACTU checking
When the invoice comes from VERI*FACTU, AEAT can compare it against records previously submitted by the issuer.
Verifiable-invoice wording
In VERI*FACTU mode the invoice must show the verifiable-invoice wording or the VERI*FACTU expression under the applicable rules.
Checking result
AEAT can report an invoice as found or not found depending on the information held in its records.
Not every case is identical
QR scope has exceptions and cases outside the general RRSIF, so templates should not assume every Spanish invoice follows the same rule.
One presentation source
In a multi-adapter architecture QR and wording should come from the fiscal core and be consumed by WooCommerce, PrestaShop, or ERP.
STEP BY STEP
How to integrate QR without breaking the invoice flow.
Presentation should be tied to the same fiscal operation that generated the recordId and state.
Issue or reconcile
Obtain the fiscal state before treating the invoice representation as complete.
Receive presentation
Consume the QR URL and wording associated with that invoice from the core.
Render in your channel
Insert the presentation into PDF, HTML, or structured documents according to the platform.
Do not rebuild locally
Avoid letting every plugin independently recreate taxpayer ID, URL, wording, or invoice parameters.
KAIROSETH FISCAL
WooCommerce and PrestaShop consume the same presentation contract.
The goal is one fiscal source for the QR even when the final renderer differs. PrestaShop can insert it into its native PDF; WooCommerce exposes it neutrally for the invoice renderer used by the store.
FAQ
Frequently asked questions.
Short answers grounded in official sources.
What is the VeriFactu tax QR?
It is the encoded representation on the invoice that opens an AEAT service with specific invoice data. In VERI*FACTU mode it can be used to compare the invoice against records submitted by the issuer.
Must a VERI*FACTU invoice say it is verifiable?
AEAT states that when the invoicing system operates in VERI*FACTU mode, the invoice must include the wording 'Factura verificable en la sede electrónica de la AEAT' or 'VERI*FACTU'.
What happens when the QR on a VERI*FACTU invoice is scanned?
AEAT can report that the invoice was found with matching characteristics or that it was not found, depending on the records held by the Tax Agency.
Does a missing QR automatically remove the right to deduct VAT?
AEAT clarifies that a missing QR by itself does not determine VAT deductibility when substantive requirements are met. It is a formal issuer obligation within the applicable scope.
Does every Spanish invoice carry a VeriFactu QR?
No. AEAT identifies situations outside this requirement, including certain SII taxpayers, regional tax regimes, or invoices not issued through a covered invoicing system.
KEEP EXPLORING
Canonical VeriFactu guides.
Each guide owns a distinct intent to avoid duplication and make the path from question to solution clear.
What is VeriFactu
Open guide →Requirements
Open guide →Self-employed and SMEs
Open guide →Free VeriFactu / AEAT app
Open guide →Current 2027 dates
Open guide →2028 announcement and horizon
Open guide →OFFICIAL SOURCES
Always check the current official version.
This guide summarizes official rules and documentation; it does not replace tax advice or checking the exact scope that applies to each organization.
AEAT · QR and verifiable-invoice FAQ
Open official source →AEAT · QR concepts and scope
Open official source →AEAT · VERI*FACTU invoice checking
Open official source →BOE · Order HAC/1177/2024
Open official source →TRUST & CONTROL
Authority stays explicit as the platform grows.
Kairoseth separates identity, organization scope, product roles and product capabilities. A login route, browser state or AI response never becomes an authorization boundary by itself.
KAIROSETH PLATFORMCONTROL PLANE
- Identity
- Shared account
- Verified
- Organization
- Tenant scope
- Required
- Product
- RBAC assignment
- Explicit
- Sensitive actions
- Policy gate
- Controlled
Organization scope
Customer resources and access are resolved inside an active organization context rather than treated as global account state.
Product-scoped roles
Owner, Admin and Member authority is assigned per product. Organization membership alone does not automatically grant every product.
Server authority
Sensitive access, policy and capability decisions remain authoritative on the server instead of trusting client UI state or model output.
Controlled execution
Capabilities that can act are introduced behind explicit grants, staged gates and audit rather than implied autonomy.
Public trust evidence
Review the customer-facing policies that define privacy, security reporting, acceptable use and the current legal operating framework.
SOFTWARE VERIFACTU
Can your current invoice add the QR without replacing your whole system?
Kairoseth Fiscal separates presentation from rendering: the core generates the fiscal contract and each platform displays it using its real capabilities.