Fund Accounting Platform

The workflow starts with portfolio and fund activity. Trades change positions and cash. Corporate actions change entitlements, income, tax treatment, or instrument terms. Expenses create accruals and liabilities. Subscriptions and redemptions change ownership and cash. Pricing and FX change valuation. Each event has to be mapped to fund, entity, account, instrument, investor, currency, and date dimensions before it can support accounting.

NAV is a control output, not just a calculation. The NAV input set depends on correct positions, confirmed or explainable cash, valid prices, current FX, complete income, approved expenses, investor activity, allocation rules, and clear treatment of outstanding breaks. A platform that supports NAV oversight should show which inputs are final, which are estimated, which are timing differences, and which require escalation.

Reconciliation is the control gate. Fund records should be compared against custody positions, bank cash, broker activity, administrator files, pricing evidence, internal trade records, and corporate action data. Breaks should be classified by cause: timing, missing source, identifier mismatch, price variance, cash mismatch, failed settlement, fee discrepancy, or adjustment. The platform should retain the evidence used to resolve the break.

Fund accounting also needs an approval trail. Controllers, operations teams, administrators, finance teams, or oversight reviewers may all touch the record before close. The system should record who reviewed exceptions, which documents supported the decision, which adjustments were made, and whether close occurred with unresolved items. That trail matters because fund accounting outputs are often reviewed after the operating window has passed.

Source capture brings together data from trading systems, custodians, banks, administrators, pricing sources, corporate action feeds, investor servicing workflows, expense systems, and internal records. Each source should remain traceable. The platform should preserve the raw record, source timestamp, normalized record, mapping logic, and workflow status.

Normalization creates the common fund accounting model. A fund may have multiple entities, accounts, strategies, currencies, share classes, investor types, fee terms, or allocation rules. A platform should not let those dimensions live only in spreadsheets or downstream reports. They should be part of the operating record because they determine how activity flows into NAV support and investor allocation.

NAV preparation organizes the inputs that affect fund value. Positions, cash, prices, FX, accruals, expenses, liabilities, subscriptions, redemptions, corporate actions, and adjustments all become part of the input set. The platform should distinguish expected activity from confirmed activity, and it should show the status of each input before the fund record is used.

Reconciliation tests whether the record can be trusted. Position reconciliation compares internal position state with custody, broker, administrator, CSD, or ledger evidence. Cash reconciliation compares fund cash with bank, custodian, payment, and settlement records. Transaction reconciliation checks trades, confirmations, allocations, settlement events, and fees. Corporate action reconciliation checks terms, elections, entitlements, and cash or position outcomes.

Exception handling is part of the accounting process. A break may be immaterial, timing-related, pending a source file, caused by an identifier mismatch, or caused by a substantive record error. The platform should route each break to an owner, capture the resolution basis, and preserve the adjustment history. A close process without exception state is difficult to supervise.

Reporting should come from controlled state. The platform may support NAV oversight, shadow accounting, administrator review, accounting feeds, management reporting, investor allocation support, audit packages, or regulatory reporting inputs. The strongest output is one that can be traced back to source events, reconciliations, approvals, and evidence.

Digital assets and tokenized fund activity add more fields to the same operating problem. Tokenized fund units, tokenized money market funds, stablecoin settlement legs, or on-chain transfers require token identifiers, wallet or custody records, chain identifiers, transaction hashes, finality state, decimal precision, and valuation evidence. Those records should join the fund accounting control model instead of forming a separate side process.