How Slippage Questions Work in Forex

Direct answer

In forex, “slippage questions” usually refers to the question of how much an order’s execution price differs from what you expected and why that difference happened. The key idea is mechanical: an order is submitted with some conditions, but by the time it is actually filled, the available price at the moment of execution may have changed. Slippage questions focus on quantifying that gap and understanding the inputs and failure modes behind it, without assuming a single, predictable outcome.

To explain it clearly, treat slippage as an execution mismatch between an expected reference price and an actual fill price. The expected reference could come from a quote you saw, a “market” price at submission time, a broker-provided price at the moment of acceptance, or a back-office record—different sources lead to different slippage numbers.

Mechanics: definition and how the “gap” forms

Slippage (in the execution sense) is commonly defined as:

Slippage = Actual fill price − Expected reference price

For buys, a positive difference means you paid more than expected; for sells, it can mean you received less than expected (sign conventions vary, so always state the rule you use).

A simple execution timeline helps separate stable mechanics from variable conditions:

Quote/reference is observed: You or a system observes a price (or a bid/ask) that becomes the “expected” reference.
Order is submitted: An order request is sent with an order type (for example, market-like or limit-like) and size.
Order reaches the execution venue/provider path: Between submission and execution, the order may pass through several systems.
Matching/execution happens: The order is matched or filled at the best available price at that moment (subject to the order type).
Fill is recorded: An actual fill price and timestamp are stored.
Comparison is computed: Slippage is calculated by comparing actual fill price to the chosen expected reference.

This is the heart of slippage questions: the “gap” exists because the expected reference and the actual fill are not generated from the same instant. Even with fast systems, the market can move and available liquidity can change.

Inputs and outputs: what to record to answer slippage questions

To answer slippage questions in a way you can independently verify, you need consistent inputs and measurable outputs.

Inputs to define

Expected reference price: Pick one and define it precisely. Examples of reference types include:
- the bid/ask you saw at the moment you clicked/place-requested (client-side view)
- the broker/provider quote/price at request acceptance (server-side view)
- a historical quote you later retrieve and map to your submission time
Order conditions: State the order type conceptually (for example, “market-execution style” vs “price-constrained/limit style”), the side (buy/sell), and the size.
Timing data: Use timestamps from the same clock domain if possible (or clearly explain any conversion).
Quote source: Identify where the expected reference came from (client display vs provider record vs market data feed).

Outputs to compute

Actual fill price: The recorded execution price.
Fill timestamp: When the fill occurred.
Slippage amount: The numeric difference using the stated sign convention.
Optional cost decomposition (educational, not predictive): For example, separate “price change over time” from “execution at a different available level,” if your data supports it.

A minimal worked example (with explicit assumptions)

Assume you define expected reference as “the ask price shown at order submission for a buy.”

At submission time, the expected reference ask is 1.12000.
The order is actually filled later at 1.11970.
Using Slippage = Actual − Expected, slippage = 1.11970 − 1.12000 = −0.00030.

This negative value means the fill price was lower than the expected reference for a buy under this definition. If you instead use a different reference (for example, a server acceptance quote), your slippage number may differ even if the fill price is the same.

Evidence and examples of why slippage can happen

Slippage questions often come up when users notice that actual fills differ from the price they associated with the order. Common, non-promotional explanations include:

Market movement between reference and execution: FX prices can move quickly; if the market moves against your position during the delay, the fill can reflect the newer available price.
Liquidity and order-book depth changes: Even if the “mid” doesn’t move much, the best available bid/ask levels can thin out, making the next executable price less favorable.
Execution path delay (latency): Network or system delays can increase the time gap between observing the reference and receiving the fill.
Spread dynamics: The bid/ask spread can widen temporarily; a quote-derived expectation can become stale sooner than you expect.
Order size relative to available liquidity: Larger orders can consume multiple price levels (depending on execution logic), changing the realized average fill.

A single numeric slippage value is therefore not the whole story. Two traders can see different slippage outcomes because their expected reference price sources and timing assumptions differ.

Limitations and risks: material failure modes in slippage analysis

Slippage questions have important limitations. Even when you compute slippage correctly by your definition, you may still reach misleading conclusions if assumptions or data are inconsistent.

Reference mismatch failure mode: If the “expected” price is taken from a client display while the actual fill is compared to a server-side quote, your comparison can overstate or understate slippage.
Timestamp misalignment: If timestamps come from different clock sources, you may attribute slippage to “market movement” when it was actually caused by measurement delay or rounding.
Order-type misunderstanding: Limit-like conditions can produce partial fills, rejection, or no fill. Comparing expected vs actual without handling such cases can be incorrect.
Averaging effects: Some systems may fill in parts. If you treat one fill record as a single outcome, you may ignore the difference between the first fill, subsequent fills, and the average fill price.
Spread and currency-pair formatting: Quoted decimals, pip conventions, and rounding rules can distort the numeric slippage if you do not standardize units.

Finally, slippage analysis does not guarantee future results. Historical relationships between “expected quote” and “later fill” do not establish a predictable slippage distribution for future orders.

Verification and next question to ask

A reliable way to verify slippage questions is to standardize your definitions and check consistency across records: