- Before
- Spends half the day finding the PO, the amendment and the delivery proof across five places, then writes the reply from scratch.
- Now
- Opens each case with the proof pack built and a decision proposed, asks the agents what they would ask a colleague, and approves, edits or rejects with a reason.
A $27,360 price question on a $316,200 invoice, settled by the contract
A customer, a diagnostics laboratory group, says one invoice overbills 228,000 sterile sample tubes by $27,360. Here is how the AR specialist works the case with the agents, asking them questions in plain words, opening each source they cite and approving the answer, screen by screen in the working solution.
A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.
- 01Wednesday morning
The agents worked the queue overnight and wrote a brief
AR specialistThe AR specialist's home screen says the agents worked the 24 open disputes overnight and read 6 new ones: 10 need the specialist ($71,422 disputed), $244,790 is in dispute, 4 answers are due this week and 9 were resolved this week for $30,470. The Needs you list is in the order the agents suggest (answer date, then amount), and beside it is the report writer's morning brief, each line with its source.
“Biggest today: the lab group, $27,360 on price. The invoice is right: their PO missed the latest amendment.”
- 02After the brief
A question to the brief, in plain words
AR specialistUnder the brief is an ask box: "Ask about any dispute, customer or credit". The specialist asks what is due this week. The report writer answers in the thread: four answers are due by Friday. One is due today and sits with the AR manager; two are due Friday, both waiting for sales; and one more is due Friday with its reply ready. One is past due and sits with the controller.
Suggested questions sit under the box: “What is due this week?” · “Which credits need the AR manager?” · “Why so many price disputes?”
- 03Overnight arrivals
New disputes from each channel, read and linked to the line
Intake reader · ClassifierSix arrivals since 17:00 yesterday: from email, a customer's supplier portal, the company's own dispute form, a call note from customer service and a short payment from cash application. One lab customer's email is linked to line 2 of its invoice at 0.95 confidence, $1,140 disputed, and the classifier proposes Short delivery, owner the AR specialist, answer within 10 business days, reminders paused on $1,140 only. A duplicate and a "not a dispute" are flagged; one short payment is marked "Check the reading".
“Your call. Nothing is opened until you accept.”
- 04The customer's email
One case: the customer's thread on the left, the proof pack on the right
Customer AP leadThe customer's AP lead writes that the invoice bills the tubes at $1.37 while their PO says $1.25, and that they are holding the invoice. Two minutes later the intake reader has linked it to line 1 and paused reminders on the $27,360 only; the undisputed $288,840 stays due on its due date. The classifier calls it a price dispute, owner the AR specialist, with an answer date, and an acknowledgement goes to the AP lead under the acknowledgement rule. Twelve minutes in, the decision agent, at 0.96, says the invoice is right: the latest amendment sets $1.37 for deliveries shipped on or after its start date, the order shipped after it, and the customer did not object to the acknowledgement at $1.37 within 5 business days.
Each agent message shows its confidence and numbered citations to what it read. Credit owed $0; $316,200 to collect by the due date.
- 05Ten minutes in
Eight items, each checked against the disputed line
Proof gathererThe proof gatherer pulls 8 items from the ERP, the contract repository, the carrier and the mailbox: the customer PO at $1.25 (their claim), the supply agreement, the latest amendment, the order acknowledgement, the carrier's proof of delivery, the ERP price list, earlier invoices and a CRM note. The specialist opens the amendment: signed by the customer, it applies to all deliveries shipped on or after its start date, whatever the date of the purchase order.
“Kept with the case · highlighted text is what the agent used.”
- 06One question today
A second agent that could have disagreed, and one question for sales
Contract checker · Sales account managerThe contract checker, working on its own at 0.97, agrees: the price follows the ship date, not the PO date; notice was 31 days against the 30 required by §4.5; and 950 cases × 240 = 228,000 tubes. It flags one thing for a person: a CRM note that the customer's buyer asked whether $1.25 could hold until the next quarter. The specialist clicks "Ask the account manager", and the sales account manager answers in the thread. The checker's last line now reads that sales confirmed no price hold was agreed.
“No. I checked, and we did not agree a price hold. The customer knows. Go ahead, and copy me.”
- 07The draft
The reply in the customer's terms, and the next dispute found
Reply and credit drafter · Root-cause analystThe drafter has written to the AP lead, copying the customer's buyer and the account manager, using their PO number and portal reference. It attaches the amendment and the order acknowledgement, asks the customer to release the invoice for payment of $316,200 by its due date, and prepares the same answer for the customer's supplier portal, where the invoice shows "On hold". The specialist can edit it in place or tell the agents in plain words: "Make the reply softer", "Copy the AR manager". Below it, the root-cause analyst has found four open POs from the same customer that still say $1.25 (516,000 tubes, $61,920 at risk of the same dispute), drafted a heads-up to the buyer, and added the case to the root cause "price changes not reaching customer POs".
The drafter drafts only. Nothing is sent until the specialist approves.
- 08Before signing
The question the specialist would ask a colleague
AR specialistThe specialist types "What if a price hold was agreed?" into the case. The contract checker answers at 0.95, with two citations: a price hold agreed in writing would override the amendment for the orders it covered, and the $27,360 would become a credit, above the specialist's limit, so the AR manager would sign it. Nothing in writing exists: the CRM note only says the buyer asked, and sales confirmed no hold was agreed.
Anything that changes an amount, a credit or what is sent still comes back to the specialist first.
- 09One decision
Approved with a reason, the signature recorded
AR specialistThe specialist clicks Approve and send. The dialog states exactly what goes out (the reply to the AP lead, copying the buyer and the account manager, with the amendment and the acknowledgement, posted on the customer's supplier portal, no credit) and asks for a reason: "Invoice correct, contract price applies". A note for the record is optional. No credit is involved, so it is within the specialist's authority; a credit above $10,000 would go to the AR manager instead.
“Signed by the AR specialist, with the date and time · kept in the audit trail.”
- 10Sent · answered
Sent, posted and followed up
Proof gathererThe thread records the reply sent to the AP lead with the buyer and the account manager copied, the answer posted on the customer's supplier portal with 2 attachments, and the heads-up on the four POs sent to the buyer. The case reads "Answered · waiting for the customer", and the proof gatherer will read the customer's portal and the bank receipts on Friday, their next payment run.
“Reply sent and posted on their portal. The proof gatherer checks their payment run on Friday.”