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.
- Stock Trading Platform
- Features
- Positions
Positions
Provider position snapshots by account and instrument.
OverviewPosition snapshot calendar×
Stock Trading Platform · Positions
New
Position snapshot calendar
Position snapshots
| Snapshot number | Account | Instrument | As of | Quantity | Cost basis USD | |
|---|---|---|---|---|---|---|
| PS-37587 | TA-120 | INS-6399 | 13 Oct | 410 | 940 | |
| PS-44262 | TA-130 | INS-8754 | 05 Oct | 170 | 230 | |
| PS-52916 | TA-130 | INS-8064 | 15 Oct | 270 | 430 | |
| PS-25232 | TA-130 | INS-4953 | 09 Oct | 690 | 650 | |
| PS-36877 | TA-110 | INS-9100 | 13 Oct | 200 | 900 |
6 of 6 records
MVU-275Position snapshots · PS-37587
AccountTA-120
InstrumentINS-6399
As of13 Oct
Quantity410
Cost basis USD940
What you can do
Keep the provider's view of every position by date
A position snapshot records what the provider says an account holds in an instrument as of a date: the quantity, the cost basis in US dollars, the mark price and the resulting market value, with the provider’s snapshot ID. Snapshots are kept by date, so the desk can see how a position stood at any month-end or on the day a question was raised.
Snapshots sit beside the desk’s own orders and executions. The operations analyst compares the quantity in a snapshot with the filled orders and executions for that account and instrument; a difference is a break to resolve with the provider or custodian before positions are reported. Because each snapshot carries its provider ID, a reloaded file does not create a second snapshot for the same date.
Market value is mark price times quantity as reported, and cost basis comes from the provider. Pricing, charts and performance analytics stay in your market data and portfolio tools; this record is the reconciled position the desk relies on.
How the work is organized
Operations analysts load and check snapshots; traders and the desk manager read them.
- As of a date. Every snapshot states the date it describes.
- Provider ID on every snapshot. Reloads do not duplicate.
- Checked against fills. Snapshot quantity is compared with the desk’s executions.
What to agree during setup
Agree which accounts and instruments are snapshotted, how often, and from which provider. Agree how a break between a snapshot and the desk’s fills is investigated and who signs it off. Decide how long snapshots are kept. Prepare examples of a matching snapshot, one with a quantity break and one reloaded twice.
Check the handoff on an actual case
At month-end the custodian’s snapshot shows 120,000 shares of a stock in a client account. The desk’s filled orders for that account add up to 125,000. The analyst finds a 5,000-share sell filled late on the last afternoon whose execution had not yet been brought in. Once the execution is recorded, the desk’s figure matches the snapshot and the break is closed with a note on the order.
What your team sees
- Position snapshot calendar — Snapshots by date with quantity, cost basis, mark price and market value.
- Trading orders working — Orders still open that will change positions.
Follow the work through
- Order to fill: How fills build positions.
Check the data model before loading historical snapshots.
What it keeps track of
Data model- Position snapshots
- Provider position snapshots by account and instrument
- Trading accounts
- Custodied trading accounts used for orders
- Instruments
- Tradable instruments with venue and quote currency
- Executions
- Deduplicated broker executions per order
Who uses it
Permissions- Operations Analyst
- , Desk Manager, Trader.
- Analysts load and reconcile; the desk manager and traders read.
Set up Stock Trading Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.