Reviewing imported transactions

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. A bank row only links to something that moves money the same way, in or out.
• 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. Endute only proposes a pair when it is clear which two accounts the money moved between and the dates are close: the same day or the next, two days apart when one side looks like a transfer, up to four days when both do. Otherwise, for example when the same amount could belong to more than one account, the rows stay as ordinary transactions for you to pair.

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.

The description can be changed on the row too. A pencil next to the bank's wording opens a single-line field; Enter or clicking away keeps the new text, Escape puts the old one back, and once the two differ a small undo restores the bank's wording. Whatever the row says when you process it is what the transaction is called. The bank's original text is not lost: the edit screen of any bank-imported transaction shows it as From your bank whenever the description has been changed, with a button to restore it.

On the web, a row one of your rules filled in carries a badge, Rule: <name> (or N rules when several matched). Its description and tags come from the rule, and you can change them before you process it. The wand button, Make a rule, on any row starts a new rule from that transaction.

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.

What next

If the queue feels like a chore, why we ask you to review explains what each confirmation buys you, the payees guide covers default categories and matching texts, and rules let you decide how any kind of transaction is filled in or imported.