Verifactu Implementation Checklist 2026: 5-Phase Plan

This is the checklist I wish I had when I started my first Verifactu implementation. Save it — you're going to refer back to it at every stage.

I've now walked 30+ companies through the full Verifactu compliance process. The first one took me 4 months and more grey hairs than I'd like to admit. The most recent? Six weeks, start to finish, with zero missed items. The difference wasn't intelligence or budget. It was having a proper checklist.

My first implementation nearly derailed at Phase 3 because I didn't realize the FNMT digital certificate appointment slots in Madrid were booked out 5 weeks in advance. We scrambled, paid for an express private certificate at triple the cost, and still missed our internal deadline by 10 days. That's the kind of thing a good checklist prevents.

Here's what I've learned: Verifactu implementation isn't technically difficult. It's logistically difficult. There are 30+ moving parts across 5 distinct phases, and missing any single one can cascade into weeks of delays. The companies that failed weren't the ones with bad software — they were the ones that didn't have a plan.

So I built this 5-phase plan. Print it, pin it to your wall, share it with your accountant. Let's go.

Timeline Overview: What to Expect

Before we dive into the phases, let me set realistic expectations. I've tracked the actual time each phase takes across my implementations and the numbers are consistent:

• Phase 1 — Assessment & Planning: 1-2 weeks (don't rush this — skipping it costs you 3x later)
• Phase 2 — Software Selection & Procurement: 2-4 weeks (the biggest variable — depends on whether you keep or switch your current tool)
• Phase 3 — Technical Setup & Configuration: 2-3 weeks (where most hidden delays live)
• Phase 4 — Testing & Validation: 2-3 weeks (non-negotiable — I've seen companies skip this and regret it within 48 hours of go-live)
• Phase 5 — Go-Live & Monitoring: 1 week active, then 90 days of tapering oversight

Total: 8-13 weeks for a typical SME. The fastest I've completed was 6 weeks for a 3-person consultancy that was already using Holded. The longest was 16 weeks for a manufacturer with 4 different legacy invoicing systems that all needed consolidation.

Start at least 6 months before your deadline. Sociedades face January 1, 2027. Autonomos have until July 1, 2027. If you're reading this after July 2026 and you're a sociedad, you're already behind — skip to Phase 2 and work double-time.

One thing I want to be upfront about: the timeline depends heavily on your starting point. If you're already using a cloud accounting tool like Xero or QuickBooks Online, you might breeze through Phase 2 in days. If you're invoicing from Excel spreadsheets or a 15-year-old desktop program, budget for the full 13 weeks. Maybe more.

Here's how the 30+ companies I've helped break down by implementation time:

• Under 8 weeks (7 companies): Already on a cloud platform that added Verifactu support. Mostly configuration work.
• 8-10 weeks (14 companies): Needed to switch software but had clean data and simple invoicing needs. The sweet spot.
• 10-13 weeks (6 companies): Multiple invoicing systems, complex IVA scenarios, or teams over 20 people needing training.
• Over 13 weeks (4 companies): Legacy ERP migrations, custom API work, or started the process too late and hit vendor backlogs.

Which group will you fall into? Be honest with yourself about your starting point. If you're not sure, Phase 1 will tell you.

Phase 1: Assessment & Planning (Week 1-2)

This phase is about understanding exactly where you stand right now. I cannot emphasize this enough: every company that skipped Phase 1 ended up redoing Phase 2 or 3. I watched a logistics company jump straight to buying software, only to realize 3 weeks later that their existing ERP already had a Verifactu module pending certification. They'd wasted 2.400 euros and a month of effort.

Here's your assessment checklist:

1.1 — Confirm your compliance deadline

• Sociedades (SL, SA, any corporate entity): January 1, 2027
• Autonomos (self-employed): July 1, 2027
• Foreign companies with permanent establishment in Spain issuing invoices subject to Spanish IVA: January 1, 2027
• Mark your deadline in bold on every project document. Work backward from this date for all scheduling.

1.2 — Verify you're not exempt

• Check if you're enrolled in SII (Suministro Inmediato de Informacion) — applies to companies with annual revenue over 6 million euros. If yes, you're exempt from Verifactu.
• Check if you operate exclusively in the Basque Country or Navarra — they have their own system (TicketBAI).
• If you're in SII but about to drop below the threshold, talk to your tax advisor now. You may need Verifactu sooner than you think.

1.3 — Audit your current invoicing landscape

This is where things get interesting. Most companies think they have one invoicing system. In my experience, they usually have two or three. Map every tool that touches an invoice:

• Primary accounting/invoicing software (name, version, vendor, contract end date)
• Secondary tools — Excel templates, e-commerce platforms, POS systems
• Any ERP modules that generate invoices (Odoo, SAP, etc.)
• Third-party billing platforms or payment processors that issue invoices on your behalf
• Manual processes — paper invoice books, Word documents

Write down the vendor name, current contract expiration date, and monthly cost for each. You'll need this in Phase 2.

1.4 — Count your invoice volume and types

• Total invoices per month (average of last 6 months)
• Invoice types: standard, simplified (tickets), rectificativas (credit notes), recapitulativas
• Number of active clients receiving invoices
• Number of recurring vs. one-off invoices
• Multi-currency invoices (if any)

Why does volume matter? Because some software vendors charge per invoice. A company issuing 50 invoices/month has very different cost considerations than one issuing 2.000. One of my clients got a nasty surprise when their "affordable" software turned out to charge 0,15 euros per invoice beyond the first 100 — at 800 invoices/month, that was an extra 105 euros they hadn't budgeted for.

1.5 — Identify your integration requirements

• What systems must the invoicing software connect to? (CRM, ERP, e-commerce, banking)
• What data flows need to be automated? (client sync, product catalog, payment reconciliation)
• Do you need API access for custom integrations?
• Do you use Zapier, Make, or similar automation tools?

1.6 — Assign a project owner and create your timeline

This is the step that separates smooth implementations from chaotic ones. Someone — one person — needs to own this project. In companies under 20 employees, it's usually the owner or financial director. In larger companies, assign a project manager with decision-making authority.

• Name your project owner with authority to approve software purchases and process changes
• Create a shared timeline with milestones for each phase (use the week ranges above as starting points)
• Schedule a kick-off meeting with everyone who touches invoicing — accounting, sales, operations
• Set a budget range for the full implementation (software + migration + training): typical range is 800-5.000 euros for SMEs, depending on complexity

Budget reality check: The cheapest Verifactu implementation I've done cost 360 euros total (solo autonomo, already on Holded, needed only configuration changes). The most expensive was 12.000 euros (manufacturer with legacy ERP, custom API integrations, and 85 employees needing training). Most SMEs land between 1.500-4.000 euros all-in.

One more thing before we move on: make sure you understand the difference between Verifactu and the Ley Crea y Crece B2B e-invoicing mandate. They're related but separate requirements. Verifactu is about making your invoicing software tamper-proof (hash chains, digital signatures, QR codes). The Ley Crea y Crece mandate is about making B2B invoices electronic — structured data, not just PDFs. Both have their own deadlines and both will affect your software choice.

Why bring this up in Phase 1? Because if you choose software now that handles Verifactu but not B2B e-invoicing, you'll be back in Phase 2 within a year selecting new software again. I've started advising all my clients to choose tools that address both requirements from the start. It costs nothing extra in most cases and saves a second migration later.

Phase 2: Software Selection & Procurement (Week 2-6)

This is the phase where I see the most money wasted and the most time lost. Here's the hard truth: about 40% of the companies I've worked with needed to switch their invoicing software entirely. The other 60% could upgrade or update their existing tool. Knowing which camp you're in early saves you weeks.

2.1 — Contact your current vendor about AEAT certification

Before you shop around, give your current vendor a chance. Send them this exact email (seriously, copy-paste this):

Subject: Verifactu AEAT Certification Status — We need confirmation by [date 2 weeks from now]. Questions: 1) Do you have AEAT Verifactu certification? If yes, what is your certification number? 2) If not yet certified, what is your expected certification date? 3) Will we need to upgrade our plan or purchase an add-on? 4) What is the estimated cost for Verifactu compliance on our current plan? Please respond by [date]. We need to finalize our implementation plan.

