RIA Billing Software Versus Reconciliation

In our experience, RIA billing software is good at one job, which is taking a fee schedule and producing an invoice or fee file. Reconciliation is a different job, which is proving the fee that left the client’s account matches the fee the firm was entitled to charge under the agreement in force.

That distinction matters because most fee problems are not arithmetic problems. They are entitlement problems, such as the wrong schedule, the wrong household, the wrong asset base, the wrong date convention, the wrong exclusion, or the wrong split. A billing engine can compute a number flawlessly and still leave the firm exposed if no one independently checks what was actually debited.

For firms where the revenue number has to stand up to a regulator, a custodian, or an auditor, the question is not “which platform bills?” It is “what system can prove the bill was right?”

The Anatomy of a Quarterly Fee Run

A quarterly advisory fee is not a single calculation. It is a chain of inputs, each of which may live in a different system or in a side agreement no platform can infer on its own.

The practical point is that each input has to be correct before the arithmetic even starts. Billing software usually owns the middle of the process. The firm still owns the inputs.

What Actually Goes Wrong With Advisory Fee Billing

Advisory fee billing is a common regulatory examination focus because the failures are usually mundane, repeatable, and expensive. The useful way to think about the problem is not “did the vendor calculate?” but “which class of error can this control actually catch?”

The pattern is consistent, because the calculation may be technically correct given the wrong input. That is why a feature list is not the same thing as a control environment.

Why Calculation-only Tooling Misses Most of the Risk

Most billing platforms are designed to produce an invoice, a fee file, or both. That is useful, but it is not the same as independent proof. If the schedule is wrong, the household is wrong, or a side letter was never loaded, the platform will happily calculate the wrong fee with high confidence.

This is especially true in firms with inherited complexity:

• books acquired from other advisers with legacy pricing terms
• held-away, private, or direct assets that the custodian does not price
• more than one custodian
• advisor-specific concessions negotiated over years
• revenue splits that do not map neatly to account-level billing

In those firms, the hardest part is not math. It is preserving the entitlement logic in a form that can be replayed and explained quarter after quarter.

The Independence Problem With Custodian Billing Tools

There is a real control issue when the custodian computes the fee, deducts the fee, and reports the fee. None of those steps is inherently wrong. The issue is independence, because the firm has not separately performed the check.

A custodian-provided billing tool can be useful. It is not, by itself, an independent control. At minimum, the firm should be able to produce an expected-versus-actual reconciliation using its own agreement data and its own billing-group definitions, then compare that result against the custodian debit file.

That means the firm needs a source of truth for three things:

• the entitlement rules in force
• the population of accounts or households being billed
• the actual debits that left client accounts

If those three are all owned by the same counterparty, the firm should understand exactly what control it is relying on, and what it is not.

The Quarterly Reconciliation Every Firm Should Be Able to Run

At the end of each billing cycle, the firm should be able to explain the difference between the fee it expected to charge and the fee actually deducted. The reconciliation is simple in concept and unforgiving in practice.

1. Build Expected Fee by Billing Group

Start with the agreement and the schedule in force. Calculate expected fee per household or billing group using the valuation method specified in the contract, including breakpoint logic, proration, exclusions, and any discount or rebate.

2. Pull Actual Debits From the Custodian File

Extract the actual fee debited from each account or relationship during the period. Normalize the file so it can be matched to the same billing group definition used in step 1.

3. Compare Expected Versus Actual

Match each billing group, then calculate variance. Use a materiality threshold the firm can defend. Small rounding differences should not be treated like true billing errors; everything else needs a disposition.

4. Dispose of Each Variance

Every variance should land in one of four buckets:

• No issue. The difference is rounding, timing, or an agreed convention and is documented.
• True under-bill. The firm charged less than entitled and may need a catch-up, subject to contract and disclosure.
• True over-bill. The firm charged more than entitled and should refund promptly.
• Configuration or data error. The schedule, household, exclusion, or valuation input is wrong and must be corrected before the next run.

5. Retain the Record That Makes the Decision Defensible

For each material variance, keep the agreement version, the fee schedule in force, the billing-group logic, the custodian debit file, the variance report, and the disposition note. A refund without this trail is just a correction. A refund with it is evidence of control.

Buy or Build Criteria That Actually Matter

Do not choose based on feature count. Choose based on the shape of the revenue problem.

Buy billing software when:

• the book is effectively single-custodian
• fees are standard, transparent, and modelled cleanly by the vendor
• nearly all billable assets are custodied and priced in the same system
• householding and grandfathered schedules are limited
• the firm mainly needs invoice production and fee file generation

Consider building the revenue layer when:

• a meaningful share of billable assets is held away, alternative, private, or otherwise not priced by the custodian
• householding and legacy schedules are bespoke enough to live in spreadsheets beside the billing system
• the firm operates across more than one custodian
• revenue has to be attributed across advisors, partners, or acquired books on custom terms
• billing output and revenue reporting must be the same number

What not to build is invoicing, payment collection, or statement delivery. Those are commodity functions. If the firm builds anything, it should build the revenue layer underneath them, meaning the rules, the reconciliation, and the audit trail. We write about regulated financial systems on our fintech software development page.

What Version One of a Revenue Layer Should Contain

Version one does not need to be clever. It needs to be reproducible.

• agreement and fee schedule stored as structured data, not just PDFs
• a firm-owned billing-group definition
• expected-fee calculation logic for the current schedule
• variance report against custodian debits
• clear audit trail for every rule, override, and exception

It should not contain client portal features, general invoicing workflows, payment rails, or broad practice-management scope yet. The first job is to make the fee defensible.

What RIA Billing Software Can and Cannot Prove

RIA billing software helps produce a fee. It does not, by itself, prove the fee was entitled, correctly applied, and independently checked. For firms with simple books, that may be enough. For firms with inherited schedules, held-away assets, multiple custodians, or custom revenue splits, it is not. The real control is reconciliation, and the real question is whether the firm can reproduce its own fee run without depending on memory. For the reproducibility side of this problem, read can you reproduce last quarter's fee run and our companion piece on reproducible fee runs, or talk to Better Software about your own revenue layer.

Frequently Asked Questions

How Often Are Advisory Fees Paid?

In our experience most advisory fees are billed quarterly, though some firms bill monthly, semi-annually or annually, depending on the client agreement and disclosure documents. The billing frequency has to match the contract and the schedule in force.

How Often Can Advisory Fees Be Charged?

Only as often as the agreement permits. We treat the contract, the Form ADV disclosure and the billing schedule in force as three documents that must agree on frequency before any fee run starts, because a mismatch is itself a billing error.

What Is Wrap Fee Billing?

It is a bundled arrangement where the client pays a single fee that may cover advisory services and certain transaction or custody-related costs, subject to the program's terms. We would always check the program documents, because they control what the bundle includes.

What Is Flat Fee Billing?

It charges a fixed amount rather than a percentage of assets, and it is common for planning, project-based or minimum-fee arrangements. We still reconcile it, because the amount debited has to match the amount the agreement entitles the firm to charge.

What Is the Difference Between an Advisory Fee and a Management Fee?

In practice the terms are often used interchangeably. We read advisory fee as the fee charged under the advisory agreement and management fee as the asset-based component, but the documents control, so we always check what the agreement says.