| The converted amount does not update | The source amount, selected pair or rate data may be missing or invalid. | Enter a numeric amount, confirm both currency codes, refresh rate data and check connectivity. |
| The rate differs from my bank | Reference mid-market data and a retail bank quote use different margins or timestamps. | Compare timestamp, provider spread and transfer charges, then use the bank quote for settlement. |
| USD and CAD were confused | Both currencies can show a dollar symbol despite having different codes. | Select USD or CAD explicitly and inspect the currency name before proceeding. |
| Conversion direction appears reversed | The From and To currencies may be swapped. | Confirm base and quote labels and use the swap control if needed. |
| Inverse rate looks slightly inconsistent | The displayed rate and inverse may be rounded independently. | Use more precision where available and distinguish display rounding from market spreads. |
| Exchange-rate chart is blank | Requested pair or period may have no available history. | Try a supported period or currency pair and confirm network access. |
| Historical chart disagrees with official data | Some pairs use modelled histories or different rate fixings. | Verify the chart data type and use an official archive for regulatory or audit purposes. |
| A weekend rate seems stale | Institutional fiat market references may not update during market closure. | Check the timestamp and verify a fresh provider quote when markets reopen. |
| Crypto estimate changes rapidly | Digital asset prices can fluctuate 24/7 and venues use different liquidity. | Refresh close to the action and compare executable exchange order books. |
| The bank recipient amount is lower | Retail spreads, payment fees or intermediary deductions apply. | Model all known fees and confirm the amount receivable directly with the provider. |
| A provider marked zero fee costs more | The provider may embed compensation in the offered conversion rate. | Compare net payout under identical transaction assumptions. |
| CSV upload is rejected | Headers, delimiter, codes or amount format may not match expected input. | Review a small sample, use supported codes, remove unexpected symbols and retry. |
| Bulk result uses a wrong currency | A row may contain an invalid or incorrectly mapped source/target code. | Inspect the CSV column mapping and spot-check affected rows. |
| Comma decimals are misread | Spreadsheet locale formatting can make decimal and thousands separators ambiguous. | Normalize numbers according to the tool input requirements before importing. |
| Transfer comparison looks unrealistic | Fee or spread assumptions may not reflect the selected provider and corridor. | Replace estimates with the current provider quote and rerun calculations. |
| Card cost estimate differs from statement | Issuer, network and dynamic-conversion charges can be different from chosen markup. | Read actual card terms and compare charged currency and transaction date. |
| Travel daily budget seems too high | The trip length or home versus destination currency may be incorrect. | Confirm dates, number of days, budget units and currency direction. |
| Forex pip profit appears wrong | Position size, pip convention or quote currency may be misinterpreted. | Verify pair-specific pip size, lot units, trade direction and account denomination. |
| Forex trade profit ignores costs | Financing, spread, commission or slippage may be excluded from inputs. | Add known execution charges and account for unmodelled live market risks. |
| Rate alert does not appear on another device | Alerts and watchlists are kept locally in each browser profile. | Recreate the target on the other device and do not expect cloud sync. |
| No alert arrived when the browser was closed | Local tool alerts are not necessarily server-backed push notifications. | Open the tool to check conditions or use a verified notification service. |
| Saved favorites disappeared | Browser storage may have been cleared or a private session was used. | Rebuild favorites and preserve critical pairs externally. |
| Currency comparison values have different dates | The source rate snapshots might have updated at different times. | Refresh relevant pairs and record time/source for a consistent comparison. |
| A currency is not in the list | The tool covers many but not every world currency or token. | Check supported code options and use a suitable authoritative data source for unsupported pairs. |
| Crypto currency pair cannot load | A market data source might not support the pair or is temporarily unavailable. | Try a supported base pair and verify the quote externally. |
| Conversion total differs by a few cents | Displayed precision, intermediate rounding or provider rules differ. | Retain adequate precision until final rounding and follow settlement rules. |
| Rate alert threshold is set incorrectly | Pair direction or greater-than/less-than condition can be reversed. | Recheck the currency pair and threshold direction in the alert setup. |
| PDF or spreadsheet report has wrong dates | Saved calculation assumptions may predate the current rates. | Refresh data and inspect pair, time, units and amount before sharing. |
| Rate refresh fails on slow internet | The external rate provider cannot be reached in time. | Check network access and retry; do not treat an old cached value as live. |
| Automated insight sounds like a prediction | Generated narrative may describe patterns too confidently. | Use it as descriptive context only and confirm claims against source data. |