Getting started

How long deleted transactions stay recoverable, and what next

A deleted transaction stays in the recycle bin for 30 days. How to restore one in time, why edits are different from deletions, and a monthly habit for the bin.

Editorial illustration for How long deleted transactions stay recoverable, and what next

In SpendixAI, a deleted transaction goes to a recycle bin and stays recoverable for 30 days. If you restore it within that window it returns; after the 30 days it is gone for good. Deleting by mistake is therefore fixable if you notice quickly, and it is worth a short monthly check so a slip does not outlive the window.

What exactly happens when I delete a transaction?

It does not vanish at once. It moves to the recycle bin, which holds it for 30 days, and it no longer counts in your totals while it sits there. That matters: a deleted row changes your reports immediately even though it can still be recovered.

How do I get one back?

  1. Open the recycle bin in the app.
  2. Find the transaction by date, amount or merchant.
  3. Restore it.
  4. Check that it has returned to the right account and category, and that your totals look right again.

If you are not sure where the recycle bin is in your version of the app, look in the transactions area, or ask through the help pages. The exact menu may change as the app changes.

What happens on day 31?

After 30 days a deleted transaction is not recoverable from the bin, and nothing in the app can bring it back. If you need the row back, you have two routes: import the original statement again, or add the expense by hand. Re-importing may bring back rows you already have, so look carefully at the import history and any possible duplicates before saving.

Is editing the same as deleting?

No. Deleting sends the whole row to the recycle bin. Editing changes a field, such as the amount or the category, in place. The recycle bin is described as a place for deleted transactions, so do not assume it keeps the earlier version of an edit. Before a big clean-up, such as recategorising dozens of rows or changing amounts, note down what you are about to change, or download a CSV first as a snapshot.

A monthly habit for the bin

  • Pick a fixed day each month, the same day you import the statement.
  • Open the recycle bin and scan it.
  • Restore anything you deleted by mistake.
  • Leave genuine duplicates and test rows in the bin; they will expire in time.
  • If you deleted several rows on purpose, glance at your totals once to confirm they match the statement.

A worked example of the timeline

Say you delete a ₹2,400 transaction by mistake on the 5th of a month. If you open the bin on day 20 after deleting, it is still there. If you wait until day 35, it is gone. Because a monthly check can land anywhere in that cycle, a quick glance at the bin right after any big clean-up is safer than waiting for the routine day. The dates are invented.

Day after deletingWhat you can do
Day 0 to day 30Restore from the recycle bin
Day 31 onwardsRe-import the statement or add the row by hand

What should I do straight after a mistaken delete?

  • Open the bin at once and restore the row, rather than meaning to do it later.
  • Check the month's totals against your statement to confirm the number is back to normal.
  • If you deleted several rows together, restore them one by one and tick them off against a list.
  • If you are unsure which rows you removed, compare the import history with your statement to see what is missing.

Who can delete, and what about the whole workspace?

Owners can delete transactions and can also schedule deletion of the whole workspace, with a 7-day window to change their mind. That is a separate, larger action from deleting a single row. Treat the two differently: a single row has a 30-day safety net, and a workspace has a 7-day one.

SPENDIXAI JOURNAL

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

Explore your reports