Agentic AI Use cases

Every payment posted the day it arrives, and every short-pay coded.

Match every incoming customer payment to its open invoices, post it in the ERP the day it arrives, and code each short-pay for the deductions desk.

70%
median auto-match rate across the 15 cash application vendors benchmarked (The Hackett Group, 11 August 2025)
dated source
$15M
of unapplied cash to release at a typical large enterprise (The Hackett Group, 11 August 2025)
dated source
89%
more payments applied automatically at companies that redesign order-to-cash around AI (The Hackett Group, 15 July 2026)
dated source
90% to 97%
straight-through cash application at named adopters, vendor-published (HighRadius, 23 September 2026; BlackLine, 14 April 2026)
dated source
A moment in the day

Where this use case starts

JH
Tuesday 08:10 · finance · the cash queue

J. Harrison, finance lead, opens the cash queue. Overnight Northbay Logistics paid $184,300 against 14 invoices, and the remittance arrived as a PDF in the shared inbox. At 06:30 Juno read it, matched 12 invoices, applied a 2% discount that sits inside terms and posted the receipt in SAP S/4HANA at A4. The accounting document number is on the card.

Two lines are short. The larger one, $6,200, carries the customer’s freight claim number, so on its second pass Juno opened a dispute case with the PDF attached and routed it to the deductions desk. The smaller one, $410, sits inside the write-off tolerance, and the tolerance is hers, so the write-off waits for her as a one-click draft. She approves it.

On Friday she audits a sample, 20 of the week’s 340 postings, each read from its record. This is the A4 scene of the gamut in chapter 3: the agent posts, re-tries and re-routes; the person audits after the fact. Showcase estate; the role is designed, yet to be built.

Why this is a top use case

What the market is doing, with the evidence

Cash application is the only order-to-cash step with two dated analyst benchmarks of its own. Hackett benchmarked 15 cash application vendors and found a median auto-match rate of 70%, same-day matching at 61% of companies and up to $15 million of unapplied cash to release at a typical large enterprise (The Hackett Group, 11 August 2025) 2. Companies that redesign order-to-cash around AI apply 89% more payments automatically and run the process at 52% to 59% lower cost (The Hackett Group, 15 July 2026) 1. Hackett’s 2026 review describes receivables platforms moving to workflows executed by agents with human supervisors (The Hackett Group, 30 March 2026) 3.

The ERP vendors have built it in. SAP made AI payment advice processing generally available with a 70% reduction in document processing effort (SAP, 14 April 2026) 10, and lists a cash management agent for bank statements from the first quarter of 2026 (SAP, H2 2025) 13. BlackLine’s remittance agent processes remittances at about 90% straight-through (BlackLine, 14 April 2026) 27 and is trained on more than $1 trillion of receivables transactions 28.

The named results are vendor-published and high. HighRadius names Kimberly-Clark at 97% straight-through cash application and Johnsonville at 95% (HighRadius, 23 September 2026) 23, and DXP at 90% automation with a 20-day reduction in days sales outstanding (HighRadius, 10 September 2026) 22. Esker reports up to 95% less unapplied cash for its customers (Esker, n.d.) 31, and Gartner’s 2024 assessment of invoice-to-cash applications lists nine vendors that all sell matching automation (Gartner, 6 May 2024) 6. A finance lead recognises the unapplied cash and the lockbox key-in fees at once.

By hand today

How it is done today

Each morning an accounts receivable analyst opens the bank statement and the lockbox file, then hunts for the remittance advice in e-mail, the customer’s payables portal or an EDI 820 message. The analyst identifies the payer from bank details, keys invoice numbers and amounts, applies cash discounts and tolerances, codes short-pays with a reason and posts the receipt in SAP or Oracle.

Payments that fail to match sit as unapplied cash on the customer account and are chased for days, while lockbox banks charge key-in fees for paper remittances. The median company matches 70% automatically and 61% match on the day of receipt; the rest takes one to five working days of analyst time per batch 2.

The cost sits in three places: the analyst hours per 1,000 payments, the bank’s key-in fees, and the cash that stays unapplied while the customer’s account shows an overdue balance it has already paid, which the collections desk then chases.

