How to Get a Customer to Pay a Disputed Invoice

To get a customer to pay a disputed invoice, separate the contested line from the uncontested balance, get the balance into the next payment run, and turn the contested part into a claim with a named owner, a defined scope and a response date. Monk is an AI-native invoice-to-cash platform that runs invoicing, AP portal submission, collections and cash application as one system, so a query raised in an email thread becomes a tracked exception against a specific invoice line rather than a note somebody half remembers. Most disputes are not refusals to pay. They are requests for evidence, raised by someone who cannot approve the invoice and has no deadline for answering you. Given a scope, an owner and a date, a dispute usually closes in days.

The shape of it is familiar. An invoice goes out on net 30, and on day twelve an accounts payable analyst replies that the rate does not match what was agreed. The invoice moves to a hold status and nothing else happens. Your ageing report shows the amount sliding into the 60 day bucket, your notes say "customer disputing", and the analyst has moved on to the next exception in her queue. The money sits behind a question nobody has been asked to answer by a date.

Why does one contested line hold up the whole invoice?

Accounts payable platforms approve, hold and pay an invoice as a single document, so a query against one line freezes the full amount until the exception is cleared.

In Coupa, SAP Ariba, NetSuite or Sage Intacct, your invoice is matched against the purchase order and, for goods, the goods receipt. When a line falls outside the match tolerance, the status changes to something like "exception" or "pending requester approval", and the weekly payment proposal skips it. The requisitioner who could clear it may not know it exists, because the notification sits in a queue she reviews on Fridays.

The fix is to stop treating the document as indivisible. Ask the AP contact one question: can the uncontested lines be released in this week's payment run while the query on line four stays open? Some AP teams can approve a partial payment directly. Others cannot, because their configuration requires the approved amount to equal the invoice total, and there the answer is a credit note for the contested line and a reissued invoice for it alone.

Record whichever route you take where the buyer works. If the invoice went through a supplier portal, put the credit note and the rebill through the same portal and add a case comment quoting the original invoice and purchase order numbers. Email to an analyst's personal mailbox does not update the record the payment run reads.

Which of the five dispute types are you dealing with?

Every dispute reduces to one of five claims, price, quantity, quality, terms or authorisation, and each has a different owner and a different document that closes it.

A price dispute says the rate billed does not match the rate agreed. It comes from the rate card in the master services agreement, the unit price on the purchase order line, an uplift applied without a countersigned change order, or an annual increase that never reached the buyer's contract record. Procurement owns this one.

Quantity disputes say you billed for more than was delivered: more hours than the approved timesheet shows, more units than the delivery docket records, more licences than the account holds. They are the easiest to close, because the counting evidence sits in a system both sides can see. Quality disputes say the work arrived but not to specification, and those move slower because an operational manager owns the decision.

Terms disputes concern the due date, payment terms, an early settlement discount, tax treatment, currency or retention, and they usually mean two documents disagree, with the contract saying net 45 and the purchase order saying net 60. Authorisation disputes are the most common in large organisations: no purchase order was raised, the order was closed or exhausted, the cost centre is wrong, or the requester has left. The invoice is correct and still unpayable.

Ask the buyer to state which of the five applies, in writing, with the line and the amount. One question does most of the work: which line, what amount, and what would you need to see to release it?

What evidence closes each type of dispute?

One document, sent to the person who owns that decision, closes most queries in a single exchange.

Package the evidence as one PDF rather than five attachments, named so it survives being forwarded twice, using the invoice number, the purchase order number and the word "evidence". Repeat the summary in the body of the message, because the approver often reads on a phone and will not open an attachment.

Where the buyer runs a portal, upload the same file against the invoice record and repeat the summary in the case comment. Portals are where the status lives, and 92% of enterprise invoices must be submitted through a vendor portal or network rather than paid from an emailed invoice, measured across the receivables Monk manages.

Who at the buyer can release the payment?

The person who raised the dispute is rarely the person who can clear it, and the invoice stays frozen until your evidence reaches someone with authority.

Six roles matter. The AP analyst processes the document and raises the query but cannot approve outside tolerance. The AP supervisor can release partial payments and adjust match tolerances. The requisitioner, usually the manager who asked for the work, approves the exception in the workflow and is the most important name to obtain. Procurement owns the contract and the purchase order value, and the financial controller owns the payment calendar.

In organisations running a shared service centre, your query becomes a ticket with an SLA measured in business days. Ask for the ticket reference, put it in the subject line of everything you send, and ask which team it went to. A ticket with a reference gets worked.

Get the name by asking plainly. Who owns the approval on this exception, and what is their email address? Most analysts will tell you, because clearing the exception moves it off their queue too.

How do you escalate without damaging the relationship?

Escalate the process rather than the person, and give the current owner a dated chance to close the item before you go above them.

Escalation works in four steps. Send a written summary separating the contested amount from the uncontested balance, and ask for the balance in the current payment run. Attach a specific date for a decision on the contested part, with a reason. Copy your own account owner so the relationship is informed rather than surprised. Only after the date passes, write to the AP supervisor or the budget holder's manager, reciting the timeline without characterising anyone.

Contract remedies are legitimate and can be stated as facts: interest under late payment legislation, suspension of further work under the service schedule, the notice provisions in the agreement. Name them late, once, and without adjectives. Here is a message you can adapt for the second step.

