Digitizing Your Practice Before Verifactu (Jan and Jul 2027): The Half the Rules Don't Cover

Digitizing Your Practice Before Verifactu: The Half the Rules Don't Cover

The calendar is finally stable. Royal Decree-Law 15/2025, published in the BOE on 3 December 2025 and ratified by Congress on 11 December, pushed Verifactu to 1 January 2027 for corporate income tax payers and 1 July 2027 for everyone else — sole traders under IRPF, non-resident taxpayers with a permanent establishment, and income-attribution entities. Two dates, two waves, roughly six months apart.

Here is the part most migration checklists skip, and it should change how you budget the project: Verifactu regulates *invoicing software* — the invoices your clients issue. Royal Decree 1007/2023 sets requirements for the systems that generate and seal those invoices. It does not regulate invoice reception, and it does not regulate bookkeeping. The AEAT's own FAQ is explicit that receiving an invoice follows the same rules as before, and that a recipient scanning the QR code to check an invoice against the tax agency is an option, not a duty.

So run the numbers on your own practice before you scope anything. Which side of the invoice actually consumes your staff hours — the ones your clients issue from their own software, or the pile of supplier PDFs, photos and forwarded receipts that lands on your desk every quarter? For almost every practice it is the second. Ardent Partners' 2025 benchmark puts the average cost of processing a single invoice at $9.40, rising to $12.88 where the process is manual, against $2.78 for best-in-class teams. Verifactu will not move that number by a cent. If your digitization plan is only a software migration, you are spending a year fixing the half that never cost you anything.

The two-wave calendar, and why the second one is the hard one

Wave one — companies — is small and well-behaved. Sociedades usually already run proper invoicing software, have someone in-house who understands it, and their vendor almost certainly shipped a compliant version already: software producers have been required to offer Verifactu-compliant products since 29 July 2025, and selling non-compliant invoicing software has been sanctionable since then.

Wave two is the one that will hurt. It is the long tail: the sole trader invoicing from a Word template, the shop owner using a 2011 desktop program the vendor no longer maintains, the professional who "invoices from Excel". They are the bulk of most portfolios, they arrive six months later, and each one is a conversation rather than an install.

The sanction regime is worth having in the front of your mind when you make those calls. Article 201 bis of the General Tax Law sets a fine of up to 50,000 € per tax year for holding or using invoicing software that must be certified and isn't — or that has been tampered with — and up to 150,000 € for those who produce or market non-compliant software. That is a client-facing number, not a practice-facing one, and it is the reason to start the conversation early rather than in June 2027.

Do the capacity maths on your own portfolio

This is the calculation nobody does, and it is the one that determines whether the year is manageable. The numbers below are illustrative — substitute your own.

Say you carry 80 clients: 25 sociedades and 55 sole traders. From mid-August 2026 you have around 19 calendar weeks to 1 January 2027. Take out the October filing peak and the Christmas shutdown and you realistically have about 13 usable weeks for wave one. That is roughly two company migrations a week, every week, alongside normal work.

Now price the migration itself. If a client conversation, a vendor check, a data export and a first-invoice test run to 90 minutes each, 25 companies is about 37 hours — one full working week of someone's time, spread thin. Wave two is 55 clients over the following six months, but each takes longer because more of them have no software at all.

Then ask the question that decides the whole plan: where do those hours come from? If your team is already spending its Januarys keying supplier invoices by hand, they are not available. That is the practical link between the two halves of this article — automating the received side is what frees the capacity to do the issued side on time.

A four-step plan from here to January

1. Segment the portfolio into the two waves. One list of corporate taxpayers with a January deadline, one list of everyone else with a July deadline. Do this first; everything else is scheduling.

2. Audit invoicing software, not clients. Group wave one by the software they use, not by client name. If twelve of your companies use the same package, that is one vendor call and twelve identical emails, not twelve projects. The vendors have been obliged to have a compliant version since July 2025 — ask for the version number and the upgrade path in writing.

3. Flag the clients with no software at all. These are your July casualties if you leave them. They need a decision — which tool, who installs it, who trains them — and that decision takes weeks of back-and-forth, not days. Start them now even though their deadline is later.

4. Fix your own intake before the wave arrives. This is the step that gets dropped and shouldn't. Your inbound documents — supplier invoices, receipts, utility bills, the photos clients send at 11pm — will look exactly the same on 2 January 2027 as they do today. Getting that flow to land as structured data instead of as a folder of PDFs is what creates the hours to absorb everything else. There's a practical breakdown of that side in how to automate invoice extraction using WhatsApp and AI, and a client-facing version you can forward as-is in how to prepare supplier invoices before handing them to your accountant.

Three mistakes with a real price tag

Treating Verifactu as an accounting project. It is an invoicing-systems project that lands in your clients' businesses, not in your ledgers. If you scope it as "our software has to change", you will discover in November that the work is 80 client conversations and you have no calendar left for them.

Waiting for wave two clients because their deadline is later. The July group is bigger, less equipped and slower to decide. Six extra months of deadline does not mean six extra months of your availability — their window overlaps your Q1 and Q2 filing peaks.

Assuming the QR code solves your data entry. A Verifactu invoice carries a QR that lets the recipient check it against the AEAT. That confirms the invoice was registered. It does not hand you the line items, the VAT breakdown or the supplier's tax ID in a format your software can read, and the recipient is under no obligation to check it at all. Verification and extraction are different problems. If you want the broader picture of what does and doesn't change on the invoice itself, see what Verifactu really means for the way you handle invoices.

The decision criterion

One question sorts the whole thing: for each client, does the deadline require them to change software, or does it require you to change how their paperwork reaches you?

If they issue invoices from a system, it is a vendor question — version, date, cost — and it is genuinely their problem with your supervision. If they issue few or no invoices but send you a mountain of received documents every quarter, Verifactu barely touches them, and the useful digitization work is entirely on your side of the relationship.

Most portfolios are a mix, and practices that split the list this way in September stop treating 2027 as one big cliff and start treating it as two manageable queues. If you want to see how the received-document side is handled end to end, our tools for accounting and advisory practices cover the intake, extraction and export path.

The fastest way to judge whether that half is worth automating is to test it on a real document rather than read about it: send one of your own supplier invoices through the free extractor — no signup needed and see what comes back as structured data.

Frequently asked questions

###

###

###

###