Direct answer
Cross rates are exchange rates for one currency pair derived from two other currency pairs. The main risks come from (1) how market prices for the underlying pairs move, (2) how the cross rate is calculated and implemented, (3) how costs and execution timing affect what you actually receive, and (4) how you interpret the cross rate versus what is realistically tradable or hedgeable. Because these elements can vary independently, a cross rate can look consistent in theory while outcomes differ in practice.
Mechanism: what a cross rate is
A cross rate expresses the value of currency A relative to currency C when you do not directly observe A/C as a primary quote. A typical approach uses a relation such as:
- If you have A/B and B/C, then A/C can be computed from them using arithmetic (multiplication or division), depending on the quote conventions.
Key assumptions for any calculation are:
- You use the correct quote direction (base/quote ordering).
- You use consistent spot-vs-forward conventions.
- You apply the same timestamp or effectively “synchronized” inputs.
- You include the same treatment of spreads or fees (if you are comparing to an executable price).
If any assumption is violated, the derived cross rate can be systematically wrong even if each underlying input is correct.
Evidence or example: realistic scenarios and what can go wrong
Consider a scenario where you compute A/C using two underlying rates: A/B and B/C.
-
Market movement risk (path dependence) Even if A/C is the quantity you watch, it inherits sensitivity to both A/B and B/C. If B changes quickly versus both A and C, the cross rate can change rapidly. Also, the “most recent” inputs may not correspond to the same market moment, so the computed cross rate can lag or jump.
-
Implementation risk (calculation and data alignment) If your A/B and B/C inputs come from different feeds, different time stamps, or different quote conventions, the cross rate calculation can be off. For example, mixing a quote quoted as “B per A” with one quoted as “A per B” requires different arithmetic; otherwise the derived value can be inverted.
-
Execution and cost risk (realized vs computed) A cross rate might be computed from mid-market prices, but execution often occurs through liquidity that has a spread and possibly additional costs. If you implement the cross by trading through two legs (A/B and B/C), the realized outcome depends on the spreads, partial fills, and the time gap between legs. Two legs rarely have perfectly synchronized pricing, so realized results can deviate from the single computed cross.
-
Counterparty and operational risk (process and settlement) Even when prices are correct, operational details—how orders are handled, how pricing is updated, whether a venue can provide both legs at the intended size, and how settlement is processed—can affect the practical ability to obtain the derived exposure.
Limitations and risks: what cannot be guaranteed and how to verify
Cross rates involve uncertainty because the inputs, the calculation method, and the real-world trading process are not identical. Historical relationships between currencies do not establish future behavior of the cross rate, especially during regime shifts or periods of low liquidity.
Material limitations and risks you can independently check include:
- Consistency: verify quote direction and conventions before computing.
- Synchronization: compare whether the two underlying rates use comparable timestamps.
- Pricing basis: confirm whether you are using mid, bid/ask, or executable pricing.
- Cost realism: assess how spreads and fees would alter the effective cross rate.
- Failure mode: recognize that liquidity constraints or execution timing can break the link between the computed cross rate and the realized outcome.
Verification and next question
To verify your understanding of cross-rate risk, work from your own clearly stated assumptions: specify quote conventions, choose whether you use mid or executable prices, and define the timing for input rates. Then ask which step could fail—data alignment, convention handling, cost inclusion, or execution timing. If you want a focused next step, clarify whether your goal is purely computational understanding (the math) or operational understanding (how realized prices can differ).