Invoice Requirements in Italy: Legal Rules for 2026

Italy is distinctive because B2B and most B2C domestic flows typically require electronic invoicing through the Sistema di Interscambio (SDI) in XML formats—not optional PDFs for many traders. IVA treatment, split payment in public-sector-like cases, and withholding (ritenuta) lines make Italian invoices dense compared with simpler VAT regimes. This overview targets 2026 practice for mainstream resident suppliers; it is not legal advice. Validate intra-EU, export, agricultural, and special sectors with your commercialista. Public administration (PA) customers often require CIG/CUP and split payment mechanics that consumer templates omit—map procurement data before you automate sends.

Required fields

Electronic invoices carry structured fields including supplier and customer identifiers (including Codice Fiscale / Partita IVA as applicable), document type, number and date, payment terms, line descriptions, taxable amounts, IVA rates (for example 22%, 10%, 5%, 4%, or Natura codes for exempt lines), withholdings where due, and totals. Cross-references to orders, contracts, or CIG/CUP may be required for public administration customers. Credit notes use defined document types and must chain to the original fattura.

Tax rules (VAT/GST/sales tax rates)

The ordinary IVA rate is 22%. Reduced rates apply to enumerated categories; zero-rated exports and qualifying intra-EU supplies depend on evidence and VIES-consistent VAT IDs. Exempt supplies use Natura codes rather than headline rates. Reverse charge and split payment scenarios must be declared consistently in XML and VAT ledgers.

Language requirements

Italian is the operational norm—SDI XML descriptions are typically Italian, and tax codes assume Italian semantics. English summaries may appear for foreign parents but should not contradict coded tax lines.

Digital invoicing rules

Certified invoicing software or service providers submit FatturaPA / FPR XML to SDI, which returns delivery outcomes you should archive. PDF copies are secondary to XML for legal evidence in many audits. Retention expectations are long—treat SDI metadata as part of your record bundle. Certified software updates can change XML schemas—schedule regression tests whenever your provider ships mandatory upgrades. Archive SDI receipt ACKs beside customer PDFs so disputes about delivery timestamps close quickly.

Penalties

Agenzia delle Entrate may levy sanctions for late or invalid e-invoices, mismatched VAT, and incorrect XML. Customers may reject payments when SDI status is not accepted, creating cash-flow risk beyond pure tax fines. Ritenuta lines that drift from contract withholding percentages trigger double corrections—sync legal and finance before month-end closes.

Finance and IT should co-own the SDI integration runbook: who monitors schema upgrades, who tests credit notes, and who archives delivery acknowledgements. Public tender teams must inject CIG/CUP and split-payment data before automation goes live—retrofitting XML after award notices arrive delays cash. Quarterly reconciliation of Partita IVA master data against Agenzia registers prevents drift that only surfaces when buyers lose deductions.

Maintain a living data dictionary that maps each product SKU to SDI tax codes and Natura values so new catalogue launches do not require emergency weekend fixes. When auditors request samples, produce XML plus buyer acceptance receipts in one zipped bundle—partial responses extend review timelines. Finally, calendar an annual review of withholding and split-payment obligations whenever public-tender volumes exceed internal thresholds.

Template link

Use our Italian invoice template to align human-readable layouts with SDI-style data you will still need in XML. Read the invoice tax compliance guide and tax rate lookup tool. Official references include Agenzia delle Entrate and Electronic invoicing. Join InvoiceQuickly early access to coordinate Italian e-invoicing with your global billing.