Foreign currency lines on a statement usually show the rupee amount that actually hit your account, plus a note of the original amount in the narration. Record both: the original currency amount for your own reference and the rupee amount for your totals. Never convert a rupee figure back through a rate you guess; use the one the bank applied.
Who runs into this, and when?
Gig workers and freelancers who are paid by clients or platforms abroad see it first: a design job paid in one currency, a stock-photo royalty paid in another, an ad network paying out once a month. It also affects anyone who pays for tools such as design software or a cloud server on a card and sees a rupee debit with a foreign amount tucked into the description.
The statement itself is in rupees. The confusing part is that the narration may carry a currency code and an original amount, and a simple importer might read that number as the transaction value.
What should each row carry?
| Field | Example | Why it matters |
|---|---|---|
| Date | the day it hit your account | not the invoice date |
| Original amount | a figure in the client's currency | matches your invoice |
| Original currency | a three-letter code | tells you what you were paid in |
| Rupee amount | what the bank credited or debited | drives your totals |
| Rate applied | rupee amount divided by original | a sanity check |
The rate applied is worth calculating once per row. If an invoice was for 250 units of foreign currency and the bank credited ₹19,750, the rate is 19,750 divided by 250, which is ₹79 a unit. If a bank charge of ₹300 was taken out of the same remittance, the net credit may be lower, and that charge belongs on its own row.
How do you import it step by step?
- Open the statement and find the foreign rows by searching the narration for the currency code or for the word remittance.
- Check whether the amount column is rupees. For a bank statement it nearly always is.
- Copy the original foreign amount and code from the narration into their own columns, and keep the rupee column as your total.
- Put any bank or conversion fee on a separate row so your net income is correct.
- Compare the sum of the rupee column against the bank's credited total for the month.
Does the rate on the day matter?
Yes, because the rupee value of the same invoice changes with the day it is converted. Two invoices of 250 units each, one converted at ₹79 and one at ₹81, bring in ₹19,750 and ₹20,250, a difference of ₹500. Recording the bank's rupee figure keeps your income honest; recalculating later at a different rate does not.
How does SpendixAI handle another currency?
In SpendixAI each expense can carry its own currency, while totals are shown in a base currency using the rate saved with each transaction. Pick the base currency, which for most readers will be the rupee, before importing, because it cannot be changed once transactions exist. A Foreign-currency spend report pulls those rows together. Uploads are reviewed before saving, so check the currency and amount shown on each foreign row at that stage. Do not assume every statement layout will parse perfectly.
Before you file the month away
- Every foreign credit has a matching invoice number in the description or a note.
- Bank and conversion charges sit on their own rows.
- The rupee total of foreign credits matches the bank's summary.
- If your client or a platform needs a receipt of payment, you know which statement row proves it.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


