OwedA customer says they never received the invoice. Another says the HVAC repair was incomplete. A general contractor says the change order was not approved. These are not accounts to leave in a generic “past due” pile. Knowing how to document customer disputes gives your office a clear record of what happened, who owns the next step, and when to follow up without damaging a relationship.
For a busy contracting business, the goal is not to win an argument in your accounting system. It is to separate a real billing or job concern from an invoice that simply needs attention, then move the account forward professionally. Good documentation prevents the same customer from being contacted repeatedly, helps office staff stay aligned, and gives managers a better view of overdue revenue that may still be collectible.
Why dispute documentation matters in accounts receivable
An overdue invoice and a disputed invoice are not the same thing. A past-due balance may be waiting on a forgotten approval, a check run, or a customer who has not seen the invoice. A dispute means the customer has raised a question, objection, or condition that may affect payment.
When those statuses are mixed together, follow-up becomes inconsistent. One team member may send another payment reminder while a project manager is already investigating a workmanship concern. Or a customer may promise to pay once revised paperwork arrives, but that commitment gets buried in an email inbox.
Clear dispute records help your team answer practical questions quickly:
- What exactly is the customer questioning?
- Which invoice, job, line item, or change order is involved?
- When did the customer raise the issue?
- Who is responsible for reviewing it internally?
- What information or action is needed before the next customer contact?
- Is the undisputed portion of the balance still due?
This information also makes your aging report more useful. Instead of seeing one large number labeled overdue, you can distinguish balances awaiting payment, accounts with a promise to pay, invoices under review, and accounts that should be paused from routine follow-up.
How to document customer disputes step by step
The best process is simple enough that your office will use it during a busy week. Create the record as soon as the dispute is raised, even if you do not yet know whether the customer’s concern is valid.
Record the customer’s concern in their own words
Start with a concise, factual description. Avoid labels such as “refusing to pay” or “difficult customer.” Those phrases do not help resolve the issue and can lead your team to make assumptions.
Instead, document what the customer said and how they said it. For example: “Customer stated by phone that the invoice includes two hours of labor they believe were not authorized.” If the concern arrived by email, save the message or copy the relevant text into the account record.
Include the date, time, communication channel, and the employee who received the dispute. If a technician, project manager, or owner heard the concern first, make sure it reaches the person managing accounts receivable.
Tie the dispute to the right records
A useful dispute record connects the customer’s concern to the underlying work. At a minimum, identify the invoice number, invoice date, amount due, job or project number, and service address if your business uses one.
Then attach or note the records that may help verify the issue. Depending on the trade and the dispute, that might include a signed estimate, approved change order, work order, service ticket, job photos, completion signoff, delivery confirmation, or prior email correspondence.
A roofing company, for example, may need to compare the invoice against the approved scope and change documentation. A plumbing company may need the technician’s service notes and customer authorization. Do not make the record a warehouse for every document your company has. Capture the materials that will help someone investigate the specific question.
Classify the dispute without oversimplifying it
Use a small set of categories so reporting stays consistent. Common categories include billing accuracy, pricing or scope, work quality, incomplete work, missing documentation, duplicate invoice, warranty concern, insurance or third-party approval, and administrative delay.
The category is not a final judgment. It is a way to route the account and identify patterns. If several customers are disputing missing signed work authorizations, that points to an operational issue worth fixing before more invoices become overdue.
Some accounts have more than one issue. A customer may question part of the invoice while also waiting for warranty paperwork. Record both, but identify the primary issue and the next action needed first.
Separate the disputed amount from the undisputed amount
Not every dispute applies to the entire invoice. A customer may question a $350 material charge on a $4,000 electrical project, or may agree the work was completed but need a corrected purchase order number before their accounts payable team can release payment.
Document the total invoice amount, the amount being disputed, and the amount the customer does not appear to dispute. Your follow-up approach should reflect that distinction. It may be appropriate to ask whether the undisputed amount can be paid while the remaining question is reviewed, but the right approach depends on the customer relationship, contract terms, and the facts of the job.
Avoid changing an invoice balance or offering a credit before the appropriate person has reviewed the matter. The record should show what the customer requested, not silently treat the request as approved.
Assign an owner and a deadline
A dispute with no owner is usually just a delayed invoice. Assign one person to move the review forward. That may be the project manager, service manager, estimator, bookkeeper, or owner, depending on the issue.
The record should state the next internal action and a target date. For example: “Project manager to review signed change order and call customer by Thursday,” or “Office to resend invoice with certificate of completion and follow up in two business days.”
A deadline matters because customers often interpret silence as a lack of concern. Even if the review is not complete, a brief update can preserve trust: “We are reviewing the work order and will update you by Friday.”
Keep a dated communication timeline
Every meaningful contact should be recorded in one place. Note outbound calls, voicemails, emails, customer replies, documents sent, internal decisions, and payment commitments. Keep entries factual and brief.
A useful timeline might show that the customer disputed an invoice on Monday, the office sent supporting documents Tuesday, the service manager inspected the work Thursday, and the customer agreed to pay after receiving a revised invoice Friday. Without that timeline, the next employee may repeat a question the customer already answered or send a reminder that ignores the active review.
When a customer promises payment, record the amount promised, the expected date, and any condition attached to the promise. A promise to pay after receipt of a revised invoice is different from a promise to pay by Friday. Track both separately from the dispute itself.
Set rules for pausing routine follow-up
A dispute does not always mean all follow-up should stop. It does mean routine reminders should be handled thoughtfully. Your team needs clear rules for when an account is paused, who can remove the pause, and when the next review is due.
For example, you may pause standard payment reminders while a documented workmanship concern is being inspected. You might continue administrative follow-up when the only issue is a missing invoice copy or vendor form. The correct choice depends on the facts, the relationship, and your company’s communication policy.
If a customer asks not to be contacted through a particular channel, record that decision clearly. If there is a reason to stop all contact temporarily, document the reason and review date. Do not rely on someone remembering a phone conversation from three weeks ago.
Review disputes before they become old receivables
Set a regular cadence to review open disputes, ideally at least weekly. Look at the age of the dispute, disputed and undisputed dollars, last customer contact, assigned owner, and next action date. Older disputes deserve attention because missing documents, unclear handoffs, and unresolved job questions become harder to address over time.
This review is also where operations and accounts receivable can work together. A bookkeeper may know an invoice is unpaid, but a field manager may know the customer is waiting for a final inspection. Both pieces of information are needed to determine the next step.
An organized platform such as OwedWell can help teams track disputes alongside replies, payment promises, pauses, and verified payments. AI can assist with organizing account information and preparing follow-up, while your business reviews and approves customer-facing communication. The contractor remains in control of the customer relationship and the decision-making.
Use documentation to improve the process, not just the account
Over time, dispute records can reveal avoidable causes of delayed payment. If “missing documentation” appears often, your invoicing checklist may need work. If pricing disputes cluster around change orders, your approval process may need to be more consistent. If warranty questions are regularly sent to the office after a service call, technicians may need a clearer customer handoff.
Keep the focus on patterns, not blame. Many disputes begin with ordinary operational gaps: an invoice sent to the wrong contact, a customer who did not understand a charge, paperwork that was not attached, or work that requires a return visit. Better documentation helps you correct those gaps while still following up on money your business has earned.
A well-documented dispute gives the customer one clear point of contact and gives your team one reliable version of the facts. That is how you protect cash flow, reduce repeated follow-up, and keep a solvable billing question from becoming an old unresolved balance.