Getting started

Fixing duplicate transactions when you send money home to India

NRIs sending money to India often log a transfer twice, once on each side. Here is how to find and remove those duplicates and keep totals honest.

Editorial illustration for Fixing duplicate transactions when you send money home to India

Regular transfers home can enter the records twice: once as the amount that left the overseas account and once as the rupees that arrived in India. The fix is to decide which side you are tracking, keep one record per transfer, and delete the other.

This differs from a local duplicate because the two rows rarely match. One is in a foreign currency, the other in rupees, with different dates if the transfer took a day or two, so a simple amount sort will not catch them.

Why transfers get recorded twice

  • You log the outgoing transfer by hand when you send it, then upload the Indian account statement where the same money shows as a credit.
  • You track expenses in rupees but also log the foreign-currency leg for your own reference.
  • A parent withdraws the money and you log the withdrawal as a family expense as well, so the same funds are counted as both a transfer and a spend.

A worked example with a conversion in the middle

Say you send 600 units of your local currency and the rate saved with the transaction is ₹84 a unit. That is 600 x 84 = ₹50,400. Your parents' Indian statement shows a credit of ₹50,150, because a small difference was taken in fees along the way. You logged ₹50,400 by hand and then imported the Indian statement.

RowAmountSourceWhat to do
Outgoing transfer, 600 units at ₹84₹50,400typed by youKeep as the single transfer record
Credit in the Indian account₹50,150imported statementDo not count as income in your own book; delete or mark as the receiving side
Difference (50,400 minus 50,150)₹250fees or rate gapRecord as a fee line if you care about it

If you count both, your money sent home looks like ₹1,00,550 for one transfer. The ₹250 gap is a made-up figure; check the real one in your remittance receipt rather than assuming.

How do I decide which side to keep?

Ask what question the book answers. If you want to know what your own life abroad costs, keep the outgoing record and ignore the Indian credit. If you are tracking your parents' household in India, keep the rupee credit as their income and leave the foreign-currency record out of that book.

  1. Choose the book: yours, or the family's in India.
  2. Mark transfers between your own accounts as transfers, not spending.
  3. Search the month for rows of about the same size within three or four days of each other.
  4. Keep one, delete the other, and note the receipt reference on the survivor.

What about the currency settings?

SpendixAI lets each expense carry its own currency and totals everything in a base currency using the rate saved with each transaction. You must choose the base currency before importing, and it cannot be changed once transactions exist, so decide before you load the first statement. There is also a Foreign-currency spend report. Statement imports are reviewed before saving and possible duplicates are flagged, though a foreign-currency row against a rupee row may not look like a duplicate at all, so you still check by eye.

Monthly checklist

  • Match each outgoing transfer to one credit and keep only one.
  • Check the saved rate on every converted row against the receipt.
  • Look for family withdrawals that duplicate a transfer.
  • Work from exported statements; never hand your net-banking login to anyone to fix this.
  • Ask your CA about anything tax-related on remittances; this article covers records only.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports