Direct answer: what a worked example means
A worked example of a currency converter shows the exact arithmetic for converting an amount from one currency into another. It states every assumption (for example, which exchange rate is used, whether it is a “mid-market” rate, and whether any fee is subtracted) so you can independently verify the result.
Mechanism and definition of a currency converter
A currency converter is a calculation tool that estimates how much money in one currency corresponds to an amount in another currency. The core mechanics are typically:
- Choose an exchange rate for a specific direction (e.g., 1 unit of currency A equals X units of currency B).
- Multiply the starting amount by that rate.
- If the converter includes costs, subtract or add them according to the provider’s stated method.
Stable mechanics vs. variable conditions:
- Stable mechanics: the math relationship between amount, rate direction, and unit conversions.
- Variable conditions: the rate you actually receive can differ from the rate assumed in the example due to market movement, the provider’s spread, and execution timing.
Assumptions you should always make explicit in a worked example:
- Which pair is being used and the direction (A→B versus B→A).
- What kind of rate it is (a mid-market rate versus a buy/sell rate).
- Whether fees exist and how they are applied (fixed amount, percentage, or included in the rate).
- Rounding rules (how many decimal places are shown).
Evidence or example: a transparent worked scenario
Below is a worked scenario with fully stated assumptions. This is an illustration of how the converter’s math could be done, not a claim about any live market price.
Scenario A: conversion with a quoted rate and no fees
Assumptions:
- You want to convert 1,000 units of Currency A into Currency B.
- The converter uses an assumed exchange rate: 1 Currency A = 0.90 Currency B.
- No fees, no spreads, and no rounding beyond the final display.
Calculation:
- Amount in Currency B = 1,000 × 0.90 = 900
Result under these assumptions:
- The converted estimate is 900 Currency B.
Scenario B: conversion that includes a fee
Assumptions:
- Same starting amount and exchange rate as Scenario A.
- A fee of 1% is applied to the starting amount in Currency A before conversion.
- The converter’s method is: fee = starting_amount × 1%, then convert the remainder.
Calculation:
- Fee in Currency A = 1,000 × 0.01 = 10
- Net amount in Currency A after fee = 1,000 − 10 = 990
- Amount in Currency B = 990 × 0.90 = 891
Result under these assumptions:
- The converted estimate is 891 Currency B.
Checking the direction (common arithmetic trap)
Assumptions:
- The same two currencies are involved, but someone uses the reverse relationship by mistake.
If the true rate were 1 Currency A = 0.90 Currency B, then the reverse would be 1 Currency B ≈ 1/0.90 ≈ 1.111… Currency A. Using the wrong direction changes the output even if the math is internally consistent.
Limitations and risks: what can make results differ
A worked example is useful, but it has material limitations:
-
Rate mismatch over time Even if the example uses a correct assumed rate, the real exchange rate you might get can change between the time you compute the estimate and the time a conversion is executed.
-
Spread and execution effects Providers often do not let you trade at exactly the mid-market rate. The effective rate can be worse than the assumed rate because of spreads and execution timing.
-
Fees can be applied differently Two converters can both show the same “rate,” yet apply costs differently (for example, subtracting a fee upfront versus embedding it into the rate). Your worked example must match the provider’s stated calculation method.
-
Rounding differences If a converter rounds intermediate steps (for example, rounding the converted amount before applying a fee), you can see small discrepancies compared with calculations that keep full precision until the end.
-
Jurisdiction and product-specific rules Conversion can be subject to local rules, payment rails, or platform-specific settings that change the effective costs or how rates are quoted. A worked example should clearly avoid implying these details.