Client Disputed a Guard Invoice? The Backup Pack That Ends the Argument Fast

The short answer: send one organized pack that lets the client trace every billed hour back to a contract term, a scheduled post, a recorded presence, and an approval. Build it around the specific line they disputed, not the whole invoice. Most guard invoice disputes are not really about the money. They are about the client being unable to see why a number is what it is. Give them a path from invoice line to evidence in under two minutes, and most disputes close in one exchange.

Here is how to build that pack, in the order a reviewer will read it.

Start by finding out what they are actually disputing

Before you assemble anything, get the dispute in writing and narrow it. "The invoice is wrong" is not a dispute you can answer. Ask for the specific lines, dates, posts, or totals they question. Clients usually fall into one of four camps:

• "We did not order that coverage." A scope or authorization question.
• "Your guard was not there that long." A worked hours question.
• "That rate is not what we agreed." A contract rate or premium question.
• "We have never seen this charge before." A surprise, usually an extra, an overtime premium, or a holiday rate.

Each one needs different evidence. If you send the same fat folder of everything to all four, you bury the one page that matters. A narrow question gets a narrow, fast answer, and it signals that you are in control of your records.

Build the pack in five layers

Think of the pack as a chain. Each layer answers one question, and the next layer only matters if the previous one holds.

1. The contract terms that apply

Quote the exact clause, not a summary. Include the rate schedule, the minimum shift length, the overtime and holiday rules, the notice period for schedule changes, and the invoicing terms. Put the clause text next to the invoice line it governs. If the dispute is about a premium rate, the reader should see the rule and the charge on the same page.

If the rate or rule came from an amendment, an email approval, or a site instruction rather than the original contract, include that document and its date. A verbal change that was never written down is the weakest part of most packs, so find out early whether you have one.

2. The schedule or post order that authorized the hours

This is the "we ordered it" layer. Show the schedule as it stood when the shift was worked: the post, the date, the start and end times, and who requested it. If the client asked for extra coverage by email or a ticket, attach that message. Late changes matter here. A shift added the afternoon before is a different conversation from one on the standing schedule, and your pack should show which it was.

3. The record that the hours were actually worked

This is the layer clients push on hardest. Pull the evidence that a guard was on post for the billed time. Depending on how you operate, that may include timesheets, clock in and out records, patrol or checkpoint logs, daily activity reports, or site access records. Use what you actually have. Do not stretch a record to mean more than it does. A patrol log proves presence at checkpoints, not necessarily every minute in between.

Reconcile in plain terms: scheduled hours, worked hours, billed hours. Where they differ, say why. A guard who stayed late for a handoff, a no-show that was covered, a shift that ran short: each is a normal reason, and each is far better explained up front than discovered by the client.

4. The calculation, shown line by line

Show the arithmetic. For each disputed line: hours, rate, any premium, and the resulting amount, tied back to the clause from layer one. If you rounded, state the rule you used. If you applied a minimum shift charge, say so and cite where it comes from. A client who can redo your math and get your number stops arguing about the number.

5. The approvals and prior acceptance

If a site manager signed the timesheet, approved the schedule, or paid earlier invoices built the same way, include that. Be careful with tone here. This layer supports your position, but it should never read as "you already agreed, so be quiet." It should read as "this is how we have both treated this so far, so here is where the difference is."

Lead with a one page cover sheet

The backup should open with a single page that a busy person can read standing up. Include the invoice number, the disputed lines, the amount in question, a two or three sentence explanation per line, and an index of the attached evidence with page references. Everything after that page is reference material.

Keep the language flat and factual. Skip phrases like "as clearly stated" or "per our records, you are mistaken." Write the way you would want to be written to if you were the client's accounts payable contact trying to close a ticket.

Be honest about what you find

Sometimes, while building the pack, you discover the client is partly right. A rate was applied wrongly, a shift was billed that was cancelled, hours were counted twice. Say so immediately and issue a correction for that line. This costs you a little money and buys you a lot of credibility on the lines you keep. A client who watches you correct one error without being pushed is far more likely to accept the rest of the pack without a fight.

If you cannot support a line with real records, do not defend it. Credit it, and fix the process that let it through.

Make the next dispute shorter

Once this one is closed, look at where the pack took longest to build. The pain usually sits in one of three places: schedules that changed without a written trail, worked hours that live in several places that do not match, or contract terms that nobody can find quickly. Fixing those at the source, before invoicing, is worth more than getting good at packing evidence afterward.

A simple habit that helps: before an invoice goes out, spot check the lines most likely to be questioned, such as premiums, late additions, and any shift where scheduled and worked hours differ. Attach the reason to those lines at the time, while the story is fresh.

FAQ

How much backup should I send? Only what answers the disputed lines, plus the cover sheet. Offer the rest on request. Sending everything makes the reviewer hunt, and hunting makes people suspicious.

What if the client says the guard was not on site, and my records are thin? Share what you have and be precise about what it proves. If the gap is real, credit the hours in question. A fast, honest credit is cheaper than a long dispute you cannot win.

Should I hold payment on the undisputed lines while we resolve the rest? Ask for payment of the undisputed portion and treat the disputed lines separately. Check your contract's terms on partial payment and dispute notice windows, and have someone qualified review any language you are unsure about.

Who should send the pack? Whoever owns the client relationship, with the person who prepared the numbers available for questions. A pack that arrives from a named person feels more accountable than one from a generic billing inbox.

Is this legal advice? No. If a dispute involves a contract interpretation you are unsure about, or a significant amount, get qualified advice before you respond.