← Glossary

Devancore Post-Trade Glossary

Investment Accounting Software

Software that turns institutional trades, positions, cash, accruals, corporate actions, tax lots, reconciliations, and close controls into accounting-ready investment records.

Definition

Investment accounting software maintains the controlled investment records used to turn portfolio activity into accounting-ready data. It sits around the post-trade lifecycle: executed trades, allocations, positions, cash movements, settlement status, income, accruals, fees, expenses, tax lots, corporate actions, reconciliations, and close evidence.

The core problem is record quality. An accounting record is only useful when the firm can explain the source event, the current state, the accounting impact, and the evidence behind it. A trade that has been executed but not settled may belong in the investment view, but it should not be treated the same way as a custodian-confirmed settled position. A coupon accrual may be expected, but it still depends on instrument terms, calendar rules, currency, rate source, and posting policy. A corporate action may change quantity, cash, income, tax lots, or entitlement records, but the treatment depends on the event terms and the firm's election.

Investment accounting software is therefore different from generic accounting software. Generic accounting systems usually start from journals, invoices, bank transactions, and enterprise finance entries. Investment accounting starts from instruments and lifecycle events. It must understand securities identifiers, trade date and settlement date, custody records, market calendars, corporate actions, income schedules, FX, tax lots, position lots, valuation inputs, and reconciliation evidence.

Investment accounting records

Investment accounting records

Investment accounting software connects operating records to accounting and reporting views.

Record Primary user Control question
IBOR Portfolio and operations teams What do we expect to own, owe, receive, or deliver?
ABOR Accounting, finance, administrators, auditors What has been confirmed, posted, reconciled, and closed?
PBOR Performance and client reporting teams What records support returns, attribution, and reporting?
Subledger Accounting and integration teams What detailed postings should feed the general ledger?
General ledger Corporate finance What summarized accounting entries support financial reporting?

The investment book of record (IBOR), accounting book of record (ABOR), and performance book of record (PBOR) are related views of the same economic activity. The IBOR supports timely investment and operations decisions. The ABOR supports accounting, NAV oversight, financial reporting, and audit. The PBOR supports performance reporting and attribution. A subledger preserves investment-level accounting detail and can feed summarized entries to the general ledger.

The distinction matters because each record has a different control question. The IBOR asks what the portfolio expects to own, deliver, or receive. The ABOR asks what has been confirmed, posted, reconciled, and closed. The PBOR asks whether the data used for returns and attribution is complete and explainable. A strong investment accounting system does not blur those records. It keeps timing differences visible and makes the path from source event to accounting record traceable.

Trade-date and settlement-date treatment is one of the clearest examples. On trade date, the firm has committed to buy or sell. That affects expected positions, cash forecasting, exposure, restrictions, and liquidity planning. On settlement date, custody, clearing, and cash records confirm whether the economic commitment became a settled accounting record. The investment accounting process must preserve both states because operations, accounting, and reporting teams need different answers at different points in the lifecycle.

How it works

Investment accounting software works by collecting source activity, normalizing it into a governed operating record, applying workflow controls, and producing accounting-ready outputs only when the required state and evidence are present.

The process usually starts with trade and activity ingestion. Source records may come from an order management system, execution management system, broker feed, custodian file, bank record, corporate action notice, pricing source, FX feed, or reference data system. Each source has its own identifiers, cutoffs, formats, and timing. The accounting process depends on mapping those records to the correct instrument, account, legal entity, portfolio, currency, calendar, and accounting policy.

Workflow controls

Workflow controls

Each workflow produces accounting impact only when the required record and evidence are present.

Workflow Accounting impact Evidence required
Trade capture Creates expected position, cash, and tax-lot activity Executed trade, account, instrument, side, quantity, price, broker, allocation
Settlement Moves expected activity into confirmed accounting state Settlement status, custodian or clearing confirmation, cash movement
Cash processing Updates balances, receivables, payables, and funding view Bank or custodian record, currency, value date, source reference
Accruals and income Posts coupon, dividend, fee, expense, or amortization activity Instrument terms, calendar, rate, calculation method, approval
Corporate actions Changes position, cash, income, cost basis, or entitlement records Event notice, election, entitlement calculation, effective date
Reconciliation Controls whether records are trusted for close and reporting Matched source records, exception classification, resolution history

After ingestion, the system enriches each event. A trade may need settlement instructions, broker commission detail, exchange fees, tax lot treatment, instrument classification, currency, market, price source, and account allocation. A fixed-income position may need coupon schedule, day-count convention, maturity, call features, accrued interest, and amortization method. A fund or account may need expense accrual rules, reporting currency, valuation policy, and close calendar.

Reconciliation controls determine whether the record can be trusted. Position reconciliation compares internal position state against custodian or administrator records. Cash reconciliation compares internal cash movements against bank or custodian activity. Trade reconciliation compares executed trades, allocations, broker confirmations, and settlement records. Income and corporate action reconciliation verifies that expected entitlements were calculated and posted correctly. Unresolved breaks should keep their source context, owner, age, materiality, and resolution history attached to the record.

The close workflow turns controlled records into accounting outputs. Accounting teams review exceptions, approve adjustments, confirm reconciliations, and prepare reporting evidence. In some operating models, the investment accounting system feeds a detailed subledger, which then sends summarized entries to the enterprise general ledger. The subledger preserves investment-level detail that the general ledger usually should not carry line by line.

Multi-currency and multi-book accounting add another layer of control. A firm may need local currency, base currency, tax basis, statutory basis, management basis, and performance basis views. Those views may use different price sources, FX rates, recognition rules, or cutoff policies. The system should make the basis visible rather than hiding differences inside a single balance.

Digital assets and tokenized securities do not remove the accounting problem. They add new evidence fields: wallet, address, token identifier, transaction hash, block timestamp, protocol finality, and custody model. The same accounting questions remain: what changed, when did it become final, what cash or settlement asset moved, how was it valued, what tax lot or cost basis changed, and what evidence supports the record.

In Devancore™

Devancore supports the operating records investment accounting depends on: trades, positions, cash, settlement events, reference data, controls, reconciliations, and evidence.

The platform is framed as a post-trade operating and control layer. It helps maintain the state that accounting, finance, operations, compliance, and reporting teams need before a record is trusted for close or downstream reporting. That includes source event lineage, settlement status, position state, cash state, exception history, approval trail, and supporting evidence.

For investment accounting workflows, Devancore can connect the path from trade capture to accounting-ready record. A trade enters as an operating event. The event is enriched with account, instrument, settlement, tax lot, and reference data context. The system tracks whether the event is expected, pending, matched, failed, settled, reconciled, or approved. Breaks stay attached to the source event rather than becoming detached spreadsheet rows.

This matters for ABOR, IBOR, and PBOR workflows. The same underlying event can support an expected investment view, a confirmed accounting view, and a performance reporting view without losing the source trail. A settled record can point back to the trade, allocation, settlement instruction, custodian confirmation, cash movement, pricing input, corporate action event, adjustment, and approval history that produced it.

Devancore should not be described as a generic general ledger or as a full fund administrator. The stronger product boundary is more precise: Devancore organizes post-trade records, workflow state, reconciliation evidence, and reporting inputs that accounting and reporting processes depend on. It can feed accounting systems, reporting systems, compliance workflows, and review processes while preserving the operational trail behind each record.

Ops teams can use Devancore's conversational interface to ask controlled questions over the investment accounting record: which positions remain unreconciled, which cash breaks affect close, which trades have settlement-state conflicts, which corporate actions changed cost basis, or which records lack approval evidence. The value is not free-form chat. The value is permissioned access to governed records with source evidence attached.