Every remittance home shows up twice in the records: once leaving the overseas account and once arriving in the Indian account. These are not duplicates, but they will look like them if you import both. To avoid duplicate transactions when importing bank statements, decide which side you will record before you upload either one.
Choose the base currency first
In SpendixAI the base currency has to be chosen before importing, and it cannot be changed once transactions exist. Each expense can carry its own currency, and totals use the rate saved with that transaction. For someone whose life is in INR, such as supporting parents or paying a home loan, INR is the natural base. Decide this first, because switching later is not possible.
One remittance, two statements
Say you send 1,200 units of your local currency and it arrives as ₹1,00,800 at a rate of 84 per unit. That 84 is a hypothetical figure for this example. The overseas statement shows 1,200 leaving. The Indian statement shows ₹1,00,800 arriving. Add them as two rows and your records say you moved a lakh rupees twice.
| Statement | Row | Meaning |
|---|---|---|
| Overseas account | 1,200 debit | Money you sent |
| Indian account | ₹1,00,800 credit | Same money received |
| Indian account | ₹40,000 debit to a parent's account | Real spending in India |
Choose a rule. Either record only the Indian account, where the spending happens, or record the overseas debit as the transfer and treat the Indian credit as its other side. Do not count both as income or both as expense.
How do I avoid overlapping files across two banks?
- Pick a shared date window for both banks, for example 1 April to 31 March if your family thinks in Indian financial years.
- Download one file per account for that window.
- Check the transfer rows on both sides: dates can differ by a day or two across time zones.
- Import the Indian account first, because most of your real spending is there.
- Import the overseas account next and label remittances as transfers.
Statement layouts differ from bank to bank, so look at your own file and make sure the dates, amounts and currency columns are what you expect. Any bank statement in PDF, CSV or Excel can be uploaded, rows are reviewed before saving, and you should not assume every layout parses perfectly.
What the review step catches
Possible duplicate imports are flagged when you review, and the import history shows each upload's status. Remember that a flag compares what is in your records, not the story behind two payments. A same-amount monthly remittance of the same size is a real repeat. Reading the date and narration will settle it.
What about timing differences?
A transfer sent late on a Friday abroad may be credited in India on Monday or Tuesday. In your records the debit and the credit then sit on different dates, sometimes in different months at a month's end. Do not read that as a mismatch or a duplicate. When you reconcile, match by amount and reference, allowing a few days, and keep the month in which each statement actually shows the row. If the statement months straddle a financial year end on 31 March, mark those transfers clearly so your CA can follow the trail without guessing.
- Match by reference, allow a few days.
- Keep each row in the statement's own month.
- Flag transfers near 31 March.
A closing checklist
- Base currency chosen as INR before the first import.
- Each statement imported into its own account.
- Remittances labelled as transfers, with the rate noted.
- No two files covering the same dates for the same account.
- Remember rules about remittances and reporting change, so confirm the current position with your CA.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

