Spain SII: Complete Guide to Real-Time VAT Reporting

Spain's SII (Suministro Inmediato de Información, or Immediate Supply of Information) is a real-time VAT reporting system, not a traditional e-invoicing mandate. Businesses in scope must submit invoice data electronically to Spain's tax authority, the AEAT, within four calendar days of each transaction. SII has been mandatory for large Spanish taxpayers since July 2017 and applies to both resident and non-resident businesses that meet certain criteria.

Many finance teams conflate SII with two related but distinct systems: VeriFactu and the upcoming Crea y Crece B2B electronic invoicing mandate. This guide explains how all three differ, who must comply with SII, what gets submitted, how the process works in practice, and what penalties apply when businesses fall short.

What is Spain's SII (Suministro Inmediato de Información)?

Spain's SII is a real-time VAT reporting regime. It was launched on July 1, 2017, under Royal Decree 596/2016 and is managed by the AEAT (Agencia Estatal de Administración Tributaria), the Spanish tax agency. Rather than filing periodic VAT ledger summaries, businesses subject to SII must submit detailed invoice data electronically in XML format within a short window after each transaction.

SII replaces traditional periodic VAT ledger reporting obligations. Specifically, businesses enrolled in SII no longer need to file Form 340 (quarterly record books), Form 347 (annual third-party transaction report), or Form 390 (annual VAT summary return).

How SII differs from traditional VAT reporting

Under traditional VAT reporting, businesses file periodic returns summarizing their VAT activity. The reporting takes place weeks or months after the underlying transactions occur.

SII flips that process. Instead of a summary filed after the period ends, businesses submit invoice-level data within four calendar days of each transaction. This means the AEAT has a near-live view of a business's VAT activity, which it can cross-check against other taxpayers' records in close to real time.

That shift has real operational implications. This means data errors surface faster. Mismatches between submitted records and VAT returns get flagged quickly. And businesses lose the luxury of reconciling everything at period end. Books must be accurate in real-time.

SII vs. Verifactu vs. Crea y Crece: understanding Spain's three e-reporting systems

Spain has three overlapping digital tax systems, and understanding which one applies to your business matters a great deal.

1. SII is a real-time VAT book-keeping system for large taxpayers. Businesses submit invoice data directly to the AEAT in XML format within four calendar days of each transaction.
2. VeriFactu is a certified billing software requirement. From January 1, 2027, businesses that are not subject to SII must use invoicing software that meets specific technical standards under Royal Decree 1007/2023. This software must generate tamper-proof invoice records with digital fingerprints and QR codes that allow recipients to verify the invoice with the AEAT. Crucially, businesses already using SII (mandatory or voluntary) are exempt from Verifactu.
3. Crea y Crece (Law 18/2022) is Spain's upcoming structured B2B e-invoicing mandate. It requires businesses to exchange invoices with other businesses in a structured electronic format. It is expected to roll out in two phases with large companies (turnover of €8 million or above) starting from 2027, and all other businesses and freelancers starting from 2028.

Here is a summary of how the three systems compare:

‍

Long story short, SII and Verifactu are not the same system. If your business is already in SII, you do not need to comply with Verifactu. Crea y Crece is a separate layer that will eventually require a structured invoice exchange between trading partners, building on top of these existing systems.

Who must comply with Spain's SII?

SII is mandatory for specific categories of taxpayers. All others can opt in voluntarily.

Large companies exceeding €6 million turnover

The main threshold for mandatory SII is an annual volume of operations (turnover) in Spain exceeding €6,010,121.04 in the prior calendar year. This applies to both resident and non-resident businesses that have a Spanish VAT registration. The rule is industry-agnostic: manufacturers, retailers, service businesses, software companies, and any other type of enterprise all fall under the same threshold.

Note that outgoing invoices (sales, exports, intra-community supplies) count toward the threshold calculation. Incoming purchase invoices are excluded from the threshold count.

VAT groups and REDEME members

Two other categories are mandatory regardless of turnover. All entities that belong to a Spanish VAT group must comply with SII. The same applies to all businesses enrolled in REDEME, Spain's Monthly VAT Refund Registry.

From January 1, 2025, a new group was added to the mandatory scope: holders of gas tax deposits and companies involved in the extraction of hydrocarbon products from tax deposits.

Voluntary enrollment for other businesses

Any business with a Spanish VAT registration can opt into SII voluntarily, even if their turnover falls below the €6 million threshold. Businesses can enroll voluntarily via Form 036, and file in November of the year before the opt-in takes effect.

Voluntary enrollment comes with benefits. Businesses that opt in get the same benefits as mandatory filers: exemption from Forms 340, 347, and 390, extended VAT return deadlines, and access to pre-populated draft VAT returns from the AEAT.

