Txn Posting
An investor's capital changes when a contribution, distribution, fee or allocated result is recorded against the investor's capital account. The amount must have an identifiable source and the appropriate journal relationship. A contribution's cash amount, a fee charge and an allocation component do not all use the same sign or posting path.
Open Accounting → Fees & Capital Allocations → Txn Posting to compare existing movements with those source and journal expectations. For specified eligible allocation components, the control can also identify an expected movement that was never saved. It reviews delivery of accounting effects; it does not create or post them.
Scope the control
Select Entity and its Accounting Period, then optionally Share Class. Recon Status defaults to Exceptions; choose All to see Ready rows as well. Changing a table filter cannot restore rows excluded by the global status filter.
The fictional Entity #1, July–September 2026, with Recon Status All. No capital-account transactions or eligible accounting allocation runs exist, so the table is empty. Existing subscription cash and Draft journal #1 do not prove capital posting.
Understand a row
Compare like effects: a capital reduction should be checked against the source's expected signed capital reduction, not against an unrelated gross debit/credit total. Account, recipient, date and currency establish where the effect belongs; source and journal lineage establish why it exists and how it was recorded. Amount agreement alone cannot explain a movement delivered to the wrong investor.
Suppose an eligible accounting allocation run records a recipient expense component of −USD60, but no corresponding capital movement was saved. This control can show the missing expected component even though there is no Capital Account Txn ID to open. Follow the allocation run and recipient line to establish what was expected, then ask the accounting owner to investigate delivery through the authorized process. The example is hypothetical; the screenshot has no eligible runs or transactions.
A row therefore represents either an existing capital-account transaction or a missing expected allocation component. For an existing transaction, start from its saved ID; for a missing component, start from its allocation source.
For an existing transaction, compare Date, Type, Capital Account, Subscription, Share Class and Currency. Then read Status / Recon Issue and compare Capital Account Amount, Source Amount and the relevant journal evidence. Source Amount can be a derived accounting effect rather than the raw activity value; contributions, distributions, fees, transfers and allocation components have different signs and accounting paths.
The control uses a one-cent amount tolerance: a difference greater than 0.01 fails the relevant amount check. A Ready result does not replace inspection of journal status and the complete accounting chain.
Investigate an exception
- Read Recon Issue first, then open the configured transaction, source or journal reference.
- Confirm the source exists and that account ownership, date, currency, sign and amount describe the intended event.
- For allocation components, check the source run and recipient line. Expected nonzero components come from eligible reviewed/finalized runs within the period, using this control's own run-ranking rule.
- Review Matching Transaction Count when investigating duplication. It is a specialized allocation/adjustment check, not a universal uniqueness test for every source.
- Correct source facts with the FundOps owner; route capital-account mapping, lineage and journal issues to Accounting. Recheck the control after the authorized correction.
This page does not synthesize every missing contribution, distribution or fee movement. An empty table therefore does not certify that every source has reached capital accounting. Compare Subscription Coverage and the relevant source/recipient controls.