A foreign-currency purchase often shows a slightly different rupee amount in your tracker than on your card bill because the two use different exchange rates, may be converted on different days, and are rounded separately. The card statement is the amount you actually owe and paid, so treat it as the truth and treat the tracker figure as a close estimate. A gap of a few rupees on a small charge is normal and not a sign that something broke.
What are the usual reasons for the gap?
- Markup or conversion charge. Card issuers and payment networks convert at their own rate and may add a charge on top. Your tracker does not know your card's terms.
- Different rate date. The tracker holds the rate saved with the transaction. The bank may convert when the charge settles, which can be a day or more after the purchase.
- Rounding. The foreign amount is converted and rounded to paise by each side separately, and a few lines can drift by a rupee or two.
- Added items. A tip, a hotel hold, a tax line or a currency-choice prompt at the till can change what was actually billed.
- Refunds and reversals. A returned item comes back at a different rate than the original charge, so the pair never nets to exactly zero.
None of these is a fault in your records. Your card's terms and the merchant's setup decide most of it, so check your own statement and card terms for how foreign charges are converted.
Which figure should I trust?
The statement. It is what left your account. In SpendixAI each expense keeps its own currency and its own saved rate, and totals are expressed in your base currency using that rate. That is a good estimate for tracking, but a bank cannot be asked to match an estimate. When you need the exact outflow for a month, read it from the card statement total.
A worked example with invented numbers
Say you made three purchases abroad in a month. All numbers below are made up to show how small gaps add up.
| Purchase | Tracker total | Card bill | Gap |
|---|---|---|---|
| Hotel booking | ₹9,450 | ₹9,612 | ₹162 |
| Museum tickets | ₹1,260 | ₹1,284 | ₹24 |
| Online course | ₹2,100 | ₹2,139 | ₹39 |
| Month total | ₹12,810 | ₹13,035 | ₹225 |
Check the sums: 9,450 + 1,260 + 2,100 = 12,810 and 9,612 + 1,284 + 2,139 = 13,035. The gap is 13,035 minus 12,810, which is ₹225. On ₹12,810 that is about 1.8 per cent. If every line is off by a similar proportion, the cause is a consistent conversion difference, not three separate mistakes. If one line is far out, look at that purchase for a tip, a hold or a typing slip.
How do I line the two up if I want them to match?
- Open the transaction and compare its foreign amount with the foreign amount printed on the statement, if your statement prints one. If those agree, the entry is right.
- If you want the rupee figure to equal the bill, note the difference in the entry's notes instead of forcing the numbers. A note keeps the history honest.
- If you import the card statement, the imported line already carries the bank's rupee amount. Keep that one and remove a duplicate hand entry for the same charge.
- Do not chase rounding of a few rupees line by line. Reconcile at month level against the statement total.
When should I worry?
A difference is worth investigating when it is large compared with the purchase, when the foreign amount differs rather than just the rupee amount, or when a charge appears twice. SpendixAI has a Possible duplicate charges report that lists the same amount to the same merchant within two days, and a Foreign-currency spend report that shows all your foreign purchases together, which makes a stray line easier to spot.
A short habit to keep it calm
- Enter or import foreign purchases as soon as you can, while you remember the context.
- Once the card statement arrives, compare month totals, not single lines.
- Accept a small, consistent percentage gap as the cost of converting.
- Ask your card issuer, not the tracker, if a particular charge looks wrong.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