For businesses with a Spanish VAT registration that are below the €6 million threshold but still file frequently or have complex cross-border transactions, voluntary SII can reduce audit exposure and simplify compliance. Sphere will support SII from Q2 2026, including for businesses that choose voluntary enrollment.

SII submission requirements and deadlines

The 4-business-day reporting window explained

The SII deadline is four calendar days from the date of issue (for issued invoices) or from the accounting record date (for received invoices). Weekends and Spanish national public holidays are excluded from the count.

Example: Say your business issues an invoice on a Tuesday. The four-day clock starts Wednesday. Excluding any weekend days, the submission deadline falls the following Monday (assuming no public holidays take place.) All SII submissions must be completed before the 16th of the month following the reporting period, even if the four-day window would otherwise extend beyond that date.

The four-day window applies to all transaction types: B2B, B2G, B2C, domestic, intra-EU, and cross-border. There is no minimum transaction value that creates an exemption.

Issued invoices (Facturas Expedidas)

Issued invoice records must be submitted within four calendar days of the invoice date. The SII submission covers:

• Domestic sales
• Exports of goods and services
• Intra-community supplies of goods and services

Required data fields for each issued invoice record include: invoice number and series, issuance date, buyer's NIF (tax identification number), taxable base, VAT rate applied, total gross amount, and operation type code.

Received invoices (Facturas Recibidas)

Received invoices work slightly differently. The four-day window starts from the date the invoice is recorded in the business's accounting system or ERP, not the date printed on the invoice. This is important because invoices can sometimes arrive weeks after the underlying transaction.

The received invoices register covers:

• Purchase invoices from domestic suppliers
• Imports of goods and services
• Intra-community acquisitions of goods and services

Investment goods, capital goods, and intra-community transactions

SII covers four registers in total: issued invoices, received invoices, investment goods, and certain intra-community transactions such as:

• transfers of own goods
• consignment goods held in other EU countries
• goods sent temporarily to another EU member state for use or repair

One important distinction is that investment goods are not reported in real time alongside other invoices. Investment goods records are submitted on an annual basis. Finance teams should flag this difference when setting up their SII workflows, as the cadence is very different from the regular four-day cycle.

How Spain's SII works in practice

XML web services via API integration

The preferred method for most businesses with high invoice volumes is direct API integration. Data is submitted as structured XML files conforming to AEAT's technical specifications. This method supports high-volume automated submission without manual intervention and allows for real-time validation from the AEAT.

Sphere's SII support, launching in Q2 2026, uses direct API rails into the AEAT. That means submissions are automated as part of your regular tax workflow rather than handled as a separate manual task.

Manual submission through the AEAT portal

For businesses with low invoice volumes, the AEAT's online portal (Sede Electrónica) supports manual entry and CSV upload. The digital certificate is still required for portal access. This method is practical for a handful of invoices per week, but becomes unwieldy at scale.

Required data fields for each invoice record

The data fields required vary slightly between issued and received invoices. The table below shows the key fields for each:

‍

When a single invoice covers supplies at multiple VAT rates, each rate and its corresponding taxable base must be reported separately.

SII penalties for late or incorrect submissions

Financial Penalties

Late reporting under SII carries a penalty of 0.5% of the missed invoice amounts, with a minimum of €300 and a maximum of €6,000 per quarter. That quarterly ceiling applies across all late submissions within the same quarter, not per invoice.

For wrong or incorrect information that was already submitted, the penalty rises to 1% of the misreported amount, with a minimum of €150 and a maximum of €6,000. 

Errors or omissions in the investment goods register or the intra-community transactions register, carry a fixed penalty of €150.

Complete non-compliance, where a required business submits no SII data at all, can trigger a penalty of 1% of annual turnover.

What triggers SII penalties?

The AEAT applies penalties for several types of non-compliance:

• Missing the four-day submission deadline
• Submitting incomplete or inaccurate data
• Failing to correct the records that the AEAT has flagged as rejected
• Failing to submit any data at all

It’s important to note that a one-day delay can lead to fines, which are calculated quarterly with no reduction based on how late the data was submitted. In other words, being one day late triggers the same percentage penalty as being two weeks late.

Operational risks beyond financial penalties

The financial penalties are one concern, but the operational risks can be equally disruptive. The AEAT compares SII data against VAT return submissions (Form 303). Where the two do not match, VAT deductions can be disallowed. If input VAT reported in your VAT return is not supported by matching SII records, the AEAT can deny that deduction. That is an immediate cash flow hit on top of any fine or penalty.

