At a glance
- An expected-document list is derived line by line from each client's prior-year return, not a blank checklist: a client who filed a 1099-B last year is expected to have one again this year.
- The rule table below assigns every expected document a detection method, a reminder tier, and an escalation trigger — some gaps belong to the client, and some belong to a different party a client reminder can't move.
- We recommend capping automated reminders at two tiers before a preparer calls: automation handles the routine gap, and a call is reserved for the one automation can't resolve.
- A packet is complete when flagged conflicts are resolved and every third-party-controlled item is accounted for, not just when every row shows a checkmark.
- Track days-to-complete-packet and escalation rate by document type and reason code, not one aggregate "hours saved" figure.
How do you know which tax documents a client is missing?
The reliable way is to derive the list from the client's own prior-year return or tax organizer (the pre-season questionnaire capturing what changed since last year), not a generic checklist. A prior-year W-2 from a named employer means a current-year W-2 is expected from that employer; a prior-year Schedule D with broker activity means a current-year 1099-B is expected.
Where the firm's tax platform exposes prior-year data through a documented interface, the match can run automatically. CCH Axcess publishes a developer portal for its Open Integration Platform, reachable via a firm's own login[1]; whether it exposes the prior-year fields a given match needs is something to confirm with the vendor. SmartVault's product page describes a packaged version of the same idea: SmartRequest AI builds its request list from "whichever prior-year source has the most to work with, an already-connected return, last year's answers, or a prior year 1040"[2].
The expected-document list and reminder-tier playbook
The table below covers the current-year document each prior-year signal implies, how to detect it, which reminder tier applies, and what triggers escalation.
| Prior-year signal | Expected current-year document | Detection method | Starting tier / track | Escalation trigger |
|---|---|---|---|---|
| Prior-year W-2 wages from a named employer | Current-year W-2 from the same employer | Match employer name and EIN to last year's W-2 issuers | Tier 1 | No response by the Tier 2 deadline moves it to Tier 3 |
| Prior-year 1099-INT or 1099-DIV from a bank or brokerage | Current-year 1099-INT or 1099-DIV from the same payer | Match payer name to last year's 1099 issuers | Tier 1 | No response by the Tier 2 deadline moves it to Tier 3 |
| Prior-year Schedule D or broker-statement activity | Current-year 1099-B from the same broker | Match broker name to last year's 1099-B issuer | Tier 1 | No response by the Tier 2 deadline moves it to Tier 3 |
| Current-year 1099-B received; client or broker reports a correction is pending | Corrected Form 1099-B replacing the original | Match broker and account; a form marked CORRECTED replaces the original | Third-party track — waiting on the broker | Past the firm's cutoff, the preparer follows up with the broker, not the client |
| Prior-year Schedule K-1 from a partnership or S corporation | Current-year Schedule K-1 from the same entity | Match issuing-entity name to last year's K-1s | Third-party track — waiting on the entity | Past the firm's cutoff, the preparer contacts the entity directly, not the client |
| Prior-year Schedule C income or 1099-NEC/1099-K | Current-year 1099-NEC or 1099-K from the same payer | Match payer name to last year's issuer | Tier 1 | No response by the Tier 2 deadline moves it to Tier 3 |
| Prior-year dependent-care credit claim | Current-year provider statement | No third-party filer to match; flag as client-supplied only | Tier 1, on a shortened interval | No response by the first deadline goes to a preparer call |
Exact dates shift by tax year, which is why the table uses tiers rather than dates: for 2026-tax-year returns, the IRS generally requires employers to furnish W-2s by "February 1, 2027"[3]; for 2025-tax-year returns, it requires payers to "file and furnish a copy of Form 1099-NEC ... by February 2, 2026", and sets a later date of "February 17, 2026" for Form 1099-B and several other information returns[4].
Treat K-1s and corrected 1099-Bs as controlled by the issuing entity's own schedule, not the client's: neither follows the recipient-furnishing dates above, which is why the table gives both a separate, third-party track.
The three numbered tiers are a recommended design; adapt intervals to your calendar. Third-party-track rows skip these tiers: no client reminder moves a document someone else controls.
- Tier 1: automated, first touch
A client-portal notification (the secure site clients use to upload documents) or email names the item as soon as the match flags a gap.
- Tier 2: automated, second channel
A second reminder follows on a different channel (text or portal banner), on the interval you set.
- Tier 3: a person calls
A preparer calls the client directly; automated reminders pause, so the call isn't competing with a bot.
A second table answers a different question: what does "complete" mean? Treat it as exit criteria before a preparer sees it, not "everything was uploaded."
| Checklist item | What "done" looks like | Who confirms it |
|---|---|---|
| Every expected document from the rule table is received and classified | No item shows "missing" or "unclassified" | System, spot-checked by the preparer |
| Every document's tax year matches the return being prepared | No item is flagged "prior-year document" | System |
| Every conflicting or corrected document is resolved | The corrected version replaces the original, not sits beside it | Preparer |
| Every third-party-controlled item (a K-1, a corrected 1099-B) is received or waived | A waived item shows a stated reason and approver | Preparer or reviewer |
| The reminder and escalation log is attached to the case | Every tier and call is timestamped against the case | System, reviewed by the preparer |
How many reminders should a client get before a preparer calls?
We recommend two automated tiers before a person calls: a first reminder when the gap is flagged, a second on a different channel days later, then a call if neither moves the client.
- Escalate earlier when the firm's internal cutoff is close, regardless of reminders already sent.
- Escalate earlier for a client with a history of ignoring every reminder channel.
- Escalate earlier for a high-value or complex return, where a late gap costs more.
How should automation handle a late or amended K-1?
A corrected 1099 or K-1 — resent because the original had an error — needs different handling than an unfiled document, since the client can't fix it alone. The IRS's own instructions to partners are direct: "If you believe the partnership has made an error on your Schedule K-1, notify the partnership and ask for a corrected Schedule K-1"[5]; the remedy runs through the issuing entity, not the client.
For some corrections — for example, a security reclassified as covered after a transfer statement arrives — the 2026 Instructions for Form 1099-B give the broker 30 days to "file a corrected Form 1099-B"[6], with the same 30-day window after certain basis-affecting issuer statements. Those corrections run on the broker's own timeline, triggered by paperwork it receives, not by anything the client does.
- Flag a late K-1 or a corrected 1099-B as "waiting on entity," not "client missing," in the packet-completeness checklist above.
- The escalation owner becomes the preparer contacting the partnership, S corporation, or broker directly, and the return stays open rather than proceeding on an estimate.
Can AI tell a prior-year form from a current-year form?
A step that classifies a W-2, 1099, or K-1 by form type can also read the tax year printed on it — for example, "2025 Form 1099-DIV" — and compare it against the return's own tax year. A mismatch is a checkable signal, not a guess.
A client re-uploading last year's saved PDF, or a portal surfacing an old file by mistake, looks identical to a real upload unless something checks the year. Treat a mismatch as a hard stop for a person to confirm, not a low-priority warning: a stale document silently satisfying a checklist item is exactly the failure this list exists to prevent.
Where to start: a first scoped workflow
Start with one return type, not a firm-wide rollout. Individual-return clients without K-1s or brokerage accounts are the easiest population: every row stays on standard client tiers, with none on the third-party track.
- Pick one population and export its data
Choose one return type (for example, 1040 clients without K-1s or brokerage accounts) and export last year's line items.
- Build the expected-document list
Map each client's prior-year line items to the relevant rows of the rule table above.
- Wire two reminder tiers and a named Tier 3 owner
Set the Tier 1 and Tier 2 channels and intervals, and name the Tier 3 caller and internal cutoff.
- Run one season and score it before expanding
Log each gap's resolution against the packet-completeness checklist, then extend to K-1 clients.
This workflow is one of several tax-season workflows covered on our accounting-firms industry page.
Our document review with human approval page covers classification, extraction, and approval once a document arrives. If prior-year data lives in an older system with no API, our legacy finance workflow automation page covers working through whatever interface it offers.
The Tier 3 handoff and the packet sign-off both keep a specific person accountable — the governance question our human-in-the-loop AI governance article covers generally: automation does the exhaustive checking, and a person owns the judgment call.
To measure whether document chasing improved, track:
- Days-to-complete-packet: time from first request to passing every completeness-checklist row, by return type.
- Reminder count per completed packet, by tier: a rising Tier 2 share, or a rising share reaching Tier 3, is worth investigating.
- Escalation rate: the share of cases reaching a preparer (a Tier 3 client call or third-party follow-up), by reason (non-response versus third-party-controlled).
- Rework rate: packets reopened over a wrong tax year or a later-superseded correction.
When this playbook doesn't fit
- Your tax platform already builds and tracks an expected-document list from prior-year data; a second rule table adds a second source of truth.
- Document volume per engagement is low enough that a preparer already reviews the full prior-year file by hand.
- The client is new, with no prior-year return to draw signals from; build the first-year list from the engagement letter or an intake interview instead.
- Whether a missing document changes filing strategy is a professional-judgment call that stays with the preparer regardless.
Frequently asked questions
How do you know which tax documents a client is missing?
Derive the expected-document list from the client's own prior-year return or organizer, not a generic checklist. A prior-year W-2, 1099, or K-1 from a named employer, payer, or entity means the same current-year document is expected, so a missing item is a named, specific gap.
How many reminders should a client get before a preparer calls?
We recommend two automated reminder tiers, on different channels, before a preparer calls directly. Escalate sooner for a client with a history of ignoring every channel, a high-value or complex return, or when the firm's internal cutoff date is close, whatever the reminder count.
How should automation handle a late or amended K-1?
Flag it "waiting on entity," not "client missing," since the IRS's own instructions direct a partner who spots an error to ask the issuing partnership for a corrected Schedule K-1 — the client can't produce that alone. The escalation owner becomes the preparer contacting the entity; the return stays open.
Can AI tell a prior-year form from a current-year form?
Yes, by reading the tax year printed on the form itself, such as "2025 Form 1099-DIV," and comparing it against the return's own tax year. A mismatch is a checkable signal worth a hard stop: a stale document silently satisfying a checklist item is exactly the failure an expected-document list exists to prevent.
What should a preparer see when a packet is marked complete?
Every expected document received and correctly dated, every conflicting or corrected document resolved rather than left beside the original, every third-party-controlled item received or explicitly waived with a stated reason, and the full reminder and escalation log attached to the case.
How do you measure whether document chasing improved?
Track days-to-complete-packet and reminder count per completed packet, both by return type, alongside an escalation rate by reason and a rework rate for packets reopened over a wrong-year or superseded document. One aggregate "hours saved" figure hides which of these is driving the result.
Related reading
- Document review with human approval covers classification, extraction, and approval once a document arrives.
- Legacy finance workflow automation covers pulling prior-year data from an older system with no API.
- Human-in-the-loop AI governance covers the governance pattern behind the Tier 3 handoff and packet sign-off.
- Our accounting-firms industry page covers this workflow alongside other CPA-firm tax, CAS, and notice-handling workflows.
- Handling missing data in document automation covers the general abstain/escalate logic these detection methods build on.
Sources
- [1] — Developer Portal home page, sign-in prompt (accessed 2026-09-30)
- [2] — SmartRequest AI product page, "How it works" (accessed 2026-09-30)
- [3] — General Instructions for Forms W-2 and W-3, "Furnishing Copies B, C, and 2 to Employees" (accessed 2026-09-30)
- [4] — 2025 General Instructions for Certain Information Returns, Part C (When To File) and Reminders (due dates for recipient statements) (accessed 2026-09-30)
- [5] — Partner's Instructions for Schedule K-1 (Form 1065), General Instructions, "Errors" (accessed 2026-09-30)
- [6] — 2026 Instructions for Form 1099-B, Transfer Statement and Issuer Returns corrected-form provisions (accessed 2026-09-30)
More in Professional firm operations
AI Proposal Automation for A&E Firms: Speeding Up SF330 and RFP Responses Without Losing Quality Control
AI proposal automation for A&E firms: a workflow table showing what an agent drafts for SF330 and RFP responses and what your licensed staff review.
Engineering FirmsWhy Clients Reject Your Invoices: Reducing Billing Disputes at Consulting and A&E Firms
Why clients reject your invoices, and how an AI review catches fee-cap overages, wrong phase codes and missing backup before billing. Includes a cause table.
Engineering FirmsWIP Accounting for A&E Firms: Catching Overbilling, Underbilling and Subconsultant Reconciliation Gaps
WIP accounting for A&E firms: what a WIP report shows, how to spot over- and underbilling, and a weekly exception table that includes subconsultant invoices.
Engineering Firms