E‑invoicing Requirements in Italy, Fatturapa V1.9.1 (may 15, 2026 Deadline)

Last updated: 31 May 2026

The e‑invoicing requirements Italy 2026 deadline that every business operating in the country must now act on arrived with the Agenzia delle Entrate’s publication of FatturaPA Technical Specifications v1. 9. 1 on 31 March 2026, with mandatory adoption from 15 May 2026. Italy’s Sistema di Interscambio (SDI) clearance model, already one of the most mature mandatory e‑invoicing regimes in the world, now enforces updated XML element values, tighter validation rules and refreshed code lists that will cause automatic rejections of non‑compliant invoices.

This guide sets out the precise legal obligations, the technical changes finance and IT teams need to implement, the 12‑day transmission window, the 10‑year archival requirement under conservazione sostitutiva, and the penalties for non‑compliance, giving compliance managers, CFOs and external accountants a single, authoritative playbook.

Is E‑Invoicing Mandatory in Italy? Background and Legal Basis

What Is SDI and How Does It Route Invoices?

Italy operates a clearance model for electronic invoicing. Every invoice, whether B2B or, in most cases, B2C, must pass through the SDI Italy portal before it reaches the recipient. The SDI performs real‑time validation of the XML file against the current FatturaPA technical specification, checks the digital signature or qualified seal, and routes the document to the buyer through the registered delivery channel. If the file fails any validation control, the SDI issues a rejection notification (notifica di scarto) and the invoice is legally considered as never issued. This clearance architecture means that compliance is not optional: an invoice that bypasses SDI has no legal effect for VAT purposes.

Legal Bases, Statutes and EN 16931 Alignment

The obligation to issue electronic invoices through SDI was introduced by Budget Law 2018 (Law No. 205/2017, Art. 1, paragraphs 909–928) and extended to all domestic B2B and B2C transactions from 1 January 2019. Italy also aligns with the European standard EN 16931 for public‑procurement invoicing, as documented by the European Commission’s Digital Building Blocks programme. The Italy e‑invoice XML format, known as FatturaPA, is the national implementation of these requirements. Italy invoice requirements therefore sit at the intersection of domestic tax law and EU harmonisation, making ongoing specification updates legally binding for every taxable person established or VAT‑registered in the country.

What FatturaPA v1.9.1 Changes, Technical and Legal Summary

Summary Table of Key XML Field Changes and New Codes

The FatturaPA 1.9.1 specification, published by the Agenzia delle Entrate on 31 March 2026 and mandatory from 15 May 2026, introduces a set of targeted adjustments to XML element values, code lists and validation logic. The table below summarises the most operationally significant changes that finance and IT teams must address.

New Validations That Will Cause SDI Rejections

Industry observers expect three categories of rejection to spike immediately after the 15 May 2026 cut‑over. First, invoices referencing deprecated TipoDocumento or Natura sub‑codes will be blocked outright. Second, the tighter CodiceDestinatario validation means that any recipient code that has been deactivated or is incorrectly formatted will trigger a notifica di scarto. Third, invoices bearing an outdated schema version attribute, even if the underlying data is correct, will fail the initial format check. Finance teams should treat the 15 May 2026 date as a hard cut‑off: SDI will not provide a grace period for files that do not conform to the new specification.

Who Must Adopt the New Spec and by When

Every entity that is required to issue FatturaPA must comply with v1.9.1 from 15 May 2026. This includes resident businesses, VAT‑registered non‑residents, public administrations and any intermediary that issues invoices on behalf of a taxable person. There is no opt‑in mechanism: the SDI will begin enforcing the new validations automatically on the mandatory date.

E‑Invoicing Requirements Italy 2026 Deadline, Practical Compliance Checklist

Step 1, Update XML Templates and Mapping

Begin by downloading the official FatturaPA v1.9.1 schema (XSD) from the Agenzia delle Entrate technical specifications page. Compare every code list, TipoDocumento, Natura, ModalitaPagamento and RegimeFiscale, against the values currently hard‑coded in your ERP or invoicing software. Replace deprecated codes, add any new values required for your transaction types, and update the schema‑version namespace in the XML header. If you use a third‑party invoicing provider, request written confirmation that their platform has been updated to generate v1.9.1‑compliant files and ask for a test invoice to validate locally.

Step 2, Test Against SDI and Fix Common Rejection Codes

The Agenzia delle Entrate provides a test environment (the canale di test) where businesses can submit sample invoices and receive validation feedback. Submit at least one test invoice for each TipoDocumento you regularly use. Pay particular attention to the following common rejection scenarios:

