FlowieExchange
Compliance · 🇪🇸 Spain Phased rollout

Spain — Veri*Factu, Crea y Crece, FACe

Veri*Factu reporting · Crea y Crece B2B mandate · FACe B2G — regulator: Agencia Estatal de Administración Tributaria (AEAT). Facts last refreshed: 2026-05-05.

Coverage model
Flowie operates a registered Peppol Access Point in this jurisdiction directly where we hold national accreditation, or via a vetted local partner registered with the in-country regulator where on-the-ground presence is required (KSeF, SDI intermediario, ZATCA service-provider, etc.). Either way, you call the same POST /v1/documents/send.

TL;DR

Deadlines

DateWhoWhat
2015-01-15Public-sector contracting (B2G)FACe mandatory.
2025-07-01Corporate billing softwareVeri*Factu obligation begins.
2026-07-01Self-employedVeri*Factu obligation extended.
≥ 2026-Q4Large taxpayers (Crea y Crece)B2B e-invoicing mandate (date pending royal decree).
≥ 2028All taxpayers (Crea y Crece)Universal B2B mandate.

Background

Spain runs three parallel regimes that often confuse newcomers:

Veri*Factu is about billing-software certification: any software used to issue Spanish invoices must hash and chain them, and may (or, where ordered, must) transmit to AEAT in real-time. Already live for corporate.

Crea y Crece is the upcoming B2B e-invoicing mandate proper — invoices in structured format between businesses. Phased rollout dates are still subject to the implementing royal decree but tracking 2026–2028.

FACe is the long-running B2G hub. Suppliers to Spanish public buyers send Facturae XML through FACe; Flowie does this transparently.

Format profile

Required fields

Public sector (B2G)

HubPeppol identifier schemeLookup
FACe (Punto General de Entrada de Facturas Electrónicas)0009:ES-FACE-<codes>https://face.gob.es

FACe accepts Facturae 3.2.x; Flowie renders it from the same JSON payload. The three administrative codes (DIR3) must be set on buyerReference.

B2B reporting / clearance

Veri*Factu (AEAT) — Hash-chain certification + optional real-time transmission of invoice headers.

Lifecycle statusReported as
issuedHash recorded; if real-time mode, transmitted to AEAT.
cancelledCancellation event in the chain.

Opt-out: settings.autoCompliance.ES.veriFactu = "hash-only" (no real-time transmission)

Error codes

CodeMeaningFix
VERI-CHAIN-101Veri*Factu hash chain broken.Don't manually edit the chain. Flowie maintains it; if you detect divergence, call /v1/compliance/es/veri-factu/repair.
FACE-DIR3-MISSDIR3 administrative codes missing.Set the three codes on buyerReference; format OC|OG|UT.
ESCIUS-S-007Facturae profile validation failed.Inspect error.details.

Testing in sandbox

What you want to testHow
FACe B2GRecipient 0009:ES-FACE-A12345678|B12345678|C12345678.
Veri*Factu hash-onlySet verifactu.mode: "hash-only"; chain returned, no AEAT transmission.
Force Crea y Crece rejectionsimulateCompliance: "reject_CREAYCRECE_001".

FAQ

Is Veri*Factu the same as Crea y Crece?

No. Veri*Factu is about billing-software certification (already live for corporate); Crea y Crece is a future B2B e-invoicing mandate (phasing from 2026). They overlap but are separate obligations.

Do I still need to register with FACe?

Only if you upload invoices manually. When sending via Flowie's AP, FACe is the recipient and we route there transparently.

References

Primary sources (government / regulator / standards body):

Industry analyses (vendor trackers — useful for cross-referencing):