SAP E-Invoicing in Spain: VeriFactu, SII & DRC Integration

Spain has two compliance systems, SII and VeriFactu. SAP Spain e-invoicing integration handles each on its own terms. This guide covers what SAP Document and Reporting Compliance does, how S/4HANA, ECC and Business One differ, and the steps for SAP e-invoicing configuration.

Key Takeaways

• SAP Document and Reporting Compliance (DRC) is the standard SAP module for Spain e-invoicing.
• S/4HANA supports DRC natively. ECC and Business One need extra setup or a certified connector.
• SII reports invoice data within four calendar days. VeriFactu governs how your software generates and stores the records themselves.
• SII-registered taxpayers are exempt from VeriFactu/SIF requirements.
• Facturae remains the format for B2G invoicing through FACe, while B2B is moving toward UBL.

What Is SAP E-Invoicing Integration for Spain?

SAP e-invoicing integration for Spain is the configuration that connects your SAP system to the AEAT's reporting systems and generates invoices in the formats Spanish law requires.

What drives all this is SAP Document and Reporting Compliance Spain, known as DRC. It creates structured invoice records, applies the digital signature, adds the required QR code, and submits data to the tax authority. Depending on your SAP version, DRC either runs built into the system or connects through SAP's cloud integration layer.

The legal basis behind all of this sits across three instruments: the General Tax Law, Royal Decree 1619/2012 on invoicing obligations, Real Decreto 238/2026, de 25 de marzo (published 31 March 2026) defining e-invoicing architectureand Royal Decree 1007/2023 (published 6 December 2023), which introduced VeriFactu. Between them, these define what counts as a valid invoice, what data must reach the AEAT, and the deadlines your SAP configuration needs to meet.

Technical Requirements Across All SAP Systems

Whatever SAP version you run, a SAP VeriFactu integration needs a few technical pieces in place before you can call the setup compliant. Spain does not accept a partial implementation, since SII and VeriFactu each carry their own penalties for gaps.

• Structured invoice output- Your system needs to produce invoice data as XML, matching the AEAT's expected schema.
• A qualified electronic signature- VeriFactu records need XAdES or an equivalent signature to prove authenticity.
• Hash chaining- Under VeriFactu, each invoice record carries a hash of the one before it. Alter a record after submission, and the chain breaks from that point on.
• Live connectivity to the AEAT- SII needs a real-time submission channel. VeriFactu mode, if you switch it on, needs the same.
• QR code generation on printed invoices- Every VeriFactu-compliant document needs a scannable QR linking to the AEAT verification page.

SAP Note 3585725 sets out the technical detail for VeriFactu, and KBA 3609812 answers the common configuration questions. For ECC specifically, KBA 2872857, the eDocument Spain Troubleshooting Guide, lists the SAP Notes your Basis team needs to install in sequence. All three are worth having open while you plan.

SII vs VeriFactu in SAP: What's the Difference?

The two systems solve different problems, and SAP treats them as separate configuration tracks.

A SAP Spain SII integration handles reporting. SII, the Suministro Inmediato de Información, is about getting invoice data to the AEAT fast. Once you're in scope, invoice ledger data goes to the AEAT within four calendar days of issue or receipt. In SAP, this runs through the eDocument cockpit, submitting structured records as each invoice posts.

A SAP DRC VeriFactu setup is about the software itself, not the reporting. It sets rules for how your billing system generates and stores invoice records, chained, unalterable, and carrying a QR code. If your business is already in SII, whether by size or by choice, you're outside VeriFactu's scope, since SII already gives the AEAT the same real-time visibility. If you're not in SII, VeriFactu applies once you use invoicing software that meets the legal definition of a Sistema Informático de Facturación (SIF).

In practical terms: large SAP customers already on SII configure DRC for SII submission. Everyone else configures DRC, or a certified add-on, for VeriFactu instead.

There's a third layer too, separate from both. B2B e-invoicing under the Crea y Crece law will eventually require structured invoice exchange between businesses, likely in UBL format, including CII (UN/CEFACT), EDIFACT, and Facturae, all aligned to EN 16931, alongside a copy sent to a central public platform. Its final technical rules are still pending a Ministerial Order, so SAP customers should treat SII and VeriFactu as the immediate priority and build in flexibility for B2B requirements to follow.

Step-by-Step: SAP E-Invoicing Configuration for Spain

Step 1: Confirm your scope- Work out whether your entities sit under SII, VeriFactu, or both, since some group structures have a mix.

Step 2: Choose your integration approach- For SAP ECC VeriFactu setups, the route differs from S/4HANA. S/4HANA and S/4HANA Cloud customers activate DRC directly. ECC customers use SAP's own eDocument Framework together with SAP Document Compliance, on-premises edition, a separately licensed add-on that communicates through SAP Cloud Platform Integration. It's a native SAP path, not a third-party workaround, but it does need its own licence and setup, distinct from DRC on S/4HANA. 

For SAP Business One Spain e-invoicing, customers typically need a certified partner add-on instead, since Business One has no equivalent native module. A VeriFactu SAP add-on from a certified partner fills that gap, drawing on SAP's local partner network to cover Spanish requirements.

Step 3: Activate DRC and define your process- In S/4HANA Cloud, this means switching on Document and Reporting Compliance and defining process communication through cloud services, covered under the standard SSCUI configuration steps for Spain.

Step 4: Map your invoice output- A Facturae SAP configuration means setting up your billing documents to generate the correct format. Facturae for B2G submissions through FACe, and the format your VeriFactu or SII process expects for everything else.

Step 5: Set up the digital signature and QR code- Configure the certificate used for signing, and confirm your print forms carry the QR code where VeriFactu applies.

Step 6: Test in the AEAT sandbox- Submit test invoices before going live, since both SII and VeriFactu offer pre-production environments for exactly this.

Step 7: Monitor through the eDocument cockpit- Once live, use it to track submission status, catch errors early, and confirm the AEAT has acknowledged each record.

Conclusion

Spain's dual system means SAP configuration is not a single task. SII and VeriFactu each carry their own technical requirements and their own risks if left incomplete. S/4HANA customers have the most direct path through native DRC, while ECC and Business One users need to plan for a SAP certified connector Spain or add-on earlier in the project. Getting e-invoice configuration in SAP right from the start avoids a costly rebuild later. Getting the scope right first, SII, VeriFactu, or both, is what keeps the rest of the configuration straightforward.