Free AI Training / 4 ChatGPT Prompts Every Bookkeeper & Accountant Needs (RCTFC Framework)

4 ChatGPT Prompts Every Bookkeeper & Accountant Needs (RCTFC Framework)

Some bookkeepers are still finishing close week at midnight. Others finished Tuesday and went home. This lesson hands you the exact framework — RCTFC — to turn ChatGPT from a generic-answer machine into a tool that writes client summary emails, sets up transaction categorization rules, builds tax document checklists, and drafts collections emails that actually get paid.

Watch on YouTube →Book a Free Strategy Call →

Overview

Bookkeeping and accounting work is full of writing that isn't the actual numbers work: explaining a close to a client who doesn't read balance sheets, setting up categorization rules for a new client's messy chart of accounts, building a tax document checklist that doesn't waste anyone's time, and following up on an invoice without burning the relationship. RCTFC — Role, Context, Task, Format, Constraints — turns ChatGPT into a tool built specifically for these tasks. This guide walks through four real workflows built on that framework.

What You'll Learn

Understand the RCTFC prompting framework and why each of its five parts matters
Write a client-facing monthly summary email that explains the story behind the numbers
Set up transaction categorization rules that map to a client's actual chart of accounts
Build a personalized tax document checklist instead of a generic form list
Draft a firmer collections email that gets paid without damaging the relationship

Use Case 1: The Monthly Summary Email

Close is done, and now it has to be explained to a client who doesn't read balance sheets — a task that's easy to under-deliver on with a generic "here are the numbers" email. This prompt sets the role as a bookkeeper who writes plain-English summaries, feeds in the actual numbers and what changed from last month, and asks for a client-facing email in three short paragraphs. The constraint to translate every number into what it means for the business, not just state it, is what turns a restated report into an explanation. Flagging the overdue receivables clearly, rather than burying them, is what makes this the email that actually builds client trust.

Translating numbers into what they mean, not just restating them, is the whole point of this prompt
Feeding in what changed from last month gives the email a story instead of just data
Flagging overdue receivables clearly keeps the email useful, not just reassuring

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are a bookkeeper who writes plain-English monthly financial summaries for non-financial clients. Context: Revenue was $45,000 (up from $38,000 last month), expenses were $32,000 (driven mostly by a one-time equipment purchase), net profit was $13,000, and accounts receivable is creeping up — two invoices are now over 60 days late. Task: Write a client-facing summary email covering the month's performance. Format: Three short paragraphs, no accounting jargon. Constraints: Translate every number into what it means for the business, not just what it is. Flag the overdue receivables clearly.

This explains the story behind the numbers instead of just restating them — that's the email that makes a client trust you.

Use Case 2: The Transaction Categorization Guide

A year of uncategorized transactions from a new client rarely fits a standard chart of accounts cleanly — a mobile dog-grooming business has gas charges, payment processing fees, and a scheduling subscription that don't map to generic categories on their own. This prompt sets up categorization rules for those specific patterns, tied to the client's actual chart of accounts. The constraint that every rule must map to an existing account, with no inventing new categories, is what keeps the books consistent with the client's actual setup. That's what turns a generic bank feed into books that actually reflect how this specific business runs.

Naming the actual recurring transaction patterns is what makes the rules specific, not generic
Requiring every rule map to an existing account keeps the chart of accounts consistent
The reasoning behind each rule makes it easy to apply the same logic to future transactions

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are a bookkeeper setting up transaction categorization rules for a new client. Context: Client is a mobile dog-grooming business, chart of accounts is QuickBooks' standard service-business template, and there are recurring charges for gas, mobile payment processing fees, and a monthly software subscription for scheduling that don't cleanly fit the default categories. Task: Write categorization rules for those three recurring transaction patterns. Format: One rule per pattern — the pattern, the category it maps to, and the reasoning. Constraints: Every rule must map to an existing account on their chart of accounts. No inventing new categories.

This turns a generic bank feed into books that actually reflect how this specific business runs, rule by rule.

Use Case 3: The Tax Document Checklist

A generic tax document checklist — "W-2s, 1099s, mortgage interest statements" — is the same list for a W-2 employee and a client with three rental properties, which means half of it doesn't apply and the client wastes time hunting for forms they don't need. This prompt builds a checklist personalized to the client's actual situation: their real income sources and what changed since last year. The constraint to only request documents that actually apply, nothing generic, is what saves everyone the back-and-forth. That's the checklist a client can actually work through in one sitting instead of guessing what's relevant to them.

A client's actual situation — not a generic template — determines what's on the checklist
Grouping by category in plain language keeps the checklist approachable, not intimidating
Only requesting documents that actually apply saves the back-and-forth of a generic list

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are a tax preparer building a personalized document request list for a client. Context: Client has W-2 income, started renting out a second property this year, sold some stock in a taxable brokerage account, and paid for a home office setup for a side consulting business. Task: Write a personalized document checklist for this client's tax return. Format: Grouped by category, plain language, no tax-code citations. Constraints: Only request documents that apply to their actual situation. Nothing generic or boilerplate.

Nobody's hunting for forms that don't apply to them — every line on this list is something this specific client actually needs to send.

Use Case 4: The Collections Email

An invoice sixty days overdue after two ignored friendly reminders needs something firmer, but "firmer" too easily tips into either passive-aggressive or genuinely damaging to the relationship. This prompt writes a response that holds the line — a real deadline, a real consequence — in four sentences a client can't misread. The constraint against exclamation points and vague warnings, requiring the actual consequence stated plainly instead, is what makes this the version that finally gets a reply. It doesn't read like the two emails that already got ignored, because it isn't soft in the way they were.

A real deadline and a real, stated consequence replace vague "please pay soon" language
No exclamation points keeps the tone professional, not passive-aggressive
Four sentences is short enough that the client can't misread what's being asked

Example Prompt

💡 Click "Copy Prompt" below to copy this prompt directly to your clipboard—no typing needed.

Role: You are an accountant writing collections emails that get paid without damaging the client relationship. Context: Invoice is $4,200, now 60 days overdue, and two friendly reminders have already been sent and ignored. Task: Write a firmer follow-up email. Format: Four sentences. One clear deadline. One clear next step if the deadline is missed. Constraints: Professional, not passive. No exclamation points. State the actual consequence, not a vague warning.

This is the version that actually gets a reply, because it doesn't read like the two emails that already got ignored.

Summary

RCTFC doesn't replace the judgment call on which client relationship needs a phone call instead of an email — it saves the twenty minutes you'd otherwise spend rewriting the same email three times. The four prompts in this guide cover the highest-frequency client-facing writing in a bookkeeping or accounting practice: the summary, the categorization rules, the checklist, and the collections email. Each follows the same five-part structure, so it transfers directly from one task to the next.

Next Steps

Run the monthly summary prompt on your next client close, with their real numbers in place of the example. As tax season and overdue invoices come up, the checklist and collections prompts carry the same five-part structure straight through.