Direct answer
Cross rates express the exchange rate between two currencies using one or more intermediate “reference” currencies (for example, deriving A/B from A/Ref and B/Ref). Their main limitation is that the mathematical relationship only holds under shared assumptions—especially consistent quoting (bid vs ask), timing, and market conditions. In practice, those assumptions often fail, so a computed cross rate may differ from the rate you can actually trade.
Mechanism and definition
A cross rate is a derived conversion rate between currency pairs. Common ways to express it include:
- Quoting convention: whether you treat a currency pair as “base/quote” (how many units of quote currency per one unit of base currency).
- Reference currency: the intermediate currency used to link the two pairs.
- Math approach: using either multiplication or division of other currency rates, depending on how pairs are defined.
This works cleanly only if all input rates refer to the same moment and use compatible bid/ask conventions. “Stable mechanics” means the algebra is straightforward once the definitions are fixed. The “variable” part is the market inputs you plug in.
Evidence and example (with explicit assumptions)
Assume you want the cross rate for Currency A versus Currency B using a reference Currency C.
- Suppose the market quotes you use are mid prices at the same time.
- Suppose both input pairs use the same style of expression (for example, A/C is “C per A” and B/C is “C per B”). Under these assumptions, you can compute A/B from the two inputs with consistent units.
Now change one assumption: instead of mid prices, you compute using bid for one pair and ask for the other (a common mismatch when data sources differ). Even if the algebra is correct, the derived cross can become systematically biased because bids and asks represent different sides of the market. Another failure mode is timing: using A/C from one timestamp and B/C from a slightly different timestamp can create an apparent inconsistency during fast moves.
Limitations and risks
At least one material limitation is that cross-rate calculations are sensitive to data compatibility:
- Bid/ask mismatch: Inputs must reflect the same market side logic; otherwise, the cross can be meaningfully off.
- Timing differences: Exchange rates change continuously; “derived” results depend on how synchronized the inputs are.
- Execution and liquidity differences: Even if the computed cross looks internally consistent, actual execution may face spreads, partial fills, slippage, or depth constraints.
- Costs and frictions: Trading costs and operational factors can prevent the realized conversion from matching any theoretical cross.
A second limitation is interpretability: a cross rate is not automatically a signal of future movement. Historical relationships can help with understanding algebra and conventions, but they do not establish that the same relationship will persist under new liquidity, volatility, or quoting conditions.
Finally, cross rates can be less useful when you must compare them across providers or platforms. If one source publishes different quote types (mid vs indicative vs executable) or different conventions, the “same” cross-rate concept can produce different numbers.
How to verify and what to check next
To independently verify cross-rate facts, treat it as a definition-and-input problem rather than a predictive one:
- Confirm the pair conventions (base/quote direction) used in your inputs.
- Confirm the reference currency and whether it matches across all inputs.
- Check whether your inputs are mid, bid, or ask, and keep them consistent.
- Check timestamp alignment and whether the data represent executable pricing or estimates.
If you find that small changes in quote type or timing cause large differences in the derived cross, that is itself evidence of a key limitation: real markets rarely respect the simplifying assumptions behind a clean cross-rate computation.