Product guides

Re-running a rule over old transactions safely

Applying a rule to existing transactions can tidy years of data or create a mess. Preview, limit and verify before you let a rule rewrite history.

Editorial illustration for Re-running a rule over old transactions safely

New rules start with a tempting offer: also apply to transactions you already have. Accepting it can clean up months of data in seconds. It can also change hundreds of entries in ways you did not intend. A careful routine makes the first outcome far more likely than the second.

What gets changed

The rule editor is specific about what a re-run touches. Category, business or personal status, tags and the reports flag are applied when rules are re-run. Renaming and the reimbursable flag are applied as new transactions arrive. So a re-run tidies classification, but does not rewrite names on old entries. Knowing this prevents disappointment when names stay messy after a re-run.

Manual choices are also relevant. Unless the rule is set to override, transactions you categorised by hand are not touched.

Step one: preview

Before saving, read the preview of what the rule would match. If the number is far larger than you expected, stop. Look at the first handful and the last handful of matches. Edges often reveal mistakes, such as a keyword that also appears in unrelated payees.

Step two: start narrow

For the first run, narrow the rule so that it covers only a small slice, perhaps a single merchant or a recent date range. Check the outcome. If it is right, widen it in the next run. Starting small makes mistakes small.

Step three: verify

After a re-run, open a few transactions that changed and a few that should have but did not. Check the category and any other fields the rule sets. A rule that finishes with a message that nothing needed changing is also useful information: it means the history was already consistent.

CheckWhy it matters
Count of matches vs expectationCatches overly loose conditions
Sample of changed rowsConfirms the category is right
Sample of unchanged rowsReveals manual protection or missed variants
Reports before and afterShows the real-world effect

If something goes wrong

Mistakes do happen. If a re-run misfiled a batch, the quickest repair is a second, corrective rule or a bulk edit on the affected rows. Selecting many transactions together and recategorising them is faster than undoing them one at a time. Keep in mind the recycle bin is for deleted transactions, not for undoing category changes, so careful previewing is the real safeguard.

Notes help too. Before a big re-run, write down the date and what you changed. If a past report later looks different, you will know why.

When not to re-run

  • When the rule's condition is still vague.
  • When you have not checked how manual choices will be treated.
  • When a report deadline is near and the numbers must not shift.
  • When the history includes periods you have already reported or filed.

The last point is easy to forget. If a month has been closed, shared or used for an official purpose, changing its categories alters figures people may already have seen. Apply new rules only going forward in those cases.

Keeping a trail

Large re-runs are easier to live with when there is a trail. Before running one, note which rule, which period and roughly how many transactions you expect to change. Afterwards, add the actual number. If a later report looks odd, that short record tells you where to look first, and it helps anyone else who shares the workspace understand what changed and why.

A sensible cadence

For most people, one tidy-up after writing a new rule is enough. Afterwards, let new transactions flow through the rule on arrival. Saving the occasional full re-run for a planned clean-up keeps the data stable and the reports comparable month to month.

SPENDIXAI JOURNAL

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

Explore your reports