The reminder for the disputed freight
What the user reports
Brennock's accounts payable is on the phone again. When they paid BWU-PO-5733, they told Calder's customer service that they won't pay the 255.00 of freight on it, because their own truck collected the pumps. Customer service said it would look into it. Last week Brennock got a Reminder for exactly that 255.00. The next dunning run is due, and it would send them a Second reminder.
The error: Brennock received a dunning Reminder for its residual item of 255.00 (freight disputed, reason FRT), and the next run proposes a Second reminder for the same item.
What you'll do
- See the problem as the accounts receivable accountant: On Dunning, propose letters with the run date three weeks after the residual item's due date. The run must keep Brennock's disputed 255.00 out of every letter and list it as held by a dispute case.
- Find the cause: Dunning keeps disputed items out of its letters. Why did Brennock's 255.00 get a Reminder, and why is the next run about to send a second?
- Fix it as the customer service representative.
- Prove it: run the step that failed again.
The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.
Answer and explanation (open after the drill)
The fix: The dispute lives only in a phone call: there is no dispute case on the item, so to the dunning run it is an ordinary overdue item.
A dunning run reads the books, not the phone log. It keeps an item out only when a dispute case is open on it; a reason code on the item says why it was left open, not that someone is working it. Holding the letter covers one run, and the next run proposes it again. The interval only spaces the letters out; it never decides whether an item is chased. Opening the case, with an owner, keeps the item out until the case closes.
Why it broke
The dispute was real but lived only in a phone call. A residual item's reason code says why it was left open; only an open dispute case tells the dunning run that someone is working it. So the 255.00 aged like any late item, and the letters followed the levels.
How teams prevent it
Whoever takes a customer's dispute opens the case before the call ends, with an owner. A worklist of residual items with a dispute reason and no case, checked before every dunning run, catches the rest.
Across teams
Customer service took the call, accounts receivable ran dunning, and Brennock's accounts payable got a letter that said nobody had listened. The credit manager now has a dispute and an annoyed customer instead of only a dispute.
Where AI fits
Extract and assist: a model reading inbound emails and call notes can spot a dispute and propose the case on the right item, with its reason; the owner confirms it. The dunning run's own rule, no letter while a case is open, stays plain automation.
Learn more: Order to cash end to end