SDI compliance checklist Italy: e-invoicing success

Italy's SDI (Sistema di Interscambio) has been mandatory since 2019 for all VAT-registered businesses, covering B2B, B2C, and B2G invoicing. Unlike post-audit systems, SDI validates every invoice in real-time before delivery, meaning errors don't surface weeks later; they halt transactions immediately.

For financial and compliance teams managing e-invoicing platforms, billing software, or ERP systems in Italy, that risk is not abstract. It is a daily operational reality. This article gives you a practical, expert-level checklist to keep your SDI process clean, your invoices accepted, and your team ahead of every regulatory update.

Understanding SDI compliance: What and why

SDI is the Italian government's centralized hub that every e-invoice must pass through before it reaches the recipient.

B2B e-invoicing in Italy is governed by this system, and the rules apply to virtually every VAT-registered entity operating in the country. When you submit an invoice, SDI validates the FatturaPA XML format, verifies VAT numbers are correct and active, routes the invoice to the recipient via their Codice Destinatario or PEC address, and returns a receipt confirming delivery or rejection.

Real-time reporting in Italy is directly tied to this process. But SDI does more than route invoices. It feeds tax data to the Agenzia delle Entrate in near real-time. Every error in your invoice becomes an error in your tax record. Rejected invoices delay cash flow, trigger audit flags, and in serious cases, result in administrative penalties.

Step-by-step SDI compliance checklist for e-invoicing

This checklist is built for teams who need to verify, fix, or upgrade their SDI invoicing process. Work through it sequentially.

1. Verify VAT registration and fiscal codes. Confirm your Partita IVA and Codice Fiscale are active and correctly registered with the Italian tax authority before you issue a single invoice.
2. Use FatturaPA XML version 1.9. Invoices must use the correct FatturaPA XML format, be fully populated, and transmitted through approved SDI channels. Outdated versions will be rejected.
3. Include all mandatory fields. Every invoice needs a unique sequential number, issue date, VAT amounts, taxable totals, and the recipient’s Codice Destinatario or PEC address.
4. Choose your transmission method. You can send via PEC (certified email), the Agenzia delle Entrate web portal, or a certified intermediary software. Respect file size limits: 5MB for XML files, 30MB for PEC transmissions.
5. Apply digital signatures where required. For B2G invoices, a qualified digital signature is mandatory. For B2B, it is optional but strongly recommended for audit integrity.
6. Log all SDI acknowledgments. Every transmission returns a receipt. Store these systematically. They are your proof of delivery and your first line of defence in any tax audit.
7. Automate with a certified invoicing API for SaaS. Manual processes introduce human error. Purpose-built APIs handle formatting, transmission, and acknowledgment logging automatically.
8. Monitor regulatory updates. SDI rules evolve. Recent changes like TD29 and TD17 document type updates have caught many teams off guard. Use ERP automation for SDI to stay current without manual tracking.

Integrating SDI into your software: Tools and compatibility

Once your checklist is in place, the next challenge is making your software do the work reliably.

The first step is deciding how to connect to SDI. You can transmit directly via PEC-certified email, through the Agenzia delle Entrate web portal, or by working with a certified intermediary authorized service provider like software platforms or PEPPOL Access Points. 

For API-based ERP integration, the core setup involves three steps: registering your company data (Partita IVA, Codice Fiscale, tax regime code), mapping your invoice workflow to FatturaPA XML fields, and establishing a secure, authenticated connection to the SDI gateway.

Here is a quick comparison of integration approaches across common platforms:

For teams managing compliance risks across multiple clients, an embedded API approach is almost always faster and more reliable than building native SDI logic from scratch.

SDI compliance challenges and troubleshooting tips

Even well-configured systems hit problems. Knowing the most common failure points in advance saves hours of troubleshooting and prevents payment delays.

Here are the most frequent SDI compliance failures teams encounter:

• Incorrect or missing Codice Destinatario: The invoice cannot be routed without a valid 7-character code or PEC address
• Wrong document type code: Using TD01 (standard invoice) when TD17 (self-billing for services from abroad) is required
• Date mismatches: Invoice date outside the accepted transmission window
• Unsupported XML version: Submitting FatturaPA 1.2 when 1.9 is required
• Invalid VAT number format: Even a single digit error causes immediate rejection

Here is how the old and new requirements compare for two key document types:

For troubleshooting SDI rejection messages, start with the error code in the ricevuta di scarto (rejection receipt). SDI returns specific codes that map to exact field errors. Fix the field, regenerate the XML, and retransmit. Do not just resubmit the same file.

Why a proactive compliance culture beats checklists alone

Here's an uncomfortable truth: a checklist is only as good as the team that uses it. We've seen companies with perfect documentation still getting invoices rejected months after Italy's April 2025 version 1.9 update because nobody owned the process of staying current.

The companies that handle SDI well build operating rhythms around compliance. They set up automated alerts for Agenzia delle Entrate specification updates. They run weekly SDI acknowledgement reviews to spot rejection patterns before they become systemic. They train teams to interpret error codes like "00404 - VAT number not found" without escalating every incident.

Most importantly, they choose technology partners who absorb regulatory changes on their behalf. When Italy updates validation logic or introduces new document types, their systems stay compliant without emergency engineering sprints. The checklist gets you started. The culture keeps you compliant.

Streamline SDI invoicing with smarter solutions

Managing SDI compliance manually across multiple clients, ERP systems, or markets is a significant operational burden. Purpose-built API changes that equation entirely.

For software companies serving Italian clients, DDD Invoices provides a unified API that covers Italy's SDI alongside other European e-invoicing mandates through a single integration.

This eliminates the need to build and maintain separate connections for each jurisdiction, letting your engineering team focus on core product features rather than compliance overhead. For platforms looking to go further, our guide on monetizing e-invoicing compliance shows how to turn compliance features into a revenue driver, not just a cost center.

FAQs

Which documents must go through the SDI platform in Italy?

All VAT-registered businesses must send B2B, B2C, and B2G invoices through SDI using the FatturaPA XML format. There are no exceptions for domestic transactions between Italian VAT entities.

What is the role of digital signatures in SDI compliance?

Digital signature is required for B2G invoices and optional for B2B, but applying it to all invoices adds a layer of legal integrity and simplifies audit responses.

How do I resolve SDI invoice rejection errors due to XML mistakes?

Read the rejection receipt code first, then fix the specific field flagged. Recent FatturaPA updates affect XML mapping, so always validate against the current 1.9 schema before retransmitting.

Which software options help streamline SDI compliance?

Certified platforms and ERP connectors automate XML generation, transmission, and acknowledgment tracking, giving your team a reliable audit trail without manual intervention.