Fee Calculation
A fee calculation applies agreed terms to an evidenced basis for a particular window. The schedule describes the terms; the run identifies the calculation and version; its lines preserve the component and recipient results. A rate is not meaningful without knowing its basis and applicable time convention, and a stored result is not proof that those choices match the agreement.
Open Accounting → Fees & Capital Allocations → Fee Calculation to inspect that existing calculation evidence and lifecycle. The control checks required records and states; it does not independently recompute the contractual fee.
Choose the run population
Select Entity and Accounting Period, then optionally Fee Run, Share Class and Recon Status. Fee runs are scoped by their stored accounting-period association, not merely an As of Date inside the quarter. Voided runs and lines are excluded.
Share Class on this tab selects complete runs containing that class on the run header or an active line. Fee Line Total and Basis Total remain whole-run amounts; they are not necessarily that class's share. “Without Share Class” tests the run header.
The fictional organization has no fee runs for this period. Recon Status All distinguishes this empty population from the default Exceptions filter. No fee amount, computation or finalization is demonstrated.
Read the calculation control
One row represents one non-voided fee run. Start with Status / Recon Issue, then inspect Fee Schedule, Fee Type, Run Status, dates, Version, Active Lines, Currency, Fee Line Total, Basis Total, Missing Inputs and Missing Evidence. Scroll horizontally for these fields.
Status is this control's verdict; Run Status is the stored lifecycle state:
- Draft/computed runs show Needs Review first. That label can take precedence over additional line/input failures.
- Other checks look for active lines, one currency, required basis/rate/term inputs and calculation evidence.
- Reviewed/finalized runs also require their active calculation lines to be finalized.
Ready means the required records and lifecycle evidence pass this control. You still need to compare the fee terms, calculation basis and amount with the approved agreement and calculation evidence.
Reconstruct one calculation before relying on its status
Begin with the agreement: identify what amount the fee is based on, which rate applies, the period to which it applies, and any contractual timing or day-count rule. Reproduce the relevant calculation from those inputs, then compare the stored line result. A simple basis-times-rate-times-period-fraction illustration is useful only when the approved terms actually require that method; more complex terms need their own evidenced calculation.
Assume approved terms explicitly require a simple quarterly fee of USD100,000 × 2% per year × 3/12. The arithmetic is USD500. To review a stored run for that example, find the basis of USD100,000, the 2% rate, the quarter fraction and the evidence supporting each input, then compare the stored line outputs. Different contractual day-count, timing or fee-base rules require their own calculation; this example sets no policy.
A stored USD500 result can still be a computed run awaiting review. The control can identify absent input/evidence records and lifecycle issues, but it does not independently reproduce the calculation or establish that USD500 is contractually correct. After calculation review, inspect Fee Posting and Fee Recipients for accounting delivery. The native example remains empty; no USD500 run has been produced.
Follow the evidence
- Open the Fee Run reference and identify the exact run and version.
- Review its schedule/terms, basis, applied rates and calculation breakdown against approved source evidence.
- Use Fee Recipients with the same Fee Run for recipient lines. When class-filtered, remember that this tab still reports the whole run while Recipients narrows the lines.
- Route incorrect terms/inputs or absent evidence to the fee-calculation owner. Use the authorized calculation/review workflow, then refresh these controls.
- Continue to Fee Posting for accounting lineage. Calculation readiness does not prove journal posting.
An empty table does not mean no fee is due: absent runs are not automatically synthesized as exceptions. Check scope, expected schedules and whether the run was produced. All removes status filtering, but not voided or ignored-record exclusions.