PureFacts Research

The Revenue Leakage Map

Where wealth management firms lose earned revenue and why current systems miss it.

$0T
Global AUM by 2030
0%
Profit per AUM decline since 2018
$0M
1bp exposure on $250B AUM
0%
Asset managers under profit pressure

Executive Summary

Revenue leakage in wealth management is rarely the result of one broken calculation. It is the cumulative loss of earned revenue caused by gaps between client agreements, account data, householding logic, investment strategy structures, fee schedules, valuation feeds, billing operations, collections, advisor compensation, and executive reporting. The problem hides between systems and therefore cannot be solved by treating billing as a standalone back-office utility.

The economics of wealth management make that gap more costly than it used to be. Global assets under management are projected to grow from US$139 trillion in 2024 to US$200 trillion by 2030, but PwC reports that profit per AUM is down 19% since 2018 and that 89% of surveyed asset managers experienced profitability pressure over the prior five years. In U.S. wealth advice, McKinsey estimates that fee-based advisory relationship revenue grew from approximately $150 billion in 2015 to $260 billion in 2024. Cerulli reports that 83% of advisors expect to charge less than 1% by 2026 for clients with more than $5 million in investable assets.

A one-basis-point miss on $250 billion in AUM is $25 million of annual gross revenue exposure before any tax, compensation, or margin assumptions.

A modern household may include multiple account registrations, an advisory program, a UMA, one or more SMA strategies, private assets, cash exclusions, security-level exclusions, negotiated discounts, tiered household breakpoints, tax overlays, third-party manager fees, advisor team splits, and billing in arrears. Each term may be reasonable in isolation. Together, they create an operating model that many systems cannot fully express, monitor, reconcile, and evidence.

The Central Argument

A billing engine calculates fees. A revenue management architecture governs whether the right agreement terms, account data, investment strategy rules, approvals, calculations, collections, payouts, and reporting all reconcile to the same revenue truth.

01

Why Fee Billing Became More Complex

A decade ago, many wealth billing models were comparatively straightforward: account-level AUM fees, standard schedules, quarterly billing, liquid public-market assets, and a limited set of discounts or exclusions. Those models still exist, but they are no longer the whole business. Large firms now monetize advice through a wider range of products, service levels, account structures, investment programs, and advisor team arrangements.

The complexity did not arrive all at once. It accumulated through a series of industry shifts.

Complexity driverOperational impact
Household and relationship pricingMultiple accounts, entities, trusts, spouses, and related relationships must be aggregated for pricing, breakpoint, discount, and service-tier logic.
Program and strategy-level feesUMA, SMA, model, direct-indexing, tax-overlay, and third-party manager structures introduce sleeve-, strategy-, or product-level billing rules.
Asset eligibility rulesCash, alternatives, restricted securities, employer stock, held-away assets, annuities, and private assets may each require different inclusion, exclusion, valuation, or disclosure treatment.
Bespoke client economicsNegotiated discounts, temporary waivers, pricing concessions, service tiers, retainer fees, and grandfathered arrangements require durable configuration and expiry logic.
Advisor teams and compensation complexityRevenue must flow into team splits, succession arrangements, referral credits, payout grids, and advisor statements that match the billing economics.
M&A and platform conversionAcquired books bring legacy agreements, undocumented exceptions, paper fee schedules, and conversion-era patches into the revenue stack.

Complexity is manageable when the rules are explicit, versioned, automated, and reconciled. It becomes leakage when the rules live across contracts, spreadsheets, CRM fields, portfolio systems, billing engines, advisor desktops, and compensation workbooks that do not share the same revenue truth.

02

A Typical Complex Fee Structure: How Leakage Happens in Practice

Consider a $10 million high-net-worth household. The relationship is not unusual for a large wealth firm, but it is complex enough to expose why leakage hides in the seams between systems.

