Custodian bank due diligence on external asset managers is the part of a Swiss private bank's AML framework that is easiest to underestimate. The end client is the bank's contracting partner, but the firm that brings the client in, collects the documents, explains the source of wealth and gives the instructions is an independent manager the bank does not employ. Swiss law lets the bank rely on that firm for part of the know-your-customer work: articles 28 and 29 of the FINMA Anti-Money Laundering Ordinance (AMLO-FINMA) and article 43 of the Swiss Bankers Association's due diligence agreement (CDB 20) set the conditions. What the law does not do is move the responsibility: under art. 29 para. 1 AMLO-FINMA, the bank remains responsible under supervisory law, in all cases, for the proper performance of the tasks it delegated.
This article covers the regulatory basis, what an EAM file should contain, how KYC files can move from the external asset manager to the bank without being re-keyed, and how the periodic review should cover both the client and the EAM. It also flags the change of 1 January 2027, when a revised AMLO-FINMA and a new CDB 27 come into force.
1. Two relationships, two due diligence files
In the classic Swiss EAM model, the end client opens an account in their own name at the custodian bank, mandates the external asset manager (in French-speaking Switzerland, the gérant de fortune indépendant or GFI) to manage the portfolio, and grants it a power of attorney on the account. The bank and the EAM sign a collaboration agreement.
That structure produces two distinct files at the bank:
- The client file. The end client is the contracting partner. The bank verifies their identity, establishes the beneficial owner, understands the purpose of the relationship and the origin of the assets, and classifies the risk, exactly as for a client who came without an intermediary.
- The EAM file. The manager is an authorised representative on many accounts and usually the party that performs part of the client due diligence on the bank's behalf. The bank needs to know who it is, whether it is authorised, who acts for it, and whether it can be trusted with delegated tasks.
Mixing the two is a common source of gaps. A complete EAM file does not make the client files complete, and a clean client file says nothing about whether the manager who prepared it is still authorised. For the EAM's own perspective, see our guide to KYC and AML compliance for external asset managers.
2. The legal basis: AMLA, AMLO-FINMA, the CDB and FinIA
The Anti-Money Laundering Act (AMLA). Art. 3 AMLA requires the financial intermediary to verify the contracting partner's identity when the relationship is established. Art. 7 para. 1bis, in force since 1 January 2023, requires it to check periodically whether the documents are up to date, with frequency, scope and method depending on the risk. Portfolio managers and trustees authorised under the FinIA are themselves financial intermediaries (art. 2 para. 2 let. abis AMLA).
AMLO-FINMA. The FINMA ordinance sets the general rules on reliance on third parties (arts. 28 and 29). For banks and securities firms, art. 35 adds that the identification of the contracting partner, the controlling person and the beneficial owner is governed by the CDB.
The CDB. CDB 20, the agreement of 13 June 2018 in force since 1 January 2020, contains its own delegation rule (art. 43), documentation rules (arts. 44 and 45) and the duty to repeat the identification in case of doubt (art. 46).
The Financial Institutions Act (FinIA). The FinIA defines the portfolio manager and requires a FINMA authorisation, the first thing a bank checks about an EAM (section 5).
From 1 January 2027. FINMA amended AMLO-FINMA by an ordinance of 29 October 2026 (AS 2026 618). In the consolidated version on Fedlex, art. 35 refers to the CDB 27 of 30 October 2026, which replaces CDB 20. The wording of arts. 28 and 29 is unchanged; they move into a new section 5 on reliance on third parties. Banks should read the CDB 27 text itself for any change to the delegation article and the forms before updating their EAM procedures.
3. Delegating identity verification: what art. 28 requires
Art. 28 para. 1 AMLO-FINMA allows the financial intermediary to mandate, by written agreement, persons or companies to verify the contracting partner's identity, establish the controlling person or beneficial owner and carry out the additional clarifications, on three conditions:
| Condition (art. 28 para. 1) |
What it means for a bank working with an EAM |
| a. careful selection of the third party |
A documented onboarding of the EAM: authorisation, ownership, management, reputation, AML organisation |
| b. instruction on the tasks |
The bank's requirements (forms, documents, certification, deadlines) given to the EAM in writing |
| c. ability to check compliance |
A control plan: checks on delivery, sample testing, consequences when files are deficient |
Para. 2 allows delegation without a written agreement to a group entity applying equivalent standards, or to another financial intermediary subject to equivalent AML supervision and regulation that has taken measures to perform its due diligence in an equivalent way. A FINMA-authorised portfolio manager is a financial intermediary, but the bank still has to assess that equivalence and stays responsible either way. Whatever it decides, the collaboration agreement is the natural place to record the instructions required by para. 1 let. b.
Under para. 3, the third party may not itself call on other persons or companies: an EAM cannot pass the identification on to an introducer. Art. 43 CDB 20 mirrors these rules with bank-specific detail: the mandatee forwards all identification documents to the bank and certifies that the copies match the originals (para. 2), further delegation is prohibited (para. 3), and delegation within a group or to a supervised financial intermediary needs no written agreement (para. 4).
4. The responsibility stays with the bank
Art. 29 AMLO-FINMA turns the delegation into duties that remain with the bank:
- Para. 1: the bank remains responsible under supervisory law, in all cases, for the proper performance of the delegated tasks.
- Para. 2: it keeps a copy of the documents used to meet its AML duties and obtains written confirmation that the copies match the originals.
- Para. 3: it checks the plausibility of the results of the additional clarifications itself.
The third point is the one most often missed. An EAM can collect the source-of-wealth documents and draft the explanation, but the bank's compliance function decides whether it is plausible. A thin narrative does not become complete because a regulated intermediary wrote it. CDB 20 adds a timing rule: under art. 45, the identification documents must be available before the account can be used, with a narrow exception and a 30-day deadline for missing items.
5. The FinIA authorisation: where custodian bank due diligence on external asset managers starts
Since the FinIA came into force on 1 January 2020, anyone who can, on the basis of a mandate, dispose of clients' assets professionally in their name and for their account is a portfolio manager (art. 17 para. 1) and needs a FINMA authorisation (art. 5). Firms that were not subject to authorisation under the old law had three years to apply (art. 74 para. 2), so the transition is complete. Ongoing supervision is carried out by supervisory organisations (SOs) authorised by FINMA (art. 61 para. 2). For the full set of obligations on the manager's side, see FinSA and FinIA obligations for Swiss asset managers.
For the bank, this means concrete checks:
- the EAM appears on FINMA's list of authorised portfolio managers and trustees monitored by an SO, or on its list of group companies it supervises directly;
- the SO that monitors it is recorded in the file;
- the firm is not on FINMA's warning list;
- the entity, its owners, its managing persons and its signatories match the authorisation and the commercial register.
A Swiss portfolio manager without an authorisation is not a partner a bank can delegate to. For a foreign manager, the analysis starts with whether it is subject to equivalent AML supervision.
6. What goes into an EAM file
A defensible EAM file is short, structured and dated. The exact list belongs in the bank's internal directive; the components below are a reasonable baseline.
| Component |
Purpose |
Trigger for update |
| FINMA authorisation and SO affiliation |
Confirms the EAM may manage assets and is supervised |
Change of SO or authorisation status |
| Commercial register extract, articles, ownership |
Identifies the entity and its controllers |
Change in owners or management |
| Managing persons and authorised signatories |
Shows who may instruct the bank |
Any change of signatory |
| Sanctions, PEP and adverse media screening on entity, owners, managers |
Legal and reputational risk |
Each review, each new hit |
| AML organisation (compliance function, directives) |
Supports the "careful selection" test |
Periodic review |
| Collaboration agreement ("EAM agreement") |
Roles, delegated tasks, documents, information rights, termination |
Contract changes |
| Model power of attorney |
What the EAM may do on client accounts |
Change to the bank's standard |
| Control record |
Results of file checks and sample tests |
Each control cycle |
The EAM agreement is where art. 28 para. 1 let. b becomes practice: which forms to use, which documents must be certified and by whom, how fast changes in a client's situation must be reported, and what happens when a file is incomplete. The power of attorney is granted by the client, but its scope is a central risk parameter for the bank: a power limited to management and information carries a different risk from one that also allows transfers to third parties. Any extension beyond the bank's standard model should be visible in the client file.
7. Moving KYC files between EAM and bank without re-keying
The friction in EAM business is rarely the rules; it is the format. Each custodian has its own forms, so an EAM working with several banks fills in the same information several times, and each bank's back office re-keys what it receives. Every manual step can create an inconsistency between the two files, and inconsistencies are what auditors look for.
Art. 29 para. 2 AMLO-FINMA and art. 43 para. 2 CDB 20 require a copy of the documents, confirmed as matching the originals. Neither text requires that copy to travel by email or on paper, or to be retyped. A digital transfer works if it preserves four things:
- Integrity: the bank can show that what it received is what the EAM sent, and when.
- Certification: the confirmation that copies match the originals stays attached to the file.
- Consent: the client has agreed to the exchange between the EAM and the bank, and the consent is recorded (see data protection and KYC under the FADP and GDPR).
- Structure: data arrives as fields the bank's systems can read, not as a PDF to transcribe.
This is the model Barclays Private Bank Switzerland chose. In May 2026, Wecan announced that the bank would initially deploy Wecan's solution for its EAM ecosystem, enabling a fully digital, secure and standardised onboarding and KYC process between external asset managers and the bank, with identity verification, sanctions, adverse media and PEP screening, ongoing risk assessments and a blockchain-based audit trail. The bank's delegation duties do not change; the channel through which delegated work arrives does. More on the bank-side workflow on our digital onboarding page.
8. The periodic review: the client and the EAM
Art. 7 para. 1bis AMLA requires a risk-based periodic check that client documents are current. In an EAM relationship, the review has two objects.
The client file. The bank sets the frequency by risk category, but the information usually comes through the EAM. If the agreement does not say what the EAM must deliver for a review and by when, reviews stall. Changes the EAM learns about between reviews should reach the bank without waiting for the next cycle.
The EAM file. The bank should review the manager itself on a fixed cycle: authorisation and SO affiliation still valid, owners and signatories current, screening rerun, results of its own file controls taken into account. This is the evidence that the bank is still able to check compliance under art. 28 para. 1 let. c. An EAM whose files repeatedly fail those checks is no longer a third party the bank can rely on without additional measures.
The cycles are linked: a new signatory or a change of SO at the EAM affects every account it manages, and a process that treats each client in isolation will miss it. Our periodic reviews page shows how reviews can be event-driven rather than batched at year-end.
9. Frequently asked questions
Can a custodian bank rely on the EAM's KYC?
Yes, within art. 28 AMLO-FINMA and art. 43 CDB 20. The bank selects the EAM carefully, instructs it, can check its work, keeps certified copies and checks the plausibility of the additional clarifications itself. Responsibility under supervisory law stays with the bank (art. 29 para. 1).
Does the bank need a written delegation agreement with a FINMA-authorised EAM?
Art. 28 para. 2 let. b allows delegation without one to a financial intermediary subject to equivalent AML supervision that has taken equivalent measures. The bank must still assess that equivalence, and the collaboration agreement remains the natural place to document instructions.
How does a bank check that an EAM is authorised?
FINMA publishes a list of the portfolio managers and trustees it has authorised that are monitored by an SO, and a list of group companies it supervises directly. The bank records the date of the check and repeats it at each EAM review.
Can an EAM pass the identification on to someone else?
No. Art. 28 para. 3 AMLO-FINMA and art. 43 para. 3 CDB 20 prohibit further delegation.
What changes on 1 January 2027?
The revised AMLO-FINMA of 29 October 2026 comes into force, and art. 35 refers to the new CDB 27 of 30 October 2026 instead of CDB 20. Arts. 28 and 29 keep their wording. Banks should review CDB 27 before amending their EAM directives.
10. What Wecan Copilot does
Wecan Copilot connects banks and asset managers on a shared compliance network: each asset manager keeps a single structured file (identity, beneficial owners, regulatory status, signatories, documents) and shares it, with consent, with the banks it works with. When a signatory changes or a document is renewed, every authorised counterparty is notified, and every entry and access is anchored on blockchain. For client files, an EAM can update KYC once and share it with each custodian, with the client's consent. See how it works for external asset managers or book a demo.