A disputed invoice is cash you've earned and can't collect until someone fixes the problem.
Log every disputed invoice the day it is raised: customer, invoice, amount, reason, owner and target date. Route it to the team that can fix it, such as sales for pricing or operations for delivery, and track it to resolution with a credit note, a corrected invoice or confirmation that it is payable. Report disputes by reason each month and fix the most common causes.
Disputed invoices sit in receivables, push up DSO and often end as write-offs simply because nobody owned them. The customer won't pay until the problem is fixed, and credit control can't fix pricing or delivery problems alone.
A shared Excel log, one row per dispute:
| Column | Content |
|---|---|
| A | Date logged |
| B | Customer |
| C | Invoice number |
| D | Disputed amount (may be part of the invoice) |
| E | Reason code: price, quantity, quality, not received, duplicate, PO missing, other |
| F | Owner (named person) |
| G | Target resolution date |
| H | Status: open, awaiting customer, resolved |
| I | Outcome: payable, credit note, re-invoice |
Flag overdue disputes:
=IF(AND(H2<>"Resolved",TODAY()>G2),"OVERDUE","")
Summarise the log monthly by reason code with a pivot table. If most disputes are about missing purchase order numbers, fix the invoicing step. If they are about price, check that sales and billing use the same price list. Fixing the top two reasons usually removes most disputes.
Credit notes reduce revenue and receivables, so they need approval by someone other than the person who raised them, within authority limits. A rise in credit notes, or credit notes just after month end, deserves a look. See the credit control policy.
Flag disputed invoices on the aging report, so credit control doesn't chase them as ordinary late payments. Report disputed balances separately in the month-end pack, with the value over 30 and 60 days, so management can see how much cash is stuck. The payment reminder templates cover the undisputed part.
Most disputes come from a small number of avoidable errors: a missing purchase order number, a price that doesn't match the quote, a delivery that was short, or an invoice sent to the wrong contact. A short pre-invoice check for large invoices, and a customer master that records each customer's invoicing requirements, prevent many of them before they start.
The process is the same in both countries. Keep written records of dispute resolution: they matter if a debt later goes to formal recovery.
Applies the payments your customers make to the invoices they are paying, including part-payments and one payment for several invoices, and shows what is still owed. Runs in your browser on your own computer: nothing is uploaded.
Work out DSO and the cash tied up in late payers. Free to use online.
The Credit Control & Receivables System calculates ageing, DSO, best-possible DSO and CEI from the ledger, shapes a bad debt provision to IFRS 9 / ASC 326 logic and requires independent approval for credit limits and write-offs. Excel, no macros, one-time price.
Consider them separately. A dispute that will end in a credit note reduces revenue rather than being a bad debt, so estimate the likely credit as well as the collection risk.
The team that can fix the cause: sales for price disputes, operations for delivery or quality, billing for invoice errors. Credit control tracks it to resolution.
Yes. Ask for payment of the undisputed amount straight away, and resolve the disputed part separately.
Set a target in your policy, often a couple of weeks for simple disputes. Anything past target should be escalated.
Last updated 21 October 2026. General guidance for finance teams; check it against your own policies, systems and local rules.