Household componentFee or operating ruleWhy it matters
Four related accountsTaxable account, IRA, revocable trust, and family LLC account treated as one economic household.If the accounts are not linked, breakpoints, service tiers, reporting, and advisor payout logic can all be wrong.
Tiered household scheduleFirst $5M at 75 bps; assets above $5M at 55 bps; billed quarterly in arrears.The platform must support household aggregation, marginal tier logic, arrears billing, and period-end valuation.
6-month introductory discountA 10 bps discount applies for the first two billing cycles only.Without an expiration control, a temporary concession becomes a recurring leakage event.
UMA with multiple sleevesThe UMA includes model sleeves, a tax overlay, and a direct-indexing sleeve.Billing may need to distinguish program fees, overlay fees, underlying manager fees, and excluded positions.
SMA strategyA separately managed account has a strategy-level fee and a third-party manager fee.If the strategy is coded as non-billable or the manager fee is handled outside the billing system, fee capture and reporting diverge.
Cash and security exclusionsCash above a threshold and a concentrated employer-stock position are excluded from advisory billing.The system must apply exclusions at the correct asset, account, and period level, not as a broad account override.
Private assetA private credit position is valued quarterly and billed only when a current valuation is available.Late or stale valuations can cause underbilling, overbilling, delayed billing, or manual adjustments.
Mid-quarter fundingThe client contributes $500,000 halfway through the billing period.Proration must reflect timing, eligible assets, and household rate logic.
Advisor team splitRevenue is split 70/30 between lead advisor and service advisor.Compensation must use the same collected revenue and household economics as finance and billing.

Illustrative leakage exposures on a single $10M household

$10,000/yr
Discount expiry
10 bps persisting on $10M after the introductory period should have expired
$7,800/yr
Strategy fee capture
$1.2M SMA sleeve at 65 bps coded as non-billable due to external manager fee
$2,750/yr
Cash exclusion error
$500K incorrectly excluded at 55 bps when only cash above the threshold should be excluded
$1,100/yr
Stale private valuation
$200K of billable private-credit value falling out of the fee run
$688
Mid-period proration
$500K mid-quarter deposit not prorated at 55 bps for half a quarter
Full invoice
Failed collection
Calculated revenue never becomes collected revenue due to unretried failed debit

None of these leakage points requires a dramatic failure. Each can look like a reasonable exception, data gap, product nuance, or manual adjustment. At enterprise scale, the same patterns repeat across thousands of households, advisors, products, and billing cycles.

03

The Revenue Leakage Diagnostic

The following diagnostic shows where earned revenue breaks inside the operating model, why the break happens, who typically owns it, and what control is required. Large firms can use this as a discovery tool, control checklist, and business-case structure for billing or revenue architecture modernization.

Contract and disclosure alignment

Failure points: Agreement terms, service commitments, disclosures, and billing setup do not match.
Why missed: Document systems, CRM, and billing platforms do not share executable contract terms.
Control needed: Contract-to-billing mapping; approved template control; evidence retention.

Client and household data

Failure points: Related accounts, trusts, entities, spouses, or advisor relationships not linked correctly.
Why missed: CRM householding, billing householding, and compensation hierarchies use different definitions.
Control needed: Authoritative household rules; master data governance; automated relationship matching.

Investment strategy and product structure

Failure points: UMA/SMA sleeves, strategy fees, manager fees, overlays, alternatives not represented consistently.
Why missed: Portfolio systems understand positions and strategies, but billing systems may not express strategy-level economics.
Control needed: Product and strategy fee taxonomy; sleeve-level rules; manager-fee and overlay-fee controls.

Asset classification and valuation

Failure points: Cash, alternatives, annuities, private assets, employer stock included or excluded incorrectly.
Why missed: Asset classifications change across custodian, portfolio, product, and billing systems.
Control needed: Billable-asset taxonomy; valuation controls; exception monitoring for stale or missing values.

Fee schedule and calculation

Failure points: Wrong rate, tier, breakpoint, billing frequency, day-count, or proration rule applied.
Why missed: Fee logic is configured locally, patched manually, or not versioned against agreement terms.
Control needed: Versioned fee library; deterministic calculation engine; regression testing of fee rules.

Discounts, waivers, and exceptions

Failure points: Temporary discounts become permanent; credits and waivers lack reason codes or approval evidence.
Why missed: Exceptions sit in emails, spreadsheets, or account notes instead of controlled workflows.
Control needed: Approval workflow; expiry dates; reason codes; exception aging and review.

Billing operations and reconciliation

Failure points: Late feeds, manual adjustments, aged exceptions, unresolved variances disrupt fee runs.
Why missed: Operations can resolve individual breaks but cannot always identify root causes or recurring patterns.
Control needed: Reconciliation workflow; exception queues; GL/custodian/billing tie-out; root-cause reporting.

Collection and adjustments

Failure points: Direct-bill invoices age; failed debits not retried; credits and write-offs not classified.
Why missed: Billing output is not fully connected to AR, collections, client servicing, and profitability analytics.
Control needed: Collections workflow; failed-payment escalation; write-off governance; collected-revenue reporting.

Advisor compensation and payout

Failure points: Compensation based on billed rather than collected revenue; splits do not match client-level economics.
Why missed: Compensation runs on a separate data model from billing and finance.
Control needed: Integrated payout engine; advisor statements; split governance; dispute workflow.

