Spain · Verifactu · SII · Facturae
Spain E-Invoicing & Verifactu Integration
Make your existing billing software compliant in Spain: Verifactu invoice records and QR codes, SII reporting, FACe public-sector invoices and structured B2B e-invoices, without replacing your ERP.
Who must comply with Spain e-invoicing?
- Verifactu: businesses and self-employed people using invoicing software, other than those in SII or under Basque/Navarre regional regimes.
- SII: large companies (by turnover), VAT groups and those registered for monthly VAT refunds, plus voluntary registrants.
- TicketBAI / Batuz: businesses under Basque provincial tax jurisdiction.
- FACe: suppliers invoicing Spanish public administrations.
- B2B e-invoicing (Crea y Crece): businesses and professionals invoicing each other, phased by company size once in force.
Timelines have changed more than once. Use the AEAT website for the current dates.
How do Verifactu, SII and Spanish e-invoicing fit together?
Spain's approach has layers. Verifactu and SII are about recording and reporting invoice data to the tax agency: Verifactu through certified-behaviour billing software (with optional real-time submission), SII through near-real-time reporting for larger companies. On top of that, B2B e-invoicing requires invoices exchanged between businesses to be structured electronic documents, with payment-status information. FACe handles invoices to the public sector.
- Definition: Verifactu
- Spain's requirements for invoicing software (RD 1007/2023): each invoice creates a signed, hash-chained record and a QR code, and records can be sent to the AEAT in real time.
What are the technical requirements in Spain?
- Invoice records (registro de facturación) with hash chaining, electronic signature and event logs.
- QR code on every invoice, linking to AEAT verification, with the "VERI*FACTU" mention where records are sent in real time.
- SII XML submissions via AEAT web services for in-scope companies.
- Facturae XML (signed) for B2G through FACe.
- Structured B2B formats permitted by the B2B regulation, such as Facturae, UBL, CII or EDIFACT.
How does Co-Mate make your ERP compliant in Spain?
We add a compliance layer beside your ERP or POS. It creates the signed, chained invoice records and QR codes, submits them to AEAT or SII as required, generates Facturae or other structured invoices, and writes status back to the ERP. One platform can also produce French, German and Peppol outputs for multi-country groups.
Which ERPs and billing systems do we support for Spain?
- SAP Business One
- Microsoft Dynamics 365
- Oracle NetSuite
- Sage
- Odoo
- A3 / other local ERPs (via API/exports)
- Custom PHP / .NET / Java
- POS systems
Don't see yours? If it stores invoices in a database or exposes an API, export or webhook, we can connect it. See all ERP e-invoicing integrations.
Implementation steps
A predictable path from first call to live, monitored e-invoicing.
- 1
Regime check
Identify which Spanish regimes apply to each entity: Verifactu or SII, TicketBAI or Batuz in the Basque Country, FACe for public customers, and the B2B e-invoicing mandate.
- 2
Software gap analysis
Check whether your billing software already creates hash-chained, signed invoice records with QR codes, or needs a compliance layer.
- 3
Compliance layer build
Build invoice record generation, chaining, signatures, QR codes and submission to AEAT (Verifactu mode) or SII, as applicable.
- 4
B2B e-invoice output
Prepare structured B2B e-invoice output (Facturae, UBL or other permitted formats) and exchange as the mandate requires.
- 5
Testing
Test against AEAT test environments and with real scenarios: rectifying invoices, simplified invoices, cancellations.
- 6
Go-live & support
Phased switch-on with monitoring and updates as regulations and technical specifications change.
Common Spain e-invoicing challenges and how we handle them
| Challenge | Why it matters | How we handle it |
|---|---|---|
| Several overlapping regimes | Verifactu, SII, TicketBAI, FACe and B2B e-invoicing apply to different entities and flows. | Regime map per entity and one integration layer with separate modules. |
| Tamper-evident records | Invoice records must be chained and signed, and cannot be altered. | Sequencing service with hash chaining and secure key storage. |
| POS and simplified invoices | High volumes from many terminals. | Per-terminal records, offline queues and batch submission. |
| Changing timelines | Dates have been adjusted by the government. | Build early, switch on per official schedule, keep rules configurable. |
Spain e-invoicing FAQ
What is Verifactu?
Is B2B e-invoicing mandatory in Spain?
What is SII?
What is FACe and Facturae?
What about TicketBAI in the Basque Country?
Can our existing ERP comply in Spain?
Official sources
Last reviewed:
- Agencia Tributaria (AEAT): Verifactu and SII
- FACe: public-sector e-invoicing entry point
- European Commission: eInvoicing and EN 16931
E-invoicing rules, timelines and technical specifications change often. This page summarises the official guidance as we understood it on the review date. Always confirm obligations and dates with the tax authority or your tax adviser before acting. Co-Mate provides integration engineering, not tax or legal advice.
Related e-invoicing guides
- E-invoicing integration hubAll countries, models and our approach in one place.
- ERP e-invoicing integrationsSAP Business One, Dynamics, NetSuite, Odoo, Zoho, Tally and more.
- France e-invoicingCertified platforms, Factur-X and e-reporting.
- Germany e-invoicingXRechnung and ZUGFeRD.
- Integrate e-invoicing with your existing ERPConnector architecture for multi-country rules.