Transaction Review Workflow

Use this workflow for day-to-day or month-end bank and card review. For details about each action, see Transaction Review; this page focuses on sequencing a batch safely.

1. Define the batch

Select the client, open Banking, and choose an account. Set the date range, then review Uncategorized, Posted, and Excluded counts. Confirm the source and date coverage through Statements & API before taking bulk action.

Use filters for amount, action, reconciliation, method, source, recent activity, or human-versus-AI result. Filter with AI can translate a natural-language request into a filter; inspect the resulting rows before acting.

2. Review high-confidence rows

For each transaction, choose the outcome that reflects what already exists in the ledger:

• Post or Quick Post creates a new journal impact.
• Split & Post handles more than one counter-account.
• Match links the row to an existing entry and avoids duplicate posting.
• Transfer handles movement between the client's accounts.
• Exclude keeps a true source exception outside the ledger.

Verify account, payee, tags, method, evidence, date, and amount. Use bulk actions only when the entire selection shares that outcome.

If the account requires additional transaction details, complete them before posting. The Post dialog shows a separate set of inputs for each selected transaction. Use Save details to keep an incomplete draft. For splits, complete the required details on each relevant journal line.

3. Route ambiguity instead of guessing

Use Ask Client for unclear purpose or missing support. A focused question creates a trackable client work item; it does not post the transaction. Link receipts, invoices, statements, or replies so the answer remains with the accounting decision.

Work from Client Work and Shared Files until the row can be resolved.

4. Accelerate repeat work

Open Categorize Faster for an AI-assisted batch and use Guide Wesley for that run's instructions. The client AI Automation setting controls how much work is prepared:

• On categorizes routine repeat transactions and leaves the rest to the team;
• Experimental categorizes routine repeat transactions with early access to Wesley's newest transaction experiments;
• Off provides payee and account suggestions; active rules post matches while the team reviews the rest.

Use Auto-Coding Rules for narrow, deterministic patterns. Preview eligible uncategorized rows and understand that Apply & Activate can post them immediately. See Rules and AI.

5. Quality-check the result

Sample posted transactions by source, reviewer, how they were categorized, unusual amount, and reconciliation status. Look specifically for duplicate postings, transfers coded as expense or income, missing payees/tags, and broad rule matches.

Review Excluded rows before month-end. Exclusion is reversible, but a legitimate transaction left there remains outside the books.

6. Correct and hand off

Unposting removes the associated posting and returns the transaction to Uncategorized. Restoring an excluded transaction returns it to active review. Reconciled transactions and closed-period dates require extra review and may need an authorized reopen.

Hand off with the remaining uncategorized count, unresolved client requests, source gaps, exclusions, rule changes, and any reconciled rows that were corrected. Then continue to Reconciliation.