Client email reply checklist for bookkeepers
Why a checklist
Client emails about money arrive one at a time, mid-task, and are answered fast. The mistakes are not dramatic. They are a transposed amount, an export from last week, a promise that sounded casual and was not. A fixed list catches them because it asks the same questions every time.
Read each line as a yes or no question, and use the list as a gate between "drafted" and "sent". The longer guide on answering a client's categorization question explains how to build the reply; this is the check on the finished text.
The checklist
The question
- I can state in one sentence what the client actually asked.
- The reply answers that question first, not a related one.
- If the question was ambiguous, the reply asks which transaction or period they mean.
The sources
- I found the exact ledger line, not a similar one.
- The export or report I used is dated, and the date is later than any change the client mentions.
- Each figure in the reply appears on a source line, and I checked the digits.
- Each date is right, including the year, and the period named matches the period asked about.
- Each rule I mention is in our written procedures, and I know the section.
The wording
- The reply states what the ledger shows, not what I assume happened.
- Anything uncertain is said to be uncertain, with what would settle it.
- There is no promise about a tax result, a refund, a deadline outcome or a penalty.
- Any request to the client is specific: which document, by when.
- The reply does not name another client or reveal anything that is not theirs.
The routing
- The topic is not one that always goes to the owner, the client's tax preparer, EA or CPA.
- If the client mentioned a notice, an audit, an amended return or a penalty, I stopped and routed it instead of answering.
- A short notice that this is not tax advice is on the reply if our procedures call for one.
The mistakes this list is built to catch
| Mistake | What it looks like | What stops it |
|---|---|---|
| Wrong line | Answering about a $480 payment when the client meant a different $480 | Match payee, date and amount, not amount alone |
| Stale export | Saying an invoice is unpaid after it was paid yesterday | Date the export and say "as of" in the reply |
| Loose promise | "That will be deductible" | Describe the bookkeeping, hand off the tax question |
| Memory rule | "We always put that in supplies" | Quote the procedure or say there is none |
| Wrong period | Quarter totals that include a line dated just outside it | Check the first and last date of every total |
| Silent gap | A total that leaves out an uncategorized line without saying so | List excluded lines and why |
Three habits that make the checklist faster
- Put the sources next to the draft. Have the ledger line and the procedure open while you read the reply. Reading from the draft alone checks wording, not truth.
- Say "as of" every time. A reply about a balance or a payment status is true on a date. Naming it protects you and tells the client how far to trust it.
- Keep a short escalation list. If your firm decides once which topics are never answered by email, nobody has to decide it again under pressure. For example, the list might cover anything involving a tax authority's notice, an audit, an amended return or a penalty.
When the checklist says stop
If any box cannot be ticked, do not send. Either fix the gap or send a holding reply that says you are looking into it and when you will come back. A holding reply with a date is better than a quick answer that has to be corrected later, in a second email that undoes the first.
How GroundedReply does this step
GroundedReply builds several of these checks into the draft. You upload the client's question, your written procedures and a QuickBooks or Xero ledger export. The draft cites the ledger line or procedure sentence behind each claim, and code checks every figure against the source it cites. If a figure cannot be traced, the draft is held back and marked as needing a manual answer, with the sources listed so you can write the reply yourself.
Questions about amended returns, IRS or state notices, audits, penalties and legal matters, and any topic your own procedures say to escalate, get only a fixed holding reply. That is the escalation list from above, applied by code before anything is drafted. A second AI model reviews each draft, fixes what it can and lists the rest. Every reply carries the notice "Not tax advice. Read this reply before you send it."
You still read it and you still press send, from your own inbox. A reply costs 3 credits and there is no subscription. To try it on a real client question, sign up.
Questions
- Is a checklist overkill for a two-line reply?
- The short replies are where the slips happen, because nobody rereads them. Once the list is habit it takes very little time, and the check that matters most is the one on numbers and dates.
- Who should send the reply, the owner or a junior?
- Whoever your procedures name. What matters is that the sender reads the whole reply and the sources behind it first, and that your firm decides in advance which topics always go to the owner.
- Should replies be kept with the client file?
- Yes. Keep the sent reply and the export it was based on together, so you can answer a follow-up months later without redoing the work. Check your retention policy for how long.
Stop typing the same five answers from memory.
Sign in, upload the question, your procedures and a ledger export, and get a cited draft.