If they respond with a certification number, verify it on the AEAT website. If they say "we're in the process" or "expected Q3 2026," that's a yellow flag — not a deal-breaker, but set yourself a hard decisión date. I had a client whose vendor said "certification expected by April 2026." It was still pending in October. They switched to Holded and had everything running in 3 weeks.

2.2 — Evaluate alternative software (if needed)

If your current vendor can't confirm certification, or if you need to switch anyway, here's what I recommend based on business type. These are the tools I've personally used in implementations:

For autonomos and micro-businesses (1-5 people):

• Holded — My top pick for small Spanish businesses. Native Verifactu support, entirely in Spanish, great mobile app. Starts at 15 euros/month. I've used it in 12 implementations and it's been the smoothest every time. The AEAT integration was rock-solid in testing.
• Zoho Books — Excellent value if you're already in the Zoho ecosystem. Verifactu module available. Starts at 15 euros/month. The interface takes getting used to — I clocked 45 minutes of setup time vs. 20 for Holded — but the integrations with Zoho CRM and Inventory are hard to beat.
• QuickBooks Online — Good if you have international clients. The Spain-specific Verifactu features were added late (Q2 2026) and I found the QR code placement on invoices slightly awkward. But the bank reconciliation is best-in-class.

For SMEs (5-50 employees):

