Team Handover for Receivables Follow-Up
Create a shared system so anyone on your team can chase invoices with the same professionalism
Different team members send wildly different follow-up messages, from overly aggressive to embarrassingly soft. Clients notice the inconsistency and some learn to wait for the less assertive voices.
That is the gap this drop closes. It is a finance & admin skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Finance managers and team leads who need to standardize invoice collection across multiple staff members
How it works
The skill file does five things, in this order.
1. Build the shared template library. Document three to five standard message templates with clear rules about when to use each one based on days overdue and client relationship.
2. Set ownership triggers, not territories. Assign responsibility based on invoice age or amount rather than client lists, so no one feels personally awkward chasing their own contacts.
3. Create the handoff note format. Require a standard three-line note in your system whenever a case escalates, capturing what was said, client response, and next agreed action.
4. Run a monthly tone calibration. Review two or three real examples as a team to discuss whether the tone was right and build shared judgment without singling anyone out.
5. Track by stage, not by person. Report on how many invoices are at each follow-up stage rather than who collected what, keeping the focus on process health.
What comes back
A consistent collections voice across your team that protects client relationships while reducing the time spent deciding what to say
The mistake to avoid
New hires often copy the tone of the first template they see. Make your gentlest early-stage template the most visible in your shared folder so professionalism becomes the default.
Running it
Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are helping our finance team standardize how we follow up on overdue invoices.
Create a set of {number} email templates for our shared library, covering invoices from {start_days} to {end_days} days overdue.
For each template, include:
- Suggested subject line
- Email body
- Clear trigger rule stating exactly when to use this template
- Tone guidance in one sentence
Client context:
{client_relationship_description}
Our company tone is: {company_voice_description}
Things to avoid: {words_or_phrases_to_exclude}
Format each template so it can be copied directly into our email system. Include {placeholders} for client name, invoice number, amount, and due date.
After the templates, add a simple decision tree showing which template to use based on days overdue and whether this is a first-time or repeat late payer.