How to Handle Invoice Disputes and Deductions
.png)
When a customer disputes an invoice or takes a deduction at payment, the disputed amount stops moving until someone works the case. Most of what makes these cases recoverable happens in the first few days, while there's still time to gather evidence and file before the customer's appeal window closes. This post covers:
- how to spot disputes and deductions early
- how to decide which cases to work first
- what evidence wins them
- when to escalate
Undisputed balances should keep moving through collections the whole time.
How do disputes, deductions, and short pays differ?
A dispute is a customer challenging an invoice or one of its lines. When the customer instead subtracts an amount on their own at payment, that's a deduction. Any payment that arrives for less than the invoice total is a short pay, whether or not the customer gives a reason. Our post on short pays and deductions covers the common deduction types in detail.
The working rule is the same for all of them. Separate the disputed amount into its own case and keep collecting the rest of the invoice on its normal schedule.
How do you catch disputes and deductions early?
The sooner you find an exception, the more time you have to gather evidence and appeal. A case found during month-end reconciliation has often already lost a few weeks.
Signals to check every day:
- customer replies that mention a missing PO or a pricing problem
- payments in cash application that don't match an open invoice
- rejection messages from AP portals such as Coupa or Ariba
- partial payments that clear for less than the invoice total
Rules you can set up this week:
- Route every customer reply to one shared collections inbox.
- Flag messages that contain words like "dispute," "short pay," "deduction," or "credit."
- Have cash application open a case automatically when a payment covers less than 95% of an open invoice.
- Check your largest customers' AP portals each day for rejected or held invoices, and give each one an owner the same day.
In Monk, cash application matches 80% of payments automatically, rising to 95% with suggested rules. Payments that don't match, including short pays and claimed discounts, go into a cash exceptions queue where someone can review and assign them. When a customer raises a dispute in an email or on a call, Monk opens a dispute case linked to the invoice and the original conversation.
How do you decide which cases to work first?
A $200 pricing disagreement with two months left to appeal and a $40,000 promotional deduction that expires in five business days need different handling. Sort the open queue by dollars at risk and by days left before the dispute window closes.
| Window closes in under 10 days | Window open more than 10 days | |
|---|---|---|
| High dollar (over $5,000) | Work today, escalate if needed | Schedule for this week |
| Low dollar (under $5,000) | Batch-process today | Standard queue |
Adjust the thresholds to fit your average invoice size and team capacity. Every open case should sit in one of the four boxes. If a high-dollar case with a closing window goes two business days without progress, move it to a senior owner.
What should every case record include?
Keep the record short and the same for every case. It should have the reason code, amount at risk, invoice number, owner, date opened, resolution deadline, and the status of the evidence. Over time, reason codes show patterns, such as one customer repeatedly short-paying over PO mismatches. The amount at risk can feed straight into your cash forecast. Our guide to managing invoice disputes has a fuller template.
How should cash application and collections hand off short pays?
This handoff is where deductions most often get lost. Cash application should flag the gap and leave the unpaid balance open. Collections then confirms with the customer what the deduction is for and moves the case forward.
In practice, cash application never writes off an unmatched amount. It leaves the balance open and tags it with a suggested reason. Collections reviews tagged items within one business day and confirms or corrects the reason. From there it either opens a dispute case or keeps following up on the undisputed part. Reminders on the undisputed amount keep running while the disputed line is handled separately.
In Monk, short pays and deductions are classified by reason automatically, with a review step to confirm or correct the classification. For allocating partial payments, see our post on handling partial payments in AR.
What evidence wins disputes?
Disputes are usually won with documentation you can produce quickly. Here's what to have ready for the most common types:
- PO mismatch: the original purchase order and signed proof of delivery or service.
- Pricing disagreement: the contract or price list in effect on the invoice date, plus any amendment or quote the customer acknowledged.
- Quality dispute: inspection reports and any written correspondence with the customer about the issue.
- Receipt dispute: shipping confirmation with tracking and signed proof of delivery.
Large retailers and enterprise buyers often set strict appeal windows, sometimes 30 days from the deduction date. Record each customer's window in the case and set a reminder at least five business days before it closes.
When should you escalate to sales, ops, or legal?
Use fixed triggers so the decision doesn't come down to judgment each time. Common ones:
- an amount above your AR team's approval limit
- a case past its deadline
- a customer who disputes repeatedly
- a dispute that depends on contract language
When you escalate, send the full history: communications, evidence, the case record, and what you're asking for, such as a credit memo or a re-invoice. Credit memo approvals should have a named owner and a faster path for cases close to their deadline. Pre-approving small credit memos up to a set amount also saves days.
How do you measure whether it's working?
Track amount at risk, recovery rate, average days to resolution, and write-off rate. Report them monthly in terms of cash and DSO so the CFO can see the effect. Our post on AR dispute KPIs explains how to calculate each one.
Across our first 100 customers, Monk has reduced DSO by more than 40% on average and saved teams about 26 hours a month.
| Customer | Result |
|---|---|
| ElevenLabs | 60% reduction in overdue AR in 30 days |
| Profound | 122% more cash on hand in month one |
| Elate | DSO cut in half, collections doubled |
| Unify | 50%+ cut in overdue Stripe AR |
What can you change this quarter?
Most of the gains come from a few process changes rather than a large project.
- Days 1 to 30: Set up the detection rules and daily triage, and assign an owner to every new case within 24 hours. Start tracking the KPIs above at the same time.
- Days 31 to 60: Write standard evidence templates and escalation packets, and agree on SLAs with sales and ops.
- Days 61 to 90: Review reason codes to find repeat customers and adjust the matrix thresholds. Report the quarter's recovery rate to leadership.
For connecting dispute handling to the rest of your collections workflow, see our guide on how to automate collections.
Monk handles dispute and deduction cases alongside cash application and collections. If you want to see how it would work with your own invoices, book a demo.
Frequently Asked Questions
How do I decide whether to dispute a deduction or accept it?
Compare the amount against what it costs to gather evidence and appeal. If the deduction is small and the relationship is good, accepting it and adjusting the contract for future invoices can make more sense. For larger deductions, dispute within the appeal window.
How do we stop deductions from expiring before we appeal?
Find them sooner. Open cases automatically from cash application mismatches and set a reminder five business days before each customer's appeal deadline. High-dollar cases should have an owner within 24 hours.
How should we set SLAs between AR, sales, and operations?
AR owns triage and evidence gathering, with a target of two business days. Escalations and approvals need their own response times, plus a faster path for small credit memos. Review how well the SLAs are being met each month.
How do you keep an audit trail when automation handles cases?
Log every automated action with a timestamp and the rule that triggered it. Human overrides should also leave a logged note. Together, these give you a record that holds up for internal controls and external audits.
Which reports show the dispute process is returning cash?
Start with recovery rate and net cash impact, meaning recovered dollars minus the cost of the team's time on disputes. Report them monthly alongside average days to resolution and write-off rate. If recovery and write-offs are both rising, the team may be closing easy cases while harder ones expire.
How can a team of one or two people keep up with deductions?
Use the dollar and deadline matrix so you only work the high-impact cases by hand. Automate case creation and evidence assembly, and pause reminders on disputed lines. Monk's AI collections agent, Julia, reaches customers with a 24% higher response rate than standard dunning.
What should we keep to defend a deduction six months later?
Keep the original invoice and PO, proof of delivery or service, all customer communication about the dispute, and the case record. Include any internal approvals or credit memos. Store everything in one searchable place so anyone on the team can reconstruct what happened.
.avif)