Spain introduced the Immediate Supply of Information (SII – Suministro Inmediato de Información del IVA) to modernize VAT administration, improve tax transparency, and combat VAT fraud. Inspired by the success of mandatory electronic reporting systems in Latin America, SII requires certain taxpayers to submit VAT ledger information electronically to the Spanish Tax Agency (AEAT) in near real time. Rather than transmitting complete invoices, businesses report the relevant VAT register data through XML-based web services, enabling the tax authority to reconstruct VAT records and monitor compliance more effectively.

The SII obligation was introduced through Royal Decree 596/2016 (2 December 2016), which amended the Spanish VAT Regulations (Royal Decree 1624/1992). The system became mandatory on 1 July 2017 and remains one of Europe's earliest continuous VAT reporting regimes.

Background

Several Latin American countries—including Mexico, Brazil, Chile, and Peru—have successfully implemented mandatory e-invoicing and electronic VAT reporting to reduce tax evasion and improve VAT collection. Their success influenced European tax authorities to adopt similar digital reporting initiatives.

Spain became one of the first European countries to implement near-real-time VAT reporting with the launch of SII in July 2017.

Unlike traditional e-invoicing systems, SII focuses on the electronic submission of VAT ledger information rather than the exchange of invoices themselves.

Current Status

• Go-live: Mandatory since 1 July 2017.
• Reporting model: Near-real-time electronic VAT ledger reporting.
• Tax authority: Spanish Tax Agency (AEAT).
• Submission method: XML-based web services through the AEAT Electronic Office.
• Invoice transmission: Full invoices are not submitted; only VAT register information is reported electronically.
• Primary objective: Improve VAT control, reduce fraud, and streamline VAT audits.

Legal Framework

Who Must Comply

SII is mandatory for:

• Large businesses filing monthly VAT returns
• Companies registered in the REDEME (Monthly VAT Refund Register)
• VAT Groups
• Other taxpayers that voluntarily opt into the SII regime

Businesses outside these categories may continue using traditional VAT reporting unless they elect to participate voluntarily.

Reporting Requirements

Unlike traditional e-invoicing systems, SII requires businesses to submit the information contained in their VAT books rather than complete invoice documents.

The following records must generally be reported:

• Sales invoices
• Purchase invoices
• Intra-Community transactions
• Investment goods records
• Certain cash accounting transactions where applicable

The information is submitted electronically through XML-based web services to AEAT.

Reporting Timeline

Businesses must generally transmit VAT ledger information:

• Within four calendar days of issuing or recording an invoice
• Saturdays, Sundays, and national public holidays are excluded when calculating the deadline

Timely reporting is critical because delayed submissions may result in penalties.

How the Model Works

Reporting Architecture

Spain follows a centralized reporting model.

The reporting process typically consists of:

1. Invoice is posted in the ERP system.
2. VAT ledger information is extracted.
3. XML message is generated.
4. XML is transmitted electronically to AEAT.
5. AEAT validates the submission.
6. Status response is returned to the taxpayer.

Possible responses include:

• Accepted
• Rejected
• Partially accepted

Businesses must monitor these responses and correct rejected submissions where necessary.

SAP Technical Roadmap

For SAP ECC and SAP S/4HANA environments, SII compliance is commonly implemented using SAP Document Compliance.

The standard process includes:

Business Scenario Identification

Determine which transactions require reporting, including:

• Outgoing invoices
• Incoming invoices
• Intra-Community transactions
• Investment goods

Data Mapping

Map SAP accounting fields to the required SII XML structure.

Typical mapping includes:

• Customer/vendor information
• Tax codes
• VAT amounts
• Invoice numbers
• Posting dates
• Tax dates

XML Generation

Generate XML payloads according to AEAT specifications.

Integration

Transmit XML messages using:

• SAP Document Compliance
• SAP PI/PO
• SAP Cloud Integration (CPI)
• Third-party middleware

Response Handling

Capture AEAT acknowledgements and manage:

• Accepted submissions
• Rejections
• Partial rejections
• Corrections and resubmissions

Typical SAP Implementation Flow

A standard implementation follows these stages:

1. Post accounting document in SAP.
2. Generate SAP eDocument.
3. Extract VAT reporting data.
4. Build XML payload.
5. Submit to AEAT through the integration layer.
6. Receive validation response.
7. Store submission status in SAP.
8. Monitor, correct, and resubmit rejected records if required.

This closed-loop process ensures both successful transmission and confirmation that AEAT has accepted the reported information.

Implementation Considerations

A successful SII implementation requires both technical configuration and strong business controls.

Key activities include:

• Legal and compliance gap analysis
• VAT process review
• SAP field mapping
• Tax code validation
• XML configuration
• Interface development
• Exception handling
• User acceptance testing
• Production monitoring

Testing should include scenarios such as:

• Credit notes
• Invoice cancellations
• Simplified invoices
• Intra-Community transactions
• Posting date versus reporting deadline differences
• Rejected and corrected submissions

Compliance Challenges

Organizations commonly face challenges related to:

• Meeting the four-day reporting deadline
• Ensuring high-quality master data
• Maintaining VAT code accuracy
• Managing corrections and resubmissions
• Reconciling SAP records with AEAT acknowledgements
• Integrating SAP with external middleware and tax authority services

Failure to submit complete or accurate information within the required timeframe may lead to penalties and additional administrative effort.

Benefits

SII offers several long-term advantages:

• Improves VAT transparency
• Reduces tax fraud
• Enables near-real-time tax monitoring
• Simplifies VAT audits
• Encourages higher-quality accounting data
• Automates VAT reporting processes
• Reduces manual reporting activities
• Improves reconciliation between taxpayers and tax authorities

Key Takeaways

• Understand the legal scope: Determine whether your organization falls within the mandatory SII regime or has opted in voluntarily.
• Prepare SAP systems: Configure SAP ECC or SAP S/4HANA to generate compliant XML reporting through SAP Document Compliance or an equivalent solution.
• Ensure data quality: Accurate master data, tax codes, and invoice information are essential for successful reporting.
• Monitor submissions: Track AEAT acknowledgements and establish efficient correction and resubmission procedures for rejected records.
• Treat SII as a business transformation initiative: Successful compliance depends on aligning legal requirements, business processes, SAP configuration, and system integration to support continuous electronic VAT reporting