Chase invoices and get paid faster

Service-business founders and agency owners (5-50 people) billing B2B clients net-30/60 · Assemble in ~10 min; full dunning sequence drafted per client in <5 min once installed.

FinanceEdit flowon X◐ readiness 79

step 1connector

Pull overdue invoice list

⚡ bring your own tool

step 2partial

Triage invoices by age and risk tier

finance-billing-ops

step 3ready

Design the escalating dunning cadence

email-sequence15 alts

step 4ready

Draft each dunning email per client

email-drafter

step 5partial

Send touches and log client responses

email-ops

step 6partial

Triage replies and classify intent

dm-respond10 alts

step 7partial

Decide: extend, escalate, or hand off to collections

renewal-churn-save

Did this recipe work for you?

What you get

▸Tiered AR aging triage (by client, amount, risk tier) you own as a CSV or table
▸Full dunning sequence plan with touch cadence and tone ladder per tier
▸Ready-to-send email drafts for every overdue client at the correct escalation level
▸Reply classification log (promise-to-pay / dispute / no-reply) plus escalation memos for 60+ day accounts — review all final notices with your accountant or attorney before sending

tools: Accounting export (QuickBooks/Xero — existing subscription); Gmail/Outlook for send (existing); no additional paid tools required

tokens: ~$1-4 per batch of 20 invoices

≈ $2-10/mo at typical agency AR volume

What stays yours

· Approve every email before it sends — tone calibration matters for client relationships, and errors in amount or due date must be caught before delivery
· Make the escalation call on 60+ day accounts: whether to extend terms, engage a collections agency, or involve an attorney — the agent drafts the memo but the decision and any legal correspondence require human judgment and professional review
· Record actual payment dates back into your accounting system — cash confirmation is outside the agent loop

✓ Last verified 2026-06-11claude-sonnet-4-6 (subagent, test-mode fixtures)

✓ step 1 · Pull overdue invoice list

✓ step 2 · Triage invoices by age and risk tier

✓ step 3 · Design the escalating dunning cadence

✓ step 4 · Draft each dunning email per client

✓ step 5 · Send touches and log client responses

✓ step 6 · Triage replies and classify intent

✓ step 7 · Decide: extend, escalate, or hand off to collections

view sample outputs from this run

step 2 · Triage invoices by age and risk tier

# Tiered Invoice List — AR Triage
_Applied skill: finance-billing-ops | Input: ar-aging-report.md | Date: 2026-06-11_

---

## Triage Framework

| Risk Tier | Age Bucket  | Risk Profile                          | Collection Posture                              |
|-----------|-------------|---------------------------------------|------------------------------------------------|
| T1 — Low  | 1–30 DPO   | First or minor delay, good pay history | Friendly reminder, assume oversight            |
| T2 — Medium | 31–60 DPO  | Notable delay, mixed history          | Firm follow-up, request payment ti…

step 3 · Design the escalating dunning cadence

# Dunning Sequence Plan — Escalating Cadence by Tier
_Applied skill: email-sequence | Input: tiered-invoice-list.md | Date: 2026-06-11_

---

## Design Principles

1. **Tone ladders with age.** Each tier starts at a different rung. T1 opens warm; T4 opens formal.
2. **One angle per touch.** Touches do not repeat the same argument — each escalates the stakes or shifts the frame.
3. **Clear call to action per email.** Every email ends with exactly one ask (pay now / confirm date / respond by X).
4. **Gaps are firm.** No touch arrives less than 3 business days after the last; no gap exceeds 5 bus…

step 4 · Draft each dunning email per client

# Drafted Dunning Emails — All Clients, All Touches
_Applied skill: email-drafter | Inputs: dunning-sequence-plan.md, tiered-invoice-list.md | Date: 2026-06-11_

---

## TIER 1 — LOW RISK

---

### INV-044 | Kallio Software Inc. | $5,900 | 17 DPO

**Touch T1-A — Friendly Reminder**

> **To:** accounts@kalliosoft.com
> **From:** Sarah Chen, Meridian Design Studio <sarah@meridiandesign.studio>
> **Subject:** Invoice #INV-044 — Quick Reminder ($5,900)
> **Send date:** 2026-06-11

Hi team,

Just a quick note — Invoice #INV-044 for $5,900 (covering the May UI design sprint) came due on May 25. It m…

The problem

When I finish a project or ship an order, I want someone to chase the invoice for me with escalating, context-aware follow-ups so that I get paid without the awkward emails stealing my Sunday afternoons

Cybernetic layers

Memorybyo

AR state (who was contacted, which touch number, what they replied, promised-pay dates) must be tracked in a Google Sheet, Notion table, or local CSV. No harvested memory artifact covers AR-specific state. This is the primary gap — without it, the agent cannot self-resume across sessions.

Background / schedulingbyo

Dunning only works if touches go out on schedule. A true background scheduler (Claude Code cron, Zapier, or a Make scenario) is needed to trigger each follow-up at the right interval. Not a library artifact yet — you wire it manually or use a byo scheduler.

Harnessready

Claude Code is the runtime. Drop each skill into ~/.claude/skills/ and invoke by name. The agent can run the full sequence in one session given the invoice CSV as input.

Click any step to see what fills it — and the ranked alternatives you can swap in.