These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Crypto Exchange Platform
- Features
- Reconciliation
Reconciliation
Compare provider movements with confirmed instructions and dated account positions.
OverviewExecution exceptions×
Crypto Exchange Platform · Reconciliation
New
Execution exceptions
Executions
| Provider event ID | Executed at | Amount USD | State | Account | Matched instruction | |
|---|---|---|---|---|---|---|
| PEI-105 | 10 Oct | 400 | Unmatched | TA-110 | INS-64428 | |
| PEI-158 | 21 Oct | 190 | Exception | TA-140 | INS-84012 | |
| PEI-840 | 21 Oct | 340 | Unmatched | TA-140 | INS-94960 | |
| PEI-647 | 08 Oct | 270 | Exception | TA-110 | INS-34105 | |
| PEI-373 | 13 Oct | 700 | Unmatched | TA-130 | INS-26101 |
6 of 6 records
PEI-105Executions · EXC-47289
UnmatchedExecuted at10 Oct
Amount USD400
AccountTA-110
Matched instructionINS-64428
What you can do
Run the operating work
A provider supplies an execution event for a trading account and a position snapshot dated after it. Operations locates the linked confirmed instruction and compares the account, amount and confirmed occurrence date. Only an exact match can move the execution from Unmatched to Matched. A differing amount or date remains unmatched or becomes an exception for a person to investigate.
How the work is organized
- Identify the movement. Operations Analyst keeps the provider event identifier with its account, amount and execution date.
- Compare the instruction. Match only when the account, exact amount and confirmed occurrence date agree.
- Check the position. Compare the signed confirmed movements with a dated provider snapshot and retain differences for review.
What to agree during setup
Agree the provider ledger opening balance and the sign assigned to confirmed movements. Compare the resulting expected position with the provider snapshot for that same account and date. Keep the snapshot identifier and its ledger and available US dollar amounts; the available amount and ledger amount may answer different questions. Decide who owns a discrepancy and when a correction requires renewed review.
Check the handoff on an actual case
Use one provider movement whose amount and date agree with confirmed evidence, then one with the correct amount but a different date. The first can be matched after account identity is checked; the second stays visible. Compare a dated snapshot against opening balance plus signed confirmed movements. Let the reviewer inspect the exception and original provider evidence before any correction is recorded.
Use two provider movements for the same account and amount but different dates. Only the movement on the confirmed occurrence date qualifies for a match. A second account with the same amount is another mismatch. Compare the provider snapshot’s ledger balance with the expected ledger position; keep its available balance separate. The reviewer should be able to follow each difference back to the source event and instruction.
When a provider sends a corrected event, retain the original identifier and the correction evidence. Recheck the linked instruction and dated position instead of overwriting the earlier comparison. A matched movement and a balanced account position are separate checks, and both should be explainable from source records.
What your team sees
- Execution exceptions — Investigate unmatched or exceptional movements by account and event identifier.
- Confirmed instructions — Check the provider outcome before linking a movement.
- Verified provider evidence — Compare event date and amount with the execution under review.
Follow the work through
See instruction review and provider reconciliation for the full handoff. Implementation sets out the pilot sequence.
What it keeps track of
Data model- Executions
- Source-identified provider movements matched against instructions.
- Position snapshots
- Dated provider position snapshots for a trading account.
- Trading accounts
- Provider-held trading accounts owned by a counterparty.
- Instructions
- Typed instructions moving through authorization, submission and confirmation.
- Execution evidence
- Provider statements, confirmations, settlement notices and corrections for an instruction.
Who uses it
Permissions- Operations Analyst
- Compares provider movements and account positions.
- Independent Finance Reviewer
- Investigates discrepancies and disputed evidence.
- Auditor
- Inspects the retained events, snapshots and decisions.
Set up Crypto Exchange Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.