M&A, conversion, and migration

Failure points: Legacy fee schedules, grandfathered terms, paper agreements not digitized cleanly.
Why missed: Conversion teams often map accounts and positions before they fully map revenue terms.
Control needed: Fee-term digitization; migration controls; post-conversion testing; sunset logic for temporary patches.

Reporting and analytics

Failure points: Executives cannot see eligible, billed, collected, compensated, and adjusted revenue by owner or root cause.
Why missed: Reporting aggregates outcomes but does not preserve the lineage of data, rules, and decisions.
Control needed: Revenue waterfall; leakage KPIs; owner-level dashboards; audit trail.

Pattern to note

Leakage clusters where ownership changes hands: contract to billing setup, household data to fee logic, product strategy to asset eligibility, fee calculation to collection, collection to compensation, and operations to executive reporting. These seams are the places large firms should test first.

04

Why Current Systems Miss Leakage

Large wealth firms are not underinvested in technology. They often operate modern CRMs, portfolio accounting systems, billing platforms, custodian feeds, data warehouses, advisor desktops, compensation tools, and reporting environments. Leakage persists because each system solves part of the operating model, while revenue depends on the whole model working together.

Technical Limitations

  • Account-centric architecture: many systems are organized around accounts and positions, while wealth economics are often household-, strategy-, team-, or service-tier-based.
  • Static fee configuration: many billing setups handle standard schedules well but struggle with temporary discounts, conditional terms, strategy-level rules, and exception expiry.
  • Product taxonomy gaps: portfolio systems may know the security or model, but not whether that exposure is billable, excluded, wrapped, rebated, or subject to an overlay fee.
  • Semantic integration gaps: APIs move fields, but do not automatically reconcile the meaning of household, account, product, advisor, team, fee schedule, or collected revenue.
  • Calculation without context: a billing engine can calculate exactly what it is told, even when the upstream household, asset class, contract term, or discount rule is wrong.
  • Reporting without lineage: dashboards may show revenue outcomes without preserving the policy version, data inputs, approvals, overrides, collections, and payouts that produced them.

Operational Limitations

  • Exceptions leave the control environment: one-off discounts, overrides, and reconciliation patches are often managed in email or spreadsheets.
  • Product launches outpace billing governance: new strategies, overlays, private assets, or fee treatments enter the business before the fee taxonomy is fully governed.
  • M&A creates inherited complexity: acquired books bring legacy terms, undocumented concessions, and account structures that may not map cleanly into the target platform.
  • Ownership is diffused: distribution, compliance, operations, finance, data, technology, and compensation each own part of revenue integrity, but no single function owns the full lifecycle.
  • Manual fixes become permanent process: teams solve the current billing cycle under time pressure, but the underlying root cause remains for the next cycle.
  • Advisor trust is affected: when statements are late, opaque, or disconnected from billing outcomes, advisors build shadow ledgers and disputes become a signal of upstream leakage.

A Practical Test

Ask distribution, operations, finance, compensation, and compliance to produce the same household revenue waterfall for the prior quarter: contracted revenue, approved adjustments, billed revenue, collected revenue, advisor payout, and unresolved exceptions. If the numbers do not reconcile without manual intervention, the firm does not yet have revenue integrity.

05

The Economics of Leakage

Revenue leakage becomes a board-level issue because small basis-point differences scale quickly across enterprise AUM. The models below are illustrative and are not intended to assert a universal industry leakage rate; each firm should substitute its own AUM, realized yield, payout ratio, margin, and valuation assumptions.

Model 1: What one basis point means (60 bps realized yield)

AUMGross revenue at 60 bps1 bp exposure2 bp exposure3 bp exposure
$50B$300M$5M$10M$15M
$250B$1.5B$25M$50M$75M
$750B$4.5B$75M$150M$225M
$1.5T$9.0B$150M$300M$450M

Model 2: 2% revenue leakage scenario (30% EBITDA conversion, 13x EV multiple)

AUMGross revenue2% leakageEBITDA impactEV impact
$50B$300M$6M$1.8M$23M
$250B$1.5B$30M$9.0M$117M
$750B$4.5B$90M$27.0M$351M
$1.5T$9.0B$180M$54.0M$702M

Enterprise-scale firms do not need large error rates to create large exposure. A temporary discount without an expiry, a strategy fee coded incorrectly, an unlinked household, or a conversion mapping error can compound quietly across years.

06

Regulatory Proof Points: Why Precision Now Matters More

