Track Missing Client Documents Before Accountant Review

The client has sent a bank statement, but the card statement covers only part of the requested month and an invoice index is still missing. A shared inbox may show what arrived, yet it does not necessarily show what remains, who owns the next request, or whether the case can be handed to an accountant. This guide gives an intake coordinator a manual way to answer those questions.

Start with a restricted spreadsheet or your firm’s existing register. You do not need AI, a new subscription or an automated client portal. The free starter above includes a blank CSV, an example workbook and four entirely fictional cases. It contains no real source documents or client communication.

Scope: administrative completeness and a traceable handoff. The qualified reviewer sets the engagement’s required-document list and checks the original records, figures, classifications and any professional conclusion. An intake status never approves accounting work, advice or a filing.

Set up one record for each expected item

Before requesting anything, have the qualified reviewer confirm which document types and period belong to this engagement. Give the case a non-identifying ID such as FIC-001. In the blank tracker, use one row per expected document, with a document type, requested period, request date, item status, evidence reference, follow-up owner and next check date. Keep an action log when an owner, status or reason changes.

Keep actual files in the firm’s approved, access-controlled repository. A tracker should hold only the minimum references staff need to find those files through authorized access. It is not a place for account numbers, balances, invoice contents, public sharing links or a copy of the client archive. Check the firm’s retention and access rules before using a shared spreadsheet; a file’s sharing setting alone does not make it a professional approval record.

The example workbook demonstrates a fixed set of ten item rows. Its formulas and cached results illustrate the rules for those rows; extend and check the formulas before using more rows. For a new case, begin with the blank CSV or an approved internal system and have a reviewer validate your setup. Do not mistake a fictional workbook cell for a real sign-off.

Use statuses that describe what staff actually know

Receipt and acceptance are separate. Staff may check that a statement is readable and shows the requested dates; they cannot infer that its figures are correct or that it is sufficient for the engagement. If the document type or period is ambiguous, leave the item open. If deciding whether the item is needed involves accounting judgment, use SPECIALIST_SCOPE_REVIEW instead of guessing.

1. Record each expected itemUse a case ID, requested period and evidence reference. Keep originals in approved storage.
2. Assign each exceptionMark missing, partial or uncertain items. Name an owner and next check; ask a specialist about scope.
3. Prepare the handoffOnly an administratively ready case enters the ordinary review queue. The specialist checks original records and decides.

Make a partial submission visible and owned

Filter the tracker to one case. For every open row, write a concrete reason, one next owner and an internal next check date. For example, “card statement shows September 1–19; September 20–30 not recorded” is more useful than “incomplete.” A blank evidence ID means no source is recorded in this example; it does not prove that nothing exists in the firm’s inbox. Reconcile the approved source system before telling a client an item is missing.

Draft a short follow-up that names only the confirmed outstanding items and the relevant period. Do not put financial figures or private document links in the draft. An authorized person must check the recipient, wording and channel before sending through the firm’s existing process. Changing a tracker status does not send a message. Record the actual send reference only after a real authorized send; the fictional starter’s action log includes drafts marked DRAFT_ONLY_NOT_SENT.

If the owner is away, reassign the item explicitly and log the handoff. If the client says an item is unnecessary or cannot be supplied, preserve that reply in the approved system and ask the qualified reviewer to decide what happens next. Do not silently mark the item complete.

Decide whether a case is ready for specialist review

Use a case-level status only after checking the underlying item rows:

1. Any SPECIALIST_SCOPE_REVIEW item makes the case SCOPE_REVIEW until the qualified person decides its scope.
2. Otherwise, any REQUESTED, RECEIVED_UNCHECKED or NEEDS_REPLACEMENT item makes it BLOCKED for an ordinary complete-file handoff.
3. When every required item is ADMIN_ACCEPTED or expressly NOT_REQUIRED after specialist review, mark it READY_FOR_REVIEW.

READY_FOR_REVIEW is a queue entry, not professional approval. An urgent or exceptional case may still be sent to a reviewer as an explicitly incomplete exception under the firm’s own procedure; do not mislabel it ready. The reviewer receives the case ID, expected period, item list, evidence IDs, unresolved exceptions and owner history. They open the original records and make an independent decision. If a source fails that review, record a new exception and return it to the right owner.

Walk through two fictional cases

In the downloadable sample, FIC-001 has three requested items. SYN-001 describes a bank statement whose visible dates cover September 1–30, so staff marked that item ADMIN_ACCEPTED. SYN-002 describes a card statement covering only September 1–19, so its row is NEEDS_REPLACEMENT. The supplier invoice index has no recorded evidence ID and remains REQUESTED. The case is BLOCKED; the follow-up is a draft only. Nobody sent a client message or checked the numbers.

FIC-002 has three ADMIN_ACCEPTED item rows, each with a synthetic evidence ID. Its case status is READY_FOR_REVIEW, meaning the administrative packet can be placed in a qualified review queue. The sample does not claim that the reviewer approved any accounting outcome. The other fictional cases show a wrong-period source and an unresolved scope question. Use the workbook alongside the evidence manifest and action log to trace each status back to an item and a recorded next action.

Add a tool only when the manual process has a clear limit

If repeated cases outgrow a controlled spreadsheet, assess the firm’s current practice system first. Compare how candidate tools handle roles, private sharing, export, source references, reminders, exceptions and the ability to pause client-facing actions. A task board can show ownership; a document-request product may help collect files; neither independently decides accounting completeness or professional scope. Vendor plans and prices change, so check current official terms before choosing one. No vendor account, integration or client workflow was tested for this guide.

AI could later draft a summary from permitted minimal metadata after the firm defines its data permissions and review rules. It should not silently accept items, classify accounting treatment, send reminders or produce final advice. ICAEW’s guidance on confidentiality and output verification and its accounting-specific validation guidance reinforce the need to check AI output against trusted sources. A firm considering custom support can describe its administrative bottleneck through a project request without sending client records; any proposal would be scoped against its systems, permissions, review controls and deployment needs. External AI model or subscription charges are paid by the client separately.

What was checked: the starter’s fictional CSVs, workbook formulas and cached sample statuses were inspected. What remains untested: a real client record, secure setup at a firm, a sent follow-up, vendor account or integration, professional review, legal requirements in a particular jurisdiction, and any time-saving or search-performance outcome. Adapt the method under your firm’s policies before using real data.