INTERMEDIATE ARTICLE 1 OF 5

Execution Quality and Transaction-Cost Analysis: Slippage, Rejects and Last Look

7 min read

Lesson objective: Measure requested versus filled prices, execution tails, rejects, price improvement and last-look effects instead of relying on speed claims.

The opening problem

A broker advertises average execution of 40 milliseconds. The statistic sounds excellent, but a fast fill can still be poor if the price is consistently worse than the quote available when the order was sent.

Execution quality is multidimensional. Intermediate traders should measure price, probability, speed and stability together.

Intermediate education begins when a learner stops asking only what forex execution quality means and starts asking how to define it, test it, falsify it and implement it after costs. The purpose of this lesson is to turn a familiar trading concept into an auditable research process.

Prerequisites

Ability to calculate pip value, notional exposure, margin and net P&L
Understanding of bid, ask, spread, slippage and overnight financing
A written risk limit and position-sizing method
Access to a spreadsheet, code notebook or platform report
Willingness to record losing and failed examples, not only successful charts

What you will learn

How to define forex execution quality without relying on hindsight.
Which variables must be fixed before testing.
How to separate market observation from interpretation.
How transaction costs, regimes and execution alter the result.
How institutional market participants frame the same problem.

Requested, benchmark and filled price

The requested price is the quote associated with the order. A benchmark can be the midpoint, arrival price or another defined reference. The fill is the actual execution.

Slippage must be signed from the trader’s perspective. A buy above the benchmark is adverse; a buy below is positive.

Research discipline

Write the rule in a form that another analyst can reproduce. Record the data source, timezone, market, timeframe, decision timestamp and execution convention. A visually convincing explanation is not enough when small definition changes can reverse the result.

Order-type differences

Market orders accept price uncertainty. Limit orders control price but risk no fill. Stop orders become aggressive after triggering in many systems.

Mixing all order types in one slippage average makes the statistic difficult to interpret.

Research discipline

Rejects and requotes

A rejection can result from stale price, insufficient margin, invalid size, credit limits or technology. A requote offers a new price instead of the original.

Rates should be segmented by session, order size and event conditions. A high reject rate in normal markets deserves different interpretation from one during an exceptional release.

Research discipline

Last look

Last look allows a liquidity provider a brief window to accept or reject a trade request under the venue’s rules. It can protect against stale quotes but creates fairness concerns when hold times or rejection practices are opaque.

Retail traders may not know whether last look exists in the liquidity chain. The practical evidence is fill and reject behaviour.

Research discipline

Average versus tails

An average can hide rare but severe negative slippage. Report median, 90th, 95th and 99th percentiles as well as maximum loss.

Strategies trading news or stops are often determined by tail execution rather than the ordinary average.

Research discipline

Implementation shortfall

Implementation shortfall compares the achieved result with the decision benchmark, including delay, spread, market impact and missed opportunity.

It connects strategy research with live implementation and reveals whether a theoretical edge survives actual trading.

Research discipline

Finance Chronicles research box

Minimum execution dataset

Decision timestamp
Submission timestamp
Acknowledgement timestamp
Bid, ask and midpoint
Order type and size
Trigger price
Filled price and quantity
Positive or negative slippage
Reject or requote reason
Session and event flag
Broker entity and platform

Without timestamps and quote-side data, an execution claim is difficult to verify.

The purpose of this box is to expose hidden assumptions. Intermediate analysis is not better because it contains more indicators or terminology. It is better when it states what was measured, how it was measured and what evidence would prove the idea wrong.

How an institutional desk approaches the problem

Institutional transaction-cost analysis compares venues and algorithms while accounting for order difficulty. Large urgent orders should not be compared directly with small passive orders.

The retail version should compare like with like: same pair, size, order type and market condition.

Institutional practice varies by mandate, venue and organisation. The transferable lesson is the separation of research, execution and risk. An attractive thesis can still be rejected because liquidity, capacity, correlation or legal constraints make implementation unsuitable.

Worked research example

Five hundred market orders:

Median slippage: −0.02 pip
Mean slippage: −0.11 pip
95th-percentile adverse slippage: −0.9 pip
Worst 1% average: −6.2 pips
Positive slippage frequency: 28%
Reject rate: 0.6%

A scalping strategy with 1.5-pip gross expectancy may survive the median but fail when the tail and spread are included. The relevant execution model depends on the strategy’s order distribution.

How to audit the example

Recalculate every numerical step.
Confirm that all inputs were available at the decision time.
Add spread, commission, financing and slippage.
Test nearby parameter values rather than one exact setting.
Review both successful and failed signals.
Separate in-sample design from out-of-sample validation.
Express the result in R, account currency and drawdown terms.

Failure modes and false confidence

Using speed as the only metric

Price quality and fill probability can be poor despite speed.

Averaging all order types

Market and limit orders have different selection effects.

Ignoring positive slippage

The study becomes one-sided.

Removing worst fills as outliers

Tail events can be economically real and strategy-defining.

Practical assignment

Export at least 200 orders from demo or small-live validation. Calculate signed slippage, fill rate and latency by order type, session and event status. Report medians and tails. Compare the live distribution with the cost assumptions used in the backtest.

Do not optimise the assignment until a desired result appears. Freeze the definitions first, preserve the original output and document every later change as a new strategy version.

Knowledge check

Can slippage be positive?
Why separate order types?
What does last look permit?
Why analyse tails?
What is implementation shortfall?

Show answers

1. Yes.

2. They have different execution objectives and fill behaviour.

3. A short accept-or-reject decision under venue rules.

4. Rare severe fills can dominate results.

5. The difference between decision benchmark and achieved execution.

Final takeaway

The intermediate standard for forex execution quality is not whether the chart explanation sounds persuasive. It is whether the concept can be defined before the outcome, tested with realistic execution, compared with a simple baseline and monitored for failure after deployment.

Related lessons

Previous lesson: FX Market Microstructure
Next lesson: Volatility-Based Position Sizing and Portfolio Currency Risk

Authoritative sources

Editorial and risk disclosure

This lesson is provided for educational and informational purposes only. It does not constitute financial, investment, legal, tax or trading advice. Forex, CFDs, futures and options involve substantial risk. Historical analysis, backtests and worked examples do not guarantee future performance. Product rules, client protections and legal availability differ by jurisdiction and legal entity.

Finance Chronicles Education Desk · Reviewed 2026-07-10