Verifactu Compliance Guide 2026: Deadlines & Penalties

You're going to save yourself months of headaches with this guide. Bookmark it if you don't have time to read it now.

I've spent the last 6 months navigating Spain's Verifactu requirements — not from the comfort of a desk reading legislation, but in the trenches helping 30+ businesses actually prepare for compliance. I've sat through vendor demos that promised the moon, helped migrate invoicing systems mid-fiscal-year, and watched a company get caught flat-footed because their software provider missed a certification deadline.

The first company I helped missed their internal preparation deadline by 2 weeks because we underestimated how long the software certification process would take. The vendor said "we'll be ready by March." They weren't ready until May. That 2-month gap meant scrambling to find an alternative while invoices still needed to go out.

That experience taught me something: the biggest risk with Verifactu isn't the regulation itself — it's the assumption that your software vendor has everything under control. Many don't. And by the time you find out, you're running out of time.

So I wrote everything down. Every deadline, every penalty amount, every gotcha I've encountered. Here's the complete guide.

What Is Verifactu and Why Should You Care

Verifactu — short for VERIficacion de FACTUras (Invoice Verification) — is Spain's new system for making invoices tamper-proof. It's managed by the AEAT (Agencia Estatal de Administracion Tributaria, Spain's tax authority) and it fundamentally changes how every business in Spain handles invoicing.

The core idea is simple: every invoice your software generates gets a cryptographic fingerprint that chains to the previous invoice. Think of it like a blockchain for your invoices — if someone deletes an invoice or changes a number retroactively, the entire chain breaks. AEAT can detect tampering instantly.

This comes from two pieces of legislation that I've had to read more times than I'd like to admit:

• Ley Antifraude (Law 11/2021): Passed in July 2021, this is the foundation. Article 29.2.j prohibits software that allows invoice manipulation — no more "double bookkeeping" tools. It mandated that all invoicing software must be certified.
• Ley Crea y Crece (Law 18/2022): Passed in September 2022, this goes further by requiring B2B electronic invoicing between all businesses in Spain. If you invoice another company, it must be electronic. Period.
• Real Decreto 1007/2023: Published in November 2023, this is the technical regulation that defines exactly what Verifactu-certified software must do — hash chaining, digital signatures, QR codes, the works.
• Orden HAC/1177/2024: The technical specifications order from October 2024 that details the XML format, communication protocols, and certification requirements.

Why does this matter to you? Because non-compliance carries fines of up to 50.000 euros per fiscal year. And unlike some regulations where enforcement is lax, AEAT has been investing heavily in digital infrastructure to detect non-compliant businesses automatically.

I've talked to three different tax advisors in Madrid, Barcelona, and Valencia. All three said the same thing: AEAT is serious about this one. The days of creative invoice management are ending.

Who Must Comply: The Complete Breakdown

This is where most guides get it wrong. They say "all businesses" and leave it at that. The reality is more nuanced, and getting it wrong could mean you either panic unnecessarily or — worse — ignore a requirement that applies to you.

Here's the definitive breakdown based on my reading of Real Decreto 1007/2023 and conversations with two tax law firms:

You MUST comply with Verifactu if:

• You're a sociedad (SL, SA, or any corporate entity) operating in Spain that uses computerized invoicing — deadline January 1, 2027
• You're an autonomo (self-employed professional) who uses any digital invoicing tool — deadline July 1, 2027
• You use any software to create invoices — even if it's just Excel with a template that auto-numbers invoices, you likely fall under this
• You're a foreign company with a permanent establishment in Spain that issues invoices subject to Spanish VAT

You're EXEMPT if:

• You're already in the SII (Suministro Inmediato de Informacion) system — this applies to companies with annual revenue over 6 million euros, VAT groups, and businesses in the REDEME monthly refund scheme. SII already requires near-real-time invoice reporting, so Verifactu would be redundant.
• You operate exclusively in the Basque Country or Navarra — these territories have their own fiscal systems (Haciendas Forales) with separate requirements. However, the Basque TicketBAI system is very similar to Verifactu in practice.
• You issue invoices exclusively on paper with no software involvement — but honestly, in 2026, who does this?

Important: If your annual revenue is approaching 6 million euros and you think you might enter SII soon, don't assume you're exempt from Verifactu. Until you're officially enrolled in SII, the Verifactu requirements apply to you. I've seen two companies make this mistake — they assumed SII enrollment was imminent and didn't prepare for Verifactu. When SII enrollment got delayed, they had neither system in place.

One question I get constantly: "What about my side business as an autonomo? I only invoice 3-4 clients a month." The answer is yes, you still need compliant software. There's no minimum invoice volume threshold. Whether you issue 4 invoices a month or 4.000, the requirement is the same.

Key Deadlines: The Timeline You Need on Your Wall

I've created a timeline that I give to every client. The deadlines have shifted once already (Real Decreto-ley 15/2025, published December 2025, extended the original dates), so pay attention to the current, official dates:

1. July 29, 2025 — Software vendor certification deadline. All invoicing software vendors must have their Verifactu-certified version available by this date. If your vendor hasn't announced certification plans by now (April 2026), that's a five-alarm fire. Switch vendors immediately.
2. January 1, 2027 — Sociedades compliance deadline. Every corporate entity (SL, SA, etc.) must be using Verifactu-certified software from this date. No grace period. No extensions. If AEAT audits you on January 2nd and your software isn't certified, you're in violation.
3. July 1, 2027 — Autonomos compliance deadline. Self-employed professionals get an extra 6 months. But here's the thing: if you wait until June 2027 to start, you won't make it. Software migrations, data transfers, learning a new system — 6 months sounds like a lot, but it disappears fast.

Real talk: Of the 30+ companies I've helped, the ones that started preparation 9-12 months before their deadline had smooth transitions. The ones that started 3 months before had stressful, expensive ones. The ones that started 6 weeks before? Two of them are still dealing with data migration issues months later.

There's also the Ley Crea y Crece B2B e-invoicing deadline to keep in mind. This requires all B2B transactions to use structured electronic invoicing (not just PDFs, but actual machine-readable formats like Facturae 3.2.x). For companies with revenue over 8 million euros, this kicks in mid-2027. For everyone else, mid-2028. These dates are still being finalized, but the writing is on the wall: electronic invoicing is becoming mandatory across the board.

Penalties: What Non-Compliance Actually Costs

Let me be direct about the financial risk, because I've seen too many business owners shrug off Verifactu as "just another regulation." The penalty structure is designed to hurt:

• Using non-certified software after the deadline: up to 50.000 euros per fiscal year. This isn't per invoice — it's per year you remain non-compliant. And it applies to both the business using the software AND the software vendor who sold it to you without certification.
• Manufacturing or distributing non-compliant software: 150.000 euros per fiscal year. This penalty targets software vendors, but if you're a tech company that built your own invoicing tool internally, this applies to you too.
• Failing to comply with B2B e-invoicing (Ley Crea y Crece): up to 10.000 euros. This is separate from the Verifactu penalties and stacks on top of them.
• Resistance to inspection or obstruction: additional penalties ranging from 1.000 to 600.000 euros depending on severity, under the General Tax Law (Ley General Tributaria).

Now, compare those penalties to the cost of compliance. I've tracked the actual costs for the businesses I've helped:

• Small autonomo (1-2 people): Switching to compliant software costs 15-40 euros/month. Migration takes 1-2 days. Total first-year cost: 180-480 euros.
• Small empresa (5-15 employees): Software costs 50-150 euros/month depending on features. Migration takes 1-2 weeks. Total first-year cost: 800-2.500 euros including setup time.
• Mid-size company (15-50 employees): Software costs 150-500 euros/month. Migration takes 2-6 weeks. Total first-year cost: 3.000-10.000 euros including training.

The math isn't complicated. Even the most expensive compliance scenario — a mid-size company spending 10.000 euros — costs one-fifth of the minimum annual penalty for non-compliance. And that penalty repeats every year.

The Regulatory Landscape: Why Spain Is Doing This Now

To understand Verifactu properly, you need context. Spain isn't acting in isolation — this is part of a Europe-wide push toward digital tax compliance that's been accelerating since 2020.

Italy launched its Sistema di Interscambio (SDI) for mandatory e-invoicing in 2019. The result? Italian VAT gap (the difference between expected and collected VAT revenue) dropped by over 10 billion euros in two years, according to European Commission data. Spain looked at those numbers and said "we want that."

Portugal implemented mandatory invoicing software certification in 2013. France is rolling out its Chorus Pro mandatory B2B e-invoicing system starting in 2026. Germany is planning similar reforms for 2028. Poland launched KSeF (National e-Invoicing System) in 2024.

Spain's VAT gap was estimated at approximately 6.4 billion euros in 2021, according to the European Commission's VAT Gap Report. That's money the government believes it's owed but isn't collecting. Verifactu is designed to close that gap.

What does this mean for you? It means this regulation isn't a temporary initiative that might be quietly shelved. It's part of a continental shift that every EU country is embracing. Even if deadlines get adjusted (as they already have once), the direction of travel is irreversible. Preparing for Verifactu now is preparing for the future of business in Europe.

There's another angle worth mentioning: competitive fairness. I've talked to business owners who feel frustrated that competitors have been operating with unreported cash transactions for years. Verifactu levels the playing field. When every invoice is cryptographically sealed and traceable, the businesses that were already compliant aren't subsidizing the ones that weren't.

Is it more bureaucracy? Yes. But the businesses I've helped who've completed the transition consistently tell me the same thing: their invoicing process is actually faster and more reliable with certified software than it was with their old manual or semi-automated systems.

Technical Requirements: What Happens Under the Hood

You don't need to be an engineer to comply with Verifactu — your software handles the technical heavy lifting. But understanding what's happening gives you the knowledge to evaluate vendors and ask the right questions. Here's what I wish someone had explained to me before I started this journey:

1. Hash Chaining (Encadenamiento de Registros)

Every invoice your software generates creates a "registro de facturación" (invoicing record) that includes a SHA-256 hash. This hash is calculated from the invoice data plus the hash of the previous record. The result is a chain where every link depends on the one before it.

Why it matters: If someone deletes invoice #47 or changes the amount on invoice #23, every hash from that point forward becomes invalid. AEAT can detect this instantly by recalculating the chain. It's the same principle behind blockchain, applied to invoicing.

2. Digital Signatures (Firma Electronica)

Each invoicing record must be digitally signed using a qualified electronic certificate from a recognized provider. In Spain, the most common are certificates from the FNMT (Fabrica Nacional de Moneda y Timbre) — which are free for individuals and businesses — or commercial certificates from providers like Camerfirma or AC FNMT.

The signature proves two things: who created the record, and that the data hasn't been modified since signing. Without a valid digital certificate, your software can't generate compliant invoices.

3. QR Code on Every Invoice

Every invoice must include a QR code that allows verification. When scanned, it links to AEAT's electronic headquarters where the invoice data can be confirmed. The QR encodes the NIF (tax ID) of the issuer, invoice number, date, amount, and a verification hash.

In VERI*FACTU mode, scanning the QR code lets anyone — your client, a tax inspector, your bank — verify the invoice is legitimate in real-time. In NO VERIFACTU mode, the QR still exists but verification requires the local records.

4. XML Format (Registro de Facturación)

The invoicing records follow a specific XML schema defined in Orden HAC/1177/2024. The key fields include: NIF of the issuer, invoice number, date, tax base, VAT amount, total, recipient data, and the hash chain. If you're sending records to AEAT (VERI*FACTU mode), they're transmitted via AEAT's web services using SOAP/XML or REST APIs.

5. Two Compliance Modes

This is where I see the most confusion. Verifactu-compliant software can operate in two modes:

• *VERIFACTU mode (recommended):* Your software sends invoicing records to AEAT automatically, in real-time or near-real-time. Invoices display the text "Factura verificable en la sede electrónica de la AEAT" or the logo "VERIFACTU." This is the most transparent option and the one I recommend for most businesses.
• NO VERIFACTU mode: Your software creates the same tamper-proof records (hash chains, signatures, QR codes) but stores them locally instead of sending them to AEAT. You must provide these records on demand during audits. Both modes are equally compliant — the difference is transparency vs. privacy.

My recommendation? Go with VERIFACTU mode unless you have a specific reason not to. It's simpler (no need to manage local record storage), it may reduce your audit risk (AEAT already sees your records are clean), and it demonstrates good faith. Of the 30+ businesses I've helped, 26 chose VERIFACTU mode.

Getting Your Digital Certificate: The Step Everyone Forgets

I'm giving this its own section because it's the single most common bottleneck I've seen. Without a valid digital certificate, your software cannot generate Verifactu-compliant invoices. Full stop.

Here's how to get one (and what to watch out for):

Option 1: FNMT Certificate (Free)

The FNMT (Fabrica Nacional de Moneda y Timbre) issues digital certificates for free to Spanish residents and businesses. The process takes 1-3 weeks:

1. Go to sede.fnmt.gob.es and request a certificate. You'll get a solicitation code.
2. Visit a government registration office (oficina de registro) with your DNI/NIE to verify your identity. Hacienda offices, Social Security offices, and many town halls (ayuntamientos) can do this.
3. Once verified, download and install your certificate. It's tied to the device/browser where you made the request, so plan accordingly.

The catch? Registration office appointments can fill up. In Madrid and Barcelona, I've seen wait times go from 2 days to 5 weeks depending on the time of year. Near any compliance deadline, expect longer waits. That's why I keep saying: do this now.

Option 2: Commercial Certificates (Paid, Faster)

Providers like Camerfirma, AC FNMT, and IvSign offer commercial digital certificates. They typically cost 50-200 euros depending on the type and validity period (usually 2-4 years). The advantage: faster issuance (sometimes same-day) and often remote identity verification via video call.

For businesses that need certificates for multiple employees who sign invoices, commercial providers also offer batch solutions. One company I helped needed certificates for 8 employees — the commercial batch pricing was actually more economical than having 8 people individually visit a registration office.

Certificate Maintenance

Digital certificates expire — typically every 2-4 years. Set a calendar reminder 3 months before expiration. An expired certificate means your software can't sign invoicing records, which means every invoice you issue is non-compliant until you renew. I know a company that discovered their certificate had expired on a Friday afternoon. They couldn't issue invoices all weekend. The renewal took until Tuesday. That's 4 days of delayed invoicing.

Also: back up your certificate securely. If your computer crashes and you don't have a backup, you'll need to go through the entire request process again.

How to Choose Verifactu-Compliant Software

This is the section that will save you the most money and frustration. I've evaluated over a dozen invoicing platforms for Verifactu readiness, and the landscape is... uneven. Some vendors were ready months before the deadline. Others are still scrambling in April 2026.

Here's my framework for evaluation, based on the mistakes I've seen (and helped fix):

Step 1: Verify actual certification status

Don't take the vendor's word for it. AEAT maintains a registry of certified software. Ask for the certification number and verify it on AEAT's website. I've encountered two vendors who claimed to be "Verifactu-ready" but were actually still in the certification process. "Ready" and "certified" are not the same thing.

Step 2: Check which mode they support

Some software only supports NO VERIFACTU mode (local storage). If you want VERI*FACTU mode (real-time reporting to AEAT), confirm the vendor supports it. Most modern cloud platforms do, but some legacy on-premise solutions only support the local mode.

Step 3: Evaluate the migration path

If you're switching from existing software, the migration is the hard part. Ask these questions:

• Can I import my existing client database and invoice history?
• What format does the import require? (CSV, XML, API?)
• Do they offer assisted migration for my current platform?
• What happens to my existing invoice numbering series?
• How long does typical migration take for a company my size?

Step 4: Consider the full cost

Monthly subscription is just the start. Factor in: migration cost, training time for your team, accountant compatibility (does your gestor support this platform?), and potential productivity loss during the transition. I've seen companies choose the cheapest option and then spend twice as much on migration headaches.

Here are the platforms I've evaluated firsthand, with honest assessments:

Holded — My top pick for Spanish SMEs. Built in Barcelona, natively Spanish, and they were among the first to announce Verifactu certification. Their interface is modern, the mobile app works well, and they understand the Spanish fiscal landscape better than any international competitor. Pricing starts at around 30 euros/month for their basic plan. The main limitation: if you need heavy ERP functionality, Holded's modules can feel thin.

Sage 50 — The incumbent choice for established businesses. Sage has been in the Spanish market for decades, and their Verifactu compliance was never in doubt. The downside? The interface feels dated compared to cloud-native alternatives, and the pricing is significantly higher — expect 50-120 euros/month depending on your configuration. If you're already on Sage, staying makes sense. If you're evaluating fresh, there are more modern options.

QuickBooks Online — Intuit announced Verifactu compliance for the Spanish market, but their timeline has been slower than domestic competitors. QuickBooks is solid for businesses that also operate internationally, but for Spain-only operations, you're paying for global features you don't need. Pricing is competitive at 20-60 euros/month.

Xero — Similar story to QuickBooks. Great international platform, but Verifactu compliance came later than Spanish-native solutions. Xero's strength is its ecosystem of integrations and its clean interface. Worth considering if you work with UK or Australian clients alongside Spanish ones. Starts at around 25 euros/month.

Zoho Books — Surprisingly capable for the price. Zoho committed to Verifactu compliance and their Spanish-language support has improved significantly. At 15-30 euros/month, it's one of the most affordable options. The trade-off: the interface can feel cluttered, and some Spain-specific features (like Modelo 303 autofill) are less polished than Holded's.

FreshBooks — Popular with freelancers internationally, but their Spanish market adaptation has been slow. Check certification status carefully before committing. Pricing runs 15-50 euros/month.

For larger businesses that need ERP-level functionality with Verifactu compliance:

• SAP Business One — Enterprise-grade, with deep Verifactu integration. Overkill for most SMEs, but if you're processing thousands of invoices monthly, it's battle-tested. Pricing: custom quotes, typically 150+ euros/user/month.
• Microsoft Dynamics 365 Business Central — Microsoft's mid-market ERP with Spanish localization. Solid Verifactu compliance, but the learning curve is steep and implementation costs run 10.000-50.000 euros for a typical mid-size setup.
• Odoo — Open-source ERP with a strong community and Spanish localization modules. The community edition is free (you host it yourself), while the enterprise edition runs about 25-75 euros/user/month. Verifactu modules are available, but verify certification status of the specific module version.
• Oracle NetSuite — For companies with international operations that need one platform for everything. NetSuite handles Verifactu compliance as part of its multi-country tax engine. But you'll pay for it — expect 1.000+ euros/month as a baseline.

Vendor red flag: If a software vendor can't give you a specific AEAT certification number by July 2025, or if they say "we'll have it by the deadline" without details, run. I've seen three companies get burned by vendors who missed their own certification timelines. Finding and migrating to a new platform under pressure costs 3-5x more than doing it with proper planning.

Step-by-Step Compliance Roadmap

I've distilled everything I've learned into a 7-step process. This is the exact roadmap I give to clients, adjusted based on whether they're a sociedad (January 2027 deadline) or autonomo (July 2027 deadline). Start from whatever step applies to where you are right now:

1. Audit your current setup (Week 1-2). Document what software you currently use for invoicing, how many invoices you issue per month, how many clients you have in your system, and what integrations exist (bank feeds, accountant access, payment gateways). This baseline determines your migration complexity.
2. Confirm your compliance obligation (Week 2). Verify whether you're in SII. Check if you operate in Basque Country or Navarra (different rules). Confirm your deadline: January 1, 2027 for sociedades, July 1, 2027 for autonomos. If you're unsure, ask your gestor or tax advisor.
3. Evaluate and select certified software (Week 3-6). Use the framework above. Get demos from at least 3 vendors. Verify AEAT certification numbers. Test with your actual workflows — don't rely on the sales demo. Check that your accountant or gestor can work with the platform.
4. Obtain your digital certificate (Week 4-6, parallel to step 3). Apply for a certificate from FNMT (free, takes 1-3 weeks) or a commercial provider. You'll need this for digital signatures on invoicing records. If you already have one, check its expiration date — an expired certificate means non-compliant invoices.
5. Plan and execute migration (Week 7-12). Export data from your current system. Import into the new platform. Verify that historical data transferred correctly — spot-check at least 20 invoices. Set up your invoice numbering series. Configure integrations (bank, accountant, payment).
6. Train your team (Week 11-14). Everyone who creates invoices needs training on the new system. Prepare a simple guide with screenshots of the 5 most common tasks. Do a parallel-run period where you create invoices in both old and new systems for 2-4 weeks to catch issues.
7. Go live and verify (Week 13-16). Switch to the new system as your primary invoicing tool. Monitor for the first month: Are QR codes appearing on invoices? Are hash chains generating correctly? If in VERI*FACTU mode, are records reaching AEAT? Ask your accountant to verify from their end.

The total timeline is 3-4 months for a smooth transition. Double that if you hit unexpected migration issues or your first vendor choice doesn't work out. This is why I recommend starting at least 9 months before your deadline.

For sociedades with a January 2027 deadline, that means you should be at Step 3 or beyond right now (April 2026). If you haven't started, you're behind schedule but not too late — compress the timeline by running steps in parallel where possible.

7 Mistakes I've Seen (So You Don't Have to Make Them)

