cowork-invoice-chaser

Solid

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.

AI & Automation 229 stars 38 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 89/100

Stars 20%
79
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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 invoi...

Details

Author
OneWave-AI
Repository
OneWave-AI/claude-skills
Created
9 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

invoice-and-payment-writer

You are a professional invoicing expert. Generate clear invoice copy and diplomatic payment reminder emails that maintain client relationships while ensuring timely payment. ## Process 1. Gather invoice details (amount, due date, services) 2. Create professional invoice copy 3. Write payment reminder sequence 4. Include clear payment terms and methods 5. Maintain professional, non-confrontational tone ## Output Format ## Invoice: #\[Number\] From: \[Your Name/Company\] To: \[Client Name/Company\] Date: \[Invoice Date\] Due Date: \[Due Date\] ### Services Rendered <table header-row='true'> <tr> <td>Description</td> <td>Qty</td> <td>Rate</td> <td>Amount</td> </tr> <tr> <td>\[Service 1\]</td> <td>X</td> <td>\$X</td> <td>\$X</td> </tr> <tr> <td>\[Service 2\]</td> <td>X</td> <td>\$X</td> <td>\$X</td> </tr> <tr> <td>Total</td> <td></td> <td></td> <td>\$X</td> </tr> </table> ### Payment...

0 Updated 1 weeks ago
prvthmpcypher
AI & Automation Solid

accounts-receivable-followup-writer

Draft escalating invoice reminder sequences (gentle→neutral→firm→final) from invoice details and client relationship context. Preserves relationships while collecting payment. Use when client hasn't paid, need professional follow-up, overdue invoice. Triggers: 'write invoice reminder', 'overdue invoice follow-up', 'клиент не платит', 'просроченный счёт', 'напиши напоминание об оплате'.

14 Updated yesterday
KirKruglov
AI & Automation Solid

cowork-inbox-triage

Daily inbox triage using Cowork's email write tools (Microsoft 365 or Gmail) -- classifies unread mail, drafts replies in your voice, flags what needs a decision, and schedules follow-ups. Built to run as a recurring Cowork scheduled task.

229 Updated 1 weeks ago
OneWave-AI