Spain Fiscalization Update: Rethinking POS Investment

The planned VERI FACTU delay strengthens the case for waiting on a speculative checkout redesign while the new B2B invoicing timetable requires preparation now

Spain has given retailers a reason to reconsider their next compliance investment, although the strongest argument for restraint applies to a narrower category of spending than the headlines suggest. For a large retailer already reporting through Suministro Inmediato de Información, or SII, a project to install today’s VERI*FACTU model across the store estate has little justification solely on the assumption that this will become its next mandatory architecture. Preparation for B2B electronic invoicing, however, now has a concrete timetable, and treating the latest announcement as permission to suspend that work would confuse two different regulatory developments.

On 5 October, the Ministry of Finance announced its intention to postpone the pending obligations under Royal Decree 1007/2023 until October 2028, aligning them with mandatory electronic invoicing for businesses whose annual turnover does not exceed €8 million. After that calendar alignment is approved, Hacienda intends to pursue convergence in scope and certain technical aspects, taking future ViDA reporting requirements into account. The ministry also says that the existing requirements for data integrity and preservation, together with the system’s other technical guarantees, will remain substantially equivalent.

The wording matters because the ministry published a statement of intended changes, rather than the legislative amendment implementing them. Europa Press and the EFE report carried by Infobae describe the development as a postponement, but an investment decision should retain the distinction between a government announcement and an enacted deadline. The existing legislation still sets 1 January 2027 for the relevant corporate taxpayers and 1 July 2027 for the remaining taxpayers in scope; the October 2028 date needs the corresponding legal amendment.

Meanwhile, Spain has moved forward on a separate track. Order HAC/1028/2026 was published in the BOE on 5 October and entered into force on 6 October, starting the implementation periods for mandatory B2B e-invoicing. Under Royal Decree 238/2026, the general timetable is twelve months for businesses whose relevant annual volume of operations exceeds €8 million and twenty-four months for the rest, pointing to 6 October 2027 and 6 October 2028 respectively. The proposed VERI*FACTU alignment therefore refers to the later invoicing phase, rather than giving every large retailer until 2028.

Taken together, these measures suggest a government trying to reduce the cost of successive adaptations while allowing an already developed invoicing framework to advance. For retail technology budgets, that creates a distinction between implementing requirements with a defined legal basis and financing a store-level design for a successor system whose specifications have yet to be established.

The Senate proposal is becoming more relevant

In my August article on the Senate’s convergence motion, I argued that large retailers should pay attention because the proposal challenged the separation between SII, VERI*FACTU and electronic invoicing. I also considered it more likely that the government would pursue interoperability while retaining the 2027 VERI*FACTU rollout. The October announcement changes that assessment, since Hacienda now explicitly intends to defer the pending rollout and examine convergence beyond the calendar itself.

This strengthens the strategic relevance of the earlier debate without establishing that the government has adopted the Senate’s entire proposed architecture. The ministry’s note does not announce the abolition of SII, remove its current exclusion from the invoicing-system regulation or prescribe a universal successor interface. My reading is that the case for convergence has gained government support, while the architecture through which it will be delivered remains open.

That uncertainty has a direct commercial consequence. A retailer that commissions a substantial POS modification today to comply with an imagined unified Spanish model would be paying for assumptions about scope, document handling and reporting interfaces that the ministry has not yet translated into requirements. Even if a future model incorporates concepts familiar from VERI*FACTU, it could distribute responsibilities differently between the checkout, central invoicing services and the tax reporting layer.

Large retailers remain in a different position

The starting point for large retailers remains their current SII status. The invoicing-system regulation excludes taxpayers keeping their VAT ledgers through SII, and the AEAT confirms that exclusion. Mandatory SII participation includes large businesses whose previous-year VAT volume of operations exceeds €6,010,121.04, as well as VAT groups and businesses registered for monthly refunds, with voluntary participation also possible. The €8 million e-invoicing threshold is a separate test and should never be used as a substitute for determining SII status.

A group’s consolidated size is therefore an insufficient basis for a deployment decision. A retailer needs to establish the position of each Spanish taxpayer entity, including separately operated franchises or smaller subsidiaries, and account for any applicable territorial regime. A business with volume of operations between the two thresholds may already belong to SII while entering the later B2B e-invoicing phase, illustrating why a single label such as “large retailer” cannot resolve every obligation.

