Create and send monthly client invoices and check last month's payments, with your checks before invoices are created and before they're marked paid
Have Claude Code run a skill that drafts your monthly client invoices from your time reports and calendar, creates them in Xero, emails them from Gmail and checks last month's payments, pausing for your check before invoices are created and before they are marked paid.
What the agent did
Source-reported example · as described by Peter Hartree, freelancer and self-described AI Uplift Consultant; author of the AI Wow study journal and newsletter (wow.pjh.is); describing his own freelance invoicing
The author, Peter Hartree, a freelancer who writes the AI Wow site and newsletter, built a Claude skill in Claude Code for his monthly invoicing.
Each month the skill creates a monthly admin task list in Obsidian; downloads time reports from Toggl, extracts billable hours per client and saves PDFs for his records, then asks him to check before proceeding; drafts invoices for hourly clients from the Toggl data and gets coaching-client session counts from Google Calendar (he invoices coaching per session), asks him to check before proceeding, then creates the invoices in Xero; emails the invoices to his clients from Gmail, with the invoice PDF and time tracking reports attached (shown in a screenshot in the post) and reminds him to submit one client's invoice manually via Deel; and confirms last month's invoices were paid by searching Gmail for payment notifications and cross-checking with Xero, asking him to check before proceeding and then marking invoices as paid in Xero.
If corrections are needed he explains them verbally, as he would to a human assistant. Creating the skill took him 1-2 hours, all in conversation with Claude.
Reported by the author: "Claude now handles >90% of the work. What was a 1-hour task now takes 5 minutes." Building the skill took 1-2 hours.
Limitations
The post is a short outline: it does not publish the skill file, give invoice volumes, show any errors, or say how the apps are connected.
Owner approval, as stated in the source: the skill asks the author to check before proceeding after the Toggl hours are extracted, after invoices are drafted (before they are created in Xero), and after the Gmail/Xero payment cross-check (before invoices are marked paid in Xero).
The post does not state a separate check immediately before the invoices are emailed to clients. The post says some steps "require manual action" from the author (marked in red on the page) but the text alone does not show which; one client's invoices are submitted manually via Deel.
Fixed-quote projects are mentioned as part of the complexity, but the post does not say how the skill handles them. The author says his software engineering background helped at times. The model is not named in the post (his newsletter of 2025-12-12 discusses skills with Opus 4.5 generally but does not say that model ran this skill).
Try it in your business
What you'll need
Claude Code; a Claude skill describing your monthly invoicing steps; access from Claude Code to your time tracker (Toggl), accounting software (Xero), calendar (Google Calendar), email (Gmail) and a notes app for the task list (Obsidian); your client rates and invoicing rules; your own review at the skill's checkpoints (after the time reports, before invoices are created in Xero, and before invoices are marked paid); the post states no check right before invoices are emailed, so our suggested prompt adds one
The skill works across the author's existing apps (Toggl, Xero, Google Calendar, Gmail, Obsidian) from Claude Code; the author says he wrote no code himself, so this is not presented as custom development, though the connection method is undisclosed.
Author's original prompt
This is the opening prompt the author quotes for creating the skill in Claude Code; he says the skill was then built over 1-2 hours of conversation. It is not the monthly run prompt, and the finished skill's instructions are not published. Checked the post in full and the site's home page and About page on 2026-10-20.
Hey Claude, I'm a freelancer and I have to send invoices every month and also verify that my past month's invoices were paid. Could you help me make a skill to do this?
Optional starting prompt (ours, untested)
How ours differs from the original setup: Same execution agent (Claude Code). The author's version is a saved skill built from his opening prompt; ours is a one-off starting prompt you could turn into a skill.
Ours is strictly draft-and-approve: it adds an explicit approval before each invoice email is sent and before any invoice is marked paid (the post states checkpoints before invoice creation and before marking paid, but not immediately before emailing).
Placeholders replace the author's specific apps; the fixed-quote line and the ambiguity flag are our additions. Ours leaves out the author's first step of creating a monthly admin task list in Obsidian.
Help me with my monthly client invoicing as a freelancer. 1) Download last month's time reports from [time tracker], extract billable hours per client, save the reports for my records, and show me the totals. Stop and wait for my check. 2) Draft invoices: hourly clients from the time data at their rates [rates], per-session clients from session counts in [calendar], fixed-quote projects from [list]. Show me every draft and wait for my approval before creating anything in [accounting software]. 3) After I approve, create the invoices as drafts and prepare the emails to each client. Do not send any invoice or email until I explicitly approve each one. Remind me about any client I invoice manually [e.g. via Deel]. 4) Check last month's invoices: search [email] for payment notifications, cross-check them with [accounting software], and list paid, unpaid and unclear invoices. Do not mark anything as paid, record payments or delete anything until I explicitly approve. Flag anything ambiguous instead of guessing.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.
Draft late invoice reminder emails every Monday for your approval
Have Claude Cowork set up a Monday-night agent that drafts late-invoice reminder emails for you to review and send, as the author describes.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; access to your list of overdue invoices (the post does not say how); a Google Sheet of customer names and contact names; your own reminder email template; access to your mailbox so drafts can be saved; your own review before anything is sent.
Every Monday evening, open [my receivables or invoice system] and list invoices that are past due. Match each customer against my Google Sheet [name] (customer name, contact name). For each match, draft a late-invoice reminder from my template [paste template], using the contact name and each overdue invoice's number, amount and due date. Save the drafts in my Drafts folder. Do not send any email. Then give me a short report: customers included, amount owed per customer and the total, plus any overdue customer who is not in my Sheet and anything you could not read. Do not change or mark anything in the invoice system; I review and send the drafts myself.
Check weekly for missed membership payments and cancellations and draft follow-up emails
Have Claude Code check Stripe and Thrivecart every Monday for missed payments and cancellations, send a report, and save missed-payment emails with each customer's Stripe payment link as Gmail drafts, with membership access changed only after the owner approves.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code (the author uses the VS Code extension with a Claude Max subscription); access to the payment platform (Stripe), checkout platform (Thrivecart), email (Gmail) and community platform (Circle); a way to run the check each Monday; the author's approval step before membership access changes
Run my weekly membership payments check. Using the connected tools, look in [checkout platform, e.g. Thrivecart] for cancellations and in Stripe for missed or overdue payments since [last check date]. Give me a report listing each member affected, what happened, the amount and date. For each missed payment, find that customer's Stripe payment link and write a short, friendly email draft in Gmail that includes the link, using [my email tone notes]. Save these as drafts only; do not send anything. For each cancellation, list the change you would make to the member's access in [community platform, e.g. Circle] and wait for my approval before changing it. Don't cancel subscriptions, issue refunds, delete members or contact anyone yourself.

