Every Pay Query Starts With Someone Retyping the Hours
Why pay queries in a security company usually trace back to hours typed in more than once, and how to stop errors creeping in between shift and payroll.
By Michael Bryce · 16 November 2026 · 4 min read
Anyone who has run a security team knows the message. It arrives on a Friday or a Monday morning, usually short. "This isn't what I worked." Sometimes they are right, sometimes they are not, and either way you now have a conversation to have that nobody wanted.
I have come to think most of these queries have the same cause. It is rarely anyone being dishonest, and it is rarely the person who sent the message. It is the same set of hours being typed in more than once.
One shift, three typing jobs
Follow a single shift through a typical small security company. It starts on the rota, where someone typed the site, the start time and the finish time. It gets worked. Then the hours go onto a timesheet, a text, a clock-in record or a note on the back of something, depending on how the week went. Then someone types those hours into the payroll. Then, if the client is billed by the hour, someone types them again to build the invoice.
That is at least three places where one fact lives. Each is typed by a person, often tired, often at the end of a long week, often a different person each time. None of them has to be wrong by much. A twenty minute handover that was written down as fifteen. A shift that ran over because the relief was late and nobody updated anything. A swap that happened on a phone call.
Nobody sets out to get it wrong. The system just gives them three chances to.
The error is never where you look first
When a query lands, the instinct is to check the payroll. That is the last place the mistake was made, not the first. By the time hours reach the payroll they have already been through two or three hands.
The honest answer to "what did they actually work?" is often "let me find out". That is the problem. If you cannot answer it in a minute, you are not running on facts, you are running on whoever's version is most convincing.
It also costs more than the pound or two in dispute. The officer who gets short paid once and has to chase it does not forget. They remember who made them chase. Losing someone good over a clerical slip is a poor trade, and quietly overpaying to avoid the row is not a system either.
What I would want before anything else
I would not start with software. I would start with one rule: the hours that get paid and the hours that get billed come from the same record, and that record is made at the time, by the person who worked the shift.
Everything else follows from that. If the clock-in time and place is captured as it happens, there is nothing to retype and nothing to argue about. If the hours are only ever read, never copied, then the payroll and the invoice cannot disagree with each other, because they are looking at the same thing.
That does not remove judgement. Someone still has to decide whether to pay the fifteen minutes of handover, or whether a client will accept a late relief on the bill. Those are management calls and they should stay management calls. What you take away is the clerical layer underneath them, where mistakes happen without anyone choosing them.
Where the client fits in
The same applies on the billing side. A client who disputes an invoice is usually asking the same question as your officer, just from the other end: how do you know? If your answer is a spreadsheet someone built last Thursday, that is a weak position. If it is the record of when each person started and finished on that site, it is a short conversation.
Month end is rarely anyone's favourite day. Most of the dread comes from not trusting the numbers until they have been checked twice. Fixing that is worth more than any clever rate negotiation, because it gives you your evenings back and takes the sting out of the awkward calls.
What TacDesk does here
This is the part of the job I built TacDesk to take off people. Shifts are clocked in and out in the app, and the hours are recorded as they are worked, so the same record can feed the payroll side and invoicing instead of being typed again. Which plan includes which integration varies, and the pricing page is the place to check it, not my memory. The Xero payroll integration, for instance, is included on one plan and an add-on on others.
None of that replaces a decent rota either. If the hours are right at the end, it is because the plan at the start was clear. I have written separately about building scheduling that holds up, and the two go together.
A short test for your own business
Pick one officer and one shift from last month. See how long it takes you to answer three things, using only what you have on file: when they started, when they finished, and what you paid and billed for it.
If you can answer all three in a couple of minutes and the numbers agree, you are in better shape than most. If you have to ring people, find a text or open three different documents, you have found where your pay queries come from.
That is where I would start, and it costs nothing to try before changing anything else.
If you want to see how this works on real shifts, book a demo and I will walk through it.
Michael Bryce
Founder of TacDesk. Writes about SIA compliance, operations, and running a UK security company, from someone who actually works the shifts.
Connect on LinkedIn →See TacDesk in action
Win contracts, pass SIA audits, and run your whole operation from one place. Book a free 30-minute demo.
Related reading
The Christmas Rota Is a Fairness Problem Before It Is a Cover Problem
Filling the Christmas rota is hard, but asking the same guards every year does lasting damage. A founder's view on sharing festive shifts fairly.
The Shift Change Nobody Told Them About
Most rota failures are a change that never reached the officer. A founder's view on closing the gap between the rota and the phone in a guard's pocket.
Not Every Contract Is Worth Keeping
A founder's view on the contracts that quietly cost more than they pay, how to spot them, and how to hand one back without burning the relationship.