Can You Reproduce Last Quarter's Fee Run?

Most RIA billing software does one job well: it calculates what should be charged and produces a file for the custodian or invoicing system. The harder question is the one the principal ends up owning: can you reproduce why that exact fee left the client’s account?

That is the difference between calculating a fee and reconciling a fee. Calculation is arithmetic against a schedule. Reconciliation is proof: the agreement in force, the schedule applied, the values used, the exclusions honored, and the actual debit that hit the account all line up. If you cannot reconstruct that chain, you have a billing process. You do not yet have defensible revenue.

The distinction matters because the regulator does not ask whether your software generated an invoice. It asks whether the client was charged only what the firm was entitled to charge, under the fee arrangement actually in force, using the correct assets, the correct grouping, and the correct timing.

The anatomy of a quarterly fee run

A quarterly advisory fee is usually assembled from seven inputs. In a healthy firm, each one has an owner, a source of truth, and a way to be checked. In a brittle firm, several live in a spreadsheet, a PDF, and someone’s memory.

Most billing platforms own the schedule, the pricing math, and the output file. Fewer own the exception logic around held-away assets, grandfathered agreements, householding rules, and split revenue. That is where the real risk sits.

What actually goes wrong

The SEC’s Division of Examinations risk alert on adviser fee calculations is useful because it names the failures that matter in practice. The alert described fee-related deficiencies at nearly every adviser examined in a sweep of roughly 130 examinations, including over-billing, inaccurate tiered and breakpoint calculations, incorrect householding, failure to apply promised discounts and rebates, double-billing, and fees charged on assets that should have been excluded.

That is a better operating checklist than any vendor feature table. Here is the same list translated into the language of a billing owner:

The pattern is consistent: the failure is usually not the math itself. It is the input to the math.

Why calculation-only tooling misses the real exposure

Fee billing software is optimized for a clean world: one custodian feed, one current schedule, one pricing basis, one householding rule, and one stable account map. RIAs rarely live there.

Established firms accumulate exceptions. A legacy client keeps a grandfathered schedule. A recruiting deal adds a side letter. A held-away private credit account is billed off-platform. A household was defined years ago in a spreadsheet and never normalized into the system. A second custodian is added after an acquisition. None of that is exotic in the market segment shopping for ria fee billing software. It is the market segment.

That is why a billing engine can be correct and the firm can still be wrong. It may calculate exactly what the data told it to calculate. The problem is that the data did not fully describe the agreement.

For firms with meaningful held-away, alternative, private, or direct assets, this gap widens. Those assets are often part of the fee base, but they are precisely the assets the custodian may not price. The math has to leave the custodian feed and re-enter a firm-controlled model. Once that happens, the question is no longer “does the billing platform calculate?” It is “can we independently prove the calculation against the agreement?”

The independence problem

Some billing platforms are distributed by custodians. That is not inherently a problem. It becomes a problem when the same counterparty computes the fee, deducts the fee, and reports the fee, while the adviser treats that output as the control.

Stated plainly: if the party that moves the money also supplies the number, the firm has not performed an independent reconciliation. It has accepted a statement.

An independent check requires four things:

• The agreement and schedule in force, not just the current standard template.
• The period’s pricing basis and all exception logic, including householding and exclusions.
• The actual debit file from the custodian, account by account and household by household.
• A variance report that explains every difference between expected and actual.

What is reasonable to accept from a custodian-provided tool? The calculation engine, the debit file, and the statement file can all be useful inputs. What is not reasonable is to let the same system stand in for reconciliation without an adviser-owned review of exceptions, variances, and fee changes over time.

The quarterly reconciliation every RIA should run

Every quarter, the firm should be able to produce an expected-versus-actual fee reconciliation at the billing-group level. Not a summary. Not a screenshot. A working document that lets an owner trace the fee from agreement to debit.

