Payroll Operations

How the Payroll Command Centre works

Written for the people who use it every day. Nothing here is a rule you have to memorise — the point of the board is that it works out what is late so nobody has to remember. Back to the board

Checked against the app on 21 November 2026. Anything that has changed since is under What has changed.

The idea in one paragraph

A run is one payroll schedule for one pay period — Harbour Kitchen's September, or Copperworks' week 36. Every run has nine steps and a handful of deadlines worked back from its pay date. You tick steps off as you do them; the board works out from those ticks and those dates whether a run is fine, at risk or late. Done and Overdue are never set by hand, which is the whole point: a status somebody has to remember to update is wrong by Wednesday.

If the board says something is overdue and you think it is not, the fix is almost always a tick that has not been made or a date on the client that is wrong, not the status. You can park a run On hold with a reason, but you cannot mark it Done or wipe out an Overdue.

Where things are

The screens are in the sidebar on the left, grouped the way WSOP groups its areas: My work (Home, Activity, Tickets), Payroll (the Lifecycle, the Calendar, Team, Imports, Reconciliations, Payroll cases), Tronc (its overview, schemes and set-up, the staff register, periods and sign-off, the calendar, the rules, cases and consultations, and starter letters), Clients (Clients, Compliance, Templates), Firm performance (Enterprise, Scorecards, Profitability, Trends, Reports), Improvement (CIP, SOPs) and Settings (Admin). The square beside Go to folds it down to a rail of icons, and the browser remembers that. Go to, or Ctrl K, finds a screen by name. On a phone the sidebar is behind the menu button at the top left. Inside Client Operations it starts as the rail, because CIP's own sidebar is already on the left.

Your name at the top right is a menu: who you are and what you can see, Use the board in Claude, Preferences (which screen the board opens on, and whether the sidebar starts open or as the rail, on any computer), Change password and Sign out.