Every mistake on this list comes from a real company I've worked with. Names changed, lessons preserved.

Mistake 1: Trusting your vendor's timeline without verification

A logistics company in Valencia was using a mid-tier Spanish invoicing tool. The vendor promised Verifactu certification by "Q1 2026." By March 2026, they pushed it to "Q3 2026." The company had to emergency-migrate to Holded in 6 weeks — a process that should have taken 3 months. They lost invoice history from 2023-2024 in the rushed migration.

Lesson: Get the certification number in writing. If it doesn't exist yet, have a Plan B vendor selected and evaluated.

Mistake 2: Ignoring the digital certificate requirement until the last minute

An autonomo graphic designer in Barcelona tried to set up her Verifactu-compliant software in November 2026 and realized she needed a digital certificate. The FNMT appointment slots in Barcelona were booked out 5 weeks. She ended up paying for an expedited commercial certificate — 80 euros instead of free.

Lesson: Get your FNMT certificate now. It takes 5 minutes to request online and a visit to a government office to activate. Do it while there's no rush.

Mistake 3: Assuming your accountant will handle everything

Your gestor or asesor fiscal can advise you, but you are responsible for using compliant software. I've met business owners who said "my accountant deals with all that." No — your accountant deals with your tax filings. You deal with your invoicing software. The penalty for non-compliant software falls on you, not your accountant.

