When to use
Use this when AR is a spreadsheet of 'we should ping them' and the person who remembers is also the person doing the work. Do not use this to threaten collections on day one.
Prerequisites
- Invoices live in one system (QuickBooks, Xero, or similar) with a due date
- A written tone for reminders (short, specific, not legal-threat day one)
- A human who sends or approves the first two weeks of drafts
SKILL.md
First half on the page. The rest is one click — no email. Crawlers get the full file either way.
--- name: invoice-follow-up description: Draft overdue invoice reminders from the books. Skip disputes, payment plans, and do-not-contact flags. Never send email, never threaten collections, never change invoice status. --- # Invoice follow-up ## Flow 1. Pull open invoices whose due date is past and balance > 0. 2. Exclude: dispute flag, payment-plan flag, do-not-contact, credit-hold conversations this week. 3. Group by customer. One draft per customer, listing every overdue invoice. 4. Draft a reminder: invoice number(s), amount(s), original due date, how to pay (the link you already use). 5. Queue to the owner. Do not send. ## Cadence (default) - Day 3 past due: first reminder (facts only). - Day 10: second reminder, still facts, cc the owner. - Day 21: escalate to the owner as a task — no third email from the skill. Adjust the days. Do not skip to legal language. ## Safeguards - Never send without a human confirm. - Never threaten collections, credit reporting, or stopping work unless the owner writes that sentence. - Never change invoice status, void, or apply a payment. - If the customer replied this week, skip — a human is already in the thread. ## Example draft ``` Subject: Invoice 4412 — $2,400 due Jul 28 Hi Maya — invoice 4412 for the June service window is 8 days past due ($2,400). Pay link is the same one on the invoice. If this is already in progress or something's off, reply here and I'll sort it. — Alex ``` ## Add it to your agent Read this file and follow the instructions. Dry-run a week of drafts against last month's AR aging before anyone hits send.
Still ungated. Page stays short until you ask.
Common questions
Will this email customers by itself?
Not in v1. It drafts. A human hits send. Once the miss rate is near zero you can add a send-after-approve step — still not a blind blast.
How is this different from the software's built-in reminders?
Built-in reminders don't know about disputes, payment plans, or the customer you already called this morning. This skill reads those flags first.