Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français

Agenzia Entrate: New Rules on E-Invoice Data Use in 2026

Italy formalizes how e-invoice aggregates are used for tax collection targeting. Practical implications for ERP data quality, controls, and finance-IT governance.

Agenzia Entrate: New Rules on E-Invoice Data Use in 2026

Italy has moved into a new phase of fiscal use of electronic invoicing data. Through provision no. 153611/2026, signed on May 22, 2026, Agenzia delle Entrate defines how aggregated invoicing data can be shared with Agenzia delle Entrate-Riscossione to support selected debt-collection procedures (provision 153611/2026).

In concrete terms, the framework uses two indicators over the previous six months: total consideration amounts and invoice counts, calculated by debtor and co-obligated parties against the same counterparty (provision 153611/2026).

The legal basis was established earlier. The new provision operationalizes the change introduced by Italy’s 2026 Budget Law (Law no. 199 of December 30, 2025), which expanded the permitted use of e-invoice data (provision 153611/2026).

The text also confirms a practical implementation timeline. In its rationale, it references the requirement to publish this implementation act within 90 days after the law entered into force (provision 153611/2026).

For IT and finance leaders, this shifts the topic from policy debate to operational reality. It is no longer only about issuing compliant e-invoices, but about governing secondary uses of ERP-generated transaction data.

Business impact: what changes for CIOs and CFOs

First, data quality becomes an indirect collection-risk issue. The mechanism relies on billing aggregates (amounts and volumes). Structural errors in outbound flows, counterparty classification, or VAT mappings can create a distorted activity profile.

Second, traceability requirements become stricter. The provision describes an initial “as is” phase using PEC transmission with password-protected files, followed by a target automated “to be” service (provision 153611/2026). For IT teams, this means stronger control over exports, technical logs, and audit trails across ERP and middleware.

Third, the boundary between tax compliance and customer-supplier risk management is narrowing. Finance teams should plan for aggregated invoicing data to be used in analyses that can trigger executive collection actions involving third parties. In practice, master-data discipline (counterparties, co-obligated entities, and relationship history) becomes an operational protection asset.

What to monitor now

In the short term, three points require close monitoring.

  1. The transition from the current secure but non-industrialized exchange model to the automated “to be” service described by the administration (provision 153611/2026).
  2. The practical criteria for selecting positions to be flagged, as the text references proportionality and territorially phased rollout (provision 153611/2026).
  3. Internal CFO-CIO decisions on how much additional control to apply to outbound e-invoice flows before SdI submission.

For Italian SMBs and mid-market firms, the strategic takeaway is not “more reporting.” It is stronger source-data reliability inside ERP workflows, so imperfect data does not become downstream enforcement risk.

To go deeper, read our mandatory e-invoicing in Europe guide, our analysis of Italy’s Fatturazione Elettronica v1.9.1 changes and our breakdown of Italian ERP vendors focused on fiscal compliance.