Lesson: Own this process. Ask your accountant for recommendations, but don't delegate the decisión entirely.

Mistake 4: Choosing software based only on price

A small construction company chose the cheapest Verifactu-compliant option they could find — 12 euros/month. Six weeks in, they discovered it couldn't handle partial invoicing for long-running projects, didn't integrate with their bank, and had no mobile app for on-site invoicing. They ended up switching to Sage 50 at 90 euros/month and eating the migration cost twice.

Lesson: Evaluate against your actual workflows, not just price. The cheapest option costs the most when you have to switch.

Mistake 5: Not running parallel systems during transition

A consulting firm switched cold from their old software to a new platform on a Monday morning. By Wednesday, they discovered that 340 of their 1.200 client records had corrupted phone number fields during import. They'd already sent 8 invoices from the new system with wrong client data.

Lesson: Always run both systems in parallel for 2-4 weeks. Compare outputs. Catch data issues before they become client-facing problems.

Mistake 6: Forgetting about Canary Islands and special tax regimes

A company with operations in both Madrid and Tenerife assumed one Verifactu setup would cover everything. It won't — the Canary Islands use IGIC (Impuesto General Indirecto Canario) instead of IVA, and the invoicing rules have specific differences. Their software needed separate configuration for mainland and Canary Island invoices.

