Templating recurring communications · AI for Accountants

Open the sent folder of any small accounting practice in Nepal and you will find the same email, in slightly different words, written eight or twelve or thirty times in the same month. The monthly P&L cover note to each retainer client. The VAT-deadline reminder before the 25th. The TDS deduction summary at month-end. The “please send the bank statements” follow-up that goes out, predictably, on the eighteenth and twenty-fifth and last day of every month. Each of these emails took five to fifteen minutes to write. Cumulatively, in a practice with forty clients, they consume a working day a week. This is the work AI is most obviously made for — not because it can write them better than you can once, but because it can give you a template that means you only ever write them once.

The 80/20 rule for templating

Not every email should be templated. Most of the genuinely valuable client work — a tax-planning conversation, a tricky reclassification, a one-off advice memo — is exactly the work that should not be templated, because the value is in the specificity. The templates exist to clear the recurring deck so you have time and attention left for the cases that matter.

The discipline is to look honestly at the last three months of your sent folder and identify any message you have sent three or more times in a single month. These are your templating candidates. In a typical Nepali practice the list is depressingly predictable:

1. Monthly P&L and balance sheet cover note (sent to every retainer client between the 5th and 10th). 2. VAT payment reminder (sent before the 25th of each month). 3. TDS deduction summary (sent after month-end close). 4. Missing-document follow-up (sent whenever a client has not provided what you asked for after seven days). 5. Quarterly compliance summary (sent at the close of each quarter). 6. Annual fee renewal note (sent in Asar or Bhadra, depending on practice). 7. Festival-period filing reminder (sent before Dashain and Tihar when deadlines bunch up).

If you template even these seven, you have already converted the largest single block of repetitive writing in the practice into reusable artefacts. The marginal hour you save each week compounds into a week a year, and that week is the difference between leaving the office at seven and leaving at nine in busy months.

The template prompt

The prompt that builds a usable template is structured, not vague. The shape that works:

Build a reusable email template for the following recurring communication. Show me the variable fields clearly marked in square brackets. Produce both an English version and a Nepali version, side by side, using the same field names in both. The communication is: a monthly P&L and balance sheet cover note sent to retainer SME clients between the 5th and 10th of each Gregorian month, summarising the previous Nepali month’s financial position, flagging two or three notable items, and reminding the client of any pending follow-ups. Tone: warm and professional, suitable for a long-term client relationship. End with a single bold action line that varies depending on whether the client has pending items.

The model returns something you can adopt almost as-is: an email skeleton with [client_name], [month_BS], [revenue_figure], [net_profit_figure], [notable_item_1], [notable_item_2], [pending_items] as the variable fields. You read it, fix the two or three things that feel wrong for your firm’s voice, paste it into your template library, and then — and this is the point — you never write that email from scratch again. The five-minute cover note becomes a thirty-second fill-in-the-blanks exercise.

For the most repetitive templates, take one more step. Build a tiny “filler prompt” that takes the variables as inputs and produces the finished email:

Using the [TEMPLATE NAME] template, fill in: client_name = …, month_BS = …, revenue_figure = …, net_profit_figure = …, notable_item_1 = …, notable_item_2 = …, pending_items = …. Output in both English and Nepali.

Now the workflow for thirty cover notes a month is: open the previous month’s spreadsheet of client figures, copy each row into the filler prompt, hit enter. The bottleneck moves from writing to reviewing — which is where it should have been all along.

Where templates fail — and what the failure tells you

The signal that you have over-templated is unmistakable when it arrives, and it almost always arrives in the form of a polite but unmistakable reply: “This feels like a form letter.” Or, in the Nepali version a Bhairahawa cement dealer once sent a senior CA who had templated too aggressively: “दाइ, मलाई एकजना मान्छेसँग कुरा गरेको जस्तो लागेन।”

This reply is feedback, not failure. It tells you something true: the situation this client is in cannot be handled by a template, and your judgement to send a templated message was the actual mistake. The correct response is not to spin up an AI to draft a more personal-sounding reply; that doubles down on the original error and the client will feel it. The correct response is to pick up the phone, or to write three or four genuine sentences yourself, by hand, with the client’s actual situation in front of you. Some emails are the price of the relationship; charging the relationship for them is the wrong economy.

The deeper rule: templates handle the high-volume, low-stakes communications. Anything genuinely high-stakes — a fee discussion, a disagreement about scope, a sensitive personal matter affecting the books, the death of a partner — is human-only. The model is allowed nowhere near those emails. The cost of getting them wrong is not a corrected document; it is a lost client and a damaged reputation that takes years to rebuild.

A useful mental check before pressing send on a templated message: “If this client reads this and feels processed rather than served, will I regret it?” If the answer is anywhere near yes, abandon the template and write by hand. The five extra minutes are insurance.

Template management for the whole team

A template that lives only on your laptop is a half-built tool. The team around you sends the same emails to the same clients; if each member is drafting from scratch, the practice is paying for the same work three or four times over, and the client receives inconsistent communications signed by different people that read like they came from different firms.

The minimum viable template system is depressingly simple: one shared document per client type, with the current version of each template, dated and owned by one person who is allowed to change it. SME templates. Individual taxpayer templates. Corporate templates. Each document has the seven-or-so templates listed above, in their current bilingual form, with variable fields in square brackets. Anyone who finds a phrase that consistently lands badly proposes a change to the document owner; the owner edits the master; everyone uses the new version.

The bilingual discipline matters more than it sounds. If your English and Nepali templates drift apart over a year — a phrase added here, a tone changed there — you end up sending different actual messages to the English-reading CFO and the Nepali-reading owner of the same company. They will notice. Keep the two versions in the same document, side by side, and edit them as a pair.

A starter set every Nepali practice should have

If your practice has none of this, start with these. They cover roughly seventy percent of recurring outbound communication in a typical small Nepali firm:

1. Monthly P&L cover note (English + Nepali, with variable revenue, profit, and notable-items fields). 2. VAT payment reminder (sent on or before the 22nd of each month, with variable amount and bank reference). 3. TDS deduction summary (sent after month-end, with variable rates and amounts by head). 4. Missing-document follow-up — first request (sent at day-seven of waiting). 5. Missing-document follow-up — escalation (sent at day-fourteen, firmer tone, consequence named). 6. Quarterly compliance status note (sent at the close of each quarter, listing returns filed and pending). 7. Annual engagement renewal (sent in late Asar or early Shrawan, with variable scope and fee fields).

Build them in a single working session — perhaps three hours with a junior staff member helping you collect the recent examples — and you have just bought back roughly a working day a week, every week, indefinitely. There are few investments in a practice with that return on time.

Check your understanding

Quick check

—

A long-term family client replies to your templated monthly cover note with: "This feels like a form letter — I miss the personal touch from before." What is the right response?

Use AI to draft a new, more personal-sounding reply and send it back with the template tweaked for warmth.
Ignore the reply — the template is efficient and the client will adjust.
Recognise the reply as feedback that the template was the wrong tool for this client or this moment, and respond with genuine human contact (a phone call, or a few sentences you write yourself), then consider whether this client should be moved off the templated workflow.
Apologise, then continue using the template because templating saves the practice time overall.

What comes next

You now have the three pieces of an AI-assisted client communication practice: fact-first drafting, paired translation with consequence sentences, and a maintained library of bilingual templates. The next chapter steps back from individual workflows and asks the harder question — how do you build safe AI habits across the entire practice, so that the time you saved this year does not become the risk that lands on your desk next year? Chapter 6 is about the practice-level disciplines: what to log, what to never log, how to onboard staff onto AI tools, and how to set boundaries that hold even when the model gets dramatically better.