07:30
Open the filesThe bank statement and the lockbox file arrive; the analyst opens both and lists the payments.
07:50
Hunt for the remittanceE-mail, the customer’s payables portal or an EDI 820 message; for paper, the lockbox key-in.
08:30
Key and matchIdentify the payer from bank details, key invoice numbers and amounts, apply the discount and the tolerance.
10:30
Code the short-paysEach difference gets a reason code and a note for the deductions desk.
11:00
Post what matchedThe receipt is posted in SAP or Oracle; the rest sits as unapplied cash on the account.
Day 2 on
Chase the unappliedCalls and e-mails to the customer, while collections chases an invoice that has been paid.

A cash applier’s morning by hand, and the days after it. Illustrative times; the steps are the ones a receivables desk runs today.

Stage by stage

How Juno enables it

Chapter 6 gave the six stages behind the PO cancellation agent; the same machinery would carry cash application, with the finance objects in place of purchase order lines. Everything in the rows below is a design: the roles sit on the blueprint, and the tense is “would”.

01
Register
Bank statements (CAMT.053 or MT940) and lockbox files (BAI2) from the bank portal and the host-to-host feed; remittance advices as e-mail PDFs, portal downloads and EDI 820 messages; incoming payments, open receivable items and aging, the customer master with bank details, payment terms and cash discounts, short-pay reason codes and unapplied cash items, read in place from SAP S/4HANA receivables and Oracle Fusion Receivables through the data fabric.
02
Map
The ontology objects would be the customer, the invoice as an open receivable item, the incoming payment, the remittance line, the payment terms and the dispute case. A remittance line links to an invoice by number, amount and date, and a payment to a customer by bank details; SAP’s open items and Oracle’s receivables read as one object, the way purchase order lines did in chapter 5.
03
Ask
Two questions a cash applier would type: “How much cash is unapplied today, by customer and by age?” and “Which of Northbay Logistics’ payments this month were short, and by how much?” ChatLima would answer both from the same objects, with the systems it read and the query on show.
04
Teach
The team would add ‘short-pay’ with its reason codes, ‘remit’ as an alias for the remittance advice, and each large customer’s habit of quoting the delivery note number in place of the invoice number. Every match the analyst corrects would teach the next remittance from that customer.
05
Act
Trigger: each bank file and remittance as it arrives, and a sweep at 23:00 for anything still unapplied. Actions: post the payment and clear the matched invoices; apply the discount and the tolerance inside limits; park the remainder as unapplied cash with the reason found; open a dispute case for each coded short-pay. Level: A4 for the matching roles, with exceptions routed to the analyst. Write-back through the released receivables interfaces of SAP S/4HANA and Oracle Fusion; the accounting document number and the clearing status confirm each posting.
06
Learn
The auto-match rate and the same-day share are the measures that would move. Every match the analyst corrects, every write-off the team lead approves and every re-assigned payer would be recorded with the rule version and used, so the next remittance from that customer matches on the first pass; rule discovery would propose a customer’s habits as a new version for J. Harrison to sign.
Cash application policy · designedA4 Autonomousblueprint · designed, yet to be built
Match each incoming payment to the open invoices of its payer where the remittance names the invoice or the amount equals one open item or a sum of open items and the discount taken is inside terms; post the receipt and clear the matched items. For a residual inside the tolerance of $500, draft the write-off for the finance lead. For a residual above $500 with a reason on the remittance, open a dispute case with the evidence attached. For anything else, park it as unapplied cash and ask the analyst.
What it compiles to: the planning table
RowKindWhat it tests or doesData it readsThen
01CheckThe payer is identified from bank details or the remittancebank statement, lockbox file, customer mastercarry on
02CheckRemittance lines match open items by number, amount and dateremittance advice, open itemscarry on
03CheckThe discount taken is inside the payment termspayment terms, invoice date, payment datecarry on
04ActionPost the receipt and clear the matched itemsincoming payment, open itemswrite-back; the document number confirms it
05LimitThe residual against the $500 tolerance, and the reason on the remittanceresidual, reason codeinside: a write-off draft · a reason given: a dispute case · otherwise: to the analyst
Owner: the receivables team leadTolerance $500: J. Harrison, finance leadWould be simulated on last quarter’s payments firstVersion 1, yet to be built

