Getting started

iCompta not working: protect your data first, then troubleshoot

If your finance app such as iCompta stops working, back up the data file first, then test with a copy, record the error and contact the vendor with details.

Editorial illustration for iCompta not working: protect your data first, then troubleshoot

When a desktop or phone finance app stops working, protect your data before you try fixes. Make a copy of the data file or export everything, note the app and system versions and the exact error, then try the simple fixes in a sensible order. This applies to iCompta and to any similar personal finance software.

Why back up before fixing?

Most fixes are harmless, but a few, such as reinstalling or restoring, can overwrite a file you have not saved. A copy costs you two minutes and removes the worst outcome. Save it somewhere separate from the app, for example a different folder or an external drive.

What do I check first?

  1. Note the exact wording of any error and what you were doing when it appeared.
  2. Write down the app version and your device's system version.
  3. Quit the app fully and open it again.
  4. Restart the device.
  5. Check for an update from the place you installed it, and read the update notes.
  6. Try the app with a different, empty data file; if that works, your original file is the suspect.

How do I tell whether the data file or the app is broken?

TestIf it worksIf it fails
Open a new empty fileApp is fine; check the old fileApp or system issue
Open the backup copyOriginal file may be damagedProblem is not that file
Open on another deviceProblem is local to the first deviceProblem may be the file itself

A worked example of checking after a repair

Say your app holds 2,400 transactions with a net total you noted before the problem, ₹1,86,500. After any repair or restore, check the row count and the total again. If you now see 2,386 rows, 14 are missing; if the total differs by ₹3,200, one or more rows changed. Compare against your backup before you carry on entering data.

When should I ask the vendor?

  • Write to the vendor with your app and system versions
  • Quote the error text exactly
  • Say what you already tried
  • Attach a screenshot, but not any file containing real account numbers unless the vendor's official process asks for it

What if I want to move on?

Before leaving any app, export your history in the most open format it offers, such as CSV, and check that the dates and amounts survived. Keep that file as your permanent copy whichever tool you choose next.

If you are rebuilding from bank statements, SpendixAI takes PDF, CSV or Excel uploads, lets you review rows before saving, and gives you the same workspace on web and mobile.

How often should I back up a finance file?

Backing up once a week is a reasonable habit for a file you update daily, and once after any large import. Keep the last four copies, named by date, rather than overwriting one. If something goes wrong on a Tuesday, the Sunday copy loses only two days of entries, and you can re-enter those from your statement. Store one copy off the device, because a lost laptop takes both the file and an on-device backup with it.

Should I move to a different tool?

Only after the problem is understood. If a fresh file works and your old file does not, the app is fine and the file needs attention. If the app fails on every file and the vendor is slow to answer, then start exporting. Moving in a panic is how people lose categories and notes that took years to build.

Recovery checklist

  • Backup copy made
  • Versions and error noted
  • Spare file tested
  • Row count and total compared
  • Vendor contacted with evidence
SPENDIXAI JOURNAL

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

Explore your reports