Valuations & Allocations
A valuation records an investment's accounting value at an as-of date, with its method and source evidence. It can supply the mark against which investment accounting is reviewed. An accounting allocation run performs a different job: it records a calculation/version that distributes a source pool of income, expense or gains among recipients.
Open Accounting → Accounting Operations → Valuations & Allocations to inspect the stored marks, run headers and recipient lines. A FundOps participation scheme describes who participates in an item. A run records the result of applying a particular calculation and basis; its lines hold the recipient amounts. Inspect resulting capital movements and journals separately to establish what reached the accounting books.
Scope the records
Choose Entity and confirm Period. This page does not have a global Share Class filter; use a table's own filters where the relevant field is available.
The fictional organization has no stored investment valuations, accounting allocation runs or run lines in the July–September 2026 period. Its existing participation scheme and Draft expense journal have not been treated as generated valuation or allocation results.
A run and its recipients
First establish what is being distributed, which basis applies and which recipients belong in the calculation. The header preserves the run and version; each line preserves one recipient's share and components. Adding the lines should explain the selected run's total within its currency. That agreement tests distribution of the pool; it does not prove the pool itself is complete, the basis is approved or the resulting movements were posted.
Consider an illustrative accounting allocation of USD100 of expense between two recipients at 60% and 40%. One run identifies the calculation and version; two run lines hold expense amounts of −USD60 and −USD40. Those lines explain the result to inspect. They are not two cash payments, and their presence would not prove that capital movements or a Posted journal were produced.
The screenshot has no such run or lines. Its existing FundOps participation scheme describes who participates in an item; the accounting owner must use the authorized calculation process before this page can show a run and its recipient outputs. Check the run's source pool, scheme snapshot and actual lifecycle evidence before relying on an allocation result. The arithmetic above illustrates those record relationships and does not prescribe an allocation policy.
Follow the three levels
Investment Valuations has one stored valuation record per row. Review Investment, As of Date, Fair Value, Currency, Method and source document/type/record. More than one valuation can exist for an investment. Use the source document and the valuation owner's approved evidence to understand the mark.
Allocation Runs has one run header/version per row. Review Entity, Share Class, As of Date, Start Date, End Date, allocation scheme and scheme snapshot dates, Status and Version. Computed At, Reviewed At and Finalized At show the dates recorded for those stages. Check the corresponding workflow evidence when confirming that a stage was completed.
Allocation Run Lines has one row per recipient/result within an allocation run; one run can have many lines. Follow Allocation Run Id to its header and review Capital Account, Subscription, Entity, Share Class, Allocation Percent, allocated income, expense, realized and unrealized amounts, and Currency. These allocated results are accounting amounts, not additional cash settlements.
The three tables are independent. Selecting a valuation or run does not automatically filter the others. To inspect one run's recipients, apply Filter → Allocation Run Id in Allocation Run Lines and compare the exact run/version.
Understand the period and status boundaries
Valuations appear when their As of Date falls within the selected period. This is not a “latest applicable valuation” view: a valid mark dated before the period may be absent.
Runs are also filtered by their As of Date, rather than by overlap of Start Date and End Date. Run lines follow the parent run's As of Date. Check the relevant dates before assuming a record is missing.
All stored run statuses can appear. Keep Draft, reviewed/finalized and voided versions distinct; do not add multiple versions together. A status or timestamp alone does not prove that the intended computation, review, finalization or posting was performed correctly.
Investigate before changing anything
- Verify the valuation's Investment, date, currency and source evidence.
- Identify the intended accounting run and scheme snapshot; confirm its period, version and lifecycle evidence.
- Isolate its lines by Allocation Run Id. Review recipients, percentages and amounts within each currency.
- Continue to Fees & Capital Allocations for the relevant allocation controls and Accounting Review & Close for period review. Use Capital Accounts to inspect any resulting capital movements separately.
Authorized users can select and maintain records in these tables. Insert and editable Status fields do not replace a calculation/review/finalization workflow. Saving source records may also trigger configured automation; understand that configuration before changing them.
If the tables are empty, check scope and ask the valuation or accounting-allocation owner whether the expected records were produced. Do not infer zero NAV from an empty table or manually fabricate generated run lines to make the example or a control look complete.