Payroll Command Centre

Every priced client, fee per WI against what the book earns per WI overall — with a pill against the ones worth a look, so a pricing conversation starts with the right dozen without losing sight of the rest. Where one fee covers several schedules — several sites billed as one client, or a Monthly/Weekly pair — they are consolidated into one row, with the schedules that make it up underneath, rather than left to scatter across this list as several unrelated-looking fractions of what the group is really worth.

Four of these seven have a real data source in the Delivery Tracker — inputs chased, an amend's cause, and sign-off against its deadline — computed over the window below. The other three (Response time, Payroll profitability, Client satisfaction) need a query timestamp, a cost figure and a survey mechanism this board does not have yet, so they say so rather than showing a number that is not really there.

Every ticket raised with the payroll team, from HubSpot. The weekly report is a summary of these; this is all of them.

Click a row to see that client's tickets in Search.

Clients that are not live yet, plus any live one missing something that stops the app working — a live schedule with no pay day is the same problem wearing a different status. Blocking means no runs can be generated at all; the rest will work but make a number wrong, usually by making the workload index read low. Add a new client from the Clients tab — this is where an existing one gets checked over before it goes live.

Moving a schedule moves its open runs with it, so the new operator sees the work immediately. Signed-off runs deliberately keep the name of whoever did them — that is the record of who did the work, not an assignment.

How a client's payroll is actually run, written down once so somebody picking up a client they have never done does not have to ask. The timetable and the settings are derived from the client record rather than retyped — the written half is only the part the app cannot know. Biggest client first, because an unwritten COM for three hundred employees is a bigger hole than one for a single director.

The columns written into the files BrightPay is given. These start as a sensible guess — open your own BrightPay import once, correct the headers here to match it, and every import afterwards comes out right. Money goes out as plain numbers to two decimal places and dates day-first, whatever the headers say.

Every time somebody ticks “remember this mapping” on a dropped file, it lands here, and the same export next month arrives already mapped. Delete one if a client changes the shape of what they send.

Sign-ins, failures, password resets and account changes. Failed attempts record the address that was typed, never the password.

Clears out expired sessions and old failed sign-in attempts, and marks import drafts nobody has touched for a month as abandoned. Nothing anybody is using is removed, and no payroll data is touched.