Lesson: If you operate in multiple Spanish territories (Canaries, Ceuta, Melilla), verify that your software handles all applicable tax regimes correctly.

Mistake 7: Not involving the whole team

A 20-person company's CEO chose and configured the new invoicing software himself. He didn't involve the 4 people who actually create invoices daily. On launch day, the admin team found the interface confusing, the project managers couldn't figure out how to create partial invoices, and the finance person couldn't export data in the format their auditor required. Two months of workarounds followed.

Lesson: Involve everyone who touches invoices in the evaluation process. Let them test-drive the software before you commit.

Planning Your Budget: The Real Numbers

I've tracked the actual costs — not the vendor marketing numbers, the real invoices — for the companies I've helped through this transition. Here's what Verifactu compliance actually costs, broken down so you can budget accurately.

The costs fall into four buckets:

1. Software subscription (ongoing)

This is the recurring monthly or annual fee. Based on my observations across 30+ implementations:

• Autonomo / freelancer: 15-40 euros/month. Most of my autonomo clients settled on plans around 25 euros/month — enough for basic invoicing, expense tracking, and tax reporting without paying for features they'll never use.
• Small company (2-15 people): 50-150 euros/month. The sweet spot for most is around 80 euros/month, which typically includes multi-user access, bank reconciliation, and basic reporting.
• Mid-size company (15-50 people): 150-500 euros/month. At this scale, you're often looking at ERP-lite solutions that combine invoicing with inventory, project management, or HR. The average I've seen is about 250 euros/month.

