Trustdeskapp.
Buyer's Guide

Eight Mistakes Wealth Managers Make When Buying Client Reporting Software

Most regrets about reporting platforms start in the evaluation, not the software. Here are eight common buying mistakes, each paired with the test or contract term that prevents it.

Trustdeskapp editorial team · November 2026 · 9 min read

Mistake one: scoring the demo on the vendor's sample data

The system you're choosing will put your firm's numbers in front of every client, every quarter, for years. Switching later is expensive. It usually means a migration project, at least one or two quarters of parallel running, and sometimes historical return series rebuilt by hand. Most problems firms discover after signing for client reporting software for wealth managers were visible beforehand to anyone who tested for them. Here are eight common mistakes and the test or contract term that heads off each one.

The first is letting the vendor run the demo on its own data. Demo environments are built to flatter. Every security is priced, every corporate action is clean, and every account has one currency and one custodian. Your book doesn't look like that. It has structured notes priced monthly, a private equity fund with capital calls, a trust with three beneficiaries and an account that changed custodians mid-year.

Advertisement

What to do instead: Before the second meeting, send the vendor an anonymized data pack covering five to ten real households, with about two years of transactions, positions and prices from your current system or custodians. Ask for a scripted demo that loads this data and reproduces your current quarterly report pack. If a vendor won't do this for a serious prospect, that's a preview of how implementation will go. Firms with more than a few hundred accounts should consider a paid proof of concept. Fees typically fall somewhere in the $10,000–$50,000 range in the 2026 market, though they vary by vendor and scope. Some vendors credit the fee against the license if you sign, so ask for that in writing.

Mistake two: assuming the return figures will match your own

Two well-built platforms can report different returns for the same portfolio and both be correct. The differences come from method choices that rarely come up in a sales cycle:

  • Time-weighted method: true daily valuation, or Modified Dietz with monthly chain-linking. The gap widens in months with large flows unless the system revalues the portfolio when they happen.
  • Money-weighted returns: whether IRR is available alongside TWR. You need it for private markets and for clients who decide when they add or withdraw money.
  • Fee treatment: gross versus net, accrued versus paid, and how fees billed outside the portfolio are handled.
  • Accounting basis: trade date versus settlement date, and whether dividends and bond interest are accrued.

What to do instead: Run a known-answer test. Pick three to five portfolios whose returns you already trust, including one with a large mid-month flow and one with an illiquid holding. Ask the vendor's performance reporting software to reproduce them. Set a tolerance in advance, for example a couple of basis points per month, and require a written explanation for every difference beyond it. Then attach the vendor's methodology document to the contract as a schedule and require advance notice, say 90 days, of any change to calculation methods.

Be skeptical of any claim of GIPS compliant reporting. Under the GIPS standards, only firms and asset owners can claim compliance. Software can't. A platform can support compliance by managing composite membership rules, keeping an auditable record of when portfolios joined and left composites, calculating internal dispersion and producing what your verifier will ask for. If a vendor calls its product "GIPS-certified," ask exactly what that means, and ask for a reference firm whose verification was done on the system.

Mistake three: underestimating multi-custodian data feeds

Feeds are where most implementations run late. When a vendor says it "supports" hundreds of custodians, that can mean a daily production feed used by dozens of clients, a file format mapped once for one client, or simply "we can build it." Data arrives as SWIFT messages (MT535 holdings, MT536 transactions, MT940/950 cash statements, with ISO 20022 equivalents increasingly common for cash), proprietary files over SFTP, APIs and, at some institutions, PDF statements only. Smaller private banks, regional custodians and alternative fund administrators cause the most trouble.

What to do instead: Give the vendor every custodian and administrator you use, with account counts. Ask it to place each one in a category: live in production with reference clients you can call, buildable with an estimated timeline, or manual upload only. Ask how often each feed produces reconciliation breaks and what time reconciled T+1 data is usually ready each morning.

A hypothetical example: say a multi-family office in Dubai uses nine custodians across Switzerland, Singapore, the UK and the UAE. The vendor has six live. The other three need new builds, each taking a few months and priced within the feed-build range in the cost table below. If none of that is pinned down in the contract, either go-live slips or a third of your assets are uploaded by hand for months.

The contract should name each feed with a target go-live date, fix the price of future feed builds and include a data-timeliness service level backed by service credits. It should also say who pays when a custodian charges for data access. Some do, and the charges vary by bank and region.

Mistakes four and five: single-currency thinking and skipping cost disclosures

Cross-border client books quickly expose platforms built for one domestic market. Multi-currency reporting means more than converting the totals. Check whether each client or entity can have its own reporting currency, which FX source and fixing time the system uses, and whether it can split returns into local-market return and currency effect. Ask how it treats hedged share classes. Multilingual output has the same trap. Translating labels is easy. The hard part is swapping disclaimers, commentary and regulatory notices by jurisdiction, rendering right-to-left Arabic and Chinese characters correctly in PDFs, and formatting numbers and dates for the client's locale.

