Skip to main content
This app is being retired. New integrations should use the Italy app, which reaches SDI through Invopop’s own accredited channel.

SDI Sending

View implementation guide ›

SDI Receiving

View implementation guide ›
The SDI (Sistema di Interscambio) is Italy’s central hub for transmitting, validating, and delivering all electronic invoices throughout the country. It is managed by the Italian tax authority (Agenzia delle Entrate).Electronic invoicing is mandatory for all businesses in Italy. The SDI system operates using a standardized XML format called FatturaPA, which ensures all invoices contain the required information and comply with the strict validation rules established by the Italian tax authority.Invopop simplifies SDI integration by allowing you to work with GOBL format instead of XML, providing synchronous validation before submission, and offering a simple API integration with automatic handling of SDI notifications and status updates. Invopop has partnered with A-Cube to provide SDI integration services.Key features
  • Workflow automation: This app provides automated workflows for sending and receiving invoices through the SDI system.
  • FatturaPA XML generation: Automatically converts GOBL documents into compliant FatturaPA XML format.
  • Real-time status updates: Automatically handles SDI notifications and status updates, including delivery confirmations and acceptance/rejection notifications.
  • Bidirectional support: Send invoices to SDI and receive invoices from suppliers through the same app.
  • Customer registration: Register companies to receive invoices through SDI with a simple workflow step.
  • GOBL FatturaPA integration: Uses the open-source GOBL FatturaPA library for conversions.
Make sure to check out our SDI Italy Sending Guide and SDI Italy Receiving Guide for instructions on how to issue and receive invoices.

FAQ

Invoicing questions
Install the Italy app for structured invoicing through SDI, or the Smart Receipts app for B2C-only AdE CF receipts. Run invoices through a workflow with the Send invoice to SDI step — see the issuing guide.
Retail receipts (documento commerciale, commonly called scontrino) are not SDI invoices — they are reported to the tax authority as corrispettivi through a separate channel. Use the Smart Receipts Italy app for those, and see the Smart Receipts issuing guide.
See the Italy tax regime in GOBL for tax categories, codice fiscale rules, and SDI-specific extensions. The it-sdi-v1 addon documents required FatturaPA fields.
The Send invoice to SDI step completes as soon as SDI accepts the file — it doesn’t wait for SDI’s verdict. What takes time is SDI’s own processing: a rejection usually arrives within minutes, but delivery confirmations can take up to 5 days. Each verdict is recorded against the invoice as a status entry, so nothing is stuck while you wait. See the status guide for the full lifecycle.
SDI confirms delivery with an RC (ricevuta di consegna) notification, recorded on the invoice as a status entry with the GOBL status acknowledged. A rejection arrives as NS with status error. Every notification and what it means is covered in the status guide.
Set a reserved codice destinatario on the customer — for example SIMNS00 to simulate a rejection. The sandbox simulates SDI end to end and feeds back the notifications a real exchange would produce; any ordinary code resolves to a successful delivery. The full list of reserved codes is in the issuing guide.
Invopop handles both Italian tax identification numbers in the supplier and customer sections of invoices:
  • Partita IVA (VAT number): Automatically extracted from the tax_id/code field.
  • Codice Fiscale (fiscal code): Must be specified as an identity with the key it-fiscal-code.
Here’s an example showing both identifiers in a supplier object:
Supplier with Partita IVA and Codice Fiscale
Registering supplier questions
Provide the supplier’s Partita IVA and Codice Fiscale (where different) in their party configuration. No certificate upload is needed — Invopop transmits to SDI over its own accredited channel.
No supplier certificates are required. Invopop exchanges documents with SDI over its own accredited channel; only the Partita IVA and routing metadata are stored.
You don’t need to. SDI has no supplier registration for sending: set the supplier’s Partita IVA on the party and send. Registration is only needed for receiving — see the receiving invoices guide.
None — Invopop exchanges documents with SDI over its own accredited channel, so suppliers don’t manage any certificates. The one exception is invoices to public administrations (FPA12), which require a qualified electronic signature and are not yet supported.
Receiving questions
Register Invopop’s recipient code (BDCS3JD) with the tax authority and run the registration workflow on the company’s party entry. Invopop automatically receives matching invoices and routes them through the configured import workflow. See the receiving invoices guide.
Inbound FatturaPA XMLs are parsed via gobl.fatturapa. The original signed XML is preserved as a silo entry attachment alongside the GOBL representation.
Register the company for reception in your sandbox workspace, then send a sandbox invoice addressed to it — the app loops it back to you as an inbound delivery and runs your import workflow, exactly as a real delivery would. This is the only way to receive an invoice in sandbox: there is no tax authority to register with, and no real supplier can reach it. See receiving your own invoices.
The import step attempts to convert the FatturaPA document into GOBL. If conversion fails, the step returns KO, but the original file stays stored — the invoice can be re-processed later without SDI needing to redeliver it.If the invoice has significant structural issues that prevent conversion, you may need to contact the sender to request a corrected invoice.
Invoices are typically received within minutes after being sent by suppliers through SDI. The automatic import process in Invopop processes them as soon as they are received by our system.
Yes, multiple companies can be registered to receive invoices through a single Invopop workspace. For each company, you must:
  1. Register the recipient code BDCS3JD with the Italian tax authority for that specific company
  2. Have its tax ID registered by running the registration workflow on the company’s party entry
  3. Use the same import workflow configured in the app settings
This two-step registration process (with the tax authority and with Invopop) must be completed for each company you want to register. This is particularly useful for white-labeling scenarios where a user manages multiple entities.
Yes, but only one party at a time can hold a given tax ID. Run the unregister workflow on the party that currently holds it, then register the new one.Registering a tax ID that another party already holds fails with a clear error.Sandbox and live are counted separately, so the same tax ID can be registered in both at the same time.
The two-step registration process serves different purposes:
  1. Registering with the Italian tax authority - Tells SDI to route invoices addressed to your company to Invopop’s channel using the Codice Destinatario BDCS3JD.
  2. Registering with Invopop (the registration workflow) - Tells Invopop which invoices to accept and process for your workspace.
Both steps are necessary: the first routes the invoices to Invopop, and the second ensures Invopop knows which workspace should receive those invoices.
Signed FatturaPA XML (versions 1.2.x), conforming to the Agenzia delle Entrate schema. The original file is kept attached to the entry exactly as SDI delivered it, alongside SDI’s delivery metadata.
More answers in our Italy FAQ section


Participate in our community

Ask and answer questions about SDI Italy App →