Why Endute asks you to review transactions
A design choice, not a limitation. The short version: numbers you have seen are numbers you can trust.
The choice we made
Every finance app faces the same fork. Import silently, and the app feels effortless until the day a mis-categorised salary has been quietly wrecking three months of reports. Or ask the user to look, and risk feeling like homework. We chose the second path, deliberately, and then spent our effort making the looking fast rather than making it optional.
The reasoning is about trust compounding. A budget is only as trustworthy as its categories; a net worth trend is only as real as the transactions beneath it. When every imported row has passed through your hands, even at a glance, the reports stop being the app's opinion and become your record. That difference is hard to see in week one and impossible to miss in month six.
What each review actually does
Reviewing is not just quality control; it is teaching. Confirm a suggestion and Endute strengthens the match that produced it, so the same bank text resolves faster next time. Correct one and the correction is what gets remembered, including the negative: a suggestion you rejected is recorded so it stops being offered. Accept a community suggestion and your confirmation, stripped to an anonymous fingerprint of the bank text, makes the same suggestion better for every user who encounters that merchant after you. The queue gets easier precisely because you have been working it.
The behavioural half
There is a second reason, and it has nothing to do with data quality. Budgeting, at its core, is not about restriction; it is about comfort, the settled feeling that the things you are spending on are the right things. That feeling cannot be computed for you. It forms one way only: by consciously seeing your transactions, one at a time, at review. A charge glanced at today plants a small awareness; months of those glances and you know your own spending the way you know your own street. Apps that import silently keep the numbers and skip the knowing, which is why their users can have perfect reports and still feel out of control.
The review queue is where that awareness builds, a few seconds at a time. It is the difference between being told where your money went and having watched it go.
The full map of when we don't ask
Review by default does not mean review always. There are exactly two paths into your ledger that skip the queue, and both exist because a different safety net fits them better:
Auto-import rules you create. When a payee is so predictable that reviewing it teaches nothing, you promote it: the rule needs a default category, applies to that payee alone, and every transaction it imports is marked as auto-imported so you can always see what came in that way. This is review graduating, not review skipped; the payees guide covers it.
The connection-time history import. When you first connect a bank, months of history arrive at once, and reviewing a thousand rows one by one would be cruelty dressed as diligence. So that one import shows you a preview, goes in as a batch, and carries a one-tap undo instead. Your ongoing transactions still arrive in review as usual.
Everything else waits for you. Even a bank row that matches a scheduled bill you predicted is surfaced as a match for one-click confirmation rather than consumed silently. One quiet convenience rounds the picture out: when the second leg of a transfer you already confirmed arrives from the other bank, it attaches itself to the existing transfer instead of asking you twice. Nothing new enters your ledger there, so there is nothing new to review.
If the queue still feels heavy
Process Selected rather than daily. The design goal was never that you review a lot. It is that nothing reaches your reports without the option of your eyes on it.What next
The review guide covers the mechanics end to end.