Subject: INV-2043 / PO 4500118872, uncontested balance and one open query. Hi Priya, thanks for flagging the rate on line four. To keep this moving I have split the invoice in two. Lines one to three and five to nine are not in question, so please can that portion go into Thursday's payment run. If your system cannot part pay, tell me today and I will raise a credit note for line four and reissue it separately.

On line four, attached is the countersigned change order setting the revised day rate, with the purchase order line showing the same figure. If something there does not match your record, tell me which document you are working from. I need a decision by Friday next week so the amount does not roll into a further ageing bucket, and I have copied Daniel who runs the account. Who owns the approval on this exception in Coupa?

When should you concede?

Concede when the cost of proving the point exceeds the contested amount, when the evidence you would need was never captured, or when the account is worth more than the line.

Work out the carrying cost with real numbers. A contested line consumes credit control time, account manager time and often delivery time to reconstruct what happened. Where the evidence depends on a sign off nobody obtained, or a verbal agreement between two people who have both left, you will not win it.

Concede in one movement rather than in stages. Issue the credit note with a reason code, state that the credit is a commercial decision on this occasion, and ask for a payment commitment on the balance in the same message. Concessions offered week by week teach a buyer that pressure produces discounts.

Then fix the cause. Nearly every conceded dispute traces to something upstream: a rate card never loaded into the buyer's contract record, work started before the purchase order was raised, a delivery accepted without a signature. Code the reason on the credit note and review the codes by customer each quarter. Edge cases of this kind cause 39% of cash flow slowdown.

How does Monk handle this?

Monk treats a dispute as a structured exception on a line rather than a status on a customer, and keeps the uncontested balance moving while the contested part is worked.

When a reply arrives saying the rate is wrong, Monk's Intelligent Collections reads the thread and classifies the item against the invoice and line it concerns. Julia, Monk's AI agent for Intelligent Collections, ingests the context of the conversation, so the next message acknowledges what the customer said instead of repeating the last reminder. That context is why Julia sees a 24% higher response rate than standard dunning, and why 90% of collections resolve with zero human intervention.

Monk's AI cash application matches 80% of receipts automatically, rising to 95% with suggested matching rules, which counts when a buyer pays short and leaves the disputed line outstanding. Monk works with QuickBooks, NetSuite, Salesforce, HubSpot and Stripe, is SOC 2 Type II compliant, and manages $2B+ in accounts receivable. Teams report a 40% average reduction in DSO and 26 hours a month saved.

Where should you start?

Spend an hour this week on every invoice marked as disputed, answering four questions for each.

What is the contested amount, and what is the uncontested balance? If you cannot produce the split in two minutes, the dispute has never been scoped. Which of the five types is it? Who owns the approval at the buyer, by name and email? What date have you given them, in writing?

Most teams find a third of their disputed items have no named owner and no date. Those are unanswered questions ageing in someone else's queue. Send the uncontested balance request today and the evidence pack tomorrow. To see the same triage run automatically against your open ledger, book a demo.

Frequently Asked Questions

Can I ask a customer to pay the undisputed part of an invoice?

Yes, and ask in your first reply rather than after a fortnight of argument. Many AP teams can approve a partial payment against a held invoice, and where their configuration prevents it, the workaround is a credit note for the contested line and a separate invoice for it. Name the lines that are not in question and the payment run you want the balance in.

How long should I give a customer to resolve a dispute?

Set a date rather than a duration, and tie it to the evidence you have provided. Ten business days from the moment the pack reaches the named approver suits price and quantity queries, and longer for quality disputes needing an inspection. Say why the date matters, for example that the amount will otherwise move into a further ageing bucket. A date with a reason gets answered.

What if the customer will not tell me what is wrong with the invoice?

Send the five categories and ask them to pick one. A message asking whether this is a price, quantity, quality, terms or authorisation query, and which line it affects, is easier to answer than a request for their concerns. With no reply, contact the requisitioner who received the work, since they know what happened operationally. On a portal, check the status field for a rejection code.

Should I stop work while an invoice is disputed?

Check the contract first. Most service schedules allow suspension after a defined notice period for undisputed sums that remain unpaid, and using that clause for an amount under live dispute can put you in breach. Where the dispute covers one line and the rest is overdue without explanation, the undisputed part is usually a valid basis for notice. Involve your account owner before sending anything.

Does a disputed invoice still accrue late payment interest?

That depends on the contract and the jurisdiction, and in most cases a sum under live dispute is treated differently from one unpaid without explanation. The uncontested balance continues to fall due on the original terms. Rather than arguing about interest early, use it as a factual reminder that the clock is running. Reserve any formal claim for after the dispute is resolved.

Who should own dispute resolution, credit control or the account manager?

Credit control should own the process, the timeline and the evidence, while the account manager owns the relationship and any commercial concession. Splitting it this way stops the account manager becoming a collections channel and stops credit control making pricing decisions they cannot authorise. Copy the account manager on escalations from the start so nothing surprises them at renewal.

How do I stop the same dispute happening every month?

Code every credit note and resolved dispute with a reason, then review the codes by customer once a quarter. Recurring price disputes usually mean an agreed uplift never reached the buyer's contract record, and recurring authorisation disputes usually mean work starts before purchase orders are raised. Fix the upstream artefact, whether that is a rate card, a change order template or a rule that no work begins without a PO number.