Most articles on KYC build vs buy assume the choice is between a vendor platform and an in-house development project. For a large share of Swiss independent asset managers (EAMs) and for the KYC back office of many smaller private banks, that is not the real comparison. The real incumbent is a spreadsheet: a client list in Excel, documents in shared folders, review dates in someone's calendar and four-eyes approvals in an e-mail thread. It costs nothing on any invoice, which is precisely why it survives.
This article sets out what the law and your auditor actually require, where a spreadsheet-based KYC process stops meeting those requirements, what building your own tool really commits you to, and a cost grid you can fill in with your own figures. It does not invent market prices: where it uses numbers, they are the benchmarks Wecan has already published in its pricing guide and ROI analysis, and they are labelled as such.
1. The real competitor: Excel, e-mail and shared folders
A spreadsheet KYC set-up usually looks like this: one workbook with a row per relationship (name, domicile, risk category, PEP flag, last review date), a folder per client on a shared drive, sanctions checks run by hand on a public search tool and saved as a screenshot or PDF, and approvals recorded as "OK" in an e-mail. It works because the people running it know it intimately.
Its strengths are real. It is flexible, it requires no procurement, and for a book of a few dozen relationships managed by one compliance officer it can be kept in order. The problem is not that Excel is a bad tool. The problem is that the obligations in section 2 are about evidence over time: who decided what, on which information, when, and whether the file was kept current. A spreadsheet stores the latest state of a cell. It was not designed to prove how that state was reached.
2. What the AMLA, the AMLO-FINMA and the audit actually require
The requirements that matter for the build vs buy decision are few, and they are all about traceability, documentation and controls.
Documentation that a third party can follow. Under article 7 of the Anti-Money Laundering Act (AMLA), the financial intermediary must keep records of transactions and of the clarifications it carried out so that third-party experts can form an objective view of the transactions, the business relationships and compliance with the Act. Paragraph 1bis, in force since 1 January 2023, adds that it must periodically check that the required documents are current and update them, with the frequency, scope and method of review depending on the client's risk. Paragraph 3 sets a ten-year retention period after the relationship or transaction ends.
A risk-based approach that is written down. Article 6 AMLA ties the information to be collected, the level of management that approves a relationship and the frequency of checks to the risk the client presents. Under the AMLO-FINMA, the anti-money-laundering unit (or another independent unit) prepares a risk analysis approved by the board or senior management and updated periodically (article 25 para. 2), and the institution adopts internal directives covering, among other things, the criteria for higher-risk relationships and the principles of transaction monitoring (article 26).
Monitoring and controls. Article 20 AMLO-FINMA requires effective monitoring of relationships and transactions. Banks and securities firms must use an IT-based system for transaction monitoring, unless they have few clients and few transactions; FINMA can also require an asset manager or trustee to introduce one where that is necessary for monitoring to be effective (article 20 para. 5). Article 8 AMLA requires organisational measures, staff training and controls, and since 1 October 2026 it expressly extends them to preventing breaches of coercive measures under the Embargo Act (EmbA), in other words sanctions.
The changes of 2026 and 2027. Three recent texts raise the bar further:
- The Federal Act on the Transparency of Legal Entities (LETA) and the revised AMLA entered into force on 1 October 2026, as the Federal Council announced on 12 June 2026. Financial intermediaries may consult the transparency register online for their due diligence (article 27 LETA), and those consultations are logged (article 29). Where an intermediary finds a discrepancy between the register and its own information that casts doubt on the beneficial-owner data, and the client has not resolved it within a reasonable time, it must report it to the register within 30 days, with a standardised justification (article 30). Our LETA guide covers the register in detail.
- The revised AMLO-FINMA of 29 October 2026, in force on 1 January 2027, adds an explicit duty to understand the client's ownership and control structure (article 9b) and requires preventive measures against breaches of EmbA coercive measures, applying the monitoring, organisation and internal-directive provisions by analogy (article 30). For banks and securities firms, article 35 now refers to the CDB 27, the banks' due diligence agreement dated 30 October 2026.
- For Swiss groups with EU entities, the EU Anti-Money Laundering Regulation (Regulation (EU) 2024/1624, the AMLR) applies from 10 July 2027.
3. Replacing Excel for KYC: where the spreadsheet breaks
The question is not whether a spreadsheet can hold the data. It can. The question is whether it can produce the evidence. Five points usually decide it.
Versions. Shared workbooks get copied, renamed and e-mailed. Even with version history switched on, the history records that a file changed, not why a client's risk rating moved from medium to high, who approved it and on the basis of which document. Article 7 AMLA asks for the reasoning, not just the result.
Audit trail. An auditor testing a sample of files wants to see, for each one, the evidence behind each conclusion and the person who reached it. In a spreadsheet set-up that trail is spread over the workbook, the folder, the mailbox and the analyst's memory, and it is reassembled by hand before every audit.
Periodic review reminders. Article 7 para. 1bis makes periodic updating a legal obligation with a risk-based frequency. A due date in a column does nothing unless someone filters on it. When the person who owns the workbook is absent, reviews slip silently, and the backlog only becomes visible when it is already a finding.
Screening. The SECO search tool describes itself as an aid only, and states that it provides no information on ownership or control relationships. Checking a portfolio by hand also checks it only on the day you do it: lists change, and a manual process has no way to re-screen the whole book automatically when they do. With sanctions prevention now written into article 8 AMLA and, from 2027, article 30 AMLO-FINMA, "we checked at onboarding" is a weak answer.
Deadlines that now come from outside. The LETA discrepancy procedure introduces a sequence (detect, ask the client, wait a reasonable period, report within 30 days) that has to be tracked per entity. That is workflow, and spreadsheets do not run workflows.
None of this means every spreadsheet must go tomorrow. AMLO-FINMA article 3 para. 2 lets FINMA take an institution's size and risk into account. But the smaller the team, the more the whole control framework rests on one or two people, and the less margin there is when one of them leaves.
4. Building in-house: the code is the cheap part
Institutions with an IT team sometimes conclude that a KYC tool is a database, a few forms and a workflow, and that they can build it. The first version is usually achievable. What is underestimated is everything that has to happen after it goes live.
Sanctions and PEP data. You need a data source, a contract for it, an ingestion process and a matching engine that handles transliterations and aliases. SECO publishes its consolidated list in XML with a published schema, so it can be processed automatically, but EU, UN, UK and US lists, PEP data and adverse media come from other sources, each with its own format and update cycle. Someone has to own that pipeline, permanently.
Regulatory change. Each of the revisions listed in section 2 means new fields, new rules, new controls and new documentation for the auditor. A vendor spreads that cost over many clients; an in-house tool carries it alone.
Evidence of the tool itself. An auditor will ask how the tool works: how risk scores are calculated, who can change parameters, how changes are tested and logged. Article 25 para. 1 let. b AMLO-FINMA makes the AML unit responsible for setting the parameters of the monitoring system, so those parameters must be documented and controlled. That is software governance, and it has to be written, maintained and audited.
Time to value. Wecan's pricing guide estimates that building typically takes 12 to 24 months to first value, compared with 4 to 12 weeks for a modern SaaS onboarding platform and 6 to 18 months for an enterprise client-lifecycle-management deployment. During that period, the spreadsheet carries on.
5. KYC build vs buy: decision criteria
| Criterion |
Stay on Excel |
Build in-house |
Buy a platform |
| Book size and complexity |
Small, few legal entities |
Any, if requirements are genuinely unique |
Any |
| Audit trail |
Rebuilt by hand |
As good as you design and maintain it |
Depends on the product: test it |
| Periodic reviews |
Manual reminders |
To be built |
Usually standard; check risk-based scheduling |
| Sanctions and PEP screening |
Manual, point in time |
Data contract plus pipeline to build |
Integrated; check whether you can bring your own provider |
| Regulatory change |
Absorbed by staff |
Carried alone |
Shared across clients; check the vendor's track record |
| Key-person risk |
High |
High |
Lower, but add vendor dependency |
| Exit |
Easy |
Easy |
Check export format and terms before signing |
Four questions usually settle it:
- Is our requirement really unique? A cross-border private bank with unusual products may need custom logic. Most EAMs do not.
- Do we have a standing team to maintain compliance logic for years? Not to build it, to maintain it.
- Can we produce, today, a complete audit trail for any file within an hour? If not, the status quo already has a cost.
- What happens to our KYC when the person who runs it is away for a month?
A common middle path is to buy the regulated plumbing (file, workflow, screening, audit trail) and build only the thin layer that is truly proprietary, such as a link to your portfolio management system or a specific report.
6. A total cost grid, without invented numbers
Compare the three options over the same period (three or five years) and with the same scope. Fill each line with your own figures; leave none blank.
| Cost line |
Excel and e-mail |
In-house tool |
Platform |
| One-off |
Template set-up |
Specification, development, testing, security review |
Implementation, integration, migration |
| Recurring software |
Existing licences |
Hosting, security, maintenance |
Licence |
| Screening data |
Manual searches or a data subscription |
Data contract plus ingestion |
Included or your own contract |
| Regulatory change |
Staff time per revision |
Development per revision |
Usually in the licence: confirm |
| Compliance staff time |
Time per file × annual volume |
Time per file × volume, after go-live |
Time per file × volume, after go-live |
| Audit preparation |
Days per audit to reassemble evidence |
Depends on the tool |
Depends on the tool |
| Hidden costs |
Review backlog, findings, key-person risk |
Key-person risk, opportunity cost of the build period |
Vendor dependency, exit costs |
The line that decides the comparison is almost always compliance staff time, and it is the one most often left out because it never appears on an invoice. To estimate it, the pricing guide suggests taking an analyst's loaded annual cost, dividing it by the number of files completed in a year and adding tooling and archiving. For reference, Wecan's published benchmarks are a loaded Swiss analyst cost of CHF 80,000 to 110,000 a year, manual onboarding of roughly CHF 300 to 800 per file in a private-banking context (up to CHF 350 to 1,000 with corporate structures), and manual throughput of around 15 to 25 files per analyst per month, against 80 to 120 with automation. The ROI analysis works through one profile, an intermediary with 500 active clients and 2 FTEs, where the manual baseline is estimated at about CHF 200,000 a year and the all-in software investment at about CHF 30,000 a year.
Treat these as orders of magnitude to test against your own data, not as quotes. And note that freed capacity is only a saving if it is actually redeployed.
7. Frequently asked questions
Is Excel allowed for KYC under Swiss law?
No Swiss text prescribes a particular tool. The law requires documentation a third-party expert can follow, risk-based periodic updating and ten-year retention (article 7 AMLA), plus effective monitoring and controls. The question is whether your spreadsheet set-up can evidence all of this.
When does it make sense to build a KYC tool in-house?
When your requirements are genuinely unique and you have a standing team able to maintain compliance logic, screening data and documentation as regulation changes. Wecan's pricing guide estimates 12 to 24 months to first value for a build. Many institutions buy the regulated core and build only a thin proprietary layer.
What changed for KYC in Switzerland in 2026?
The revised AMLA and the LETA entered into force on 1 October 2026. Article 8 AMLA now covers preventing breaches of Embargo Act measures, and the LETA created a transparency register that intermediaries can consult and to which they must report unresolved discrepancies within 30 days. The revised AMLO-FINMA follows on 1 January 2027.
How do I calculate the total cost of my current KYC process?
Take a loaded analyst cost, divide it by the files completed per year, add tooling and archiving, and multiply by your annual volume of onboardings and periodic reviews. Add the days spent preparing each audit. Compare that baseline with the total cost of each alternative over three or five years.
Does buying a platform remove the need for internal expertise?
No. The risk analysis, the internal directives, the parameters of the monitoring system and the decisions on files remain the institution's responsibility under the AMLO-FINMA. A platform changes how the work is done and evidenced, not who is accountable for it.
8. What Wecan Copilot does
Wecan Copilot keeps each client file as structured data with an append-only audit trail recording who entered each field, when and from which source. Screening runs through the provider of your choice or ours, internal rules are written in plain language, and workflows carry four-eyes approvals and deadlines. Periodic reviews are scheduled by risk band and arrive pre-filled. To see it on one of your own files, book a demo.