It's the 6th of the month. A bookkeeper with eighteen monthly clients has roughly two thousand bank and card lines waiting. Most are dull in the best way: the same rent, the same software subscriptions, the same fuel stations as last month.
The trouble hides in the rest: a marketplace order that could be office supplies, inventory or the owner's personal shopping, a $9,850 transfer to an account she's never seen, a vendor refund that someone booked as income last month.
Clicking through the routine lines leaves too little attention for these, and these are the ones that matter.
What a good suggestion looks like
A useful suggestion is more than an account name. It uses this client's chart of accounts, not a generic list.
It says why: the payee, the amount pattern, how the same payee was coded before. And it's honest about doubt, holding a line instead of forcing a guess. Here's how a handful of lines might come through for a hypothetical contractor client:
| Bank line | Suggestion | Reason | Next step |
|---|---|---|---|
| Fuel station, $68.12 | Fuel, vehicles | Same payee coded to fuel every month this year | Batch approve |
| Design software, $59.99 | Software subscriptions | Same amount on the same day each month | Batch approve |
| Card processor deposit, $3,214.55 | Sales clearing | Matches the processor's payout report | Match to the sales report |
| Marketplace order, $412.37 | Hold | Payee coded to three different accounts before | Ask the client |
| Transfer to account ending 4471, $9,850.00 | Hold | Account not in the books; round amount | Bookkeeper reviews |
| Loan payment, $1,420.00 | Hold | Needs the principal and interest split | Use the lender statement |
Flowchart
One bank line through review-first categorization
- StartBank feed brings in a $412.37 marketplace order on the 6th
- StepCompared with the client's chart of accounts and two years of coded history
- DecisionClear pattern, and no hold rule triggered?NoA personHeld: bookkeeper reviews it, or a question goes to the client; answers return to the queueYes
- StepSuggestion queued with its account, reason and confidence
- A personBookkeeper approves the day's routine suggestions as a batch
- StepApproved entries posted to QuickBooks Online or Xero
- DecisionDoes the account reconcile to the bank statement?NoA personBookkeeper finds the difference before anything else movesYes
- DoneReviewer signs off the close; the monthly package goes out
What to hold instead of guess
Holding is where review-first earns its name. Write these rules down per client, and let the system apply them before it suggests anything:
- Payees this client has never paid before
- Transfers to or from accounts that aren't in the books, which could be an owner, a lender or another business
- Amounts that are round, or large compared with the client's usual activity
- Payees coded to more than one account in the past, such as big-box and online retailers
- Loan payments, which need a principal and interest split
- Anything that looks personal, which needs an owner's draw or a question rather than an expense account
- Refunds and reversals, which should offset the original expense rather than land in income
- Payroll, sales tax and tax payments, which should tie to their own reports
- Anything dated in a period the accountant has already closed and locked
Make held items easy for clients to answer. Send one list per client, and give each line the date, amount, payee and two or three likely choices: “Was the $412.37 order on May 3 for (a) office supplies, (b) materials for a job, or (c) personal?” A client can answer that from a phone in a minute, and each answer goes straight back into the queue.
Before and after
Monthly bookkeeping, before and after
Categorizing in the feed
- 01Bookkeeper opens each client's bank feed in turn
- 02Accepts or corrects the ledger's guesses line by line
- 03Unclear items parked in an uncategorized account
- 04Client questions sent one email at a time
- 05Close runs well into the following month
ResultHours of clicking, and guesses buried in the books
Review-first queue
- 01Suggestions arrive with the account, the reason and the history
- 02Routine lines approved in batches
- 03Unusual lines held, each with the reason it was held
- 04Client questions grouped into one short list per client
- 05Only approved entries reach the ledger
ResultTime goes to the lines that need judgment
What the ledgers already do, and the setting to check
Both major ledgers have their own tools, and they're worth using for truly fixed payees. QuickBooks Online bank rules can carry up to five conditions, and only one rule applies to a transaction, so rule order matters. Rules can also be set to add matching transactions automatically, and Intuit itself warns that you then won't get a chance to review them before they're added to the books.
Xero's automatic reconciliation, where your plan includes it, acts only when it's highly confident, and it can be switched on or off for each bank account. Know which client accounts have it on.
What outside tools can and can't touch
Before you trust any outside tool with live books, know what it can reach. It generally can't work inside QuickBooks Online's “For review” bank feed: answers on Intuit's developer forum say the public Accounting API doesn't expose that queue. Xero has said it won't let apps reconcile bank statement lines through its API either.
So when an outside tool “posts” a categorized line, it usually creates a new transaction in the books, while the bank feed still delivers its own copy that someone has to match or exclude. That's why review-first has to happen in the tool's own queue, before anything is written to the ledger. Ask every vendor exactly how it avoids duplicates, then test it on a sample company before connecting a client's live books.
A month-end close built around the queue
With routine lines handled during the month, close becomes a short checklist instead of a scramble. The days below are targets to adapt, not promises.
| When | Work |
|---|---|
| During the month | Feeds pulled; suggestions queued; routine batches approved weekly |
| Days 1 to 3 after month-end | Final statements in; one question list sent to each client |
| Days 3 to 5 | Answers applied; holds cleared; loan splits entered; payroll and sales tax tied to their reports |
| Days 5 to 7 | Every bank and card account reconciled; receivables and payables aging reviewed; changes from last month noted |
| Days 7 to 10 | Reviewer signs off; monthly package sent with variances flagged for the accountant to explain |
Start with three clients, not thirty
- 01Pick three clients with steady, well-kept books and at least a year of coded history.
- 02Write each client's hold rules, starting from the list above.
- 03For one month, keep coding as usual while the system makes its suggestions alongside.
- 04Compare line by line, and sort the differences: wrong account, should have been held, or held for no good reason.
- 05Adjust the hold rules, then switch those three clients to review-first and add the next few.
Messy books make poor teachers. A client whose history is full of miscoded lines will get suggestions that repeat the mistakes, so clean up the worst accounts before using that history for anything.
Guardrails that keep the books yours
- Each client's chart and history stays with that client. Patterns from one client never code another client's books.
- Require in each vendor contract that client transactions aren't used to train models, and name every tool in your written information security plan. Firms that prepare tax returns are required to keep one under the FTC Safeguards Rule.
- Every approval is logged with who approved it and when.
- Closed periods are locked in the ledger, so a late suggestion can't change last quarter.
- A reviewer signs off on every account at close.
Clean bank coding pairs naturally with on-time documents from clients; see automating client document collection. For the broader principle behind review queues, read human-in-the-loop AI, and for how we set this up inside QuickBooks Online or Xero, see our page for accounting firms. Requirements differ by state and by the services your firm offers, so take the compliance points as general guidance rather than legal advice.
Sources
- QuickBooks: Set up bank rules to categorize online banking transactions in QuickBooks Online
- Intuit developer forum: Is there API access to QuickBooks Online bank transactions “For Review”?
- Xero Developer: “Reconcile via the API” request, declined by Xero (May 2026)
- Xero: Bank reconciliation software (automatic reconciliation)
- IRS: Security Summit reminds tax pros they need a Written Information Security Plan