Your invoicing, ready for the next step.
Adapt your Odoo to VeriFactu or start with a new implementation. We help you find the route to VERI*FACTU that fits your company, ahead of the 2027 deadlines.
Find your starting pointA technical team. A plan built around your business.
*Deadlines for adapting invoicing software set by Royal Decree-law 15/2025 for those within the scope of the regulation. Whether it applies, and which mode, depends on each case. Read the AEAT notice (Spanish) ↗
Choose your situation.
The plan starts with understanding you.
We start from what you already have: version, modules, customisations and how you issue invoices. That tells us what your installation needs for VeriFactu.
Request a review of my OdooVersion, hosting, Spanish tax localisation and the modules involved in invoicing.
Identify the configuration, updates or migrations your case needs.
Agree on testing and support before going into production.
VeriFactu (officially VERI*FACTU) is one of the modes of Spain’s invoicing-software regulation: every invoicing record is sent to the Spanish Tax Agency (AEAT) as the invoice is issued.
Law 11/2021, known as the Anti-Fraud Act, requires invoicing software to guarantee the integrity, preservation, traceability and immutability of its records. Royal Decree 1007/2023 sets out those requirements and Order HAC/1177/2024 defines their technical specifications.
When an invoice is issued, the system creates its invoicing record with a fingerprint chained to the previous record. Cancelling or correcting an invoice creates a new record: an earlier one is never deleted or overwritten.
In VERI*FACTU mode, records are sent to the AEAT immediately. In NO VERI*FACTU mode they are kept in the system itself, with extra requirements such as signing every record and keeping an event log. Invoices carry a tax QR code.
Companies that keep their VAT books through the Immediate Supply of Information system (SII) are outside this regulation. Scope and exclusions should be checked case by case, together with your tax adviser.
We work with Odoo Community 17 and 18 and the OCA (Odoo Community Association) VeriFactu modules. If you use Odoo Enterprise or another version, we review your installation and tell you what it needs.
VeriFactu is switched on in Odoo with your company’s own digital certificate.
When an invoice is confirmed, Odoo creates its invoicing record with the fingerprint chained to the previous one.
The record is sent to the AEAT and Odoo shows the status of each submission.
If the AEAT returns an error, it is fixed from within Odoo.
The invoice carries the tax QR code.
Cancellations and corrections create their own chained record.
We install Odoo on your own server. You control the environment; we configure VeriFactu, your digital certificate and the backups.
We deploy it on AWS, Azure or Google Cloud so you don’t have to look after any installation.
Either way: your company’s own digital certificate and a managed backup of the record chain, which the rules require you to preserve.
Invoicing, sales, purchasing, projects or e-commerce. An adaptation makes sense when it fits the way you work.
See an Odoo implementation case study Odoo experience; not a VERI*FACTU-specific case.Your version, your data, your processes and the people who use them.
A proposal that sets out the work, the dependencies and the next steps.
Testing and go-live planned around the way you work.
Share your starting point so we can assess the fit and prepare the next conversation.
Let’s start with the most common ones about VeriFactu in Odoo.
It depends on your current system and what it can do. If you already use Odoo, we first review your version, modules and customisations. If you use other software, we assess with you whether an Odoo implementation fits your business.
They are different things. VERI*FACTU is a mode of the invoicing-software regulation that sends records to the AEAT. Business-to-business e-invoicing has its own framework and timetable.
No. The scope and the exclusions have to be checked, such as companies already in the SII. The regulation also provides for VERI*FACTU and NO VERI*FACTU modes. We review the technical fit of your case, together with your tax adviser where appropriate.
Royal Decree-law 15/2025 sets 1 January 2027 for Corporate Income Tax taxpayers and 1 July 2027 for all other taxpayers. The AEAT explains it on its website.
We work with Odoo Community 17 and 18 and the OCA VeriFactu modules. Tell us your version and whether you use Community or Enterprise: compatibility and the changes needed are reviewed for each installation, and not every version needs the same work.
Your own company’s digital certificate. We configure it in your Odoo during go-live; we never use shared or third-party certificates.
Both options comply with VeriFactu in the same way; what changes is who runs the infrastructure. On your server if you prefer to control it; in the cloud (AWS, Azure or Google Cloud) if you would rather we took care of it.
It depends on your starting point, data volume, customisations and integrations. The proposal sets out scope, budget and schedule before the project starts.