AI agent · Finance & accounting · Match & reconcile
Cash application
The software links each customer payment to its remittance advice, finds the invoices it pays and applies the cash when the match is unambiguous. Short payments become deduction cases with the evidence attached; unidentified payments go to a person.
Typical volumes for this process, not a client figure.
Payments land in the bank; someone works out which invoices each one pays.
Matched to open invoices using the remittance; short payments and unknown payers go to a person.
Where the time goes today
Customer payments arrive on the bank statement with a payer name, an amount and a short reference field, often truncated by the banks along the way. The detail of what is being paid arrives separately: a remittance advice by email, a download from the customer's supplier portal, a few lines inside the payment message. A cash application analyst identifies the customer, finds the invoices and applies the cash in the receivables ledger.
The easy payments quote one invoice number and the exact amount. The hard ones take the time. One payment covering eighty invoices. A parent company paying for six subsidiaries. A payment short by an unexplained amount because the customer deducted a promotional allowance, a damaged delivery or a price it disputes. A remittance that arrives three days after the cash. An invoice number with two digits swapped.
Unapplied cash then sits on account. Collections teams chase customers who have already paid, credit holds land on customers who are up to date, and deductions are discovered weeks later, when the evidence to challenge them is hard to find. At month end, the pressure to clear the unapplied balance produces misapplications that have to be reversed the following month.
How the agent works
- Read the paymentThe agent takes each bank statement line and links any remittance that arrived by email, portal or inside the payment message. Payments without a remittance wait for a period you set before the agent works from the bank line alone.
- Identify the customerIt identifies the customer from the payer account, name variants and the history of who pays for whom, including parent companies and payment centres.
- Match to open itemsIt uses invoice numbers from the remittance first. Where there are none, it looks for the combination of open invoices that adds up to the amount, preferring invoices the customer has paid together before.
- Handle the differenceFor a short payment it reads the remittance for a deduction reason, codes it and opens a deduction case with the remittance line attached. Small differences within your tolerance are handled by your write-off rule; overpayments stay on account.
- Apply or holdExact and unambiguous matches are applied in the receivables ledger. Everything else stays unapplied, with the proposed match and the reason it was not applied.
What stays with a person
Deductions need a person: validating the customer's claim, accepting or disputing it, and talking to the customer. So do unidentified payments, which may be misdirected and need returning, and refunds of overpayments, because money leaving the business is not something the agent does.
Write-offs above your tolerance and any change to a customer's payer relationships are also a person's decision. The agent proposes, with the evidence on screen; the analyst confirms or corrects, and the correction is kept for the next time the same pattern appears.
What it reads, what it produces
| It reads | It produces |
|---|---|
| Daily bank statements | Cash applied in the receivables ledger, with the matching evidence stored |
| Remittance advices from email, customer portals and payment messages | Deduction cases with the remittance line attached |
| Receivables open items and customer master data | An unapplied list with the proposed match and why it was held |
| Customer hierarchies and known payer relationships | A daily tie-out of bank receipts to applications |
| Deduction reason codes and your application rules |
Controls that come with it
- Automatic application only when invoice references match, or when exactly one combination of open invoices fits the amount; if two combinations fit, a person chooses.
- Differences above your tolerance are never written off automatically.
- Every application records its evidence and can be reversed through the standard unapply function.
- A daily check that cash received equals cash applied, held unapplied and left on account.
- Refunds are never issued by the agent.
How you know it works
- Share of cash applied on the day it arrives
- Unapplied cash balance and its age
- Misapplications reversed each month
- Days from short payment to deduction case
- Collection contacts with customers who had already paid
Is your process ready?
- Written rules: how to apply partial payments, which invoices take priority and how deductions are coded are documented.
- Systems: bank statements arrive as files or through an interface, the receivables ledger accepts applications through an interface, and the remittance mailbox can be read.
- Cheap check: each application can be verified against its remittance line in seconds, and reversed if wrong.
- Volume: hundreds or thousands of payments a day, with remittances in many formats.
- Same description: every regional team treats partial payments and deductions the same way.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Forcing a match before the remittance arrives, when waiting a day would have given the answer.
- Combination matching on customers with many invoices of the same amount, where several sets fit.
- Deduction codes too coarse to support recovery later.
- Payment centres paying for many unrelated customers without any reference.
Questions we get
Our ERP already has auto-matching rules. What is different?
Rules handle payments that carry a clean invoice reference, and if most of yours do, keep the rules. The agent is worth considering when a large share of cash is left for analysts because the detail sits in remittances of every format, in payer relationships the rules do not know, or in deductions that need reading. It works alongside the ERP, applying through it.
What happens to deductions?
Each short payment with a reason in the remittance becomes a deduction case with the reason coded and the remittance line attached, opened on the day the payment is applied. Short payments with no reason stay unapplied for a person. Deciding whether the deduction is valid, and disputing it with the customer, remains with your team.
Can it apply cash to the wrong invoice?
Yes, and that is why it applies automatically only when the evidence is unambiguous. Each application stores the remittance line and the rule used, so a wrong one is found quickly and reversed through the normal unapply function. Misapplications are tracked monthly, and a weekly sample of automatic applications is re-checked by an analyst.
How long does it wait for a remittance?
As long as you decide, set per customer from how late that customer's remittances have arrived in the past. While it waits, the payment shows as received but unapplied, with a note that a remittance is expected. After the wait, the agent works from the bank line and open items, and holds anything ambiguous for a person.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.