Electrical Contractor Invoice Dispute Backup: What to Send When a Customer Challenges the Bill

The invoice went out three weeks ago. This morning the reply came back: "Three guys, five days? On what?"

What you need now is electrical contractor invoice dispute backup — the documentation that sits underneath the invoice and shows what the hours bought. Not a better-looking invoice. The invoice already said what it said: in this example, 112 hours at a $95 T&M bill rate, $10,640.

Every guide on this subject teaches you how to create an invoice. This one starts the moment after a customer pushes back on one.

Below: the triage to run first, the packet to send, the wording to send it with, what to concede and what to hold, and the four one-page documents that keep the next job from getting here.

What Counts as Invoice Dispute Backup?

Backup is the record that lets your customer reconstruct the charge themselves, without taking your word for anything. It answers four questions on every line: what day, who was on site, what they did, and how long it took.

An invoice is a summary. A summary gives the customer nothing to check. So they check the only thing available to them — their own sense of whether 112 sounds like a lot.

The test is simple. Hand the document to somebody who wasn't on the job. If they can follow the work day by day, you have backup. If they have to trust you, you have an invoice with more rows on it.

Run the Two-Minute Triage Before You Answer

Before you write a word back, find out what you actually have for the disputed hours. Pull the timesheets, the job folder, the text threads, and the photos on the crew leader's phone.

Then put yourself in one of three columns. Each one gets a different response, and one of them is honest bad news.

What you have	What it means	What to do
Described work, by day, by person "Thu — Martinez, Ruiz, Delgado — pulled and terminated circuits 12–18, second-floor east wing"	You can answer the dispute completely	Assemble the packet, send it, hold your number
Hours only "5/13 — Martinez 8.5, Ruiz 8.5, Delgado 8.0"	You can prove attendance, not work	Rebuild the narrative from photos, texts, delivery tickets and the crew's memory — this week, while it's still recoverable
A lump total "112 hrs @ $95"	You have nothing the customer can check	Limit the damage on this one and fix the capture before the next job

If you landed in the third column, skip to the concession section. Arguing from a lump total burns the relationship and usually ends in a bigger write-off than a straight conversation would have.

The Line That Loses the Argument and the Line That Ends It

Two versions of the same charge. Same hours, same money, same job. One of them gets questioned every time.

Example, using 112 hours at a $95 bill rate across three workers — Martinez, Ruiz and Delgado — over five dates:

Loses the dispute	Ends the dispute
Electrical labor — 112 hrs @ $95/hr — $10,640	Thu 5/15, 7:02a–3:48p — Martinez, Ruiz, Delgado — pulled and terminated circuits 12–18, second-floor east wing — 8.77 hrs each @ $95/hr
Nothing on this line can be checked. The customer is left comparing 112 against their own impression of the job	Names a task the customer can walk out and look at. A terminated circuit is either there or it isn't

That is the whole mechanism. The note your electrician writes in the field is the explanation your customer reads at their desk.

They are not two separate problems. Getting clean hours out of the crew and getting invoices nobody fights is one job, done once.

What Belongs in a Customer-Safe Backup Packet

Six columns, one row per worker per day. That is the entire format, and it is enough.

Column	Example	Objection it answers
Date	Thu 5/15	"When was anybody even out there?"
Who	Martinez, Ruiz, Delgado	"Three guys? For what?"
What was performed	Pulled and terminated circuits 12–18, second-floor east wing	"What am I actually paying for?"
Hours	8.77 each	"That seems like a lot of time"
Bill rate	$95/hr, per agreement dated 4/28	"Since when is it that much?"
Amount	$2,499.45 — 8.77 hrs × 3 workers × $95/hr	Arithmetic they can redo themselves

Add on-site verification as corroboration only — arrival and departure times, or a plain "on site, verified" stamp. It supports the hours; it is not the point of the document.

Do not send a location trail or anything resembling a map of where the truck went. It reads as surveillance, it invites new questions, and it does not make the hours any more believable.

A filled-in version of this format, annotated line by line, is on the sample billing packet page. No signup, nothing to fill in.

What Must Never Leave Your Office

This is the mistake that turns a billing dispute into a pricing negotiation: exporting the internal job cost report and forwarding it as backup.

That report carries what you pay your electricians. The moment your customer sees your cost rate — say $38 on a job you're billing at $95 — sitting on the same page, the conversation stops being about hours.

Goes in the packet	Stays internal
Date, worker, task, hours	Cost rate — what you pay the electrician
Agreed bill rate and extended amount	Total labor cost, burden, insurance loading
Signed T&M tags and change orders	Gross margin, budget variance, job costing reports
"On site, verified" arrival and departure	Location history, anything resembling a movement trail
Photos tied to a date and a task	Any note about a worker's pace or performance

Your bill rate is a contract term. Your cost rate is nobody's business but yours. Keep the two documents physically separate so a rushed Friday afternoon can't merge them.