The primary reason to control leakage is economic: firms should capture the revenue they have earned and avoid margin dilution. But the regulatory record shows that fee and revenue-control failures can also create remediation, penalty, and reputational costs.

2018

SEC Advisory-Fee Risk Alert

Identified common deficiencies including fee billing based on incorrect account valuations; billing in advance or with improper frequency; applying incorrect fee rates; omitting rebates or applying discounts incorrectly, including householding and breakpoint failures; disclosure issues; and adviser expense misallocations.

2023

Wells Fargo Advisors Settlement

The SEC charged two Wells Fargo advisory firms with overcharging more than 10,900 investment advisory accounts by more than $26.8 million. Agreed reduced advisory fee rates were handwritten into client agreements but not entered into the firms' billing systems. Wells Fargo paid a $35 million civil penalty and reimbursed affected accountholders approximately $40 million including interest.

2025

SEC: $60M in Combined Civil Penalties

The SEC announced $60 million in combined civil penalties against Wells Fargo Advisors and Merrill Lynch relating to cash sweep program policies and procedures.

2025

FCA Ongoing Advice Services Review

The FCA told firms to ensure consumers receive the services they are paying for, with attention to contracts, evidence, monitoring, and redress where needed.

2026

CIRO Enhanced Cost Reporting

Canada's CIRO enhanced cost reporting amendments take effect January 1, 2026, requiring more transparent client reporting of investment fund costs and charges.

Practical expectation for large firms

What is promised, configured, billed, collected, compensated, and reported must be reconcilable. The stronger the audit trail, the lower the cost of answering questions from regulators, auditors, clients, advisors, and acquirers.

07

The Control Model: From Billing Accuracy to Revenue Integrity

The operating model for leakage reduction has six layers. Each layer is necessary; none is sufficient alone.

Layer
What it governs
Control objective
Policy
Version-controlled fee schedules, discount rules, householding definitions, asset eligibility rules, proration logic, compensation rules, and exception authorities.
Every revenue-affecting calculation can be traced to an approved policy version.
Data
Authoritative client, household, account, product, strategy, asset, advisor, team, rep-code, and service-tier data.
The same relationship and economic facts are used across CRM, billing, compensation, finance, and reporting.
Calculation
Configurable fee and compensation logic across tiered, blended, marginal, performance, retainer, project, advisory, and hybrid structures.
Results are deterministic, reproducible, and tied to the data and policy version used.
Workflow
Approval, exception, adjustment, reconciliation, migration, collections, and dispute workflows embedded in the system.
Revenue-impacting events happen inside a controlled workflow with owner, reason code, timestamp, and evidence.
Analytics
Reporting that shows eligible revenue, approved adjustments, billed revenue, collected revenue, compensated revenue, and realized yield.
Leakage is measurable by source, owner, segment, advisor, household, product, and trend.
Audit trail
Evidence of policy changes, data changes, approvals, calculation runs, invoice adjustments, collections, payouts, and overrides.
The firm can answer regulatory, audit, client, advisor, and M&A diligence questions without reconstruction.

Instead of asking whether the billing engine calculated the fee correctly, the firm asks whether the entire revenue lifecycle is governed: was the right contract term captured, the right household identified, the right asset base classified, the right invoice collected, the right advisor paid, and the right revenue reported?

08

What to Look for in a Modern Revenue Management Architecture

Once leakage is viewed as a lifecycle issue, the architecture question becomes clearer. A firm may still need to replace or modernize its billing engine. But the evaluation should test whether the future-state platform can support the full revenue management model, not just fee calculation.

01Maintain a single, governed source of revenue policy, including fee schedules, discount approvals, asset-eligibility rules, householding definitions, proration logic, strategy fee rules, and compensation rules.
02Translate contracts, service terms, and product structures into executable billing, monitoring, and reporting rules.
03Use authoritative client, household, account, asset, advisor, team, and strategy data across billing, compensation, finance, and reporting.
04Calculate complex fees and payouts across products, strategies, entities, custodians, advisors, teams, and channels.
05Prevent exceptions from leaving the control environment by embedding approvals, reason codes, adjustment workflows, collections workflows, and reconciliation processes.
06Track the revenue waterfall from eligible revenue to billed revenue to collected revenue to compensated revenue.
07Surface leakage drivers through analytics rather than waiting for complaints, disputes, close variances, or regulatory findings.
08Produce audit-ready evidence for any material fee, adjustment, override, invoice, payout, or policy change.

