cowork-invoice-chaser — Claude Code skill: purpose and install
The cowork-invoice-chaser Claude Code skill reconciles invoices with payment records and prepares an accounts receivable aging report. A weekly run updates payment matches and drafts follow-ups for confirmed unpaid invoices.
MIT 104 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a claude-codeWhat cowork-invoice-chaser does
The skill extracts invoice and payment details, matches payments to invoices, and groups outstanding balances by how late they are. Its report includes total outstanding, weighted average days late, and the three largest exposures. It can read invoices in PDF or DOCX and payment evidence from bank exports, remittance emails, CSV files, or a maintained paid list.
For confirmed unpaid invoices, it drafts follow-up emails whose tone reflects the overdue stage and client relationship. It never sends them. Ambiguous matches go to a person for review, and late fees appear only when the invoice or contract includes them.
In weekly scheduled mode, it rescans the folders, reconciles new payments, advances escalation stages, and prepares a digest. Each run combines a client’s overdue invoices into one email and tracks the last stage used for each invoice so a follow-up advances rather than repeats.
What it helps with
- reconcile invoices against payment records
- group outstanding balances by overdue period
- draft follow-ups for confirmed unpaid invoices
- flag ambiguous payment matches for human review
Example prompts for the agent
- Build an aging report from my invoices and payment records.
- Draft follow-up emails for all confirmed overdue invoices.
- Show which clients have started paying later.
How to install cowork-invoice-chaser
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-invoice-chaser/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-invoice-chaser/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a codex2Manually: put the files in place
.agents/skills/cowork-invoice-chaser/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a cursor2Manually: put the files in place
.cursor/skills/cowork-invoice-chaser/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-invoice-chaser2Manually: put the files in place
.github/skills/cowork-invoice-chaser/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-invoice-chaserManually: put the files in place
.devin/skills/cowork-invoice-chaser/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-invoice-chaser
How do I install cowork-invoice-chaser in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-invoice-chaser -a claude-code. The skill file is at ~/.claude/skills/cowork-invoice-chaser/SKILL.md.
What does cowork-invoice-chaser do?
It matches invoice and payment records, reports outstanding balances by age, and drafts follow-up emails for confirmed unpaid invoices. The drafts are not sent.
What data does cowork-invoice-chaser need?
It needs a folder of issued invoices in PDF or DOCX and payment evidence, such as bank exports, remittance emails, a CSV file, or a maintained list of paid invoices.
Source text
SKILL.md · MIT
--- name: cowork-invoice-chaser description: Point Cowork at your invoices and payments records -- builds an AR aging report, drafts escalating follow-up emails matched to each invoice's age and the client relationship, and runs as a weekly scheduled task so nothing slips past 30 days unnoticed. tools: Read, Glob, Grep, Write, Bash model: inherit --- # Cowork Invoice Chaser Chase receivables the way a firm-but-warm operator does: know exactly who owes what and for how long, escalate on a schedule, and never send a dunning email to someone who already paid. Inputs: a folder of issued invoices (PDF/.docx) and payment evidence (bank exports, remittance emails, a payments .csv, or a paid-list the user maintains). ## Workflow 1. **Build the ledger.** Extract from every invoice: number, client, contact, issue date, due date, amount, terms. From payment records: date, amount, payer. Reconcile -- match payments to invoices (exact amount first, then partial payments, then aggregated payments covering multiple invoices). 2. **Age the book.** Produce the AR aging report: current, 1-30, 31-60, 61-90, 90+ days past due, by client. Include total outstanding, weighted average days late, and the three largest exposures. 3. **Flag before chasing.** List invoices with ambiguous payment status (partial matches, unidentified deposits near the amount) separately. These get a human decision, not a chaser. 4. **Draft the chasers.** For each confirmed-unpaid invoice, draft an email matched to its escalation stage -- drafts only, never send: - Due in 3 days: friendly heads-up with invoice attached reference - 1-14 late: polite nudge, assume oversight, restate amount and payment details - 15-45 late: direct, reference prior contact, ask for a payment date - 46-90 late: firm, propose a call, mention terms (late fees only if the invoice/contract actually states them) - 90+: final notice tone, next-steps language, flag to the human for a collections/legal decision 5. **Digest.** One summary per run: total outstanding and change since last run, payments received, drafts queued by stage, ambiguous items needing a decision, and clients whose pattern changed (reliable payer suddenly 30 days late is a relationship signal, not just an AR line). ## Rules - Never send -- drafts only. A wrong dunning email costs more than a late invoice. - Never chase an ambiguous invoice. Unmatched payment evidence near the amount means human review first. - Match tone to relationship: the user can tag clients (`key account`, `standard`, `problem`); key accounts never get form-letter tone regardless of age. - One email per client per run, covering all their overdue invoices -- three separate nudges in one morning reads as automation and burns goodwill. - State late fees only when the underlying invoice or contract specifies them. Never invent penalty terms. - Keep the escalation memory: track what stage each invoice last received so a resent nudge escalates rather than repeats. ## Scheduled Mode As a weekly Cowork scheduled task: re-scan the folders, reconcile new payments, advance escalation stages, and deliver the digest with drafts ready for approval. The run is idempotent -- no invoice is double-chased within its stage window. ## Quick Commands - "Age my receivables" -- steps 1-2 only - "Chase everything overdue" -- full workflow - "Who pays late?" -- client payment-behavior profile from the ledger history - "Draft the 90+ letters" -- final-notice drafts only
© OneWave-AI · MIT · OneWave-AI/claude-skills