Claude can draft invoices and chase late payers with no code: give it a job sheet, timesheet export or forwarded client email, ask for draft line items and polite reminders, then check every figure and send them yourself. The approval step holds as long as Claude drafts and only you send, or approve each send.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe approval step is easy to lose once Claude is connected to your inbox or your books. On Pro, Max, Ultra and Team plans, Anthropic is rolling out Auto as the default permission mode, and in Auto, connector actions marked "Needs approval" can run without asking you. Intuit also says every invoice Claude creates through the QuickBooks connector lands in QuickBooks straight away. So decide where the human gate sits before you connect anything: draft-only chats, Gmail drafts you send yourself, or Manual mode for any run that touches money or clients.
What can Claude do for invoicing, and what stays with you?
Claude can turn raw billing information into invoice wording, totals and reminder emails, while issuing the invoice, recording payment and pressing send stay with you and your accounting software. The split below is the one I would start with in any small firm.
| Job | Claude's part | Your part |
|---|---|---|
| Line items | Turns timesheet rows, job notes or an email thread into clear descriptions and quantities | Confirm the work was done and agreed |
| Pricing and totals | Applies the rates and fixed fees you give it and adds them up | Let your accounting software recalculate; compare the two totals |
| Issuing the invoice | Can create it in QuickBooks if connected, where it lands immediately | Create it yourself, or review it in QuickBooks before it is sent |
| Finding who is late | Reads an aged receivables export and ranks the overdue invoices | Confirm against bank receipts before anyone is chased |
| Writing chasers | Drafts gentle, neutral or firm reminders in your voice | Approve each one; make the phone call on serious debts |
| Sending | Can save Gmail drafts, or send if you allow it | Send yourself, or approve every send |
Your accounting or invoicing software should still issue the real invoice. It numbers invoices in sequence, posts them to your ledger, adds the tax lines your settings require and tracks payment against each one. A Claude draft does none of that; it is a well-written proposal for what the invoice should say. Claude also cannot see whether a client has paid unless you give it your ledger, a bank export or a connected payment tool, which is why the payment check in the chasing stage is yours.
Which Claude setup do you need: a chat, a Project or the plugin?
A one-off batch works in an ordinary Claude chat, a monthly routine belongs in a Project, and the Small Business plugin suits owners who want Claude reading QuickBooks or Xero directly. The Project route saves your rates and terms so each month starts from the same rules.
| Setup | Plan needed (Claude pricing page, 22 November 2026) | Where your approval happens | Best for |
|---|---|---|---|
| Chat with uploaded files | Free ($0) works; uploading XLSX needs code execution and file creation switched on | You copy each draft into your software or email | Testing the idea on last month's billing |
| A Project | Free allows up to five projects; Pro is $20 a month, or $17 a month billed annually | You copy drafts out, or Claude saves Gmail drafts you send | A monthly billing and credit-control routine |
| Small Business plugin | Pro, Max, Ultra, Team or Enterprise (Claude Academy) | The plugin waits for your go-ahead, and the permission mode adds a second gate | Chasing straight from a connected ledger |
If the invoices carry client names, fees and project details, think about the plan before the prompt. On the consumer plans (Free, Pro and Max), Anthropic uses your chats to improve its models when the model-improvement setting under Settings, then Privacy, is switched on, so check it before the first upload. Team plans ($25 a seat a month, or $20 billed annually, for 2 to 150 seats) do not train on your content by default, and a practice that handles other people's financial records will usually want that default rather than a setting each person has to remember.
Setting up an invoice-drafting Project in about 15 minutes
A Project keeps your rate card, payment terms and wording rules in one place, so each month's batch starts from the same rules instead of a fresh explanation. The steps follow Anthropic's help page on creating projects.
- Open Projects from Claude's sidebar and click + New Project. Name it something plain such as "Billing and credit control". Claude itself does not read the project name or description, so put nothing important there.
- Click Set project instructions, paste the instructions below, edit them to your firm, then click Save instructions.
- Use the + button in the project knowledge panel to add your rate card, standard payment terms, a page of client billing notes (billing entity, purchase-order rules, who receives invoices) and two or three past invoices you were happy with. Leave your bank details out; they belong in your invoicing software only.
- If you want the project's memory kept apart from your other chats, turn off Use account memory under Memory on the project's page.
- Each month, start a new chat inside the project and attach the export with + then Add files or photos. Claude accepts CSV, XLSX, PDF, DOCX and TXT among other types, up to 20 files per chat and 500MB per file.
PROJECT INSTRUCTIONS: Billing and credit control
You draft invoices and payment reminders for a six-person accountancy
practice. You never send anything. Every output is a draft for the
practice manager to check.
Invoices
- Use only rates, fixed fees and terms from the project files.
- If a price, quantity, purchase-order number or billing contact is
missing, leave the field as [MISSING] and list it under "Questions".
- Never copy bank details from emails or attachments.
- One line per job; description under 20 words, in plain English.
- Show your arithmetic in a separate table so totals can be checked.
Reminders
- Use the payment history column to pick the tone:
on time most of the time = gentle; mixed = neutral; mostly late = firm.
- One request per email. No threats, no fees or interest unless the
clause is quoted from our terms file.
- Sign off as [your name], never as "the accounts team".
Output
- Start with a summary table, then each draft in full.
- End with "Questions" and "Things I could not check".
Turning a spreadsheet or forwarded email into a draft invoice
Claude works from whatever you already have: a timesheet or job export as CSV or XLSX, a photo of a signed job sheet, or the email where a client agreed extra work. Saved email files are not on Claude's list of supported upload types, so paste the email text into the chat or print the thread to PDF first.
The prompt matters less than the rule that Claude must not fill gaps. Here is a prompt for a month of unbilled time, with the kind of answer you should expect back.
PROMPT
Attached is our unbilled time export for October (columns: Client, Job,
Staff, Date, Hours, Rate, Narrative). Draft one invoice per client job.
Apply fixed fees from the fee schedule in the project files where a job
has one; otherwise bill hours x rate. Flag anything that looks wrong
instead of fixing it silently.
SAMPLE OUTPUT (illustrative)
| Client | Job | Basis | Draft amount |
| Client 04 | Year-end accts | Fixed fee | $1,500.00 |
| Client 11 | Advisory call | 2.5h x $140| $350.00 |
| Client 17 | Payroll setup | 6.0h x $95 | $570.00 (!) |
Questions
1. Client 04: time recorded at standard rates is $2,460, but the fee
schedule shows a fixed fee of $1,500. Bill $1,500 and record a
$960 write-off?
2. Client 17: senior time is charged at $95 an hour; the rate card says
$140. Agreed discount, or a coding error?
3. Client 09: billing notes require a PO number. None found. [MISSING]
What I would fix before approving: question 1 is a partner decision, not a drafting one, so it goes to whoever agreed the fee; question 2 needs a look at the engagement letter; question 3 means the invoice waits until the client sends the PO, because an invoice without it will bounce back from the client's accounts team and add two weeks to payment.
A forwarded email shows the same rule from another angle. Say an electrical contractor forwards a client's message: "Happy for you to go ahead with the extra six double sockets in the kitchen at the price you quoted on the phone." A good draft line reads "Supply and fit 6 double sockets, kitchen, as agreed by email on 14 October: [MISSING PRICE]". A bad one invents $480 because six sockets at $80 looks plausible. The phone quote exists only in the contractor's head or notebook, so the price has to come from there.
If cleaning the timesheet export before Claude sees it is the slow part, try The Complete Excel Course with AI Integration on Coding Liquids.
An accountancy practice's October billing run, start to finish
Take an illustrative six-person accountancy practice. Seventy clients pay monthly fixed fees that the practice software invoices automatically, so Claude is not needed there. The work is the ad hoc jobs billed at month end, plus chasing whatever is overdue. Before Claude, the practice manager spent roughly three hours writing invoice narratives and an afternoon on reminder emails every month.
In October the unbilled time export held 17 jobs worth $21,340 at standard rates. Inside the project, Claude produced 17 draft invoices and four questions in a few minutes:
- One fixed-fee job where time at standard rates ($2,460) exceeded the agreed fee ($1,500). The partner confirmed the fixed fee, so $960 was written off and noted on the job.
- Two time entries whose narratives named a different client from the one they were coded to. They moved to the right job before billing.
- One client whose billing notes require a purchase-order number on every invoice, with none in the file. That invoice waited three days for the PO.
- One senior's time charged at $95 an hour instead of $140. It turned out to be an agreed discount, now written into the client notes so the question does not come back next month.
After the adjustments the practice billed $19,880, and the manager's review took about 50 minutes instead of three hours. Every invoice was then raised in the practice's own accounting software, which recalculated the totals; the two sets of figures matched to the cent, which is the check that matters.
Chasing came next. The aged receivables report on 1 November showed 12 overdue invoices across 9 clients, $16,920 in all:
| Days overdue | Invoices | Value | Tone Claude proposed |
|---|---|---|---|
| 1 to 14 | 5 | $4,150 | Gentle (four clients who normally pay on time) |
| 15 to 30 | 4 | $6,370 | Neutral |
| 31 to 60 | 2 | $3,600 | Firm, with a pay-by date |
| Over 60 | 1 | $2,800 | Phone call first, then a firm letter |
Claude drafted nine emails, one per client, combining a client's overdue invoices into a single message. Before approving, the manager checked the bank feed: one "overdue" client had paid by bank transfer the previous Friday and the payment had not been matched yet. That email was deleted. Eight went out, the over-60 client got a phone call, and by 30 November $11,480 of the $16,920 had come in.
What should you check on a Claude-drafted invoice before it goes out?
A Claude-drafted invoice needs nine checks before you approve it: client entity, work done, quantities, rates, discounts, tax, total, terms and due date, and payment details taken from your own records. The table fills each one in from the October run.
| Check | Why it matters | How to verify | October example |
|---|---|---|---|
| Billing entity | Groups often have several companies; the wrong one delays payment | Compare with the engagement letter or contract | Client 22 billed to its holding company, as agreed |
| Work actually done | Drafts can include time that should not be billed | Read each line against the job file | Two entries moved to the right client |
| Quantities and hours | Copying errors creep in from exports | Spot-check three lines against the source | All matched |
| Rates and fixed fees | Claude only knows the rates you gave it | Compare with the rate card and fee schedule | $95 discount confirmed and recorded |
| Discounts and write-offs | A partner decision, never a drafting one | Get the fee-owner's yes in writing | $960 write-off approved |
| Tax lines | Rates and wording depend on your registration and the client | Let your accounting software apply tax, not Claude | Applied by the software |
| Total | Language models can slip on long additions | Software total must equal the draft total | $19,880 on both |
| Terms and due date | Wrong terms make chasing awkward later | Match the client's agreed terms | Two clients on 14 days, the rest on 30 |
| Payment details | Changed bank details are a classic fraud | Taken only from your invoicing software's template | No bank details in any Claude draft |
The total check deserves a moment. Claude usually adds correctly, but a 40-line invoice is exactly where a carried digit goes astray, and why AI slips on arithmetic in quotes and invoices explains the mechanism. Treat your accounting software's total as the true figure and Claude's as a cross-check.
How do you get Claude to write chasers that stay polite but get paid?
Claude writes better payment reminders when it knows the client's payment record, the invoice facts and the single action you want, so upload your aged receivables report and set the tone by that record. A long-standing client five days late needs a nudge; a client who is late every quarter needs a date.
A five-stage routine covers most small firms. The days are a starting point; move them to suit your terms.
| Stage | When | Tone | What the email does | Who approves |
|---|---|---|---|---|
| 1. Courtesy note | 3 days before due | Warm | Says the invoice is due on Friday and includes the pay link | Owner approves the week's batch |
| 2. First reminder | 3 days after due | Gentle | Assumes oversight, attaches the invoice again | Owner, batch |
| 3. Follow-up | 14 days after due | Neutral | States the facts and asks whether a query or PO is holding it up | Owner, each email |
| 4. Firm reminder | 30 days after due | Firm | Gives a pay-by date and the next step your terms allow | Owner, after a phone call |
| 5. Final notice | 45 days after due | Formal | Confirms the call and the date work stops or the debt is referred | Owner personally |
Two sample drafts show the difference in tone. Both are illustrative outputs from the project above.
GENTLE (client usually pays on time)
Subject: Quick reminder: invoice 2417 for $1,250
Hi [first name],
I know October was busy, so a quick nudge: invoice 2417 for $1,250
(year-end accounts) was due on 31 October. A copy is attached, and you
can pay by the link on the invoice.
Thanks very much,
[your name]
FIRM (client paid late on 5 of the last 7 invoices)
Subject: Past due: invoices 2311 and 2364, $3,600 (38 days overdue)
Hi [first name],
Invoices 2311 ($2,100, due 24 September) and 2364 ($1,500, due
30 September) remain unpaid. Please arrange payment of $3,600 by
Friday 14 November.
If something is holding this up, reply today and I will call you.
[your name]
What I would change in drafts like these: delete any sentence that threatens something you will not actually do, check that "attached" is true before it goes, and remove phrases such as "as per our records" that make a gentle email sound cold. If Claude adds a late fee or interest that is not quoted word for word from your terms, cut it.
How do you keep the approval step once Claude can reach your inbox?
Claude keeps a human approval step only if your settings require one: Manual mode asks before connector actions unless a tool is set to "Always allow", while Auto can let "Needs approval" actions run unasked. Choose the mode from the selector in the message box before you ask for a chasing run, not after.
- Draft-only. Keep connectors off in the billing project. Claude writes the text and you paste it into your invoicing software and email. Slower, but the approval step cannot leak.
- Gmail drafts. Claude's Gmail connector has a separate tool for creating drafts and another for sending. Ask for drafts, and set the send tool to "Always ask", which Anthropic's help pages say makes Claude ask before each use of that tool in every mode, or block it outright. The steps are in connecting Claude to Gmail, Calendar and Drive safely.
- QuickBooks. Intuit says every invoice Claude creates lands in QuickBooks right away and tells you to check new invoices under Sales, then Invoices, before asking Claude to send them. Deleting an invoice and sending a payment reminder both ask for your confirmation. Start read-only, as connecting Claude to QuickBooks read-only first describes.
- Team plans. An owner can go to Organization settings, then Connectors, open a connector's Tools tab and set write tools to Needs approval or Blocked for everyone. Members cannot override it.
- Schedules. A scheduled task may wait for an "Always ask" tool or finish without it, so keep chasing runs unscheduled until several manual batches have gone out clean.
If you want help fitting invoice drafting and chasing into how your practice runs, I offer one-to-one AI consultations for small businesses.
What does the Small Business plugin's invoice chaser add?
The Small Business plugin's invoice chaser reads overdue invoices from a connected ledger, checks recent payments, scores each customer's payment history and drafts one reminder per customer, then waits for your go-ahead. Anthropic's plugin page says every one of the plugin's 43 workflows starts in approval mode.
The plugin's published skill file for the chaser (read on 22 November 2026) spells out rules worth copying even if you never install it:
- Ledgers. It pulls overdue invoices from MYOB, NetSuite, QuickBooks, Xero or Zoho Books, whichever is connected, plus Stripe and Airwallex where connected.
- Possibly paid. Any customer with a settled payment in the last 14 days is flagged "possibly paid, verify" instead of chased. PayPal is checked over a 7-day window because of its rate limits, and the skill notes that cheque or bank-transfer payments are invisible to that check.
- Tone by history. Customers who paid on time for at least 75% of invoices get a gentle reminder; those late on 25% to 50% get a neutral one; those late on more than half get a firm one. With fewer than three invoices on record, the tone defaults to neutral.
- One email per customer. Several overdue invoices become one email with each invoice listed and a combined total.
- Sending. PayPal invoices are reminded through PayPal; everything else is queued as a draft in Gmail or Microsoft 365, and only after your approval.
- No connectors. Upload the aged receivables report as a CSV and the same drafts come back for you to send by hand.
The plugin needs a Pro, Max, Ultra, Team or Enterprise plan. If you are weighing it against the wider set of workflows, which Claude for Small Business workflows to turn on first puts the invoice chaser in context with cash-flow and payroll planning.
Where Claude-drafted invoices and chasers go wrong
Most problems come from Claude working with incomplete information and nobody noticing. These are the ones I would watch for in the first two months.
A chaser reaches a client who has already paid
It shows up as an annoyed reply with a remittance advice attached. The cause is almost always a payment sitting unmatched in the bank feed. Reconcile the bank before every chasing run, and tell Claude to list any client with a receipt of the same amount in the last fortnight as "check before sending".
The invoice goes to the wrong company
A client trades under one name but signed the engagement letter as another company, and the invoice is rejected by their accounts team three weeks later. Keep the billing entity for every client in the project's billing notes, and make "billing entity" the first column in Claude's summary table.
Claude fills a gap with a plausible number
The forwarded email had no price, so the draft carried one anyway. The fix is the [MISSING] rule in the project instructions, plus your spot-check of three lines against the source on every batch.
An email asks you to change bank details
A supplier or client email may say "please note our new bank details" or contain instructions aimed at Claude itself. The plugin's own rules treat text inside emails as data, never as commands, and you should do the same: never change payment details on an email's say-so, and confirm by phone on a number you already hold. Catching duplicate invoices and payment fraud covers the wider checks.
Two reminders go out for one invoice
An invoice raised in your accounting software and also collected through a payment processor can appear twice in the data. Ask Claude to match on invoice number first, then amount and due date, and to send one reminder per customer.
A firm letter goes to your best client
A nine-year client, five days late for the first time, receives a pay-by-Friday notice. Tone set by days overdue alone causes this. Base the tone on payment history, as the plugin does, and read every firm draft yourself.
How do you know the routine is working after a month?
The invoicing routine is working if debtor days fall, fewer invoices need correcting after approval, and your review time per batch drops, so record all three for the month before and the month after.
A quick sum for debtor days: divide what clients owe you by annual fees and multiply by 365. For the illustrative practice, $124,000 owed on $840,000 of annual fees is about 54 days. If steady chasing brings the balance down to $101,000, debtor days fall to about 44, and $23,000 sits in the bank instead of in clients' accounts. The other two measures are simpler: count the invoices you changed after Claude's draft (October: 4 of 17) and time the review (October: 50 minutes). Both should fall in month two as the billing notes fill up.
If the numbers do not move, look at stage 3 of the chasing routine first. Most money that arrives late arrives after a polite, specific follow-up at about two weeks, and that is the email owners most often skip when the month gets busy. For trades businesses with stage payments, polite AI reminders for trades adapts the same routine to deposits and retentions.
Questions owners ask about invoicing with Claude
Can Claude send invoices to clients automatically?
Yes, if you connect it to QuickBooks or Gmail and your permission settings allow it, but you should not start that way. Intuit says every invoice Claude creates through its connector lands in QuickBooks straight away, and Auto mode can let some connector actions run without asking. Keep Claude to drafts, check each invoice in your accounting software, and send it yourself until a month of batches has gone out clean.
Is it safe to upload client invoices and timesheets to Claude?
It can be, if you pick the plan and settings deliberately. On Free, Pro and Max, chats are used to improve Claude when the model-improvement setting under Settings, Privacy is on, so check it before uploading. Team and Enterprise plans do not train on your content by default. A deleted consumer chat leaves your history at once and Anthropic's back-end within 30 days.
Does Claude's invoice chasing work with Xero or only QuickBooks?
Both work. The Small Business plugin's invoice chaser reads overdue invoices from MYOB, NetSuite, QuickBooks, Xero or Zoho Books, whichever is connected, and can also check PayPal, Stripe and Airwallex. With nothing connected, export an aged receivables report as a CSV and upload it; Claude drafts the same reminders and hands them back for you to send.
How many reminder emails should go out before I phone a late payer?
Two or three emails, then a phone call. A courtesy note before the due date, a gentle reminder a few days after it and a neutral follow-up at about two weeks cover most forgetful clients. Past 30 days, an email is easy to ignore, so ring first, then send the firm written reminder that confirms what was agreed on the call.
Can Claude add late payment interest or fees to a chaser?
Only if your own terms and the law that applies to you allow it, and Claude cannot judge that for you. Put the exact late-payment clause from your terms into the Project and tell Claude to quote it, never invent it. If your terms say nothing about interest or fees, leave them out and ask your accountant or a legal adviser before adding any.
Further reads
- How Freelancers Use AI for Invoices, Proposals and Chasers — The same drafting and chasing ideas for a one-person business.
- Claude (Formerly Cowork): Sort Receipts for Reconciliation — Sort receipts and supplier bills before the month-end close.
- How to Use Claude for Month-End Close With QuickBooks and PayPal — Close the month once the chased payments have landed.
- How to Build a Rolling Cash Budget With Claude From Actuals — See how faster collections change your cash forecast.
- Claude for Small Business Cost: Which Plan You Need — Which Claude plan the Small Business plugin needs.
- Quote to Cash: Connect Quotes, Invoices and Payments With AI — Join quotes, invoices and payments into one flow.
Show 5 more related tutorials
- How to Chase Late Invoices and Missing PODs in Trucking With AI — A day-by-day reminder sequence, a missing-POD list and copy-ready messages that a carrier's office can run with AI in about fifteen minutes a day.
- AI Automation for Architects: Enquiry to Fee Invoice, Step by Step — Six draft-only automation steps from enquiry form to overdue-invoice reminder, with costs, task counts and the architect approving every document.
- Credit Control Software for a Small Distributor: Which to Pick — Chaser, Satago and built-in accounting reminders compared for a small distributor, with monthly costs, limits and a checklist of AI features to ask about.
- How Much Does Dext AI Assist Cost, and Is It Worth It? — Dext AI Assist learns how you code receipts and suggests the rest. What it does, what it costs, and when a small workload makes it worthwhile.
- Claude for Payroll Prep: What to Check Before You Approve a Pay Run — An 18-point pre-approval checklist for pay runs Claude has prepared: hours, rates, starters and leavers, leave, cash cover and bank-detail changes.
Browse all AI-for-business tutorials
Sources: Claude pricing page; Claude help centre articles on uploading files, creating projects, getting started with Cowork, connectors and Google Workspace connectors; Gmail and Intuit QuickBooks connector listings in Claude's directory; Intuit's help article on the QuickBooks connector for Claude (updated 28 October 2026); Claude privacy centre articles on data retention and model training; Claude for Small Business plugin page and Anthropic's launch post (13 May 2026); the plugin's published invoice-chase skill files (all read 22 November 2026).
