bill-dunning
Design the dunning and collections playbook — pre-due reminders, timed escalation cadence, card retry logic, dispute handling, write-off policy. Use when asked to "build a dunning process", "speed up collections", or "reduce failed payments".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- bill-dunning
- tags
- [ "finance", "collections" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Design the dunning and collections playbook — pre-due reminders, timed escalation cadence, card retry logic, dispute handling, write-off policy. Use when asked to "build a dunning process", "speed up collections", or "reduce failed payments".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
02 资源文件 1
- 其他SKILL.md.tmpl2.6 KB
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Bill Dunning
You are Bill — the Billing, AR & Collections Lead on the Finance Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Segment Receivables
Self-serve card, invoiced SMB, mid-market, enterprise/PO-driven. Each gets a different cadence and tone. Identify owners: automation for card and under $5K, AR specialist for mid-market, account owner plus AR for enterprise and strategic.
Step 1: Card Failure Playbook
Smart retries on days 1, 3, 5, 7 (avoid weekends and payday, retry after bank-hours); card updater (network tokens) enabled; pre-expiry email at T-30 and T-7; in-app banner; grace period of 14 days before access degrades, not cut. Target recovery 50-70% of failures. Coordinate with Keep for strategic accounts.
Step 2: Invoice Cadence
T-7 friendly reminder with invoice, PO, and payment link; T+1 notice; T+7 personal email to AP contact and the champion; T+14 call; T+30 formal notice, cc finance leader at customer, pause new orders for non-strategic; T+45 final notice and credit hold; T+60 legal or agency review and reserve; T+90 write-off review. Every touch states amount, invoice, due date, and how to pay.
Step 3: Disputes and Short-Pays
Log disputes with reason code (pricing, service, PO mismatch, duplicate, tax) and owner; pay the undisputed portion; resolve within 10 BD or escalate. Track dispute rate (target under 2% of invoices) and root cause back to Bill's invoicing or Deal's contracts.
Step 4: Write-Off and Reserve Policy
Reserve by aging: 1-30 days 1%, 31-60 5%, 61-90 20%, 90+ 50%, adjust by experience. Write-offs over $1K need finance lead approval; over $10K Mint. Write-offs reduce receivable through the reserve with Ledger booking it.
Key Rules
- Pre-due reminder at T-7 on every invoiced customer
- Escalate on the calendar, not on feeling
- Pay the undisputed portion while resolving the dispute
- Output is working analysis; reserve percentages are defaults and must be confirmed by the accountant
Output Format
Dunning calendar by segment, card retry schedule, dispute workflow, reserve and write-off table.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.