Receivables Recovery Agent
Chases what is actually collectable, in the order that gets you paid
- 8hard rules
- Things it must never do, enforced in every run
- 5handover rules
- Conditions where it stops and gives the work to a person
- 9output fields
- A structured result, not a paragraph you have to re-read
- ≤5steps per run
- Bounded work: at most 4 tool calls, enforced by the runtime
Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.
Overview
Collections tools run one ladder for everyone: a reminder at seven days, firmer at fourteen, a final notice at thirty. That is the problem. A customer who always pays at fifty-five does not need chasing at seven, and one who is three days late for the first time has lost the invoice — a firm letter turns a good account awkward for nothing.
This agent ranks by what is collectable. It reads each customer's own payment history, so a late invoice from a reliable payer is treated differently from one from a customer who has slipped every quarter, and it puts the largest genuinely-overdue balances at the top rather than the oldest.
And it separates late from wrong. A large share of overdue invoices are not a collections problem at all — a purchase order is missing, a line is disputed, the address is wrong. No reminder collects those, and every one sent damages the relationship. Those go to a different list with what to fix. It drafts each message in your tone and sends none of them: what leaves under your name, to your customer, is your decision.
Benefits
Cash in sooner
By chasing the invoices that will actually move.
Relationships intact
Nobody chased for an invoice that was wrong in the first place.
The wrong invoices fixed
Which is the only thing that ever collects them.
What it does
Ranks by collectable, not by oldest
The largest genuinely overdue balance first. A date-sorted list chases the wrong invoice every morning.
Separates late from wrong
A missing purchase order or a disputed line is not a collections problem, and no reminder will ever collect it.
Reads each customer's own rhythm
Fifty-five days from someone who always takes fifty-five is not late in any useful sense.
Escalates by history, not by day count
First-time slip and fourth-quarter-running are different situations and get different words.
Flags the account worth protecting
Where the customer's value makes a firm chase the expensive option.
Sends nothing
What goes out under your name to your customer is your decision, every time.
What this changes
What this changes about your week
- It takes over
- Deciding who to chase this week and writing each message.
- Done today by
- Whoever least wants to do it, which is why it slips.
- How often
- Weekly, and it is the week it slips that hurts.
- Typical manual effort
- Working an aged ledger properly is a morning a week.
Why Finance & Accounting in particular. Collections tools run one ladder for everyone. A third of overdue invoices are not late but wrong — a missing PO, a disputed line — and no reminder ever collects those, while every one sent damages the account.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Receivables Recovery Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.
How it runs
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
- 1InputValidated against the agent input schema
- 2Modelclaude-sonnet-5 with automatic fallback
- 3Toolsextract_structured_data
- 4PermissionsRuns READ actions automatically; anything higher waits for approval
- 5OutputStructured result matching the output schema
- 6LoggingTokens, duration and every step recorded
Demo
Demo dataIllustrative sample output, abridged.
Input
{
"currency": "USD",
"invoices": []
}Output
{
"chase": [
{
"rank": 1,
"tone": "light",
"draft": "…",
"amount": 31400,
"customer": "Harbour Logistics",
"reference": "INV-2291",
"whyThisOrder": "Largest balance that is genuinely late. 34 days against their own median of 21, and they have paid on time nine times before — this is unusual for them, which makes it likely to move.",
"lateAgainstTheirNorm": "13 days beyond their normal rhythm."
}
],
"escalate": true,
"disclaimer": "Drafts and priorities from your own records. No message has been sent, nothing has been written off, and nothing here is a legal demand or a statement that a debt is enforceable.",
"unknownStatus": [
"INV-2199 — no record of contact or dispute. Ask whether delivery was ever confirmed before chasing."
],
"notActuallyLate": [
"INV-2260, Meridian — 48 days, and their median is 52. Chasing them costs goodwill and buys nothing."
],
"escalationReason": "One customer represents 31% of receivables, above the exposure threshold.",
"notLateJustWrong": [
{
"problem": "No purchase order number on the invoice; their AP system rejects invoices without one.",
"toFixIt": "Reissue with the PO from the order confirmation. No reminder will collect this one.",
"reference": "INV-2244"
}
],
"protectTheAccount": [
"Harbour Logistics is 31% of your annual revenue. A firm chase here is the expensive option; the draft is deliberately light."
],
"likelyUncollectable": []
}Requirements
Integrations
No integrations required.
Before you start
- Your overdue invoices
- Payment history per customer
- Any disputes or queries on the account
- Requires the Starter plan or higher
Use cases
Weekly collections run
Who to chase, in what order, with the message drafted.
A cash squeeze
The shortest path to the most money.
Cleaning an aged ledger
Which balances are collectable and which need fixing or writing off.
Pricing
Starter
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits
FAQ
Will it send the chases?
No. A collections message goes to a customer under your name and can damage a relationship worth far more than the invoice. Every draft waits for you.
Does it threaten legal action?
Never. Threatening proceedings, interest or an agency is a decision with legal consequences and rules about how it may be worded. It flags the account and stops.
How does it know an invoice is wrong rather than late?
From your own records — a raised dispute, a missing purchase order, a bounced delivery, a query on the account. Where the records do not say, it marks it unknown and suggests the question to ask.
Reviews
Reviews open once customers have run this agent.
Need this agent to work differently?
Tell us what to change and our team will scope a customised version for your business.
Customize this agent