Mandatory Electronic Invoicing in Spain: VeriFactu and Ley Crea y Crece Guide

Mandatory Electronic Invoicing in Spain: VeriFactu and Ley Crea y Crece Guide

If you sell into Spain, have a Spanish subsidiary, or run finance for an SME on Spanish soil, you've probably heard three names in the same conversation: VeriFactu, Ley Crea y Crece, and mandatory electronic invoicing. Three labels, two regulations, several shifting deadlines — and one recurring question: what am I supposed to do, when, and how?

The confusion is understandable. Two regulations, months apart, both touching invoicing, both staged. The government has postponed deadlines more than once. International teams end up reading contradictory English summaries, while local advisors fluent in IRPF and corporate tax aren't always comfortable explaining digital signatures, Facturae XML or real-time AEAT integration.

This guide clears that up, written for non-Spanish companies invoicing Spanish counterparties and for Spanish companies whose finance discussions happen in English. Every date and sanction is cited against the BOE, Spain's official gazette. Think of Spain's e-invoicing framework as the local cousin of Italy's Sistema di Interscambio (SdI) or France's Chorus Pro / Factur-X — same direction of travel (structured formats, real-time visibility, traceable B2B flows), different plumbing. If you want help implementing it, here's how we prepare SMEs for VeriFactu and Ley Crea y Crece.

What exactly is an "electronic invoice" in Spain?

An electronic invoice, in Spain's regulatory sense, is not a PDF attached to an email. It's a tax document issued in a structured format (XML Facturae for the Spanish standard, UBL or CII in broader European contexts), digitally signed with a qualified certificate, and stored on a system guaranteeing integrity, legibility and full traceability.

The word that matters is "structured." A PDF is designed to be read by a human: its fields are free text inside a visual layout. An electronic invoice is a file a machine parses unambiguously: <ID> is the invoice number, <TaxableAmount> is the tax base, <TaxTotalAmount> is the VAT. That distinction enables automatic reconciliation, real-time cross-checks with the tax authority, and automatic rejection of invoices with the wrong VAT applied.

The minimum characteristics the regulation demands:

• Structured format that allows automated processing (XML, EDIFACT, or equivalent).
• Electronic signature based on a qualified certificate, guaranteeing authenticity and integrity.
• Immutable: any correction requires a rectifying invoice, not an overwrite of the original.
• Auditable: the system must demonstrate, to a tax inspector, every movement on every invoice.
• Status tracking: B2B electronic invoices carry defined states (issued, accepted, rejected, paid) that must be recorded and communicated.

If a PDF is like a WhatsApp message — formatted for a human eye — an electronic invoice is closer to a JSON payload: structured, addressable, machine-native. Spanish regulation doesn't ban PDFs outright; to a retail consumer, a PDF or paper ticket remains legitimate. But in B2B, and in any scenario involving a Sistema Informático de Facturación (SIF, Invoicing Software System), the structured version must also exist.

Spain is converging toward what Italy did with FatturaPA in 2019, what France is rolling out with Factur-X and Chorus Pro, and what the EU's ViDA directive will eventually harmonise. If you already file into SdI or Chorus Pro, the model is familiar — formats differ, but "structured, signed, traceable" is shared.

Electronic invoice vs digital invoice vs PDF

The most common mix-up in Spanish SMEs — and in international finance teams new to Spain — is treating "electronic invoice" and "digital invoice" as synonyms. They're not, and the difference has legal consequences.

Digital invoice is generic: any invoice not printed on paper. A PDF emailed to a customer or a scanned JPG both qualify — neither is automatically an electronic invoice in the regulatory sense.

Electronic invoice requires two additional conditions: a structured format, and an electronic signature backed by a recognised digital certificate. A PDF without a digital signature — even one generated by a computer — is not, strictly speaking, an electronic invoice under Ley Crea y Crece or the AEAT's SII framework.

In practice, the "send a PDF to my customer" workflow most Spanish SMEs use today will not, on its own, satisfy Ley Crea y Crece once the implementing regulation is fully in force. The structured, signed version will need to be issued either alongside or in place of the PDF.

Two regulations, two timelines: VeriFactu and Ley Crea y Crece

The piece that most disorients foreign teams: Spain has two separate regulations aimed at invoicing, with different purposes, converging on overlapping deadlines without being the same thing.

VeriFactu (Royal Decree 1007/2023 and its amendments) regulates Invoicing Software Systems (SIF). It imposes technical requirements on the software you use to issue invoices: each record must be chained via hash to the previous one, signed by the system, and — optionally in baseline mode, mandatorily in "VeriFactu mode" — transmitted in real time to the AEAT (Spanish tax authority). The objective is fraud prevention: no invoice can be issued, altered or deleted without leaving an immutable trail.

