FIOS · Architecture of a financial operations ecosystem

Capital markets operations run on dozens of systems that each keep their own copy of the truth. Copies drift, drift becomes breaks, and breaks become a reconciliation department. FIOS is designed the other way round: capture each business event once, validate it once, and let every process read the same record. It sits between existing systems and between firms; it replaces none of them.

The layers

Sourceswhat already exists
Book of record and order systems (FIX)Dealer chat: terms agreed between tradersExchange fills and clearing-house filesCounterparty confirmations (OTC, FX)Client allocationsSWIFT MT and ISO 20022Custodian and depository statementsMarket data and FX ratesIssuer and corporate action noticesExcel and CSV
▼ read-only connectors
Capture and normalizeevery dialect, one model
Translate each source's format into one event model, modelled on concepts from the open Common Domain Model (CDM)Read agreed terms from chat into structured fieldsValidate once: identifiers, check digits, dates, amountsKeep the original message beside the event
▼
The shared recordthe single source of truth
Append-only: nothing is overwrittenEach event fingerprinted and chained to the previous one: tamper-evidentCorrections are new events, never editsOne timeline across trades, positions, loans, cash, income and fees
▼ every event, applied once
Engineslogic, not copies
Matching with typed, agreed tolerancesLifecycle: trade, position, loan, income, corporate action, cashBreak prediction before settlementCompliance rules (configurable per firm)Billing: fees derived from events
▼
Viewsper desk and process
Front, middle and back officeSettlement and custodyIncome and corporate actionsTreasury, FX and cashLending and collateralFinance and billingRiskCompliance
▼ ▲ between firms
Shared workspacebetween firms
Both sides see the same record of a joint trade or loanEach firm sees only what concerns itAffirmation signed by bothDaily state agreed, not discovered at month-end
▼
Outputsback to existing systems
Booking filesISO 20022, FpML, CSV, JSONInvoices and fee statementsAccounting entriesRegulatory and audit extracts

Why every process knows at the same moment

One write, every view

An event is written once. Every view (settlement, custody, income, billing, compliance) is computed from the record in the same step. No process waits for a nightly batch, so none is ever behind another.

Views are not copies

A department's view is a definition (columns, filters, rules), never a second copy of the data. There is nothing to reconcile between departments, because there is only one record.

A break is one case, not ten tickets

When something differs, FIOS traces it to its root event and shows every process it reaches. Ten teams don't each open their own ticket for the same problem.

The fix is an event too

A correction is recorded as a new event. Every affected process clears in the same step, and the history shows exactly what was wrong, who fixed it and when.

Matched the moment each source arrives

Chat, before the booking settles in

OTC and FX trades are agreed on chat. FIOS reads the terms and compares the booking with them as soon as it is entered, before the counterparty's confirmation arrives.

Exchange, instantly

Each booking is compared with its exchange fill as the fill arrives, then with the clearing report at the end of the day.

Counterparties and clients, same day

Confirmations and client allocations are matched on arrival, well ahead of settlement and of the NI 24-101 matching deadline.

Custody, cash and fees, daily

Positions, cash, income, loans and fee statements are compared every day, not discovered at month-end.

Traced to the source

Every trade carries the user ID of the trader who entered it, the desk, the workstation, and where it was allocated. Every external message carries who sent it. When something breaks, the case shows where it started (a trader's booking, a client's allocation, a counterparty's confirmation, a custodian's notice, a market move) and every process it reaches, so the right person fixes it once.

One trade, from execution to invoice

  1. Agreement and execution: the terms agreed on chat or the exchange fill, and the booking with its trader, desk and workstation, recorded once.
  2. Confirmation: the counterparty's version arrives in its own format; both are matched field by field.
  3. Allocation and settlement: instructions are checked against the trade before they leave, not after they fail.
  4. Custody and positions: the expected position is compared with the custodian's, daily.
  5. Income and corporate actions: entitlements are computed from the position on the record date; elections are tracked against deadlines.
  6. FX and cash: expected cash per currency is compared with what actually arrives.
  7. Lending and collateral: fees accrue daily on agreed terms; coverage is watched against the minimum.
  8. Billing: commissions, custody and lending fees are derived from the same events, then compared with each counterparty's statement.
  9. Finance, risk and compliance: accounting entries, exposures and rule checks read the same record, so none of them disagree with operations.

Design principles

PrincipleWhat it means in practice
Between, not instead ofExisting systems keep running. FIOS connects them and the firms around them.
Capture once, use everywhereEach fact enters once. Every process reads it from the same place.
Agreed tolerance, explicitRounding and price-source noise are absorbed by tolerances both sides agree on; a real difference is never hidden.
Nothing edited, everything traceableAppend-only record, chained fingerprints, corrections as events.
Standards in and outFIX, SWIFT MT, ISO 20022, FpML, CDM, CSV: speak each system's language rather than ask it to change.
Read-only firstA pilot runs beside the current process on read-only data and is measured against it before anything is relied on.
People decide what mattersThree levels: FIOS acts on routine matches; FIOS proposes and a person approves; a person always decides on judgement calls.

This page describes the design. The prototype on this site implements it on generated sample data; connecting it to a firm's own systems is what a pilot does. See Ecosystem to watch it run.