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, 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.

FAQ

Related: The Spanish reporting calendar · The French reporting calendar · Banca d’Italia segnalazioni