The Italian reporting calendar for a payment firm

Italy asks for more separate AML data returns than any other market in this cluster — four, to one intelligence unit, on four different triggers. That is the defining feature of the Italian calendar and the thing that most surprises firms arriving from a market where AML reporting means suspicion reporting and nothing else. Add the prudential layer, the tax archive and the conduct cycle, and the Italian reporting inventory is long but highly structured.

1. Four counterparties

2. The four AML obligations

These run in parallel and have genuinely different triggers, which is why treating “Italian AML reporting” as one workstream fails:

3. The rest of the inventory

• Segnalazioni di vigilanza — the supervisory and financial returns to Banca d’Italia, built on the Matrice dei Conti with the European frameworks layered above it.
• Anagrafe dei rapporti finanziari — a monthly event communication on relationship openings and closings, and an annual balances return due 15 February.
• Conduct and complaints — the dispute-resolution and complaints reporting cycle.
• MiFIR transaction reporting to CONSOB, where investment services are provided.
• CESOP — quarterly cross-border payment data through the tax administration.
• OAM registration obligations where agents are used.

4. Portals are the critical path

Italy routes returns through distinct portals with distinct enrolments — INFOSTAT for statistical and supervisory data, Infostat-UIF for AML — and at least one of them carries an express deadline of its own: obliged subjects must register on the Infostat-UIF portal within 30 days of commencing activity, independently of when a first return falls due.

That is the pattern to plan around. Enrolment is not a by-product of authorisation, it is not instantaneous, and it is per system. A market-entry plan that treats reporting as a post-launch workstream discovers the enrolment lead time at the worst possible moment.

5. Building it

Facts: an EMI licensed elsewhere in the EU establishes an Italian branch and begins offering accounts and transfers.

What the analysis produces: the branch engages the supervisory returns and the AML obligations as applied to the establishment. The financial relationships archive question is answered from the list of financial operators in Annex 1 to the provvedimento of 20 June 2012 rather than from intuition. The instrument set determines whether the objective cash communications apply in practice, though the obligation itself is criteria-driven rather than optional.

What the practitioner does: builds the register with a column for trigger type — suspicion, threshold, calendar, or lifecycle event — because that column determines the control. Calendar obligations need a due-date monitor; threshold and lifecycle obligations need a reconciliation between the population that should have generated a filing and the population that did; suspicion obligations need evidence that assessments are being recorded, including the negative ones.

6. Language, and the reconciliation nobody schedules

Two closing practicalities. Italian filings and supervisory correspondence proceed in Italian, and the technical specifications for the data returns are published in Italian — which makes translation capacity a reporting dependency rather than a convenience, particularly where a specification changes mid-year.

And the highest-value control across the whole Italian inventory is a reconciliation between the returns that describe the same population from different angles. The archive that must be kept current, the monthly aggregate statistics and the account communications to the tax administration all derive from the same underlying customer and transaction base. Where their populations diverge, one of them is wrong — and because three of the four AML obligations fail silently, that reconciliation is frequently the only thing that would surface it.

7. The calendar, return by return

Italy splits the work across three collectors, and the AML side alone carries four parallel obligations with four different clocks. The deadline column gives the operating rule; the instrument behind each return is in the linked article.

The S.A.R.A. clock is the one that catches people. A deadline expressed as the second working day of the third month after the reporting month reads as generous and behaves as the opposite: three months are always in flight at once, so a data problem found in the current month is usually also present in two returns already prepared.

8. The row that is new: CRS/DAC2 to the Agenzia delle Entrate

Council Directive (EU) 2023/2226 extends the Common Reporting Standard to specified electronic money products from 1 January 2026, first exchange 2027. For an Italian branch that adds an annual return to a calendar that previously had no CRS entry at all.

The Italian mechanics are specific and worth separating from the Spanish and French ones:

• Deadline: 30 June of the year following the reference year, so 2026 data is due by 30 June 2027.
• Legal basis: the ministerial decree of 28 December 2015 implementing Law 95 of 18 June 2015 and Directive 2014/107/EU.
• Channel: the same SID exchange channel used for the financial-accounts archive, which means an institution already accredited there has the hard part done. Transmission must be performed by a party currently enabled on that system.
• Negative return: required where there is nothing to report.

Worked example. An Italian branch already files the monthly relationship data through the tax authority’s exchange system and assumes CRS will simply be another flow on it. Rule: the channel is indeed shared, but CRS/DAC2 has its own technical annex, its own signing and encryption step and its own enablement. What the practitioner does: confirms the existing accreditation covers the CRS flow rather than assuming it, and tests the signing and encryption path against a sample file well before June. Outcome: the shared channel is an advantage rather than a false assumption — which is only true if somebody checks.

FAQ

9. What to do, today

• Write the calendar down as a table with an owner per row, not as a set of diary entries. A row with no name against it is the one that is missed.
• Record the channel and the enrolment beside each return. Enrolment, certificates and access are the long pole on almost every one of these, and they expire.
• Add the CRS/DAC2 row now if it is not there. The 2026 data is being generated already, whatever year the first filing falls in.
• Run a coverage query on tax residence and foreign tax identification numbers against the existing book before year end, and let the result decide whether year one is a negative return or a full build.
• Check which returns require a nil or negative filing. Several here do, and “nothing to report” is not the same as nothing to file.
• Diarise the head-office annual accounts. It is a branch duty with no owner in most operating models.
• Re-derive the calendar whenever the product set changes. A new product does not announce itself to the reporting function.

Related: The Spanish reporting calendar · The French reporting calendar · Banca d’Italia segnalazioni · CAI — Centrale di allarme interbancaria · SID — the Agenzia delle Entrate channel · Circolare 217 — supervisory reporting for IP and IMEL · Segnalazioni periodiche antiriciclaggio — Banca d’Italia’s annual AML return · Relazione annuale antiriciclaggio — Italy’s 30 April AML report and self-assessment