Note
What Your Job Records Do When a Client Disputes an Invoice
When a client disputes an invoice, most contractors’ first instinct is to send someone back to site. A technician inspects the work, confirms it was done correctly, and the visit report is emailed to the customer. Sometimes that resolves it. Often it takes a second trip.
Neither trip should be necessary if the right records exist from the original job close.
The documentation produced when a job closes properly is not just an administrative record. It is evidence that travels when you are not there: a dated photograph, a scope checklist, a signature. When a client raises an invoice dispute, the question is either answered by those records or it is not answered at all.
What Types of Invoice Disputes Actually Come Up?
Factory electrical work tends to produce four categories of payment dispute.
Contested completion. “We don’t think this section was finished.” This is the most common and usually the simplest to resolve. The job close record, with a completion date and technician sign-off, addresses it directly. A signed handover document with a scope checklist closes it.
Condition at completion. “The work was done but left in an unacceptable state.” This requires photographic evidence. The photos taken during and after job close show what the installation looked like when the crew left. Without those photos, the conversation depends on recollection, and recollections do not hold up well across a six-week billing cycle.
Contested scope. “We didn’t agree to this line item.” This traces to variation orders and change documentation. If a scope change was agreed verbally and recorded nowhere, the client’s interpretation carries the same weight as the contractor’s. A signed variation order, produced at the time of the change, is what separates a resolvable disagreement from a write-off.
Post-completion fault. “The system has a problem so we’re not paying.” The documentation here needs to include the commissioning baseline record and any subsequent signed visit records. A fault that appeared six weeks after a properly documented handover is a different conversation from a fault on a site where the handover status is uncertain.
What Does a Strong Documentation Package Look Like?
When a payment dispute arrives, the response package should address the specific category being raised. In most cases the practical package includes:
- The signed handover certificate, showing the date, the scope accepted, and the name of the person who signed it. This is the most important single document in any completion dispute.
- Completion photographs from the final day on site. For each major system area: at least one photo showing the installed condition, with readable labels where equipment serial numbers or circuit identifiers matter.
- The job close record showing the technician, the date, and the checklist items confirmed at close. This is the contractor’s own internal record, but it corroborates the date and the scope.
- Signed variation orders for any scope items added after the original agreement. If the disputed line item was added mid-installation, the signed variation stands in for the original quote.
Worked example: A contractor invoices for a panel upgrade at a Chonburi factory. The invoice includes a variation for additional cable trunking added when the factory expanded a circuit partway through the job. The factory’s accounts department disputes the variation line, saying it was not authorised. The contractor sends the variation order signed by the factory’s electrical engineer, dated three weeks before completion. Accounts confirms with engineering. The invoice is paid in full. Total resolution time: one email and two days.
What Happens When the Records Are Not There?
The direct answer: the dispute becomes harder to settle without returning to site, and returning to site is not free.
A technician’s time for a return visit, including travel and the inspection itself, is one to two hours at minimum. At a factory in an industrial estate, it is often half a day once access is arranged and the relevant person is available. Multiply that by the number of contested invoices in a year and the cost of missing documentation becomes concrete.
Beyond the direct cost, there is the dispute outcome. A contractor without a signed handover document is in a weaker position on any completion dispute, regardless of whether the work was actually done correctly. The absence of the document does not mean the work was not done. It means you cannot show it was done.
Some disputes are written off rather than escalated because the cost of pursuing them exceeds the expected recovery. That write-off rate rises when documentation is thin.
How Does a Structured Job Close Prevent This?
The records that resolve disputes are the records produced at job close, not records reconstructed after a dispute arrives.
A job close process that requires a signed handover, photographs of each major system area, and a completed checklist before a job enters the billing queue is the same process that produces a useful documentation package eighteen months later.
The signed handover matters at billing. The photos matter at the first warranty call. Both matter when a new facilities manager at the factory has no knowledge of the original agreement and questions an invoice. The cost of capturing them is a few minutes on the day. The cost of not capturing them arrives later, in the form of return trips, longer dispute cycles, and write-offs on work that was genuinely completed.
The records also travel independently of the people involved. The technician who did the installation may have moved on. The project manager who ran the job may be on a different project. The documentation is what remains when the people who remember it are not available.
FAQ
What if the client signed the handover but now claims they didn’t understand the scope?
A handover document with a clear scope checklist is difficult to walk back. The standard approach is to send the signed document, noting the date and who signed it, and ask the client to identify specifically which item they are questioning. Most disputes in this category resolve when the actual scope list is in front of both parties and the client can see what their colleague signed off on.
What if the person who signed the handover has since left the client’s organisation?
This happens frequently after a 12 to 18-month project and billing cycle. The new contact has no personal knowledge of what was agreed. Present the signed handover as a reference document rather than a correction: “Here is the handover record from when we completed the installation. It might be useful context for the billing question.” The document does the work; the framing keeps the conversation constructive.
Does a signed handover certificate prevent all invoice disputes?
No. It addresses disputes about whether completion happened and what the scope was. Performance disputes, equipment failures within the warranty period, and workmanship quality questions all require the underlying technical records as well. A handover certificate is one layer, not the full set. The commissioning baseline record, technician close logs, and inspection visit records are what address the other categories.
The records that resolve a payment dispute are the same records produced when every job closes through a structured process. If you want to see how TRACE 30 builds that process, the /program/ page covers what goes into each job close.