How to chase clients for missing documents

By Babagana Zannah, team lead · Published 6 August 2026 · Updated 6 August 2026

Babagana Zannah
Leads engineering teams; puts AI to work inside one of the UK's largest companies

Client document chasing works best as a controlled record process, not a stream of increasingly urgent emails. The practice needs one current list, one clear request, a reliable way to reconcile replies and a named owner for anything uncertain.

The process below covers operational administration for UK accountancy and bookkeeping practices. It does not decide which records a client must keep, whether evidence is sufficient, whether Making Tax Digital applies, or how tax and accounting matters should be treated. Those decisions stay with appropriately authorised people using current guidance and the engagement facts.

1. Confirm the request is within scope

Before contacting the client, confirm that the practice is responsible for requesting the item and that the agreed service covers the work. ICAEW’s engagement-letter resources describe engagement letters as a record of the contract and the work to be carried out. Use that record to establish:

• the engagement and period;
• who decides which records are required;
• the authorised client contact;
• approved communication and return routes; and
• who handles questions, disputes and professional decisions.

Do not infer authority from an old email thread. Resolve a changed recipient, unclear service boundary or unapproved return route before sending.

2. Build one missing-items list

Choose one controlled tracker as the operational source for the chase. It can link to an existing practice system; it should not become another archive of client documents.

Use a separate record for each requested item. Useful fields include:

• client and engagement reference;
• item and period;
• current factual state;
• last verified timestamp;
• requested response date;
• approved return route;
• next action and owner;
• stop or exception state; and
• evidence reference for contact, receipt and decisions.

States should distinguish requested, partly received, received for review, accepted, not applicable, disputed and blocked. A single “done” state is too vague: it could mean a file arrived, a reviewer accepted it or a filing occurred.

HMRC’s digital-record guidance says taxpayers or their agents may need to create and store digital records and continue keeping supporting records. The responsible professional must determine what that means for the individual client. The tracker only manages the resulting approved request.

3. Verify the list immediately before contact

A stale request wastes time and can damage trust. Check the agreed inboxes, portal, folders and tracker just before a message is approved or released.

For each item, ask:

• Has it arrived through another approved channel?
• Is it already waiting for review?
• Has an authorised person marked it not applicable?
• Has the client or engagement changed?
• Is the intended recipient still authorised?
• Is the return link, mailbox or portal working?

Record the check time and who performed it. If the workflow cannot do a reliable pre-send check, keep approval with a person who can.

4. Make the request specific

A useful message tells the client:

1. which engagement or period the request concerns;
2. the exact items currently missing;
3. the approved return route;
4. the practice’s requested response date;
5. how to report “already sent”, “unavailable” or “not applicable”; and
6. where to ask a question or request an accessible alternative.

Use the accountant reminder-email templates as structures. Keep the client response date separate from an official filing date. Only include an official date after it has been confirmed for that client.

HMRC’s agent toolkit advises practices to set expectations for record submission and tailor communication to the client’s circumstances and digital capability. A cadence therefore needs judgement; there is no responsible universal rule such as “send three reminders two days apart”.

5. Minimise data in the message and tracker

The ICO’s data-minimisation guidance says personal data should be adequate, relevant and limited to what is necessary for the purpose.

Apply that to the full workflow:

• avoid sensitive detail in subject lines;
• copy only necessary, authorised recipients;
• request only the agreed item;
• point to an approved return route;
• store state and evidence references instead of duplicate documents; and
• define a safe route for unexpected personal data.

Do not request credentials by email. If a client sends them, stop routine processing and follow the practice’s security route.

6. Reconcile each reply before another reminder

A reply changes the known state, so pause the routine sequence until it has been classified.

• Expected item received: link it to the approved location and mark it received for review.
• Partial response: record what arrived and ask only for the remaining item.
• Already sent: check approved locations and correct the tracker before contacting the client again.
• Not applicable: route the statement to the person authorised to decide.
• Question: send it to someone competent to explain the request.
• Unexpected sensitive content: limit copying and follow the privacy or security process.
• Complaint, dispute or vulnerability: stop routine chasing and give it to the named owner.

Receipt is not acceptance. Keep filing or storage, reconciliation and professional review as separate actions with separate evidence.

7. Use stop rules that a system can follow

Write the rules before launch. Stop the routine path when identity, authority, scope, the requested item or the next date is unclear; the channel fails; the client disputes the request; the reminder limit is reached; or professional judgement is required.

Each exception needs:

• a safe current state;
• the evidence available;
• the named owner;
• the action that must not occur; and
• the condition for resuming or closing.

“Send to the team” is not enough. Name a role and set an expected response path.

8. Test with representative edge cases

Use synthetic data and exercise the uncomfortable cases as well as the expected path:

• an item arrives one minute before a scheduled reminder;
• only one of several files arrives;
• the client says it was sent through another channel;
• the recipient changes;
• the return route fails;
• a password or unrelated sensitive file arrives;
• two people update the tracker at once; and
• an authorised person pauses the chase.

Check the message, source record, file location, next action and audit trail after every test. A successful email delivery does not prove that the workflow can stop or reconcile safely.

9. Measure process facts, not assumed outcomes

Useful operational counts include requests approved, messages delivered, replies classified, items moved to review, exceptions raised, duplicate chases prevented, failed actions and human handling time.

Those counts do not by themselves establish compliance, accuracy, tax saved, client satisfaction, successful filing or a financial return. Compare periods with the same definitions and include preparation, approval, review and exception work.

If the main requirement is a controlled nudge, simple scheduling may be enough. If reply classification, permitted filing, tracker reconciliation and exceptions are central, use the automated reminders versus managed chasing comparison.

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 official guidance, the engagement or the operating process changes.

• HMRC: Get ready for MTD, preparing your clients
• HMRC: Use MTD for Income Tax, create digital records
• ICO: Principle (c), data minimisation
• ICAEW: Engagement letters

Questions owners ask