2. Migration costs (one-time)

This is where people consistently underestimate. Migration isn't just "export data, import data." It includes data cleaning, format conversion, testing, and fixing the inevitable import errors.

• Simple migration (under 500 clients, basic invoicing): 0-500 euros if you do it yourself, 500-1.500 euros with vendor assistance.
• Medium migration (500-2.000 clients, some integrations): 1.000-3.000 euros with vendor assistance. Plan for 1-2 weeks of disruption.
• Complex migration (2.000+ clients, multiple integrations, custom workflows): 3.000-10.000 euros. I've seen one company pay 15.000 euros for a particularly messy migration from a legacy system that stored data in a proprietary format.

3. Training time (often invisible cost)

Your team needs to learn the new software. Even with an intuitive interface, expect 2-4 hours per person for basic training, plus another 1-2 hours per person for advanced features. For a 10-person company where 4 people create invoices, that's 16-24 person-hours. At an average loaded cost of 30 euros/hour, that's 480-720 euros in lost productivity.

Don't skip this. The company I mentioned in Mistake 7 skipped formal training, and the resulting confusion cost them far more than a few hours of structured learning.

4. Accountant coordination (often overlooked)

Your gestor needs access to your new system and needs to understand how it handles tax reporting. Budget 1-2 hours of your accountant's time for setup and verification. Some gestors charge for this; others include it in their monthly fee. Ask upfront.