How to Build the Packet Today From Records You Already Have

You do not need software for this. A spreadsheet and an afternoon will produce a packet that holds up.

1. Pull every source for the disputed dates. Timesheets, payroll records, text threads, dispatch messages, supply house delivery tickets (they date-stamp which day the 500 MCM went to the job), and the photos on the crew leader's phone. 2. Lay out one row per worker per day. Date, name, hours. Get the skeleton right before you worry about descriptions. 3. Fill in the "what was performed" column. Gear and panel photos date themselves — a photo of a trimmed-out panel fixes which day the terminations happened, and a delivery ticket fixes when the material arrived to make it possible. Call the crew leader for the rest, this week, while it's still recoverable. 4. Mark anything you can't substantiate. Do not guess and do not round up. An honest blank is survivable. An invented description that gets found out is not. 5. Break out drive time, supply house runs and standby on their own lines. Buried inside a labor total they look like padding. Labeled, they're ordinary: "0.75 hr — supply house run, 500 MCM lugs, per RFI 12." 6. Attach the authorizations. Signed T&M tags, the change order log, the email where the GC's PM said proceed. Reference each one by the dates it covers, and if added circuits came out of an RFI or ASI, put that number next to the hours it generated. 7. Total it and check the arithmetic twice. One transposed number in a dispute packet costs you the credibility of every other line on the page.

What to Write Back

Send the packet with a short, flat cover note. No defensiveness, no lecture on how T&M works, and no apology either.

Three things that note does. It hands over the evidence without being asked twice, it volunteers the two lines they were most likely to challenge, and it invites a specific objection instead of a general one.

A customer who has to argue about 5/20 has already conceded every other line on the sheet.

What to Concede and What to Hold

Concede anything you cannot document, immediately, without being pushed. Hold everything you can.

Cheap concessions are what make the rest of the packet credible. A contractor who defends all 112 hours down to the last minute looks like a contractor who would.

Example arithmetic: 112 hours at a $95 bill rate is $10,640. Drop 6 hours you can't substantiate and you're at 106 hours, or $10,070 — a $570 concession that buys agreement on the other $10,070. Run it with your own hours and rate; the invoice dispute calculator will do the arithmetic if you'd rather not.

Concede	Hold
Hours with no description you can reconstruct	Hours with a described task and a matching photo or delivery ticket
Duplicate entries and arithmetic errors — fix them out loud	Work covered by a signed T&M tag or written approval
Travel billed contrary to your own contract terms	Standby you flagged in writing on the day it happened
Supply house runs billed as labor when your contract prices them as overhead	Troubleshooting hours with a described fault and a corrective action — "open neutral on RTU-3, replaced lug, retested"
Anything a reasonable person would look at and call padding	Rework you were directed to do after a design change moved the panel or added circuits

Say the concession in plain numbers: "Line 7, Friday 5/16 — 6 hours, no task description on file. I'm taking it off. That's $570. The remaining 106 hours are detailed on the attached sheet."

Then stop talking. The person on the other end now has to name which documented line they believe is false.

When the Customer Says the Work Was Never Authorized

Documentation of hours won't touch this one. The argument isn't whether you were there — it's whether anyone told you to be.

The answer is the paper trail from before the work happened: a signed T&M tag, a numbered change order, or an email saying proceed. If the scope grew out of an RFI or a field condition, the RFI number belongs in the packet next to the hours it generated.

For unsigned work already performed, the best evidence available is contemporaneous — the email you sent that day, the photo of the condition, the text where the PM said keep going. Contemporaneous beats reconstructed every time, which is the entire argument for writing things down as they happen.

Going forward, get the tag signed in the field on the day, before anybody leaves. A signature on a phone screen at 3:45 that afternoon is worth more than any amount of explaining in August. More on that in T&M billing best practices.

If Documentation Doesn't Settle It

Sometimes the customer isn't confused, they just aren't paying. Documentation is the foundation of every remedy that follows, but it is not the remedy.

Know your deadlines before you need them. Most states have prompt payment statutes covering construction, and lien and notice deadlines run in months, not years — Texas, for instance, requires subcontractor notice by the 15th day of the third month after the month the labor was performed (Texas Property Code Ch. 53). Your state is different. Look it up now, not mid-argument.

Here is the honest limit: past a certain point this is a contract question and a lawyer's question, not a documentation question. What documentation decides is whether you walk into that conversation with a story or with a record.

The Four Documents That Prevent the Next One

Everything above is recovery. These four are prevention, and each one is a single page.

Document	When it gets created	What it answers later
T&M work authorization	Before the extra circuits, the panel move or the after-hours call starts	"I never approved that"
Daily field report	End of each day, by the crew leader	"What happened out there on the 15th?"
Labor backup sheet	Rolls up from the daily entries	"What did these hours buy?"
Change order log	Every time scope moves — a new RFI, an added home run, a relocated panel	"Why is this more than you told me?"

