AR Cash Collector
Chase every unpaid invoice. Never email a customer who already paid.
A daily AR aging cockpit that proves an invoice is genuinely open — in integer cents, with zero AI in the math — before it ever drafts a reminder. Every reminder is supervised, number-checked against your ledger, and waits for your approval. B2B, first-party only.
How a reminder gets out the door
Read the books
Open invoices from QuickBooks / Xero; captured payments from Stripe + your accounting.
Prove it's open
A deterministic engine matches cash to invoices in integer cents. Paid, partially paid, disputed, or in-flight → never dunned.
Draft, supervised
A reminder in your voice. Every figure is re-checked against your ledger; a second AI from a different vendor reviews it for collector / threat language.
You approve
Nothing sends on its own. You approve from the queue; a final freshness re-check aborts if the invoice was paid since the draft.
The cardinal rule
One false reminder to a paying customer can cost the relationship. So we don't send one.
The dunnability decision is pure arithmetic — captured payments and credit memos applied to invoices in integer cents, with no language model anywhere in the math. An invoice is only ever marked safe to dun when the open balance is provably greater than zero at high confidence. Anything ambiguous — a lump-sum wire with no remittance, an in-flight charge, a partial payment — is held for a human, not guessed. Chaser, Tesorio, and Growfin send reminders too; the difference is the false-dun proof underneath ours.
What it does — and won't
An explicit scope. The role refuses out-of-scope work instead of improvising.
Does well
- Daily AR aging across QuickBooks / Xero, bucketed by days overdue.
- Deterministic cash application — proves which invoices are settled, partial, or open.
- Supervised, voice-matched reminders with every figure verified against your ledger.
- A staged cadence (gentle → firmer → final notice) capped to one reminder per debtor per week.
- Pulls an invoice from the cadence the moment a customer says "paid" or "disputed".
Partial / with a human
- Lump-sum payments with no remittance reference — surfaced for you to match.
- In-flight / pending charges — held until they settle, never counted as paid or unpaid.
- Disputed or credited invoices — flagged, never chased.
- Phone / SMS / WhatsApp dunning — not offered; email only.
Refuses
- Consumer debt. B2B, first-party invoices only — this keeps the role outside FDCPA / state collection law by design.
- Collecting debt you bought or were assigned. You must attest you are the original creditor.
- Reminders under a name that isn't your validated business name.
- Threats, legal-action language, or anything a debt collector would say.
- Emailing anyone who has asked you to stop.
The proof, made visible
The cockpit shows you the invoices it won't chase and exactly why. This is the guarantee you can audit.
| Invoice | Open balance | Decision | Why |
|---|---|---|---|
| INV-2048 | $12,400.00 | Safe to dun | Open balance proven, high confidence. 31 days overdue. |
| INV-2041 | $0.00 | Do not dun — paid | Captured payment settled the balance to zero. Never emailed. |
| INV-2037 | $4,800.00 | Hold for human | A lump-sum payment arrived with no remittance reference — can't prove which invoice it settles. |
Pricing
Start free, read-only: connect your books and watch the engine classify your AR before a single reminder is ever drafted. Turn on supervised reminders when you're ready.
Cockpit
Free
Read-only aging + safe-to-dun classification. No sending.
Solo
$249/mo
Up to 150 open invoices, one entity. Supervised reminder queue.
Team
$599/mo
Up to 750 invoices, three entities, five seats.
Business
$1,499/mo
Up to 3,000 invoices, SSO, procurement. Enterprise on request.
Multi-entity practice pricing for fractional-CFO firms available on request.
Under the hood
Deterministic math, no AI in the decision
The safe-to-dun classification is pure integer-cents arithmetic over your captured payments and credit memos. A language model never decides whether an invoice is paid — it only drafts the words once the math says the balance is open.
Two-model supervision on every reminder
The draft is written by one AI and adversarially reviewed by a second, independent AI from a different vendor. Every dollar figure is re-derived from your ledger; any collector or threat language is caught and the draft is held.
Sends from your own mailbox
Reminders go out from your own billing address over your own SMTP — transactional email to a customer you already have a relationship with, not a cold-outreach domain.
A send-time freshness re-check
Even after you approve, a final re-classification runs against the live ledger at the moment of sending. If the invoice was paid overnight, the send aborts. The paid-Tuesday / approved-Wednesday / sent-Thursday catastrophe cannot happen.