How bookkeepers can complete the operator practicum

Schedule it for a quiet fortnight between filing deadlines. The practicum is two weeks reviewing an agent's bookkeeping work: suggested coding, recurring postings, reconciliation differences, client queries and held payments. Nineteen decisions in twenty must be correct, with no missed red line, such as letting a posting into a locked period. A Pryme assessor signs off the result.

What is the practicum, and how does a bookkeeper take it?

The practicum is the second half of Certified Pryme Operator; the written exam comes first. You work a queue of decisions an agent could not complete alone, decide each one with a reason, and are assessed against the standard. The explainer on what the operator practicum is covers the design.

Many bookkeepers work in small practices or for themselves, where Pryme may not be in use. That is not a barrier. You can do the practicum on a simulated queue in a free workspace, held to exactly the same standard, as doing the operator practicum without a job explains. The guide to AI operator certification sets out the full path.

What will your queue hold?

Expect the work of a month-end, broken into decisions:

• bank-feed transactions with suggested categories and tax codes;
• recurring items the agent posted within rules, for you to sample;
• reconciliations listing unexplained differences;
• items that could be business or personal, such as card spending by a director;
• capital purchases that could be miscoded as repairs or supplies;
• supplier statements that disagree with the ledger;
• client queries drafted by the agent about missing receipts;
• payments prepared for clients and held for release, some following a bank detail change.

Plenty of items will be right as drafted. Approve them. Holding everything shows caution, not judgement.

How should you work through each decision?

1. Agent, depth 1: has read the bank feed, ledger and receipts. The bank feed is sealed; a client's receipt photo is declared; a supplier's emailed statement is external.
2. Agent, depth 2: has suggested the category, tax code or reconciliation match, or drafted a client query.
3. You: decide: accept, recode, query the client, hold or escalate.
4. You: write a one-line reason with the evidence and, where it applies, the rule.
5. Agent, depth 3: recurring postings within agreed rules have already been made. Sample them as the queue asks.
6. Agent, depth 4, held: client payments wait for an authorised release. Decide whether the conditions are met.
7. Assessor: reviews your decisions and reasons.

Which red lines will a bookkeeper meet?

Missing any red line ends the attempt. Expect these:

• A posting into a locked or filed period approved without authority.
• A tax treatment change that would alter a filed return, approved without review.
• A ledger change driven by an external document alone, such as posting an invoice because a supplier's statement says it exists.
• A client payment released to bank details changed by email without verification. An external claim cannot authorise a payment.

What makes a good reason?

The assessor reads reasons to see how you think. Each should name the evidence:

• Weak: "Recoded."
• Strong: "Laptop over capitalisation threshold; recoded from office costs to equipment."
• Strong: "Statement shows invoice not in ledger; external; held, client asked for copy."
• Strong: "Card spend at supermarket by director; no receipt; coded to director's loan pending client confirmation."

Write the reason when you decide. Reconstructing it later produces vague notes.

Here is an invented example of the kind of item to expect. A bookkeeper we will call Grace sees a reconciliation the agent has matched cleanly, except for one receipt from a hardware shop coded to repairs. The amount is large for repairs, and the description mentions a new workbench. Grace recodes it to equipment and notes why. On its own it is a small decision; across a fortnight, decisions like it are what the assessor is looking for. Later that day, a held payment to a client's supplier follows a bank change emailed the same morning. Grace holds it pending a call to the number on file. That one is a red line, and she caught it.

What should you track during the two weeks?

Keep a short list of decisions you were unsure about, grouped by type. Bookkeepers often find their hesitation clusters around one area, such as tax on mixed supplies or the line between repairs and improvements. Revisit the relevant lessons that evening. If you make 180 decisions, nineteen in twenty allows nine wrong, and not one may be a red line.

The operator practicum preparation checklist helps you set up the fortnight: time blocked, red lines learned, log ready.

Where do bookkeepers usually slip?

• Coding from memory of the client. The practicum client is not your client. Read the evidence.
• Clearing reconciliation differences to make the numbers balance. An unexplained difference should stay unexplained until you have evidence.
• Missing the quiet errors. A miscoded item that does not affect the reconciliation is still wrong.
• Treating sampling as a formality. Sample depth 3 postings properly; one may be the test.

People from other backgrounds meet the same standard differently. Team leaders bring calibration habits, and paralegals bring careful reading of documents, both useful comparisons.