Italian invoicing law makes the Sistema di Interscambio (SdI) mandatory: every fattura elettronica must be produced as a schema-valid FatturaPA XML, routed to the Agenzia delle Entrate exchange platform, and reconciled against the notifiche (RC, MC, NS, NE, DT) that SdI sends back. Out of the box, Odoo's core Invoicing does not speak FatturaPA end to end, and generic apps.odoo.com connectors rarely cover the full B2G, B2C and cross-border picture your commercialista signs off on.

This is a BUILD-TO-ORDER Odoo module. It is not an existing instant download — ECOSIRE designs, builds, installs and supports it against your exact Piano dei Conti, VAT setup and SdI channel over a typical one working week lead time, on Odoo 17, 18 or 19 (Community or Enterprise).

The module extends account.move with a compliant FatturaPA layer. A dedicated builder maps every mandatory block — CedentePrestatore, CessarioCommittente, DatiGeneraliDocumento, DettaglioLinee, DatiRiepilogo, DatiPagamento — into the correct FatturaPA 1.2.x XML, driven by Odoo fields, taxes and partner data. Computed fields with @api.depends keep the XML in sync with the invoice, while an XSD/business-rules validator blocks non-conformant documents before they ever reach SdI so you avoid the dreaded "Scarto" (NS) rejection.

Transmission is handled through your chosen channel — a certified intermediary/provider, PEC, or the SdI web service — with the correct TipoDocumento (TD01, TD24, TD16-19 reverse charge, etc.), FormatoTrasmissione (FPR12 for private, FPA12 for public administration) and Codice Destinatario or PEC routing resolved per customer. Inbound and status notifiche are parsed and written back onto the invoice via automated actions, so accounting always sees the live SdI lifecycle: sent, delivered, accepted, rejected or "mancata consegna". Digital signature (CAdES .p7m) is supported for B2G flows that require it, and self-billing / integration documents plus Esterometro (cross-border, now folded into SdI via TD17/TD18/TD19) are covered so foreign purchases and sales are reported correctly.

Security follows Odoo conventions — ir.model.access.csv grants plus record rules keep FatturaPA data scoped to the right accounting roles and companies in a multi-company database. QWeb-rendered human-readable copies, a searchable SdI log, and clean XML-RPC/JSON-RPC access mean the same compliant flow works from the UI, from scheduled jobs, and from any upstream system you integrate. You get a documented, upgrade-friendly module — not a fragile one-off — plus training and a support window after go-live.