Turn every short-pay, debit memo and distributor claim into a case with a reason, its evidence and a validity call, then credit, deny or write it off within policy.
J. Harrison, finance lead, opens a case Juno drafted an hour ago. Helvetia Retail AG short-paid $23,600 on an invoice for material 7741-X and quoted a price-protection claim. The residual came out of Tuesday’s cash application, where it was coded and routed here with the remittance attached.
Juno found the price-change notice of 1 September, the channel stock report at the change date and the credit memo issued in July, and shows them side by side: $21,900 is valid under the programme, and $1,700 duplicates the July credit. It has drafted a credit memo request for $21,900 and a denial letter for $1,700 at A2, with the basis and a confidence on each. Both sit under the thresholds for the channel manager and the controller, so they wait for the desk’s named approver, this week her.
She approves both. The credit memo number and the case status land on the audit trail with the rule version and her name, and the service-level clock on the case stops at 26 hours, against a 90-day habit. Showcase estate; the roles are designed, yet to be built.
Disputes and deductions share the collections benchmark and add the largest named recoveries in the chain. Hackett’s 2026 review of 19 vendors reports an average 8-day improvement in dispute resolution cycle time and up to 57% of staff capacity released, and describes receivables platforms moving to workflows executed by agents with human supervisors (The Hackett Group, 30 March 2026) 3. Companies that redesign order-to-cash around AI resolve disputes 43% faster and halve invoice corrections (The Hackett Group, 15 July 2026) 1.
The 2026 agents are new. SAP’s dispute resolution agent, in beta for its public cloud edition, scans invoices, sales orders, deliveries, pricing agreements and tax rules to find the source of a discrepancy and prepares fixes such as credit memos (SAP, 14 April 2026) 10; a dispute creation agent opens cases from e-mails (SAP, n.d.) 11. Oracle’s claims settlement workspace is built to settle claims faster, shorten cycle time and improve control (Oracle, 9 April 2026) 15.
The named results are vendor-published and large. HighRadius names Kraft Heinz recovering $124 million of invalid deductions a year, Danone North America $25.5 million and Coca-Cola bottlers $33.4 million (HighRadius, 10 September 2026) 25, with 34 days to resolve against a 90-day industry average 22. Esker classifies deductions with its own models and posts approved deductions as credit notes in the ERP (Esker, n.d.) 33, and Emagia reports coding more than 85% of deductions automatically (Emagia, 8 June 2026) 48. For a high-tech manufacturer the same roles would validate ship-and-debit and price-protection claims from distributors.
A deduction begins as a residual item after cash application or as a debit memo or claim file from a distributor or retailer portal. A deductions analyst opens a case, downloads the backup from the customer’s portal, finds the promotion, price-protection notice, ship-and-debit authorisation or proof of delivery it refers to, and compares amounts line by line.
Valid claims go to sales or channel marketing for approval and then to a credit memo request; invalid ones are denied with a letter and re-billed; small ones are written off on the controller’s signature. Each case passes through three or four desks and, by one vendor’s account, takes about 90 days on average to close 22.
The 90 days are mostly waiting: for the backup, for the person who holds the programme terms, for a signature. The comparison itself takes an hour once the three documents are on one screen.
Ninety days by hand, most of it waiting. Illustrative day ranges around a vendor-published average.
The same six stages as chapter 6, with the deductions desk’s objects and the channel programme’s terms among them. Everything in the rows below is a design: the validity call sits on the blueprint at A2, coding and routing at A3, the write-off approval at A0, and the tense is “would”.
One case from the residual on Tuesday to the outcome check in October: the agent’s steps, the limits it checked and the one decision a person made. Showcase estate; designed, yet to be built.
The market runs draft-and-approve (A2) for the validity call and the credit memo, and execute within rules (A3) for capture, coding, evidence retrieval, routing and small settlements: vendors auto-code most deductions, predict validity and post approved credit notes, while write-offs and denials stay with people 10 25 33 48. Lima’s blueprint designs the same split: deduction validity at A2, root cause, routing and credit memos at A3, and the write-off approval at A0, listed so the map stays complete. The badge reads A2 because the decision this page is about, valid or invalid, is the one a named person approves; the coding and the evidence search around it would run at A3 from the first week.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Close every short-pay, debit memo and distributor claim with a validity call and its evidence, and credit, deny or write off within policy | Deductions team lead, in a sentence | New version |
| Data scope | Residuals, dispute cases, claims, deliveries and proof of delivery, price and programme terms, credit memos and write-offs in SAP S/4HANA, Oracle Fusion, the contract repository and the portals | A. Novak, data lead | New version |
| Rules | The validity rules by reason code and programme, and their planning table, version 1 | Deductions team lead with the Planner Agent | New version, simulated first |
| Trigger | A residual after cash application · a claim or debit memo as it arrives · a portal notification · the daily aging of open cases | Deductions team lead | At once |
| Actions permitted | Open and code a case · attach evidence · draft the validity call · draft a credit memo request or a denial · route with a clock · post a write-off inside tolerance | Deductions team lead, owner | New version |
| Limits | Claims above $25,000, to the channel manager · write-off tolerance $500 · confidence floor 0.80 for a draft · a denial to a key account, to the controller · daily budget 150 cases | J. Harrison, finance lead | New version |
| Escalation | Below the floor, to the analyst inside the clock · above $25,000, to the channel manager · a key-account denial or a write-off above tolerance, to the controller · a clock about to run out, to the team lead | Deductions team lead | At once |
| Level | A2 Supervised for the validity call, the credit memo and the denial; A3 for capture, coding, evidence and routing; the write-off approval stays human-led | J. Harrison, finance lead | Up on evidence, down in one step |
| Feedback | Every changed validity call, edited credit memo and duplicate caught is recorded and used in the next cycle | Always on | Fixed |
Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.
Additional capability in Order-to-Cash lists the rest of the map for this chain.
| Measure |
|---|
| Days to resolve: 90-day average against 34 days at one named adopter; 8-day and 43% improvements in Hackett's benchmarks [22][3][1] |
| Invalid deductions recovered: $124 million and $33.4 million a year at named adopters [25] |
| Share of deductions coded automatically: above 85% at one vendor [48] |
| Open case aging against service level |
| Write-off rate and duplicate claims caught |
| Staff capacity released: up to 57% [3] |
Baseline days to resolve first, by reason code. It is the number both the vendor figure (90 days as an industry average, 34 at one adopter; HighRadius, 10 September 2026) and the Hackett benchmarks (8 days and 43% better; 30 March and 15 July 2026) speak to, and it separates the waiting from the work: the evidence search and the validity call would be the agent’s, the approvals stay people’s, and the clock on each case shows which is which. Take it from the cases closed in the last two quarters, from the open date to the clearing document.
A named person, always. The denial is a draft with the basis and the evidence; the analyst or, for a key account, the controller approves it before the letter goes and the amount is re-billed.
It reads the earlier credit memos for the same customer, material and period and shows the match on the case. The duplicate is a draft denial with the earlier document beside it; the person decides.
From the contract repository and the channel programme records registered in the first stage. A term that lives only in someone’s inbox is the first thing the team would add.
The claim was valid because the order had shipped at the old price. Where did that order come from, and who let it ship while the account was over its limit?
Orders read from PDFs and portals, created with confirmed dates, and the credit, delivery and data blocks cleared with the evidence on the card.
Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.