• Error 00305, Invalid CodiceDestinatario. Verify all stored recipient codes against the SDI registry and update any that have been deactivated.
• Error 00200, Schema validation failure. Ensure the XML namespace and version attribute reference v1.9.1 exactly.
• Error 00400, Invalid Natura code. Cross‑reference your VAT nature code mapping with the updated sub‑code list.
• Signature errors. Confirm that your digital certificate uses an algorithm profile accepted under the new spec.

Document every test result. Auditors may request evidence that pre‑go‑live testing was performed.

Step 3, Update Transmission Procedures and SLAs (12‑Day Flow)

Review your internal service‑level agreements for invoice issuance to ensure they align with the statutory transmission windows. Under current Italy invoice requirements, an invoice must generally be issued (i.e. transmitted to SDI) by the 12th day following the date the transaction took place. Confirm that your workflow, from goods delivery or service completion through to SDI submission, can consistently meet this window. Update any automated scheduling rules and alert thresholds. If you rely on intermediaries for SDI transmission, confirm their SLA covers same‑day or next‑business‑day forwarding so that the 12‑day limit is not breached by processing delays.

Transmission Timing, Receipt and Correction Rules

Transmission Workflow and SDI Response Codes

Once an invoice file is submitted, the SDI processes it through a multi‑stage validation pipeline. If the file passes, the SDI delivers it to the recipient and returns a delivery receipt (ricevuta di consegna) to the sender. If the recipient’s channel is unreachable, the SDI places the invoice in the recipient’s reserved area (area riservata) on the Agenzia delle Entrate portal and notifies the sender via a mancata consegna (non‑delivery) notification. The invoice is still legally issued at the point SDI accepts it, delivery failure to the buyer does not invalidate the invoice for VAT purposes, but the sender must retain the non‑delivery notification as proof.

Time Limits for Issuing, Cancelling or Correcting Invoices

The general rule is that an immediate invoice (fattura immediata) must be transmitted to SDI within 12 days of the taxable event. A deferred invoice (fattura differita) may be issued by the 15th day of the month following the month in which the goods were delivered or services rendered, provided that supporting documentation (e.g. a transport document or DDT) exists. If an invoice is rejected by SDI, the issuer has five days from the date of the rejection notification to correct and re‑submit it; the corrected invoice is treated as timely if re‑submitted within this window.

Consolidated Invoicing Rules

Businesses that make multiple supplies to the same customer within a calendar month may issue a single consolidated deferred invoice (fattura differita riepilogativa) by the 15th of the following month. Each line item must reference the relevant transport document or delivery note. Where statutory ambiguity exists regarding specific timing windows, for example, certain sector‑specific rules referencing seven‑day intervals, businesses should consult the Agenzia delle Entrate’s published guidance and, where necessary, seek a formal interpello ruling.

SDI Routing, PEC vs Codice Destinatario

Recipient Code (Codice Destinatario) Explained

The Codice Destinatario is a seven‑character alphanumeric code registered by the invoice recipient (or their intermediary) with the SDI. It identifies the specific electronic channel, typically a web‑service endpoint, to which the SDI should deliver the invoice. Every registered channel has a unique code, and a business may register more than one. Suppliers must include the correct Codice Destinatario in the XML’s CodiceDestinatario element. If no code is available, the field should be populated with 0000000 (seven zeroes) and the recipient’s PEC address must be specified instead.

PEC (Certified Email) vs Codice Destinatario, When to Use Which

For B2B transactions, the Codice Destinatario is the preferred and more reliable channel because it supports automated machine‑to‑machine processing. PEC delivery, by contrast, delivers the XML file as an email attachment, requiring the recipient to download and import it manually. PEC is typically used only when the recipient has not registered an SDI channel or when the supplier does not have the recipient’s Codice Destinatario. For B2C invoices to consumers without a registered channel, the default code 0000000 is used and the invoice is deposited in the consumer’s reserved area on the Agenzia delle Entrate portal.

How to Obtain or Update Codes and Common Mapping Errors

Businesses register or update their Codice Destinatario through the Agenzia delle Entrate’s online services portal (Fatture e Corrispettivi). The most common mapping errors include using a deactivated code, transposing characters, and failing to update the code after switching intermediary providers. The table below outlines the main routing channels and associated risks.

Archiving and Conservazione Sostitutiva, 10‑Year Retention

Legal Retention Requirement and Accepted Methods

Italian law requires that all e‑invoices, both issued and received, be preserved for a minimum of 10 years through a legally compliant digital archiving process known as conservazione sostitutiva. This process must guarantee the authenticity, integrity, legibility and retrievability of each invoice for the entire retention period. Acceptable preservation methods include those that apply a qualified electronic time stamp and maintain an archive index (indice di conservazione) in accordance with the AgID (Agenzia per l’Italia Digitale) technical rules. Paper printouts alone do not satisfy the requirement; the XML file itself must be preserved in its original digital format.

