Skip to content

Customer disputes an invoice — the reply that resolves it

A dispute is not a collections problem. The moment one is raised, chasing payment stops being useful and starts making the dispute harder to settle.

  • Two weeks overdue
  • Neutral tone
  • They dispute the amount

The email

Subject

Re: invoice [Invoice number] — let us get this settled

Body

Hi [Customer name],

Thanks for telling me. I have put invoice [Invoice number] on hold and stopped the reminders while we sort it out.

So I can deal with the right thing: which line or amount do you think is wrong, and what did you expect it to be? If it is easier, mark up the attached copy and send it back.

Once I understand the objection I will either correct the invoice and re-issue it, or explain why I think it is right — and if part of it is not in question, I can split that out so it is not held up by the rest.

Can we agree to have this resolved by [Date]?

Thanks,
[Your name]
[Your business]

Fill in before you send

  • [Customer name]
  • [Invoice number]
  • [Date]
  • [Your name]
  • [Your business]

When to send this

  • As soon as a customer questions the amount, the scope or the work — before you have decided whether they are right.
  • When part of the invoice is uncontested and could be paid now while the rest is argued about.
  • When the objection has been vague so far and you need it specific enough to answer.

When not to send this

The wrong reminder at the wrong moment costs more than no reminder at all.

With a reminder still running, or with the next scheduled chase left switched on.
Instead: Turn the sequence off for this invoice first, then send it. A dispute plus a reminder in the same week reads as a refusal to listen, and it converts a fixable billing error into a matter of principle that costs far more to settle.
With your defence of the invoice already in it.
Instead: Ask the question and stop. Defending a charge before you know which one is being questioned makes the email about your position rather than their objection, and it hands them arguments they had not thought of.
When what they raised is a complaint about the work rather than about the invoice.
Instead: Answer the complaint on its own terms, without mentioning the balance at all. Replying to 'this was not what we agreed' with a question about which line is wrong tells them you heard an accounting query when they made a professional one.

Not certain this is the reply you got?

This template assumes they dispute the amount. Replies rarely say so in those words, and picking the wrong one is how a dispute gets chased or a kept promise gets nagged. Paste what they actually sent and the decoder will tell you which situation it is — and therefore which email belongs here.

Decode the reply you were sent

Notes on this one

Offering to split the invoice is the most underused sentence in collections. It is common for a customer to be querying one line on a much larger bill; splitting it gets the uncontested majority paid on time and shrinks the argument to its actual size.

Putting a date on the resolution rather than on the payment keeps the process moving without asking for money while a dispute is open. It also makes it visible if the dispute is being used to stall, because a customer with a real objection will agree to a date.

Questions this comes with

Should you keep sending reminders while an invoice is disputed?
No. Reminders during an open dispute do not speed anything up and they do real damage: they signal that the objection has not been read, they give the customer a reason to widen the complaint, and if the matter ever goes anywhere formal, a record of continued chasing over an unanswered dispute is not a good look. Pause the sequence, resolve the objection, then restart from where you left off.
What if the customer disputes an invoice only after you chase it?
Treat it as a real dispute anyway, and handle it the same way. A late objection is often a stall, but you cannot tell without asking the specific question — and the specific question is what exposes a stall, because a manufactured objection rarely survives 'which line, and what did you expect it to be?' Handling it seriously also costs you nothing if it turns out to be genuine, which it sometimes is.

Collectly does this across every invoice, on its own

You just picked the email to send on one invoice. Collectly does the same thing continuously for every unpaid invoice you have — reads the replies, works out why each one is unpaid, estimates when it will land, and drafts the follow-up for you to approve.

With 15 rules it cannot talk its way around

  • A paid or written-off invoice is never chased again. Follow-ups are switched off permanently, not deferred.
  • A disputed invoice stops automated chasing entirely and goes to a person to resolve.
  • A promise to pay on a date pauses reminders until that date has passed. Collectly checks back the day after, not on the day.
  • At least three days between reminders on the same invoice, so re-running the analysis cannot turn into nagging. A resent or corrected invoice the customer has just asked for is not a reminder, and still waits for your approval.

Want the full template pack in one email?

All of them in one message you can keep. Both offers are opt-in, and you confirm by email before anything is sent.

What should we send you?

Double opt-in: you get one email asking you to confirm, and nothing else until you click it. Every email after that has a working unsubscribe link.

More free tools on the tools index.