Money basics

Savings contribution counted twice? How to find and fix double entries

A retried or duplicated savings entry shows twice in your tracker. Learn to spot it, check it against your bank record and stop repeats.

Editorial illustration for Savings contribution counted twice? How to find and fix double entries

If a savings contribution shows up twice, compare your tracker against the bank or UPI record for that date. One debit and two tracker entries means a duplicate. Delete the extra entry, note why, and check how the entry was created, because retries, double taps and re-imported statements are the usual causes.

How does a double count happen?

  • You tapped save twice on a slow connection, and both went through.
  • A payment failed, you retried, and you logged both attempts.
  • A statement was imported twice, or overlapping date ranges were imported.
  • You typed an entry by hand and then imported the statement that contains it.
  • A standing instruction ran, and you also logged a manual top-up for the same month.

How do you confirm it is a duplicate?

  1. Open your bank or UPI history for the date and amount.
  2. Count debits that match: how many times did the money actually leave?
  3. Count tracker entries for the same amount and date.
  4. If the tracker count is higher, the extra ones are duplicates.
  5. If the bank shows two debits, you really paid twice, which is a different problem to take up with the platform or your bank.

A worked example

Say you contribute ₹5,000 towards a goal. The payment page hangs, you tap again, and you log both. Your goal shows ₹10,000 saved, but the bank shows one debit of ₹5,000. After checking, you remove one entry, and the goal drops back to ₹5,000. If you had not checked, the next month's ₹5,000 would have made it look as if you were ₹5,000 ahead of schedule, and you could easily spend what you never saved.

SourceEntries for the 5,000Amount counted (₹)
Bank statement1 debit5,000
Tracker, before fix2 entries10,000
Tracker, after fix1 entry5,000

What does idempotent mean, and why care?

An operation is idempotent when doing it twice has the same effect as doing it once. For a contribution, it means a retry of the same request should not add the money again. Whether a tool you use is built that way is a technical detail you can test: submit once, then retry the same action and see whether the total changes. If it does, treat that tool's totals as needing a check against your bank.

How does importing handle duplicates?

For statement imports, SpendixAI flags possible duplicate imports and has a Possible duplicate charges report that lists the same amount to the same merchant within two days. That covers imported rows and repeated payments. For goal contributions, check the figures against your account, since you can only be sure what the money did by looking at the bank record.

What if the bank itself charged you twice?

Then the problem is outside your tracker. Note both debits with date, time and any reference number, screenshot the confirmation or failure message, and raise it with the app or bank that took the money. Failed or duplicate debits are usually reversed, but how fast depends on the provider, so read their own timeline. Until it is resolved, keep both entries in your tracker with a note, so your records still match the bank.

What rules prevent repeats?

  1. Log a contribution only after the bank confirms it.
  2. Prefer one source of truth: either import the statement or type by hand, not both for the same row.
  3. Use a note with date and amount, such as 5,000 goal 14 Nov.
  4. Check overlapping dates before every import.
SPENDIXAI JOURNAL

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

Explore your reports