Navigation

fino data services logo
KNOWLEDGE · FACTSHEET

E-invoicing in Spain

FactsheetReading time: approx. 7 minutes

Deadlines at a glance

Date Who is affected What applies
15 January 2015 Corporations and other suppliers to public administrations E-invoice in the Facturae format via FACe or the competent entry point
1 January 2027 Users of invoicing software subject to corporate income tax Verifactu requirements, postponement to October 2028 announced
1 July 2027 Other users of invoicing software Verifactu requirements, postponement to October 2028 announced
6 October 2027 Companies with a volume of operations of more than 8 million euros in the previous year Issuing, transmitting and receiving e-invoices, status messages
6 October 2028 All other businesses and self-employed professionals Issuing, transmitting and receiving e-invoices, status messages for legal entities
6 October 2029 Natural persons and entities under the income attribution regime up to 8 million euros Status messages
1 July 2030 Businesses with cross-border B2B transactions within the EU Mandatory e-invoicing under ViDA

E-invoicing in B2B

Obligation to receive

Businesses and self-employed professionals must be able to receive e-invoices from other businesses. The obligation is set out in Article 2 bis of Ley 56/2007, inserted by Ley 18/2022. The same cut-off dates apply to receiving as to sending, namely 6 October 2027 for companies with a volume of operations of more than 8 million euros and 6 October 2028 for all others. Anyone who does not designate their own entry point with a private platform can be reached via the public solution of the AEAT (Article 6 of Real Decreto 238/2026).

Obligation to send

The obligation applies to invoices to businesses and self-employed professionals with a registered office, permanent establishment or residence in Spain. What counts is the volume of operations (volumen de operaciones) of the previous year under Article 121 of the Spanish VAT Act. Companies with a volume of operations of more than 8 million euros must issue electronically from 6 October 2027, all others from 6 October 2028. The cut-off dates are set by Orden HAC/1028/2026. Companies in the first stage must attach a readable PDF version during the first twelve months, unless the recipient waives this. Simplified invoices (facturas simplificadas) are exempt. This does not apply to qualified simplified invoices under Article 7.2 of Real Decreto 1619/2012.

Status messages

The recipient must report acceptance or rejection with the date, as well as full payment with the payment date, in each case within four working days, excluding Saturdays, Sundays and national public holidays (Article 10 of Real Decreto 238/2026). Partial acceptance, partial payment and assignment can be reported. If there is neither a rejection nor a corrective invoice (factura rectificativa), the invoice is deemed accepted (Article 12(1)). Natural persons and entities under the income attribution regime (entidades en régimen de atribución de rentas) with a volume of operations of up to 8 million euros only have to submit status messages from 6 October 2029. The status data is used to monitor payment terms. The AEAT transmits it annually to the state monitoring body for late payment.

Formats

Permitted are invoices based on the semantic data model of EN 16931 in the UBL, CII, EDIFACT or Facturae syntaxes (Article 7 of Real Decreto 238/2026). For exchange via private platforms, messages in the Peppol BIS Billing format are also valid. The public solution of the AEAT processes UBL exclusively. Invoices issued via private platforms must carry an advanced electronic signature (Article 7(3)). For invoices via the public solution, a signature is possible but not required. Each invoice receives a unique code made up of the issuer’s tax number, the series and number of the invoice and the date of issue (Article 7(5)).

Transmission methods

Invoices are exchanged via private invoice exchange platforms or via the public solution of the AEAT (Solución Pública de Facturación Electrónica, SPFE). Under Article 13, private platforms must, among other things, be certified to ISO/IEC 27001 or equivalent, use AS2 or AS4, and employ advanced electronic signatures and seals. They must be able to exchange invoices in all permitted syntaxes and convert between them, and maintain a business continuity plan. If a customer requests a connection to another platform, the customer’s platform must establish it (Article 8). The requested platform must accept every request, make the connection operational within one month of receipt and may not charge any fees for it (Article 9). For every invoice not issued via the public solution, private platforms must simultaneously transmit a UBL copy to the SPFE.

Retention

Under Article 30 of the Código de Comercio, invoices must be retained for six years. For tax purposes, at least the four-year limitation period applies. E-invoices must be archived in their structured format, and signed invoices together with their signature.

Verifactu

Independently of the e-invoicing obligation, Real Decreto 1007/2023 sets out requirements for invoicing software. The software must chain every invoice record to the previous one (hash) and add a QR code to every invoice. The software can operate in two modes. In VERI*FACTU mode, it automatically transmits every invoice record to the AEAT, and the invoice bears the notice “VERI*FACTU” or “Factura verificable”. In the second mode, it signs the records electronically, stores them and makes them available to the AEAT on request. Software producers have had to meet the requirements since 29 July 2025. For users, under Real Decreto-ley 15/2025, the dates are 1 January 2027 for those subject to corporate income tax and 1 July 2027 for all others. On 5 October 2026, the Ministry of Finance announced that it would postpone the users’ obligations to October 2028. For companies with a volume of operations of up to 8 million euros, they would then coincide with the e-invoicing obligation. Until a legal provision on this is published, the 2027 dates apply.