Ley Crea y Crece (Law 18/2022 + RD 238/2026) regulates the obligation to issue an electronic invoice between businesses and professionals. When invoicing another company or self-employed professional, the invoice must be electronic in the strict sense (structured and signed) rather than a PDF. The underlying objective is late-payment policy: traceable status gives the state visibility into payment terms and enables enforcement.

The two are orthogonal. A self-employed dentist who only invoices patients is subject to VeriFactu but not to Ley Crea y Crece. A purely B2B software house is subject to both. An agricultural cooperative that sells direct-to-consumer but buys supplies B2B is only affected by Ley Crea y Crece on the receiving side.

Prepare for both in one project and the work is done once. Rush VeriFactu first and tackle Ley Crea y Crece later, and you pay twice: consultancy, development and operational downtime. For international teams used to Italy's one-hub SdI model, the staggered Spanish approach can feel fragmented — but it's deliberate, giving vendors time to align specs.

VeriFactu (RD 1007/2023): what, who, when

Royal Decree 1007/2023, of 5 December, approved the regulation establishing requirements for Invoicing Software Systems — the Reglamento SIF (RRSIF) — and was published in the BOE on 6 December 2023 at BOE-A-2023-24840. It was later developed technically by Ministerial Order HAC/1177/2024, which set the detailed specifications software must comply with.

The regulation defines two modes. Non-VeriFactu mode (mandatory for all obligated parties): software must chain records by hash and sign them, without real-time transmission to AEAT. VeriFactu mode (voluntary): adds immediate transmission to AEAT and turns records into "verifiable" invoices — each carrying a QR code that the recipient can scan to confirm registration in the tax authority's systems. In either mode, the software must comply with RRSIF's technical rules.

Who is obligated

The subjective scope is defined in article 3.1 of the RRSIF:

• Corporate Income Tax payers (Impuesto sobre Sociedades, IS): essentially all Spanish limited companies and commercial corporations.
• Personal Income Tax payers with economic activities (IRPF): self-employed, professionals, farmers.
• Non-residents with a permanent establishment in Spain — the category most relevant to foreign groups operating through a Spanish PE.
• Entities under the income-attribution regime: community of property arrangements, civil partnerships with economic activity.

Excluded are those already under mandatory SII (Suministro Inmediato de Información, real-time VAT reporting), certain very specific special regimes, and those who don't issue invoices at all. Practical rule: if you issue invoices through software and aren't already in SII, the RRSIF applies to you.

Current deadlines after the definitive extension

Dates have shifted more than once. The original calendar was modified first by Royal Decree 254/2025, of 1 April (BOE-A-2025-6600), a first extension. The definitive one came via Royal Decree-Law 15/2025, of 2 December (BOE-A-2025-24446), which rewrote the regulation's transitory provision.

The deadlines currently in force:

• SIF producers and distributors: deadline already passed. Order HAC/1177/2024 gave 9 months from entry into force, ending 29 July 2025. From that date on, any SIF sold to Spanish taxpayers must be RRSIF-compliant.
• Corporate Income Tax payers (art. 3.1.a RRSIF): obligated from 1 January 2027.
• Other obligated taxpayers (self-employed under IRPF, non-residents with PE, income-attribution entities): obligated from 1 July 2027.

In practice: if you invoice as a self-employed professional using a commercial product that updates by late 2026, you're probably on track. If you rely on a custom in-house system, a spreadsheet, or a ten-year-old unmaintained program, you have until mid-2027 to migrate — and waiting until Q2 2027 is risky because implementers will be saturated.

Ley Crea y Crece B2B (RD 238/2026): what, who, when

The second regulation comes from a different track. Law 18/2022 of 28 September, on the creation and growth of companies — "Ley Crea y Crece" — introduced in its article 12 the obligation to issue electronic invoices in every operation between companies and professionals. The law is from 2022, but as often happens in Spanish regulation, it delegated technical development to a later regulation that didn't arrive until March 2026.

Royal Decree 238/2026, of 25 March develops that obligation and was published in the BOE on 31 March 2026 (BOE-A-2026-7295). It entered into force on 20 April 2026. Together with the parent law (BOE-A-2022-15818), it defines how Spanish B2B electronic invoicing will operate.

What the regulation requires

RD 238/2026 rests on three pillars:

1. Mandatory format: Facturae (the Spanish standard) or formats interoperable with it (UBL, CII). Invoices must be structured and electronically signed.
2. Exchange channel: the law contemplates two complementary paths. A public exchange service operated by the AEAT (an evolution of FACe, today used for invoicing the public administration), and accredited private platforms that must, in every case, replicate each invoice into the public service — so the state retains visibility regardless of which platform businesses use. This model is closer to France's Chorus Pro + Partner Dematerialisation Platform architecture than to Italy's single-hub SdI.
3. Status communication: the recipient must notify the issuer, through the same channel, of invoice status (accepted, rejected, partially paid, fully paid). That status register feeds official late-payment statistics and eventually underpins enforcement of Spanish payment-terms law.

Who is obligated

All operations between businesses and professionals established in Spanish territory. Operations with end consumers (B2C) are excluded — receipts or simplified invoices still apply — as are certain edge cases (rectifying invoices for pre-regime operations).

If your customers are end consumers, Ley Crea y Crece doesn't obligate you on the issuing side — though VeriFactu still will, from the SIF angle. If you sell B2B, you're in scope. Non-Spanish companies selling into Spain should note: the rule applies to operations where both parties are established in Spain. Cross-border intra-EU B2B is not directly in scope, but VAT treatment and recipient requirements may still demand structured invoicing from you.

Projected deadlines (subject to Ministerial Order)

Caution is warranted. RD 238/2026 states the definitive deadlines will be counted from the publication of the Ministerial Order developing technical aspects (exact message format, accreditation rules for private platforms, status schema). That Order has not been published yet as of April 2026.

The projected calendar — subject to shift:

• 12 months after the Ministerial Order: obligation for companies with annual turnover above €8 million. Projection: approximately July 2027 if the Order is published mid-2026.
• 24 months after the Ministerial Order: obligation for everyone else. Projection: approximately July 2028.

Waiting for the official date before starting means little runway. SMEs already adapting for VeriFactu can cover the Facturae XML layer and B2B signing in the same project at marginal incremental cost. If you use Odoo, our practice for electronic invoicing helps you implement a compatible SIF without redoing your ERP.

What happens if you don't comply: penalties by regulation

One of the areas where misinformation circulates most freely is the sanctions regime. English-language summaries often read "fines of up to €150,000", implying any SME slipping into non-compliance is staring down that number. That conflates three separate things.

The regime varies depending on which obligation you breach. There are three distinct legal contexts, with different subjects and very different amounts:

1. Non-compliant SIF producers and distributors: article 201 bis of the General Tax Law (LGT). Proportional fine, cap up to €150,000 per system per financial year. This article does not apply to the business using the software — it applies to the party that manufactures or sells it. Buy a non-compliant program and the vendor gets fined; you don't get fined €150,000 for using it (though other consequences apply).
2. Obstruction of tax-audit activities: LGT article 203, variable amounts depending on severity. Predates VeriFactu and is invoked when a taxpayer refuses to hand over records, destroys files, or impedes an inspection.
3. Failure to issue an electronic invoice in B2B when required: article 2 bis.9 of Law 56/2007 on the Information Society — modified to absorb Ley Crea y Crece's sanctions. The fine is up to €10,000, not €150,000.

Mixing the three produces impressive headlines, but for real SME risk assessment what matters is knowing which one applies to you.

For the average SME, the real exposure sits in the third row: up to €10,000 for not issuing an electronic invoice when obligated. It's a number that concentrates the mind, but it's not the €150,000 apocalypse sometimes implied.

Five steps to prepare your business

The regulatory side is intimidating; the operational side, approached methodically, is manageable. A reasonable preparation project breaks into five steps:

One: audit your current system. Before buying anything, know where you stand. Which software today? How many invoices issued and received per month? What share of customers are B2B vs end consumers? Do you have a valid digital certificate, and who holds it? Most SMEs can't answer without reviewing a quarter of data — and that exercise is already half the project. For international groups, this is also where you decide whether the Spanish entity runs the group ERP or diverges onto a local stack.

Two: choose certified software. Pick a SIF compatible with both VeriFactu and Facturae. Not every product will qualify: some older packages have no upgrade roadmap; others haven't shipped the compliant version yet. We work primarily with Odoo 18, whose Spanish localization (l10n_es) implements Facturae and, from 18.1+, adds VeriFactu support. Holded, Sage, Contasol and FacturaDirecta are in motion or compatible.

Three: configure the integration. Compliant software isn't enough without proper configuration. Activate electronic signing with the company's digital certificate, define sequential invoice numbering, connect to AEAT's SII or to FACe for public-administration invoicing, and — once the Ministerial Order is published — to whatever B2B channel it defines. Each step involves configuration hours and non-trivial decisions.

Four: onboard your suppliers. Issuing is half the picture; you also receive. Once the B2B obligation kicks in, suppliers will send Facturae instead of PDFs. Configure an inbound channel in your ERP, parse incoming XML, auto-create draft vendor bills, and communicate status back. While the ecosystem migrates, residual PDFs run through an OCR + AI pipeline so you don't lose the automation gains.

