VERI*FACTU and Spain’s Computerized Billing-System Rules

Spain’s RRSIF framework regulates computerized invoicing systems (SIF) used by in-scope businesses and professionals. VERI*FACTU is the optional operating mode that sends invoice records to AEAT continuously; a compliant non-VERI*FACTU mode also exists.

Compliance Summary

Area	What SAP teams should check
Mandate	RRSIF requirements for computerized billing systems; VERI*FACTU is the optional immediate-transmission mode
Authority	Agencia Estatal de Administración Tributaria (AEAT)
Core impact	Invoice-record generation, immutability, traceability, QR content, XML output, and optional near real-time AEAT transmission
Current timing	Under Royal Decree-law 15/2025 (December 2025), which postponed the original 2026 dates: Corporate Income Tax filers before 1 January 2027; other taxpayers before 1 July 2027.
SAP review focus	Billing documents, tax codes, customer master data, XML mapping, corrective invoice handling, transmission workflow, and response/error monitoring

Core Objectives

• Combat tax fraud: reduce the use of invoicing software that can hide, alter, or delete invoice records.
• Preserve invoice integrity: make invoice records traceable from creation through cancellation or correction.
• Support digital tax control: enable invoice data to be validated or checked through AEAT-aligned records and formats.

Key Requirements for Invoicing Software

• Integrity and immutability: invoice records must not be changed without a controlled correction or cancellation trace.
• Traceability: each issued invoice needs a record that can be followed through the reporting and audit process.
• Secure transmission mode: systems may operate in VERI*FACTU mode by sending invoice records to AEAT in real time or near real time.
• QR and verification data: invoice output must support the required verification information where applicable.
• XML output: invoice records need to be generated in the required structured format for the applicable workflow.

Who Is Affected?

The rules apply to in-scope businesses and professionals using computerized invoicing systems, subject to the detailed territorial, taxpayer and transaction exclusions. Taxpayers already subject to SII are expressly excluded from RRSIF; this is not merely an “interaction” to review.

SAP Impact Areas

SAP area	Why it matters
SD billing	Invoice and corrective invoice data usually originates from billing documents.
FI tax data	Tax codes, VAT treatment, exemptions, and reverse-charge cases need correct mapping.
Master data	Customer and company tax identifiers must be clean enough for reporting and validation.
XML generation	Invoice records need to be mapped to the required AEAT-aligned structure.
Monitoring	Rejected or partially accepted records need operational follow-up by finance and IT teams.

How S4FN Can Help

S4FN helps SAP teams review the billing, tax-code, invoice-record, QR and operating-mode design needed for Spain’s RRSIF readiness. Where VERI*FACTU mode is selected, the review also covers continuous AEAT transmission and response monitoring. The technical design should be confirmed against the current AEAT specifications and the customer’s actual SAP landscape.

Official sources

• AEAT — scope, obligated taxpayers and included operations
• AEAT — extended SIF adaptation deadlines

Regulatory content verified: 10 July 2026.

Verified on: 10 July 2026. Confirm the current legal scope, authority technical package and SAP-supported scenario before implementation.