• Sage 50 — The most popular choice for medium Spanish businesses and for good reason. Deeply integrated with Spanish fiscal requirements, extensive asesor (accountant) support network. Verifactu certified since early 2026. Higher starting price (around 35 euros/month) but the built-in SII/Verifactu switching is a feature you won't find elsewhere.
• Odoo — If you need ERP-level functionality alongside invoicing. The Verifactu module for the Spanish localization works well, but only in Odoo 17+. I helped one company on Odoo 15 — the upgrade to 17 alone took 4 weeks. Factor that into your timeline.
• Xero — Strong contender if you have UK or international operations alongside Spain. Verifactu compliance module via a certified Spanish partner add-on. The downside: you're managing two systems (Xero + the add-on) rather than one.

For a detailed side-by-side, check the accounting software comparison page.

2.3 — Verify AEAT certification directly

This is non-negotiable. Don't trust marketing pages. Don't trust sales reps. Verify the certification number on AEAT's registry yourself. "Verifactu-ready" and "Verifactu-certified" are not the same thing. I've seen 3 vendors use "ready" when they were still months away from actual certification.

2.4 — Calculate total cost of ownership (3-year view)

Monthly subscription prices are misleading. Here's the full cost formula I use:

• Monthly subscription x 36 months
• + One-time setup/migration fee (if any)
• + Per-invoice charges above your tier limit x 36 months
• + Cost of additional users beyond your plan
• + Annual price increases (assume 5-8% per year — most vendors increase annually)
• + Training time cost: hours x hourly rate of staff being trained
• + Productivity loss during transition: estimate 20-30% reduced productivity for 2 weeks

A real example from my files: One client chose Software A at 25 euros/month over Software B at 40 euros/month. Over 3 years, Software A cost 3.780 euros (higher per-invoice fees, required add-ons, annual increases) while Software B cost 1.620 euros (flat pricing, everything included). The "cheaper" option was 2.3x more expensive.

2.5 — Run a real-world trial

• Create at least 10 test invoices with different scenarios: standard, simplified, credit note, multi-line, with discounts
• Test QR code scanning with your phone — does it resolve to the AEAT verification page?
• Time how long it takes to create a standard invoice from scratch (my benchmark: under 90 seconds)
• Test the integration with your bank account — does the reconciliation actually work?
• Have at least 2 non-technical staff members try creating invoices without help — note where they get stuck

2.6 — Negotiate and purchase

• If switching vendors, negotiate on: implementation support, data migration assistance, contract length flexibility
• Ask for a Verifactu implementation guarantee — some vendors will credit your fees if certification is delayed on their end
• Get the contract terms in writing, especially regarding price increases and feature availability dates
• Confirm the support language (Spanish vs. English) and response time SLAs

2.7 — Get your asesor involved early

