Metabase vs Tableau for RIAs: AUM and Fee Reconciliation

Most RIAs bill quarterly, in advance or in arrears, off a tiered schedule based on assets under management, and the custodian's own reporting rarely makes it easy to verify that every household was billed at the correct tier with the correct proration for a mid-quarter deposit or withdrawal. A Metabase dashboard joining custodian data to your fee schedule can flag any account billed outside an expected range for review before the invoice goes out, catching a proration error while it is still a two-minute fix rather than a client-facing correction after the fact.

A client who catches their own overbilled fee before you do is a trust problem, not just a math error, and it tends to color how they read every other number your firm shows them afterward.

A practical fee reconciliation check covers these points:

• Join custodian data to your fee schedule, so each household's billed fee can be compared with the tier that client actually agreed to.
• Verify proration for mid-quarter deposits and withdrawals, since custodian reporting rarely makes that easy to confirm.
• Confirm whether fees are billed in advance or in arrears before comparing, because the timing changes the expected amount.
• Record manual adjustments, such as a fee waiver for a household, as documented exceptions so they are not flagged as errors.
• Run the reconciliation ahead of each billing cycle, so a person can review flagged accounts before invoices go out.

A single point-in-time AUM number, viewed alone without any historical context, is much less useful than the trend behind it: how much growth came from market performance versus net new client contributions versus client withdrawals. Separating those three drivers, which requires joining periodic account snapshots rather than just looking at the latest balance, tells you whether the firm's growth is durable or mostly a function of a strong market that could reverse. This is a straightforward Metabase build once historical account snapshots are captured on a regular cadence rather than only checked at quarter-end.

A solo advisor or a small partnership where every principal already sees every household's data does not need Tableau. A larger RIA with multiple advisors, each managing their own book of client relationships, has a real access question: an advisor should see their own households in full detail, a compliance reviewer needs firm-wide visibility for oversight purposes, and advisors generally should not see each other's client-level fee and account detail without a specific business reason. Tableau's row-level security supports that layered access more cleanly than manually managed Metabase permissions do once the advisor count grows past a handful.

Disqualifier: skip Tableau if the firm is small enough that full internal visibility is already the norm, or if the added governance layer would sit unused by an audience that does not yet exist within the firm's current structure.

A dashboard showing which accounts have drifted furthest from their target allocation percentages is operational monitoring, a way to flag accounts due for a rebalancing review, not a recommendation engine making trade decisions. Keep the language on any such dashboard descriptive rather than prescriptive, and route any account flagged for drift through whatever review and approval process your firm's compliance program already requires before any trade is placed. The dashboard's job is to make sure nothing falls through the cracks of that process, not to replace it, and every account flagged should still end with a documented human decision and sign-off, not an automated action taken on the data alone.

Before any dashboard reaches client-facing use or gets referenced in client communication, have your compliance officer or outside compliance counsel review exactly what data it shows, who can see it, and how it is worded. An internal operational tool for catching fee reconciliation errors is a very different thing from anything that could be read as investment advice or a performance claim, and that line matters enough to confirm explicitly rather than assume it will be obvious to everyone building or viewing the dashboard.