Bank reconciliation exception list
An agent compares bank feed transactions with entries in QuickBooks Online or Xero and lists unmatched, duplicated, or oddly categorized items with a suggested match for the bookkeeper to confirm.
The use case
Bank reconciliation is easy when everything matches and slow when it does not. Small businesses often fall behind because a handful of unmatched deposits, split payments, or duplicate entries take most of the time. The agent reads the bank feed and the ledger for the period, matches transactions on amount, date, and payee, and lists the leftovers: deposits with no invoice, payments with no bill, likely duplicates, and transfers recorded on only one side. For each exception, it suggests the most likely match or explanation and says how confident it is. The bookkeeper reviews each suggestion, makes the actual matches and adjustments in the accounting software, and completes the reconciliation. The agent does not post journal entries, delete transactions, or mark accounts as reconciled.
Example workflow
- At the end of each week or month, the agent pulls bank feed transactions and ledger entries for the period from QuickBooks Online or Xero.
- It matches items by amount, date range, and payee name, allowing for small date differences.
- Unmatched and possibly duplicated items are listed in a Google Sheet with the bank and ledger details side by side.
- For each exception, the agent suggests a likely match or explanation and gives a confidence note.
- The bookkeeper works through the list, makes matches and corrections in the accounting software, and marks each row resolved.
- Rows left unresolved carry forward to the next run so nothing quietly drops off the list.
Tools
- QuickBooks Online
- Xero
- Google Sheets
- Claude
- Zapier or Make
Risks and guardrails
- A suggested match is wrong but looks plausible — guardrail: suggestions include a confidence note, and the bookkeeper confirms every match in the accounting software.
- The agent posts or deletes entries — guardrail: it uses a read-only connection and writes only to the exception sheet.
- Exceptions are cleared in the sheet but not in the books — guardrail: the next run re-checks the ledger and reopens rows that are still unmatched.
- Bank data is exposed through shared sheets — guardrail: the sheet is restricted to finance staff and shows only the fields needed to match.
Related recipe
Receipt Capture and Categorization for Bookkeeper Review: An agent extracts vendor, date, amount, and tax from receipts in email, Drive, or photos, suggests a category from your own chart of accounts, and queues drafts in QuickBooks or Xero for a bookkeeper to approve.
Want it set up for you? Request a quote.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- QuickBooks Online MCP server (official page): github.com/intuit/quickbooks-online-mcp-server (checked 2026-11-09)
- Xero MCP server (official page): github.com/XeroAPI/xero-mcp-server (checked 2026-11-09)
- Claude (official page): claude.ai (checked 2026-11-09)
- Zapier MCP (official page): zapier.com/mcp (checked 2026-11-09)
- Make MCP server (official page): developers.make.com/mcp-server (checked 2026-11-09)