foreign currency expense converted at wrong rate error
Fixes foreign-currency conversion errors by verifying the rate source and date, then correcting the converted total. Use when an expense in another currency converts at an unexpected rate. Not for multi-currency review rejections needing documentation.
TL;DR
The expense converted with the wrong rate source or the wrong date's rate. Check which rate and date the tool used, switch to the correct rate (card posting date rate or the documented actual rate), and correct the home-currency total.
Error
foreign currency expense converted at wrong rateSteps
- Open the expense and find the foreign amount, the converted amount, and the rate and rate date the tool used. Expected: all four values are visible.
- Determine the correct rate: for card charges use the card network's posting-date rate; for cash use the documented exchange rate for the transaction date. Expected: you know which rate should apply.
- Compute the expected home-currency total yourself (foreign amount times the correct rate). Expected: a number to compare against.
- Override the converted total with the correct figure and attach rate evidence (card statement, exchange receipt). Expected: the expense shows the corrected total with documentation.
- If the tool's rate feed is systematically off, report it to your admin. Expected: the feed gets corrected for everyone.
When to use
- A foreign-currency expense shows a converted total that does not match the card statement.
- The rate date differs from the transaction date.
When not to use
- Finance rejected the expense pending rate documentation (attach the evidence).
- The currency itself is wrong (fix the currency, not the rate).
Tool compatibility
- Expensify, Concur, Ramp multi-currency expenses; card-network rates.
Variant phrasings
Incorrect FX rate on expense
Same problem, shorter wording.
Currency conversion looks wrong
The reviewer-flag phrasing of the same issue.
Why it happens
Tools pick a rate source and date automatically (often the expense creation date, not the transaction date), and card networks settle at their own rates. Any mismatch between the tool's choice and reality shows up as a wrong total.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst60ooproFJNBnNhAbHmwHQ