How to handle payment disputes and still collect on time

A payment dispute is a customer's stated reason for not paying an invoice in full, such as a pricing error, a short shipment, or a service complaint. The invoice is not refused, it is held until the objection is resolved. To handle one without losing the payment, acknowledge it fast, route it to whoever can answer it, resolve the reason, and confirm the new payment date in writing, all while keeping the rest of the invoice collecting.

Disputes are where collections quietly stall. A reminder cadence that works on a customer who simply forgot does nothing for a customer who is holding the invoice on purpose, and sending another reminder into a real dispute only annoys them. The job is to pull disputed invoices out of the normal flow, resolve the actual problem quickly, and put them back on track to pay, rather than letting them age in limbo.

Why disputes stall collections

A disputed invoice is stuck for a reason your reminder emails cannot address. The customer is not waiting for a nudge, they are waiting for an answer. Until someone gives them that answer, the balance ages, your DSO climbs, and the invoice clogs your aging report next to invoices that are genuinely just late.

The damage compounds when nobody catches the dispute early. A customer mentions a pricing problem in a reply, the reply gets missed, the automated cadence keeps firing past-due notices, and a fixable disagreement curdles into a soured relationship. The first move in handling disputes is simply seeing them: spotting the moment a customer's silence or short pay is actually an objection, and switching that invoice from "chase" to "resolve."

Common types of payment disputes

Naming the type is the first step to resolving it, because each one routes to a different owner.

• Pricing. The invoiced price does not match a contract rate or a quoted discount. Routes to whoever set the price, usually sales or contracts.
• Quantity or shortage. The customer received fewer units or hours than billed. Routes to fulfillment, the warehouse, or the project owner with the proof of delivery.
• Quality or service. Goods arrived damaged, or the service fell short of what was promised. Routes to operations or the account owner.
• Administrative. A missing PO number, the invoice sent to the wrong contact, or terms the customer never agreed to. Often the fastest to fix once you spot it.
• Never received. The customer claims they never got the invoice, which is sometimes true and sometimes a stall. Resend with proof and a firm new date.

Most disputes fall into these five. For the cases that involve money withheld against an invoice, our guide to managing AR disputes and deductions covers how to separate the reason from the dollars and recover what was taken in error.

A step-by-step dispute resolution process

Run every dispute through the same five steps so none of them gets lost.

1. Acknowledge the same day. A fast, calm acknowledgement defuses the customer and signals you take it seriously. Silence makes them assume you are ignoring them.
2. Log the exact reason and the disputed amount. Record what they are objecting to and how much is in question. A vague "they're unhappy" note cannot be routed or measured.
3. Pause reminders on the disputed amount, keep collecting the rest. Stop the past-due cadence on the part under dispute. If the customer disputes $1,000 of a $5,000 invoice, keep collecting the undisputed $4,000.
4. Route to the owner with the document attached. Send the case to the one person who can answer it, with the contract, proof of delivery, or order already pulled, so they open a complete file instead of starting an investigation.
5. Confirm the resolution and the new payment date in writing. Once resolved, state the outcome, issue any credit, and pin down exactly when the corrected balance will be paid. Then resume collection.

Worked example: a customer holds a $6,000 invoice over a $900 pricing error. You acknowledge it that morning, log the $900 and the reason, keep collecting the clean $5,100, route the pricing question to the sales rep who quoted the deal, and two days later issue a $900 credit and confirm the $5,100 will pay on Friday. The dispute cost you two days, not two months.

Templates for acknowledging and resolving disputes

The acknowledgement, sent the same day:

Subject: Re: invoice [Invoice number], looking into this now

Hi [Customer name],

Thanks for flagging this. I want to make sure we get invoice
[Invoice number] right.

To confirm, you are holding [Disputed amount] because of [Reason as you
understand it]. I am sending this to [Team / person] to check today and
will come back to you with an answer by [Date].

In the meantime, the remaining [Undisputed amount] on the invoice is not
in question, so you are welcome to settle that part here: [Payment link]

Thanks,
[Your name]
[Company name]

When to send this: the same day a customer raises a dispute, to confirm the exact issue and keep the undisputed balance moving.

The resolution, once the case is settled:

Subject: Resolved: invoice [Invoice number]

Hi [Customer name],

Thanks for your patience. Here is where we landed on invoice
[Invoice number]:

- [Outcome, e.g. "We have applied a credit of $900 for the pricing
  difference."]
- Updated balance due: [Corrected amount]

Could you arrange payment of the [Corrected amount] by [New due date]?
You can pay here: [Payment link]

Appreciate you working through this with us.

Thanks,
[Your name]
[Company name]

When to send this: the moment the dispute is resolved, to confirm the outcome and lock in a firm new payment date.

Preventing disputes upstream

Most disputes are not really collection problems, they are invoicing and fulfillment problems that surface at payment time. Wrong prices, missing PO numbers, invoices that do not match the order, and terms the customer never agreed to all create disputes you then have to spend hours resolving. Fixing the source is far cheaper than fixing the symptom.

The high-leverage prevention work happens before the invoice goes out: accurate prices pulled from the contract, terms agreed in writing, the right PO and contact on every invoice, and fulfillment data that matches what you billed. Clean invoices simply get disputed less. Settling terms clearly up front also removes a whole class of "I never agreed to that" objections, which is part of why our guide on how to prevent late payments treats clear expectations at invoice time as the cheapest collection tool you have.

How Rex detects and manages disputes

Rex is an agentic AI accounts receivable agent, so it does not just send reminders and wait. When a customer replies with an objection or short pays an invoice, Rex reads it, recognizes it as a dispute, and classifies the reason instead of firing another past-due notice into a live disagreement. It pauses the cadence on the disputed amount, keeps collecting the undisputed balance, and routes the case to the right owner with the supporting document already pulled, across every account on the ledger at once.

Once the dispute is resolved, Rex confirms the corrected balance and resumes collection automatically, so the invoice never stalls in limbo and no fixable disagreement ages into a write-off. It escalates to a person only when a case needs a human decision, which means your team spends its time settling the disputes that matter rather than triaging an inbox to find them. Tightening the whole flow around it is the subject of our guide on how to improve your AR collection process. See how Rex runs collections end to end.