Automation does most of the sorting, but not all. Whatever it is unsure about ends up in the review queue: transactions waiting for a person to confirm a category or fix a detail. It can feel like a to-do list that never ends, so the way you approach it matters as much as the clicks.
What lands in the queue
The queue collects items where the app lacks confidence. A new merchant with no default, an ambiguous description, an unusual amount or a missing category all qualify. Each appears as a card you can act on, usually offering a suggestion you can accept or change.
It is not a list of mistakes. It is a list of questions. Treat it that way and the work becomes less stressful.
Short sessions beat long ones
A review queue allowed to build up for a month becomes a chore that feels like a punishment. Five minutes a few times a week keeps it near empty. Pick a trigger, like finishing your morning tea, and clear whatever is there. Stop when the time is up, even if cards remain.
If you do face a large queue, divide it. Work for ten minutes, take a break, and come back. Fatigue produces careless choices, and careless choices create more work later.
Decide in a sensible order
- **Highest amounts first.** Mistakes on big items distort reports the most.
- **Repeated merchants next.** Resolving one often clears several cards, and teaches the app for the future.
- **One-offs last.** Odd, unrepeated payments matter least and can wait.
This order maximises benefit per minute. Within minutes you have fixed the entries that matter most and shaped the app's learning.
Turn answers into rules
If you find yourself approving the same suggestion repeatedly, that is a signal to write a rule or set a merchant default. The review queue is where patterns show up, and the right response to a pattern is automation. A quick rule can turn twenty future cards into zero.
Accept imperfection
Some items will resist classification. A mystery payment, a shared account entry, a transfer you cannot place. Leave them. A queue with a few honest leftovers is far healthier than one cleared by guessing. Add a note to the transaction if you know something, and move on.
Keep the bigger picture in view
The queue exists to support your reports and budgets. A small error in the category of a minor payment rarely changes any conclusion. Spend your effort where it changes the numbers you rely on. That keeps the work proportionate.
| Queue size | Sensible approach |
|---|---|
| A handful | Clear in one short sitting |
| A dozen or two | Two sessions, biggest items first |
| Dozens or more | Fix top merchants, write rules, then continue |
| Persistently large | Review categorisation setup, not just the cards |
When the queue stays full
If the queue refills as fast as you empty it, the cause lies upstream. Look at how many cards come from the same few merchants, and whether imports arrive in large batches. Spending an hour on merchant defaults and a few rules usually does more than a month of nightly clearing. The aim is for the queue to shrink as the setup improves, not for effort to rise.
A weekly rhythm
On a weekly basis, aim for a queue small enough to clear in about five minutes. Once rules and merchant defaults are well tuned, it often falls to a few cards. At that point, the queue is no longer a burden but a quick weekly check that your records are in good shape.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


