FundReap
Product Pricing Guides Sign in Free health check

Using AI in accounts

How to use Claude to collect on time — a playbook for MSMEs and SMEs

Most advice about "AI for collections" is either a prompt list with no structure, or a pitch for a tool that auto-sends messages to your customers. Neither is the actual job. Here's the four-step workflow, in order, and exactly where Claude helps and where it shouldn't be trusted.

The workflow in one line

Know your real numbers → decide who actually needs a call this week → have Claude draft the outreach in your voice → track what was promised so nothing slips through next month. AI drafts and explains. It should never rank who to chase or calculate your ageing — that's arithmetic over your ledger, not a judgement call.

Step 1 — Know your numbers before you open a chat window

Every MSME/SME "collect faster" effort that fails starts the same way: someone opens ChatGPT or Claude, pastes in a rough description of who owes what, and asks it to figure out the priority order. The model will answer — fluently, confidently, and with no way for you to catch it if it misread a date or miscounted days overdue. Ranking who to chase is arithmetic over your actual ledger, and that's not a job for a language model reading a pasted summary. Get your real DSO, ageing, and worst accounts first, from your Tally export, computed the same way every time. Then bring Claude in for what comes next.

Step 2 — Decide who actually needs a call this week

Not every overdue invoice is the same kind of problem. A customer who always pays at 74 days isn't "62 days overdue and getting worse" — they're on schedule for them. A customer who paid four newer invoices but skipped one older one almost certainly has a dispute, not a cash-flow problem, and no reminder will ever fix it. This is where AI can genuinely help you think, not calculate: once you know which invoices are flagged as unusual, ask Claude to help you reason through what's actually going on with a specific one — see spotting a disputed invoice for what to look for before you even open the chat.

Step 3 — Draft the outreach, in your voice, not a template's

This is where Claude earns its keep the most. Paste in the invoice details, the customer's history, and two or three messages you've written by hand before — Claude will match your actual tone far better than any "be polite but firm" instruction. The full breakdown of prompts that work (and the ones that produce generic, ignorable filler) is in how to use Claude for payment reminders. The one rule that matters more than any prompt: a draft is reversible, a sent message isn't — never wire Claude directly to WhatsApp or email. A human reads and sends.

Step 4 — Track what was promised, so it doesn't slip next month

A customer says "I'll pay by Friday." Friday comes and goes. Without a record, next month's list looks identical to this month's, and you're chasing the same conversation from scratch. This is also where a daily/weekly reporting habit pays off — a five-minute check of what moved since last time catches broken promises early, instead of at the next full review. See Claude for daily finance reporting for the actual routine, including what to paste and what never to paste into a general AI chat (hint: not your whole customer ledger with names and phone numbers).

The prompts, if you want the full library

This playbook deliberately doesn't repeat every prompt — the complete, categorized list (reconciliation, vendor emails, GST questions, MIS summaries, collections) lives in 25 Claude prompts every accounts team should bookmark. For the collections-specific ones — what to ask, and the one thing you should never ask Claude to calculate — see Claude prompts for chasing overdue invoices.

Why this workflow, not a single "AI does it all" tool

Getting paid on time is two different kinds of work wearing one name. Deciding who and how much is consistent arithmetic over a ledger — get it wrong and you chase the wrong customer. Deciding what to say and how to say it is judgement about a relationship — get it wrong and you damage one. Claude is built for the second. Trust it for the first and you won't know something's wrong until a customer who should have been called first quietly goes another month unpaid.

Let the arithmetic be arithmetic

Upload your Tally outstanding report and Collection Plan computes the real priority order and flags disputed invoices deterministically — the same answer every time. Then use this playbook for everything that comes after. Free health check, no signup.

Run a free health check

Next: Claude for payment reminders · Claude for daily finance reporting · 25 Claude prompts for accounts teams