Slippage

Overview

Slippage arises because prices and available liquidity change between quotation and execution or because an order consumes multiple price levels. It can be positive or negative and occurs in order books, AMMs, foreign exchange, payments, and other conversion processes.

Slippage differs from explicit fees and quoted spread, though all affect total cost. Thin liquidity, large size, volatility, latency, routing, and blockchain transaction ordering increase uncertainty. Excessively loose tolerance can expose users to manipulation or unexpectedly poor execution.

Users should review estimated output, price impact, and all fees, then set tolerance appropriate to liquidity and urgency. Applications need minimum-received or maximum-paid protections and should explain reverts. Post-trade records should compare quote with final execution using consistent timestamps and quantities.

For Slippage, controls should compare independent sources and apply age, deviation, and notional limits.

Slippage can appear in the same workflow as blockchain and transaction ordering, but the records should remain separately identifiable. A relationship between them does not prove that pricing, execution, settlement, custody, or accounting has completed.

The scope of Slippage should preserve its defining condition: A displayed quote is not the realized economic outcome when liquidity, volatility, order size, latency, or provider markup changes execution. Teams should document when that condition begins, which event changes it, and what evidence shows that execution, settlement, or measurement is complete.

Operational data for Slippage should identify pair direction, source, timestamp, order size, quoted side, fees, and realized execution. It should also reflect that for reliable use, teams should record quoted pair or asset, direction, source, venue, observation time, quantity, bid or ask side, fees, and realized result. Changes to methodology or execution rules need a version and effective date so historical results remain interpretable.

Risk review should test for stale or misdirected quotes, hidden markup, thin depth, decimal errors, partial execution, and delayed settlement. Exceptions should remain open until the evidence supports closure, and any manual adjustment should record its reason, approval, and resulting financial effect. This added control specifically concerns the difference between an expected transaction price or amount and the actual result received when execution completes.