← Back to global tracker
🇪🇸

Country deep dive

Spain

Europe · ES · VAT area: EU
Last updated: 21 July 2026
Compliance model: Dual-track — VeriFactu + Crea y Crece
🧩 Spain runs two separate, complementary reforms that are easy to conflate: VeriFactu secures the invoicing software itself (confirmed dates, Jan/Jul 2027), while Crea y Crece mandates structured B2B invoice exchange (framework law passed, but the implementing ministerial order — and therefore the exact start dates — remains pending as of mid-2026).
RRSIF
VeriFactu technical standard
Jan/Jul 2027
VeriFactu deadlines
Pending
Crea y Crece ministerial order
Up to 75%
Fraud penalty (% of transaction)
2015
B2G (FACe) mandatory since
01

Compliance timeline

Three distinct regimes — B2G, SII, and now VeriFactu — have accumulated over a decade. Crea y Crece's B2B mandate is the newest piece, and the one still missing its implementing detail.

2015
2015In effect
B2G e-invoicing mandatory (Ley 25/2013)

Invoices to Spanish public bodies must be submitted in Facturae XML format via the FACe platform — a paper invoice or simple PDF is not valid and won't be processed.

2017
2017In effect
SII introduced

Large taxpayers and monthly filers must send sales and purchase ledgers to AEAT within 4 days, replacing quarterly block reporting with near-real-time visibility. Businesses in SII are outside VeriFactu's scope.

2022
2022In effect
Crea y Crece Law enacted (Ley 18/2022)

Establishes the legal framework mandating structured B2B e-invoicing — but as a framework law, leaving the technical detail and exact start dates to a future implementing ministerial order.

December 2023
5 Dec 2023In effect
Royal Decree 1007/2023 — RRSIF published

Sets out the technical requirements for invoicing systems (Reglamento de requisitos de los sistemas informáticos de facturación) underpinning VeriFactu: chained cryptographic hashes, secure timestamps, and electronic signatures to prevent undetected record alteration.

January 2027
1 Jan 2027Due soon
VeriFactu mandatory for corporate taxpayers

Businesses subject to Corporate Income Tax (IS) must use VeriFactu-certified invoicing software.

July 2027
1 Jul 2027Upcoming
VeriFactu mandatory for all other taxpayers

Self-employed workers (autónomos) and remaining taxpayers using invoicing software must comply — this is the date most sources treat as VeriFactu's true universal deadline.

Pending
Ministerial order — not yet publishedUpcoming
Crea y Crece B2B mandate activates

Once the implementing order is published, businesses with turnover above €8 million must comply within 1 year, and all other businesses and autónomos within 2 years. A public consultation on the order completed in 2026, but as of mid-2026 it remained pending.

02

File format & data specification

The single most important thing to understand about Spain: VeriFactu is not an invoice format at all — it's a requirement on the software that produces your invoices.

VeriFactu (RRSIF) — a software requirement, not a format

What it governsThe invoicing system (SIF), not the invoice's file format
Core mechanismsHash-chained records, digital signature, secure timestamp
Visible markerQR code + legend "VERI*FACTU" or equivalent

A VeriFactu-compliant invoice can still be a plain PDF in appearance — what matters is the underlying record's integrity, not its visual format.

B2G format (already mandatory)

FormatFacturae 3.2.1 or 3.2.2
SignatureQualified certificate required
DeliveryVia FACe (or FACeB2B for procurement chains)

This has applied for over a decade and isn't changing — treat it as the stable baseline while VeriFactu and Crea y Crece both continue to develop.

B2B format (Crea y Crece, pending)

Expected formatsFacturae and/or UBL-compatible standards
Confirmed requirementEN 16931 content validation
StatusFinal format not locked until the ministerial order publishes

Don't build a specific B2B schema assumption into production systems yet — Facturae and UBL are both plausible, and the order will settle it.

Software declaration (SIF)

RequirementDeclaración responsable filed with AEAT
Filed byThe software developer, not the end-user business
Must be visibleIn the system itself, per version, from time of purchase

If you're a business rather than a software vendor, your job is confirming your provider has filed this declaration — not filing it yourself.

03

Transmission protocol

Spain runs three parallel systems that don't all talk to each other the same way — knowing which one applies to you matters as much as the technical detail.

SII vs. VeriFactu

SII scopeLarge taxpayers, monthly filers
SII cadenceLedger reporting within 4 days
VeriFactu scopeEveryone else using invoicing software

These are mutually exclusive — if you're in SII, you are explicitly out of VeriFactu's scope. Don't build for both.

VeriFactu's two modes

Mode AReal-time transmission to AEAT
Mode BLocal storage under strict hash-chain/audit requirements

Both modes satisfy the legal requirement — the choice is about your operational preference for live reporting versus retained, tamper-evident local records.

Crea y Crece network (pending detail)

Public optionState platform, receiving a "copia fiel" (faithful copy)
Private optionConnected private operators
StatusFull network model still to be finalised by the ministerial order

The B2B e-invoice network does not send invoice content to AEAT the way VeriFactu can — it's a separate exchange-and-status-tracking layer between trading partners.

AEAT's audit powers

AccessFull, immediate access to SIF data on request
On-site powersCan appear where the system is located/used
Actions availableDownload, dump, consult, or copy data directly

This is a materially stronger inspection power than most EU e-invoicing regimes grant — plan your system architecture assuming AEAT can and will exercise it.

04

Getting ready

Because two reforms are running on different tracks, your readiness checklist genuinely splits in two.

Determine your regime: SII or VeriFactu

Check whether you're a large taxpayer or monthly filer already in SII — if so, VeriFactu doesn't apply to you at all.

Confirm your software vendor's AEAT declaration

Ask your invoicing software provider to confirm they've filed the declaración responsable for your specific version — this is their obligation, not yours, but you need the assurance.

Choose your VeriFactu mode ahead of your deadline

Corporate taxpayers: decide real-time AEAT transmission vs. local hash-chained storage before 1 January 2027. Autónomos and others: the same decision applies before 1 July 2027.

Keep your B2G channel current

If you already invoice public bodies, confirm Facturae 3.2.1/3.2.2 generation and FACe submission remain in good working order — this obligation isn't changing.

Watch for the Crea y Crece ministerial order

Once published, your compliance clock starts immediately — 1 year if you're above €8 million turnover, 2 years otherwise. Don't wait until publication to start evaluating platforms.

Set up dual-track archiving

Plan for 4-year tax retention and 6-year commercial retention separately, and notify AEAT if any records are hosted abroad.

05

Penalties & enforcement

Spain's penalty structure scales with the severity of the underlying issue — a formatting slip and outright fraud sit at opposite ends of a very wide range.

Agencia Tributaria — VeriFactu