All countries

E-Invoicing in Spain

B2G MandatoryPeppol
Verified: 20 December 2025

Spain runs a dual system: B2G e-invoicing via FACe in Facturae format, and SII real-time tax reporting for large taxpayers (>€6M). VeriFactu, a new invoice integrity system, becomes mandatory in 2027. The B2B e-invoicing mandate under the Crea y Crece law is still pending final ministerial order — don't build for a date that hasn't been set yet.

Mandate Status

PhaseStatusScope
B2GLive (Jan 2015)All public administration suppliers
SII reportingLive (Jul 2017)Companies >€6M revenue
VeriFactuJan 2027 / Jul 2027Corporations Jan 2027, all others Jul 2027
B2B e-invoicingPending regulationTimeline TBD — awaiting ministerial order

Technical Specifications

Validation engineFACe (B2G), SII (reporting), AEAT (VeriFactu)
Required CIUSFacturae 3.2.x (Spanish national format)
Government portalFACe (face.gob.es)
Routing identifierAdministrative codes (OC, OG, UT) for B2G routing
PeppolYes — Peppol accepted alongside Facturae for B2G
Accepted formatsFacturae 3.2.x

Implementation Notes

Spain's system is layered: existing B2G, live SII reporting, imminent VeriFactu, and a future B2B mandate. Each layer has distinct technical requirements.

SII real-time reporting. Companies over €6M revenue must report invoice data to AEAT within 4 days via the SII API. This is not e-invoicing — it's reporting of invoice metadata. But if your pipeline handles Spanish customers, you likely need SII integration regardless of the B2B mandate timeline.

VeriFactu (2027). VeriFactu adds integrity and traceability requirements to all invoicing software. Every invoice gets a hash chain linking it to the previous invoice, preventing retroactive tampering. Your ERP integration must support sequential hash generation. Corporations comply January 2027, all others July 2027.

B2G via FACe. Facturae 3.2.x is the required format with mandatory digital signature (XAdES). FACe uses administrative codes (OC, OG, UT) for routing — these are specific to each public entity and must be looked up per-recipient. Incorrect codes cause rejection with unhelpful error messages.

Common Rejection Patterns

#CodeDescription
1ES-R-003FACe routing codes requiredFix guide
2ES-R-004Digital signature requiredFix guide
3BR-ES-01Spanish NIF/CIF requiredFix guide
4ES-R-005SII reporting referenceFix guide
5ES-R-002Invalid FacturaE formatFix guide

Invoice Navigator auto-remediates these at pipeline speed. See how →

View all Spain error codes

Ship compliant Spain invoices

Validate, fix, and route Spain e-invoices through a single API. No XML editing required.

Get API Access