Agenzia delle Entrate Free Archiving vs Third‑Party Providers

The Agenzia delle Entrate offers a free conservation service through its Fatture e Corrispettivi portal. Businesses that opt in delegate the 10‑year preservation obligation to the AdE, which stores invoices on government infrastructure at no charge. Alternatively, businesses may engage an accredited third‑party conservator (conservatore accreditato). When using a third party, the business must execute a formal delegation agreement and verify that the provider complies with AgID standards. Industry observers note that the AdE service is increasingly popular among small and medium enterprises, while larger organisations with complex audit and retrieval requirements tend to prefer dedicated third‑party solutions that integrate with their document management systems.

Practical Steps to Validate Archival Compliance

Confirm that your chosen archiving method, whether the AdE free service or a third‑party conservator, covers all invoice types generated under v1.9.1. Request a written attestation of compliance from your provider and verify that metadata tagging (including the IdFiscaleIVA, invoice date and progressive number) is correct. Conduct an annual spot check of archived files to ensure they remain retrievable and intact.

Penalties, Audits and Remediation Strategies

Failure to issue an e‑invoice, or issuing one that does not comply with the applicable technical specification, can expose businesses to administrative penalties. Under Italian tax law, penalties for omitted or late invoicing generally range from 5% to 10% of the VAT amount, with minimum thresholds applying even where no tax loss occurs. Where the failure does not affect the VAT settlement (e.g. the tax was correctly reported in the periodic return), reduced penalties may apply.

In the event of a VAT audit, the Agenzia delle Entrate will verify not only that invoices were issued and transmitted through SDI, but also that they conform to the technical specification in force at the time of issuance. Businesses should therefore maintain a complete audit trail, including SDI delivery receipts, rejection notifications, and re‑submission logs. Where an error is discovered before an audit, the voluntary correction mechanism (ravvedimento operoso) allows the taxpayer to rectify the position and pay a reduced penalty, provided the correction is made before the tax authority initiates a formal inspection.

Quick Reference, FatturaPA v1.9.1 at a Glance

Reporting Obligations by Entity Type

Appendix, Sample FatturaPA XML Snippet and Common SDI Rejection Codes

Sample XML Header (v1.9.1 Schema Reference)

The following abbreviated XML snippet illustrates the correct namespace and schema‑version declaration for a v1.9.1 compliant invoice. Businesses should verify that their invoicing software generates this header structure automatically.

   A1B2C3D    
 Common SDI Rejection Codes (Non‑Exhaustive) Error Code Description Typical Cause / Fix 00200 File does not conform to XSD schema Schema namespace or version attribute not updated to v1. 9. 1, update the XML header 00305 Invalid or unknown CodiceDestinatario Recipient code deactivated or mistyped, verify against AdE registry and update customer master data 00400 Invalid Natura code value Deprecated sub‑code used, map to the correct v1. 9.
1 Natura sub‑code 00403 Invalid TipoDocumento code Removed or restricted document‑type code, replace with the updated equivalent 00404 Invalid ModalitaPagamento code Obsolete payment method code used, update to the new code list values Businesses preparing for the e‑invoicing requirements Italy 2026 deadline should treat the 15 May 2026 FatturaPA v1. 9. 1 cut‑over as a firm compliance milestone, not a soft target.  Updating XML templates, validating SDI routing codes and confirming 10‑year archival arrangements now will prevent rejected invoices, interrupted cash flow and potential penalty exposure.  Where recent Italian regulatory changes intersect with broader tax obligations, businesses are encouraged to seek specialist Italian tax advice through the Global Law Experts lawyer directory.


Need Legal Advice?
This article was produced by Global Law Experts. For specialist advice on this topic, contact Paolo Pizzocri at Paolo Pizzocri Studio Legale, a member of the Global Law Experts network.


Sources

VATupdate, Italy Updates E‑Invoicing Specs: New Format Mandatory from May 15, 2026
Fiscal‑Requirements, FatturaPA v1.9.1 News
Invoice Navigator, Italy Country Rules
Invoice Navigator, FatturaPA Explained
European Commission, eInvoicing in Italy
eu‑einvoicing.com, Agenzia delle Entrate Conservazione Sostitutiva Rules Update 2026
The Invoicing Hub, New Technical Specifications and ViDA Impact in Italy
CSV2Invoice, Italy FatturaPA E‑Invoicing Compliance