Anagrafe dei rapporti — Italy’s account data return
Italy asks financial operators for account data twice on different cycles, and the two returns carry different content. The Archivio dei rapporti finanziari — the financial relationships archive within the Anagrafe Tributaria — was given its current shape by Decree-Law 201/2011, which introduced the obligation for financial operators to communicate information on the balances and movements of active relationships. A monthly communication tracks the lifecycle; an annual one carries the numbers.
1. Two returns, two clocks
| Monthly communication | Annual communication | |
|---|---|---|
| Deadline | Within the month following the opening or closing of the relationship | By 15 February of the year following the reference year |
| Trigger | A lifecycle event on a relationship | The calendar |
| Content | Data on the relationship and on extra-account operations, the identification code, and the personal data of subjects connected to the relationship with their role specified | Identification data of the relationship, opening balance at 1 January and closing balance at 31 December, and total movements split between debit and credit |
2. Who files
The obligation falls on financial operators, and the complete list of them is set out in Annex 1 to the provvedimento of 20 June 2012. That list, rather than an intuition about what counts as a financial operator, is the authoritative scoping document — and it is the first thing to read when assessing whether a payment or e-money business entering Italy is inside the regime.
The scoping question is genuinely worth doing properly, because the archive is one of the highest-consequence data returns in the Italian system: it feeds tax enforcement and is queried by authorities against named individuals. A gap here is not a statistical inaccuracy.
3. The role field, and why it is hard
The monthly communication requires the personal data of subjects connected to the relationship with the role specified. That is a harder requirement than it reads, because the roles the archive recognises are a defined set and a firm’s own product vocabulary rarely maps cleanly onto it.
Three sources of difficulty recur:
- Multiple roles on one relationship. A person can be both holder and authorised operator, and the return has to express that rather than pick one.
- Roles that change without the relationship changing. Adding or removing an authorised person is a change to the connected subjects, not to the account.
- Legal-person structures. Where the holder is an entity, the connected natural persons and their roles are a separate mapping question again.
A mapping table from internal role names to the archive’s role codes, maintained as a versioned artefact, is the deliverable that makes this tractable — and it should be built before the first submission rather than after the first rejection.
4. Technical specifications and versioning
The archive publishes technical specifications for the communications, and they are updated on their own cycle — the current specifications apply from 4 November 2024. As with every specification-driven return in this cluster, the version in force at the reference period is what governs, and a change to the specifications changes the file without any change to the underlying decree.
Facts: a payment institution entering Italy builds its monthly communication from a nightly full extract of all open relationships.
What goes wrong: the monthly communication is owed in respect of openings and closings, so a full-population feed reports relationships that had no lifecycle event. The annual communication is the one that carries the whole population with balances.
What the practitioner does: builds two distinct feeds from the same model — an event feed for the monthly communication, keyed to opening and closing events with connected subjects and roles attached, and a population-and-balances feed for the annual return keyed to 1 January and 31 December. Attempting to serve both from one extract is the commonest structural error in this regime.
FAQ
What is the annual deadline?
15 February of the year following the one to which the information refers.
What does the annual return contain?
Identification data of the relationship, the opening balance at 1 January and closing balance at 31 December of the reference year, and total movements split between debit and credit.
Where is the list of obliged financial operators?
In Annex 1 to the provvedimento of 20 June 2012.
Is the monthly return a full population extract?
No. It is owed within the month following the opening or closing of a relationship, so it is an event feed. The full population with balances belongs to the annual return.
Related: The Italian reporting calendar · FICOBA in France · The FTF in Spain