1. Assemble the billing population. Start with the household or billing group definition used for the run.
2. Pull the governing agreement. Confirm rate, minimums, breakpoints, exclusions, and any grandfathered or side-letter terms.
3. Rebuild the expected fee. Use the schedule in force and the correct valuation basis.
4. Load actual custodian debits. Compare the amount charged, the date charged, and the accounts debited.
5. Explain variances. Separate true errors from legitimate proration, trade-date differences, new assets, exclusions, and refunds.
6. Set a materiality threshold. Small rounding differences may be immaterial; systematic errors are not.
7. Document the disposition. Refund, rebill, waive, or retain with support.

The four defensible dispositions of a variance are simple:

• Refund if the client was overcharged.
• Rebill if the original debit was too low and the agreement permits correction.
• Waive if the firm elects not to pursue a technically supportable charge.
• Retain only if the variance is explained, immaterial, and documented.

The point is not to eliminate every variance. The point is to know which ones are real, which ones are contractual, and which ones would be embarrassing under exam.

When to buy ria billing software, and when to own the revenue layer

For many firms, buying the platform remains the right answer. But the decision should be made explicitly, not by default.

Buy billing software when all or most of the following are true:

• The firm is effectively single-custodian.
• Fee schedules are standard, current, and cleanly migrated.
• Most billable assets are custodied and priced by the custodian.
• Householding rules are simple and stable.
• The firm does not need bespoke revenue attribution across advisors, partners, or acquired books.

Consider building the revenue layer underneath advisory fee billing when one or more of these are true:

• A meaningful share of billable assets is held away, alternative, private, or otherwise not priced by the custodian.
• Householding and grandfathered schedules are bespoke enough that they live outside the system.
• The firm operates across more than one custodian.
• Revenue has to be allocated across advisors, partners, or legacy deals in ways no vendor models cleanly.
• The firm needs the revenue reporting number and the billing number to be the same number.

What should not be built first: invoicing, payment collection, statement delivery, or other commodity edge functions. Those are solvable with standard tools. The strategic layer is the agreement model, the billing-group logic, the expected-fee calculation, and the reconciliation to actual debits.

What version one should contain

If a firm owns the revenue layer, version one should be narrow and concrete:

• The advisory agreement as structured data, not just a PDF.
• The ria fee schedule in force, including grandfathered and side-letter exceptions.
• A firm-controlled billing-group definition.
• An expected-fee engine that can handle householding, breakpoints, and proration.
• A variance report against actual custodian debits.
• An audit trail showing who changed what, when, and why.

Version one should not try to solve the entire operating stack. It should solve the firm’s hardest problem: producing revenue that can be defended.

A note on the Better tie-in

In regulated financial systems, the recurring pattern is the same: when a number has to withstand a counterparty, an auditor, or a regulator, the system producing it has to be open enough to explain. That is the lesson we have seen in embedded engineering on mortgage servicing, in trading systems, and in modular financial foundations built for high-growth fintech. The point is not that every firm should build everything. The point is that the ledger, reconciliation, and control layer cannot be a black box if the number matters.

You can read more about the broader fintech work at /industries/fintech and a modular financial foundation case study at /case-studies/fintech-software.

FAQ

How often are advisory fees paid?

Most advisory fees are billed quarterly, though some firms bill monthly, semiannually, or annually depending on the agreement. The correct answer is whatever cadence the advisory contract and fee schedule specify.

How often can advisory fees be charged?

They can be charged only as often as the client agreement permits. The frequency should match the disclosed billing cadence and any custodian or invoicing workflow the firm uses.

What is wrap fee billing?

Wrap fee billing is a bundled pricing arrangement where one fee covers advisory services and certain transaction or custody-related costs, subject to the terms of the wrap agreement. The key control is still the same: the firm must be able to prove what the fee covers and what it does not.

What is flat fee billing?

Flat fee billing charges a fixed amount rather than a percentage of assets. It can simplify calculation, but it does not eliminate the need for reconciliation, especially when discounts, proration, or refunds apply.

Advisory fee vs management fee: what is the difference?

In practice, the terms are often used loosely. “Advisory fee” usually refers to the fee for investment advisory services under the client agreement, while “management fee” may refer to portfolio management or a subset of advisory services. The decisive document is the agreement, not the label.

For an RIA owner, the real test is not whether the platform can produce a fee file. It is whether the firm can reproduce the fee after the fact, explain every variance, and stand behind the number when the regulator asks.