01Why "human in the loop" matters for categorisation
Transaction categorisation is the most repetitive part of bookkeeping, which makes it the obvious place to automate. It is also where small errors compound: a miscoded vendor in January is miscoded all year. The goal is to remove the typing while keeping a person responsible for what ends up in the books.
A human-in-the-loop design does exactly that. Software proposes; a person disposes. Nothing posts without approval, and the approval is recorded.
02Step 1: Clean up the chart of accounts and rules
Automation is only as good as the categories it maps to.
- Tidy the chart of accounts. Merge duplicate accounts and retire ones nobody uses.
- Write rules for known vendors. Payroll provider, rent, utilities and regular suppliers should map to the same account every month.
- Document exceptions. If a vendor can be two different things, such as a supplier that sells both stock and equipment, note how to decide.
Rules handle the predictable majority. AI suggestions handle the long tail of new and irregular vendors.
03Step 2: Let the software draft every transaction
For each new transaction, the software should propose:
- A category, from your chart of accounts.
- A confidence score, showing how sure it is.
- A reason, such as "matches 11 earlier invoices from this vendor coded to Dental supplies".
- Alternatives when it is unsure, such as "Loan payment (54%) or Equipment (31%)".
The reason is what makes review fast. A reviewer who can see why a suggestion was made can approve it in seconds or spot the mistake immediately.
04Step 3: Set confidence thresholds
Not every suggestion needs the same attention. Split the queue into bands:
| Band | Typical handling |
|---|---|
| High confidence and matches a rule | Approve in bulk after a quick scan |
| High confidence, no rule | Approve individually with the reason visible |
| Medium confidence | Review the alternatives and choose |
| Low confidence | Investigate, or ask the client |
Start with conservative thresholds and loosen them as you see how reliable the suggestions are for each client.
05Step 4: Review in a focused queue
Reviewers should work from a queue that shows only what needs attention, filtered by client, account or band, rather than scrolling through every bank line. Good queues let you:
- Filter to "to review", "transfers" or "payroll".
- Approve several high-confidence items at once.
- Change a category and add a note in the same step.
- See the bank line, the source document and the suggestion side by side.
06Step 5: Turn unknowns into client questions
Some transactions cannot be categorised without the client. Instead of guessing or parking them in "Ask my accountant", raise a question with the details and a few answer options. Plain-language questions with one-tap answers get faster replies; see how to get clients to send documents on time for the same principle applied to tax documents.
07Step 6: Record every approval
An audit trail should show, for each transaction, the suggestion, the final category, who approved it and when. That record protects your firm, helps you train new staff and shows where rules need improving.
08Step 7: Improve the rules every month
At the end of each close, look at the corrections reviewers made:
- Recurring corrections become new rules.
- Vendors that are often wrong get an exception note.
- Clients with many questions may need a short conversation about how they record spending.
Over a few months, the share of items that need real attention falls, and the close gets faster without losing control. For the close itself, see our month-end close checklist.
09Mistakes to avoid
- Auto-posting without approval because confidence is high. High confidence is not the same as correct.
- Hiding the reason. A category without a reason is hard to review.
- Using a suspense account as a parking lot for months. Unknowns should become questions with an owner and a date.
- Never revisiting rules. Rules drift as clients change.
10Sample rules for a typical small-business client
Rules work best when they are specific and documented. An illustrative set for a dental practice:
| Vendor or pattern | Category | Notes |
|---|---|---|
| Payroll provider debits | Payroll clearing | Split by the payroll journal, not here |
| Dental supply company | Dental supplies | Equipment over the capitalisation threshold goes to fixed assets |
| Landlord | Rent | Fixed monthly amount; flag if it changes |
| Card processor deposits | Patient revenue | Fees recorded separately from the processor statement |
| Insurance payouts | Patient revenue | Match to the remittance where available |
| Transfers to savings | Transfer | Never income or expense |
| Payments to the bank | Ask | Could be loan principal, interest or a purchase |
The last line matters as much as the others. Some patterns should always become a question.
11What reviewers should check in each band
High confidence with a rule. Scan for amounts that look unusual for the vendor. A rent payment twice the normal size deserves a look even if the category is right.
High confidence without a rule. Read the reason. If it is based on several past transactions from the same vendor, approve. If it is based on a vague match, check the source.
Medium confidence. Compare the alternatives. Look at the memo, the amount and the date. If you still cannot tell, ask.
Low confidence. Assume it needs the client. Raise a specific question with answer options.
12Writing good client questions
A good question is specific, short and easy to answer:
"We see a payment of $2,100 to Chase on October 9. Is this a loan payment or an equipment purchase?" [Loan payment] [Equipment] [Something else]
Avoid questions like "Please explain the attached list of transactions". Clients answer one clear question faster than a list of twenty.
13Measuring progress
Track a few numbers each month for each client:
- The share of transactions approved in bulk.
- The number of corrections reviewers made.
- The number of client questions and how quickly they were answered.
- Review time for the close.
Over the first few months, bulk approvals should rise and corrections should fall. If they do not, the rules or the chart of accounts need attention.
14How Marksford Books does it
Marksford Books suggests a category with a confidence score and the reason for every transaction, waits for a person to approve, and raises differences as questions through your ClientBase portal. Your chart of accounts and rules are applied the same way every month, and every approval is recorded. Read more in what AI bookkeeping software can and can't do.
FAQFrequently asked questions
What is the difference between a bank rule and an AI suggestion?
A bank rule is a fixed instruction you write, such as "payments to this landlord go to rent". An AI suggestion is a prediction based on patterns in past coding and the transaction details. Rules are predictable; suggestions cover vendors you have not written rules for. Most firms use both.
How long does it take before automated categorisation saves time?
Most firms see a difference within the first two or three closes for each client, as rules are added and reviewers learn to work the queue. The biggest gains come once recurring corrections have been turned into rules.
Should every client use the same confidence threshold?
No. Start with one conservative threshold, then adjust per client. Clients with stable, recurring vendors can use a lower bar for bulk approval; clients with irregular spending need more items reviewed individually.
Can I let clients approve their own categories?
Clients can answer questions about specific transactions, which is very useful, but approval of the books should stay with your team so that categories follow your chart of accounts and your firm's standards.
Can bank transaction categorisation be fully automated?
It can be largely automated, but a person should still approve suggestions before they change the books, especially for new vendors and unusual amounts.
What is a confidence threshold in bookkeeping software?
It is a cut-off for how sure the software must be before a suggestion can be approved quickly. Items below the threshold get a closer look or go to the client.
How do I handle transactions only the client can explain?
Raise them as specific questions with answer options, through a portal or a single thread, rather than guessing or leaving them in a suspense account.
What should an audit trail for categorisation include?
The suggested category, the final category, who approved it, when, and any note explaining a change.
→Tools for this topic
→Related guides
This guide is general information for accounting professionals. It is not legal, tax or accounting advice. Marksford is not a CPA firm.