Guide
E-Invoicing in Italy
Key formats, routing options, and a practical checklist for sending compliant e-invoices in Italy.
What matters in practice
This Italy guide covers FatturaPA XML, SdI routing, Codice Destinatario or PEC delivery, and the validation checks that matter most before submission.
This article treats E-Invoicing in Italy as a practical reference, not just a navigation page. It explains the term or workflow in context, shows why it matters for European e-invoicing, and connects the topic to invoice creation, validation, routing, archiving, and ERP implementation decisions.
Common e-invoice formats
Common e-invoice formats is where the general explanation of E-Invoicing in Italy becomes operational. The section focuses on FatturaPA XML, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- FatturaPA XML
Routing & delivery
Routing & delivery connects E-Invoicing in Italy with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding Sistema di Interscambio (SdI) to validating or converting the invoice file.
Common identifiers
Common identifiers is where the general explanation of E-Invoicing in Italy becomes operational. The section focuses on Codice Destinatario / PEC and VAT ID, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Codice Destinatario / PEC
- VAT ID
Mandate & scope
Italy is known for a clearance-style approach where invoices are routed through the SdI platform (FatturaPA XML).
Mandate & scope
Mandate & scope is where the general explanation of E-Invoicing in Italy becomes operational. The section focuses on Format: FatturaPA XML is the common format for platform routing, Routing: Codice Destinatario or PEC is used to deliver invoices to the recipient and Compliance: ensure totals, VAT breakdown, and identifiers match platform rules, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Format: FatturaPA XML is the common format for platform routing.
- Routing: Codice Destinatario or PEC is used to deliver invoices to the recipient.
- Compliance: ensure totals, VAT breakdown, and identifiers match platform rules.
How to send (practical steps)
How to send (practical steps) is where the general explanation of E-Invoicing in Italy becomes operational. The section focuses on Confirm whether the recipient expects Codice Destinatario or PEC and collect the correct value, Generate the required XML format and validate against platform/business rules and Submit via the SdI process (portal/API/provider) and track the platform status/acknowledgements, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Confirm whether the recipient expects Codice Destinatario or PEC and collect the correct value.
- Generate the required XML format and validate against platform/business rules.
- Submit via the SdI process (portal/API/provider) and track the platform status/acknowledgements.
- Store delivery receipts and outcomes for audit and dispute handling.
Validation & compliance
Validation & compliance is where the general explanation of E-Invoicing in Italy becomes operational. The section focuses on Keep recipient routing identifiers accurate (wrong codes commonly lead to non-delivery), Ensure VAT calculations and totals are consistent across lines and summaries and Avoid free-text identifiers where the platform expects structured codes, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Keep recipient routing identifiers accurate (wrong codes commonly lead to non-delivery).
- Ensure VAT calculations and totals are consistent across lines and summaries.
- Avoid free-text identifiers where the platform expects structured codes.
Common pitfalls
Common pitfalls is where the general explanation of E-Invoicing in Italy becomes operational. The section focuses on Wrong Codice Destinatario/PEC leading to routing failures, VAT and rounding inconsistencies causing rejections and Missing mandatory identifiers for seller/buyer or taxable status, so it can be used to check the required fields, process decisions, and validation controls before the invoice workflow is used in production.
- Wrong Codice Destinatario/PEC leading to routing failures.
- VAT and rounding inconsistencies causing rejections.
- Missing mandatory identifiers for seller/buyer or taxable status.
Frequently asked questions
Frequently asked questions answers the practical questions that usually appear after reading the main explanation of E-Invoicing in Italy. The answers focus on What invoice format is used in Italy and What causes the most problems with Italian invoices and are written to clarify implementation choices quickly.
What invoice format is used in Italy?
Italy commonly uses FatturaPA XML for SdI routing, so the structured XML must match the recipient’s delivery details.
What causes the most problems with Italian invoices?
Routing identifiers, VAT consistency, and missing mandatory party data are the most common reasons for rejection or non-delivery.
Official links
Official links connects E-Invoicing in Italy with the next useful reference pages and tools. These links are included to support a complete workflow, from understanding FatturaPA / SdI to validating or converting the invoice file.