ScreenWhat it is for
HomeYour day: My tasks, everything on the board that is yours, with the bell for anything unread, and Nora.
ActivityThe board itself. One row per run, the filters, bulk ticking and what has moved.
Payroll LifecycleThe same runs grouped by where they are in the cycle, so you can see where work is stacking up.
Payroll CalendarWhat pays on which day, bank holidays included.
TeamWho carries which schedules and runs: each person's portfolio, how it compares with the team average, and their runs week by week.
ImportsClient files in (CSV, Excel or PDF), BrightPay files out.
ReconciliationsThe period reconciliation, and the National Minimum Wage check. It also opens the pre-draft check in the run drawer.
Payroll casesNMW checks, HMRC enquiries and compliance checks, penalties, status questions and the other payroll episodes, each with its correspondence and the dates it set.
TroncIts own heading: every client's tronc scheme, the staff register, each period's calculation and sign-off, the payslip calendar, the scheme rules, cases and consultations, and the letters to new starters.
ClientsSchedules, pay day rules, notes, the client's own steps and their SOP.
ComplianceThe measures, RTI exceptions, pensions, Payments to HMRC and Employment Allowance.
EnterpriseWorkload index, pricing and KPIs.
ScorecardsOne card per client, worst first: paid on time, why runs slipped, our delays, accuracy, client inputs, tickets per 100 payslips, days to close and margin, with touches a run and rework per 100 runs per client and per lead, and complaints marked in OpsDesk per 100 runs (shown, never part of the grade).
ProfitabilityWhat each client pays against what it costs to serve, and the book against its budget.
TrendsTickets and timelines a month at a time, and which way each is going.
ReportsThe delivery and timeliness report for a month, to export as a PDF or email inside the firm.
TemplatesClient messages (sent by email, or in the client's OpsDesk thread), handover and cover notes, and the festive and bank holiday pay-date emails.
TicketsThe payroll team's tickets from both places they live, each marked OpsDesk or HubSpot. OpsDesk inbox is payroll@'s OpsDesk tickets worked like a help desk: the tickets on the left (Mine, Unassigned, payroll@ and any other department mailbox you can open, or one client's), with a dot on the unread ones, the SLA time left, the priority and who has it; the conversation in the middle, the client's emails on one side and the team's replies on the other, internal notes dashed amber and labelled, changes as small grey lines, files to download, and earlier quoted emails folded away; and the ticket's details on the right (its client here, status, priority, who has it, the SLA, merge, and Open in OpsDesk). Write under the conversation: Reply to client or Internal note (mention a colleague by their work email, in notes only), attach files, Ctrl+Enter to send. A reply shows as Sending at once and as Sent when Outlook confirms it; if it does not go it says Not sent, with Retry. It is live: what anybody does in OpsDesk, WSOP or here shows within seconds, you can see who else is looking at or replying to the ticket, and you are warned before you send if somebody answered while you were writing. Everything is done as you, so OpsDesk's own permissions apply, and a read-only account here can only read. On a 13 or 14 inch laptop all three parts fit side by side, an email address in the details stays on one line (hover over it for the whole address); on a narrower window Details shows them in place of the conversation, and on a phone it shows one part at a time. Client view sets one client's OpsDesk tickets beside their HubSpot ones. Search is HubSpot's tickets, tagged to clients (most of them by themselves, marked matched), and Insight: what both sources say is going wrong. An OpsDesk ticket is counted against a client by who raised it (their address, then their company domain); Counted against on the ticket's details shows which, and you can change it there. Under it, This payroll is that client's open run with the nearest pay day: its period, pay day, colour and stage, the inputs, approval and funding request with their deadlines, what happens next, the lead and the pinned notes, with Open the run to go to it on the board. Only a run you could see on the board is shown. When pay day is close and the run is not approved, the row says Suggest urgent (pay day within one working day) or Suggest high (within three), and the details say why with a Set button; nothing changes until you press it, and it never suggests lowering a priority. A ticket marked a complaint in OpsDesk carries a red Complaint chip. With the Payroll cases screen, Payroll cases in the details lists any case opened from the ticket, and Open a payroll case (for anybody who can change the board) opens the case form with the client it is counted against and the ticket's subject as the title. A CSV, Excel or PDF file on a ticket counted against a client has Send to Imports beside it (with the Imports screen, for anybody who can change the board): the file goes into that client's open import batch for its current run, or a new one labelled with the ticket's number, read exactly as a dropped file is, up to 3MB. It says where it went, with Open in Imports, and if the email is evidence that the run's inputs have arrived it offers Tick Inputs in, which you press. Sending the same file again adds nothing, and the file on Imports says From OpsDesk, which opens the ticket again.
CIPThe continuous improvement plan: why runs were late, what the tickets say, ideas and actions.
SOPsThe firm's procedures, shared with WSOP: one manual, the same in both. Opens as your WSOP account.
AdminPeople and their access, adding somebody, the account log, who has confirmed the weekly briefing, the health check, clients and workload, import set-up and the system. Administrators only.

How it works and What's new sit at the top right of every screen, including when the board is open inside Client Operations.

The weekly briefing. The first time you sign in each week (weeks start on Monday) a short window opens: what has been added since you last looked, from What's new, then a few things the board already does, a different few each week. It turns over by itself; the arrows or the bars along the top move through it, and the pause button or resting the pointer on it holds it still. Once you have seen every item, tick that you know the Command Centre does each of them and press Done for this week. It cannot be closed without the tick, and it does not open again that week on any device. It only mentions screens you have, and each confirmation is a line on the Admin account log. Administrators see who has confirmed each week on Admin > Weekly briefing.

Your day: the Home screen

The board answers "what is the state of everything". Home answers the question you actually have at 9am: what is waiting on me, in what order, and who am I waiting on. Under Nora is My tasks: everything on the board that is yours, in one place, the same way Tasks works in WSOP.

To do and Notices

  • To do is work that needs you. It stays until it is done. Marking it read does not clear it, because reading a thing is not doing it.
  • Notices are things that happened to your work: somebody else ticked a step on one of your runs or moved a run to you, left a reminder on one of your clients, answered an idea you put forward, or changed or handed you an improvement action. They go quiet once read, and opening one marks it read.

What is on your To do list

  • Complaints: a ticket somebody in OpsDesk has marked a complaint (or a Poor survey answer marked for them), on a client you lead, red from the day it is marked and first on the list. Administrators who see the whole book get every one, including a complaint counted against no client yet, which says to tag it. It opens the ticket in the inbox, and it goes when the ticket is closed in OpsDesk. A complaint is not also listed as an ordinary open ticket.
  • Payroll runs: one next action per run of yours, and it is the first step not done, not the furthest along. If somebody drafted before the inputs were ticked, chasing the inputs is still the job. Anything overdue is shown however old; everything else has to fall due inside the next seven days. Tick records the step on the run exactly as the board does, and the run moves on to its next step.
  • Inputs may have arrived: an email from the client's contact, with files attached, came into payroll@ in OpsDesk while your run was waiting for its inputs (from a week before the period ends up to the inputs deadline). It names the OpsDesk ticket and the time it came in. Look at it first: Tick Inputs in ticks the step as the board does, at the time you tick, and also notes on the run when the email arrived. Nothing is ticked for you. It follows the Tickets screen. The run drawer shows the same, under Inputs may have arrived, with Open the email.
  • Approval due tomorrow: send the approval chaser: on the working day before a run's approval deadline, once its inputs are in and it is not yet approved. Opening it takes you to Templates with the approval chaser (a template whose name says approval) and that run's dates filled in. Nothing is sent until you press Send. A chaser sent to the client since the inputs came in, or the approval being ticked, takes it off. It follows the Templates screen.
  • Inputs due tomorrow: send the client a reminder: on the working day before a run's inputs deadline (a Friday for a Monday deadline, and over the weekend in between), while its inputs are not in. One for each such run. Opening it takes you to Templates with the Inputs reminder template, the client and that run's dates filled in, and the client's open OpsDesk thread offered when there is one. Nothing is sent until you press Send. Sending it, or any chaser in the week before the deadline, takes it off. A reminder is recorded as a reminder, not a chase, so it never counts as the inputs having been late. It follows the Templates screen.
  • Funding cut-off tomorrow: funds not requested: from the working day before a run's funding cut-off (a Friday for a Monday cut-off, and over the weekend in between), while neither Funds requested nor Paid is ticked. On the cut-off it says today; once it has gone it is red and says how many days ago. It says what Modulr's emails in payroll@ show for that run (for example awaiting the client's approval since a time), or nothing seen from Modulr when there is none, which is not the same as not approved. Opening it takes you to Templates with the Funding chaser template and the run's dates, in the client's open OpsDesk thread where there is one. Nothing is sent until you press Send, and a funding chaser is never counted as a chase of inputs or approval. Sending one does not take the item off, because the chaser is not the request: Tick Funds requested does, as ticking it on the board does. It follows the Templates screen, and Modulr is read only for an account with the Tickets screen.
  • RTI: an HMRC rejection, or an FPS whose reference belongs to more than one client and needs allocating (in the RTI card at the foot of Home).
  • HMRC payments: a PAYE month on one of your clients not yet marked paid, from five working days before the 22nd (amber), and red once the 22nd has gone, saying how many days late. An administrator also sees every month already late on another lead's client, and any month due on a client with no lead. Only a person marks a payment paid, on Compliance › Payments to HMRC.
  • Pension contributions: a paid run of yours whose Pension submitted is not ticked, from five working days before the 22nd of the month after its tax month (amber), the same date Compliance judges pension submissions by, and red once that has gone, saying how many days late. A client with no pension scheme, or with pension automated, is never listed. Tick Pension submitted ticks it as the board does. An administrator also sees every run already late on another lead's work, and any due on a run with no lead. It does not change a run's colour or its deadlines.
  • Tronc: a tronc period on one of your clients not yet paid, once its deadline is inside a week (amber) or past (red, because that is a breach of the tips law). It names the next step: work out the split, chase the figures if the client or troncmaster sends them, approve it, or pay it and mark it paid. Open it goes straight to the period. Whatever the deadline, it also lists a client's figures that have arrived and not been used, people on the timecards who are not on the register, and an approved period whose BrightPay export did not match (red).
  • Cases: a payroll or tronc case on one of your clients, or one you handle, that needs something: a reply we owe that is late (red) or due within a fortnight (amber), a date the client or the workers missed (to chase, or for a consultation that has closed, a decision to make), or nothing recorded for 30 days. A case in hand with nothing due is not listed. Payroll cases follow the Payroll cases screen and tronc cases the Tronc screen. Open it goes straight to the case.
  • Pension duties: a client's pension re-enrolment, and the declaration of compliance due within five months of it, each from three months before its date (amber); a declaration past its date is red and says how many days late. The dates come from the client's pension dates on Edit client (see Clients, notes and quirks). Once the declaration is made with The Pensions Regulator, put its date on Edit client and the item goes.
  • Year end: from 1 March, one item per client with the next step of its year-end checklist and its date (the final FPS, the EPS, P60s, P11Ds); red once that date has gone. Where nobody has said whether the client has benefits, it asks that instead. It opens the client's drawer, where you tick the step.
  • Reminders left on your clients that have come due, with a Resolved button.
  • Clients: one that cannot go live, or is live and cannot run, and SOPs to review or write.
  • Tickets open on your clients, oldest first.
  • Continuous improvement: your improvement actions, and any late run of yours that has been paid but has no cause recorded.
  • For administrators, ideas waiting for a decision, people waiting for a password, and clients with no payroll lead.

Your runs are the ones with your payroll lead name on them, whatever you are allowed to see. An administrator who sees the whole book does not get the whole book as a to-do list. A run on hold, or signed off, is nobody's job today and is not on the list.

Finding your way round it

  • The tiles are filters: Overdue, Due in the next 7 days, Waiting on others (a chase, where the client has the next move), Waiting for your decision, and Not yet read. Press one again to clear it.
  • The chips under them narrow the list to one area, and the search box searches what is left.
  • Open it goes straight to the run, client, payment or action, not just the tab.
  • The list is ordered worst first, then by area, then by date.

The bell

The bell in the header, and the number on the Home tab, count what you have not read: to-dos you have not looked at yet and unread notices. It updates every five minutes on any tab. Press it to go to your list.

The + for quick actions

The coral + beside the bell starts the things people do most, from any tab: add a client being onboarded, offboard a client (pick it and its final pay date, nothing else), generate periods, start an import, open a new payroll case, put forward an idea, and for administrators add someone. It only offers what your account may do and has the screen for, so a read-only account does not see it.

Team tasks

Under My tasks is Team tasks: everybody's outstanding runs, so the whole team can see what is open and who has it. Each run is reduced to its one next job, and the jobs are grouped (Chase inputs, Issue drafts, Chase approval and so on), with a tick against each and the lead's name on every row. The row of names above says how much each person has outstanding and how much of it is overdue; press a name to see only theirs, or Everybody to see it all. Looking ahead sets how far forward it reaches: anything overdue is always shown. An account set to see its own schedules only sees its own work here.

Somebody else's list

An account that sees everything has a Whose list picker, to open any colleague's list as they see it. Nothing you look at there is marked read for them: what they have not read is how they find out something happened.

The board, and the nine steps

The board, on the Activity tab, is one row per run, soonest pay date first. The nine dots are the steps, in order:

  1. Inputs received — the client's hours and changes are in. Due by the inputs deadline.
  2. Draft issued for client review — the draft is out to the client for approval. It is due when approval is, unless the client has Client review days before approval set on Edit client (off for everyone until somebody types a number): then it is due that many working days earlier, the drawer shows Draft by, Home chases it by then, and a late approval after a late draft is counted as ours (or both) on CIP, not the client's.
  3. Approved — the client has approved it. If it came back with amends first, tick Approved with amends in the run; that still counts as approved.
  4. Funding requested — we have asked the client for the money. Due by the funding cut-off.
  5. Paid / Processed / Payslips live — people have been paid and payslips are out. Due on pay day.
  6. RTI submitted — the FPS has gone to HMRC. Ticked from HMRC's confirmation email, not by hand (see below).
  7. Pension submitted — the pension file is uploaded.
  8. Journal posted — it is in the ledger.
  9. Payroll cycle complete — someone has checked it and signed it off. Due three working days after pay day.

Click any row to open it. Tick a step and the time is stamped by the server, with your name against it, and it appears in that run's history and on What has moved at the foot of the board.

Which dates you are looking at

Pay dates in the filter rail decides which runs are on the board. It reaches both ways: the Ahead windows run from the start of this month out to 14, 30, 60 or 90 days or 12 months, the Back ones cover the last 30 days, 3, 6 or 12 months, and Everything is the whole board. Custom range… opens a From and a To box for any two dates. The line under the rail always says which dates are in.

Two things hold whatever the window says. Anything still unpaid is shown, however far back its pay date is — an unpaid run from two months ago is exactly what the board must not hide. And the strip at the top counts what is on the board, so if you look back a year the counts are about that year; click one and you get the rows behind it, always.

The Payroll Calendar and Compliance › Payments to HMRC each have the same control over their own dates.

The Payroll Lifecycle and the Payroll Calendar filter the same way as the Board: pick clients, leads and statuses (and stages, on the Lifecycle), or type in Search to find a client, code, period or note. The number beside each option is what you would get with the other filters already set, and the chips underneath say what is filtering the screen. On the Lifecycle the worst runs sit at the top of each column.

Checking the payroll before the draft goes

Open the run and, under Pre-draft check, attach the period's BrightPay payroll export (CSV or Excel) before you tick Draft issued for client review. It is checked against the schedule and against the export attached to the schedule's previous run, in plain arithmetic: the period (the title row's week, fortnight or month and its ending date against the run, a weeks column against the cycle), payslips of nothing, the same person on two rows, swings in a person's or the whole payroll's gross and net pay, holiday hours on top of basic hours that did not change, last period's leavers paid again, and the minimum wage. Each check says Passes, Look, Fails or Not checked, and Show who lists the people. The thresholds are written under the results.

The board holds no minimum wage rates: hourly staff are read against BrightPay's own Minimum required hourly rate column, and salaried staff are checked only once you give their usual weekly hours. A check that cannot be made (no earlier export, a column missing) says Not checked and why; it never passes by default.

Ticking Draft issued for client review while a check fails asks for a note saying why the draft is going anyway. The note is kept in the run's history beside the checks that failed. It never stops the tick; the bulk bar leaves such a run for you to tick in its own drawer. Taking a failing export off the run (Take this export off) also asks for a note, and the run's history records it with the checks that failed, so attaching the right file is never a way round the note. The file's rows are kept until the keeping time after the run is signed off (see How long dropped files are kept under Imports), then removed, leaving only how many things each check found. It needs the Reconciliations screen, and nothing about it is given to Nora or Claude.

Ready for the April minimum wage rise

This is off until an administrator types next year's minimum wage rates, once, with the date they take effect, on Admin > Import set-up (Next April's minimum wage). The board holds no rates otherwise. Once they are typed, Reconciliations > April minimum wage lists every live schedule in your book against them, from each schedule's latest pre-draft export still inside the keeping time: how many hourly staff are paid below the new rate (gross pay less tips over hours worked), by age band where the export carries a date of birth or age, else against the 21 and over rate, and says so. Salaried staff are not checked, and a schedule with no export is Not checked, never "nobody affected". The names are on that screen only.

From 1 February until the rates change, your Home list has one item per client with staff below the new rate, and one line counting the clients that could not be checked. Letter to the client opens the Minimum wage rise template in Compose: counts only, with blanks you fill in, and you send it. None of this passes or fails a run, and Switch off on Admin clears it.

Two things that are not steps

Inputs chased and Amends required are flags, not progress — chasing a client is not a step forward and amends coming back is a step back. Both are recorded so "who have we chased" has an answer.

Why the stage sometimes lags the ticks

The stage shown is the last step finished in sequence. If you tick RTI submitted without Approved (which happens when a client approves by phone), the stage stays where it was. That is deliberate: it stops the board claiming more progress than there is. A run can therefore read Done while its stage says something earlier, if a step in the middle was never ticked. That is how you notice you forgot one.

What the colours mean

StatusMeans
DoneSigned off. Not "paid" — signed off.
OverdueOne of four deadlines has gone by with its step not done: inputs, approval, the funding cut-off, or pay day itself.
At riskOne of those four deadlines is today.
On holdParked by hand, with a reason. Stops the chasing.
On trackEverything still ahead of it.

The red text beside a status says why — "no inputs (due 24 Sep 26)", "funds not requested (cut-off 29 Sep 26)" — so you rarely need to open the run to know what to do.

The colour stops escalating once people are paid. Journal, pension and sign-off after pay day are chased on Home and measured on Compliance, not by turning a paid run red.

You can pin On hold, At risk or On track on a run if you need to say something the dates cannot. You cannot pin Done or Overdue: those are facts about dates and ticks, and being able to set them would only let the board lie. A pin can raise the colour, never lower it. Pin At risk on a run whose client has gone quiet and it shows amber; pin On track on a run that has missed its funding cut-off and it still shows Overdue, because nobody is going to be paid.

Pay days and deadlines

A pay day is a rule, not a date

On the clientMeans
LWDthe last working day of the month
LWFthe last Friday of the month
LWWthe last Wednesday of the month
28th, 7ththat day of the month
Fridaythe weekday a weekly or fortnightly schedule pays on

Weekly, fortnightly and four-weekly schedules also need a seed pay date — one real pay date. Nothing can work out which Friday a fortnightly client is paid on, so without a seed the board generates nothing for them and tells you so.

Deadlines are in working days

A client's processing days is their SLA in working days, counted back from pay day and skipping weekends and bank holidays. Four working days before a Monday pay date is the Tuesday before, not the Thursday. The other two are the same: the approval lead, and the funding cut-off (before pay day, because BACS takes days). Sign-off is three working days after pay day.

Missing the funding cut-off is the one that stops people being paid at all, so a run goes red the day after that cut-off rather than waiting for pay day.

Putting runs on the board

Generate periods puts every period that pays inside a window onto the board. It is safe to run twice and safe to run for a month somebody else has already done — anything already there is left exactly as it is. A client marked Offboarding gets nothing after its final pay date, and the message says which clients it stopped for; a client marked exited gets nothing at all.

Changing a pay day moves the runs already on the board. When you save a client with a new pay day, seed pay date or lead time, its upcoming runs are moved to the dates the new rule gives, and the message lists them. A run somebody has started, or whose dates were changed by hand on the run, is left as it is. Generate periods never moves a run, so you do not need to run it again after a change.

Doing thirty at once

A weekly Monday means the same step across a lot of clients. Rather than opening thirty runs:

  1. Filter the board — the filters take more than one value, so "Annick and Mandy" or "awaiting data and awaiting approval" both work.
  2. Tick the box in the header to select everything shown, or pick rows individually.
  3. A bar appears with the steps on it. Click one.

Every run gets its own history entry, so the audit trail is exactly as if you had done them one at a time. The selection stays afterwards, because the next thing you usually want is the next step across the same thirty. Use the Tick / Un-tick toggle to reverse one, and Also change… to set the payroll lead, pin a status or set the chased and amends flags across the selection.

The chips under the filters show what is currently filtering the board, so a short board is never a mystery.

Sending a chaser in the client's OpsDesk thread

On Templates, when the client you pick has an open ticket in payroll@ in OpsDesk raised by the schedule's contact email or any of its contacts by role, Compose shows Send in the client's OpsDesk thread, ticked, naming the ticket. Send then goes as your reply on that ticket, through OpsDesk, so the client sees one conversation instead of a new email beside it. The newest such ticket is used; one raised by somebody else at the client is not, because the reply would go to them.

  • It is recorded exactly as a chaser sent by email: it counts towards clients chased, shows in the run's history and Comms sent (with a link to the thread), and the continuous improvement tab reads it the same way.
  • Untick it, or pick a client with no open ticket, and it is sent by email as before.
  • It needs the Tickets screen and write access to payroll@ in OpsDesk. Pressing Send again after a failure sends it once, not twice.

Telling a client their payslips are out

On Edit client, Tell the client when payslips are out switches it on for that client; it is off for every client until somebody ticks it. Then, when you tick Paid/Processed/Payslips live on one of their runs, a short update to the client's Updates contact (else the contact email) is written from the Payslips are out template (category payslips-out on Templates, where you can change its words) and put on your Home list and on Templates under Drafts to send. The run drawer says so, with Open it.

  • Nothing is sent: open the draft, check it, and press Send, or put it aside.
  • If the client has an open ticket on payroll@ in OpsDesk, the draft is a reply on it: one asking whether the payroll is done comes first, else their newest open ticket. It is addressed to whoever raised the ticket, and Drafts to send says a reply in OpsDesk #n. Send in OpsDesk posts the reply there; then Close the ticket is offered, and the ticket is closed only if you press it. Without the Tickets screen, or with OpsDesk not answering, the draft goes by email as before.
  • One per run. Unticking and ticking Paid again does not write a second.
  • To stop it, untick the switch on Edit client. Deleting the template only stops it until the database is next updated, which puts the template back.
  • CIP > Ticket insight shows whether those clients ask "is it done?" less since.

Asking clients about pay days at Christmas and New Year

Templates > Festive pay dates asks each company what it wants done with a pay day that falls on, or around, the Christmas and New Year bank holidays. It is for an account that sees the whole book, because one email covers every schedule a company has.

  1. One email per company. Schedules with the same name (once Weekly, Monthly and the like are taken out) and the same code are one company. The email goes to the contact on the client, and lists every pay date that company has between 21 December and 4 January, worked out from the pay-day rules, so a January run you have not generated yet is still on it. A company with no contact name or email is listed as No contact and is never sent a blank. Fix the contact on Clients, then refresh.
  2. Send. The companies are a table like the board's, with a tick on each one that can be sent (every company that is ready starts ticked). Click a company to read the email it will get, exactly as it will go, beside the table. Untick any you want to hold back, then press Send on the bar above the table to send every ticked one. Or open a company to edit its email and send just that one. It goes from payroll@ like any other, is signed with your name, and carries a reference in the subject (for example FPD2026-123) that a reply keeps. The wording is a template of category festive, edited with the other templates.
  3. Replies are read from the tickets, OpsDesk's payroll@ and HubSpot's, by that reference, so nothing has to be matched by name. An OpsDesk reply is named by its ticket number. Opening a company shows what the client wrote, and what it seems to say (bring forward, move back or keep). That is only a reading of the words. Nothing is moved from it.
  4. Record the answer. Choose bring forward, move back or keep for each date, with the new date where there is one, and press Record. A pay date can only be moved to a working day that has not gone, and only for a run that is on the board and not yet paid: generate periods first if it is not there. Recording moves the run's pay date and works its deadlines out again from the new date. The run's History says the client asked for it, its lead gets a notice, and CIP > Overrides does not count it, because it is the client's decision and not somebody setting aside the board's dates. Changing an answer later puts the run where the new answer says.

Each company shows where it stands: not sent, awaiting a reply, a reply to read, confirmed, or past the date replies were needed by.

Pay days on a bank holiday, the rest of the year

The pay-day rules do not move a pay date off a bank holiday, and BACS does not settle on one. Good Friday is the last Friday of March in 2027, so it is every last-Friday client's March pay day, and the late May bank holiday is every last-working-day client's May pay day. The board catches every pay date that lands on a bank holiday outside Christmas and New Year (those stay on Festive pay dates, exactly as above), whether the run is on the board or not generated yet.

  1. Home tells the lead from six weeks before: Pay day on a bank holiday: ask the client to move it, amber, and red in the last week. It goes once the answer is recorded, or the run is paid. An account that sees the whole book opens it on Bank holiday pay dates; a lead who sees only their own schedules opens the run.
  2. Templates > Bank holiday pay dates works exactly as Festive pay dates: pick the holiday, set the date replies are needed by, and send one email per company from the ticked list. Each email carries a reference for that holiday (for example BHP20270326-123), so a reply is found in the tickets and never mixed up with another holiday's. The wording is a template of category bank-holiday, edited with the other templates.
  3. Record the answer the same way: bring forward, move back or keep, with the new date. The run moves and its deadlines are worked out again; its History says the client asked for it because of the bank holiday, its lead gets a notice, and CIP > Overrides does not count it.

Nothing is sent or moved by itself: the board only says where a pay date lands, and a person asks and records.

RTI, ticked from HMRC's own emails

Nobody ticks RTI submitted by hand. HMRC's Gateway confirmation emails land in the payroll mailbox, and the board reads the PAYE reference and the submission date straight off each one and ticks the matching run. The date on the tick is the date HMRC recorded, not the date somebody got round to it.

  • One clear match is ticked on its own.
  • More than one possible run (two pay dates close together on the same reference) lands under Compliance › RTI with the options listed. Pick the right one and it is ticked.
  • A rejected submission shows there too, and clears itself when a later successful one for the same reference arrives.

An administrator can still tick it by hand, for a submission the mailbox never saw. If you lead your own clients, you only see, allocate or dismiss exceptions for your own clients.

Building a BrightPay file

The Imports tab takes the files a client sends — rota export, timesheet, tronc sheet, bonuses, new starters — and writes the two CSVs BrightPay imports. CSV, Excel and PDF all work. A PDF has to have real text in it; a scan is refused rather than guessed at.

  1. Pick the client, tie it to a run if you like, and start.
  2. Drag the files in. Every sheet of a workbook is read separately, and the header row is found even when there is a title and a blank line above it.
  3. Check each file: what kind it is, what identifies a person in it, and which column feeds which field. It guesses, and the guess is a convenience — never the thing that decides what gets paid.
  4. Read Worth a look. Anything it could not resolve is listed rather than guessed.
  5. Download the pay data CSV, the employee CSV, or both.

Year to date, for a client moving to us part way through the year

Drop the previous provider's year-to-date report in like any other file. It is recognised by its name (YTD, year to date, P11) or its columns, and its figures (tax code, NI letter, gross, taxable pay, tax, NI, pension, student loans, SSP, SMP, SPP, all to date) map like any other column. A Year to date card shows each figure added up over the people who have it: agree those totals to the provider's own report before you download year to date CSV.

Nothing about the year so far is guessed. The same report dropped twice is not added up, two different figures for one person are left blank and listed to fix, and a blank taxable pay or tax to date must be fixed: a blank is not nought. A nought to date is written as 0.00 even with Exclude 0 values ticked, because it is a figure BrightPay needs. The layout is a starting point: check its headings against BrightPay's year-to-date import once, and correct them on Admin > Import set-up.

How people are matched across files

A works number is believed first. Then the client's own mapping file — their spelling of a name against a payroll number — if they send one. Then the pairing the other files imply: if the rota carries both a name and a number, a tronc sheet with nothing but names lands on the right people by itself. Only then a name on its own.

Tick remember this mapping and next month's identical export arrives already mapped. Saved mappings are listed on the Admin screen.
Amounts go into the file exactly as they were written, including the sign. If a client writes deductions as negatives, the note on screen says so — check that is how your BrightPay deduction expects them before you import.

Files from an OpsDesk ticket

A client's file on an OpsDesk ticket does not need downloading and dropping: press Send to Imports beside it in the inbox. It lands in the client's open batch for the run with the nearest pay day (the same batch Start would carry on with), or a new batch labelled From OpsDesk #number, and is read and mapped exactly as a dropped file. The ticket must be counted against the client first (Counted against in the ticket's details); a file Imports cannot read, or one over 3MB, is refused in words before anything is stored. The file card shows From OpsDesk, which opens the ticket again.

How long dropped files are kept

Imports, Reconciliations and the pre-draft check keep each file already read, so a mapping can be corrected and the combine run again. Those rows hold names, NI numbers, hours and pay, so they are not kept for ever: they are removed a set number of days after the file's run is signed off (90 unless an administrator has changed it on Admin > Import set-up), by Tidy up on Admin's Health check and by a schedule every morning.

  • The file stays listed with its name, headings, mapping and row count, so it is on record that it came in and how it was read. Remembered mappings are not touched.
  • A batch whose rows have gone says so when you open it: The rows have gone. The combine cannot be run again, nothing can be downloaded from it and no file can be added to it; start a new batch.
  • Nothing is removed for a run that is not signed off. A batch not tied to a run is kept, and listed on the Health check once it is older than the keeping time, so somebody can tie it to its run.
  • A reconciliation report is tied to a run by its period's ending date (the line BrightPay writes under its headings), and only to a run of the same schedule ending that very day.
  • Every batch shows where it stands under its title: kept while the run is open, kept until a date, or removed on a date.
BrightPay keeps the payroll record itself. What is kept here is a working copy for doing the payroll, and a copy kept longer than it is needed is a risk with nothing gained.

Starters and leavers sent by the client

The starter and leaver form lets a client send us new starters and leavers through a private link instead of an email. It is off until an administrator switches it on at Admin > Import set-up, because it brings employees' personal details onto the board, which needs the firm's decision as data controller: the administrator types who decided and when. It cannot be switched on until the keeping time above has been saved, because that is what removes the details again. Switching it off stops every link at once.

  • While it is on, the client's drawer has Starter and leaver form: Make a link (with an optional last day it works) and copy the address. It is shown once; making a new one stops the old, and Stop it closes it. You send it to the client yourself.
  • For each starter the form asks exactly what BrightPay's employee import takes: title, name, address, postcode, date of birth, gender, NI number (blank if not known), email, phone, start date, job title, department, works number, and an hourly rate or an annual salary. The pay frequency is the schedule's own. For a leaver it asks a name or works number and the last day worked, nothing else. Anything that does not look right (an NI number HMRC never issues, a postcode that is not one, a date that does not exist) is sent back to the client to put right, and nothing is kept until it is.
  • The starters arrive as an employees file in the client's import batch for the current run, ready for you to check on Imports and build the BrightPay file as usual. The leavers arrive on the run, under Leavers from the client's form, where you tick each P45 once you have issued it in BrightPay. The client's drawer lists what has arrived as counts. Nothing goes to BrightPay or HMRC by itself.
  • The details go the keeping time after the run is signed off, like every dropped file; what stays is that a form arrived, how many people were on it, and whether each P45 was ticked. Nora and Claude never read them, and the account log and the run's history say only how many starters and leavers arrived.
  • This period's files. The same form takes the period's own inputs: hours, rotas, timesheets or bonus sheets as CSV, Excel or a PDF with text in it, up to ten files and 3MB together. They go into the batch for the run open now, read and mapped as if you had dropped them on Imports, and the client is told the time we received them. With no run open the files are refused and the client is asked to send them to you; a scanned PDF with no text is refused too. Nothing ticks by itself: the run drawer shows Files from the client's form with the time they arrived and Tick Inputs in from these files, and Home lists the same while Inputs in is not ticked. Ticking from there records on the run when the files came. The cycle status page shows Files received at for this cycle. The files go the keeping time after the run is signed off, like any other, and Nora and Claude never read them.

Suggest the columns

If a file arrives with headers the board cannot work out — Ttl Hrs Wkd, Bsc Rate, Trnc — press Suggest the columns. It reads the headers and comes back with what each column probably is, how confident it is, and why.

Nothing changes until you say so. You get a list of what it wants to change, with a tick box each. Anything it is less than 60% sure about arrives unticked. Read it before you press apply — the whole point of a mapping screen is that a person looked at it.

It never sees anybody's details. What gets sent is the column headers and the shape of the values, not the values: an NI number goes as AA999999A, a name as Aaaaa Aaaa, a postcode as AA9A 9AA. Numbers go as a range, because 22 to 44 is what says "hours" and 12 to 14 is what says "hourly rate". No name, no number, no address and no figure attached to a person leaves the building. There is an Exactly what was sent link on the screen — open it, it is the truth.

How this compares to last time

Underneath the files, the board compares what you have dropped in against the last lot from the same client. This is not the AI — it is arithmetic, done here, and nothing is sent anywhere for it.

  • Fix — a subtotal line about to import as an employee, or the same works number twice. Deal with these before you download anything.
  • Check — somebody's hours or pay nearly doubling, somebody on the last import missing from this one, a starter with no NI number, a row with no name.
  • Note — new starters, and a headcount well off what the client record says.
The one worth taking seriously is a Total row. Files often end with one, and imported as a person it is an employee being paid everybody's wages. It gets caught whether the word is in the name column or the payroll-number column, and it is the only thing on this screen the board calls an error.

Paying HMRC

PAYE is paid per tax month, not per run: tax months run the 6th to the 5th, and several weekly runs roll into one payment. So Compliance › Payments to HMRC is one row per client per tax month, due on the 22nd of the month that tax month ends in — a pay date of 3 September is in the tax month that began 6 August, and is paid by 22 September.

The amount owed is added up from the runs inside the period every time you open the screen, so filling in a run's HMRC figure updates it here with nothing to regenerate. Record what was actually paid and a reference; if the two differ, the row says so rather than quietly reconciling it.

A period showing nothing in the "from the runs" column means no figures have been entered yet, not that nothing is owed. Those are different, and the second one is how a payment gets missed.

You no longer need to press Work out periods for the months to appear: the same thing runs by itself every morning over the whole book. It only adds a month that is missing; it never fills in an amount and never marks anything paid. The button is still there if you want a month now.

The run drawer shows the PAYE month the run falls in under Funding and PAYE, beside the funding request: this run's HMRC figure, what the runs in the month add up to, whether it has been marked paid, and how many days late it is if not. A run with no HMRC figure says so; it never reads as £0.00.

Under Funding and PAYE the drawer also shows what Modulr's own emails in payroll@ say about the run's funding, read from OpsDesk as you: for example Awaiting client approval in Modulr since 08:03, approved, paid out, or funds received, with the amount where the email gives one and Open the email. It is evidence only: nothing is ticked by it. If Funds requested is not ticked it says so, with a button for the board's own tick. An email that names no schedule on the board exactly (by name, legal entity, or the client code in the reference) is not put on any run. It needs the Tickets screen.

Compliance

The obligations a bureau is judged on, measured from what was ticked on this board:

  • RTI filed on or before pay day.
  • PAYE paid to HMRC by the 22nd.
  • Pension contributions submitted.
  • Runs signed off within three working days.
  • Tronc paid by the legal deadline (shown once tronc is set up). Never paid is a breach whatever the percentage.
  • Clients with a current SOP.
  • Pension re-enrolment and declarations on time (also on the Pension tab): a declaration of compliance past its date is red. A client with no pension dates stated is not measured and listed as such, and while any client is not measured this measure cannot read green.
  • Year end done by its dates: every year-end step whose date has gone, for the tax year being judged (from 2026-27, judged from 1 March 2027). A step not done is red, one done after its date is counted as late, and a step that cannot be known (benefits not said, pay days that cannot be placed) is not measured and keeps the measure from reading green.
  • Accounts and access in order.
  • Dropped files kept no longer than 90 days.

Three rules hold. A measure with nothing in it says not measured, never green. Never filed is counted apart from filed late, and anything never filed makes the measure red whatever the percentage. And the overall verdict is the worst measure, not an average.

These figures are what was recorded here. They are an internal control, not HMRC's record of what reached them.

Tronc schemes

Tronc has its own heading in the sidebar, with eight sections. Every section after the overview is about one scheme, picked at the top right, apart from Cases and consultations, which covers every scheme (see Cases below). The calculation is the bureau's Troncmaster workbook, built into the board: it was checked against a live client workbook, person by person, to the penny.

  • Tronc overview is the register: every scheme, whether NICs are due, what needs attention under the tips law, and the latest period. Underneath are clients marked Tronc: Yes with no scheme yet. Bring in the tronc client list reads the Xero Account Transactions report for Tronc Revenue: each Tronc Master invoice is a scheme. Check the client each line is matched to, pick any it could not match, untick what should not be added, then press Add the ticked lines. Each scheme is recorded with the firm as independent troncmaster and its fee; it still needs its sites, policy date and holiday pay answer, and its checks say so. A business that is not a client we run only the tronc for (no payroll of ours) is added from its line with Add as a new tronc-only client: it goes on the board with no payroll runs. A missing payroll client is added on Clients.
  • Schemes and set-up holds the scheme and the rules the engine runs (frequency, whether each site shares its own pot, whether guarantees are paid first, holiday hours, levy, the minimum guarantee, the payslip calendar and the rules document details), its sites and its roles. Bring in a Troncmaster workbook reads the client's workbook and shows what it found before anything is saved: the rules, sites, roles, the staff register and the period it was last run for. Where somebody typed over a guarantee in the workbook, the figure comes across as a guarantee set by hand with a note, for you to confirm. The scheme also records whether tronc counts towards holiday pay (a legal question for each employer, flagged until it is answered) and the cut-over date.
    Tying a site to its till. Edit a site, type the client or site name under Find its till in Dynamic Integrations, press Find and pick it. Toast tills give the card tips and the gratuities; Lightspeed gives the service charge only; any other till says it holds no tips yet. This is done by somebody who sees the whole book, once an administrator has connected Dynamic Integrations on Admin > Integrations.
    What arrives by itself holds three switches the board acts on each morning: lay down each period from the calendar; read the till once a period has ended and fill any pot nobody has entered; and ask the client for their figures the day after each period, with one reminder three days later, at the address you give or the client's contact email. It never approves, never pays, never changes a pot somebody entered, and never fills a pot while a source the scheme takes (cash tips, say) is still missing, because a pot of card tips alone would underpay everybody by the cash.
  • Staff register is everybody in the scheme: rota ID, payroll number, site, role, hourly or salaried, house pay, promised tronc, start and leaving dates and email. The promised rate is what each person is paid first.
  • Periods and sign-off: enter each site's gross pot as the employer confirmed it, with the confirmation reference, then drop the weekly timecard exports (regular hours are worked, paid time off is holiday, sickness is neither). The calculation updates as you go. Each person's promised rate is paid first from their site's pot; what is left is shared by hours; if the promises come to more than the pot they are scaled down and the shortfall is shown for the employer to decide. A guarantee set by hand needs a reason. The checks are the workbook's QA sheet: a fail stops approval, and anything marked Review needs a line in the sign-off notes. Approve as Troncmaster needs the reviewer and the employer's confirmation reference, and freezes the figures. Download for BrightPay drops straight onto the Imports screen as a tronc sheet.
    What has arrived sits above the pots on a saved draft. Read the till shows each tied site's card tips and service charge for the period, and says when a figure is not ready yet (the till has not synced past the period end, or a day is marked incomplete). Ask the client for the figures emails a link to a short form, with no sign-in, showing their sites and what their own till recorded; they fill in every figure, including cash tips, and put their name to it. Their answer appears here and on your tasks. Use these figures fills the pots: the client's figure where they gave one, the till's where they did not, with their reply as the confirmation reference. Where the client and the till differ by more than a pound, or a pot typed by hand differs from the till, it is a check marked Review, so approval asks you to say why. Anybody on the timecards who is not on the register is listed here too, because they are paid no tronc until they are added. Lay down the periods from the calendar on the list of periods adds every period the calendar has up to today, and pressing it twice adds nothing twice.
    Against what BrightPay paid: once a period is approved, drop BrightPay's export for the run. Each person's tronc is matched to the approval on their works number, to the penny; anybody paid differently, not paid, or paid without being approved is listed with both figures. If it does not match, Mark paid asks why it is right to.
    Running alongside the workbook. While the client still runs its own workbook, bring each period's workbook in as well: the period then shows Against the client's workbook, person by person, and any difference with both figures. Once periods match to the penny the scheme asks for a cut-over date; set it under Edit the scheme, and from then on the board is the record and a workbook period after it is not loaded.
    Statements for staff: once a period is approved, anybody on it can be sent a statement of how their tronc was worked out, written from the approved figures; Email every statement sends them all at once and skips anybody already sent theirs. Monthly report for the client sets out the month's pots by site, what was paid, any shortfall, starters written to and whether each period was paid by its deadline, to email to the client contact. Both are kept with what they said.
  • Tronc calendar shows which monthly payslip each period lands in. One payslip a year carries three fortnightly periods; that is the month a salaried person's tronc looks high.
  • Tronc rules is the scheme's written rules, built from its settings so the document and the arithmetic cannot disagree. It says Draft and lists what is still to confirm until you record it as issued. Read and print opens it on its own to print.
  • Starter letters lists everybody who started in the last 90 days, or is still to start, without a letter. Preview shows exactly what they will receive. A letter is not sent if their record leaves one of its blanks empty, such as their promised rate or the employer contact. If mail is not available the letter is handed back to send by hand, and Record as sent by hand keeps what it said. You can change the letter for a scheme and go back to the standard one at any time. No letter goes out, by email or by hand, until an administrator has pressed Approve the wording for the scheme; changing the letter asks for approval again.

Open a client and its Tronc section shows each scheme, its latest period and what needs attention. Open a payroll run and Tronc paid in this run shows any period linked to it. Nora can say where each scheme stands, but never what one person was paid.

Every period has a deadline: the last day of the month after the month it starts in, because the law says tips are paid by the end of the month after the customer paid them. Not paid within a week of it is amber on Home, past it is red. Whether NICs are due turns on who decides the split: only an independent troncmaster deciding it is free of Class 1 NICs.

Cases: NMW checks, enquiries and consultations

A run is an obligation that comes round every period. A case is an episode: an NMW check, an HMRC minimum wage enquiry, a compliance check, a penalty, a status question; or, on the tronc side, a staff consultation on the tipping policy, a worker's request for the tipping record, a complaint, a tribunal claim or an HMRC review of a scheme. Payroll cases is under Payroll in the sidebar; Cases and consultations is under Tronc. They work the same way.

  • New case asks for the client, the kind, the subject and a title. A tronc case can be tied to one of the client's schemes. Every subject is a heading along the top, with how many are open under it.
  • Correspondence is the record: every letter, email, request and decision, oldest first, with which way it went. When you record one, the case moves to whoever has the ball next (something arriving is ours to act on, something we send is with whoever we sent it to), and you can change that before saving.
  • Dates come from the letters, never from the board. If HMRC writes "respond by", put that date on the letter. A consultation's closing date goes on the event that opens it. A case with no such date has no deadline, and is never shown as overdue for want of one.
  • The open date is the latest one nothing has answered. Only a reply to whoever set it, or a decision, answers it: a note to the client does not answer HMRC, and one worker's reply does not close a consultation.
  • Overdue is a reply we owe that is late. To chase is a date we gave somebody else that has passed: the client's figures, or a consultation that has closed and now needs a decision. Gone quiet is nothing recorded for 30 days, which is how enquiries are lost.
  • When a worker's written request for the tipping record is recorded, the four-week date the law sets is filled in for you. Change it if the letter says otherwise.
  • How to run it is the firm's steps for that kind of case: how to run an NMW check, answer an HMRC enquiry, run a consultation, answer an information request. Nora knows the same steps.
  • NMW arrears, on a minimum wage case, works out what is owed: each worker's shortfall, uplifted to today's rate where it is higher, and HMRC's likely penalty (200% of the arrears, capped at £20,000 a worker, at least £100, halved if paid within 14 days). You type the rates; the board keeps no table of them. Put the arrears on the case saves the total and the number of workers. Use a reference such as Worker 1, never a name.
  • A client's drawer lists their open cases in each book you have the screen for, with the next move and an Open button, how many are closed, and New case for this client, which starts the form with the client chosen. Tronc cases appear only for a client marked Tronc or one that already has a case.
  • From a ticket. On an OpsDesk ticket in the Tickets inbox, Open a payroll case starts the same form with the client the ticket is counted against and the ticket's subject as the title; change either before saving. The case keeps a link to the ticket and says From OpsDesk # and its number, which opens the ticket in the inbox again, and the ticket's details list the cases opened from it. The ticket sets no date on the case: record the letters as usual. A ticket marked a complaint in OpsDesk says so above the cases, and the button reads Open a payroll case for this complaint, with the title starting Complaint:.
  • Close asks how it ended. A closed case can be reopened. A case with anything on its record cannot be deleted, only closed; one opened by mistake with nothing on it can.
A case is in your scope when its client is. Payroll cases is a screen of its own that an administrator can switch on or off; Cases and consultations goes with the Tronc screen. Anything going to HMRC, a tribunal or a client in writing on a contested point is reviewed by a qualified adviser first.

CIP: why we were late, and what we do about it

The board tells you what is late today. The CIP tab tells you why things were late, so the same thing stops happening. It has six views.

  • Overview is the short list of what to work on, worst first: runs that slipped with no cause recorded, runs paid late, the commonest cause and whether anything answers it, clients with a delay more than once, and what the tickets are saying. Paid late and runs with a delay are counted apart.
  • Root causes lists every run with a delay or paid late in the window, paid-late runs first. Only people being paid after the pay date is paid late. A step before pay day (inputs, client approval, funds requested) ticked after its deadline, or still not done after it, is a delay: a run can have one and still be paid on time. RTI, pension, journal and sign-off are on Compliance, not here. Pick why, or press the suggestion, and Save. One cause per run, read off the first step that slipped: inputs three days late make approval, funding and pay day late too, and that is one failure, not four. The board records some by itself. Where inputs slipped first and a chaser went out, it records client inputs late; where the client sent amends back, client changed inputs after the draft; where both apply, the inputs. It marks these Auto (chaser evidence), every morning, back to September 2026, and never touches a cause a lead has saved. Save one to confirm it, or pick another and say why (that is counted in Overrides); an automatic cause cannot be cleared, because it would be recorded again. Anything the board cannot prove stays uncoded and on your Home list.
  • Ticket insight reads the payroll tickets by theme (pensions, leavers, pay wrong, a client asking whether the payroll is done and so on) using a fixed keyword rule shown at the bottom of the view. Telling clients before they ask counts, for the clients switched on for payslip updates, their tickets themed Is it done? Status chasing per run over the same length of time before and after each was switched on (at most 90 days each side). Fewer than three runs on a side is not measured yet. Satisfaction against how the payroll went groups the OpsDesk satisfaction surveys clients answered on tickets raised in the window by how that client's runs went in the same window: clean, delayed but paid on time, or paid late (a client is placed by its worst run). Each group shows its satisfied rate and how many answers it is over; fewer than five answers is not measured. It can show whether clients whose payroll went wrong rate us lower; it cannot say why, or anything about the clients who did not answer. Questions clients keep asking lists, per client, each theme it raised three or more times in the window (the top three), with a suggested fix picked by the theme: agree a contact and a standing update for a client asking where things are, fix it at onboarding for starters, leavers, pensions, bank details and portal access, write it in the client's SOP for their own rules (hours, holiday, tronc, statutory pay, tax codes, year end), and look at our process for pay wrong or HMRC. The rule is shown under the list. Raise an action opens a new action on the plan with the client, theme and fix filled in; nothing is raised until you save it. It flags a theme rising on the window before, a client raising three or more, a client both late on the board and raising tickets, and anything open more than 30 days. A ticket that names a client in its subject or body is tagged to that client by itself every fifteen minutes, marked matched on the Tickets tab; the rest are tagged by hand there, or the client figures read low. Picking another client corrects a match, and picking Unallocated means it is never matched again. The same view is on Tickets > Insight, with the same window. System notifications are not tickets. Mail a system sends to payroll@ (Modulr's approvals notifications, HMRC's successful receipt of an online submission, NEST and Stream notices) is left out of every ticket figure on the board: the themes and signals here, the scorecards, rework on Profitability, days to close, the questions clients keep asking, satisfaction, the ticket tasks on Home, and what Nora reads. Each of those says how many it left out ("5 system notifications, not counted"), and Left out as system notifications, under the theme rule, lists every sender, the subject it must have and why. A mail is matched on who sent it and its subject, never on what the email says. A subject saying something went wrong (unsuccessful, failed, rejected, overdue, action required and the like) is never left out, so HMRC's unsuccessful submission is always a ticket. The OpsDesk inbox still shows them, marked System notification.
  • Ideas is where anyone who can edit puts forward a better way. An administrator answers every one: accepted becomes an action, declined says why.
  • Actions is the plan. Each action needs an owner, a date and a line on how we will know it worked. Done needs an outcome and dropped needs a reason, so the plan stays a record of what was tried.
  • Overrides counts every place somebody set aside what the board or the tronc engine worked out: a colour pinned, a deadline or pay date moved, a tronc guarantee typed in, a tronc period approved with checks for review, an automatic cause a lead changed. It is shown per 100 runs, by kind, lead and client, with whether a reason was given. An override is not wrong; three on one client in the window is flagged, because that is a rule the work does not fit.
Nothing late in a window shows as not measured, never as 100% on time. The figures are worked out from the board's own ticks, the same way every time.

Team: who carries what

Team, under Payroll in the sidebar, is the portfolio by person. Each row is one payroll lead: their live schedules, employees, payslips a month, their share of the team's load, the mix of weekly, fortnightly, four-weekly and monthly payrolls, and how many runs they have open, overdue and at risk. Clients still onboarding are shown beside the name, not counted as live.

Balance compares each person with the team average. Heavy is 125% of the average or more, Light 75% or less, anything between is Even. The load is the workload index if you have the Enterprise screen, and payslips a month if you do not; the screen says which. Somebody with an account and nothing on their book is listed as Light, because they are the first place to put the next client. Schedules with no lead are a row of their own, at the foot, never part of the average.

Runs by pay week counts every run paid in each of the next few weeks (four by default, up to twelve), done or not, with how many are still open and how many are overdue. Earlier is work still open from before this week.

A schedule sits with the client's lead. A run sits with the run's own lead, because that is who sees it, so when somebody covers a run on a colleague's client it shows on the cover's row and says whose client it is. Click a person for their schedules, with the next run still to do on each, and their runs; a client or a run opens its drawer. If your account is scoped to your own schedules, Team is your own portfolio. To move work, use Admin › Clients and workload.

Planning a handover

Team › Plan a handover forecasts what happens when somebody's schedules move: a leaver, long leave or a rebalance. Pick whose schedules and the leaving date, then tick who takes them. One name moves the whole book onto that person; several spreads it, heaviest schedule first to whoever is lightest at the time. Any schedule can then be sent somewhere else from its drop-down, or to New starter for somebody not yet here.

Before and after shows each person's schedules, load and balance today and after, the leaver left out of the average because they are gone. Pay days per week, after counts the pay days each person carries from the week of the leaving date, worked out from every schedule's pay day rule, with the change from today in brackets. The handover timetable lists each schedule: the runs the receiver can mirror (sit beside the leaver on) before the leaving date, and the first run they do alone. Marked on each row: Handed over cold when no pay day falls before the date, Fewer to mirror when there are fewer than you asked for, No pay dates when a weekly or fortnightly schedule has no seed pay date, and Not placed when nobody takes it.

Nothing moves while you plan. Save plan keeps it for anybody who sees the whole book; Download plan gives a spreadsheet; Drop this plan keeps it on the list as dropped. Apply the moves now uses the same reassignment as Admin: the schedules and their open runs move straight away, so press it on the leaving date, not before, or the mirroring ends early. New starter moves and anything not placed are left where they are. Planning needs an account that sees the whole book, because it is about everybody's load.

The workload index

Every complexity input on a client exists to produce one number:

WI = (employees ÷ 25) × frequency score × adjusted complexity

Frequency scores 4 weekly, 3 fortnightly, 2 four-weekly, 1 monthly. Adjusted complexity is the base rating of 1–3 plus a loading for each thing that makes the work harder: tronc, client-led funding, hypercare, a tight SLA, a complex or multi-level approval, high comms, a salary-sacrifice pension, and no rota system or hours by spreadsheet.

Open any client and the index is shown with every loading that went into it, so it can always be explained. Tiers are High from 20, Med-High from 10, Med-Low from 5, Low below.

Enterprise › Workload is what it is for: what the book weighs, how it splits by tier and by payroll lead, the heaviest schedules, and fee per WI against the book average — which is where a pricing conversation starts.

Anything missing on a client — no complexity rating, no headcount, no rota system — makes its index read low, which hides work rather than inventing it. Those clients are listed at the foot of Enterprise › Workload. Filling them in is the single most useful five minutes anybody can spend in here.

Scorecards and profitability

Both sit under Firm performance, beside Enterprise, and come with it: whoever has the Enterprise screen has these two as well. They are built the way Client Operations builds its own client scorecards and profitability, but from what this board already records rather than from a sheet somebody fills in.

Scorecards

One card per client, with the thing to do first at the top. Eight measures, over the window you pick:

  • Paid on time: worked out from paid late only, the same as CIP: people paid after the pay date. Any run paid late needs attention. A run held up before pay day but still paid on time is a delay, shown apart.
  • Why runs slipped: the causes recorded on CIP, by the board from its own evidence or by a lead. Never worse than worth a look; a run with no cause is worth a look, because nobody can yet say whose problem it is.
  • Our delays: runs held up at a step of ours before pay day (the draft, the funding request). Two or more needs attention.
  • Our accuracy: finished runs corrected for our mistake after the client approved.
  • Client inputs: finished runs where the inputs were late, chased or amended by the client, or a client step was done after its deadline. At most worth a look: a high figure is a conversation with the client, not more effort from us, and the client's delays alone never make a card say needs attention.
  • Tickets: tickets tagged to the client, per 100 payslips, so a big client is not marked down for being big. An open ticket over 30 days old is worth a look.
  • Days to close: the median days from raised to closed over the client's tickets closed in the window. Fewer than three closed is not measured. A median of five days or more is worth a look, never worse, because a ticket can be waiting on the client's reply. Order the cards by Slowest to close tickets to find them.
  • Margin: Profitability's figure, below.
  • Touches and rework: how many times people put their hands on each payroll, and how much of it was doing something again. A touch is a person's own tick, untick or edit on the run (not the schedule's, the leaver tidy's, the HMRC mailbox's or the client's form, and not a run being made or archived), a chaser or reminder sent, or a ticket the client raised between the period start and sign-off. Rework is unticks, redrafts, amends and pre-draft checks overridden or exports taken off, per 100 runs. It does not change the grade. A run from before the board logged who did what is not measured and shows a dash, never nought. A table under the cards gives the same by payroll lead.

The card's grade is its worst measure, never an average. A measure with nothing in the window is not measured, never in order. Someone who sees only their own schedules sees their own cards and no margins.

Profitability

Each client's revenue against four costs, which an administrator sets once at the foot of the screen: the payroll team's monthly cost, software per payslip, the office recharge, and the cost of an hour with how long a ticket and a late run take.

Revenue is what Xero invoiced on the Payroll and Tronc lines over the complete months you pick, averaged to a month. It is read from Client Operations, which already holds the firm's Xero invoices, Timely's hours and Employment Hero's teams. An invoice is placed on a client here only where a name, the client code or the fee group spells it exactly; an invoice to a client with several schedules is shared across them by the fee each carries. Where Xero invoiced nothing, the fee recorded here stands in, marked fee, and the Fee here column sits beside Revenue so the two can be compared.

The team cost is shared by Timely hours: each client takes the share of the Payroll team's client time logged against it, the team being whoever Employment Hero puts in the Payroll team. The firm's own time is in nobody's share, and time on a Timely client not yet matched is cost that reaches no client, shown on its own. You can switch to sharing by workload index instead. Then the time a client's own tickets and late runs took is charged to that client first, and the rest is shared by workload index. Either way the team cost is moved, never added on top. The rework line says how much of it came from tickets and how much from runs with a delay, and hovering a client's rework figure says its tickets' part.

From Xero, Timely and Employment Hero lists what the names could not decide: Xero customers and Timely clients on no client here, ones more than one client answers to, and invoices to a client who is no longer live. An administrator answers each once, with a client or "not a payroll client here", and can take the answer back.

The list is worst margin first. A client with no revenue at all is listed apart as work we carry for nothing, and the book's total is shown before and after it. The figure after it, against the budget, is also the Payroll profitability line on Enterprise › KPIs. Profitability is only shown to an account that sees the whole book, because the team cost is shared across everybody's clients.

A cost nobody has entered is left blank, and every figure that needs it says so. It is never worked out as if it were nought: a contribution with no team cost in it would read as pure profit.

Trends

The history a calendar month at a time, over 6, 12 or 24 months: tickets raised and closed and how long they took to close, runs due, paid late and runs with a delay as separate series, runs delayed by the client's inputs, how many days late, and whether the delay was ours or theirs. Every chart has its figures in the table beneath it.

A measure is getting worse or getting better when the last three complete months differ from the three before by at least a quarter and by at least three (five points for paid on time). Anything smaller is steady: five tickets becoming seven is not a story. The current month is drawn lighter and never decides a trend, because part of a month always reads as fewer tickets. Ticket subjects that are rising are named, and the whole book also sees paid on time by lead. Touches and rework are shown a month at a time and by lead, counted as on the scorecards; a month with no run measured is a dash. Every scorecard carries its own six months of runs with a delay and tickets with the same verdict, and the cards can be filtered by it.

Reports

The delivery and timeliness report puts one month on one page, the way the WSOP compliance screens report the accounts book. Pick the month (the last complete one opens first). It starts with what to take from the month, worst first, then the headline figures against the month before (paid on time, and paid late), a block for runs with a delay and how many of those were still paid on time, a ring for every step against its deadline, six months of history, every payroll lead, every client with a delay or paid late (one in two of the last three months is flagged as a pattern), why runs slipped, and the month's tickets.

A run belongs to the month it was paid in. The step rings judge every step on its own: ticked by the end of its deadline day is on time, after it or still not done is late. A step the client has automated, or approved with amends, has no time to judge and is left out. A run is paid late, or paid on time with a delay, or neither, and never two of them. Paid late is judged on the day people were actually paid, which a lead confirms (Paid on in the run, beside Paid): until then it is the day the Paid step was ticked, said to be unconfirmed, and the report says only that the Paid step was recorded after pay day. A month with nothing due is not measured, and a run paid after its pay date makes the month need attention whatever the percentage. A month still running says so on every figure.

Confirming when people were paid. Ticking Paid asks for the day, defaulting to the pay date: change it only if payment really was late. On the board, Paid date to confirm filters to the runs whose Paid step was ticked after pay day and nobody has said when people were paid; select them and press Paid on each pay date (or Paid on a date). Every change is in the run's history, and changing it after sign-off is counted in CIP > Overrides.

Export PDF prints the report as it is on screen, landscape, with a line saying who took it, when and for whose runs. Email sends the same report as text from the payroll mailbox, to williamsstanley.co addresses only: it holds several clients' positions, so it never goes to a client. If mail is not set up, the report is handed back to copy and send by hand.

Clients, notes and quirks

The unit of work is a schedule, not a company: a client running a weekly and a monthly payroll is two rows, which is why the same name can appear twice.

Notes

Click any client for their note feed — "they send the tronc separately, always late". A pinned note appears on every one of their runs and on the import screen. That is the point: whoever does September should not have to rediscover what August learned.

Contacts by role

On Edit client, under the contact email, Contacts by role is a short list of the client's people: an address, a name, and which of four jobs each does: Inputs (sends the hours and changes), Approval, Funding and Updates (told when payslips are out). Add a contact, tick their roles and Save client. Nothing changes for a client until somebody adds one: with nobody named for a job, the contact email is used for it, as before.

  • On Templates, Compose puts the right person in To by the template: an inputs reminder or chaser to Inputs, an approval chaser to Approval, a funding chaser to Funding, and the payslips update to Updates. It says whose role it is; you can still change To before you send.
  • A ticket from any contact, or from a company domain one of them uses, counts against the client. Never a resemblance: the address or the domain must be exactly the same, and a public one such as gmail.com counts only for that exact address.
  • The OpsDesk thread offered on Compose can be any contact's own open ticket.
  • Once somebody is named for Inputs, only their emails are offered as evidence that the inputs may have arrived.
  • Every address is checked before anything is saved; one that is not a single email address, the same address twice, or a role off the list refuses the whole list. Each change is on the account log.

Steps a client's arrangements take care of

Three steps can be marked as automated for a client, on the client itself: Funding requested (a direct debit, or client-led funding with nothing to ask for), Pension submitted (no scheme, or the client submits it) and Journal posted (the client keeps their own books). An automated step shows a cog on every run and never waits on a tick.

Nothing else can be. Inputs and approval are the client's decisions, the draft and sign-off are our work, and payment and RTI are what say people were paid and HMRC was told. Marking any of those automated would let a run go green without the work being done.

Steps only this client needs

Split the tronc, check the director's manual pay — set them on the client and they are copied onto each of their runs, shown as a separate checklist and as a count on the board. Adding one now also puts it on the runs already open. They never change a run's colour; the nine built-in steps do that.

Portal invites. In the same place, Track portal invites on each run adds one step to every run of the client: Portal invites sent to this period's starters. In the run's drawer it shows how many starters are in that run's own import (people in its starter details file whose start date is in the period; anybody with no start date is counted and said). With no import on the run, no starter details file in it, or its rows removed under the keeping rule, it says the starters are not counted here, never nought: check BrightPay. Like any client step it never changes the run's colour; you tick it once the invites are sent. Portal message to forward opens Templates on Activating your employee portal, a message the client can pass to its starters on how to activate the portal; edit its wording on Templates once and it stays.

Pension duties

Every employer with a workplace pension re-enrols its staff every three years, and makes a declaration of compliance to The Pensions Regulator within five months of each re-enrolment date (and of the staging date, the first time). On Edit client, under the pension provider, put the staging date, the re-enrolment date (the last one chosen, or the first), the date of the last declaration of compliance, and tick Pension provider login confirmed once we can sign in to the provider ourselves.

The board works the rest out and shows its arithmetic, in the client's drawer under Pension duties and under the dates on Edit client: the next re-enrolment is the stated date plus three years (as many times as it takes to pass today), and the declaration is due five months after the latest re-enrolment or staging date. A declaration dated on or after that date counts as made. With only a staging date, the third anniversary is used and said to be an estimate: the employer picks the real date near it, so put it in once chosen. The same goes for a re-enrolment already gone that nobody typed (the stated one plus three years): a declaration counted from it is said to be an estimate until the date chosen is put in. Nothing is guessed: with no dates at all the client is not known, which is what Compliance shows. A client whose pension type is None has no duty. An unconfirmed provider login is one of the things worth filling in at onboarding; it never stops a client going live.

Year end

Each client's drawer has a Year end checklist for a tax year (6 April to 5 April). It shows the year still being finished until its P11Ds are due on 6 July, then the year now running; pick another year in the list. The steps and their dates are worked out, not typed:

  • Final FPS of the tax year filed, due on the pay date of the last run in the tax year. Once that run is ticked as filed on the board it counts as done by itself. With no run on the board yet, the date comes from the client's pay days and says so.
  • Week 53 checked, only where the client's pay days give a week 53 (54 for fortnightly, 56 for four-weekly), due on that pay date. A weekly or fortnightly client with no seed pay date reads not known.
  • Final EPS sent, where needed, by 19 April. If none was needed, tick it and say so in the note.
  • P60s issued by 31 May.
  • P11D and P11D(b) filed by 6 July, only where the client has benefits. Answer Benefits for P11Ds (yes, no, or not known) in the same place; until it is answered the step reads not known.

Tick each step once it is done; the time is the board's own, and a tick on a step already ticked changes nothing. A step done after its date says so. Nothing waits on the checklist: no run, status or tick is held up by it. From 1 March Home lists the next step for each of your clients, and Compliance measures the year from 2026-27, the first year the checklist existed.

A page the client can check: the cycle status link

Instead of answering "have you got our hours?" or "when do you need the money?" by email, give the client a private link. In the client's drawer, under Cycle status link, press Make a link (with an optional last day it works) and copy the address it shows. It is shown only once: the board keeps a scrambled copy, so it cannot show it again. To send it again, make a new one, which stops the old one. Stop it closes the page at once.

The page needs no sign-in and shows only this schedule's current payroll, exactly as the board has it: inputs due and received, the draft sent and approval due, funds needed by the cut-off with the wages to fund once the run carries a net figure, paid, RTI filed, and PAYE due on the 22nd with its amount once known. The board's colour is shown as it is, amber included, in words from the dates. Nothing anybody typed (notes, a hold reason) reaches it, nor anything about an employee, nor any other schedule. A figure nobody has entered says not known yet, never £0.00. A link that has been stopped, has run out, or never existed shows the same words, so nobody can find out which links exist. Making and stopping need a role that can change the board, and both are on the account log.

Approving the draft from the page is off for every client until you tick Let the client approve the draft from their cycle status link in Edit client. Then, while the draft is with them and Approved is not ticked, the page offers Approve the draft or I have changes with a box for what to change. Their answer changes nothing on the board: the run drawer shows it under From the cycle status link (their changes in their words) and your Home list says Client approved through the link: tick Approved. You press Tick Approved yourself; the run's history says it was ticked from their answer, and if they asked for changes after approving, the tick from that approval is refused. Their words are removed with the keeping time for dropped files, and never reach Nora or Claude.

Who can do and see what

Three separate settings on every account: what it may change, whose work it may see, and which screens it is shown.

RoleCan change
AdministratorEverything, plus managing people, import layouts and housekeeping.
EditorThe board, the clients, imports and HMRC. Everything except managing people and deleting.
ViewerNothing. Reads everything it can see, including the exports.

What you can see. An account is either set to see the whole book, or scoped to one payroll lead's schedules. Scoped, you see your own runs, clients, imports, emails sent, RTI exceptions and tickets, and nobody else's. Tickets nobody has tagged to a client yet are shown to everyone, because somebody has to pick them up. The server enforces this on every read and every write, not just the lists, so typing another client's number into a link gets the same refusal whether that client exists or not.

Which screens you have. An administrator switches each screen on or off per person: Edit on their row under Admin > People. Every screen is on unless somebody switches it off. Home is always there, because it holds your own tasks, and Admin goes with being an administrator. A screen switched off is gone from your tabs, and Imports, Reconciliations, Tronc, Enterprise, SOPs, Tickets and CIP also refuse on the server, so Nora cannot read them for you either. Activity, the Lifecycle, the Calendar, Clients, Compliance and Templates only lose their tab, because Home and the run drawer read the same runs and clients. Your Tasks leave off tickets and CIP items for a screen you do not have, and say so. Switching a screen off signs that person out, so it is gone the next time they open the app. The role still decides what you may change on the screens you have.

Jobs. Adding somebody starts from the job they do, which fills in the role, what they see and their screens. Any of it can then be changed before the account is made.

JobSets
Payroll administratorEditor, their own schedules, every screen but Enterprise. Needs their payroll lead name.
Payroll managerEditor, the whole book, every screen.
Read-onlyViewer, the whole book, without Imports, Reconciliations, Payroll cases, Tronc, Enterprise or Templates.
AdministratorAdministrator, the whole book, every screen.

Enterprise is workload, pricing and fees, so only a manager or an administrator is given it by default. The people list shows which job each account's settings match, or Custom when they match none. A job is a starting point, not a rule: nothing is changed on an account that already exists.

Moving a client to another lead needs an account that sees the whole book, from Admin > Clients and workload (Who carries what) or by changing the lead on the client. Either way the client's open runs go with it and signed-off runs keep whoever did them, and the new lead has to be the lead name on an active account, so the work cannot go to somebody nobody signs in as. A scoped account cannot give its own clients or runs away, and a client it adds carries its own lead name. Changing who runs a single run follows the same rule.

Forgotten your password? emails you a link that works once and lasts an hour. If mail is not set up, it tells the administrators instead, and one of them hands you a one-time password which you replace when you sign in.

Five wrong passwords for one address inside fifteen minutes locks that address out for a while. A correct password clears the count, so one fumbled attempt never counts against you later.

Inside Client Operations, the board signs you in with your CIP account, but only if you also have an account here with the same address. Being on CIP does not by itself let anybody in.

Where it is switched on, the sign-in card also offers Sign in with Microsoft. It uses your Williams Stanley Microsoft account, and the same rule applies: you need an account here with the same address, and being known to Microsoft does not by itself let anybody in.

The Admin screen

For administrators. It is laid out the way WSOP's is. The figures along the top are the things an administrator comes here to deal with, and each one opens the tab that deals with it.

TabWhat it is for
PeopleEverybody with an account. Search by name, address or lead, and filter by job, role, which screens they can open (who has Payroll cases, say) or status (never signed in, not seen for 90 days, one-time password not used, waiting for a password, and so on). Edit on a row opens that person: their name, what they may change, what they see, their screens (grouped as the sidebar is, and saying when one switch opens several sidebar lines) a job to start from, and whether they may change the board through Claude (editors and administrators only; they allow it again in Claude before it takes effect), with one Save. It says in a sentence what the choices add up to before you save, and warns when a change will sign them out. Reset password and Remove access are there too. If they carry schedules it says how many and offers to move them before their access goes, because removing access does not move the work.
Add someoneA new account, starting from the job they do. Until a job is picked it would make a read-only account that sees Home and nothing else. The one-time password appears once, at the top of the screen.
Account logEvery sign-in, failure, reset and change to somebody's access, in words. Search it, narrow it to one kind of event, tap a name for only that person, or download the whole log as a spreadsheet for an audit or a leaver review.
Weekly briefingWho has confirmed each week's briefing on what is new, week by week, so a change the team needs to know about is known to have reached them.
Health checkWhat needs a decision: accounts not used for 90 days, a one-time password that expired unused, a password request waiting more than three days, somebody set to their own schedules with no lead name, a lead whose schedules nobody can see, only one administrator, an address outside the firm, and HMRC's receipts going quiet: no FPS receipt recorded for three working days while five or more runs were ticked Paid in them, which usually means the scenario that passes HMRC's confirmation emails to the board has stopped (Open the RTI receipts goes to Compliance > RTI). Each finding has a button to where it is put right. It also says who holds the keys (administrators, who can change the whole book, who can see fees and margins, who can open Enterprise, and who can see what employees are paid through Imports, Reconciliations, Tronc or Payroll cases) and how every screen is controlled. Nothing on it changes an account by itself. Tidy up only removes what nobody could be relying on: expired sessions, sessions of closed accounts, old failed sign-ins and test accounts left behind, and the rows of dropped files whose run was signed off longer ago than the keeping time (their records and counts stay). Files kept only because no run is tied to them are listed as a decision, never removed.
Clients and workloadWho carries what (moving schedules between leads) and COM coverage.
OnboardingIts own line in the sidebar under Clients (administrators only), and the Clients to finish onboarding figure on the Admin screen. A card for every client coming on: what stops it going live, what is worth filling in, and its BrightPay migration checklist, eight steps ticked in place as they are done, with the next one to do marked. The employee step is also done by an employee details file marked imported in Imports. The figures across the top filter the cards (blocked, ready, migration not finished), and live schedules missing something are listed under them. Go live asks first while any migration step is open.
OffboardingIts own line in the sidebar under Clients beside Onboarding, and the Clients offboarding figure on the Admin screen. A card for every client under notice: its final pay date, what is left on the board (no final pay date, runs after it to archive, runs still to sign off) and its exit checklist, ticked in place, the final run and final FPS found on the board by themselves. Mark exited is offered once the final pay date has passed and every run up to it is signed off, and asks first while any checklist step is open.
Owner checkIts own line in the sidebar under Clients, for administrators who see the whole book. Every client where the payroll owner differs between the board's lead and HubSpot's Payroll Person (read from WSOP, so it needs WSOP's database address under Integrations): different people, no one in HubSpot, no lead here, a schedule split between leads, a HubSpot person with no account here, a company in only one of the two. A company is matched by its client code, then by its name exactly as the register reduces it (Ltd, & and spacing aside), never by a near spelling; two matches are left for you. OpsDesk is not compared, because its link to the board does not say who owns a client, and the page says so. It changes nothing: put the board's lead right with Move their schedules or Edit client, and HubSpot's in HubSpot. The figures across the top filter the list.
Import set-upHow long dropped files are kept after their run is signed off (35 to 730 days, 90 by default), the switch for the starter and leaver form (off until the firm decides, and only once the keeping time is saved), the BrightPay import layouts and the saved column mappings.
IntegrationsWhat the board is paired with. Client Operations (WSOP and WSCIP) is set here: WSOP's database address, which the SOPs tab reads, and the sign-on keys and address that let people sign on inside Client Operations. A secret is never shown again once saved; Test the connection says whether each part works and whether your own WSOP account was found. Everything else the board connects to is listed with whether it is set on the deployment. Modulr is here too, read only and off until an API key and secret are entered: once on, Check paid runs against Modulr now (and the same check every morning) records when people were paid, from the bank, on a run somebody ticked Paid, only where Modulr's processed payments for the client's code add up to the run's net pay to the penny. It never ticks anything and never changes a date a lead entered; where the bank disagrees with one, it says so. This has not yet been tried against the firm's real Modulr account.
SystemHow email is being sent, and Update the database.

A week on the board

Monday morning

Start on Home: My tasks, with Overdue first, then Due in the next 7 days. Then the board on Activity, where the strip along the top is a set of counts and every one is a filter. Click Overdue to see only those. Then the Payroll Calendar for what lands this week.

Through the week

Filter to yourself, select what you have done, tick the step. Chase what needs chasing and set the chased flag so nobody chases twice.

After pay day

Pension, journal, sign-off. A run is not finished until it is signed off, and it goes red three working days after pay day if it is not — which is the only thing stopping close-out work from quietly never happening.

Once a month

HMRC by the 22nd, on Compliance › Payments to HMRC. Clear anything waiting under Compliance › RTI. Then Enterprise › Workload: fill in anything on the gap list, and look at the underpriced clients before the next fee conversation.

When something looks wrong

A run says overdue and I know it is fine

Something has not been ticked, or a date on the client is wrong. Open the run: the reason text names the step. If the client's deadline itself is wrong, fix it on the client and every future run is right too.

A client's pay dates are wrong

Check their pay day rule and, for weekly and fortnightly, their seed pay date. One wrong seed moves every pay date for that schedule.

A run has gone from the board

Signed-off runs whose pay date is before the start of the current month drop out of the default window. Change Pay dates — the Back windows and Everything reach as far as the board goes — or use the CSV export.

Somebody's index looks too low

Look at the gap list on Enterprise › Workload. A missing complexity rating or headcount scores as low, not as unknown.

Something is actually broken

Tell Tom. The run history and the access log record what happened and when, so nothing has to be reconstructed from memory. Check What has changed first: if it started this week, the cause is often listed there.

Asking Nora

Nora sits in the bottom-right corner of the board. She is the same Nora our clients meet on team-pay.co.uk, doing an internal job here: answering questions about this board, and advising on tronc, tips, the minimum wage and the cases you are running.

What she is good for

Things you would otherwise go and look up across three tabs. What is overdue. Why a particular run is red. What the COM says about a client's approval route. What is owed to HMRC on the 22nd. Which schedules look underpriced against their workload index. She reads the same figures the screen shows, so she cannot tell you something different from the tab next to her.

Advice on tronc and the minimum wage

Ask her the questions you would ask a senior colleague: is this client's tronc free of NICs, what does the tips law require of a written policy, how do we run a consultation, what does a worker's request for the tipping record oblige us to do, what counts towards minimum wage pay, how are arrears worked out. She answers in a set order: the answer, the rule it rests on (the tips Act and its Code of Practice, HMRC's guidance, the minimum wage law), how it applies to the client, what to do next, and what would change the answer. She can read a client's scheme and its open points, the cases and their correspondence, and the steps for each kind of case, and she can work out minimum wage arrears and the likely penalty from rates you give her.

She says plainly where the law is not settled (whether tronc counts towards holiday pay, for example) rather than picking a side, and she never quotes a minimum wage or tax rate from memory, because rates change every April. Anything contested that would go to HMRC, a tribunal or a client in writing, or that changes what somebody is paid, is reviewed by a qualified adviser before it goes; she will say so.

Your day, and the cases

Ask her what you should be doing and she gives you your runs, each reduced to its next step, and the cases that need something from you: a reply we owe that is late or due within a fortnight, a date the client or the workers missed, and a case nobody has touched for 30 days. They are the same items as My tasks on Home. Somebody who sees the whole board gets the same thing per lead.

The team, and why runs were late

Ask her who is carrying the most, whether the work is balanced, or who could take a new client, and she reads the Team screen: each lead's schedules, load, open and overdue runs, and whether they are heavy, even or light against the team's own average. Ask her why runs are late and she reads CIP: where delays start, the causes recorded and how much of it was ours to prevent, the clients and leads running late most often, and the open actions on the improvement plan. A late run with no cause recorded is said to have none, with the board's suggestions marked as suggestions; she will not pick a cause for you. Both follow the screens: without Team or CIP switched on for you, she cannot read them either.

Drafting replies to tickets

Ask her to draft a reply to a ticket ("draft a reply to ticket 41234", or "what do I say back to the latest ticket from this client") and she reads the whole ticket, checks what it asks against the board (the run, its stage and deadlines, what HMRC is owed, any open case), and writes a reply ready to paste into HubSpot, with a note underneath on what she checked and anything you need to confirm. You can also paste a client's email straight into the chat and ask for a reply: the box keeps its paragraphs (Enter sends, Shift and Enter starts a new line), and Copy under her answer takes the whole draft, line breaks and all. New conversation at the top of the panel starts again.

For an OpsDesk ticket she reads the same This payroll the inbox shows beside it: which client the ticket is counted against and that client's run (its stage, the pay day, whether the inputs, approval and funding request are in, what happens next and the pinned notes), and she says where the payroll is only from that. If the ticket is counted against no client, or the run is not one you can see on the board, she promises nothing about when and leaves it for you to confirm.

The five slowest questions. Tickets about tax codes, holiday pay, year end (P60s and P11Ds), tronc, and leavers and P45s take us longest to answer. Each now has a ready reply on Templates (Reply: tax code query, Reply: holiday pay query, Reply: P60, P11D and year end, Reply: tronc and tips query and Reply: leaver and P45), with the client and your name filled in and an [Insert ...] gap for each thing only you know, which the draft warns about before it goes. Edit the wording on Templates once and it stays. When you ask Nora to draft a reply to one of these, she first reads the client's own procedure (the SOP section for that topic) and the run beside the ticket, starts from that reply, and fills a gap only from what she read; a section nobody has written stays a gap rather than a guess. The same words are ready for OpsDesk's own reply templates, for the OpsDesk administrator to load.

She will not promise a date or an amount the board has not given her, admit fault, offer a refund or a credit, or quote a rate: where one of those belongs she leaves a marked gap for you to fill. Anything contested, such as a penalty, an underpayment or a complaint about us, gets a holding reply and a note that Danielle should see it first. She never sends anything: you read it, change what you want, and send it yourself. Before a ticket reaches her, any National Insurance number, bank details or date of birth in it is taken out.

Two things worth knowing

She sees exactly what you see. Every lookup she does runs as you. If a client is not one of your schedules, it is invisible to her too — she will say it may not exist or may not be yours, and suggest asking Danielle. She is not being coy: she genuinely cannot see it.

She cannot change anything. She has no way to tick a step, edit a client, reassign a run, file a submission, or send or close a ticket. Ask her to and she will tell you where to do it yourself. That is deliberate — a step ticked because a question was misread is worse than a question unanswered.

What happens to what you ask her

Nothing is kept. There is no transcript: the only thing recorded is a count of how many questions each account has asked today, which is there to stop a stuck browser tab running up a bill. Don't type an employee's personal details into her — she is told not to repeat them back, and the chat is not the place for them either way.

She is the same Nora our clients meet, but she knows different things

The Nora on team-pay.co.uk answers the public about the product. She has no way to see this board — different system, different database, no access to a single client of ours, and she is told plainly not to discuss how we run the bureau even if somebody insists they already know. The one in here has both: the board, and the same product answers the website gives, so if a client asks you what we charge or whether we do tronc, she can hand you the exact wording they would have got from the website.

She keeps the two apart and will tell you which is which. Ask her what to say to a client and she gives you the public line; if the answer needs something off the board in it, she will flag that part rather than hand you a sentence with another client's name in it. That last bit is worth remembering when you paste her answers into an email.

If a question needs too many lookups

She has a handful of lookups for each question. If she runs out, she answers from what she found and tells you what she could not check; a narrower question (one client, or one week) gets a fuller answer. If an answer is too long to finish, she says the end is missing rather than stopping as though it were complete.

If she says she is not switched on

Her API key is not set on the deployment. That is an administrator job, not something a reload will fix.

When to ignore her

When her answer turns on a fact she has not been given, she will say which fact and what she assumed; check it before you rely on the answer. For a contested point that goes out in writing, a leaver's final pay, a disputed tax code or an odd NI category, she will point you at Danielle, and she is right to. Her advice is a well-reasoned starting point, not a ruling on the client's obligation.

The board in Claude

The board can be added to Claude as a connector, for the firm's own people only. Once it is, Claude answers questions from the board as you, using the same lookups as Nora, and can sit beside Client Operations and WS Insights so one question can be answered across all three.

Connecting it

The quickest way is from the board: open the menu under your name, or press the + in the header, and choose Use the board in Claude (or the link under Nora on Home). It gives you the address with a Copy button, opens Claude's connector settings for you, and lists your own connections, with Disconnect Claude to end them.

In Claude, add a custom connector with this board's address followed by /mcp. Claude opens a page on the board: sign in if you are not already (in this browser, not only inside Client Operations), read what it says it can do, and press Allow. Only an active account on a williamsstanley.co address can connect, and that is checked on every question, so a closed account stops at once. Each connection is on the account log.

What it reads

Everything Nora can: your day, runs and their whole history (every change, every chaser sent this cycle and every note on the client), clients, HMRC, compliance, workload, tronc, cases, tickets, the firm's email templates, import batches, and tronc schemes and periods, and since 27 October 2026 your Tasks list, the reconciliation reports held for a client, the Enterprise screen (scorecards, profitability, trends and the monthly report), the Payroll KPIs and the firm's procedures. It sees exactly what your account sees, and a screen switched off for you is off in Claude too.

Ask it how the board works, and what it can see

Claude has this guide. Ask it anything about how the board works, for example "what does On hold mean?", "when is the funding cut-off?" or "how does tronc sign-off work?", and it answers in the guide's own words and says which section, so you can read the rest here. Ask it "what can you see?" and it reads your own account: your role and scope in plain words, which screens are on and off for you, which lookups will answer you and which will be refused and why, whether your connection may write notes and drafts or reads only, and the list of things it can never do on the board. Both are offered as routines too: How does the board work? and What can Claude see and do here?

An import is read the way the column suggestion reads it: each column's heading and the shape of its values (a National Insurance number reads as AA999999A), never a name, a number or a figure. Claude can tell you which columns are unmapped, which field each should be, and why a batch has errors, with the file and row to look at, but it cannot tell you who, and it cannot change the mapping: you do that on the Imports screen. That is on purpose: nothing from a client's file reaches a model.

Claude never changes a payroll

Claude can find, explain and draft. It cannot tick or untick a step, set a run's flags, move a date, change a figure, mark anything paid or filed with HMRC, or change how an import file is read. When something on a payroll needs doing it tells you exactly what and where, and you do it on the board, in your own name. That is deliberate: the person who ticks a step is the person who checked it, and a payroll is somebody's wages.

Two things it can write, if an administrator has switched on "may add client notes and write email drafts through Claude" for you on Admin > People (editors and administrators only), and you have removed and re-added the connector so the Allow page can tell you: a note on a client, and an email draft. Claude asks before writing either, and both are recorded in your name marked "via Claude".

Email drafts: Claude writes, you send

Ask Claude to chase the clients whose inputs are late and it writes one draft per client from the firm's own chaser, filled from the board. Nothing is sent. Each draft appears on Templates under Drafts to send and on your Home list. Open it, read it, change anything, and press Send email: the send goes out exactly as any other, ticks what its template ticks, and the draft is marked sent. Anything left unfilled ({{payDate}} and the like) is named, and Send asks before an email with a blank in it goes. Put aside a draft you do not want; it is kept on record.

Routines

The connector comes with the firm's recurring questions ready to run, listed under it in Claude:

  • Monday payroll stand-up: red now, due this week, waiting on clients, HMRC and cases, and the three decisions for today.
  • Chase missing inputs: every late or nearly late input, with a chaser drafted per client once you say yes.
  • Why were we late?: where each late run first slipped, who controlled it, and at most three actions.
  • Client health check: one client in the round, with Client Operations and WS Insights where added.
  • Check an import before it goes to BrightPay: every error explained, and a checklist of the mapping changes for you to make on the Imports screen.
  • PAYE due this month: every payment due by the 22nd, and any mismatch with what was paid.
  • Tronc period: ready to approve?: what stops or questions approval, what the sign-off note must cover, unconfirmed pots, and the legal deadline, as a checklist for the troncmaster.
  • Tronc scheme review: the scheme against the tips law and Code of Practice, with the actions.
  • Chase tronc pot figures: every period waiting on the client, and which button on the period to press.

Tronc

Claude reads a tronc period the way a troncmaster would want it summarised: the QA checks in their own words, which pots the employer has confirmed, whether the till and the client's form agree with the pot, where the request to the client stands, how the workbook's parallel run compares, and the legal deadline. It never sees a person's name or what they were paid, and when fewer than three people share a period it does not see the totals either, because then a total is somebody's pay. It never approves, reopens or pays a period: that is the troncmaster's decision, on the Tronc screen, in their name.

Asking across the firm's systems

With Client Operations (WSOP) and WS Insights added too, ask questions none of them can answer alone, for example: "Which clients were late on payroll this month, have open service issues in Client Operations, and are below margin?" or "For this client, show the last three payroll runs next to last week's trading". Claude matches a client by its code first, then by its company or name, and says when it is matching on a name. If two clients could be meant it asks rather than guessing, and a client one connector refuses you is not filled in from another.

What has changed

Every change to how the board behaves is written up here, newest first, in the same commit as the change itself. If something works differently from last week, this is where to look.

Loading…