When Skrooge is not working, the cause is usually a file problem, not a software one: an import that reads dates the wrong way round, a damaged data file, or an install that lost its settings. Before changing anything, copy your data file somewhere safe, then test the fix on the copy. we are not describing Skrooge's menus, so use its own help for the exact clicks; the method below applies to any desktop finance program.
Back up before you touch anything
- Close the program completely.
- Find the file that holds your accounts, using the program's own help or the save dialog.
- Copy it to another folder or drive and add today's date to the copy's name.
- Work only on the original after the backup exists, and keep the copy until everything balances.
Why do my imported dates look wrong?
Bank files carry dates in a day-month-year or month-day-year order, and a program set to the other order will misread them. The tell-tale sign is a date such as 03/04/2025 appearing as 4 March when you spent on 3 April. Any day above 12 gives it away: 25/04/2025 cannot be month 25, so it either fails or is skipped.
Open the file in a spreadsheet first and look at a few rows with a day above 12. If those rows are the ones that fail, the date order setting is the cause.
Which fixes should I try, in order?
| Symptom | Likely cause | Try this |
|---|---|---|
| Import shows zero rows | Wrong file type or delimiter | Re-save the bank file as CSV and retry |
| Amounts are 100 times too big | Decimal point and thousands separator swapped | Check the separator setting for the import |
| Dates shifted or rejected | Day-month order mismatch | Set the date format to match the file |
| Program will not start | Damaged settings or data file | Open the backup copy or reinstall |
| Balances off by a round sum | One transaction missing or doubled | Compare the opening balance and the statement total |
A worked check: does the balance agree?
Say the statement opens at ₹42,500, shows credits of ₹60,000 and debits of ₹38,750, and so should close at 42,500 + 60,000 - 38,750 = ₹63,750. If your program shows ₹64,750, you are ₹1,000 over, so look for a debit of exactly ₹1,000 that failed to import. Differences that match one transaction are easy to find; differences that do not match usually mean two or more problems.
When is it time to try something simpler?
If you spend more time repairing the tool than recording money, it may be the wrong tool for how you work. A plain spreadsheet with one row per transaction is a perfectly good fallback.
An alternative for people who just want statements read into categories is SpendixAI: you pick the account, upload a PDF, CSV or Excel statement, and review the rows before they are saved. It does not connect to your bank, and there is nothing to install and back up beyond signing in with Google.
Should I keep a plain spreadsheet as a second copy?
It is a cheap safety net. Once a month, export or copy your transactions into a sheet with columns for date, description, amount and category, and save it with the month in the file name. If the program breaks, you can re-import from that sheet instead of going back to the bank. Keep the sheet in a different place from the program's own data, such as a cloud folder you already use, so a single failed disk does not take out both.
A short recovery checklist
- Back up the data file first, every time.
- Test imports on a copy, with one month of data.
- Confirm the date and decimal formats before importing the rest.
- Reconcile to the statement's closing balance before you trust the totals.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

