AI Prompts for Accountants: The Conversations That Actually Cost Time
AI prompts for the accounting work that eats the most time: plain-English tax explanations, chasing records, scope changes, and rate-rise messages.
- Updated
- Read
- ~6 min

The prompts worth having as an accountant are not the ones that write LinkedIn posts about tax season. They are the ones that get you through the awkward client conversations - a technical position explained in plain English, a polite chase for the records a client keeps forgetting to send, a scope message when the engagement has drifted past what you quoted.
Those are the exchanges where time disappears. A single scope email can take forty minutes to write and still land wrong. The six prompts on this page cover the conversations where that keeps happening, written to supply the relationship and the context rather than ask you to fill in a blank.
Before you use any of these
Three things that change the output more than any prompt tweak.
- Give it your own writing. Paste two or three of your real client emails and tell the assistant to match that voice. Generic prompting produces generic, obviously-AI prose. Your actual style is what distinguishes the draft from the template.
- Say what you want to happen. Not “write a reply” - “write a reply that gets the missing bank statements by Friday without implying this is the third time I have asked”. The outcome is the instruction.
- Name what you never say. This does more work than describing the tone you want. “No ‘please find attached’, no ‘kindly’, no listing three reasons in a row” removes more AI-sounding output than “be professional” ever will.
1. Explain a technical position in plain English
The job is not translation. It is a rewrite that keeps the position exactly as you would stand behind it, but removes the hedging a client reads as evasion and the jargon a client reads as a bill. The failure mode is simplifying so far that the position shifts - which is how clients act on something you did not actually say.
I need to explain a technical tax or accounting position to a client whose business is [describe the business]. They are not an accountant and will read anything over three paragraphs as a bill in waiting.
Here is the position exactly as I would state it to a peer:
[paste the technical note]
Rewrite this as a client email that:
- preserves the position without softening it into something I did not say
- removes qualifiers that exist for a peer audience but read as hedging to a client ("generally", "typically", "in most cases" - keep only where the qualifier changes the answer)
- replaces jargon with the plainest word that still means the same thing
- ends with a single specific action for the client, which is [what you want the client to do next]
Do not add reassurance I did not write. Do not list three benefits. Do not begin with "I hope this finds you well".Note: Any sentence that softens the position - 'you could consider', 'it may be worth' - should be put back the way you wrote it, because the client acts on the softer version and the file keeps the harder one.
Limitation: the rewrite depends on the technical note you paste. If that note hedges where you did not mean to, the output will carry the hedge. Write the peer version plainly first, then let the prompt do its job.
2. Chase a client for records without sounding like it is the third time
This email does three things and most people only remember the first: it asks for the records, it says what happens if they do not arrive, and it offers a route that is not “send them”. Written as nagging, it reads as nagging. Written with the three jobs separated, it does not.
Write a chasing email to a client for records I need to progress their work. Context on the relationship: [describe the relationship] - adjust the tone accordingly. The records are [what the records are]. The deadline and consequence: [when the deadline is and what happens if it is missed]. The email must do three things, in this order, in no more than four short paragraphs: 1. State specifically what I need and by when, without recapping how long we have been waiting. 2. State what happens if the deadline is missed - the filing moves, the fee changes, the work stops - stated as a neutral consequence rather than a threat. 3. Offer a route that is not "send them" - a short call to talk through what is held up, or a list of alternative sources (bank export, accountant from a prior year, a letter from HMRC/FBR) I can pursue on their behalf for a stated fee. Do not apologise. Do not blame. Do not say "I know how busy you are".
Note: The third paragraph is the one most chase-emails leave out, and it is the one that changes the response rate. A client with a route that is not 'find the records' will take it.
Limitation: this works for records a client has, somewhere. For records a client genuinely does not have, the useful next step is not an email at all - it is a call to decide whether you reconstruct what is reconstructible or scope the engagement down.
3. Rewrite a scope message that has started to drift
Scope creep is rarely one big ask. It is six small ones, each reasonable in isolation, and an engagement that was priced for the brief in March doing the work for a brief that now has eleven lines of extras. The honest message says so, offers a route forward, and does not read as a complaint - which is what makes it hard to write cold.
I need to write to a client whose engagement has drifted past what we agreed. Here is the original scope: [describe the original scope]. Here is what has been added since: [list what has been added, with dates where possible]. What I want to happen: [describe the outcome you want]. Write a message of no more than five short paragraphs that: - confirms the extra work is useful and I am happy to do it - states plainly that it sits outside the original engagement - gives a price for the addition, or proposes a swap against something already in scope that we can defer - ends with a single specific question that moves the decision forward Do not list the items as a complaint. Do not say "going forward". Do not thank the client for their patience.
Note: Read the second paragraph for tone: does it read as neutral record-keeping, or as an accusation? If the latter, rewrite that paragraph by hand before sending.
Limitation: the prompt cannot tell you whether the addition really is out of scope. If the original scope was vague, no email fixes that, and the honest answer may be to absorb this one and write a tighter scope for the next engagement.
4. Pre-engagement questions for a vague brief
A brief that does not say enough to price is a brief that does not say enough to deliver. The expensive mistake is quoting it anyway. The cheap one is a short, friendly message that asks the three or four questions that would let you quote properly - and that reads as professional rather than evasive.
A prospect has asked me to quote for the following: [paste what the prospect sent]. I provide [describe your service and typical pricing structure]. Write them a short reply - no more than four short paragraphs - that: - confirms I can help, in one sentence, without over-selling - asks the three or four questions I need answered to quote properly, as a short list rather than prose - states the one piece of information they will need from me before engaging (my process, my data policy, my turnaround) so the exchange feels reciprocal - ends with a specific next step and a suggested time frame Do not list five selling points. Do not promise a quote within an hour. Do not open with "Thanks for reaching out".
Note: A prospect who sees three questions and a next step replies to all four items. A prospect who sees a paragraph with questions buried in it replies to one.
Limitation: the questions are the generic set. The specific question for your practice - the one that comes from having been burned by a particular kind of engagement - is still yours to add.
5. Decline work without burning the relationship
Saying no is an accounting skill. Capacity is finite, some briefs are a bad fit regardless of fee, and most practices undercharge because the alternative feels like saying no - which it is. The prompt below writes a decline that is short, specific, and points somewhere useful.
I need to decline work. The ask was: [paste what was asked]. My real reason is: [state the reason in one honest sentence]. I can offer this as a next step: [state a referral, alternative timing, or "nothing"]. Write a reply, three short paragraphs maximum, that: - declines clearly in the first paragraph rather than burying it after two of context - gives a reason that is honest but short - no self-flagellation, no five lines of apology - offers what I can offer, whether a referral or an alternative timing, in one specific sentence - closes without a hedge that opens the door to a counter-offer I do not want Do not say "unfortunately". Do not say "at this time". Do not offer to "revisit this in the new year" unless I have said I actually will.
Note: Read the decline sentence in isolation. If the client would not know, from that sentence alone, that the answer is no, rewrite it until they would.
Limitation: this decline is for a professional no. For a client who is behaving badly, the useful message is shorter and less relational than this one, and often not an email at all.
6. Raise your rate on an existing engagement
Early, briefly, and without an essay of justifications. A long explanation invites a negotiation about each reason in turn, and the longer the message the more negotiable the rate feels. The prompt resists that instinct, because the instinct is strong and it is what weakens the message.
Write a rate-rise message to an existing client. Current rate and new rate: [state the old and new rate]. The new rate starts on: [state the effective date]. Relationship context: [describe the engagement].
Three short paragraphs, no more. The message must:
- state the new rate and the date it starts, in the first paragraph, without a preamble
- give one sentence of context that is specific to this engagement rather than generic ("costs have risen" is generic; "the scope we agreed in 2024 has grown by two monthly tasks" is specific)
- close with a line that invites a conversation if the client wants one, without implying the rate itself is up for discussion
Do not apologise. Do not list three reasons. Do not open with "I hope the quarter has gone well".Note: One specific, honest reason costs nothing to concede. A list of reasons gives the client four openings to push back on.
Limitation: the prompt cannot tell you whether the new rate is the right one. That number depends on your market, your pipeline, and how much this engagement is costing you to keep at the old rate - and those are not in the prompt.
What to do with the output
The same discipline applies to every one of these prompts:
- Read the draft as the client will read it. Not as you intended it.
- Cut anything that sounds like a policy. Clients hear policy as “a rule I did not agree to”.
- Put back the specific detail only you know. A reference to the project in March, a call three weeks ago, the favour done or asked for - the thing the prompt could not know and that turns a draft into your message.
- Keep what you cut. Save the discarded phrases in a document and reuse the openings and closings that worked. Over six months you will have a short set of lines in your own voice that no prompt could have produced.
And if the output sounds obviously like AI, the quickest fix is not a better prompt - it is the two or three paragraphs of your real emails pasted in next time.
Where to go next
- The rest of the prompts series. ChatGPT prompts for small business covers quoting, invoices, and money conversations that sit alongside this page, and AI prompts for freelancers covers the audience-specific set for solo operators.
- Data and tier questions. Is ChatGPT safe for business data covers what happens to information pasted into the major assistants, and ChatGPT Business vs Plus covers which tier changes the answer.
- How AI shows up across practice work. AI by industry has a finance and accounting section covering the broader picture of where AI fits and where it does not.
Share this guide
Keep reading
Category hub
AI Prompts
How to write AI prompts that get usable results - what a prompt is, a structure you can reuse, worked examples by task, and the mistakes that waste time.
In this category
AI Prompt Examples
Annotated AI prompt examples across ten everyday tasks - the thin version, the rewritten version, and what each added line is actually doing.
In this category
ChatGPT Prompts for Small Business Tasks
Task-specific ChatGPT prompts for quotes, invoices, suppliers, customer messages, hiring, and admin - with the context each one needs to be useful.
In this category
AI Prompts for Content Writing and Editing
Prompts for the parts of writing AI is actually good at - outlining, restructuring, tightening, and critique - with the drafting traps to avoid.
In this category
AI Prompts for Freelancers: Scope, Rates & Client Emails
AI prompts for the freelance conversations that cost money: scope creep, raising your rate, a client who has gone quiet, and saying no without burning it.
In this category
AI Prompts for Real Estate Agents
AI prompts for real estate work that eats a week: listing descriptions, cold outreach, showing follow-ups, and price-cut messages for sellers.
Questions
Frequently asked questions
Which AI prompts are actually useful for an accountant?
Not the content ones. The prompts that return the most time are for the three jobs that fill a practice week and are rarely talked about in software demos - turning a technical position into a plain-English client email, chasing a client for the records they have not sent, and rewriting a scope message when the engagement has drifted. Those are also the jobs where a confidently wrong AI answer is cheapest to catch, because you read every output before it leaves.
Is it safe to put client data into ChatGPT or Claude?
Not into the free tiers, and not without reading the data terms of whichever tier you use. Business and enterprise plans of the major assistants have different data handling than their free versions, and the training default is not the same across vendors. The safe version of this work keeps client identifiers out of the prompt entirely - names replaced, amounts rounded, dates generalised - which is a discipline rather than a setting. Our page on whether ChatGPT is safe for business data covers the specifics.
Can AI replace a qualified accountant?
No, and the ways it is sold as doing so are the ways it is most likely to produce a confident, plausible, wrong answer. AI drafts correspondence, summarises long documents, and restructures explanations. It does not take responsibility for a filing, a figure, or advice, because responsibility cannot be delegated to software. The practice is still yours, and so is the signature.
What are the most common mistakes when using AI for accounting work?
Four show up repeatedly. Treating AI output as verified when it was not, which is how incorrect figures reach clients. Pasting identifiable client information into a free-tier tool. Using AI for the final version of a technical explanation without a qualified review. And building an entire client email on a prompt without reading the output as the client will read it.
How do I stop AI-generated client emails sounding like AI?
Paste three of your own real emails and tell the assistant to match that voice, then name what you never do - no "please find attached", no "feel free to reach out", no three-adjective lists. The second half does more work than the first, because AI-sounding writing is usually not badly written - it is generically polite in a way you are not.
Should I send what AI drafts to clients without editing?
Never. Treat every output as a draft that has removed the hardest part - the blank page - and nothing more. Read it as the client will read it, cut anything that sounds like a policy rather than a person, and put back the specific detail only you know. The draft saves you ten minutes of staring at a cursor. The judgement is still the whole job.
Are there prompts for tax returns on this page?
No, deliberately. Returns and filings are the work AI assistance should never touch without a human sign-off on every line, and there is no prompt on this page that would survive a professional body's review as "AI drafted this filing". What is here are the conversations around the work - explaining it to a client, chasing the records that feed it, and setting expectations before it starts.