Why “missing” is harder than it sounds
Missing is not a property of a folder. It is the result of a comparison. Before a firm can call a W-9 or bank statement missing, it must know that the document is expected for this client, for this entity or account, and for this period.
That is why an accounting document request tracker can contain a long history of requests and still leave the team uncertain. A request is an action someone took. A file is an object that exists. Neither one, alone, defines the full set of records the client should have.
Separate the expectation from the request
Suppose a client is expected to provide a W-9 for every new contractor. The expectation belongs to the client's operating model. “Email Alex for the W-9” is one task created because the expectation was not met. When the file arrives, the task can close—but the rule about future contractors remains.
Keeping those concepts separate lets a firm distinguish a document that exists, a document that was requested, a document that is still missing, and a document that will be required again in a later period.
EXPECTED → OBSERVED → ATTENTION
A reliable model for finding document gaps
Model what should exist first, compare it with what is present, and produce follow-up only for a meaningful difference.
Expected
Define the required document, client, entity, period, due date, and recurrence.
Observed
Record the file or verified status that actually exists, including the period and validity dates.
Attention
Surface a precise gap when a required expectation has no current matching evidence.
Where common tracking approaches break down
Each tool can play a useful role. The gap appears when the firm asks one of them to represent expectations it was not designed to hold.
Email threads
Useful for: Preserve the request and the conversation around it.
Breakdown: A sent message proves that someone asked. It does not prove that the file arrived, is current, or will be needed again.
Spreadsheets and checklists
Useful for: Make a portfolio-wide list possible with familiar tools.
Breakdown: They depend on consistent manual updates, period labels, and someone who knows how each status should be interpreted.
Task and practice-management systems
Useful for: Assign work, repeat workflows, and show who owns a follow-up.
Breakdown: A completed request task can disappear even though the underlying document expectation remains true for the next period.
Shared folders
Useful for: Show the records that have actually been collected.
Breakdown: They show observed files, not the complete set that should exist. An empty folder does not explain what is missing.
Employee memory
Useful for: Handles client-specific nuance quickly.
Breakdown: The process fails during handoffs, absences, busy seasons, and growth because the expectation was never made durable.
What the model looks like in practice
W-9
Expected: A current W-9 for a new contractor
Observed: No matching file for the contractor
Attention: Request the W-9 before the next payment run
Prior-year tax return
Expected: The signed return and supporting schedules
Observed: Return is present; one schedule is absent
Attention: Follow up only for the missing schedule
Payroll reports
Expected: Reports for each applicable quarter
Observed: Q1 and Q2 are present; Q3 is not
Attention: Surface Q3 without reopening completed quarters
Bank statements
Expected: One statement per active account and month
Observed: The operating account's June statement is missing
Attention: Ask for the specific account and period
Insurance certificate
Expected: A certificate valid through the current policy year
Observed: A certificate exists but has expired
Attention: Request the renewed certificate
Annual compliance document
Expected: The current year's filed document
Observed: Last year's document is still in the folder
Attention: Create this year's follow-up while preserving history
Recurring expectations should roll forward
Annual folders and files are easy to confuse with permanent requirements. Receiving a 2025 insurance certificate satisfies the 2025 expectation; it does not satisfy 2026. The expectation should create or reveal the next period without someone copying last year's task list by hand.
Keep the recurrence rule, each period's expected item, and the observed file separate. This preserves history while making the current gap unambiguous. The same pattern works for annual tax folders, monthly bank statements, quarterly payroll reports, and expiring certificates.
Need a starting list? Use the accounting client document checklist to decide what applies before tracking the gaps. See how to structure recurring client document requests so the system continues knowing what should exist in the next period.
A PRACTICAL START
Build the checklist around evidence, not reminders
Create one expectation per client, document type, entity, and period.
Mark whether it is required, optional, one-time, or recurring.
Link the observed file or verified status to the expectation it satisfies.
Keep requested, received, reviewed, and missing as distinct states.
Assign an owner and next action only when the comparison produces a gap.
Review exceptions on a schedule and record client-specific exemptions.
Where Brivaro fits
Brivaro is one way to implement this model. A firm defines the files and folders it expects for a client, Brivaro compares those expectations with what is actually present, and missing required items become attention items. Email, tax, payroll, and practice-management tools can continue doing the jobs they do well.
Document gaps are one part of a larger client-management problem: knowing what should be true for every client, what is true now, and where the difference calls for action. Read the broader guide to accounting client management.
QUESTIONS, ANSWERED
Missing client document FAQ
How should an accounting firm track missing client documents?
Start with a client-specific list of documents that should exist, then compare it with the records actually received. Treat the unmatched required items as attention items, with an owner and next action.
What should an accounting client document checklist include?
Include the client, expected document, required or optional status, period, recurrence, due date, observed document or status, next-action owner, and any client-specific exception.
Why is a shared folder not enough to track missing documents?
A folder shows what is present, but an empty folder does not explain what should be there, whether an item is required, which period it covers, or who should follow up.
How should recurring client documents be tracked?
Keep the recurring expectation separate from any one file or request. When a new period begins, create the next period's expected item and compare it with what has been received rather than rebuilding the checklist manually.