1. Stock Trading Platform
  2. Features
  3. Executions and evidence
Feature · Executions and evidence

Executions and evidence

Broker executions and provider evidence lines verified against instructions.

OverviewExecution evidence unverified
Stock Trading Platform · Executions and evidence

Execution evidence unverified

Approval conditions

New
Evidence numberParentLine numberProvider event IDExecuted quantityExecuted price USD
EE-24096INS-92628240PEI-797230700
EE-86514INS-81609290PEI-652130300
EE-27992INS-33654350PEI-155560110
EE-24327INS-52951790PEI-123370830
EE-36741INS-72905590PEI-23570780
6 of 6 records
PEI-797Execution evidence · EE-24096
ParentINS-92628
Line number240
Executed quantity230
Executed price USD700
Fees USD620
Example screen with sample data

What you can do

Confirm an instruction only on verified evidence

When the provider reports back, each report becomes an evidence line on the instruction: a line number, the provider’s event ID, when it happened, the executed quantity, executed price and fees in US dollars, and the instruction revision it refers to. Lines start as pending. An operations analyst reconciles each one against its instruction and marks it verified when quantity, price, fees, revision and scope all match, or rejected when they do not.

Each provider event is taken once. A repeated event ID returns the earlier result and leaves a receipt, so a provider that sends the same message twice does not double-count. The instruction moves to confirmed only when verified evidence covers what was instructed; partial evidence leaves it open at the provider.

Broker executions on trading orders are kept beside the evidence: execution number, provider execution ID, quantity, price, fees, notional and time. A reversal names the execution it reverses, so a broker correction is recorded as a new line rather than an edit.

How the work is organized

Operations analysts work the unverified list and the recent executions; traders see their instructions confirm.

  • Pending until verified. Unverified evidence never confirms an instruction.
  • Each event once. Duplicate provider events are recognised and ignored.
  • Reversals, not edits. A broker correction is its own execution.

What to agree during setup

Agree the tolerance for price and fee differences, if any, and who decides on a line outside it. Agree which provider events count as evidence and how their IDs are mapped. Agree how broker reversals are reported and posted. Prepare examples of a matching line, a line with the wrong fees, a duplicate event and a reversal.

Check the handoff on an actual case

An instruction to buy US$1.5 million of an exchange-traded fund is submitted. The provider sends two evidence lines. The first matches quantity and price and is verified. The second shows fees of US$310 against an agreed US$210; the analyst rejects it and asks the provider for a corrected line. The instruction stays open at the provider.

The corrected line arrives with a new event ID and is verified. Verified evidence now covers the instruction, so it moves to confirmed with the confirmation time recorded.

What your team sees

  • Execution evidence unverified — Pending evidence lines with quantity, price and fees.
  • Recent executions — Broker executions with notional and fees.
  • Instructions open at provider — Instructions still waiting for evidence.

Follow the work through

Check the data model before mapping provider events.

What it keeps track of

Data model
Execution evidence
Provider execution evidence lines awaiting verification
Executions
Deduplicated broker executions per order
Instructions
Trading instructions prepared, authorized and submitted to providers
Trading orders
Orders submitted to the broker connection

Who uses it

Permissions
Analysts verify; traders follow their instructions through.

Set up Stock Trading Platform your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started