Apply every payment, with nothing left in suspense.
Remittances arrive as PDFs, emails, spreadsheets, or not at all. Karini AI agents apply each payment by your SOP and show exactly where any payment stalled.
- Written for
- Controller
- Also in the room
- AR manager and cash application team
- Governed by
- Cash Application Exception Handling SOPCA-OPS
DSO rises even when customers pay on time.
The payer isn't in the customer master. The amount matches several invoices, or none. A short pay comes with a one-line reason.
Until someone reconciles it by hand, cash sits unapplied, with no record of why.
The agents, in the order they run.
Eight agents run in order, from reading the remittance to posting. Each logs its output, so a stalled payment shows exactly where it stopped.
When a person decides, the decision feeds back into the chain, so the audit trail never breaks.
See it in action.
A held payment opens with the remittance, the proposed match, the variance, the deduction reason and the SOP rule that held it. The reviewer fixes the match, rules on the deduction or reassigns the payer.
The agents finish posting, and the payment closes with one audit trail.
Variance is a range, not a yes or no.
Within 2% and no dispute, the payment applies automatically. Between 2% and 5% with a clean history, a named approver decides. Above 5%, or when invoices don't add up, it holds.
These rules come from a reference SOP. On your ERP, you set the thresholds in your SOP.
Cash application rules
| Scenario | When it applies | Decision | Approval | SOP section |
|---|---|---|---|---|
| The payment matches the invoice amount exactly | AUTO_APPLY | No approver required | Cash Application Scenario Dispatch | |
| Payment variance at or below 2%, with no dispute flags | AUTO_APPLY | No approver required | Cash Application Scenario Dispatch | |
| Payment variance 2% to 5%, with clean customer history | ESCALATE | Level 2 | Cash Application Scenario Dispatch | |
| Payment variance above 5%, or several invoice references that do not resolve | HOLD | Level 3 | Cash Application Scenario Dispatch | |
| A dispute flag is raised, or the account has chargeback history | HOLD | Level 3 | Cash Application Scenario Dispatch | |
| No invoice reference, or the remittance could not be identified | ESCALATE | Level 4 | Cash Application Scenario Dispatch | |
| The payment exceeds the invoice total by more than 10% | HOLD | Level 3 | Cash Application Scenario Dispatch |
AUTO_APPLYCash applied and posted by the agent.ESCALATESent to the approver at the level the SOP sets.HOLDNothing moves until the blocking condition clears.How to get started.
Four steps. Only the first needs your process owner.
Review your SOP with a Karini AI engineer
Our forward deployed engineer works with your process owner and queue team to turn your SOP into a clear spec: rules, thresholds, approval levels and gaps.
The gaps matter most. Where your SOP is silent, the queue is being worked from memory.
You bring
The SOP that governs the process today, in whatever state it's in.
Connect the workflow and your ERP
Your SOP becomes the workflow the agents follow. We connect through APIs, governed screen access where there's no API, and email intake.
Your ERP stays the system of record. Nothing is migrated or replaced.
You bring
An environment to connect to, and the person who owns access.
Test against your own history
Every rule runs on your past exceptions first. You see which rule each case hit, and fix the SOP where it's wrong.
Fixing it here costs an SOP edit, not a reversal.
You bring
A sample of closed cases, including the awkward ones.
Deploy to production
Live in your environment, behind your approval levels, with the audit trail on from day one.
The next use case starts at step one with its own SOP, not a new project.
Bring your SOP. We'll run it against your queue.
Pick one use case. If the rules are written down, agents can follow them. If not, we write them together in the first session.
