Paste your unpaid invoices and it ages them, flags what to chase today, and drafts the follow-up for you to send. It never sends anything itself.
Takes the list of unpaid invoices you paste in, sorts each one into an overdue bucket (0-30, 30-60, 60-90 and 90+ days past due), totals what is outstanding, and tells you who to chase today, oldest and largest first. Then it drafts a firm-but-friendly follow-up message for each client in your voice, with the tone escalating as the invoice gets older: a light nudge for something a couple of weeks late, a direct message naming next steps for something months overdue. Every draft goes through a pre-ship quality gate before it is presented as ready to send. You send it. The skill does not.
By default it is a fast chase tool with no memory: you paste your current open invoices from wherever you already bill, it works on exactly that list, and nothing is stored. If you want it to remember between runs, say keep the ledger and it switches on an optional ledger: a plain, readable file listing each invoice with its amount, due date, when it was first seen, when it was last chased and its current status. On your next paste it reconciles the old list against the new one, so it can tell you what got paid, what is still open, and who has already been nudged.
This skill has no button. You start it by saying what you want. Any of these will do it:
| If you actually want | Use this instead |
|---|---|
| real accounts receivable: partial payments, credit notes, multi-currency statements, payment plans | billing software. The skill will tell you the same thing when your situation outgrows it. |
| invoices created and sent automatically, or a sync with your billing tool | your billing software does both; this skill only reads what you paste |
| an automated reminder sequence that fires on a schedule without you | email-sequence, and accept that automated sending is a different risk than a personal chase |
| to know which clients are worth keeping, not just which ones owe you | profit-by-client |
| to negotiate a disputed invoice or a client who is refusing to pay | that is a conversation, not a template; use sales-closer to prepare for the call |
| What you need | Why | |
|---|---|---|
Your current unpaid invoices, pasted as a list or small table: client, amount, due date. A line like Harbor Print Co, 1,850, due 14 May is enough | the paste is the entire input and the source of truth; the skill only works on what you give it | Required |
| A due date on each line, or at least the invoice date | an invoice with no date at all cannot be aged; it gets flagged and excluded from the buckets rather than guessed at | Required |
| A spreadsheet or PDF export instead of a paste | dropped files are parsed through the file-reading skills, so an export from your billing tool works as well as typing | Optional |
| Brand voice on file | chase drafts are written in your voice when it is available; without it they default to a professional neutral tone | Optional |
| A decision on the ledger: say keep the ledger if you want memory between runs | ledger mode is opt-in only; it is never assumed, and without it nothing is stored between runs | Optional |
| Your actual late-payment terms, if you have any | the drafts will only reference fees, interest or consequences you have stated yourself; the skill never invents them | Optional |
critique pre-ship gate before presenting it as ready to send.presumed paid [CONFIRM]. Nothing is ever deleted silently, and nothing is ever confirmed as paid without you.presumed paid [CONFIRM] means an invoice disappeared from your paste, nothing more. Confirm against your bank or billing tool before you count it as collected.| The mistake | Do this instead |
|---|---|
| Expecting the skill to email the client | It drafts, you send. Read the draft, adjust anything personal to the relationship, then send it from your own account. |
| Pasting amounts with no dates and expecting an aged summary | Include a due date per line. Undated invoices are flagged and left out of the buckets, so the summary only covers what carries a date. |
| Asking for a late fee or legal warning to be added for pressure | The skill only references terms you have actually set. If you want a fee, put it in your payment terms first, then tell the skill what those terms say. |
| Assuming it remembers last week's invoices | By default it holds no state between runs. Say keep the ledger once and it will track the list from then on. |
Treating presumed paid [CONFIRM] as money in the bank | It only means the invoice left your paste. Check your bank or billing tool, confirm it, then update the ledger row. |
| Stretching it into your AR system as the business grows | The moment partial payments, credit notes or multi-currency appear, move collections into billing software and keep this as the drafting layer on top. |
The best chase cadence is boring: a short, friendly nudge the week an invoice goes overdue beats a masterpiece written at day ninety. Clients pay the invoices that keep politely showing up. Run this weekly with the ledger on and the escalation takes care of itself, because each invoice simply gets the message its age deserves.