Fee Billing and Expense Accuracy

To meet the fee billing and expense accuracy requirement, you must calculate advisory fees and fund/client expenses exactly as the governing agreements and disclosures require, then prove it with repeatable controls, reconciliations, and oversight. Under a fiduciary standard, even small or unintentional overbilling can become a fraud issue if you lack reasonable processes and remediation discipline.

Key takeaways:

• Your control objective is simple: no fee or expense charge without contractual authority, correct calculation, and accurate disclosure.
• Operationalize the requirement with defined data sources, independent recalculation, variance thresholds, and documented approvals.
• Retain a complete “billing file” per period: inputs, calculations, reviews, corrections, and client/fund communications.

“Fee billing and expense accuracy” is a requirement that sits at the intersection of fiduciary duty, fraud risk, and operational controls. For a Compliance Officer, CCO, or GRC lead, the fastest path to operationalizing it is to treat every billed fee and allocated expense as a regulated output: it must be supported by a governing document, derived from controlled inputs, calculated correctly, reviewed independently, and corrected quickly when wrong.

The regulatory anchor is the adviser’s fiduciary duty regarding compensation received from investment companies, which creates direct pressure on how you compute fees, apply breakpoints and waivers, allocate expenses, and describe expense impacts in disclosures (15 U.S.C. § 80a-35(b)). Examiners rarely accept “our administrator does it” as a control. They look for your oversight: how you validate the numbers, how you approve exceptions, and how you ensure the client or fund is made whole when errors occur.

This page is written to help you implement requirement-level controls that work in real billing cycles, across in-house operations and third parties (administrators, custodians, pricing vendors), without turning your program into a documentation project.

Regulatory text

Excerpt (provided): “Investment advisers have a fiduciary duty regarding compensation received from investment companies.” (15 U.S.C. § 80a-35(b))

Operator interpretation: This fiduciary duty means you must (a) charge only what the advisory agreement permits, (b) calculate and bill fees accurately, and (c) treat expense allocation as a fiduciary decision, not a bookkeeping preference. The practical implications called out in the requirement summary include: accurate fee calculations, billing consistent with advisory agreements, correct application of fee waivers and breakpoints, proper disclosure of expense ratios, and ensuring expenses are reasonable in relation to services provided (15 U.S.C. § 80a-35(b)).

Plain-English interpretation (what the requirement demands)

You need a defensible process that prevents, detects, and remediates:

• Overbilling and underbilling due to incorrect rates, wrong billing frequency, stale AUM, wrong valuation dates, or misapplied breakpoints/waivers.
• Improper expense allocations where funds/clients are charged expenses that should be borne by the adviser/affiliate, or are allocated inconsistently with disclosures and governing documents.
• Disclosure mismatches where what you charge (or how you allocate expenses) drifts from what you told investors, boards, or clients.

A good test: if you were required to reconstruct a single billing period end-to-end, could you show (1) contractual authority, (2) inputs, (3) calculation logic, (4) reviews/approvals, (5) invoice/statement output, and (6) remediation for any differences?

Who it applies to

Entity types (from provided applicability):

• Investment Companies
• Portfolio Managers

Operational context (practical scope):

• Registered investment advisers that receive compensation from investment companies/funds and their complexes, including advisers overseeing fund fee schedules, breakpoints, performance fees (if any), waivers, and expense reimbursements (15 U.S.C. § 80a-35(b)).
• Portfolio management organizations where billing, expense allocations, or data inputs are performed by third parties (fund administrators, transfer agents, custodians, pricing agents) but the adviser retains oversight responsibility.

If you touch any of the following, you are in-scope: advisory agreements, fee schedules, billing files, NAV/AUM inputs, waiver memos, expense allocation policies, board reporting, prospectus/disclosure alignment, or exception approvals.

What you actually need to do (step-by-step)

1) Build a “source of truth” for fee and expense terms

Create (and maintain) a controlled inventory of governing terms:

• Advisory agreements and amendments
• Fee schedules, breakpoints, and billing conventions (e.g., average daily net assets vs. period-end)
• Waivers, reimbursements, caps, and how they are calculated
• Expense allocation rules and what the adviser vs. fund/client pays
• Disclosure mappings (where each fee/expense item is described)

Control requirement: changes must be tracked, approved, and communicated to billing owners before effective dates.

2) Map the billing process end-to-end (including third parties)

