Skip to content

CPD lab · Payroll, Controls

Payroll run checks

A monthly payroll for about 40 staff, ready to pay: use your AI tool to check the register against last month, the HR change list and the bank file, and decide pass, query or hold for every line, without holding pay that is owed.

All the ways to get this lab

Comes with Employment tax: IR35, benefits and expenses and Finance for HR and payroll teams, and with the year. 29 labs open now.

The brief

You are the payroll reviewer at Tolland & Reeve Joinery Ltd, a joinery firm with about 40 staff. The November 2026 payroll (1 to 30 November) is ready to be paid on Friday 27 November 2026 and needs your check before the bank file is released.

Use only this invented pack in any AI tool. Every company, person, NI number and bank detail in it is made up. Never put real staff data (names, NI numbers, bank details, pay) into an AI tool unless your employer has approved that tool for it. This is the data-handling habit the lab is testing, as well as the checking.

The pack has the November register (41 lines), the October register, the HR change list, the bank payment file with its control totals, and the payroll checks policy. The policy and this brief give the rates and rules, checked on 14 November 2026: from 1 April 2026 the minimum hourly rates are GBP 12.71 for age 21 and over, 10.85 for 18 to 20, 8.00 for under 18 and 8.00 for an apprentice (under 19, or 19 and over in the first year); age is taken on 1 November 2026. A starter with no P45 and no starter checklist is still paid, on the emergency code 1257L Month 1, and HR chases the checklist. The starter checklist replaced the P46.

Tax, NI and pension figures come from the payroll software. Take them as right. You are not asked to recalculate them.

Decide an action for every register line. PASS: the line is right and supported by the pack, and it is paid as shown. QUERY: the line stays in the bank file, because the employee is owed the pay, but something about it must be confirmed or corrected by a named person (HR, payroll or a manager) before or straight after the run. HOLD: the line comes out of this run's bank file, or only the part of it that is in doubt, with the rest of the pay released, because paying it could send money to the wrong person, for the wrong period or in an amount nobody approved.

Give one line per register line (41 in all, using the line_id in the register) with a short reason. Post nothing and change nothing: do not alter the register, the HR list or the bank file, and do not release any payment. Your output is the table, for the payroll manager to act on.

Querying or holding a line that is fine delays an employee's pay and teaches the team to ignore your flags. Mark only what the evidence supports.

Then write a short review note: what the AI got wrong, what you checked, and what goes to whom.

Objective: To be able to use an AI assistant to check a monthly payroll run against the HR change list, last month's payroll and statutory rates, identifying leavers, ghost employees, minimum wage and tax code problems and unapproved payments, while keeping staff data safe.

What's in the pack

Every name, figure and email in the pack is invented. Use your own AI tool: Claude, ChatGPT, Copilot or Gemini.

  • payroll-register-november.csv

    November 2026 payroll register: 41 lines, gross to net, bank details

  • payroll-register-october.csv

    October 2026 payroll register (last month): who was paid what

  • hr-change-list.csv

    HR change list: starters, leavers, pay changes, approvals and bank notes

  • bank-payment-file.csv

    Bank payment file for 27 November 2026, built from the register

  • bank-file-control.txt

    Bank file control totals: number of payments and total

  • payroll-checks-policy.txt

    Payroll checks policy extract: minimum wage rates, starters, leavers, approvals, bank accounts

The traps

The pack has 8 deliberate traps: cases where AI tools often get it wrong and a person must check. We don't list them here. Finding them is the job, and your feedback names each one you missed.

What you submit

  1. Your result, as a table with the columns line_id, action, reason.
  2. The prompt you used.
  3. A short review note, 150 to 350 words: what the AI got wrong, what you checked, and what goes to a person.

How it's marked

  • Your result, checked line by line against the answer key60%
  • Your review note, marked on traits40%

The review note's traits:

  • Payments that should stop found
  • Pay owed handled as a query, not a hold
  • Rates and rules applied correctly
  • Genuine lines not over-queried
  • Clear escalation and data kept safe

Pass at 80. Under 80, read the feedback and try again. Then write your reflection and copy the entry for your CPD record.

Price

  • Employment tax: IR35, benefits and expenses, £39. The role track and its labs, this one included. No end date.
  • Finance for HR and payroll teams, £39. The role track and its labs, this one included. No end date.
  • Everything for a year, £199. Every course, role track and lab for 365 days.
  • Monthly, £19.99 a month, cancel any time. Every lesson, plus 8 marked tasks a month, across every course, role track and lab.

Buying for a team, or want a lab built on your own process? CPD for employers.