08 / Post-trade
AvailableReconcile every fill, book every movement and settle with every counterparty
Qubit's post-trade module captures every trade, reconciles your records against venues and custodians, books everything in a double-entry ledger and tracks settlement and treasury movements until they are complete. Breaks are found by the system and resolved by people, with a record of who did what.
- Layer
- Core · Standalone · Add-on
- Works on its own
- Yes
- Interfaces
- OMS, FIX drop copy, venue APIs, custody connectors, file import
01 / The problem
Reconciliation should not take until lunch
Every morning, someone in operations downloads fills from each exchange, statements from the custodian and trades from the OMS, then matches them in a spreadsheet. Fees are booked differently on every venue. A missing fill turns into an hour of searching. OTC trades sit in chat until someone books them. When a client asks why their balance is off, the answer depends on whoever did the reconciliation that day.
02 / What it does
What the module covers
- 01
Trade capture
Every fill from every venue, every RFQ trade and every OTC trade, captured from Qubit, drop copy, venue APIs or file import.
- 02
Three-way reconciliation
Internal records against venue reports against custody balances, matched at trade, fee and balance level.
- 03
Break management
Unmatched or mismatched items become breaks with a type, an age and an owner. Resolutions are recorded with a reason and, where set, a second approver.
- 04
Double-entry ledger
Every trade, fee, transfer, deposit and withdrawal is booked as balanced entries per account, entity and asset.
- 05
Counterparty settlement
Track what you owe and are owed per OTC counterparty, net it where agreed and follow each obligation until both legs settle.
- 06
Treasury
See balances by venue and custodian against targets, and generate transfer instructions to rebalance.
- 07
Fee accounting
Trading fees, rebates and network fees are captured per fill and transfer and booked to their own ledger accounts.
03 / How it works
From fill to settled
- 01
Capture
Fills and trades arrive from the OMS, venue drop copy and venue APIs. External or legacy records can be imported from files.
- 02
Book
Each trade creates balanced ledger entries for the asset bought, the asset sold and the fees.
- 03
Match
At intervals you set, Qubit compares internal records with venue fills and balances, and with custody balances.
- 04
Resolve
Anything that does not match becomes a break and is routed to the owning team. Adjustments are booked as their own entries, never as edits.
- 05
Settle
OTC and RFQ trades create settlement obligations. Qubit nets them where agreed, produces settlement instructions and marks them settled when the transfers are confirmed.
04 / Specifics
Technical specifics
- Reconciliation types
Trade level (fill ID, quantity, price, fee), balance level (per asset per account) and transfer level (deposits, withdrawals and internal transfers against on-chain or custodian records).
- Matching rules
Exact and tolerance-based matching per field, configurable per venue. Fees can be matched by amount or by rate.
- Break types
Missing internally, missing at venue, quantity mismatch, price mismatch, fee mismatch, balance difference, unconfirmed transfer.
- Ledger
Double-entry and append-only, with a chart of accounts per entity. Corrections are reversing and correcting entries, never edits. Every entry links to the trade, transfer or adjustment that caused it.
- Settlement
Bilateral obligations per counterparty, gross or net, with settlement status (pending, partially settled, settled, failed) and aging.
- Treasury instructions
Qubit creates transfer instructions. Your custodian or exchange executes and signs them. Qubit never holds private keys and never moves funds itself.
- Inputs
Qubit OMS, FIX drop copy, venue REST and WebSocket APIs, custody connectors, CSV import.
05 / Controls and audit
What you configure, and what gets written down
Configurable
- Reconciliation intervals
- Exact or tolerance-based matching per field and per venue
- Fee matching by amount or by rate
- Break owners and second approval on resolutions
- Chart of accounts per entity
- Netting agreements per counterparty and treasury targets
Logged to the audit trail
- trade captured · source and trade ID
- ledger entry · linked trade, transfer or adjustment
- break opened · type, age, owner
- break resolved · reason, user, approver
- settlement status change · pending to settled or failed
- transfer instruction created and confirmed
06 / Where it fits
- Works on its own
- Yes, for reconciliation and trade capture: it matches your own records against venue fills, balances and custody, read-only.
- Needs the core
- The position ledger is part of the core. Settlement and treasury are add-ons that need the core and custody connectors.
- Who uses it
- Operations and finance teams at brokers, banks, OTC desks and exchanges; fund administrators and middle offices.
FAQ
Questions we get asked
Can we run reconciliation without the Qubit OMS?
Yes. Standalone reconciliation takes your own trade records by file or API and matches them against venue and custody data from read-only keys.
Does Qubit move funds during settlement?
No. Qubit tracks obligations and creates instructions. Transfers are approved and signed in your custody platform or by your bank. Qubit is never in the flow of funds.
How are manual corrections controlled?
Every adjustment is a new ledger entry with a reason, the user who made it and, where configured, a second approver. Nothing in the ledger is ever edited or deleted.
Can the ledger hold balances for our end clients?
Yes. Accounts can be set up per end client, which is the basis of the white-label brokerage configuration. Client assets themselves stay with your custodian and bank.
Close the books on crypto the way you close them on everything else
A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.