Reviewing imported transactions

A minute of confirm-or-correct that keeps every report downstream trustworthy.

Getting to the queue

Three doors lead to the same place: the Pending Review card on the dashboard (pick an account from its dropdown), the Review button with its red count badge on a connected account's page, and the review opening on its own when a fetch you trigger from an account's page finds something new.

Reading a row

Each imported transaction arrives with suggestions already in place: a category, a payee and a type, drawn from your history and our enrichment. A badge tells you how the row got here:

Pending Review: an ordinary new transaction awaiting your confirmation.
Match: Manual Entry or Match: Scheduled: it lines up with something already in Endute, a manual entry you typed or a scheduled transaction that came due. Confirming links them instead of creating a duplicate.
Potential Duplicate: it looks identical to a transaction the bank feed already delivered. Usually a discard.
Potential Pair: it looks like one leg of a transfer between your own accounts, with the counterpart already found.

Suggestion sparkles carry a colour code: blue marks a suggestion pointing at a payee you already have, green marks a suggested brand-new payee, where the row notes the payee will be created on import. Picking anything else politely dismisses either kind.

Beyond accept and discard

The review row is also where special shapes get set right, without a second visit: mark a row as a transfer and pair it with its counterpart, turn a loan payment into a proper loan repayment with its interest split, link a refund to its original purchase, split one card payment across categories, or spin a recurring bill into a scheduled transaction so future occurrences match themselves.

Submitting in bulk

Most decisions wait for Process Selected, which imports everything you marked in one batch. (A couple of the special shapes act sooner: confirming a split or creating a scheduled transaction from a row takes effect immediately.) After each batch, matching re-runs on the remaining rows, so suggestions late in a big queue are often better than the ones you started with. Work in progress is saved in your browser as you go; leaving the page and coming back restores your selections.

Payee optional, category encouraged

You can process a row without a payee (it files under an auto-created Undefined payee after a quick confirmation), and bank rows without a category will warn you rather than block you. The reports are only as good as what you let through, so the warning deserves more respect than the block would have earned.

What next

If the queue feels like a chore, why we ask you to review explains what each confirmation buys you, and the payees guide shows how predictable payees graduate out of the queue entirely.