Blank versions of all four are in the T&M Billing Backup Kit — free, no email required. Print them, put them in the truck, and the next dispute is a five-minute email instead of a lost afternoon.

The change order log is the one contractors skip and regret. Numbered rows, date requested, who authorized it, hours and materials, running total. It turns "this is way more than the estimate" into a document with the customer's own approvals on it.

The Real Blocker Is Getting the Note Written at All

None of this works if the hours come in bare. And the reason they come in bare isn't laziness — "fill out your timesheet" asks for a number, so a number is what comes back.

Ask a different question at the end of the day: what did you work on? One line. What, and where.

• "Pulled and terminated circuits 12–18, second-floor east wing."
• "Rough-in panel B, north corridor — set 14 boxes."
• "Troubleshot open neutral on RTU-3, replaced lug, retested."
• "Same as yesterday, circuits 19–24."

Eight words is plenty. No adjectives, no full sentences, no spelling standards. Name the thing and name the place.

Tell the crew why, once, and tell them the real reason: this is what stops a customer chiseling the company on work they actually performed. That framing earns cooperation. "So I can check on you" never has and never will.

Then make it cost them nothing. A spiral notebook in the gang box works. So does a group text at quitting time, a shared sheet, or a time app that prompts for the note at clock-out and lets them reuse yesterday's line — FieldTimesheet does that, and it isn't the only one that does. What matters far more than the method is whether it's still happening in week six.

One more rule: never let the crew become the bottleneck on billing. If a note is missing, the office reconstructs it that same week, while somebody still remembers.

Format It So the PM Can Approve It Without Calling You

On commercial work, the person deciding whether you get paid is usually a GC project manager processing a pay application, not the owner. They approve what fits their process and question what doesn't.

Match their format. If the job runs on AIA G702/G703 pay applications, tie your labor backup to the same line items and the same billing period so your detail drops straight into their continuation sheet.

Put the job name, the contract or PO number, and the billing period on every page. A packet that gets separated from its cover email and can't be identified is a packet that gets set aside.

And send the backup with the invoice, not after somebody asks for it. Backup that only shows up under pressure looks assembled for the occasion — which, arriving three weeks late, it usually was.

Common Questions About Electrical T&M Invoice Backup

What documentation do I need if a customer disputes my T&M invoice?

Date, who was on site, what they performed, hours per person, the agreed bill rate, and the extended amount — one row per worker per day. The task line has to name real work: "terminated circuits 12–18, second-floor east wing," not "electrical work." Attach the signed T&M tags, change orders, and any written approvals covering the scope in question.

Is a timesheet enough to back up a T&M invoice?

Usually not on its own. A timesheet proves somebody was on the clock; it doesn't say what they did, which is the actual question being asked. "8.77 hrs" doesn't say whether the day was setting gear or troubleshooting an open neutral. A timesheet plus one line of task description per person per day is enough for most disputes.

Should I send backup with every invoice, or only when the customer asks?

Send it with the invoice. Once the record exists, attaching it costs nothing. And backup that shows up only after a challenge was, by definition, assembled after the challenge — the customer can see that from the timestamps.

How much detail is too much detail?

Stop at what the customer needs to follow the work: the task and the location — "set 14 boxes, north corridor," not the method you used to pull the wire. Skip crew chatter, internal problems, and anything about how a specific worker performed. More words are not more convincing — more checkable facts are.

Can I show clock-in times or GPS without it looking like I'm watching my crew?

Yes, if you use it as corroboration and nothing more. "On site 7:02a, departed 3:48p, verified" supports the hours. A map of where the truck went all day is a different document and does not belong in a customer packet.

What if the customer already refused to pay and I have no field notes for that job?

Reconstruct what you can this week from photos, texts, delivery tickets and the crew's memory — it degrades fast. Concede the hours you genuinely can't support, hold the ones you can, and make the next job the one you document properly.

How do I give a breakdown without exposing my costs?

Never forward the job cost report. Build a separate customer-facing sheet carrying bill rate and amount only. If the sheet carries an hourly figure you recognize from your journeyman's payroll — say $38 on a job you're billing at $95 — it is the wrong document to send.

Does a signed T&M work authorization actually prevent disputes?

It prevents the "I never approved that" version, which is the hardest one to win after the fact. It doesn't prevent challenges to the hours themselves — that's what the daily description of circuits, gear and locations is for. Together they cover both arguments.

The Short Version

The charge was fair. The explanation was missing. That gap is the whole dispute.

Closing it costs one line per worker per day, written in the field while it's still true. Everything else here is what you do when that line didn't get written.

Start with the sample billing packet to see the format filled in, then take the four blank forms from the T&M Billing Backup Kit out to the truck.