Skills

Agent Skill for Invoice Chasing: Automate Payment Reminders

Turn your payment-reminder routine into a reusable agent skill that drafts polite chasers from your overdue list — and never sends anything without a human check.

A person using a calculator beside a laptop showing financial documents on a small-business desk, working on an invoice chasing agent skill reminder
Image: Pixabay / Pixabay Content License

Key Takeaways

  • An invoice-chasing skill reads your overdue list and drafts reminders in your approved tone — it never sends anything on its own.
  • Build it as a SKILL.md file with a name, a description, numbered steps, and three example templates.
  • Three guardrails keep it safe: draft only, flag instead of guessing, and cite the invoice in every draft.
  • Test it on last month's real invoices before your team uses it, and review it whenever your terms or templates change.

An invoice-chasing agent skill is a reusable set of instructions that tells your AI assistant exactly how to find overdue invoices, draft polite payment reminders, and flag the cases a human should handle. You build it once as a SKILL.md file, and your team runs the same approved routine every week. This tutorial shows you how to build one in about an hour.

What the skill does

Most small businesses chase late payments the same way every week: open the overdue list, work out who owes what, write a nudge, and send it. The wording matters, though. A reminder that is too blunt can damage a good client relationship, and one that is too soft gets ignored.

An agent skill captures that routine in a single folder of instructions. Anthropic describes Agent Skills as folders of instructions, scripts, and resources that an agent discovers and loads when they are relevant to a task. The agent first sees only each skill’s name and description, then loads the full instructions when a task matches — a pattern called progressive disclosure.

Your skill should do three things and nothing more: read your overdue list, draft a reminder in your approved tone, and flag anything uncertain for a human. It drafts. It never sends. That single rule is what makes the skill safe to use on real client relationships. Our guide to agent skills for finance teams lists invoice chasing first for the same reason: it is frequent, well defined, and easy to check.

Before you start

Gather four things: your overdue list, your current chasing routine, two or three reminder emails you are happy with, and one owner for the skill. Your overdue list can be a spreadsheet export or an accounts report with client name, invoice number, amount, due date, and days overdue. If your data is messy, fix the export first: a skill built on bad data writes confident reminders with wrong numbers. Your chasing routine is the schedule your team already uses — how many days after the due date you send the first nudge, the second, and the final notice. Your example emails should be real ones: one gentle first nudge, one firmer second reminder, and one final notice. Do not put passwords, API keys, or bank credentials anywhere in the skill; access to your accounting tool should come from the tool’s own permissions.

Step 1: Write down the routine exactly as you do it

Describe the job the way you would explain it to a new hire: what to do first, what information is needed, and what good output looks like. Then cover the reminder schedule, the tone for each stage, and the escalation point. Use a simple table like this one, and replace the numbers with your own:

Days overdueActionTone
1–7First reminderFriendly, assumes an oversight
8–21Second reminderFirm, states the amount and due date
22–30Final noticeDirect, names the next step
Over 30Escalate to the ownerNo message drafted

Step 2: Create the skill folder and SKILL.md file

A skill is a folder containing a SKILL.md file. Create a folder named invoice-chasing and add the file inside it. Where you save it decides who can use it: ~/.claude/skills/invoice-chasing/SKILL.md makes it available in all your own projects, while .claude/skills/invoice-chasing/SKILL.md inside a shared repository gives it to your whole team.

Step 3: Write the frontmatter

Every SKILL.md starts with a short YAML frontmatter block between two lines of three dashes, holding the skill’s name and a description. The description is the most important line in the file: it is what the agent reads to decide whether this skill matches the task in front of it. Name the audience and the job, for example: “Draft polite payment reminders for overdue client invoices, using the team’s approved schedule and tone.”

Keep the name short and lowercase with hyphens, such as invoice-chasing.

Step 4: Write the instructions

Below the frontmatter, write the procedure in numbered steps. Tell the agent to read the overdue list first, then draft one reminder per overdue invoice, using the template that matches the invoice’s stage in your schedule table. Each draft must include the client name, invoice number, amount, and due date, copied exactly from the source.

Add three rules that keep the skill safe:

  • Draft only, never send. Every message waits for a human to approve it.
  • Flag, do not guess. A missing or wrong-looking amount, date, or client name stops the draft; the skill never fills in a plausible value.
  • Cite the source. Every draft names the invoice it came from, so a reviewer can check it in seconds.

Step 5: Add your templates as resource files

Put your three example emails in the skill folder as separate files — first-nudge.md, second-reminder.md, and final-notice.md — and tell the skill to follow them. Keep placeholders clearly marked, such as [CLIENT NAME], [INVOICE NUMBER], [AMOUNT], and [DUE DATE], and tell the agent to fill each one from the overdue list, leaving any field blank rather than inventing it.

Step 6: Test on last month’s real invoices

Before anyone on the team uses the skill, run it against last month’s overdue list and compare every draft with the reminders your team actually sent. Check the amounts, the dates, the tone at each stage, and whether the right template was used. A skill that passes this test on real data is ready; one that only works on made-up examples is not. Run a short safety check too: confirm the skill contains no secrets and no permission it does not need. Our guide on how to audit an agent skill before your team uses it walks through that check in detail.

Step 7: Share it and keep it current

Add the finished skill to your team’s shared skill library. Assign the owner you named earlier, and review the skill whenever your payment terms, templates, or chasing schedule change. A skill that drifts from the real process is worse than no skill, because the team trusts it.

Frequently asked questions

Can the skill send reminders by itself?

No — and it should not. Keep sending in human hands. The skill drafts, a person reviews and sends. That is the guardrail that protects client relationships and prevents a wrong amount going out.

Do I need to know how to code?

No. A first version is mostly a well-written procedure in a markdown file with a short metadata header. If you can write a clear SOP document, you can write this skill.

How is this different from a saved prompt?

A prompt pasted into chat is easy to forget or rewrite by accident. A skill lives in one place, gets reviewed like any other procedure, and loads automatically when the task matches.

Sources

WebGool Tech Senior AI & Small Business Editor
Verified Contributor

Keep Reading

More in Skills

Explore all

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top