Five: monitor and scale. Keep a dashboard showing real-time status of every invoice issued and received, which are accepted or rejected by AEAT, and which are paid. Run a quarterly regulatory review: changes in the Ministerial Order, new SII obligations, ERP localization updates. Compliance isn't a one-off project; it's a layer you maintain.

Certified VeriFactu software: what "certified" means

A recurring question: "is my program certified?" The word causes confusion because the AEAT does not issue an official per-product seal. What exists is a declaración responsable — a formal self-declaration by the SIF manufacturer — stating that the product complies with RRSIF requirements. Plus a factual check: the software must actually produce records with the hashes, signatures and structures the regulation demands.

When people say "VeriFactu-certified software", they mean products whose vendor has formally declared compliance and published supporting technical documentation. The AEAT maintains official information on its page for invoicing software systems.

Representative categories — examples, not recommendations — with compatibility status as of April 2026:

• Odoo: open-source ERP with substantial Spanish presence. The l10n_es localization is rolling out VeriFactu support. Flexible for custom integrations, large community.
• Holded: SaaS for freelancers and small SMEs. Announced compatibility; good fit for simpler operations.
• Sage: several product lines (Sage 50c, 200) with their own schedules. Recent versions include support; older ones require upgrade.
• Contasol / Factusol: traditional Spanish SME software. Sage Spain announced compatibility in latest major versions.
• FacturaDirecta: small SaaS for freelancers and micro-companies, compatibility built in.

There is no universally "best" option. Choice depends on invoicing volume, business complexity, whether you already run an ERP, and integration needs. What matters is a public compatibility roadmap and ideally a shipping version in 2026.

For international groups: Spain's SIF framework is country-specific. If your group ERP is SAP, NetSuite, Microsoft Dynamics or Oracle, you'll need either a certified Spanish localization module from the vendor, a third-party connector, or an adjacent Spanish system feeding AEAT while the main ERP remains the book of record.

The real value: automating the full flow

Here's the part rarely written about and, for us, the most interesting. The default mindset — "we have to comply with VeriFactu" — treats the regulation as a burden: do the minimum, certify, keep operating as before. Understandable, and a missed opportunity.

If you're going to touch your invoicing software anyway — and you are — the marginal cost of automating the entire flow (not just the slice the law requires) is far smaller than doing it later as a separate project:

• Automatic capture of vendor invoices. Suppliers still sending PDFs — especially small freelancers — run through an OCR + AI pipeline that extracts issuer, tax base, VAT, total and line items, creates the draft vendor bill in the ERP, and leaves it ready for validation. Five minutes becomes five seconds.
• Automatic bank reconciliation. Once every invoice has a recorded status, crossing a bank statement against open invoices stops being manual. A recurring job matches payments to invoices by reference, amount and date, and escalates only when there's no clear match.
• AI agents for follow-up. Invoices accepted but unpaid for 30 days trigger a reminder; rejected invoices open a task for the sales rep; invoices with VAT discrepancies are stopped before being recorded incorrectly into SII.
• Real-time compliance dashboard. How many B2B invoices issued this month, how many paid, which customers systematically pay late. Information that used to require manual spreadsheet work.

The outcome isn't just compliance: your invoicing flow moves from administrative dead weight to a layer that runs itself, with human attention reserved for genuine exceptions.

This is the kind of work we do. Our team automates supplier invoices with OCR + AI as part of the full flow, and our methodology walks through how we do it in 30 to 60 days, without halting operations. The regulatory obligation is the trigger; automation is the real return.

Frequently asked questions

Sources and BOE references

• RD 1007/2023 (BOE-A-2023-24840) — SIF Regulation
• RD 254/2025 (BOE-A-2025-6600) — First extension
• RDL 15/2025 (BOE-A-2025-24446) — Definitive SIF extension
• RD 238/2026 (BOE-A-2026-7295) — B2B e-invoicing regulation
• Law 18/2022 Crea y Crece — Law on business creation and growth
• LGT (Law 58/2003) — art. 201 bis, 203
• Law 56/2007 on Information Society — art. 2 bis.9
• AEAT — VeriFactu Invoicing Systems

Conclusion

Electronic invoicing in Spain is no longer optional — under VeriFactu or Ley Crea y Crece. Dates may shift, but the direction is clear: automation, traceability, real-time reporting. Prepare now, reach the deadlines with margin; wait for the Ministerial Order and you'll be running.

If you want help implementing a compatible flow without redoing your ERP: here's how we prepare SMEs for VeriFactu and Ley Crea y Crece. Or directly, start a conversation.