Trade records distinguish an order instruction, execution, trade date, confirmation, and settlement evidence so investors and operations teams can verify what actually occurred.
The trade date is the date on which a securities transaction is executed. A trade ticket is a document or electronic record of an order or trade, while an execution report, trade confirmation, and settlement record document later or different parts of the transaction. These records are related, but they do not prove the same fact.
For example, an order ticket can show that an investor instructed a broker to buy 100 shares. It does not, by itself, prove that the order filled. The execution report establishes the executed quantity and price; the confirmation provides the customer-facing transaction details; and the custody or account record shows whether the cash and securities were ultimately posted.
A securities transaction generates records at several stages. The labels differ across brokers and systems, but the evidence generally progresses from an instruction to a settled position.
The safest approach is to ask what each record proves rather than assuming that every screen or document is a completed-trade record.
| Record | What it usually establishes | What it does not establish by itself |
|---|---|---|
| Order ticket or order record | The instruction, account, security, side, quantity, order type, limit or stop, time-in-force, and entry time | That the order was accepted, routed as expected, or executed |
| Order-status message | Whether the order is open, rejected, canceled, expired, partially filled, or filled | The complete economics of every execution |
| Execution report | Executed quantity, price, execution time, and often venue or execution identifier | That cash and securities later settled without correction |
| Trade or deal ticket | A firm’s operational record of the transaction; content depends on the system and product | A universal legal meaning or a guarantee of final settlement |
| Trade confirmation | Customer-facing transaction details, including information required for the transaction and account | That every downstream custody or cash posting is complete |
| Clearing or settlement record | Matching, netting, delivery, payment, fail, or completion status | The original investment rationale or every order-routing event |
| Account statement | Period activity, positions, cash, and account-level entries | Every timestamp, rejected order, route, or partial-fill detail |
The term trade ticket is used broadly. On a trading desk it may mean a deal record created after execution. In another system, an order ticket begins before execution and is updated as fills arrive. The field names and status codes control the interpretation.
The trade date, often written as T, is the business date assigned to an executed transaction under the applicable market and firm’s processing rules. It starts the settlement timeline and can affect confirmations, cash planning, position reporting, corporate-action eligibility, tax records, and performance measurement.
Trade date should be distinguished from several nearby dates:
| Date | Plain meaning | Main evidence |
|---|---|---|
| Order-entry date | When the instruction was submitted | Order ticket and timestamp |
| Trade date | When the transaction was executed | Execution report and confirmation |
| Allocation date | When an institutional block is assigned among accounts | Allocation and affirmation records |
| Settlement date | When cash and securities are due to transfer | Confirmation, clearing, and custody records |
| Posting date | When an entry appears in a particular ledger or account | Account ledger or statement |
| Value date | Date from which cash, interest, or another economic effect is calculated in some markets | Contract and product-specific record |
These dates can coincide, but they are not interchangeable. A market order submitted after a venue closes might not execute until the next trading day. An order entered on Monday and filled on Tuesday has a Tuesday trade date even though the instruction began on Monday.
Execution timestamps should always be read with a time zone and market calendar. A transaction recorded late in one location can fall on the next calendar date elsewhere. Overnight sessions, foreign markets, holidays, and system cutoffs can also make a device timestamp differ from the trade date used by the broker or venue.
Do not infer the trade date from:
Use the executed status, execution timestamp, and confirmation.
A trade ticket records the economic and operational details needed to process, supervise, reconcile, and retain a trade. Modern tickets are usually electronic records connected to an order-management, execution-management, portfolio, or broker-dealer system.
A useful ticket commonly includes:
Not every field applies to every product. A bond ticket may emphasize yield, accrued interest, principal amount, and dealer capacity. An option ticket needs the underlying, call or put, strike, expiration, and contract quantity. A foreign-exchange deal ticket needs the currency pair, direction, amount, rate, and value date.
These records are often confused because an online brokerage interface may display them in one screen.
The order ticket captures intent: what the customer or trader asked the broker or system to do. It can exist even if the order is rejected or never trades.
The execution report captures a fill or a change in execution status. A single order can receive several reports as it is partially filled. The total executed quantity and weighted average price may therefore require more than one record.
The confirmation communicates the completed transaction to the customer and provides transaction-specific disclosures. FINRA advises investors to review confirmations and statements promptly, while the exact required content depends on applicable rules and the security.
The settlement record shows whether the cash and securities movement was completed, remains pending, failed, or was corrected. A valid execution can exist even when settlement later fails.
Assume an investor enters a day limit order at 10:05 a.m. ET to buy 100 shares of ABC at no more than $25.00.
| Event | Record | Result |
|---|---|---|
| Order entered | Order ticket | Buy 100 ABC, limit $25.00, day order |
| First execution | Execution report | 40 shares at $24.96 |
| Second execution | Execution report | 35 shares at $25.00 |
| Market closes | Order status | Remaining 25 shares expire unfilled |
| Confirmation produced | Trade confirmation | 75 shares purchased, execution details and applicable charges |
| Settlement completed | Account and custody record | Cash debited and 75 shares posted under the applicable cycle |
The order quantity was 100, but the executed position was 75. Treating the original ticket as the final trade would overstate both the shares acquired and the cash required.
The volume-weighted average execution price before fees is:
[(40 x $24.96) + (35 x $25.00)] / 75 = $24.9787
The confirmation or broker calculation may round the displayed average. The underlying execution reports remain the better source for reconstructing each fill.
Trade records help investors identify unauthorized activity, unexpected quantities, incorrect prices, fees, and settlement dates. A prompt review is more useful than waiting for a monthly or quarterly statement to reveal a discrepancy.
Operations teams use identifiers and timestamps to match the front-office instruction with execution, allocation, confirmation, clearing, settlement, and ledger entries. A mismatch can create a booking error, incorrect position, failed settlement, or unexplained cash balance.
Analysts need the correct measurement date and transaction amount. Accountants and controllers need evidence that the booked transaction belongs to the correct entity, account, period, instrument, and currency. Accounting recognition rules are a separate question from the market’s trade-date label.
Order and trade records support supervision, best-execution review, communications review, regulatory reporting, and audit trails. The relevant rule and retention requirement must be checked for the actual firm, product, and jurisdiction.
For the order instruction itself, see Order. For the completed fill, see Execution.
These sources focus on U.S. securities markets. Other products and jurisdictions can use different record labels, confirmation requirements, and settlement conventions.
This article is for financial education only. It does not determine the legal effect, tax treatment, accounting recognition, or suitability of a specific transaction. Use the governing confirmation, account agreement, market rules, and professional advice for a real dispute or reporting decision.