Account registers compared across the EU
Every EU market keeps a central record of who holds which accounts, and no two collect it the same way. Some run event-driven registers fed on opening and closure. One takes a monthly file. Two do not take a submission at all: the authority reaches into a file the institution hosts. A firm operating in several markets therefore needs several build patterns for what looks like one obligation, and the differences are architectural, not cosmetic. This guide sets out the common EU basis, compares eight national mechanisms, explains who is caught across borders, and works through four scenarios a payment or e-money institution meets in practice.
1. One EU obligation behind all of them
The national registers share a legal root. Article 32a of Directive (EU) 2015/849, inserted by Directive (EU) 2018/843, required each Member State to set up a centralised automated mechanism, either a central register or a central electronic data retrieval system, to identify in a timely manner the holders and controllers of IBAN-identified bank and payment accounts and of safe-deposit boxes. Member States chose freely between the two designs. That freedom explains why the operational shape differs so much from one market to the next.
The next step is already law. Article 16 of Directive (EU) 2024/1640 (AMLD6) replaces Article 32a and widens the content. The mechanisms must cover payment accounts, bank accounts identified by IBAN including virtual IBANs, securities accounts, crypto-asset accounts and safe-deposit boxes held by a credit institution or a financial institution. For a virtual IBAN, the register must show the virtual IBAN, the account to which payments are automatically redirected, and the opening and closing dates; the holder is the holder of that underlying account. Beneficial owners of account holders must be searchable, with the dates on which they became and ceased to be beneficial owners. Information must stay available for five years after closure, with an optional further five years in specific cases.
The general transposition date is 10 July 2027 (Article 78). The Commission must interconnect the national mechanisms through the bank account registers interconnection system, BARIS, by 10 July 2029 (Article 16(6)). FIUs, and AMLA for joint analyses, will then query accounts in other Member States directly.
2. The comparison
| Market | Mechanism | Shape | PIs and EMIs in scope today? |
|---|---|---|---|
| Spain | Fichero de Titularidades Financieras (art. 43 Ley 10/2010; arts. 50-57 RD 304/2014) | A monthly fixed-width file to SEPBLAC | Yes, named in art. 43 of the law |
| France | FICOBA (art. 1649 A CGI; arts. 164 FB-164 FG Annex IV) | Event-driven: opening, modification, closure, filed within seven days since 1 May 2025 | Yes, including freedom-of-services firms for French residents |
| Italy | Anagrafe and Archivio dei rapporti finanziari (art. 7 DPR 605/1973; art. 11 DL 201/2011) | Both: an event communication within the month after opening or closing, and an annual balances return by 15 February, via SID | Scope against the financial-operator categories of art. 7 DPR 605/1973 |
| Germany | Kontenabrufverfahren (§ 24c KWG, applied by § 27(2) ZAG) | A file the institution maintains, queried without the institution seeing the request | Yes, through the ZAG cross-reference |
| Luxembourg | CRBA (Law of 25 March 2020; Circular CSSF 20/747) | A hosted file the CSSF pulls through a single-use link every working day | Yes |
| Belgium | PCC / CAP at the NBB (Law of 8 July 2018; RD 7 April 2019) | Events within five working days, balances twice a year | Yes, for payment accounts held in Belgium |
| Netherlands | Verwijzingsportaal Bankgegevens | A live connection that answers authority queries, with an availability requirement | Yes, for Dutch IBAN issuers |
| Ireland | ISBAR (S.I. No. 46 of 2022) | A baseline upload plus weekly XML deltas via the CBI Portal | No, credit institutions only until further primary legislation |
Spain adds a second, separate account collection. Modelo 196 goes to the tax administration, not to SEPBLAC, and has been monthly since January 2026.
3. Four build patterns
The mechanism dictates the architecture, and a wrong choice is expensive to unwind:
- Event-driven register (France, Belgium, Italy’s monthly flow, Ireland’s deltas). It needs a change feed off the account lifecycle, with an explicit list of change-relevant fields. Emitting on every customer-record write produces noise. Emitting only on open and close produces silent drift, because modification is a separately declarable event in France, and a change of holder identity, address or civil status must reach FICOBA within seven days.
- Periodic file (Spain’s FTF, Italy’s annual return). It needs a population snapshot pinned to a reference date, plus the usual reporting-pipeline controls: version, reconciliation, resubmission.
- Hosted file pulled by the supervisor (Luxembourg, Germany). The CRBA needs an authenticated service with mutual TLS, PGP encryption and a single-use download token. The German file must be retrievable at any time, and the institution must not see the retrieval.
- Live connection (the Netherlands). It needs uptime engineering and an availability control. There is no file, so there is nothing to archive. The control is that the service answers correctly.
4. Perimeter: who is caught across borders
The most valuable comparison is not the format but who is caught, because that is where firms scope themselves out wrongly. The triggers fall into three groups.
| Trigger | Markets | Consequence for a passporting firm |
|---|---|---|
| Customer residence | France (FICOBA), Spain (Modelo 196) | A firm with no branch is in scope for its French-resident and Spanish-resident customers |
| Establishment in the territory | Spain (FTF), Italy, Germany, Luxembourg, Ireland | A local branch or authorisation brings the firm in |
| Account held in the territory | Belgium (payment accounts), the Netherlands and Luxembourg (local IBANs) | The location of the account, often signalled by the IBAN country code, decides scope |
France’s obligation under Article 1649 A CGI expressly covers establishments operating under the freedom-of-services provisions of the Code monétaire et financier, for their operations with French residents. Spain’s Modelo 196 expressly covers foreign entities operating in Spain under the freedom to provide services, for accounts held by Spanish residents. In both cases the customer’s residence decides, not the firm’s location.
5. What all of them have in common
Whatever the mechanism, the payload is the same in substance, and so are the failure modes:
- Identity data is the whole build. Most registers hold no balances, so there is no arithmetic to reconcile. Quality depends entirely on holder identification, and every regime fails at the same point: customers whose identification data was never captured to the register’s standard.
- Roles are harder than holders. Italy asks for connected subjects with their role; Germany asks for persons with power of disposal and beneficial owners. The mapping from internal product vocabulary to the register’s role codes should be a versioned document that exists before the first submission.
- Specifications change without the law changing. France’s XML specifications, Italy’s single record layout and the CRBA annexes are all revised on their own cycle.
- Safeguarding sub-ledgers are in scope. SEPBLAC’s instructions treat accounts that only record each client’s balance inside the safeguarding account as declarable. The same reasoning applies elsewhere: if the customer has a payment account, it is reportable.
6. Worked scenarios
Scenario 1 — one platform, four markets. Facts: an EMI authorised in Lithuania serves customers in Spain, France, Italy and the Netherlands from one platform, with a branch in Spain and Dutch IBANs. Rule: the Spanish branch is a declaring entity for the FTF and files Modelo 196; FICOBA applies to the French residents under the freedom-of-services limb; Dutch IBANs require the reference-portal connection; Italy turns on whether the firm is a financial operator under Article 7 DPR 605/1973. What compliance does: builds one internal model of account, holder, connected persons and lifecycle events, carrying customer residence and IBAN country as maintained attributes, and renders it four ways. Outcome: one event feed serves three regimes, and the Dutch connection reads the same model. A reconciliation between the core ledger population and each register’s population becomes the main detective control.
Scenario 2 — a holder’s surname changes. Facts: a French-resident customer changes surname after marriage and updates the address the same week. Rule: both are declarable modifications in FICOBA, due within seven days; in Germany the same change would create a new record in the § 24c file, with the superseded record kept for three years. What the engineer does: flags surname and address as change-relevant fields, emits a modification event, and keeps history append-only rather than overwriting. Outcome: an authority query months later still resolves the former name. A nightly job that updates in place would destroy that history.
Scenario 3 — virtual IBANs for business customers. Facts: a payment institution issues virtual IBANs that redirect to a collection account held by each business customer. Rule: under Article 16(3)(d) AMLD6, the register must show the virtual IBAN, the account it redirects to and the dates, and the holder is the holder of the underlying account. What compliance does: adds a virtual-IBAN table linked to the underlying account now, before national transposition, and checks which current regimes already ask for it. Outcome: when the national rules land in 2027, the data exists. Firms that issued virtual IBANs without a durable link to the underlying account face a back-fill exercise across years of closed accounts, because of the five-year retention rule.
Scenario 4 — Irish IBANs from an EMI. Facts: an Irish-authorised EMI issues Irish IBANs. Rule: ISBAR currently binds only credit institutions; the Central Bank has said further primary legislation is needed to bring in other issuers. What compliance does: records ISBAR as a planned obligation, builds the XML data set to the credit-institution specification, and watches for the extending legislation. Outcome: onboarding becomes a configuration task, not a project, when the scope changes.
7. FAQ
Which markets catch firms with no establishment?
France and Spain frame their obligations around the customer’s residence: French residents for FICOBA, Spanish residents for Modelo 196. A passporting firm with no branch is in scope for both.
Which is the odd one out?
The Netherlands. The reference portal is a mandatory connection with an availability requirement, not a data submission. Luxembourg and Germany are close behind: the institution hosts the file and the authority takes it.
Are payment and e-money institutions in scope everywhere?
Not yet. They are in scope in Spain, France, Italy, Germany, Luxembourg, Belgium and the Netherlands. Ireland’s ISBAR covers only credit institutions until further primary legislation is adopted.
What does AMLD6 change?
Article 16 of Directive (EU) 2024/1640 adds virtual IBANs, securities accounts, crypto-asset accounts and beneficial owners to the content, sets a five-year post-closure availability period and requires interconnection through BARIS by 10 July 2029. General transposition is due by 10 July 2027.
What is the single highest-risk data field?
Holder identification. These registers are identity records attached to accounts, so identification quality is the whole quality question.
Do the registers hold balances?
Mostly not. Italy’s annual return and Belgium’s twice-yearly balances are the exceptions in this comparison.
8. What to do, today
- List every market where you hold accounts, have customers resident or issue local IBANs, and mark each register’s trigger: residence, establishment or account location.
- Build one account model with customer residence, IBAN country, connected persons with roles, beneficial owners with dates, and lifecycle events, all kept as history rather than overwritten.
- Add a virtual-IBAN link table to the underlying account now, ahead of the 2027 transposition of AMLD6.
- Run a monthly reconciliation between the core-ledger account population and each register’s population, and treat differences in either direction as findings.
- Keep a register of specification versions for each national format, with an owner who watches for updates.
Related: FICOBA · The Italian archive · Modelo 196 · Kontenabrufverfahren — the § 24c KWG account file · CRBA — Luxembourg’s central register of bank accounts · FCC and FNCI — the French cheque registers · CAI — Centrale di allarme interbancaria · FICP — the French credit-incident register · SID — the Agenzia delle Entrate channel · Central Credit Register — Ireland · Spain – the CIR threshold after Orden ECM/531/2026 · Belgium — the Centrale des Crédits aux Particuliers · Company registers compared across the EU · ISBAR — Ireland’s bank and payment account register · Ley de Integridad Pública: FTF access and the Libro de Socios · PCC / CAP — Belgium’s account register


