Imported amounts go wrong in three recognisable ways: Indian digit grouping such as 1,00,000.00 being read as a different number, a Dr or Cr suffix being ignored so credits look like spending, and amounts that appear a hundred times too big or small because the decimal point has moved. All three show up in the review step, where you can compare each row with your printed statement before saving.
What is wrong with 1,00,000.00?
Indian grouping puts the first comma after three digits and then one after every two, so one lakh is 1,00,000 and ten lakh is 10,00,000. Western grouping puts a comma after every three digits, so a million is 1,000,000. A reader that expects groups of three may be confused by a comma in an unexpected place. The risk is a number that is cut short or read as two values. Look at large amounts first: a rent or salary figure is the quickest way to spot it.
| On the statement | Correct value | A wrong reading to watch for |
|---|---|---|
| 1,00,000.00 | one lakh rupees, ₹100,000 | ₹1.00 or ₹100 |
| 12,34,567.89 | a little over twelve lakh | ₹12.34 or two separate numbers |
| 85,000.00 | ₹85,000 | Correct either way, small numbers are rarely affected |
Why do credits look like spending?
Some statements show a single amount column with a suffix, so an amount can read 4,500.00 Dr or 4,500.00 Cr. Others use separate debit and credit columns, and some show a minus sign. If the suffix is dropped, every row looks like the same kind of entry. The fix is to read the direction column or suffix in your statement and check the sign on a few rows. Take a before-and-after example.
- Statement row: salary of 62,500.00 Cr on 1 October. Wrong review row: 62,500.00 shown as an expense. Right: 62,500.00 recorded as income or a credit.
- Statement row: electricity bill of 1,840.00 Dr. Wrong review row: shown as an incoming amount. Right: 1,840.00 recorded as spending.
- Statement row: refund of 799.00 Cr from a shop. Right: a credit that reduces what you spent there, not a new expense.
Why is an amount a hundred times too large?
A shifted decimal usually means the file stores paise or a different number of decimals than the reader expected. A bill of ₹1,840.00 could appear as ₹184,000 or as ₹18.40. The give-away is that the digits are right but the size is wrong. The rows may still pass a quick glance, so test with the largest and the smallest amounts, because those make the error obvious.
Check the total too. Add up the debits you see on the review screen and compare them with the total debits printed at the bottom of your statement, if there is one. If the sums are far apart, a whole column is probably misread rather than one row.
What should I do when the review step shows a bad amount?
- Do not save the batch. The review step exists so rows can be checked first.
- Pick three rows: the biggest debit, a credit, and a small amount with paise such as 49.50.
- Compare each against the printed or on-screen statement from your bank.
- If a pattern is wrong in all three, download the statement again as CSV or Excel and import that.
- If only one row is wrong, correct it by hand during review.
When should I stop and ask the bank?
If the amounts on the bank's own statement differ from what your banking app shows, that is a question for the bank, not for your tracker. For anything else, the statement is the record of truth and the tracker should match it. SpendixAI does not promise every layout will read perfectly, so a quick comparison on each import is a sensible habit, and a mismatch is a reason to switch format and try again.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