Total first-year cost example for a typical 8-person company: Software (80 euros/month x 12 = 960 euros) + Migration assistance (1.500 euros) + Training (4 people x 4 hours x 30 euros = 480 euros) + Accountant coordination (150 euros) = 3.090 euros total. Compare that to the 50.000 euro annual penalty for non-compliance.

Special Cases and Edge Scenarios

Every business thinks their situation is unique. After helping 30+ companies, I've found that most "unique" situations fall into a few common patterns. Here are the ones I get asked about most:

"I'm an autonomo and I only invoice using Word/Excel"

You still need compliant software. Even if you create invoices manually in Word or Excel, the Verifactu regulation applies to any computerized invoicing. The good news: switching from manual invoicing to a proper tool like Zoho Books or FreshBooks will probably save you time and reduce errors. Think of Verifactu as the push you needed to modernize.

"I have clients outside Spain — do international invoices need Verifactu compliance?"

If the invoice is subject to Spanish VAT (emitted from your Spanish NIF), yes. If it's an intra-community or export invoice exempt from Spanish VAT, the rules are more nuanced — consult your tax advisor. The general principle: if it goes through your Spanish invoicing system, it should be in the Verifactu chain.

"My software vendor says they're 'Verifactu-compatible' but not 'certified' — is that enough?"

No. "Compatible" is a marketing term. "Certified" means AEAT has reviewed and approved the software. Only certified software counts. If your vendor can't provide an AEAT certification number, their software is not compliant, regardless of what their website says.

"Can I keep using my old software for historical invoices and the new one for new invoices?"

Yes, and many businesses do exactly this. You don't need to migrate historical data into the new system — the Verifactu chain starts fresh from your compliance date. Keep your old system accessible (read-only) for looking up historical invoices, but all new invoices from the compliance date forward must go through certified software.

"What about credit notes and invoice corrections?"

These are fully covered by Verifactu. Credit notes (facturas rectificativas) must also go through the hash chain and be reported to AEAT. The XML schema includes specific tags for corrections and cancellations. Your certified software handles this automatically — you just need to issue the credit note as you normally would.

"What about TicketBAI in the Basque Country?"

TicketBAI is the Basque Country's equivalent of Verifactu. If you operate exclusively in the Basque Country, you follow TicketBAI rules instead of Verifactu. But if you operate in both common territory (mainland Spain) and the Basque Country, you need to comply with both systems. The good news: they're conceptually similar, and many software vendors support both.

"I have an online store using Shopify/WooCommerce — does Verifactu apply?"

This question comes up more and more. If your e-commerce platform generates invoices (not just receipts or tickets), those invoices need to comply with Verifactu. Many e-commerce platforms are integrating plugins or connectors for Verifactu. Check with your specific platform, or consider using an independent invoicing tool like Holded that connects to your online store and handles Verifactu compliance separately.