Document the workflow from inputs to outputs:

• Data sources (AUM/NAV, flows, pricing, share class data)
• Calculation engine (spreadsheet, administrator system, portfolio accounting system)
• Invoice generation and delivery
• Payment/collection method and timing
• GL booking and reconciliation points
• Exception handling and approvals

Practical tip: write this as a swimlane diagram with named owners. Examiners want accountability more than pretty process maps.

3) Control the inputs (most billing failures start here)

Define input controls for:

• Valuation/AUM source: which system is authoritative, and when it is “final”
• Rate tables: who can change them, how changes are tested, and approval evidence
• Breakpoint and waiver flags: how they are triggered and validated
• Expense coding: how expenses are classified to adviser vs. fund/client and how overrides are approved

Minimum expectation: access control on rate/terms tables and a logged change history.

4) Independent recalculation and variance review

Implement a two-layer check:

• Primary calculation by operations/administrator using defined logic.
• Independent verification by someone not preparing the bill (often finance control, fund oversight, or compliance testing): reperform key components and compare results.

Set documented rules for:

• What gets recalculated (all items vs. risk-based sample)
• What variances require explanation, escalation, and correction
• How exceptions are approved and recorded

If you use a third party administrator, your independent check should still exist. You can reperform using administrator reports, raw data exports, and a firm-controlled calculator.

5) Expense allocation governance (prevent “improper expense” drift)

Put structure around expense decisions:

• Define allowable expense categories for each fund/client and which are adviser-paid.
• Require documentation for gray areas (e.g., shared services, travel, research tools, regulatory filing costs).
• Require periodic review of expense coding and allocations for consistency with disclosed practices.

Where boards or oversight committees are involved, align reporting to their oversight needs and keep minutes or packages that show what they reviewed.

6) Reconciliations to accounting records

Reconcile billed fees and allocated expenses to:

• Cash receipts/disbursements
• General ledger entries
• Administrator accounting (if applicable)

Look for: missing invoices, duplicate charges, stale accrual reversals, or manual journal entries that bypass billing controls.

7) Error handling and client/fund remediation

Define and follow an error protocol:

• Log the error with impact assessment (what, why, who affected, period affected)
• Stop recurrence (fix data, logic, access, training)
• Correct billing (credit/rebill) and reimburse where required
• Communicate appropriately to internal governance and, where necessary, to clients/fund stakeholders
• Retain a complete remediation file

A weak remediation trail is where “operational mistake” turns into “process failure.”

8) Ongoing testing and oversight (compliance’s role)

Compliance should:

• Test billing and expenses as part of the annual risk assessment and monitoring plan.
• Review exception reports (waivers, manual overrides, write-offs).
• Challenge whether disclosures still match operational reality (15 U.S.C. § 80a-35(b)).

If you need workflow discipline, Daydream can help you manage evidence requests, approvals, and recurring control testing without chasing spreadsheets across teams, especially where third parties provide inputs on different timelines.

Required evidence and artifacts to retain

Keep a “billing file” per billing period (or per fund/client), including:

• Governing agreement excerpt supporting the fee and billing convention
• Rate tables and effective dates; change approvals
• Source data extracts (AUM/NAV, dates, pricing feeds as applicable)
• Fee calculation workpapers (system output plus any manual adjustments)
• Breakpoint/waiver support (calculation and authorization)
• Expense allocation policy and any exception memos
• Reviewer sign-offs (pre-bill and post-bill checks)
• Invoices/statements issued and delivery evidence
• Reconciliations to GL/cash and administrator records
• Error logs, remediation calculations, approvals, and communications

Retention should align to your broader books-and-records program; the key is reconstructability.

Common exam/audit questions and hangups

Expect questions like:

• “Show me how the billed fee ties to the advisory agreement term-by-term.”
• “Who can change fee rates and waiver flags, and what prevents unauthorized edits?”
• “What independent verification do you perform over the administrator’s work?”
• “Show exceptions for the last periods and how you approved them.”
• “How do you ensure expenses charged are consistent with what was disclosed?” (15 U.S.C. § 80a-35(b))
• “Walk me through one error: detection, escalation, correction, and remediation.”

Hangups that trigger deeper review:

• Manual spreadsheets with no access controls or change logs
• Post-hoc approvals (“reviewed” after invoices went out)
• Unclear authority for expense categories
• Inability to reproduce a historical calculation because inputs were overwritten

