Transaction Review

Start From The Feed

Open Bank Transactions from the client book. Use the pending table to review bank and card activity from connected feeds, uploaded statements, imports, or integrations.

Adjust The View

Use filters and columns to expose the evidence needed for review. Narrow by account, date range, source group, status, vendor, amount, or pending type before taking bulk action.

Use AI Suggestions

Wesley can suggest accounts, vendors, customers, classes, locations, and posting actions. Review the transaction group, explanation, source evidence, and unusual amount markers before accepting a suggestion.

Choose The Right Action

• Quick Post when the suggested coding is clear.
• Ask client when transaction purpose or support is missing.
• Match when a bank row corresponds to an existing record.
• Transfer when the row represents movement between accounts.
• Exclude when the item should not affect the books.
• Create a rule when a narrow, reliable pattern should code the same way next time.

Use Bulk Actions Carefully

Select one or more rows only when they share the same accounting outcome. Confirm that the selected transactions belong together before asking the client, matching, transferring, excluding, or posting.

Automate Repeat Coding

Use Rules for repeat vendor, memo, amount, account, class, or location patterns. Use Autopilot only when the automation scope is explainable, reviewable, and easy to disable if it catches the wrong activity.

Check Before You Leave

The feed should be smaller and clearer. Posted rows should have consistent evidence and coding. Rows that still need context should be assigned to a client request, document request, match, transfer review, or rule decision.