When you pay from abroad for things in India, the bill is in rupees and the matching transaction is in another currency. The standard amount-for-amount match fails every time. To auto-match, convert first, then allow a small tolerance for rounding and for the rate your provider used.
Why the usual rule breaks
A shop bill says ₹23,400. Your transfer record says 280.00 in your home currency. Neither number is the other, so a formula that looks for equal amounts finds nothing. The fix is a helper column that converts each transfer into rupees using the rate on its confirmation, and then matches the converted figure.
Set up the helper columns
- In your transfer list, keep three columns: amount sent, rate shown on the confirmation, and date.
- Add a fourth column with the rupee equivalent: =B2*C2 if the amount is in B and the rate in C.
- Round the result to the nearest rupee with =ROUND(B2*C2, 0) for a cleaner comparison.
- In your bill list, keep date, shop and rupee total.
- Match when the rupee equivalent is within a tolerance of the bill total.
A worked example with invented numbers
Say a bill is ₹23,400 and you sent 280.00 with a confirmed rate of 83.57 rupees per unit. The rupee equivalent is 280.00 multiplied by 83.57, which is 23,399.60, and rounds to ₹23,400. That is an exact match after rounding.
Now suppose there are two other bills that week.
| Bill | Transfer | Rupee equivalent | Result |
|---|---|---|---|
| ₹23,400 | 280.00 at 83.57 | ₹23,400 | Match |
| ₹9,800 | 118.00 at 83.05 | ₹9,800 | Match |
| ₹15,000 | 175.00 at 83.40 | ₹14,595 | Gap of ₹405, review |
The third pair is off by ₹405, much more than rounding. It might be a different bill, a part payment, or a transfer for something else. Do not force it; flag it.
How wide should the tolerance be?
Pick a tolerance that reflects rounding, not mistakes. For small bills, a rupee or two is reasonable. For large ones, a slightly wider band may be needed if your provider's fee is deducted from what arrives. If your provider's fee is separate, the amount received in India is what matters for matching; check your transfer confirmation for the delivered amount rather than assuming one.
- Tolerance too tight: genuine matches show as unmatched and waste your time.
- Tolerance too loose: wrong pairs slip through. Check the date and payer as a second filter.
What about delays and weekends?
Transfers can take a day or two to land, and a bill can be paid on a day when the transfer was already on its way. Allow a window of a few days between bill date and transfer date, and widen it around festivals and bank holidays in India.
Where a tracker helps
SpendixAI lets each expense carry its own currency, with totals in a base currency using the rate saved with each transaction. Choose the base currency before importing, because it cannot be changed once transactions exist. Statements import as PDF, CSV or Excel with rows reviewed before saving, and receipts stay with their transactions. It does not connect to your bank, and the final judgement on a match is yours.
Keeping a paper trail you can read later
Write one line for each pairing in plain words: who paid the shop, which transfer covered it, and the rate used. A year on, you will not remember why 175.00 went out in a particular week, but the line will tell you. If you ever need to explain a transfer to a bank or to your CA, that line is more useful than the numbers alone.
Questions to ask yourself monthly
- Is every rupee bill paired with a transfer, or marked as paid by family in cash?
- Did every transfer keep its confirmation rate?
- Are there transfers with no bill that need a note?
- Does your CA, if you use one, need these figures in a particular currency? Ask them and follow their answer.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


