Bookkeeping

Transaction Review

Give every bank and card row the correct accounting outcome without duplicating the ledger.

Transaction review gives each imported bank or card transaction the correct accounting outcome. A transaction may be posted, matched, recorded as a transfer, sent to the client for context, or excluded from the books.

Open the review feed

Select a client, choose Banking, and open a bank or card account. Work from the Transactions tab. You can also use the Uncategorized shortcut on the Banking overview to open the outstanding queue.

The primary status views are All, Uncategorized, Posted, and Excluded. Use the reconciliation filter to switch among All, Reconciled, and Un-Reconciled rows.

Before you begin

  • You need write access to post, match, transfer, exclude, or edit a transaction. Read access is enough to inspect the feed.
  • Confirm that the source account and date coverage are correct and that the chart of accounts is ready.
  • Keep receipts, invoices, statements, or client answers available for ambiguous activity.
  • Check the period status. Posting, unposting, or changing a journal date inside a closed period is blocked.
  • Be cautious with reconciled rows. A change can make a saved reconciliation disagree with the current ledger.

Narrow the queue

Use date, search, amount, action, reconciliation, type, source, and recent-activity filters to isolate a coherent batch. You can also distinguish human and AI activity or use Filter with AI to describe the rows you need in natural language.

Clear filters before concluding that a transaction is missing. Status and account filters are the most common reason a known row is not visible.

For recommendation-led batch work, select Review Transactions and switch among the Match, Transfer, and Post tabs. Each tab shows up to 50 rows or pairs at a time, and safe recommendations on the current page start selected. Selection does not carry to another page.

  • Match recommends mutually unique, exact remaining-amount entries within each transaction's four-day date window.
  • Transfer recommends mutually unique, opposite-direction exact-amount pairs within three days. A possible ledger match takes priority over a transfer recommendation.
  • Post groups rows by the suggested accounting treatment so you can review consistent recommendations together.

Deselect exceptions, verify the dates, accounts, and amounts, then use the contextual Match, Transfer, or Post action once for the selected page.

Choose the accounting outcome

Post

Use Quick Post or Post when the transaction needs a new ledger entry. Verify the suggested or selected account, payee, tags, type, memo, and date. Posting changes the books and moves the transaction to Posted.

Use Split & Post when one bank row needs multiple debit or credit lines. The journal must remain balanced.

Match

Use Match when the ledger entry already exists, such as a previously entered bill payment or journal. Select the correct entry and review the amount and date. Matching connects the bank transaction to that entry instead of posting it again. Partial matching may be available when the amounts do not correspond one-to-one.

Transfer

Use Transfer when money moved between the client's accounts. Choose the corresponding account or movement and verify that the two sides represent the same transfer. This prevents treating the movement as income or expense.

Ask the client

Use Ask Client when business purpose or evidence is missing. Write a specific question and include the relevant transaction or document context. Wesley creates a client work item and can send the request by email. Track the answer under Client Work before posting.

See Client Work for request and response handling.

Exclude

Use Exclude when an imported transaction should not affect the books—for example, a duplicate or activity outside the intended import range. Exclusion moves it to Excluded without posting it. Exclusion is not a substitute for categorizing a legitimate business transaction.

Add detail or change context

Depending on the row, you can set a transaction type; assign a vendor, customer, class, location, or project; link or upload documents; change the source bank; or open the journal editor.

On an already posted transaction, changing the category updates its accounting classification without changing the cash account. Changing the bank account can affect reconciliation, so verify the new account carefully.

Use bulk actions only when every selected row has the same supported outcome. Review the selection count and filters immediately before confirming.

Result and side effects

  • Post creates ledger activity and changes the row to Posted.
  • Match connects a bank transaction to existing ledger activity and avoids a duplicate entry.
  • Transfer records or links the movement between accounts.
  • Ask Client creates a tracked collaboration item; it does not categorize the transaction.
  • Exclude moves the transaction out of the active queue and leaves it outside the ledger.
  • Payees, tags, documents, and types become part of the transaction's accounting context and can affect search, rules, and reports.

Correct or undo a decision

  • To reverse a normal posting, open the transaction and choose Unpost. Wesley removes the journal entry created by that posting and returns the transaction to Uncategorized for review.
  • To restore an excluded row, open Excluded, select it, and return it to the review queue.
  • To correct coding, edit the posted transaction or unpost and post it again with the right outcome, depending on the available action.
  • To correct a match or transfer, remove or change the relationship before creating a replacement entry.
  • Deleting a journal is permanent. Use the journal editor only when the entry truly should be removed.

Reconciled and closed-period activity may require the reconciliation to be reconsidered or the period to be reopened before correction.

Troubleshooting

Post is unavailable or fails. Check write access, the journal date, and whether the period is closed. Verify that required account mapping is complete.

The row already has a ledger entry. Use Match, not Post, after confirming the existing entry.

A transfer appears as income or expense. Unpost or reclassify it, then use Transfer with the corresponding account movement.

A transaction disappeared. Clear filters and inspect Posted and Excluded. Also confirm that you opened the correct bank account.

A reconciled row needs a change. Open its saved reconciliation first. Record why the change is required, then review the report again after the correction.

For repeat patterns, continue with Rules and AI.