{"id":42674,"date":"2026-10-12T09:59:53","date_gmt":"2026-10-12T07:59:53","guid":{"rendered":"https:\/\/deveho.com\/?p=42674"},"modified":"2026-10-12T11:24:52","modified_gmt":"2026-10-12T09:24:52","slug":"verifactu-spains-new-tax-control-system","status":"publish","type":"post","link":"https:\/\/deveho.com\/lt\/newsroom-lt\/verifactu-spains-new-tax-control-system\/","title":{"rendered":"VeriFactu: Spain’s new tax control system"},"content":{"rendered":"
\n

VeriFactu: Spain’s new tax control system<\/red><\/h2>\n

Businesses in Spain must prepare for new compliance requirements arising from the regulation governing computerised invoicing systems (SIF), of which VeriFactu is one of the available compliance methods. Initially scheduled for 2026, the obligation to adapt invoicing systems was postponed to 2027. On 5 October 2026, the Spanish Ministry of Finance announced its intention to postpone certain obligations until October 2028. However, this revised timetable remains subject to formal adoption of the relevant provisions. <\/p>\n

Derived from Spain\u2019s 2021 Anti-Fraud Law and developed, in particular, by Royal Decree 1007\/2023, as amended in 2025, and Ministerial Order HAC\/1177\/2024, the framework aims to strengthen the integrity, traceability and preservation of invoicing data in order to combat tax fraud. <\/p>\n

As a Sage business partner, Deveho Consulting Group supports businesses as they transition towards more secure invoicing management, including through solutions such as Sage X3. Actual compliance depends, however, on the software version, its configuration and the requirements applicable to each business.<\/p>\n

What is VeriFactu?<\/red><\/h3>\n

VeriFactu is one of the two compliance methods provided for under Spanish regulations governing computerised invoicing systems. These regulations require affected systems to ensure, among other things, the integrity, preservation, accessibility, readability, traceability and immutability<\/strong> of invoicing records.<\/p>\n

In practice, each invoice issued generates a computerised record that must meet specific technical requirements. Depending on the method selected, this record can either:<\/p>\n

    \n
  • Be transmitted automatically to the Spanish Tax Agency (Agencia Estatal de Administraci\u00f3n Tributaria<\/em>, AEAT) under the VERI*FACTU method.<\/li>\n
  • Or be retained within the invoicing system in accordance with enhanced security requirements, without systematic transmission to the AEAT, under the NO VERI*FACTU method.<\/li>\n<\/ul>\n

    The regulations also require a QR code to be included on the relevant invoices, in accordance with the conditions set out in the applicable legislation.<\/p>\n

    \n

    The objective is clear:<\/strong> to limit the possibility of manipulating invoicing data, improve traceability and facilitate tax oversight.<\/p>\n<\/blockquote>\n

    \"Logo-Verifactu\"<\/p>\n<\/p>\n

    Implementation timetable<\/red><\/h3>\n

    The regulatory timetable has already been postponed. As at 12 October 2026, the deadlines set out in the regulations currently in force remain as follows:<\/p>\n

      \n
    • From 29 July 2025:<\/strong> affected software producers and commercial suppliers must make invoicing systems that meet the regulatory requirements available, in accordance with the timetable laid down in the legislation. This does not amount to universal official certification of all software; rather, it involves meeting the applicable requirements and corresponding declaration obligations.<\/li>\n
    • From 1 January 2027:<\/strong> taxpayers subject to Spanish Corporation Tax (Impuesto sobre Sociedades<\/em>) must have adapted their computerised invoicing systems.<\/li>\n
    • From 1 July 2027:<\/strong> this obligation extends to other affected taxpayers, including self-employed individuals carrying out an economic activity.<\/li>\n<\/ul>\n

      Regulatory update:<\/strong> on 5 October 2026, the Spanish Ministry of Finance announced its intention to postpone the remaining obligations under the SIF regulation until October 2028, with the aim of aligning the timetable with that of B2B electronic invoicing for certain businesses. At the time of this update, this announcement should be distinguished from a formal legislative amendment. Businesses should therefore monitor official publications before changing their compliance timetable.<\/p>\n

      Please note that taxpayers covered by the Immediate Supply of Information system (Suministro Inmediato de Informaci\u00f3n<\/em>, SII) are excluded from the scope of the SIF regulation in respect of their own invoices, subject to the conditions set out in the legislation. Specific rules may also apply in Spanish territories operating under special tax regimes.<\/p>\n<\/p>\n

      How can you ensure compliance with VeriFactu?<\/red><\/h3>\n

      To comply with the regulations, affected computerised invoicing systems must incorporate several technical and functional requirements:<\/p>\n

        \n
      • Integrity and immutability of records:<\/strong> data must be protected against unauthorised or non-compliant modification or deletion. Corrections and cancellations must follow the applicable regulatory procedure and preserve the required audit trail; the original record cannot simply be deleted at will.<\/li>\n
      • Traceability and chaining of records:<\/strong> a digital fingerprint mechanism (hashing<\/em>) links records together, making it possible to detect potential alterations.<\/li>\n
      • Mandatory QR code:<\/strong> relevant invoices must include a QR code that allows certain information to be transmitted to the AEAT or available verification information to be consulted, depending on the method used.<\/li>\n
      • Transmission of records:<\/strong> under the VERI*FACTU method, invoicing records are transmitted to the AEAT immediately after they are generated, in accordance with the technical specifications.<\/li>\n
      • Additional security requirements:<\/strong> under the NO VERI*FACTU method, the system must meet enhanced obligations, particularly regarding record signatures and the retention of a system event log.<\/li>\n
      • Software compliance declaration:<\/strong> affected software producers must fulfil the applicable regulatory obligations for their solutions, including those relating to technical compliance and documentation.<\/li>\n<\/ul>\n

        It is important to distinguish these requirements from those governing B2B electronic invoicing. VeriFactu primarily concerns the operation and traceability of invoicing systems, whereas B2B electronic invoicing concerns the issuing and receiving of electronic invoices between businesses and professionals.<\/p>\n<\/p>\n

        The roles of the different parties involved<\/red><\/h3>\n
          \n
        • Issuer:<\/strong> the business or professional issuing the invoice must use a compliant system where the regulation applies. Under the VERIFACTU method, records are transmitted to the AEAT. Invoices issued under this method must include the prescribed wording, \u00abFactura verificable en la sede electr\u00f3nica de la AEAT\u00bb or \u00abVERI<\/em>FACTU\u00bb, as applicable under the relevant provisions.<\/li>\n
        • Recipient:<\/strong> the customer receives the invoice and can use its QR code to access the verification features provided by the AEAT. They may also submit certain information to the tax authority through the prescribed procedure. However, the QR code does not, in itself, constitute a general certification of the invoice\u2019s commercial validity.<\/li>\n
        • Software provider:<\/strong> the supplier of the invoicing system must comply with the regulatory requirements applicable to it and provide a compliant solution within the prescribed deadlines.<\/li>\n
        • Tax authority:<\/strong> the AEAT receives records transmitted under VERI*FACTU and provides the consultation and verification services \u043f\u0440\u0435\u0434\u0443\u0441\u043c\u043e\u0442\u0440ed by the system.<\/li>\n<\/ul>\n

          The benefits of VeriFactu<\/red><\/h3>\n

          Compliance with the SIF regulation and the use of the VERI*FACTU method can offer several benefits:<\/p>\n

            \n
          • Improved traceability of invoicing records.<\/li>\n
          • Automated transmission of records to the AEAT under the VERI*FACTU method.<\/li>\n
          • Reduced risk of fraudulent manipulation of data.<\/li>\n
          • Easier access to verification information through QR codes.<\/li>\n
          • Greater availability of the data required for tax inspections.<\/li>\n
          • Modernised invoicing processes and better integration with business management tools.<\/li>\n
          • A more structured approach to preparing for future changes in digital tax regulations.<\/li>\n<\/ul>\n

            The choice of method must nevertheless take into account the business\u2019s obligations, organisation and computer system capabilities. NO VERI*FACTU remains a permitted regulatory option for affected taxpayers, but it entails specific technical requirements.<\/p>\n<\/p>\n

            How can Deveho Consulting Group support your business?<\/red><\/h3>\n

            Achieving compliance with VeriFactu may require technical, organisational and functional adjustments. As a Sage business partner, Deveho Consulting Group<\/strong> supports businesses as they evolve their management and invoicing processes, including through solutions such as Sage X3<\/a><\/strong>.<\/p>\n

            Depending on the version deployed, the configuration selected and the business\u2019s requirements, this support can help to:<\/p>\n

              \n
            • Secure invoicing processes and data management.<\/li>\n
            • Assess the changes required to the computer system.<\/li>\n
            • Prepare the necessary adaptations to meet applicable regulatory requirements.<\/li>\n
            • Improve the integration of invoicing processes with other business management functions.<\/li>\n
            • Anticipate changes to the Spanish tax framework.<\/li>\n<\/ul>\n

              Compliance must be verified for the specific software version and configuration in use. Businesses are therefore advised to confirm the VeriFactu functionality available with their Sage representative or implementation partner.<\/p>\n<\/p>\n

              Electronic invoicing vs VeriFactu<\/h2>\n<\/p>\n

              Electronic invoicing vs VeriFactu<\/red><\/h3>\n

              Spain is undergoing a significant transformation of its invoicing requirements, with several measures designed to modernise business transactions and strengthen tax oversight. Two areas should be distinguished in particular: B2B electronic invoicing and the regulation governing computerised invoicing systems, of which VeriFactu is one compliance method. Although related, they have different objectives and requirements.<\/strong><\/em><\/p>\n<\/p>\n

              Electronic invoicing<\/red><\/h3>\n

              Electronic invoicing involves issuing, transmitting and receiving invoices in electronic form, in accordance with the applicable regulatory requirements.<\/p>\n

              Its objectives include digitising exchanges between businesses, improving administrative efficiency and simplifying invoice processing.<\/p>\n

              An electronic invoice is not necessarily just a PDF sent by email. Depending on the applicable legislation, it may need to meet specific requirements concerning format, transmission, receipt and retention.<\/p>\n

              Spanish regulations on B2B electronic invoicing have their own implementation timetable. In October 2026, the Ministry of Finance announced its intention to align this timetable more closely with that of the SIF\/VeriFactu obligations. The applicable deadlines must be confirmed against the officially published legislation.<\/p>\n

              \n

              To find out more about electronic invoicing in Spain and Europe, read our dedicated article:<\/em><\/p>\n<\/blockquote>\n

              \n

              E-invoicing in Europe: Accelerating towards compliance<\/a><\/p><\/blockquote>\n