Organise document collection around a checklist for each client and period, separating received, missing and unreviewed items. You can assess a Digital Employee for maintaining that register and preparing outstanding requests within agreed rules. Receiving a file does not establish its accounting or tax correctness: the professional still assesses what the engagement needs.
Organise the cycle by client and period
In an accountancy firm, “a document is missing” is too vague to direct the work. You need to know which client it belongs to, which period it covers, who requested it and which activity is waiting. A defined recurring cycle makes targeted requests possible and exposes exceptions without rereading every conversation.
The checklist comes from the engagement and the professional's instructions. It may differ between clients: do not assume everyone must provide the same documents. You can assess a Digital Employee for tracking collection, classifying received material and preparing permitted reminders. The professional decides whether that material is suitable for the accounting or tax work.
A register that prevents outdated requests
This is an illustrative example: Arco Services and Bosco Workshop are fictional clients. “April” identifies an internal collection period only, not a statutory filing deadline. File labels are synthetic references and contain no real client data.
Scroll the table horizontally to read every column.
| Client / period | Expected document | Status and evidence | Action and owner |
|---|---|---|---|
| Arco / April | Operating account statement | F-21 received, but it covers March. | Assistant: retain F-21 against the correct period and prepare a request for April. |
| Arco / April | Purchase documents in the checklist | Archive F-22 received; contents awaiting review. | Staff member: compare with the list; do not confirm completeness to the client. |
| Arco / April | Agreed expense schedule | Missing; no receipt recorded. | Assistant: include in the outstanding request after checking the latest authorised channel. |
| Bosco / April | Operating account statement | F-31 received and linked to the period. | No reminder for this document; pass it to the required review. |
| Bosco / April | Purchase document A-18 | F-32 and F-33 appear to be two versions of the same document. | Professional: confirm the relevant version; neither delete nor record it twice. |
| Bosco / April | Clarification about document A-19 | Reply M-8 received, awaiting review. | Professional: assess the reply; pause its associated reminder. |
Arco should not receive a general “everything is missing” message: its purchase archive has arrived, although it needs review. Bosco should not receive another request for the statement or the A-19 clarification. “Received” describes an event; “checked” requires the agreed intervention. Preserving that distinction prevents collection from being closed too early.
Match attachments without guessing their identity
Before linking a file, check the evidence permitted by the process: client, period, document type and request reference. Its filename alone may be insufficient. If “final_documents.zip” arrives from an address shared by several clients, flag the ambiguity to the owner rather than choosing the most likely file.
Retain the source, receipt, version and status. A document for the wrong period belongs in its appropriate context and does not satisfy the current request. Similar attachments may be corrections, copies or different documents. Prepare the comparison, leaving replacement and recording decisions to the competent person.
Prepare reminders only for what is still missing
Before each send, check the current status, latest attachments and any individual arrangements. Define frequency, attempt limits, recipients and hold conditions. If a client reports a difficulty, challenges the request or has agreed a different next step, return the case to its owner. A process schedule does not create a tax deadline.
Hello, to complete the April collection we still appear to need the operating account statement for April and the agreed expense schedule. We have received the purchase document archive and it is being checked. The account file received covers March. Could you send the remaining material through the channel already agreed with the firm? If you have already supplied it, please give us the reference so we can update the request. Thank you.
This illustrative message is ready for the owner's review. It adds no dates, threats or documents outside the checklist. During the first pilot you can limit the process to drafting. Subsequent sends require agreed permissions and rules; approval for one client does not automatically extend access or communication to others.
Hand over an understandable working pack
At the end of a cycle, prepare an index by client and period showing received files, uncertain versions, outstanding requests and replies awaiting assessment. Link each entry to its authorised source. The professional should understand why a document is classified or held without reconstructing the inbox.
The accountancy service page describes collection, reminders and file updates within defined access and rules. These activities do not certify accounting, tax or documentary correctness. Agree client-level access, channels and permitted actions using the guide to controls and approvals. Avoid combining several clients' documents in a context accessible to people who do not work on those engagements.
Check a complete cycle, including exceptions
Choose a bounded client group and one collection process. Test files covering other periods, late replies, revisions and documents already supplied. Measure unnecessary requests, wrongly assigned attachments, owner time and work remaining before professional review. Your pilot metrics should include these checks, not just the number of reminders prepared.
Begin with the checklist, authorised channels and anonymised examples described in the first-project guide. The outcome to assess is a more organised, reviewable collection process. The professional retains responsibility for deciding what the engagement requires.