Delayed or rejected SII submissions can also delay VAT refunds, since refunds are partly processed based on SII data. For businesses that regularly claim VAT refunds in Spain, getting SII right is directly tied to how quickly those refunds arrive.

How to reduce SII penalty risk

The most effective mitigation is automation. Manual data entry introduces errors. Tight deadlines leave no buffer for last-minute corrections. 

A few practical steps significantly reduce penalty exposure:

• Automate the extraction of invoice data from your ERP or billing system directly into SII-compliant XML.
• Build in a pre-submission validation step that checks required fields and format before data reaches the AEAT.
• Monitor submission acknowledgments from the AEAT and have a clear process for correcting rejected records promptly.
• Align your SII data with Form 303 before filing each monthly VAT return to prevent mismatches.

Why small errors can become expensive at scale

Consider a business that issues 500 invoices per month and misses the four-day deadline on 10% of them in a given quarter. That is roughly 150 late records in the quarter. At 0.5% of invoice value, even modest invoice amounts can push the quarterly total well above the €300 minimum and toward the €6,000 cap. Once you hit the cap, further late submissions in the same quarter carry no additional financial penalty, but the audit exposure and VAT deduction risk remain.

Benefits of SII compliance

SII compliance is not just a new administrative burden. Businesses that are subject to it (or that opt in voluntarily) also gain some true compliance advantages.

Exemption from Forms 340, 347, and 390

SII filers do not need to file three significant periodic returns:

• Form 340: Quarterly record books of issued and received invoices
• Form 347: Annual third-party transaction report (covering transactions above €3,005.06 with a single counterparty)
• Form 390: Annual VAT summary return

For businesses with large transaction volumes, eliminating these three filings means a significant reduction in compliance overhead.

Extended VAT filing deadlines

SII filers get a 10-day extension on Form 303 (the monthly VAT return). Instead of the standard 20th-of-the-month deadline, SII filers have until the 30th. That extra window gives finance teams more time to reconcile and validate data before submitting.

Faster VAT refunds and pre-completed returns

Because the AEAT already holds detailed invoice-level data from SII submissions, it can generate draft VAT declarations for SII filers. This reduces the amount of manual reconciliation needed when preparing the VAT filing with Form 303.

The quality of that pre-populated draft depends entirely on the accuracy and completeness of your SII submissions. Businesses that submit clean, complete data on time get the most benefit. Businesses with frequent errors or rejections get a messier draft that requires more manual correction.

This is also where having a single platform for both SII submissions and VAT returns becomes a significant advantage. When both data streams live in the same system and the same data model, there is no reconciliation gap between what you submitted to SII and what you reported on Form 303. Using separate vendors for each creates exactly that gap, and closing it manually is time-consuming and error-prone.

How Sphere helps businesses stay compliant with Spain's SII

Sphere will support SII from Q2 2026. It will be one of the few platforms on the market that handles both VAT returns and SII reporting within a single native data model.

That matters because the two obligations are tightly linked. Your Form 303 VAT return must match your SII records. If you use one provider for SII submissions and a different provider (or manual process) for VAT returns, you are creating a reconciliation problem every single month. Finding and fixing those discrepancies takes time, and unresolved mismatches put your VAT deductions at risk.

Sphere handles the full Spanish VAT workflow in one place: nexus monitoring, VAT calculation, Form 303 filing, and SII XML submission. The four-day submission cadence is automated, with no manual data handling required. And because everything runs through one data model, there is no gap between what Sphere reports to the AEAT via SII and what it files on your VAT return.

For businesses approaching the €6 million turnover threshold in Spain, now is the right time to assess whether your current compliance infrastructure can handle both obligations without creating new reconciliation work.

Ready to simplify your Spanish VAT compliance?

Schedule a demo with Sphere today.

Book a Call

SII is the foundation of Spain's digital VAT infrastructure

SII has been the backbone of Spain's real-time tax reporting since July 2017. It is not going away. If anything, Spain is building additional digital tax layers on top of it.

VeriFactu (mandatory from January 2027) adds requirements for non-SII businesses around invoicing software integrity. Crea y Crece (phased rollout from 2027 to 2028) will require structured invoice exchange between business trading partners. Knowing which of these three systems applies to which entity in your structure is essential.

For businesses already in SII, the priority is operational: tight four-day submission cycles, accurate XML data, and alignment between SII records and monthly VAT returns. For businesses approaching the €6 million threshold, the time to build SII-compatible infrastructure is before the obligation hits, not after.

Spain's tax authority is getting better at cross-referencing SII data with other filings. The AEAT already uses SII records to spot mismatches in VAT returns. That enforcement capability will only grow as the system matures. Be sure your business is ready.