Bookkeeping client communication: plan reminders and know when to call

One email about missing documents is not a follow-up plan. Decide in advance how many reminders to send and how far apart to send them. Also decide what to change if the client still does not answer: the wording, the way you contact them or the person who follows up.

Without that plan, every quiet client becomes an improvised judgment call, decided differently by whoever happens to be covering the file that week. Two clients with identical silence can end up treated very differently depending only on who noticed first.

Use a reminder schedule, not occasional emails

A reminder schedule sets when each contact should happen. It is not the same email resent whenever someone remembers. Practice-management writers recommend treating document collection as its own stage before preparation and review. Give it a checklist and a reminder schedule, rather than fitting it in when someone notices missing records.

Write down the reminder schedule, even briefly. That helps the team follow it during busy weeks and staff changes. A habit kept only in one person's memory disappears when that person is away or leaves.

An original three-stage reminder example

The specific intervals below are an illustrative starting point, not a rule any particular software enforces or a number drawn from independent research. A practice should set its own based on its engagement terms and deadlines.

Original three-stage reminder schedule

Day	Stage	Message focus
Day 0	Initial request	List the exact items needed and the due date, nothing vague.
Day 7	Reminder 1	Restate only the items still outstanding, same channel.
Day 14	Reminder 2	Name the specific deadline this now puts at risk and the next step if unanswered.

Decide what to change when reminders do not work

Escalation means changing the response to a problem, not just sending a more forceful copy of the same email. You might call instead, involve another authorized contact at the client or tell the firm's account manager or partner that a deadline is at risk. Choose the action and person based on each client's service agreement. One rule will not suit every client.

Case file: documents received eleven days after the deadline

A fictional client is asked on day 0 for three items — a July bank statement, an August credit-card statement, and a signed engagement-letter addendum — due by day 10.

Original case: from request to escalation to resolution

Day	Action	Outcome
Day 0	Initial request sent, three items listed, due day 10.	No response.
Day 7	Reminder 1 sent.	No response.
Day 14	Reminder 2 sent; now four days past the due date.	No response.
Day 17	Escalation: account manager calls the client directly.	Client was traveling; commits to a new date.
Day 21	All three items received.	File reopened for processing.

The escalation here was not a fourth email. It was a different channel and a different person, triggered at a defined point rather than left to whoever happened to feel frustrated enough to pick up the phone.

What this plan does not promise

Bookwits documents, clients and tasks can keep the missing-item list, due date and reminder history with the client's file. Staff can track the schedule and hand the follow-up to a colleague. This supports manual follow-up by the firm. It does not promise automatic reminder emails, a client response or bulk messaging and customer relationship management (CRM) tools. Confirm any specific automatic-sending feature separately using current information.