AFS ProCash Application
Reads the statement, works out who paid, matches it to the invoices and applies the cash.
- Bank, lockbox and remittance intake
- Payer and invoice matching
- Unapplied cash and reversal
New Watch the agents work before you let them act
All the work around
All the work around
getting paid, handled.
AI agents that read your bank files, match the cash, chase what is late and fight the deductions — and show you exactly what they did, every time.
14-day trial · no credit card · your ledger stays yours
Receipts today1,284+6.2%
Matched by agent91%+4 pts
Needs a person38
Unapplied$412K
PAY-4C0A1Costco Wholesale
Matched$242,329.42
PAY-8F758Short pay · 2% term
On account$58,110.00
PAY-21B0CAmount only — no payer
Unidentified$9,999.99
Accounts receivable
Five agents, one ledger
Each one owns a job somebody used to do by hand, and hands the rest back with its working shown.
Collections
Works the overdue book the way a collector does — by customer, not by invoice.
- Strategies per segment, not one ladder
- Promise tracking that pauses the chase
- Replies read, disputes routed on
Deductions
Pulls the retailer's claim, checks it against the carrier's receipt, files the dispute.
- Claim intake from portal exports and EDI
- Proof of delivery pulled and compared
- Per-retailer filing rules and deadlines
Credit & Risk
Scores the account before the order ships, and recommends the limit rather than quietly setting it.
- Behavioural scoring from your own ledger
- Exposure against limit, live
- Order release and hold within policy
AR Intelligence
Predicts the date each invoice will actually be paid, rolls that into a 13-week cash forecast, and flags the accounts whose behaviour just changed. Ask it in plain language and it answers from your ledger, not from a model's memory.
How it works
Money arrives. The rest is already done.
The same four steps your team runs today — only the agent has run them before anyone opens the queue.
Step 1
It arrives
Bank statements, remittance emails, lockbox scans, retailer claim reports. Whatever shape it comes in, and twice without becoming twice the money.
BAI2MT940camt.053EDI 820CSV · XLSX
Step 2
It gets matched
Who paid, which invoices, what the difference is. An amount that happens to line up is not a match, and is not treated as one.
rules firstmodel aftertolerances
Step 3
What is late gets chased
A strategy per segment — who, in what order, through which channel — stopping the moment the customer promises or disputes.
emailSMSWhatsApppromise to pay
Step 4
What is short gets fought
The claim is read, the delivery proof pulled, the dispute prepared for that retailer's portal — with its deadline in view.
POD · BOLreason codesEDI 812
Cash Application
It will not guess whose money this is
A payment that matches an open invoice by amount alone tells you nothing about who sent it. Plenty of customers owe round numbers.
- A match resting on the amount alone is capped low and stays unidentified
- Every receipt records what it was matched on, and what it was not
- A remittance that turns up after its money pairs itself up on arrival
PAY-4C0A1Matched$42,329.42
Matched onRemittance reference + exact amount
InvoiceINV-30014498%
PAY-8F758Unidentified$9,999.99
Matched onAmount only — eleven customers owe it
Confidencecapped at 0.3030%
Target CorporationIn dispute
Overdue$1,742,880
Oldest123 days
PromiseBroken 4 OctEscalate
Next actionHand 6 invoices to Deductions
StrategyDay 3 reminderDay 14 firmDay 30 call
Collections
Nobody rings the same customer thirty-seven times
A case per invoice is the right unit to track and the wrong unit to work. The worklist is the customer, because that is who gets the call.
- Every row says why it is in front of you today
- A disputed invoice is never chased for payment — it goes to Deductions
- A promise pauses the strategy; a broken one restarts it harder
Deductions
The deadline is the whole game
Past a retailer's dispute window the money cannot be recovered however good the evidence is. So the date drives the queue, not the amount.
- Claims read straight from the portal's own export, in whatever columns it uses
- Shortage claims checked against the carrier's signed delivery receipt
- Each retailer's filing rules encoded — what they need, and how long you have
APDP-99100141 days left$4,120.50
Their codeSHRT — shortage on receipt
Carrier239 of 239 delivered, signed for
VerdictEvidence contradicts the claim
FilingPacket ready · POD, BOL, invoice
Trust & control
Watch it work before you let it act.
Three settings, per agent. You move when your own numbers say to, not when a salesperson does.
Shadow
It changes nothing
The agent works everything out and touches no record — not the status, not the queue, not a balance. Its answer sits in its own column beside yours, so you can score it against what your team actually did.
Assisted
It prepares, you release
Every action is worked out and held. Nothing is applied until a person approves it, and until then the record says exactly that.
Autonomous
It acts, inside your limits
Within the confidence, value and tolerance ceilings you set. Anything outside them still comes to a person, whatever the agent thinks.
Built for people who get audited
Not a wall of badges — the controls that are actually in the product.
Tenant isolation
Row-level security in the database, enforced on every query rather than remembered in application code.
Separation of duties
Submit and approve are different rights, and never both held over your own request.
An immutable trail
Who did what, and when — with agent actions recorded apart from people's.
Nothing posts twice
Idempotent write-back to your ERP, and reversal inside the window you set.
Integrations
It reads what you already have
No new format to produce, no export to maintain. Hand it the file your bank or your retailer already gives you.
Your ledger
SAPOracleNetSuiteDynamics 365QuickBooksCSV · XLSX
Your banks
BAI2MT940camt.053PlaidDaily SFTP fetch
Retailer portals
Retail Link · APDPVendor CentralPartners OnlineSupplier portalsEDI 812
Carriers & outreach
POD / BOL lookupsEmailSMS · WhatsAppClick to pay
Accounts payable
And the payables deskPlanned
The same shape, pointed the other way. In build — honest about not being in your hands yet.
Supplier
Onboards a supplier and holds a bank-detail change until somebody independently verifies it.
AP Invoice
Matches a supplier invoice to the PO and the receipt, and routes whatever does not tie.
AP Payment
Proposes the run against terms and discounts, respects the approval tiers, releases what is cleared.
AP Control
Hunts duplicates and payments split to slip under an approval ceiling.
Pricing
Start free for 14 days
No card to begin. What separates the plans is where your data sits — and how much of it you keep here.
Starter
One workspace alongside everyone else's, isolated row by row. For a team putting its first agent to work.
$499/month
Shared database
- 2,000 transactions a month — payments, claims and accounts worked
- 2,500 customers and 25,000 invoices
- 5 people
- Cash Application and Collections
Growth
Your own schema in the shared cluster: your own tables, and every AR agent switched on.
$1,999/month
Dedicated schema
- 25,000 transactions a month
- 25,000 customers and 400,000 invoices
- 25 people
- Every AR agent, including Deductions and Credit
Enterprise
Your own database. Nothing of yours shares a process with another company, and the volume ceilings come off.
Talk to us
Dedicated database
- No volume ceilings
- Unlimited people, SSO
- Every agent, AR and AP as it ships
- A named person who knows your ledger
Every plan starts with the same 14-day trial, and the trial runs in shadow if you want it to — the agents work everything out and change nothing. Hitting a ceiling never locks you out of your own ledger: reading, approving and finishing what is open all keep working, and what pauses is taking in more.
Run it beside your team for two weeks
In shadow mode it changes nothing and records what it would have done. At the end you have a number of your own, not a pitch.