What it really costs to adapt your system to VeriFactu (and when it's worth it)

VeriFactu is no longer optional. The question isn't whether to adapt, but how to do it without throwing money away. We learned this by integrating it into our own CRM, in production since 2010. Here are the real numbers, with no sales pitch.

1. Why the decision is no longer optional

VeriFactu (Spanish Royal Decree 1007/2023) requires every invoice issued by companies and sole traders in Spain to be signed and recorded by a software system meeting very specific requirements: hash, chaining, integrity, four-year retention and, optionally, automated filing with the Spanish tax authority.

The deadlines are staggered, but they all end in 2027. The penalty for non-compliance runs from €1,000 to €50,000 per machine, not per company.

What this means in practice: if your invoicing system (ERP, CRM, spreadsheet macros, whatever it is) doesn't generate, sign and retain the QR code, hash and chaining the rules demand, you stop issuing valid invoices. Full stop.

2. The four real cost items

Anyone selling you a VeriFactu project as one lump is selling you a black box. In reality there are four separable items, each with its own decision:

2.1. Software (the most visible part)

There are three real options here, with very different costs:

• Subscribing to a commercial ERP that is already compliant (Holded, Sage, Clientum, Quipu, Anfix…). Typical fees €20-200 per user per month depending on modules. No upfront investment, all operating expense.
• A VeriFactu module on top of an existing system. If you already have a custom CRM or ERP that works, it usually costs 1.500-6.000 € to add the signing, chaining and tax-filing module.
• A new custom build with VeriFactu from day one. 8.000-25.000 € depending on scope (what else is integrated: banking, payments, accounting, and so on).

2.2. Digital certificate

You need a legal-entity representative certificate to sign on your behalf with the tax authority. Typical cost €14-40 per year (FNMT, ANF, Camerfirma). It is per company, not per user.

If you run VeriFactu in "no filing" mode (sign and store, but only submit on request), the certificate is optional. Most people end up in "filing" mode so they can forget about it.

2.3. Migration and configuration

This is the item almost everyone underestimates. It covers:

• Cleaning up the client file (missing, malformed or duplicate tax IDs).
• VAT and IGIC rates correctly configured per service or product.
• Invoice series and numbering that doesn't break your history.
• An initial reconciliation against what has already been invoiced.

On an average system: one to three weeks of work for one technician. If the ERP vendor does it, they usually bundle it into "implementation" and charge €1,000 to €4,000. If you do it in-house it's "free", but it eats 80 to 120 hours of someone's salary.

2.4. Training the team

The least quantified and often the most expensive in lost hours. Everyone who issues invoices has to understand the new flow: tax ID validation, what happens if the tax authority rejects a filing, how to cancel an invoice already submitted, how to issue a credit note.

Typically: two to four one-hour sessions plus a manual. If the ERP is good, thirty minutes will do.

3. The hidden costs nobody shows you in the sales meeting

• Cancellations and credit notes. If you get an invoice wrong once it has been filed, you can't delete it: you have to issue a credit note. The ERP must support this without workarounds.
• The IGIC regime (if you operate in the Canary Islands) or IPSI (Ceuta and Melilla). Many commercial ERPs treat it as an "extra" or don't support it cleanly.
• Support when the tax authority changes the schema (it has already happened three times since 2023). If your ERP doesn't update itself, you pay for it in your team's hours or in an extra support fee.
• Compliant backups: records must be retained for four years with their integrity intact. Does your backup already do that? If not, add it to the bill.
• Other integrations that break: if you have ContaSol, banking, a payment gateway, a quoting module… each one has to be adjusted to carry the new invoice format.

4. The cost of not adapting

We mentioned the penalties above (€1,000-50,000 per machine). But the real damage is usually elsewhere:

• Rejected invoices: if your client requires a VeriFactu invoice and you can't issue one, you don't get paid.
• Losing approved-supplier status with large companies, public bodies and tender processes.
• The cost of rushing: improvising the integration 30 days before the legal deadline costs two to three times more than planning it six months ahead.

5. How to work out whether it's worth it

The traditional ROI formula works, but most people apply it wrong. Here is the honest version:

Example: a services SME with eight people

Realistic indicative figures for a typical company. Your mileage may vary by size and sector.

6. ERP subscription vs. custom build vs. adapting what you already have

This is the real decision, not "which ERP to choose". An honest comparison:

Our honest opinion: if your current system already covers how you operate and only VeriFactu is missing, adapting it is almost always the better-value option. It saves you the never-ending ERP subscription and keeps the flow your team already knows.

7. How to minimise the investment and speed up the return

• Audit first what you have and what you're missing. Most people are surprised how much is already done.
• Start with the signing and filing module. Cancellations and credit notes can come in a second phase.
• Use the migration to clean up the client file: malformed tax IDs are the biggest source of rejections by the tax authority.
• Negotiate maintenance included for the first few months. When the tax authority updates the schema (and it will), you save hours.
• Train the team before you migrate production, not after.

Conclusion

VeriFactu is neither a technical whim nor an avoidable expense: it is how invoicing now works in Spain. The smart question is how to how integrate it at the lowest cost and the best return.

If your current system works, adapting it is almost certainly cheaper and faster than migrating to a new ERP. If you are starting from scratch, make native VeriFactu the first requirement rather than patching it in later.

The key point: plan early. The legal deadlines end in 2027 and technical suppliers will be swamped in the final six months.