Frequent implementation mistakes (and how to avoid them)

1. Relying on the administrator as the control.
   Avoidance: document your oversight controls and perform independent recalculation or data-level checks.

2. No controlled inventory of agreements and fee terms.
   Avoidance: create a single repository with version control and effective-date tracking.

3. Waivers/breakpoints handled as ad hoc courtesy items.
   Avoidance: treat waivers and breakpoints as contractual terms with testing and evidence like any other fee component (15 U.S.C. § 80a-35(b)).

4. Expense allocation “rules” live in people’s heads.
   Avoidance: publish an expense allocation standard, require exception memos, and review coding patterns periodically.

5. Fixing the dollar error but not the root cause.
   Avoidance: require root-cause classification, control enhancement, and owner sign-off before closing an incident.

Enforcement context and risk implications

The requirement summary explicitly notes SEC enforcement against advisers for overbilling and improper expense allocation (15 U.S.C. § 80a-35(b)). The operational risk is not limited to the amount of the billing error; it includes the appearance that the adviser lacks a reasonable process to meet fiduciary obligations regarding compensation and fund expenses (15 U.S.C. § 80a-35(b)).

Translate that into your risk register as:

• Regulatory risk: inaccurate fees/expenses can be framed as misleading conduct under antifraud standards when controls are weak.
• Fiduciary risk: conflicts around adviser compensation and fund-borne costs.
• Reputational risk: investor trust and board confidence.
• Operational risk: repeated errors from uncontrolled inputs, manual overrides, and poor governance.

Practical 30/60/90-day execution plan

First 30 days (stabilize and document the “as-is”)

• Inventory all advisory agreements, fee schedules, and waiver/breakpoint terms in a controlled repository.
• Map the end-to-end billing workflow and identify all third party dependencies and data handoffs.
• Identify the top error-prone points: rate changes, AUM source timing, manual adjustments, expense coding overrides.
• Stand up an error log and require documented approvals for any manual billing adjustment going forward.

Days 31–60 (implement core controls and evidence trails)

• Implement access control and change approval workflow for rate tables and waiver/breakpoint parameters.
• Launch independent recalculation for a defined scope (start with highest-AUM funds/clients or most complex fee structures).
• Create standard billing file checklists and require reviewer sign-off before invoices go out.
• Publish (or refresh) an expense allocation policy and an exception memo template.

Days 61–90 (test, tune, and governance hardening)

• Run a retrospective review for a prior period to confirm you can reconstruct calculations from retained inputs.
• Establish recurring reconciliations between billed amounts, GL, and cash.
• Review disclosure alignment: confirm billed fees and allocated expense categories match what is disclosed (15 U.S.C. § 80a-35(b)).
• Formalize reporting to management/boards: exceptions, errors, remediation status, and control issues.

Frequently Asked Questions

If our fund administrator calculates fees, do we still need internal controls?

Yes. You can outsource tasks, not fiduciary responsibility for adviser compensation practices tied to funds (15 U.S.C. § 80a-35(b)). Maintain oversight controls: data validation, independent recalculation, variance review, and documented exception approvals.

What’s the minimum evidence an examiner will expect for fee billing accuracy?

A reconstructable billing file: governing fee terms, inputs (AUM/NAV), calculation output, reviewer approval, and reconciliation evidence. If waivers or breakpoints apply, keep written authorization and the calculation support (15 U.S.C. § 80a-35(b)).

How do we control breakpoints and waivers without slowing billing to a crawl?

Treat them like master data. Lock down edit rights, route changes through a short approval workflow, and require pre-bill exception reports that show where breakpoints/waivers changed from the prior period.

What’s the best way to handle billing errors once identified?

Use a standard incident workflow: quantify impact, identify root cause, correct and reimburse/credit as appropriate, and document the communications and approvals. Close the loop by updating controls so the same failure mode cannot recur.

How should we govern expense allocations that are shared across funds or adviser entities?

Write down the allocation method, require documentation for the driver (headcount, AUM, usage, invoices), and review coding for consistency to disclosures and governing documents. Require exceptions to be documented and approved.

Can we keep the fee calculation in spreadsheets if we have reviews?

You can, but you need spreadsheet controls: locked formulas, access restrictions, versioning, documented inputs, and independent review evidence. Most breakdowns come from uncontrolled edits and overwritten inputs.