Audit intermediate Works with: Any AI

New Starter and Leaver Payroll Controls Audit

Table output Has example

Check that people are added and removed correctly.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Rate this prompt

Loading ratings…

Audit starter and leaver handling. Starters and leavers list with dates, codes and the date payroll was changed: [STARTER_LEAVER_LIST]. Process: [PROCESS]. Authorisation: [AUTHORISATION].

Check that each change was authorised, effective dates are correct, final pay was handled as policy requires, access to systems ended and no one was paid after leaving. Calculate the delay between event date and payroll change for each.

Return a table, an average delay with arithmetic, exceptions, and a process: notification form, approval, deadline for payroll cut-off, and monthly reconciliation of the payroll list to the HR list.

Add a worked delay calculation with invented data. Leaver code 21 left on 31 January; payroll changed on 14 February; one extra payment of 1,600 was made on 28 February. Delay from event to payroll change is 14 days. Starter code 33 started on 3 February; payroll set up on 10 February; delay 7 days; first pay was late by one week. Average delay for two cases is (14 + 7) divided by 2 equals 10.5 days. Describe a process with deadlines: HR sends a joiner and leaver form by the third working day; payroll processes before the cut-off; a monthly reconciliation compares the HR list with the payroll list. Provide the form fields: employee code, start or end date, role, hours, pay, bank details collected securely, authoriser and date. Add a check that system access is removed the same day for leavers. Include the steps for recovering an overpayment, handled carefully and in line with the law, which I must confirm [VERIFY] for [JURISDICTION], with the employee informed in writing. Ensure that personal data on the forms is kept confidential and retained only as long as required. Add a metric for monthly review: the number of days from event to payroll change, average and longest, with a target. Include an exceptions log with reasons for each late change.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

See an example result (fictional data)
Invented cases. Leaver code 21 left 31 January; payroll changed 14 February: delay 14 days; one extra payment of 1,600 made on 28 February. Starter code 33 started 3 February; payroll set up 10 February: delay 7 days; first pay a week late.
Average delay = (14 + 7) / 2 = 10.5 days.
Process: HR form by the third working day; payroll cut-off on the 20th; monthly reconciliation of the HR list to the payroll list.
Overpayment recovery must follow the law and be explained in writing [VERIFY].

Illustrative only, made-up data. Your results will differ and must be reviewed.

Related prompts