For an SII taxpayer, the announced delay does not create a new exemption, since the current exclusion already exists. Its significance lies in the possibility that future convergence may change the relationship between systems on which that exclusion depends. Large retailers should monitor that possibility, but the note supplies no basis for asserting that every checkout must now generate today’s VERI*FACTU records or that SII reporting can be discontinued.

The analysis also needs to distinguish the wider requirements for invoicing software, commonly discussed under the VERI*FACTU label, from the specific VERI*FACTU mode that transmits records to the tax authority. Equating the entire regulation with a single transmission model can make a procurement exercise unnecessarily narrow before the future rules have even been published.

Electronic invoicing still deserves investment

My latest article on Spain’s B2B technical specifications examined how a business invoice can originate at a retail checkout even though ordinary consumer sales remain a different scenario. That distinction becomes especially important when deciding which POS changes are justified: the B2B framework generally excludes ordinary simplified invoices, with an exception for qualified simplified invoices carrying the additional recipient information needed for VAT deduction. The actual document and transaction scope must be assessed rather than treating every store receipt as a new structured B2B invoice.

The public solution uses the EN 16931 semantic model with UBL syntax, while the rules also address faithful invoice copies and invoice and payment-status communications. A large retailer must consider its supplier invoice processes alongside its business-customer sales, which can place much of the implementation work in central invoicing and accounts payable. These are operational requirements with a published framework, even though detailed integration work must also follow the AEAT’s service specifications.

Consider a store selling equipment to a domestic business customer that needs an invoice within the B2B rules. The checkout must capture and pass the information needed to produce that invoice, but there is no obvious operational advantage in making each terminal responsible for the full exchange and payment-status lifecycle. A central service can handle those responsibilities where the architecture and applicable rules permit, provided the handoff from the sale is complete and reliably linked to the invoice.

This is where I would direct investment today. If customer identification is incomplete, invoice requests disappear between POS and ERP, or corrections cannot be reconciled with the original sale, those weaknesses will obstruct compliance regardless of how Spain eventually combines its reporting systems. Fixing them produces value under the published e-invoicing framework and reduces the difficulty of adapting to later requirements.

The investment decision depends on what is being built

POS software vendors cannot apply the same spending conclusion indiscriminately across their customer base. Vendors supplying invoicing systems within the existing regulation’s scope must continue to address their current producer and commercialisation obligations; the legislation gives them a separate adaptation rule, and a statement about postponing pending taxpayer obligations does not suspend duties that already apply. Maintaining a compliant product for customers outside SII is a different decision from building a speculative universal version for SII retailers.

Existing development also retains value because Hacienda intends to preserve the core technical guarantees. The commercial risk is concentrated in commitments that assume the current interfaces and allocation of responsibilities will remain the final design. Vendors should be careful about promising that a particular connector or store rollout already solves Spain’s future convergence programme, while continuing to support the obligations their products and customers have today.

ViDA provides a further reason to avoid rigid designs, although its reporting timetable should not be confused with a universal deadline for Spanish consumer receipts. The European Commission identifies 1 July 2030 for digital reporting affecting cross-border B2B transactions and 1 January 2035 for alignment of existing domestic real-time transaction reporting systems with the European model. Spain’s reference to ViDA indicates a longer-term design consideration, without specifying a single domestic retail reporting architecture.

For large SII retailers, I would therefore defer a major POS fiscalization rollout undertaken solely to anticipate a future convergence mandate, while continuing existing SII compliance and preparing the B2B invoice flows that fall within the new timetable. Targeted POS changes make sense where they supply missing invoice data or repair a demonstrable integration problem; a wholesale redesign based on unpublished successor requirements is much harder to defend.

Spain’s latest announcement makes the cost of premature architectural commitments more visible, particularly for retailers operating thousands of terminals. The next investment should be supported by a current obligation or a clear operational need, with enough flexibility to accommodate the convergence programme when its actual rules arrive. A retailer that preserves that discipline can use the additional time productively without paying twice for a compliance design that is still being negotiated.