A report is only as honest as the transactions behind it. If your totals include money you merely moved from one account to another, or a one-time payment that does not reflect your habits, the picture is skewed. The rule editor has an action for this: exclude from reports. It keeps selected transactions in your records while hiding them from the report figures.
What exclusion does
Excluding a transaction from reports does not delete it. The transaction remains in your list, in your account balance and in search results. It simply does not count in report totals. That makes it the right tool for entries that are real but not meaningful for analysis.
Contrast this with deleting, which removes the record entirely and affects balances. Excluding leaves the books intact and changes only the analysis.
Typical candidates
- **Transfers between your own accounts.** Money moving from savings to current is not income or spending.
- **Credit card bill payments.** The purchases were already counted when they were made; paying the bill would count them twice.
- **Wallet top-ups.** The spending is counted when the wallet is used.
- **One-off settlements.** A large repayment between friends that would swamp a month's chart.
The first three are structural: they come up every month and a rule can handle them for good. The last is a judgement call and may be better done by hand.
Writing the rule
Choose conditions that identify the pattern. For account-to-account transfers, the description often contains a recognisable phrase, or the payee is your own name. For card bill payments, a phrase such as the card name or the word payment may be stable. Use the preview to confirm the rule catches only what you intend.
Because excluding changes your totals, test it carefully. A condition that is too loose could hide real spending, and the report would look better than reality. Check a sample of matched transactions and make sure each is one you truly want excluded.
Reports flag and re-runs
The editor notes that the reports flag is one of the things applied when rules are re-run, so it works on existing transactions as well as new ones. That means a new rule can clean the history. After a re-run, compare a report before and after. The difference should equal the sum of the excluded items, which is a neat sanity check.
What exclusion cannot fix
Exclusion handles reporting, but a proper record of transfers matters for balances. If a transfer is logged on only one side, an account will drift. The aim is to have both sides recorded and both excluded from spending analysis, so balances remain right and reports remain honest.
| Item | Counts in balance | Counts in reports |
|---|---|---|
| Everyday purchase | Yes | Yes |
| Transfer between own accounts | Yes | No, excluded |
| Credit card bill payment | Yes | No, excluded |
| Deleted transaction | No | No |
Reviewing excluded items
Excluded transactions are easy to forget precisely because they vanish from reports. Once a quarter, filter for them and read the list. Make sure each still deserves exclusion, that nothing real has slipped in, and that matching transfer pairs both appear. A quick scan catches stale rules and keeps the habit trustworthy.
A last word
Exclusion is a quiet but important tool. It brings your reports closer to what you actually spend and earn, so conclusions drawn from them are sound.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


