Key takeaways
- Cash application is the step that matches an incoming payment to the open invoices it pays; an AI agent reads the remittance, proposes the match, and posts it only under rules finance sets.
- Every headline figure we found is a vendor claim: HighRadius reports 98% of payments auto-applied for one customer, and Agicap says matching runs 'often at rates above 90%'.
- Microsoft's Dynamics 365 Finance has a 'Require review before posting' setting, and Business Central labels each automatic match Low, Medium or High confidence, so approval can be a setting, not an afterthought.
- Short payments and missing remittance are the hard cases: Darwin AI says someone 'has to ask the customer what it covers', so the agent drafts the question and a person owns the answer.
- Test any vendor or custom agent on your own last quarter of payments before you trust a match rate, and keep a named person on the exception queue.
Cash application is the step that matches a customer payment to the open invoices it pays and posts the result to the ledger. An AI agent does the reading and matching, sends doubtful cases to an analyst, and posts only under rules finance sets. This 2027 guide gives six signs your team needs one, using sources read in November 2026.
For the wider picture, see our AI workflow automation guide and read our finance IT solutions guide. For the collections side, see our accounts receivable automation software post.
What is cash application, and how does an AI agent do it?
Cash application ties each incoming payment to the invoices it settles. Agicap (September 2026) says AI "uses machine learning and optical character recognition (OCR) to read remittance data from almost any source." An agent goes further than a rule: it reads, scores, proposes, and hands the unclear ones to a person.
The agent follows six steps, and the six signs below map to them. Every explainer we opened is from a vendor, a partner or a consultancy, so treat the numbers as vendor claims. BufferSol built a similar read-match-approve-post pattern for payables in its intelligent invoice processing case study, and our AI accounting software post covers the wider category, and our AI bookkeeping post shows the same agent idea on the books.
- 011 IngestCollect remittances from email, PDFs, portals, bank files and EDI
- 022 NormaliseCheck files are complete, clean the fields, drop duplicates
- 033 MatchScore each payment against open invoices by invoice number, PO, customer and amount
- 044 RoutePost high-confidence matches, queue the rest for an analyst
- 055 PostWrite the payment and settlement to the ERP with an audit trail
- 066 LearnCapture each analyst correction so the next match improves
BufferSol Technologies · buffersoltech.com
Which sources describe cash application agents, and how far can you trust them?
Only some of them are neutral, and none gives independent accuracy data. Microsoft's two documentation pages describe rule-based cash application in Dynamics 365 Finance and Business Central, and they are first-party. The rest are commercial pages from HighRadius, Agicap, Kolleno, Darwin AI, Zone & Co, LeewayHertz and Cleverence.
The table shows what each kind of source can and cannot tell you.
| Source type | Example | What it is good for | What to watch |
|---|---|---|---|
| ERP documentation | Microsoft Learn | Exact settings, review steps, limits | Describes rules, not AI |
| Vendor blog | HighRadius | Workflow ideas, named features | Figures are the vendor's own |
| Software firm or partner | LeewayHertz, Cleverence | Operating models, design advice | Not the ERP maker's statement |
| Standards listing | Stedi | What the EDI 820 message is | Says nothing about AI |
1. Do remittances reach you in five different formats?
If they do, you have the first sign. An agent's first job is to collect remittance data wherever it lands and read it. Cleverence (April 2026) says "Remittances may come via email attachments, EDI 820 transactions, customer portals, or payment gateway exports." Zone & Co says "Customer payment details rarely arrive in one clean format."
EDI is one of those formats. Stedi describes the 820 as a transaction set that "can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice", and its invoice-level detail sits in the RMR segment, "Remittance Advice Accounts Receivable Open Item Reference". A PDF in a mailbox needs reading; an 820 needs parsing. HighRadius says its agent "pulls remittance data in real-time, even from PDFs or scanned images". That is a vendor description of capability, not a measured result.
What the agent does: it watches the mailbox, portal and bank file, reads each remittance, and writes one clean record per payment. Choose it if you receive more than two remittance formats. Skip it if nearly all customers pay by one format already tied to an invoice number. Our AP automation overview shows the same intake idea on the payables side.
2. Does an analyst still key payments against open invoices by hand?
That is the second sign. Matching is where the agent saves the most hours, because the rules are repeatable. Cleverence recommends "defining matching hierarchies: try invoice number first, then PO, then customer + amount", with tolerances and safeguards. Kolleno says "Machine learning models learn from your historical data" and "predict how to match payments even when key details are missing."
Microsoft shows what a documented hierarchy looks like. In Business Central, "First the function tries, in prioritized order, to match text in the five Related-Party fields", then "text in the Transaction Text and Additional Transaction Info fields" against document numbers, and "Last, the function tries to match the amount." The page adds that "Text matching is only possible for text longer than four characters." That is a rule engine with a stated order, which an AI agent can sit on top of.
Agicap says tools match payments to invoices "often at rates above 90%". The page names no study for that number, so we treat it as a claim. Choose it if analysts spend most of the day on matching routine payments. Skip it if volume is a few dozen payments a month. Our accounts receivable software questions post lists what to ask a vendor.
3. Do short payments and deductions sit in unapplied cash?
This sign is the costly one. Cash that cannot be matched stays unapplied, and the customer still shows as owing. Darwin AI (August 2026) says "Payments arrive without remittance detail, or with remittance sent separately by email" and "When a payment arrives short or without remittance, someone has to ask the customer what it covers." It adds "Exceptions are where cash application meets customer communication".
Agicap says "When a customer pays less than the invoice amount, the system does not simply flag a generic variance." Its page says AI models assign reason codes to deductions such as early settlement discounts and route them to the appropriate team. HighRadius reports "92% of short payments identified without intervention" in one Keurig Dr Pepper case study on its own page. That is a single-customer vendor figure, so test it on your own data.
LeewayHertz is clear about who decides: "Deductions analysts decide whether a deduction is valid, invalid, recoverable, or requires a customer dispute." So the agent proposes a reason code and drafts the customer question, and a person rules. Choose it if short pays are a visible share of your queue. Skip it if customers pay in full and on time.
4. Does posting to the ERP depend on one person's know-how?
If it does, the fourth sign is key-person risk. Zone & Co says "Matching only helps if the result lands in your system of record cleanly." Posting is where an agent has to respect the ERP's own rules, and Microsoft's documentation shows limits worth knowing before you design anything.
In Dynamics 365 Finance (page dated July 2026), "When you apply cash in advanced bank reconciliation, only journal names without approval workflow are supported." A rule that generates a customer payment can be set up so it "doesn't settle the customer payment journal with the matched customer invoice". That is a design choice: post the cash first, settle later. If your journals carry an approval workflow, an agent built on that path will not fit, and you would need a different posting route.
Business Central shows another safeguard: "When you use automatic application, Business Central recognizes bank ledger entries that have already been posted, which helps prevent double-posting." It also lets you reverse a payment applied to the wrong customer, after you "un-apply the posted customer ledger entries". Our AI invoice processing post shows the payables twin of this flow. Our bank reconciliation automation post covers the bank side, and our account reconciliation post the ledger side.
The NetSuite picture is thinner. Oracle's own help page returned an error when we tried it, so the only NetSuite material we read is a partner's guide: Cleverence says it is not an Oracle page. Choose it if only one person knows how cash posts. Skip it if posting is already fully documented and covered.
5. Can nobody say who approved a match, or why?
That is the audit sign. A match that posts without a record is a control gap. Cleverence says to "Implement controls that auditors love: role-based access for rule edits, change logs with timestamps and approvers", plus evidence that high-value exceptions get a second review. Zone & Co shows an audit trail kept at every step in its workflow diagram.
Microsoft turns approval into a setting. Dynamics 365 Finance says its preview feature "allows users to review and approve reconciliation matching rule results before transactions are posted and marked as matched." With the "Require review before posting" parameter set to Yes, results "appear on the Bank reconciliation worksheet > Pending review tab", and users with permission can Approve or Reject. The page notes "You can't edit customer and vendor payment journals" in that tab, so you must reject and recreate.
Business Central labels each automatic match Low, Medium or High and has a "Review Required" field per rule. HighRadius describes the same split in its own words: "High-confidence matches are posted automatically, medium-confidence matches are routed for analyst review". The table below sets the approval points side by side.
| Step | Who decides | What the source shows |
|---|---|---|
| Read remittance | Agent | LeewayHertz: AI "does not decide, approve, or attest" |
| Confirm extracted evidence | Cash application analyst | LeewayHertz: analysts confirm before it supports a posting |
| High-confidence match | Agent, under finance's rules | Zone & Co: finance sets when a payment can post alone |
| Medium or low match | Analyst | Business Central: Low confidence lines need review |
| Short pay, deduction | Deductions analyst | LeewayHertz: analysts decide validity |
| Write-off, credit memo | Finance approver | LeewayHertz: approvers own these decisions |
6. Do analyst corrections vanish after the month ends?
That is the sixth sign. If a fix to one customer's pattern is not remembered, the same exception returns next month. HighRadius says "When a cash application analyst makes a correction, the Agentic AI captures not just the change," and describes learning from analyst corrections. That is the vendor's description, not a tested result.
A custom agent can do the same in a plainer way, as BufferSol view: write each correction to a table that holds the customer, the payment text, the invoice chosen and who corrected it. The agent reads that table before scoring the next payment, and a person reviews the table monthly. Kolleno says its tools "get better at handling edge cases—like partial payments, short payments, or vague remittance advice" over time. We would test that claim by comparing exception counts month to month on your own data. Our AI agent evaluation post shows how.
Choose it if the same customers cause the same exceptions every month. Skip it if exceptions are one-offs.
| Rule-based matching | AI agent matching (vendor description) | |
|---|---|---|
| Remittance input | Fields in a bank file, matched on text | Reads PDFs, scans and emails too |
| Incomplete detail | Falls to manual | Suggests likely matches |
| Short payment | Flags a variance | Proposes a reason code |
| Posting | Posts or queues by rule | Posts high confidence, queues the rest |
| Learning | Someone edits the rules | Captures analyst corrections |
Source: Microsoft Learn, HighRadius, Agicap, Zone & Co and Kolleno pages as read in November 2026. Right column is vendor description, not measured results.
BufferSol Technologies · buffersoltech.com
How much analyst time does a review queue take?
It depends on the share of payments that need a person. As a BufferSol calculation, with assumed numbers to show the method: say you receive 1,000 payments a month and an analyst needs 5 minutes for each one sent to review. If an agent auto-applies 90%, the share Agicap calls "often" achievable, 100 payments go to review, which is about 8 hours. If it auto-applies 70%, 300 go to review, which is 25 hours.
The point is the gap between the two cases: a 20-point difference in the auto-apply rate moves the queue from about 8 to 25 hours a month. Neither the 90% nor the 70% is a measured result for your company, so count your own with a test. HighRadius reports 98% auto-applied for one customer, which would mean 20 payments in the same 1,000. That is a vendor figure from a single case study. Our financial close automation post shows how this feeds the month-end timeline.
How do you test a cash application agent on your own payments?
Run it on a quarter of history where you know the right answer. The steps below are BufferSol view, written as a verb-first test:
- Pull three months of bank lines, remittances and the invoices they paid.
- Hide the answers, then run the agent in suggest-only mode.
- Count correct matches, wrong matches and no-match cases at each confidence level.
- Sort the wrong matches by cause: format, missing detail, short pay or customer pattern.
- Time how long an analyst needs for each queued item.
- Set the auto-post threshold only where wrong matches are zero or tiny, and log the number.
- Re-run monthly, and after any change to customer terms or remittance formats.
A suggest-first start is the safest, as BufferSol view: the agent writes proposals to a separate field before it posts anything, and our human-in-the-loop post explains the pattern. Our workflow exception handling post shows how each exception gets an owner.
Which questions should you ask a cash application vendor in writing?
Ask these before you sign and keep the answers:
- Which remittance formats do you read, and which do you not (EDI 820, PDF, portal, email body)?
- How do you score a match, and can we see the score for every line?
- What happens to a low-confidence match: does it post, queue or fail?
- Can we set the auto-post threshold per customer or per amount?
- How do short payments become dispute cases, and who sets the reason codes?
- Which ERP journals can you post to, and which are unsupported? (Microsoft's page says only journal names without approval workflow are supported in one path.)
- Can we export every match, score and approver for audit?
- Can we test on our own history before go-live? Our AI vendor security questionnaire and data processing agreement post cover data handling.
What does a cash application agent not do?
It does not decide credit, approve write-offs or know about a promise made on a phone call. LeewayHertz puts it plainly: "AI extracts and enriches remittance data but does not decide, approve, or attest." It also cannot fix a customer master with duplicates, and it will not know that a customer paid the wrong entity.
It can match wrongly with confidence, and a wrong match corrupts aging until someone un-applies it. Business Central shows the cost: you must un-apply the posted entries and reverse the register. Plan for a named person to own the exception queue, the rules table and the monthly review. Agicap says "exception handling that once required a person increasingly happens on its own" over time, which we read as a trend to measure, not a promise.
What do the sources not show about AI cash application?
They show vendor claims and no independent accuracy study. Of the pages we opened, only the two Microsoft Learn pages are first-party, and they document rules, not AI. HighRadius, Agicap, Kolleno and Darwin AI all sell finance software or AI agents.
Agicap's "DSO reductions of 20–40%" is also a vendor figure. The page says "Teams that automate cash application commonly report" it, and names no study, so we leave it as a claim. None of the pages describes a custom build, none gives an error rate for wrong matches, and the NetSuite material is from a partner, not Oracle. The Darwin AI page cites survey figures from a third party that we did not open. Our intelligent invoice processing guide shows how we test claims like these, and our AI readiness assessment helps you check your data first.
What changes in 2027 for cash application?
No source we opened forecasts the cash application market in 2027, so this section is BufferSol view, written as reasoning.
We expect buyers to ask for review-before-posting as a standard setting, because Microsoft's page shows it arriving in Dynamics 365 Finance from version 10.0.46. We expect confidence labels like Business Central's Low, Medium and High to become the common language between finance and auditors. And we expect more teams to want their own correction table, since vendors such as HighRadius already sell learning from corrections. Plan the 2027 budget around a pilot on one entity or one customer group.
When should you build your own cash application agent?
Build when remittances and ERP rules are particular to you and a packaged tool does not fit. Stay with your ERP's own matching plus a clean customer master when volume is small. For a software view, see our best accounting automation software post.
No source we opened covers custom builds, so this is BufferSol view:
- Your customers send formats no tool reads, such as bespoke PDFs or portal exports.
- You run more than one ERP or entity, so no single matching rule sees every invoice.
- You need approvals in your own tools, with named approvers and your own thresholds.
- You need your own audit log in a format you control.
BufferSol's autonomous workflows service builds these. See also how long it takes to build an AI agent, AI agent architecture and touchless invoice processing.
What would a 30-day pilot deliver?
In 30 days you get a working cash application agent on your real payments, with a person on the exception queue. The plan:
- You bring: read access to your ERP or AR ledger, a quarter of bank lines and remittances, your customer master export, your current matching rules and a named approver.
- We build, in about two weeks: a prototype that reads your remittance formats, scores matches against open invoices, writes proposals to a review queue and drafts the customer question for short pays, tested on your last quarter.
- We launch, in the final stretch: a live pilot on a first slice, such as one entity or customer group, with a log of every match, score and approver and a weekly review.
Success is measured by correct matches, wrong matches caught before posting, queue time and analyst corrections. The closest ready-made version is our collections and accounts receivable automation, built for finance teams. See also the Done For You catalogue, month-end reconciliation and invoice processing. Our duplicate invoice detection post and expense report audit automation show how the same review pattern works elsewhere.
Is this right for you?
Check how many describe your team:
- Remittances arrive in three or more formats.
- Analysts match payments to invoices by hand every day.
- Short payments and unapplied cash age in a queue.
- You can name who approves a match and where it is logged.
- You can pull last quarter's payments to test an agent.
If few apply, clean the customer master and your matching rules first, then pilot. Teams with questions about the wider role of AI in finance can read our AI for accounting firms post.
Facts checked November 2026 on the HighRadius, Agicap, Zone & Co, Kolleno, Darwin AI, LeewayHertz, Cleverence and Stedi pages and the Dynamics 365 Finance and Business Central (automatic application, rules) documentation; vendor pages are marketing. Facts we did not re-check: Oracle NetSuite's own cash application help page (it returned an error), Nacha and treasury ACH addenda pages (not readable), the BillingPlatform survey that Darwin AI cites, and any accuracy figure that is not a vendor's own.
If cash application is eating your team's week, ask BufferSol for a scoped estimate for a cash application agent on your payments now, so the 2027 budget includes it and the pilot can start in Q1 2027.
Frequently asked questions
What is cash application automation?
Cash application automation is software that matches incoming customer payments to the open invoices they settle and posts the result to the ledger. Agicap says AI uses machine learning and OCR 'to read remittance data from almost any source'. An AI agent adds reading messy remittances, proposing matches for incomplete data and routing doubtful ones to an analyst.
How does AI match a payment when remittance detail is missing?
It scores likely matches from what is available. Zone & Co says 'AI suggests likely matches when payment details are incomplete', and Kolleno says models 'predict how to match payments even when key details are missing'. Both are vendor descriptions. A low-confidence match should go to a person, not post on its own.
Does the AI post cash to the ERP without approval?
Only if finance allows it. Zone & Co says 'Finance sets the rules for when a payment can post on its own and when it needs review.' Microsoft's Dynamics 365 Finance page describes a 'Require review before posting' parameter that sends rule results to a Pending review tab for approval or rejection.
What happens to short payments and unapplied cash?
They become exceptions. Darwin AI says 'When a payment arrives short or without remittance, someone has to ask the customer what it covers.' Agicap says AI models assign reason codes to deductions and route them to the right team. A custom agent can draft the customer question while an analyst decides.
Are the match rates vendors quote reliable?
Treat them as claims to test. HighRadius reports 98% of payments auto-applied from one customer case study on its own page, and Agicap says rates are 'often' above 90%. Neither is an independent benchmark. Run any tool, or a custom agent, on your own historical payments and count correct matches, wrong matches and exceptions.
Sources
- How Agentic AI Improves Accuracy and Speed in Cash Application, HighRadius
- How AI-Powered Cash Application Software Automates Payment Matching, Agicap
- Cash application software: How AI speeds matching and posting, Zone & Co
- How AI is Used in Cash Application, Kolleno
- Cash Application Automation: How to Eliminate Unapplied Cash, Darwin AI
- AI for cash application: Use cases, operating model, and agentic workflows, LeewayHertz
- Cash application in advanced bank reconciliation - Finance | Dynamics 365, Microsoft Learn
- Automated Cash Application in NetSuite: Setup, Rules, and Best Practices, Cleverence
- Reconcile payments using automatic application - Business Central, Microsoft Learn
- Rules for automatic application of payments - Business Central, Microsoft Learn
- EDI 820 Payment Order/Remittance Advice (X12 004040), Stedi
Cite this article
BufferSol Editorial Team (2026). Cash Application Automation: 6 Signs You Need an AI Agent in 2027. BufferSol Technologies. https://buffersoltech.com/blog/cash-application-automation-2027
BufferSol Editorial Team
AI & software engineering team
Senior engineers, AI specialists and product leads at BufferSol Technologies who design, build and run AI agents, autonomous workflows and custom software for companies in the US, UK and Europe.
Reviewed by Sufyan K., Senior Writer, BufferSol Technologies.
