Typing an exchange rate by hand goes wrong in three ways: you flip the rate so it is rupees per unit instead of units per rupee, you slip a digit, or you reuse an old rate for a new date. Catch all three by dividing the rupee debit on your statement by the foreign amount and comparing it with what you typed.
What mistakes do people actually make?
- Inverting the rate: typing 0.0108 when the sheet expects 92.5, or the reverse
- Transposed digits: 92.5 becomes 95.2
- Misplaced decimal: 9.25 or 925
- Using the day's rate for a charge that posted days later
- Rounding the rate to a whole number on a big purchase
The last one is quieter than it looks. On a 2,000 euro hotel bill, rounding a rate of 92.6 to 93 adds 0.4 times 2,000, which is ₹800.
How do you check a typed rate against the statement?
The statement's rupee debit is the rate you really paid. Say the foreign amount is in column C, the rate you typed in D and the rupee debit from the statement in E. In Excel or Google Sheets:
- Rate actually paid: =E2/C2
- Difference from the typed rate: =D2-E2/C2
- Flag a row that is off by more than a rupee: =IF(ABS(D2-E2/C2)>1, "Check", "OK")
Fill these down the column, and the Check rows are the ones to look at.
A worked example with made-up numbers
| Purchase | Foreign amount | Rate typed | Rupee debit | Rate paid | Verdict |
|---|---|---|---|---|---|
| Flight booking | 300 | 92.5 | ₹27,750 | 92.50 | OK |
| Hotel | 2,000 | 95.2 | ₹1,85,200 | 92.60 | Check |
| Dinner | 60 | 0.0108 | ₹5,556 | 92.60 | Check |
The hotel rate was typed as 95.2 when the digits should have read 92.6, a transposition worth 2.6 times 2,000, or ₹5,200 in the totals. The dinner rate was inverted. Both come out of one formula column.
Which rate should you type in the first place?
- For card payments, the rate implied by your own rupee debit. That is the money you paid.
- For forex card loads, the rate your card statement shows.
- For cash bought at an exchange counter, the receipt rate.
- When you do not have a statement yet, use an estimate, mark the row as estimated and fix it when the statement arrives.
Google Sheets has a function, GOOGLEFINANCE("CURRENCY:EURINR"), that pulls a market rate, and it may be delayed. Use it as a sanity check only, since the rate you paid is almost never the market rate.
How should an expense tracker handle this?
In SpendixAI, each foreign expense is stored in its own currency, and the base-currency total uses the rate saved with that transaction. So the rate you enter, or the one saved with it, feeds your totals and reports directly. After adding foreign expenses, compare a few against your statement using the rate paid check above, and correct any that are off. Pick your base currency before importing, because it cannot be changed after transactions exist.
What if the statement is not available yet?
Mark the row as estimated and type a rate with one decimal place from a source you trust at the time. Keep a separate column for Confirmed, and tick it only when the statement line has been matched. When the statement arrives, overwrite the rate with the rate paid, and note the old figure in a comment, so the correction can be traced. Do the same for refunds, which often come back at a different rate from the original charge.
A short monthly routine
- When the card statement arrives, list its foreign charges.
- Compute rate paid for each.
- Correct typed rates that differ by more than a rupee.
- Save the corrected sheet under a new month name, rather than overwrite it.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