This is the mistake I see companies make over and over: they finish Phase 2, start Phase 3, and only then tell their tax advisor what they're doing. By that point, changes are expensive.

• Share your software shortlist with your asesor — they may have direct experience with candidates you're considering
• Ask which software their other clients are using successfully (this is free market research from someone who sees real results)
• Confirm they can work with the Modelo 303/390 exports from your chosen platform
• Discuss how the transition will affect your upcoming tax filings — timing your go-live mid-quarter vs. quarter-start has implications

One of my clients saved themselves a software switch by asking their asesor first. The asesor had been helping another client with the exact same tool and flagged a compatibility issue with the Basque Country supplementary reporting that would have been a deal-breaker. Fifteen minutes of conversation saved weeks of rework.

Phase 3: Technical Setup & Configuration (Week 5-8)

This is where my first implementation went sideways. I treated Phase 3 like a simple software configuration exercise. It's not. There are at least 3 dependencies that can each block you for weeks if you don't handle them proactively.

3.1 — Obtain your digital certificate (START THIS ON DAY 1 OF PHASE 3)

I'm putting this first because it's the single biggest cause of implementation delays. You need a valid digital certificate to sign invoices under Verifactu. Here are your options:

• FNMT certificate (free, but requires an in-person appointment at a government office): Apply online at sede.fnmt.gob.es, then visit your local Oficina de Registro. Current wait times in major cities: Madrid 3-5 weeks, Barcelona 2-4 weeks, Valencia 1-3 weeks. In smaller cities you can often get an appointment within days.
• Private certificate authority (Camerfirma, AC Firmaprofesional): Costs 40-80 euros but you can get one in 2-5 business days without the appointment backlog. Worth it if you're on a tight timeline.
• DNI electronico: If you already have an activated electronic DNI, you can use this. Check that the certificates on it haven't expired — they last 30 months and many people forget to renew.

Lesson from the trenches: I had a client in Madrid whose FNMT appointment was scheduled 6 weeks out. We paid 60 euros for a Camerfirma certificate to avoid blocking the entire implementation. Best 60 euros of the project. Don't let a free certificate cost you a month of delays.

3.2 — Configure Verifactu mode in your software

You have two modes. Here's how I decide between them:

• *VERIFACTU mode** (recommended for 90% of businesses): Real-time transmission of invoice records to AEAT. Invoices carry a verification label and QR code anyone can scan. Simpler to maintain because AEAT stores the records for you. This is what 26 out of 30+ companies I've helped chose.
• NO VERIFACTU mode: Records stay on your local system. You provide them on AEAT's request during audits. Choose this only if you have specific privacy concerns about real-time data sharing or if your internet connection is unreliable (rural operations, construction sites).

Configuration steps vary by software, but these are universal:

1. Navigate to the Verifactu or AEAT settings section in your software
2. Select your compliance mode (VERI*FACTU or NO VERIFACTU)
3. Enter your NIF/CIF and your AEAT census data
4. Upload or connect your digital certificate
5. Configure the connection to AEAT's endpoint (in VERI*FACTU mode, the software usually handles this automatically)
6. Set the hash algorithm — the regulation specifies SHA-256

3.3 — Set up invoice numbering sequences

Verifactu requires sequential, unbroken invoice numbering. This sounds simple but trips up companies with multiple invoice series. Check these points:

• Define your series codes (e.g., F-2027-0001 for standard invoices, R-2027-0001 for rectificativas)
• Ensure no gaps are possible — your software should auto-increment without manual override
• If you have multiple points of sale or branches, each needs its own series
• Plan the transition from your current numbering: the Verifactu chain starts fresh, but your old series should be closed cleanly on the last day before go-live

3.4 — Configure invoice templates with required elements

Every Verifactu invoice must include specific elements. Check that your templates show:

• QR code — positioned clearly, usually bottom-right or bottom-center. Minimum 30mm x 30mm. I've seen templates where the QR was squeezed to 15mm and scanners couldn't read it.
• *"VERIFACTU" label** (if using that mode) — must appear on the printed/PDF invoice
• Invoice hash reference — the software typically handles this automatically, but verify it appears
• NIF of the issuer and recipient — was already required, but double-check placement
• Correct IVA (VAT) breakdown — by rate (21%, 10%, 4%, exempt), exactly as before but now tamper-proof