E-invoicing in B2G

Obligation to issue

Since 15 January 2015, public limited companies, limited liability companies, joint ventures (UTE) and branches of foreign companies, among others, have had to submit invoices to public administrations electronically via the competent entry point (Article 4 of Ley 25/2013). Administrations can exempt invoices of up to 5,000 euros from the obligation.

Format

Invoices to administrations must be in the Facturae format, in versions 3.2, 3.2.1 or 3.2.2. Facturae is a national XML format with an XAdES signature. FACe converts invoices from foreign suppliers compliant with EN 16931 into Facturae.

Addressing

Every invoice to an administration must contain three codes from the DIR3 administrative directory, the Oficina contable (accounting office), the Órgano gestor (managing body) and the Unidad tramitadora (processing unit). The codes are given in the procurement documents or in the DIR3 directory. If a code is missing or incorrect, the invoice does not reach the competent invoice register.

Portals

FACe is the general entry point of the central administration. Regions and municipalities can operate their own entry points or be connected to FACe. FACeB2B is the register for invoices from subcontractors to main contractors under public contracts. These invoices must be migrated to the new B2B system within 24 months of the entry into force of Orden HAC/1028/2026.

Transmission

Invoices are submitted via the FACe web portal, the FACe web service or a connected invoicing program. The invoice must be signed before it is submitted.

What does this mean for you as a software provider?

For Spanish customers with a volume of operations of more than 8 million euros, your software must support issuing, transmitting, receiving and status messages by 6 October 2027, and for all others by 6 October 2028. It must already be able to generate invoices to public administrations in the Facturae format today, with the authority’s three DIR3 codes as mandatory fields in the customer master data.

The first product decision concerns the transmission method. Your software can act as a private platform itself and must then meet the requirements of Article 13, including ISO/IEC 27001 or an equivalent certification, conversion between all permitted syntaxes, the connection to other platforms and the UBL copy to the SPFE. Alternatively, it connects to a private platform or directly to the public solution of the AEAT. Connecting can be the shorter route if you do not want to take on certification and platform operation yourself.

Invoices via private platforms must carry an advanced electronic signature. Your software must then either generate this signature itself or connect to a signature service. If it connects to the public solution, no signature is required.

For incoming invoices, your software must be able to report acceptance, rejection and full payment with the date within four working days. For outgoing invoices, it makes sense to receive and display the recipients’ status messages, because dunning and payment reconciliation depend on them.

Invoicing software for the Spanish market must also meet the Verifactu requirements, regardless of the invoice format. As long as the dates for users may still be postponed, it makes sense to keep Verifactu and e-invoicing separately activatable in the product.

If your Spanish customers also issue invoices to business partners outside Spain, your software can transmit them via the Peppol network. To do so, you build your own Peppol Access Point or integrate a certified Access Point such as InvoiceRails. Your customers continue to work in your software and under your brand. The Peppol ID lookup shows whether a business partner is reachable via Peppol.

Outlook and special considerations

  • Verifactu and e-invoicing: The Ministry of Finance intends to merge the two regimes technically and in substance, also with a view to the reporting requirements under ViDA.
  • SII: Large companies with a volume of operations of more than 6,010,121.04 euros, participants in the monthly refund scheme (REDEME) and VAT groups have been reporting their invoice data within four working days via the Suministro Inmediato de Información since 2017. How SII and the UBL copy to the SPFE will interact in future has not yet been regulated.
  • Peppol: Businesses are registered in the Peppol network with their Spanish VAT identification number under scheme 9920.
  • ViDA outlook: From 1 July 2030, e-invoicing will be mandatory throughout the EU for cross-border B2B transactions, as decided by the Council of the EU.
  • Market figure: The statistics office INE counts around 3.31 million active companies in Spain as of 1 January 2025.

Frequently asked questions

Is Peppol mandatory in Spain?
No. What is mandatory is formats compliant with EN 16931 and exchange via private platforms or the public solution of the AEAT. Peppol BIS Billing is permitted as a format. The regulation does not specify whether platforms use the Peppol network to connect with each other.
Do our customers have to introduce Verifactu and e-invoicing at the same time?
Not under current law. Verifactu applies to users from 1 January or 1 July 2027, the e-invoicing obligation from 6 October 2027 or 2028. If the Ministry of Finance implements the announced postponement to October 2028, the two obligations will coincide for companies with a volume of operations of up to 8 million euros.
Is the public solution of the AEAT sufficient, or do our customers need a private platform?
The public solution is free of charge, processes only UBL, requires no signature and fulfils the statutory obligation. An invoice sent there may not contain embedded files. A private platform offers additional formats as well as the connection to other platforms and integrations. Which option fits depends on the invoice volume and on the formats used by the business partners.

Further reading

Factsheet

E-invoicing in France

Since 1 September 2026, France has been introducing mandatory B2B e-invoicing in two stages, with the obligation to send phased in by company size.

Still have questions?

Talk directly with the teams behind our products. No pitch deck and no unnecessary sales processes.