Clean-ups involve deleting things: duplicates, test entries, rows from a bad import. The fear of deleting the wrong item makes many people put off cleaning altogether. The recycle bin removes much of that fear. Deleted transactions go there first, and they can be restored within a limited time.
How the bin works
The recently deleted screen lists transactions that have been removed. If there are none, it says nothing has been deleted. The duplicates screen mentions that deleted copies stay in the recycle bin for 30 days, which gives the working window: if you realise a mistake within that time, the transaction can come back.
Restoring is limited by role. The screen notes that only owners and admins can restore deleted transactions, so in a shared workspace the person who deleted something may need to ask an administrator to restore it.
Cleaning with confidence
Knowing the safety net exists changes how you work. You can delete duplicates decisively, rather than leaving them in place from caution. Still, a few habits make the net more reliable.
- Delete in small batches, so a mistake affects few rows.
- Check the recycle bin right after a big delete, to confirm the rows are there.
- Note the date of a major clean-up, so you know when the 30 days end.
- Avoid deleting items you are unsure about; mark them or add a note instead.
What deleting changes
Deleting a transaction changes balances and totals immediately. An account balance will move, budgets will recalculate, and reports will shift. Restoring reverses this. If the numbers look different after a clean-up, that is expected, but it also means a mistaken delete is visible in the figures.
Delete, exclude or edit?
Deleting is not always the best tool. Consider the alternatives before removing something.
| Goal | Better tool |
|---|---|
| Hide a transfer from reports | Exclude from reports via a rule |
| Fix a wrong amount | Edit the transaction |
| Remove a true duplicate | Merge or delete newer |
| Undo a whole bad import | Discard the batch |
| Remove a test entry | Delete |
Choosing the right tool means fewer deletions and less to restore.
After the window
After 30 days, a deleted transaction can no longer be assumed recoverable. If a clean-up covers anything you might need later, consider exporting the relevant data first. An export taken before a major clean-up is a cheap and reliable backup.
Role limits in shared workspaces
In a workspace with several members, not everyone can restore deleted items. If you delete something and later need it back, you may have to ask an owner or admin. Telling them promptly matters, since the window is limited. For teams, agreeing who cleans up and who restores avoids confusion and accidental permanent loss.
Export before big changes
Before a major clean-up, export the affected period. The export is a snapshot you control, independent of any retention window. If something goes wrong after the bin has emptied, the snapshot still exists, which makes bold clean-ups much less risky.
A quick restore drill
Try restoring one harmless item once, so the process is familiar before you need it under pressure. Delete a test entry, find it in the recently deleted list, bring it back and check that balances return to normal. Knowing the route in advance turns a future accident into a thirty-second fix.
A tidy mindset
A clean set of records is easier to trust. With the recycle bin as backup, regular small clean-ups are low-risk and worth the few minutes they take.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