What to do instead: Put one hard case in your data pack, such as a CHF-based report for a client holding USD, EUR and SGD assets, produced in both English and Arabic. Read every page of the output, not just the summary.

The fifth mistake is assuming the platform takes care of your disclosure obligations. In the EU, MiFID II requires costs and charges disclosure both ex-ante and in an annual ex-post report. Service costs, product costs and third-party payments must be aggregated, shown in cash and percentage terms, and accompanied by an illustration of their cumulative effect on return. Product costs usually come from fund manufacturers via the European MiFID Template (EMT), so the system must ingest that data, store it and allocate it to each client's holdings. The UK now has its own disclosure rules, which have diverged from the EU's. Elsewhere, the SEC's Marketing Rule in the US governs how gross and net performance are presented, and regulators in India, Singapore and Hong Kong set their own requirements for fee and performance disclosure.

Give the vendor one anonymized client and ask it to produce your ex-post costs and charges report, including product costs from EMT data. Then have your compliance team or an external regulatory adviser check the output against the rules in each jurisdiction where you have clients.

Mistakes six and seven: treating the portal as an add-on and misreading the price

Clients rarely read the PDF. They read the app. Yet many firms judge wealth client portal software from a five-minute walkthrough at the end of a demo. Check for white-labeled iOS and Android apps, a document vault with read receipts, multi-factor authentication, and delegated access for family members, accountants and lawyers. Most important, household and entity views must match the consolidated report exactly. When the portal shows one number and the quarterly PDF shows another, the client calls their adviser.

What to do instead: Run a two-week pilot with a few staff, or willing clients, logging in on their own phones. Count the questions they raise.

The seventh mistake is comparing headline license fees when most of the cost sits elsewhere. The figures below are typical 2026 market ranges. They vary widely by contract, region and firm size, so confirm them with each vendor.

Cost componentCommon pricing basisIndicative range (USD)What to negotiate
Platform licensePer account, per household or basis points on AUM$15k–$60k/yr (small firms); $60k–$250k/yr (mid-size); $250k+/yr (enterprise)Price bands that don't jump on small AUM increases
ImplementationFixed fee or time and materialsRoughly 0.5x–1.5x first-year licenseA fixed fee paid against go-live milestones
New custodian feedsPer feed$5k–$30k eachPrices fixed in the contract
Portal and mobile appAdd-on module or per user$10k–$80k/yrBranding included, no per-login fees
Custom report templatesPer template or day rate$1k–$5k per templateA prepaid bank of template hours

AUM-based pricing looks cheap at signing. But if markets rise sharply in a year, your bill rises with them even if you add no clients. If you accept AUM pricing, negotiate an annual cap on increases.

Mistake eight: signing without exit and data-residency terms

Firms negotiate the way in and forget the way out. Your historical return series, composite history and audit trails are regulated records, and you may need them for years after leaving a vendor. Data residency matters as well, and the rules depend on jurisdiction. The EU and UK GDPR, Switzerland's FADP, Saudi Arabia's PDPL, India's DPDP Act, Singapore's PDPA and the DIFC data protection law each govern where client data can be stored or transferred and who may access it, and they don't all do it the same way. Before signing, find out which hosting regions the vendor offers, get its subprocessor list, and ask where support staff can view client data from. Have your data-protection counsel confirm what each relevant jurisdiction requires.

Write these terms into the contract:

  1. A full export at exit of transactions, positions, prices, calculated returns and composite membership history, in a documented, machine-readable format, either free or at a stated fee.
  2. A transition-assistance period, typically 6–12 months, at existing rates.
  3. Data retention for a defined period after termination, followed by certified deletion.
  4. A named hosting region, with advance notice of any change in subprocessor or location.
  5. The methodology schedule and feed list described above, both binding.

Cut your shortlist to three vendors and run the known-answer performance test first. Nothing eliminates vendors faster. If a platform can't reproduce your numbers, stop evaluating it.

Quick answers

Can buying a reporting platform make our firm GIPS compliant?

No. Under the GIPS standards, only firms and asset owners can claim compliance, and compliance covers your policies, composites and presentations as well as your calculations. Good software makes compliance easier to maintain and verify by handling composite rules, dispersion and audit trails. Talk to a GIPS verifier about what your firm needs before you choose a vendor.

How long does implementation of client reporting software usually take?

It depends mostly on data complexity. A single-custodian firm with a simple product range can often go live within a few months. Multi-custodian, multi-currency firms with private assets and family entities commonly take most of a year or longer, and new custodian feeds are the usual cause of delay. Plan for at least one quarter of parallel reporting before you switch off the old system.

Is it better to buy reporting as part of a full wealth platform or as a standalone tool?

It depends on where your data comes from. An integrated platform that covers portfolio management, trading and reporting cuts reconciliation between systems, at the cost of depending on one vendor for everything. Standalone reporting and aggregation tools are usually stronger at multi-custodian consolidation and alternative assets, which suits family offices and firms using several booking centers. If you run on one custodian or core system, choose the integrated platform. If you deal with many custodians, choose a specialist.

Written by the Trustdeskapp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.