If KMyMoney is not working, copy your data file to a safe place before doing anything else. Then check whether the program itself starts, whether the file opens, and, if the trouble is an import, whether dates, decimals and columns were read the way you intended. we cannot describe every version of the software, so confirm formats and menus in its own documentation.
Step one: copy the file
Desktop finance software keeps everything in one data file. If that file is damaged or overwritten, years of records go with it. Find where yours is saved, copy it to another folder with today's date in the name, and keep a second copy on a pen drive or cloud drive. Work on the copy while you troubleshoot.
Does the program start, and does the file open?
- Program will not start: reinstall the same version after copying your file, or try the latest version from the official project page.
- Program starts but the file will not open: try the backup copy, and note any error text.
- File opens but is empty: look in the backup folders before assuming it is lost.
- Program runs slowly: a very large file or low memory can be the cause.
Search for the exact error text along with your operating system. Prefer the project's own forum or documentation over random video tutorials.
Why do imported dates go wrong?
Most import trouble is not the software at all. Indian bank files use day, month, year. Many programs default to month, day, year. A line dated 04/05/2026 is 4 May in India, but a program expecting month first reads it as 5 April. A date like 25/05/2026 cannot be month first, so it may be skipped or marked invalid, which is your clue.
| File says | Read as day-first | Read as month-first |
|---|---|---|
| 04/05/2026 | 4 May 2026 | 5 April 2026 |
| 12/06/2026 | 12 June 2026 | 6 December 2026 |
| 25/05/2026 | 25 May 2026 | Invalid, month 25 does not exist |
Check the date format option in the import screen, and test with three rows before bringing in a year of data.
Other import checks
- Open the CSV in a plain editor and look at the first five lines.
- Check whether amounts use a comma or a full stop for decimals, and whether thousands are separated.
- Check that debit and credit are separate columns or one signed column.
- Confirm the account you are importing into is the right one.
- Import a small slice first and compare the balance.
Should you update the program?
Updating can fix bugs, but it can also change how files are read. That is exactly why the backup copy comes first. After an update, open the copy, check the latest balances against your bank, and only then carry on with your real file. If a new version breaks something that worked before, note the version numbers and ask on the project's own forum, where other users may have met the same problem.
When a desktop program stops being the right tool
Not everyone wants to maintain files and imports. SpendixAI is a different approach: you upload a bank or card statement as PDF, CSV or Excel, pick the account, review rows before saving, and use it on any device. It does not sync with banks, so you would still bring statements in yourself. Move only when you are sure the old records are safely exported or backed up.
Checklist before you give up
- Data file copied with a date.
- Program version noted.
- Error text saved.
- Date and decimal settings checked on a three-row test.
- Ending balance compared with the statement.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