Five questions before replacing a billing system

  1. 1.Can the platform trace revenue from agreement terms through billing, collection, compensation, and reporting?
  2. 2.Can it compare eligible revenue, billed revenue, collected revenue, and compensated revenue?
  3. 3.Can it govern householding, fee schedules, discounts, exclusions, proration, product strategies, and exceptions from a single source of truth?
  4. 4.Can it use the same revenue data for finance, operations, advisor compensation, and executive analytics?
  5. 5.Can it produce an audit-ready explanation of every material fee, adjustment, override, invoice, payout, and policy change?

Conclusion

Capturing the Revenue Already Earned

Revenue leakage is not a single operational defect. It is the cost of allowing revenue decisions to fragment across systems, teams, and control environments. In a market defined by fee pressure, product complexity, advisor capacity constraints, M&A activity, and greater scrutiny of client economics, that fragmentation is too expensive to ignore.

The firms that reduce leakage will not simply run cleaner fee calculations. They will connect what was promised, configured, calculated, collected, distributed, and monitored and they will be able to prove that connection at scale.

The revenue is already there. The question is whether the firm has the operating model to capture it.

About PureFacts

PureFacts Financial Solutions provides revenue performance management solutions for wealth and asset management firms. PureFacts helps firms manage complex fee calculation and billing, advisor and team compensation, revenue analytics, workflow, and auditability so they can reduce leakage, strengthen controls, and turn revenue operations into a scalable enterprise capability.

Appendix A: Modeling Methodology and Assumptions

AssumptionHow to interpret it
AUM scaleIllustrative tiers of $50B, $250B, $750B, and $1.5T reflect regional, national, and enterprise wealth platforms.
Realized yieldA 60 bps yield is used for illustration. Firms should substitute actual realized yield by channel, product, client segment, and entity.
Basis point exposure1 bp equals 0.01% of AUM. The formula is AUM x (basis points / 10,000).
Revenue leakage percentageThe 2% scenario is illustrative. Firm-specific back-testing should determine actual exposure.
EBITDA conversionThe paper uses a 30% illustrative conversion rate after compensation and operating-cost effects.
Enterprise value multipleThe paper uses a 13x illustrative EBITDA multiple for sensitivity. Multiples vary by growth, margin, scale, channel, and market conditions.

Appendix B: Sources

  1. PwC, "Private markets to account for more than half of global asset management industry revenues by 2030 — PwC 2025 Global Asset & Wealth Management Report," November 24, 2025. https://www.pwc.com/gx/en/newsroom/press-releases/2025/pwc-2025-global-asset-wealth-management-report.html
  2. McKinsey & Company, "The looming advisor shortage in US wealth management," February 10, 2025. https://www.mckinsey.com/industries/financial-services/our-insights/the-looming-advisor-shortage-in-us-wealth-management
  3. Cerulli Associates, "Fee Compression and Rising Service Demands Cause Advisors to Adjust Pricing Structure," April 29, 2025. https://www.cerulli.com/press-releases/fee-compression-and-rising-service-demands-cause-advisors-to-adjust-pricing-structure
  4. Broadridge, "Mitigating revenue leakage in fee billing: Strategies for optimizing fee capture and billing accuracy," 2024. https://www.broadridge.com/_assets/pdf/mitigating-revenue-leakage-in-fee-billing_broadridge-white-paper.pdf
  5. U.S. Securities and Exchange Commission, OCIE, "Risk Alert: Overview of the Most Frequent Advisory Fee and Expense Compliance Issues," April 12, 2018. https://www.sec.gov/files/ocie-risk-alert-advisory-fee-expense-compliance.pdf
  6. U.S. Securities and Exchange Commission, "Wells Fargo Settles with SEC for Charging Excessive Advisory Fees," Press Release 2023-159, August 25, 2023. https://www.sec.gov/newsroom/press-releases/2023-159
  7. U.S. Securities and Exchange Commission, "SEC Charges Pair of Wells Fargo Advisory Firms and Merrill Lynch with Compliance Failures Relating to Cash Sweep Programs," Press Release 2025-16, January 17, 2025. https://www.sec.gov/newsroom/press-releases/2025-16
  8. Financial Conduct Authority, "Ongoing financial advice services," Multi-firm review, February 24, 2025. https://www.fca.org.uk/publications/multi-firm-reviews/ongoing-financial-advice-services
  9. Canadian Investment Regulatory Organization, "Enhanced Cost Reporting," Rules Bulletin 25-0176, July 3, 2025. https://www.ciro.ca/newsroom/publications/enhanced-cost-reporting
  10. Charles Schwab Advisor Services, "2025 RIA Benchmarking Study: Growth drivers and performance," 2025. https://advisorservices.schwab.com/insights-hub/perspectives/ria-benchmarking-study-2025