Accountant client reminder email templates
Babagana ZannahLeads engineering teams; puts AI to work inside one of the UK's largest companies
A useful accountant reminder names the outstanding item, period, approved return route and requested response date. It also gives the client a simple way to report an error, ask a question or explain that the item does not apply.
A client reminder should make one current task easy to understand. It should not make the client guess what “the records” means, where to send an item, or whether a date is the practice’s planning date or an official deadline.
These templates are starting structures for UK accountancy and bookkeeping practices. They are not tax, accounting or legal advice, engagement terms, statutory notices or debt-collection wording. Approve the identity, channel, cadence, data handling and escalation route before using them with live client data.
Check the request before writing the email
The wording is only as reliable as the record behind it. Before a message is prepared, confirm:
- the engagement and period;
- the person who decided the item is required;
- the authorised recipient;
- the current missing-item state;
- the approved return route;
- the practice’s requested response date;
- any official date confirmed by the responsible professional; and
- the person who owns questions, disputes and exceptions.
ICAEW’s engagement-letter resources explain why the work and responsibilities agreed with a client need a written record. A reminder should stay within that recorded scope. It should not expand the engagement because an old template happened to mention another service.
HMRC’s MTD agent toolkit advises agents to set expectations for record submission and tailor communication to the client’s circumstances, digital capability and support needs. Build an accessible alternative into the process rather than improvising one after a client cannot use the standard route.
Template 1: first request for specific records
Use this after the required items, recipient and channel have been checked.
Subject: Records needed for [engagement or period]
Hello [client name],
To continue the work for [engagement or period], please send these items through [approved return route]:
- [specific item and period]
- [specific item and period]
Please send them by [requested response date]. This gives our team time to check what arrives and contact you if anything is unclear.
If an item does not apply, is unavailable or has already been sent another way, please reply and tell us. We will check the record before contacting you again.
[Practice sign-off]
The email separates delivery from later review. It does not say that sending a file completes the work or establishes that the file is sufficient.
Template 2: reminder for one outstanding item
Use this only after confirming that the earlier request was delivered and the item still appears as missing.
Subject: Reminder: [item] for [engagement or period]
Hello [client name],
Our current record shows this item as outstanding:
- [specific item and period]
Please send it through [approved return route] by [requested response date]. If you sent it recently, reply with the route you used and we will check the tracker before sending another reminder.
If you are unsure what is needed or cannot use that route, contact [named team or role] at [approved contact route].
[Practice sign-off]
Avoid “you still haven’t sent it” unless every approved location has been checked and that statement is accurate. A neutral description of the current record gives the practice room to correct its own data.
Template 3: deadline-aware request
Use this when an authorised person has confirmed the relevant workflow date and the practice has set an earlier client response date.
Subject: Action requested by [client response date]: [missing item]
Hello [client name],
We are preparing [engagement or work description]. Our current record shows that we need:
- [specific item and period]
Please send it through [approved return route] by [client response date]. That is the date our practice has set to allow time for checking and any follow-up before the confirmed workflow date.
If the item does not apply, circumstances have changed or you need another way to provide it, please contact [named team or role]. Do not send sensitive information through an unapproved channel.
[Practice sign-off]
Keep the client response date and the official or filing date in separate tracker fields. The first is an operational planning date. Presenting it as a statutory requirement would be misleading.
For a period-specific process, use the MTD quarterly record-collection checklist and re-open HMRC guidance for that client’s position.
Template 4: acknowledge a partial response
This prevents any reply from being mistaken for completion.
Subject: Part of your response received for [engagement or period]
Hello [client name],
Thank you. We have recorded this item as received for review:
- [received item]
Our current checklist still shows this item as outstanding:
- [missing item]
Please send it through [approved return route] by [requested response date], or tell us if it is unavailable or does not apply. A team member will review what you supplied; this acknowledgement does not mean the records have been professionally accepted or the work is complete.
[Practice sign-off]
“Received for review” is deliberate. Use “accepted” only after the person authorised to make that decision has done so.
Template 5: pause for an exception
Use this after a question, dispute, personal circumstance or security issue stops the routine sequence.
Subject: Your message about [engagement or period]
Hello [client name],
Thank you for letting us know. We have paused the routine reminder for [item or engagement] while [named team or role] reviews your message.
You do not need to resend the same information. We will contact you through [approved channel] when the next step has been confirmed.
Please do not email credentials or additional sensitive records unless a team member confirms the approved route.
[Practice sign-off]
The tracker should show the owner and safe next state. It does not need a full copy of sensitive information from the client’s message.
Keep personal data out of unnecessary places
The ICO’s data-minimisation guidance says personal data should be adequate, relevant and limited to what is necessary for the purpose. Apply that principle to the subject line, recipients, message body and operational tracker.
Before approval, ask:
- Does the subject line disclose more than the recipient needs?
- Are every copied recipient and every requested field necessary?
- Can the tracker hold a state and evidence reference instead of another copy of the document?
- Does the message direct the client to a suitable approved route?
- Is there a controlled path for unexpected or sensitive replies?
Never ask for passwords or access credentials by email. If they arrive anyway, stop ordinary handling and follow the practice’s security process.
Put stop rules beside the templates
Pause routine messages when the client replies, the item appears in another approved location, the request is disputed, the recipient or authority is unclear, a channel fails, a security concern appears, or the agreed reminder limit is reached. A complaint, vulnerability or question requiring professional judgement also needs a named human owner.
Test each template with synthetic data before launch. Include a file arriving just before a scheduled reminder, a partial response, an “already sent” reply, a broken return link, a changed recipient and an unexpected sensitive attachment. Check both the message and the tracker after each case.
The complete operating sequence is covered in how to chase clients for missing documents. If the practice is deciding between a send-only tool and wider workflow support, compare automated reminders with managed client chasing.
Sources and review status
Author: Babagana Zannah. Published 6 August 2026 and last updated 6 August 2026. Sources checked 6 August 2026. Next editorial review due 6 November 2026.
The following primary sources were re-opened on the source-check date. Recheck them sooner if the engagement, law or operating process changes.
- HMRC: Get ready for MTD, preparing your clients
- ICAEW: Engagement letters
- ICO: Principle (c), data minimisation
Questions owners ask
Can I copy these reminder emails straight into my practice?
Use them as structures, not approved engagement, legal or tax wording. Adapt each message to the agreed service, client circumstances, accessibility needs, data-protection controls and wording approved by the responsible person.
Should an accountant put a filing deadline in every reminder?
Only include a deadline that the responsible professional has confirmed for that client and purpose. Keep the practice's requested response date distinct from any statutory or filing date and allow time for review and exceptions.
What if the client says the document was already sent?
Pause the routine sequence and check every approved inbox, portal, folder and tracker before asking again. Record the reconciliation result so another person or system does not restart the same request.
Can software send these reminders automatically?
Only after the source list, recipient authority, template, cadence, stop rules and exception ownership are agreed and tested. Replies, disputes, sensitive messages and unclear requirements should pause the routine path and return to a person.