A plausible policy sentence for the matching roles, and the planning table it would compile to. Designed, yet to be built; the tolerance, the floor and the sweep are illustrative settings.

Who does what

The person and the agent, as designed

The agent A4 Autonomous
  • Reads each bank file and remittance as it arrives, identifies the payer and matches the lines to open invoices
  • Posts the receipt, applies the discount inside terms and clears the items; the ERP’s document number confirms each posting
  • Re-tries what stays open on a second pass against the portal and the inbox, then routes it: a case to the deductions desk, a write-off draft inside tolerance, or the analyst’s queue
  • Records every posting with the rule version, the facts as read and the confidence
the record, afterwards; exceptions as they land
The person
  • The accounts receivable analyst resolves matches below the confidence floor, split payments and payer identities the agent could only guess, the same day
  • The team lead approves residual write-offs above the tolerance and any re-assignment of a payment to another customer, from the approval queue
  • The deductions analyst takes over each coded short-pay as a case, with the remittance attached
  • J. Harrison audits a sample each week, 20 of 340 postings, and signs each change to the tolerances and the matching logic

Execute within rules (A3) is the market’s usual level: vendors post matched payments at 90% to 97% straight-through and route the remainder to analysts 23 27, and Hackett describes receivables platforms moving to workflows executed by agents with human supervisors 2 3. Lima’s blueprint designs cash application and matching, and bank and lockbox file ingestion, at A4, and remittance capture and unapplied cash resolution at A3. The difference is the second pass and the re-route: ‘self-corrects’ means the agent re-tries and re-routes on its own, and the audit stays with a person. A client could start the matching roles at A3 and move them up on the recorded cases, the way the PO cancellation agent moved from A2.

What you would configure

The settings on this agent

Agent settings · Cash application and remittance matching
ElementSettingSet byChanges
ObjectivePost every incoming customer payment against its invoices the day it arrives, and code each short-pay for the deductions deskReceivables team lead, in a sentenceNew version
Data scopeBank statements and lockbox files, remittance advices, incoming payments, open items and aging, customer bank details, payment terms and reason codes in SAP S/4HANA and Oracle Fusion ReceivablesA. Novak, data leadNew version
RulesThe matching policy and its planning table, version 1, simulated on last quarter’s paymentsReceivables team lead with the Planner AgentNew version, simulated first
TriggerEach bank file and remittance as it arrives · a sweep at 23:00 for anything still unappliedReceivables team leadAt once
Actions permittedPost a receipt and clear items · apply discount and tolerance · park unapplied cash with a reason · open a dispute case · draft a write-off inside toleranceReceivables team lead, ownerNew version
LimitsResidual tolerance $500 · confidence floor 0.90 for a posting · daily posting budget 600 · two-person rule on any change to customer bank detailsJ. Harrison, finance leadNew version
EscalationBelow the floor or a split payment, to the analyst the same day · a write-off above tolerance or a re-assigned payer, to the team lead · a failed write-back, to the ownerReceivables team leadAt once
LevelA4 Autonomous for matching and file ingestion; A3 for remittance capture and unapplied cash, with the analyst on exceptionsJ. Harrison, finance leadUp on evidence, down in one step
FeedbackEvery corrected match, approved write-off and re-assigned payer is recorded and used in the next cycleAlways onFixed

Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.

Built from the blueprint

The roles this use case would draw on

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.

Blueprint · designed, yet to be builtThese roles are designed on the map. Each is configured from the same parts.
Collect 4 roles
Cash application & matching A4
Bank & lockbox file ingestion A4
Payment portal & remittance A3
Unapplied cash resolution A3

Additional capability in Order-to-Cash lists the rest of the map for this chain.

How it is measured

The measures that show it working

Measure
Auto-match rate: baseline median 70%, top third above 80% [2]
Same-day application: baseline 61% of companies [2]
Unapplied cash: up to $15 million at a typical large enterprise [2]
Straight-through rate: 90% to 97% at named adopters [23][27]
Days sales outstanding: 20-day reduction at one named adopter [23]
Bank key-in fees and analyst hours per 1,000 payments [23]