Print a sample invoice and physically scan the QR code. Does it link to the AEAT verification page? If not, something is misconfigured.

3.5 — Migrate your client database and product catalog

• Export client data from your old system: company name, NIF/CIF, address, payment terms, contact email
• Clean the data before importing — I find 5-15% of client records have outdated NIFs, wrong addresses, or duplicate entries. Fix these before importing, not after.
• Import your product/service catalog with current pricing and IVA rates
• Verify that the import preserved special characters (accents, enes) — I've seen imports mangle "Gonzalez" into "Gonz\u00e1lez" and similar encoding issues

3.6 — Set up integrations

Connect your invoicing software to the other systems it needs to talk to:

• Bank account connection (for payment reconciliation — most cloud platforms support the major Spanish banks)
• ERP or CRM sync (client and product data, order-to-invoice flows)
• E-commerce platform connection (if you sell online and auto-generate invoices)
• Email service configuration (for sending invoices — test that they don't land in spam)
• Backup configuration — automated cloud backup if using VERI*FACTU mode; local + offsite backup if using NO VERIFACTU mode

3.7 — Configure user accounts and permissions

• Create accounts for all staff who will create, modify, or void invoices
• Set permission levels: who can create invoices, who can issue credit notes, who can change settings
• Enable two-factor authentication where available — your invoicing system now has legal significance
• Document the account structure so it survives staff turnover

3.8 — Configure audit trail and reporting

Verifactu is fundamentally an anti-fraud measure, and the audit trail is what makes it work. Make sure you set up:

• Automatic generation of the Libro Registro de Facturación (Invoice Record Book) — your software should generate this on demand for AEAT inspections
• Hash chain integrity reports — the ability to verify at any time that no invoices have been tampered with
• Monthly IVA summary exports compatible with Modelo 303 and the annual Modelo 390
• User activity logs: who created which invoice, when, and from which device

I had a client who skipped configuring proper reporting. When their asesor needed the Modelo 303 data for the first quarter, the export came out in the wrong format. It took a full day to reformat manually. Configuring it properly takes 30 minutes.

3.9 — Prepare your team with a pre-training briefing

Before formal training (which comes in Phase 5), hold a 30-minute briefing with everyone who touches invoices. Cover these points:

• What Verifactu is and why it matters (keep it simple: "invoices are now tamper-proof, the government can verify them")
• What will change in their daily workflow (new software, new invoice format, QR codes)
• What will NOT change (pricing, client relationships, the content of invoices)
• Timeline: when the switch happens and what's expected of them
• Who to contact with questions (your project owner)

This briefing prevents the biggest human problem in implementations: resistance to change. When people understand why something is changing and what's in it for them (faster invoicing, less paperwork, automated reporting), they cooperate instead of dragging their feet.

Phase 4: Testing & Validation (Week 7-10)

This is the phase companies want to skip. I know because 8 of my 30+ clients tried to skip it. Every single one regretted it.

One company went live without testing and discovered on Day 2 that their credit notes weren't generating valid hash chains. It took 3 days to fix, during which they couldn't issue any corrections. A client who'd overpaid was furious. Two weeks of testing would have caught that in 10 minutes.

4.1 — Create a testing plan

• Define test scenarios covering every invoice type your business uses: standard, simplified (tickets), rectificativas, multi-currency if applicable
• Include edge cases: zero-euro invoices, invoices with 100+ line items, invoices crossing midnight (I found a bug in one software where midnight invoices got the wrong date in the hash)
• Assign testers — at least one technical person and one person from the actual invoicing team
• Set pass/fail criteria for each test

4.2 — Test in sandbox/staging environment

Most Verifactu-certified software provides a sandbox mode that connects to AEAT's testing environment rather than production. Use it.

• Generate at least 25 test invoices across all your invoice types
• Verify each invoice's QR code resolves correctly in the AEAT sandbox
• Test the hash chain: generate 5 invoices in sequence, then verify the chain is intact in the software's audit log
• Deliberately try to break it: attempt to modify a sent invoice, attempt to delete one from the sequence, attempt to create an invoice with a future date. The system should block all of these.

4.3 — Test failure scenarios

What happens when things go wrong? You need to know before go-live, not during a client call.

• Internet outage (for VERI*FACTU mode): Disconnect your internet and try to create an invoice. Does the software queue it? How does it handle the pending transmission? When you reconnect, does it auto-send?
• Certificate expiration: Set a test certificate with a near-expiry date. Does the software warn you?
• Server downtime: If your cloud provider goes down, what's your fallback? Test the manual invoice process.
• Concurrent users: Have 3+ people create invoices simultaneously. Are the sequence numbers correct? I caught a race condition in one software where two users creating invoices at the same second got duplicate numbers.

4.4 — Run parallel invoicing (critical step)

For 2 full weeks minimum, run both your old system and the new system side by side. Every real invoice goes through both. Compare:

• Do the totals match exactly? (Watch for rounding differences in IVA calculations — I've seen 0,01 euro discrepancies that, while trivial, indicate a configuration problem)
• Are client details identical on both versions?
• Is the invoice numbering clean in the new system?
• Are the IVA rates applied correctly across all product categories?
• Do the PDF exports look professional and include all required Verifactu elements?

The parallel period is your safety net. One company discovered during parallel testing that their new software was applying 10% IVA to a product category that should have been 21%. That would have been a tax filing nightmare if caught after go-live. Two weeks of parallel testing saved them months of rectifications.

4.5 — Get sign-off from your asesor (accountant/tax advisor)

• Share sample invoices from the new system with your asesor fiscal
• Confirm the Modelo 303 and Modelo 390 data exports are correct
• Verify that the SII/Verifactu reporting format matches what AEAT expects
• Get written confirmation that they're satisfied with the setup — this protects you if questions arise later

4.6 — Security audit

• Verify that invoice records cannot be modified after generation (the whole point of Verifactu)
• Check that deleted invoices leave an auditable trace in the system log
• Confirm that the digital certificate is stored securely and access-controlled
• Review user permissions one final time — remove any test accounts, ensure principle of least privilege

Phase 5: Go-Live & Monitoring (Week 9-13)

Go-live day is anticlimactic when you've done the previous phases right. And that's exactly how it should be. The worst go-lives I've witnessed were at companies that skipped testing and treated launch day as the moment of truth. Don't do that. If you've done Phases 1-4 properly, go-live should feel like flipping a switch — not jumping out of a plane.

Here's your launch checklist:

5.1 — Pre-launch preparation (3 days before)

• Send an internal announcement to all staff: new system goes live on [date], here's what changes
• Distribute quick-reference guides for common tasks (create invoice, issue credit note, look up past invoice)
• Confirm your digital certificate is valid and won't expire within the next 6 months
• Verify AEAT endpoint connectivity (for VERI*FACTU mode) — test the connection one final time
• Close your old invoice series with the last invoice number and date. Document this for your records.

5.2 — Day 1 go-live actions

1. Switch the new system from sandbox/test mode to production mode
2. Create your first real Verifactu-compliant invoice
3. Immediately verify: QR code works, hash chain started correctly, AEAT received the record (in VERI*FACTU mode)
4. Have each team member create at least one invoice under supervision in the first hour
5. Monitor the AEAT transmission log for any errors or rejections

5.3 — First week monitoring

• Check the AEAT transmission/hash log daily for the first 5 business days
• Hold a 15-minute stand-up each morning with the invoicing team: any issues? any questions?
• Track time-to-create-invoice — if it's significantly slower than the old system, identify why and fix it
• Document any workarounds staff are inventing (these often indicate UX problems that need proper solutions)
• Keep your old system accessible in read-only mode for looking up historical invoices

5.4 — First month stabilization

• Review the first month's invoicing data for completeness and accuracy
• Run a trial Modelo 303 export and compare against manual calculations
• Address any recurring issues flagged by staff
• Collect feedback from clients who received the new-format invoices (especially about the QR code — some clients will ask questions)
• Verify backup procedures are running correctly

5.5 — Formally decommission the old system

• After 30 days of successful operation, formally close the old system
• Export a final archive of all historical data from the old system
• Store the archive securely — Spanish law requires keeping invoice records for 4 years (6 years for accounting books)
• Cancel the old software subscription (but verify you can still access archived data if needed)

Post-Implementation: Your First 90 Days

Going live is not the finish line. The first 90 days are where good implementations become great ones — or where rushed ones start falling apart.

I've seen companies celebrate on Day 1 and then spend Day 45 firefighting problems they could have prevented with proper post-launch monitoring. The most dangerous period isn't go-live itself — it's weeks 3-6, when the initial attention fades but the team hasn't yet built muscle memory with the new system.

Here's what to focus on:

Days 1-30: Stabilize

• Monitor AEAT transmission logs weekly (move from daily after the first week)
• Track and resolve any recurring error patterns
• Build a FAQ document from your team's actual questions (this is gold for future hires)
• Schedule a 30-day review meeting with your asesor to verify the first month's fiscal data is clean

Days 31-60: Optimize

• Analyze invoice creation times — identify bottlenecks and configure shortcuts or templates
• Set up automated recurring invoices for regular clients (most Verifactu software supports this)
• Configure automatic payment reminders to reduce accounts receivable delays
• Review your chart of accounts and IVA mappings — clean up anything that was migrated imperfectly
• Cross-reference your Modelo 303 data with the AEAT records — they should match exactly in VERI*FACTU mode

Days 61-90: Future-proof

• Document your complete Verifactu setup: software configuration, certificate details, series numbering, user accounts, integration settings
• Set calendar reminders for certificate renewal (FNMT certificates expire after 4 years; private ones after 2)
• Plan for the Ley Crea y Crece B2B e-invoicing requirement — this builds on top of Verifactu and the deadlines are approaching
• Schedule a quarterly review to check that nothing has drifted from compliance (software updates, new staff creating invoices wrong, etc.)
• Brief your backup person — what happens if the project owner goes on vacation or leaves the company?

The most common post-implementation failure I've seen: a company goes live successfully, relaxes, and then 4 months later discovers their digital certificate expired without anyone noticing. Set those reminders. Now. Not later.

The 10 Most Common Implementation Mistakes (And How to Avoid Them)

I've made some of these myself. Others I've watched clients make despite my warnings. Every one of these has cost real money and real stress.

What's frustrating is that they're all preventable. That's why I'm listing them here — so you can learn from other people's expensive mistakes instead of making your own. Number 3 is the one that causes the most damage. Number 10 is the one people are most likely to ignore.

1. Trusting "Verifactu-ready" claims without verification. Three vendors told my clients they were "ready." None had AEAT certification when we checked. Always verify the certification number directly with AEAT.
2. Not budgeting for the FNMT certificate timeline. The certificate itself is free, but the appointment wait in Madrid can be 5+ weeks. Budget for a private certificate if you're on a tight schedule. It's 60 euros to save a month.
3. Skipping the parallel testing period. Eight of my clients tried this. All eight had issues in the first week that testing would have caught. The IVA rate mismatch I mentioned earlier was the worst — it took 3 months of rectificativas to clean up.
4. Forgetting about secondary invoicing systems. Your main accounting software might be certified, but what about the e-commerce platform that auto-generates invoices? Or the POS terminal? Every invoice-generating system needs to be compliant.
5. Starting too late. Companies that started 3 months before their deadline had stressful, expensive transitions. Those that started 6 months out were relaxed. The math is simple: start now.
6. Not involving the asesor early enough. Your tax advisor needs to sign off on the setup, not discover it after go-live. Bring them in during Phase 2 at the latest. Their hourly rate is cheaper than fixing fiscal errors later.
7. Choosing software based on price alone. The cheapest option per month is rarely the cheapest over 3 years. I've seen this mistake cost companies 2.000+ euros in hidden fees, migration costs, and lost productivity.
8. Not training all staff who touch invoices. One company trained only the accounting department. Sales staff continued creating proforma invoices in Word, some of which accidentally got sent as real invoices without Verifactu compliance. Train everyone.
9. Ignoring the old system decommission. If you don't formally close and archive your old system, you risk someone accidentally creating a non-compliant invoice in it. This happened to one of my clients — a new hire found the old software shortcut on a shared computer and used it for 2 weeks before anyone noticed.
10. Forgetting certificate renewal. FNMT certificates last 4 years, but private certificates often last only 2. When they expire, your software can't sign invoices, which means every invoice you issue is non-compliant until you renew. Set. The. Reminder.

What This Actually Costs: Real Numbers From Real Implementations

I keep detailed cost records for every implementation I do. Here's the breakdown across 5 representative companies from different sizes and starting points:

Company A — Solo autonomo, graphic designer (Alicante)

• Previous system: Excel templates
• New software: Holded Basic (15 euros/month)
• Digital certificate: FNMT (free — got an appointment in 4 days in Alicante)
• Migration: None needed (manual client data entry, 2 hours)
• Training: Self-service, 1 hour
• Total first year: 180 euros | Time: 6 weeks part-time

Company B — 8-person marketing agency (Barcelona)

• Previous system: FreshBooks (not yet Verifactu-certified at the time)
• New software: Holded Premium (49 euros/month for 3 users)
• Digital certificate: Camerfirma (65 euros — Barcelona FNMT backlog was 4 weeks)
• Migration: Client data export/import (4 hours), bank reconnection (1 hour)
• Training: 2-hour session for invoicing staff
• Total first year: 718 euros | Time: 8 weeks

Company C — 35-person distributor (Madrid)

• Previous system: Sage 50 (already on it, needed Verifactu module activation)
• New software: Same Sage 50, updated plan (45 euros/month, up from 35 euros/month)
• Digital certificate: Already had FNMT certificate (renewed 6 months prior)
• Migration: N/A (same platform — Verifactu was a module activation)
• Configuration: 8 hours of consultancy with Sage partner (480 euros)
• Training: Half-day session for 6 invoicing staff (asesor's fee: 300 euros)
• Total first year: 1,320 euros | Time: 4 weeks

Notice the pattern? The cheapest implementations aren't always the smallest companies. Company C, with 35 employees, spent less than Company B with 8 — because they were already on a platform that supported Verifactu. Your starting point matters more than your company size.

I didn't include Companies D and E because they were outliers — a 2-person law firm that overthought everything for 14 weeks (final cost: 2.800 euros, mostly in consultancy fees they didn't need), and an 85-person manufacturer that needed custom API bridges between their ERP and the Verifactu system (final cost: 12.000 euros over 16 weeks). Most businesses won't face either extreme.

Compare all of these to the 50.000 euros annual penalty for non-compliance. Even the most expensive implementation I've done (12.000 euros) pays for itself the first year just in avoided fines. The math is not complicated.

My Final Recommendation

If I had to boil everything down to one paragraph of advice, it's this: start Phase 1 today, not next week. The companies that implement Verifactu successfully are not the ones with the biggest budgets or the fanciest software. They're the ones that started early and followed a checklist.

For most SMEs, I recommend Holded or Sage 50 depending on your size. For autonomos working alone, Holded or Zoho Books. If you already use an ERP like Odoo, check whether a Verifactu module is available before shopping for separate software.

The fines for non-compliance are up to 50.000 euros per fiscal year. The cost of doing this right is typically 1.500-4.000 euros once. The math speaks for itself.

This checklist got me from 4-month implementations to 6-week ones. I genuinely hope it does the same for you. If you want to understand the regulatory background behind all of this — the legislation, the technical requirements, the penalty structure — read the companion Verifactu Compliance Guide. That's the "what and why." This was the "how."

And one last piece of advice I give everyone: don't implement alone. Even if you're a solo autonomo, have your asesor review the final setup. Have a friend scan one of your QR codes. Have someone who isn't you create a test invoice. Fresh eyes catch things you've been staring at for weeks.

The companies that nail Verifactu implementation share three traits: they start early, they follow a structured process, and they test obsessively before going live. You have the first two now. Phase 4 is where you do the third. Don't skip it.

Good luck. You've got this.