IBOR Solution

Positions are the visible part of the IBOR. A useful solution has to distinguish current position, settled position, pending trade impact, projected position, custodian-confirmed position, and exceptioned position. A single number without state can mislead the user. The record should show whether it includes trade-date activity, unsettled trades, corporate action effects, pending transfers, or manual adjustments.

Cash is equally important. An IBOR solution should help teams understand settled cash, unsettled cash, projected cash, receivables, payables, income, fees, FX, and settlement funding. Available cash is an operating judgment formed from records and controls. If pending buys, pending sells, failed settlements, FX conversions, income receivables, and fees are not modeled clearly, teams may trade or fund settlement from a false cash view.

Exposure depends on reference data and classification. Issuer, sector, country, currency, asset class, maturity, counterparty, collateral, rating, token identifier, and legal entity mappings affect how a portfolio is understood. An IBOR solution should make these dimensions part of the record because they influence investment decisions, compliance monitoring, risk review, and reporting.

Reconciliation gives the record weight. The IBOR may be faster than the accounting book, but it still needs evidence. Internal positions, cash, trades, and corporate action effects should be compared against custodian, broker, administrator, bank, CSD, or ledger records. Differences should be labeled as timing items, breaks, adjustments, or unresolved exceptions.

The strongest IBOR solution does not collapse IBOR, ABOR, and PBOR into one vague record. It shows how each view is formed. IBOR supports current investment state. ABOR supports accounting state. PBOR supports performance state. The views can share source events and controls while keeping their purpose and timing clear.

Capture brings in activity from front-office, middle-office, custody, broker, administrator, bank, pricing, corporate action, and ledger sources. Each event should retain provenance: source system, timestamp, raw record, normalized fields, mapping status, and workflow state.

Normalization turns fragmented records into a common investment data model. The same security may appear under different identifiers. Accounts may be grouped differently across custodian, broker, administrator, and internal systems. Cash may be shown by currency, value date, settle date, or account. A controlled IBOR solution should expose these differences rather than bury them in a nightly file process.

Projection is the key IBOR function. The system uses trade-date activity, pending settlement, expected cash, corporate actions, income receivables, payables, FX, collateral, and transfers to estimate current and forward-looking state. A projected position or cash figure should carry status, timing, and evidence so users know how much confidence to place in it.

Reconciliation compares the IBOR state against external evidence. Position reconciliation, cash reconciliation, transaction reconciliation, corporate action checks, price checks, and FX checks all support trust in the record. The goal is not to eliminate every timing difference. The goal is to classify differences and prevent unknown breaks from becoming decision inputs.

Exception control determines whether the IBOR can be used. Breaks should have cause, owner, materiality, evidence, comments, repair action, and approval status. Manual adjustments should have reason codes and maker-checker controls. A position override without traceability weakens the record more than an open break with clear ownership.

Publication sends the controlled view to users and downstream systems. Portfolio teams may consume current positions, cash, and exposure. Operations teams may consume exceptions and settlement state. Accounting teams may consume records for ABOR handoff. Performance teams may consume PBOR inputs. Compliance teams may consume limits and evidence. Data teams may consume normalized APIs and lineage.