Baseline the auto-match rate first. It is the number the two Hackett benchmarks give you to compare against, a 70% median with the top third above 80% (The Hackett Group, 11 August 2025), and the other measures follow it: same-day application rises as matching rises, unapplied cash falls, and the analyst hours per 1,000 payments fall with it. Count it from the ERP’s clearing documents for the last quarter before the first run, so the first weeks compare like with like.

Terms on this page
Remittance adviceThe customer’s note of which invoices a payment covers: a PDF, a portal download or an EDI 820 message.
Unapplied cashA payment received and posted to the customer’s account, still unmatched to any invoice.
Short-payA payment below the invoice amount; the difference becomes a residual with a reason code.
LockboxA bank service that receives customer cheques and remittances and sends a daily file of what arrived.
ToleranceThe residual amount below which a difference is written off by rule; above it a person decides.
Questions
Why does the blueprint design this at A4 when the market runs at A3?

The market’s vendors post matched payments and route the rest. A4 adds the second pass and the re-route, and keeps the audit with a person. A client can start at A3 and move up on recorded cases, the way chapter 5’s agent did.

What happens to a payment the agent fails to place?

It is parked as unapplied cash with the reason found and reaches the analyst’s queue the same day, with the candidate invoices the agent considered. The nightly sweep raises it again until it clears.

Does the agent change customer bank details?

It reads them to identify the payer. A change to bank details waits for two named people on any agent whose actions can reach those fields, and this agent’s permitted actions leave them untouched.

Next in this chain
The question this leaves

The payment is posted and the short-pay is a case. Who chases the invoices that were paid late, or stay unpaid, and in what order?

Answered next

Collections prioritisation and dunning

Ranking overdue accounts by cash and likelihood, the right reminder at the right time, and every promise to pay followed to its outcome.

Sources

Dated sources used on this page

  1. [1] The Hackett Group, The Hackett Group Establishes AI World Class Finance Benchmarks (news release), 15 July 2026 (checked 23 September 2026) · https://www.thehackettgroup.com/the-hackett-group-establishes-ai-world-class-finance-benchmarks/
  2. [2] The Hackett Group, AI-Powered Software Is Solving the E-Payments Dilemma: The Hackett Group Reveals Top Cash Application Vendors (news release), 11 August 2025 (checked 23 September 2026) · https://www.thehackettgroup.com/ai-software-e-payments-hackett-cash-vendors/
  3. [3] The Hackett Group, The Hackett Group Identifies Top Collections, Dispute, Deduction Management Software Vendors (news release), 30 March 2026 (checked 23 September 2026) · https://www.thehackettgroup.com/the-hackett-group-identifies-top-collections-dispute-deduction-management-software-vendors/
  4. [6] Gartner, Magic Quadrant for Invoice-to-Cash Applications (document summary page), 6 May 2024 (checked 23 September 2026) · https://www.gartner.com/en/documents/5406263
  5. [10] SAP News Center, SAP Business AI: Release Highlights Q1 2026, 14 April 2026 (checked 23 September 2026) · https://news.sap.com/2026/04/sap-business-ai-release-highlights-q1-2026/
  6. [13] SAP, SAP Innovation Guide H2 2025 (undated), H2 2025 (checked 23 September 2026) · https://www.sap.com/topics/innovation-guide/h2
  7. [22] HighRadius, AI Powered Order to Cash Automation Software (product page, modified 10 September 2026), 10 September 2026 (checked 23 September 2026) · https://www.highradius.com/software/order-to-cash/
  8. [23] HighRadius, Cash Application Software (product page, modified 23 September 2026), 23 September 2026 (checked 23 September 2026) · https://www.highradius.com/software/order-to-cash/cash-application-management/
  9. [27] BlackLine, BlackLine Unveils Agentic Financial Operations to Close AI's Governance and Trust Gap (press release), 14 April 2026 (checked 23 September 2026) · https://investors.blackline.com/news-releases/news-release-details/blackline-unveils-agentic-financial-operations-close-ais
  10. [28] BlackLine, Invoice-to-Cash Automation Software (product page, undated), n.d. (checked 2026) (checked 23 September 2026) · https://www.blackline.com/products/invoice-to-cash/
  11. [31] Esker, Order-to-Cash solutions page (undated), n.d. (checked 2026) (checked 23 September 2026) · https://www.esker.com/business-process-solutions/order-cash/

See Juno answer and act on your own data

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.