Security Guard Overtime Billing Errors: How to Catch Them Before the Client Does

The fastest way to catch overtime billing errors is to reconcile three records before any invoice leaves your office: the post's scheduled hours, the hours actually worked, and the contract's overtime terms. Most errors come from the gaps between those three, not from bad arithmetic. A short pre-invoice check that compares them line by line, and flags anything that does not match, will catch the majority of problems before the client does.

This article walks through where the errors come from, a check you can run each billing cycle, and how to handle the ones that slip through.

Why overtime billing goes wrong in security contracts

Overtime in contract security is a two-sided problem. You owe your guards overtime pay under wage rules. Separately, you may or may not be allowed to bill the client for overtime, and at what rate, depending on the contract. Those two things are governed by different documents, and invoices go wrong when someone treats them as one.

A few patterns show up again and again:

• Payroll overtime is billed as client overtime by default. A guard crosses the weekly threshold across two posts or two sites, payroll pays the premium, and the invoice picks it up even though the contract only allows premium billing for specific situations, such as client-requested extra coverage.
• Coverage for a call-off gets billed at the wrong rate. When one guard calls off and another covers on a day off, the cost to you may be overtime. The contract may say the client pays the regular bill rate for covered hours, or a different rate for short-notice coverage. Someone has to read the clause, not assume.
• Holiday and overtime stack incorrectly. Many contracts define holiday rates and overtime rates separately. If both apply to the same hour, the contract should say whether they combine, and which one wins. If it is silent, that is a question for a person, not a default in a spreadsheet.
• Rounding and shift boundaries. Clock punches that round differently in payroll than in billing produce small differences on every shift. Across a month and several posts, those differences become a line the client questions.
• Hours that cross midnight or a pay-period boundary. A shift that starts Sunday night and ends Monday morning can land in two workweeks or two invoice periods depending on how the system splits it.
• Rate changes mid-period. A new bill rate, a wage increase pass-through, or a site moving to a new contract can apply to part of an invoice period, and the whole period gets billed at the old or new rate.

None of these are exotic. They are what happens when hours come from one place, rates from another, and rules from a PDF nobody has reopened since signing.

The three records you need to compare

1. The schedule. What the client asked you to staff, by post, by shift, by day. This is the baseline for what you were supposed to deliver and bill.

2. The worked hours. Actual punches, with any manual edits. Pay attention to who changed a time and why. Edited punches deserve more scrutiny than raw ones, in both directions.

3. The contract terms. For each site: the bill rate by guard classification, the overtime rule, the holiday rule, the minimum shift length, any caps on billable hours, and the approval requirement for extra coverage. Pull these into a plain table. If you cannot summarize a site's overtime terms in a few lines, nobody on your team can apply them consistently.

Overtime errors become visible only when you hold these three side by side. Looking at worked hours alone tells you what was paid. It does not tell you what is billable.

A pre-invoice check that takes less time than a dispute

Run these steps for each site before invoices are released.

1. Total worked hours against scheduled hours. Variance is not an error, but it is a question. Every post with more worked hours than scheduled needs a reason: client request, call-off coverage, or a late relief.
2. List every hour billed at an overtime or premium rate. For each one, find the basis in the contract. If the basis is "the guard was in overtime for payroll," stop. That is not automatically a billing basis.
3. Match premium hours to approvals. If the contract requires client approval for extra coverage, check that an email, ticket, or post order exists. No approval on file means you should expect pushback.
4. Look at the edits. Filter for manually adjusted punches. Confirm each one has a note and an approver.
5. Check shift boundaries. Find shifts that cross midnight, the workweek boundary, or the invoice period boundary, and confirm they were split the way the contract and your payroll treat them.
6. Check the rate table by date. Confirm the rate applied matches the rate in force on the date worked, especially in the weeks after a change.
7. Sample the totals. Pick a few guards and recompute their line by hand from raw punches. If the hand total and the invoice total differ, find out why before sending anything.

The point is not to re-do the invoice. It is to look specifically for the places where a client auditor would look first: premium hours, unexplained variance, and edited time.

What clients actually question

Clients rarely dispute a normal shift. They question lines that look unusual: a block of overtime hours on a quiet post, a weekend rate on a day they do not think was a holiday, or a total that is higher than the schedule they sent. If you can see those lines before they do, you can either correct them or attach the supporting note up front. A one-line explanation ("Covered call-off, approved by site manager by email on the 14th") turns a dispute into a non-event.

When an error gets through anyway

It will happen occasionally. How you handle it matters more than the error.

• Acknowledge it quickly and specifically. State which invoice, which lines, and what the correct amount is.
• Issue a corrected invoice or credit, according to your contract and your accounting rules, instead of quietly netting it against the next bill.
• Find the cause. If the same type of error appears twice, it is a process gap, and the fix belongs in the pre-invoice check, not in an apology.

Keep a short log of every correction with its cause. After a few cycles it will show you which sites, rules, or edits generate most of your problems.

FAQ

Is overtime I pay a guard always billable to the client? No. What you owe your employee under wage law and what you may bill under the contract are separate questions. The contract's own terms decide what is billable. If the contract is unclear, get clarification in writing.

Who should own this check? Someone who can read the contract and see the hours, usually billing or operations. Whoever it is, they need access to both, and they need authority to hold an invoice.

Should we bill overtime at all if the contract is vague? Raise it with the client before the invoice, not after. A short note explaining the situation and asking for confirmation protects the relationship better than a surprise line item.

How often should we audit past invoices? Whenever a rate, rule, or site changes, and on a regular schedule for the largest accounts. Errors tend to cluster after changes.

Do daily overtime rules matter? In some places, yes. Overtime can be triggered by daily hours as well as weekly hours, and rules differ by location. Check the rules that apply where your guards work, and confirm with qualified payroll or legal advice where needed.