SII (Immediate Supply of Information): what it is and who must use it
The SII (Suministro Inmediato de Información, Immediate Supply of Information) is the Spanish Tax Agency (AEAT) system through which the businesses it applies to send their VAT record books electronically within four days. It has been in force since 1 July 2017 and is mandatory for businesses with a turnover above €6,010,121.04, businesses in the REDEME, members of a VAT group and holders of a fuel tax warehouse; any other business can join voluntarily.
Since when the SII is mandatory
| Who | Date | Status | Rule |
|---|---|---|---|
| SII: large companies (over €6M), REDEME and VAT groups Since 1 January 2025, also holders of hydrocarbon tax warehouses (RIVA, art. 71.3). | Since 1 Jul 2017 | In force | RD 596/2016 |
| Voluntary SII: any VAT taxpayer Opting out is filed in November. | At any time | In force | Art. 68 bis RIVA |
| B2B e-invoicing: turnover over €8M | 6 Oct 2027 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
| B2B e-invoicing: all other businesses and professionals Invoice statuses optional until 6 October 2029 for individuals and pass-through entities up to €8M. | 6 Oct 2028 | Published in the BOE, future date | RD 238/2026 · Orden HAC/1028/2026 |
This is not advice: each taxpayer determines what applies to them with their adviser.
What the SII is and how it works
With the SII, the VAT record books are kept in the AEAT’s electronic office: the business sends the record of each invoice almost in real time, instead of keeping the books itself. In return, the AEAT receives VAT information continuously rather than at the end of each period, and businesses in the SII no longer file forms 347 and 390 (AEAT SII FAQ).
What is sent
Four record books, described in SII record books:
- Issued invoices book.
- Received invoices book.
- Capital goods book.
- Book of certain intra-community operations.
How it is sent
Through the AEAT’s web services (XML/SOAP) or, where applicable, an electronic form in the electronic office, under art. 62.6 of the VAT Regulation. Each record carries its regime and invoice type codes: SII codes.
Who must use the SII
| Who | Criterion | Rule |
|---|---|---|
| Large companies | Turnover above €6,010,121.04 in the previous year. | Art. 62.6 RIVA |
| Businesses in the REDEME | Monthly VAT refund register, whatever their size. | Art. 62.6 RIVA |
| VAT groups (REGE) | Members of a VAT group. | Art. 62.6 RIVA |
| Fuel tax warehouses | Holders of tax warehouses for petrol, diesel or biofuels and those who take those products out of them, since 1 January 2025. | Arts. 62.6 and 71.3 RIVA |
| Voluntary | Any other VAT taxpayer can opt in at any time of the year; opting out is filed in November. | Art. 68 bis RIVA |
It is decided by the previous year’s turnover, as defined in the VAT rules.
This is not advice: each taxpayer determines what applies to them with their adviser.
The SII, topic by topic
SII requirements
- Submission through the AEAT’s electronic office, with the electronic certificate of the taxpayer or of whoever acts on their behalf.
- Record format: the fields approved by order of the Ministry of Finance, with their codes (SII codes).
- Deadlines: four days per record, with specific rules for each book (SII deadlines).
SII penalties
Late keeping of the record books through the AEAT’s electronic office is a serious infringement under art. 200 of the General Tax Law.
| Infringement | Penalty | Rule |
|---|---|---|
| Late submission of invoicing records | A fine of 0.5% of the amount of the invoice in the record, with a quarterly minimum of €300 and a maximum of €6,000. | Art. 200.1.g and 200.3 LGT |
SII regulations
| Rule | What it regulates | Date |
|---|---|---|
| RD 596/2016 | Amends the VAT Regulation to introduce the SII. | In force since 1 July 2017 |
| Art. 62.6 RIVA | Who keeps the record books through the electronic office and how they are sent (web service or form). | In force |
| Art. 68 bis RIVA | Voluntary opt-in to the SII and opt-out. | In force |
| Art. 69 bis RIVA | Deadlines for sending invoicing records. | In force |
The SII in the foral territories
Álava, Bizkaia, Gipuzkoa and Navarre have their own foral SII, with criteria equivalent to the AEAT’s. Each business submits to the SII of the treasury that applies to it. Since 2026, businesses with their tax domicile in the Basque Country or Navarre, a turnover above €12M and at least 75% of it in common territory apply the SII under state rules (until 2025, the threshold was €10M; AEAT SII FAQ, 1.21).
- Álava: the foral SII of the Álava Provincial Council.
- Bizkaia: the Bizkaia LROE of Batuz includes the SII information and obligations.
- Gipuzkoa: Gipuzkoa foral SII.
- Navarre: the foral SII of the Navarre Foral Treasury. More about Navarre in NaTicket.
The Verifacti SII API submits to the AEAT’s SII; it does not cover the foral SII.
AEAT forms vs an API
The AEAT lets you submit records through an electronic form in its electronic office, as well as through its web services. If the volume is high or your software generates the invoices, the difference is the integration.
| AEAT web form | Verifacti SII API | |
|---|---|---|
| Who it is for | Whoever enters their invoices by hand in the electronic office. | Companies with in-house software and software vendors (ERP, SaaS). |
| Connection to your software | No: it is filled in on the electronic office. | Yes: your software sends each invoice as JSON. |
| Volume and several NIFs | One record at a time. | In batches, and several NIFs with the NIF management API. |
| Validation before sending | The AEAT validates on receipt. | Yes, before submitting to the AEAT. |
| Automatic submission | No. | Yes, with the AEAT response by webhook. |
| Cost | Free. | Custom pricing; free test environment. |
Send your SII through an API
Take your SII to a provider specialised in Spain, the same one that will cover your e-invoicing. The SII API is a JSON REST API instead of the AEAT’s SOAP: it sends your issued invoices record book, validates each invoice before submitting it and returns the AEAT’s response by webhook.
The E-invoicing API is coming soon, on the same NIF management.
Proven reliability
Hundreds of companies and software vendors in production with Verifacti. Data hosted in the EU and an SLA in the terms of use.
AEAT social collaboratorSpecialists in Spain
Common and foral territory: Verifactu, TicketBAI and SII with one provider.
TicketBAI guarantor software in Álava, Bizkaia and GipuzkoaBuilt for developers
Public documentation with examples for every call, quick start guide, Postman collections, llms.txt and a free account with a test environment.
Typical integration: one to three developer daysSII, Verifactu, TicketBAI and e-invoicing
| Rule | Relation to the SII |
|---|---|
| Verifactu | Whoever is in the SII is outside Verifactu while they remain in it. SII and Verifactu. |
| TicketBAI | Being in the SII does not exempt you from TicketBAI in Álava, Bizkaia and Gipuzkoa. |
| B2B e-invoicing | It comes on top of the SII: 6 October 2027 for turnover above €8M and 6 October 2028 for everyone else, including the €6M to €8M band (dates published in the BOE). B2B e-invoicing. |
Frequently asked questions about the SII
Which businesses must use the SII?
Can I join the SII voluntarily? And leave?
How are the REDEME and the SII related?
What is the deadline to send invoices to the SII?
What happens with e-invoicing if I am in the SII?
If I am in the SII, do I have to comply with Verifactu?
How is an SII submission validated?
Try the SII API in the test environment
Send an issued invoice as JSON to the AEAT test environment with the free account.