If you deleted an expense by mistake, look first for a recycle bin or trash in the app before you re-enter anything by hand. In SpendixAI, deleted transactions go to a recycle bin and stay there for 30 days, so you can restore one within that time. After that window, the entry is gone, which is why a quick check matters.
What to do straight away
- Stop and do not re-add the entry yet, as that could create a duplicate once you restore the original.
- Open the recycle bin and look for the transaction by amount, date or merchant.
- Restore it and check that the amount, date, category, account and any receipt are still attached.
- Look at the totals for the month to confirm they went back to what you expect.
- If you cannot find it, check the statement for the original row.
Why do accidental deletes happen?
Most come from bulk actions. You select ten rows to delete a duplicate import and an eleventh gets ticked too. Another cause is a swipe on a phone screen. A delete that looks fine on a long list can take away a rent entry or a large bill with no warning besides a small message.
A worked example with made-up numbers
Say you clean up a duplicate import and select 12 rows to delete, but one of them is a genuine ₹4,800 electricity bill. Your totals for the month fall by more than they should.
| Step | Rows | Amount in rupees |
|---|---|---|
| Duplicates you meant to delete | 11 | 7,260 |
| Genuine bill deleted by mistake | 1 | 4,800 |
| Total removed from the month | 12 | 12,060 |
| After restoring the bill | 11 | 7,260 |
You notice because the month's total fell by ₹12,060 when you expected ₹7,260. The difference of 12,060 - 7,260 = ₹4,800 points to the bill. That is the sort of arithmetic check worth doing after any bulk delete.
Habits that stop the next slip
- Filter to the exact rows before selecting, so only the intended ones are on screen.
- Read the number of selected rows before confirming.
- Sort by amount after a bulk delete and look at the biggest rows.
- Use the flagged possible duplicates list rather than guessing which rows repeat.
- Keep receipts attached so a restored row is complete.
A backup beyond the bin
The statement itself is your backup. Because SpendixAI imports from statements you upload and keeps import history, you can re-upload a statement to bring a lost row back, then review it before saving and watch for the duplicate warning. Owners can also export their data and choose how long documents are kept, so an occasional CSV download is a sensible second copy.
If it is not in the bin
If you cannot find the entry in the recycle bin, work backwards from the source. For a statement row, re-import the statement and let the duplicate flag tell you which rows already exist. For a cash expense you typed by hand, rebuild it from the receipt or your memory of the day, and add a note so you know it was re-entered. Check the same month for a possible duplicate before you save, so that you do not end up with two copies of the same bill.
What to do after a restore
Open the month's report, check the category totals against your expectation and glance at any budgets that depend on the restored row. If you share the workspace with others, tell them the entry is back so nobody deletes it as a stray.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