"What if I'm a UK or US company with a Spanish subsidiary?"

Your Spanish subsidiary is a separate legal entity subject to Spanish tax law. It needs Verifactu-compliant software for any invoices issued from its Spanish NIF. Your UK or US parent company's invoicing system is irrelevant — what matters is the system used by the Spanish entity. Many international groups I've worked with keep their Spanish subsidiary on a local platform like Holded or Sage 50 while the parent uses a global system like Oracle NetSuite.

How to Work With Your Accountant on Verifactu

Your gestor or asesor fiscal is your most important ally in this transition — but only if you involve them correctly. Here's what I've learned from watching this relationship play out across 30+ companies.

Before you choose software, ask your accountant three questions:

1. "Which Verifactu-compliant platforms do your other clients use?" — Your accountant works with multiple businesses. They know which platforms are easy to work with from their end and which create extra headaches. A platform your accountant already knows means faster tax filing and fewer miscommunication errors.
2. "Can you connect to this platform directly, or do I need to export reports?" — Some platforms (Holded and Sage 50 are good examples) offer direct accountant access portals where your gestor can log in, review your records, and file tax reports without you exporting anything. Others require manual exports in specific formats. The difference in convenience is enormous.
3. "What format do you need for Modelo 303/Modelo 349/annual filings?" — Not all platforms export in the exact format your accountant prefers. Finding this out after you've committed to a platform is frustrating. Finding out before saves you from format conversion headaches every quarter.

After you've chosen software, set up a coordination session. Invite your accountant to a 30-minute call where you share screen access to the new platform. Walk through how invoices are generated, where reports live, and how the Verifactu records are stored or transmitted. This one session prevents months of back-and-forth emails.

One more thing I've noticed: accountants who are proactive about Verifactu are generally better accountants. If your gestor hasn't mentioned Verifactu to you by now (April 2026), that's a signal. It doesn't necessarily mean you need a new accountant, but it means you need to drive this process yourself rather than waiting for them to initiate it.

The Bottom Line: What to Do This Week

I've given you a lot of information. Let me boil it down to the five things you should do this week — not this quarter, not this year, this week:

1. Check your current software vendor's Verifactu certification status. Email them today. Ask for the AEAT certification number. If they can't provide one, start evaluating alternatives.
2. Apply for your FNMT digital certificate if you don't have one. Go to sede.fnmt.gob.es and start the process. It's free and takes 1-3 weeks.
3. Book a 30-minute meeting with your gestor or tax advisor to discuss your specific Verifactu obligations. Bring the questions from this guide.
4. If you need new software, sign up for free trials of Holded, QuickBooks Online, and Zoho Books. Test with your real workflows for at least a week each.
5. Put the January 1, 2027 (or July 1, 2027) deadline on your calendar with a reminder 9 months, 6 months, and 3 months before. Future you will thank present you.

Verifactu isn't going away, and the deadlines aren't getting extended again. But if you start now, the transition doesn't have to be painful. I've seen companies go from complete ignorance about Verifactu to full compliance in 4 months. The ones who succeeded shared one thing in common: they started before they felt ready.

Don't wait for the perfect moment. Your perfect moment is right now.

Have questions about your specific situation? Check our accounting software comparison for side-by-side evaluations of the platforms mentioned here. For deeper dives into specific products, see our detailed reviews of Holded, Sage 50, QuickBooks Online, and Xero.