Wealth Software for Swiss Asset Managers: FinIA, FinSA, Costs and Timelines
FinIA licensing, SO audits and FinSA conduct rules each translate into specific system features. Here's what Swiss asset managers should require from vendors, what it typically costs and how long go-live takes.
What a FinIA license and supervisory-organization audits demand from your systems
If you run an independent asset manager in Switzerland, the software question has changed. You're no longer asking whether you need a proper portfolio management system. You're asking whether your current stack can produce the evidence your supervisory organization (SO) and its audit firm will request, year after year. The Financial Institutions Act (FinIA) and the Financial Services Act (FinSA) took effect in January 2020, and the transition period for existing managers has since ended. Portfolio managers handling third-party assets on a discretionary basis now need a FINMA license and sit under ongoing supervision by a FINMA-authorized SO, such as OSFIN, AOOS, FINcontrol Suisse, OSIF or SO-FIT.
That setup matters for software selection. FINMA grants the license, but the SO and its audit firm test day-to-day compliance. They look at your organization, risk management, internal controls, compliance function, anti-money-laundering (AML) controls and FinSA rules of conduct. Auditors don't accept good intentions. They want timestamped records, versioned client profiles, documented investment restrictions and proof that breaches were caught and handled.
Several license conditions turn directly into system requirements:
- Risk management and internal control. Smaller firms may be able to have a management member perform these functions, but the controls still have to exist and leave a trail. That means automated mandate checks, exception logs and sign-off workflows, not a spreadsheet someone opens on Fridays.
- Qualified managers and continuity. If one qualified manager is away, another person must be able to see every mandate, restriction and open issue. Systems that keep client knowledge in personal inboxes fail this test.
- Documented outsourcing. If a vendor hosts your data or runs your reconciliation, auditors will ask for the contract, your due diligence and your exit plan.
- AML duties. Your custodian banks run their own checks, but that doesn't replace your duties under the Anti-Money Laundering Act: client identification, beneficial-owner establishment, PEP and sanctions screening, and monitoring.
Our view: firms with roughly CHF 250-300 million or more in assets, or more than three custodians, should buy wealth management software for Switzerland that combines portfolio management, the client file and compliance controls on one data model. You can stitch together a PMS, a separate CRM and manual compliance checklists, but this is where audit findings tend to pile up, because no single record shows what was known about a client when a decision was made. Very small firms (one or two qualified managers, under about CHF 150 million, one or two custodians) can reasonably start with a lighter PMS plus a dedicated compliance module, provided the two share client identifiers.
Turning FinSA segmentation, suitability and documentation into a requirements list
FinSA is conduct regulation, and conduct only survives an audit if your system records it. If your team knows MiFID II, the structure will feel familiar: classify clients, assess suitability, disclose costs and conflicts, document everything. The details are Swiss, though, so don't assume an EU-built platform covers them out of the box. Use the mapping below as the core of your FinSA compliance software requirements.
| FinSA duty | What the software must do | What an auditor typically asks to see |
|---|---|---|
| Client segmentation (retail, professional, institutional) | Store segment with effective date; manage opting-out and opting-in declarations with signed evidence; stop retail-only products being treated as professional | Segment history per client and the signed opt declarations |
| Suitability for discretionary mandates | Structured risk profile (knowledge, experience, financial situation, objectives, risk capacity); link each portfolio to an investment strategy; periodic review reminders | Profile version in force when the strategy was agreed, plus review dates |
| Documentation and accountability | Immutable log of agreed services, client information collected and suitability outcomes; long retention (confirm the period with your SO; ten years is a common planning assumption) | Sample client files reproduced end to end |
| Information on costs, risks and conflicts | Generate cost disclosures; record when they were delivered and acknowledged | Proof of delivery before service started |
| Retrocessions and third-party payments | Track inducements by client and product; support disclosure and waiver or pass-through logic | Reconciliation of received retrocessions to client disclosures |
| Key information documents for retail clients | Attach and log the relevant basic information document when it's required | Delivery records for in-scope transactions |
| Reporting to clients | Periodic statements on services, composition, valuation and costs | Report samples and the generation schedule |
Retrocessions get extra attention because they're a recurring source of disputes in Switzerland. A system that can't attribute trailer fees and other inducements to individual clients forces manual reconciliation every quarter. Ask vendors to demonstrate this on a sample dataset with at least two custodians, not in slides.
Mandate controls and pre-trade checks
Suitability on paper means little if a portfolio drifts outside its agreed strategy. Require rules-based restriction monitoring: asset class bands, single-issuer limits, currency limits, ESG or client-specific exclusions, and leverage or derivative constraints. Pre-trade checks at order entry are the stronger control; post-trade daily checks are the minimum. Either way, the system should log the breach, the reviewer and the resolution.
The AML file
Look for an onboarding workflow that captures beneficial-owner declarations, source-of-wealth narratives with supporting documents, risk classification, and sanctions and PEP screening through an integrated data provider. Your clients may live in the Gulf, Latin America, the EU or Asia, so the system must also handle multiple tax residencies and nationalities per person. It should flag cross-border servicing constraints too, because rules on actively serving clients abroad differ by country.
Multi-custodian data feeds decide your go-live date
Most Swiss independent asset managers book client assets at several banks: large Swiss private banks, cantonal banks and often custodians in Luxembourg, Monaco, Singapore or Dubai. Your independent asset manager software is only as good as the position and transaction data those institutions send. Feed onboarding is where projects slip most often.
Data typically arrives in one of three ways. Some banks send SWIFT statements such as MT535 (holdings), MT536 (transactions) and MT940 or MT950 (cash). Others deliver proprietary files over SFTP. Some vendors go through a third-party aggregator that has already normalized many banks. Each route works. What matters is who builds and maintains the mapping when a bank changes its format, and who pays.
Before a bank releases any data, it needs authorization. Client data is protected by banking secrecy, so the bank will require client consent, usually in the limited power of attorney or a separate data-release form. On a migration, collecting those forms for hundreds of clients across several banks can take longer than the technical work. Start the week you sign the vendor contract, not after.
Questions that separate strong vendors from weak ones:
- How many of my custodians are live today, in production, with other clients? Ask for the list and the number of firms using each connector. A connector that's merely "on the roadmap" adds months of uncertainty.
- Who absorbs format changes? The contract should state the vendor's response time when a bank alters its file layout.
- What's the reconciliation model? You want daily automated position and cash reconciliation against the bank record, with breaks queued for review. Silent overwrites of your book with bank data are a red flag.
- How are corporate actions, accrued interest and FX handled? These drive most performance and fee errors.
- Can the platform hold non-bankable assets? Private equity commitments, real estate, private loans and art are common in Swiss private-client portfolios and often appear in consolidated reporting.
- Does performance follow a recognized method? Time-weighted returns for strategy reporting, money-weighted for client views, and fee calculation driven directly from the reconciled data.
For planning, budget roughly two to six weeks per custodian where a production connector exists, and two to four months where one must be built. Feeds usually arrive T+1, which suits reporting and post-trade controls but limits intraday pre-trade checks. Make sure your order workflow accounts for that.
Vendors active with Swiss independent managers include Swiss providers such as Expersoft (PM1), Assetmax and Profidata, international platforms such as Avaloq, QPLIX, Addepar and Masttro, and CRM-focused tools that sit alongside a PMS. Custodian coverage varies a lot, so treat any shortlist as a starting point and check connectors against your own bank list.
Hosting, data residency and secrecy under the revised Swiss data protection act
The revised Federal Act on Data Protection (FADP), in force since September 2023, doesn't impose a blanket rule that client data must stay in Switzerland. It allows transfers to countries the Federal Council recognizes as adequate, which include EU and EEA states and the UK. Transfers to US organizations certified under the Swiss-US Data Privacy Framework are also permitted. Elsewhere, you need safeguards such as standard contractual clauses adapted for Swiss law, usually supported by a transfer risk assessment.
For an asset manager, though, the FADP is only one layer. Professional secrecy duties can apply to financial institutions and their staff, and breaches can carry criminal penalties. Your custodian banks are bound by banking secrecy and will expect you to protect the data they release. Many private clients also expect, and sometimes contractually require, that their data stays in Switzerland. That's why most Swiss independent managers choose Swiss hosting even where the law doesn't strictly demand it.
Practical options, broadly in order of how often they're chosen:
- Vendor SaaS hosted in Swiss data centers, run by a Swiss colocation provider or in a hyperscaler's Swiss region (Microsoft, Google Cloud and AWS all operate regions in Switzerland). It's the simplest to defend to clients and auditors.
- Vendor SaaS hosted in the EU, with contractual and technical safeguards. It's legally workable, but expect more questions from clients and your SO, and document the analysis.
- On-premises or private cloud, now rarer and expensive to run securely for firms under about 20 staff.
Hosting location alone doesn't settle foreign access. A Swiss data center run by a company with a foreign parent may still face foreign legal requests. Ask about encryption key management: who holds the keys, whether client-identifying data can be pseudonymized, and where support staff with production access sit.
FADP duties the system and vendor contract should support:
- A record of processing activities. Smaller firms may be exempt unless processing is high risk, but many asset managers keep one anyway because it helps with audits.
- Data protection impact assessments where processing poses high risk, such as large-scale profiling.
- Breach notification to the Federal Data Protection and Information Commissioner as soon as possible when a breach is likely to pose a high risk, which requires the vendor to notify you promptly.
- Subject access requests answered from a single client view, plus deletion or restriction once retention periods expire.
- A sub-processor list with advance notice of changes and a right to object.
If you serve clients resident in the EU, the GDPR may also apply in some circumstances. Rules on servicing clients in the Gulf, Asia or Latin America add their own data and marketing restrictions. Treat outsourcing as a governance matter too: auditors will expect vendor due diligence, audit and information rights, defined service levels, and a tested exit plan that returns your data in a usable format.
Indicative costs, implementation timelines and a worked example
Pricing for Swiss asset managers usually combines a platform fee (per user, per portfolio or in basis points on assets), per-custodian feed fees and one-off implementation. The figures below are typical 2026 market ranges in USD. Contracts are often priced in CHF, exchange rates move, and vendors quote very differently by scope, so confirm every number with the vendor.
| Cost item | Small firm (under CHF 300m, 2-6 staff) | Mid-size firm (CHF 300m-1.5bn, 6-25 staff) | Main cost drivers |
|---|---|---|---|
| Annual platform license (PMS + client file) | $25,000-70,000 | $70,000-250,000 | Users, portfolios, modules, AUM-based tiers |
| Compliance, AML and screening modules | $8,000-30,000 per year | $25,000-90,000 per year | Screening data provider, transaction monitoring depth |
| Custodian feeds | $1,500-6,000 per custodian per year | $1,500-6,000 per custodian per year, sometimes bundled | Existing connector vs new build; aggregator fees |
| Implementation and migration (one-off) | $20,000-80,000 | $80,000-300,000 | History migrated, number of custodians, reporting templates |
| Internal effort | 0.3-0.5 FTE during project | 1-2 FTE during project | Data cleanup, client consent collection, testing |
Timelines follow a predictable pattern. Vendor selection with proper demonstrations takes six to ten weeks. Contracting and data protection review add two to six. Implementation runs roughly three to five months for a small firm with existing connectors, and six to nine months for a mid-size firm with several custodians, a non-bankable book or a full transaction history migration. Allow a parallel run of at least one month-end, ideally a quarter-end, before switching off the old system.
Worked example (hypothetical)
Say a Geneva-based manager has eight staff, CHF 650 million under management, 240 clients and six custodians: four Swiss banks, one in Luxembourg and one in Singapore. Five of the six connectors already exist on the shortlisted platform. The Singapore feed needs a new build.
- Platform license, priced in the upper half of the mid-size range: roughly $105,000-120,000 per year.
- Compliance and screening module: about $40,000 per year.
- Six feeds at about $3,000 each: around $18,000 per year.
- Implementation with two years of transaction history: $120,000-160,000 one-off.
- Timeline: eight weeks of selection, four of contracting, five months of implementation for the five existing feeds, with the Singapore feed live about two months later. Client consent collection runs in parallel from week one.
First-year cash outlay lands around $285,000-340,000, then about $165,000-180,000 a year. The firm can then judge whether that's justified by audit readiness, fewer reconciliation hours and room to grow without hiring operations staff.
Red flags during selection
- Custodian connectors described as "available" with no production clients using them.
- No Swiss reference clients who have gone through an SO audit on the platform.
- Suitability profiles that can be edited without version history.
- Retrocession tracking handled "in Excel export."
- Hosting location or sub-processors that change without contractual notice.
- Exit terms that return data only as PDFs or at extra cost.
Next step: put your custodian list, client segments and current audit findings into a two-page requirements brief, send it to three or four vendors, and require a scripted demonstration on your own anonymized data. Before you sign, have a Swiss compliance adviser review the FinSA documentation workflow and the outsourcing contract, and ask a data protection specialist to check the hosting and transfer setup. Decision rule: if a vendor can't show production connectors to at least two-thirds of your custodians, drop it from the shortlist.
Questions buyers ask
Does FinIA require a specific portfolio management system?
No. Neither FINMA nor the supervisory organizations prescribe software. They require adequate organization, risk management, internal controls and documentation, and your systems must be able to show these to auditors. In practice, firms with several custodians struggle to meet those expectations without an integrated platform.
Must client data be hosted in Switzerland under the revised FADP?
Not strictly. The FADP permits transfers to countries recognized as adequate, such as EU and EEA states and the UK, and to certified US organizations under the Swiss-US Data Privacy Framework. Other destinations need safeguards like adapted standard contractual clauses. Many asset managers still choose Swiss hosting because of professional secrecy, custodian expectations and client contracts, so check your specific obligations with a data protection adviser.
How long does it take to connect a new custodian bank feed?
Where the vendor already runs a production connector, roughly two to six weeks per bank is typical, mostly spent on testing and client consent forms. If a connector must be built, plan for two to four months. Collecting client data-release authorizations is often the slowest step, so start early.
Can a small asset manager use one tool for both portfolio management and FinSA compliance?
Yes, and for most small firms it's the better choice, because suitability, segmentation and mandate restrictions then sit on the same client record as the portfolio. If you combine separate tools, make sure they share client identifiers and that compliance records carry timestamps and version history. Otherwise, rebuilding a client file for an audit becomes manual work.
What do supervisory organization auditors typically check in the system?
They usually sample client files and trace them end to end: segmentation and opt declarations, the suitability profile in force when the mandate started, cost and conflict disclosures, restriction monitoring and how breaches were handled. They also review AML files and outsourcing arrangements. Your software should reproduce these records quickly, without manual compilation.
Is MiFID II-ready software automatically FinSA-compliant?
No. FinSA's structure resembles MiFID II, but Swiss specifics differ, including retrocession treatment, Swiss basic information documents and local segmentation rules. Ask the vendor to demonstrate each FinSA duty on Swiss sample data, and have a Swiss compliance adviser confirm the setup before go-live.
Written by the Vaultgridplus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.