Tax document collection: how to automate the chase for missing client documents

Where the time goes in document collection

Getting documents out of clients tops the list of workflow problems in firm surveys. In Financial Cents' 2024 survey, 65.2% of respondents named getting information and documents from clients as their biggest challenge. In the 2025 Accounting Industry Report from Woodard and Mango, 69% of firms reported delays in document collection, and 76% needed between two and five touchpoints to get what they asked for. Both surveys were run by software vendors and lean toward small firms, so read them as a direction rather than a precise measurement. Most partners need no survey to know how March feels.

The documents rarely arrive in one piece. A client may upload W-2s in February and send a phone photo of a K-1 in April, with file names like scan0003.pdf. Most come through the portal, and the rest arrive by email or on paper. Each one has to be opened and filed to the right client and tax year before anyone can check it against what the return needs.

The check itself is the slow part. Someone opens last year's return and lists every payer that sent a form. They compare that list with what came in, write to the client about the gaps and set the job to Waiting on Client in the practice management tool. When the next batch arrives, the whole check starts again. None of this needs a tax judgment, which makes it a good first job for an agent.

K-1s often decide the calendar. A significant K-1 that has not arrived by early April usually means a decision about an extension, and the chase starts again before the October deadline. IRS Publication 6292 puts the number of Forms 4868 at 20,081,406 for fiscal year 2024, and many extended returns carry a second round of requests.

What gets a client to answer

The wording of the request matters as much as the reminder schedule. One preparer wrote on the r/taxpros forum in April 2026 that clients tend to ignore automated messages and open the emails that come directly from their preparer. Another wrote that, unless a client has only a handful of documents, the chase always needs some person-to-person contact.

Both points shape the design. A request that names the missing 1099-B from the brokerage and the K-1 from a named partnership gives the client one clear task. A reminder saying that documents are outstanding gives them a reason to wait. The agent drafts the specific request, and a preparer reads it and sends it, with any edits, from the portal or mailbox the client already uses. The client hears from a person they know, about the two items actually missing.

Last year's return, read with last year's source documents, is the best checklist most firms already have. Together they show which payers sent forms. Organizer answers, when a client returns them, add what changed this year, such as a new employer or a sold rental property. From those the agent builds an expected list for each return, and anything on it that has not arrived goes into the request with its payer.

What the agent does and what your preparers keep

A workable split: the agent does anything a careful first-season staff member could do from last year's file, and a preparer keeps anything that needs judgment about the return. In practice the line falls roughly here.

Duplicates and corrected forms deserve their own rule. Brokerages sometimes issue a CORRECTED 1099-B after the first one, and clients upload both. The agent flags the pair so the preparer uses the right one, and it never deletes either. When the agent cannot tell which client or year a file belongs to, as with a phone photo of a K-1 from a family partnership, the file waits for a person.

Keep the tools you already pay for

Much of this ground is already covered, and the agent should fit around it. SurePrep 1040SCAN, GruntWorx, Drake SmartExtract and Lacerte's document import move numbers from source documents into the return. Thomson Reuters Ready to Review and Canopy Smart Prep go further and draft 1040s from the source documents for staff review. TaxDome can tag and rename uploads, and Financial Cents can send automatic client requests and reminders. If those features cover your season, use them first.

The gap often sits between those tools, because extraction starts only once the documents are in. Check whether your portal or organizer tool already sends specific missing-item requests before you commission a custom workflow. Where it does not, comparing what arrived with last year's file across the portal and the shared mailbox, then writing a request that names each missing item, still falls to a person. A custom agent earns its place there, and it hands the complete file to whatever extraction tool you already run.

Client data rules and the controls to insist on

Documents a client sends for a return are tax return information under Section 7216 of the Internal Revenue Code. The regulations let staff inside the firm use that information to prepare the return without the client's consent. The IRS has not said whether sending return information to an AI tool counts as a disclosure, and the Section 7216 guide in this series covers that open question in detail.

A cautious design keeps the agent inside your firm's environment and uses client data only to prepare the return, never to train a model. We bring tax documents in only after counsel confirms the Section 7216 exception that applies or the consent that is required. The agent also belongs in the written information security plan the FTC Safeguards Rule requires, which IRS Publication 4557 describes for tax professionals. A first project can start with bookkeeping and close documents, which usually arrive under a bookkeeping engagement, and add tax documents once counsel has reviewed the design.

The IRS Office of Professional Responsibility gave practitioners a useful rule in June 2026: treat the written text that AI generates as a draft, and use only secure, enterprise-approved AI for client data. An agent that drafts and a preparer who approves fits that rule. These controls make the arrangement hold up in a busy week:

• A confidence threshold on client and year matching, below which the file waits for a person.
• A target of zero documents filed to the wrong client, checked on a weekly sample.
• No message reaches a client without a preparer's approval during the first season.
• Access limited to the client folders and job statuses the agent needs for its work.
• A log of each file the agent read and each match it made, with the person who approved the request.

A worked example

This is an illustrative example with assumed numbers, not a client result. Take a 35-person firm that prepares 1,500 individual returns a season. Assume 900 of them are incomplete after the client's first upload, and that each takes 2.5 rounds of follow-up at 12 minutes a round. That is 30 minutes a return, or 450 staff hours across the season.

With the agent, assume 720 of the 900 are routine. A preparer reviews and sends each drafted request in 3 minutes, so 7.5 minutes a return and 90 hours. The other 180, such as new clients and returns with several K-1s, stay manual at 30 minutes each, another 90 hours. The season drops from 450 hours to 180. Over a 13-week season that is about 69 incomplete returns and 21 staff hours given back each week.

The routine share decides the result, and only a counted week of your own uploads tells you yours. A firm with many trusts and K-1 heavy returns will see a smaller share. The saving is also seasonal, so do not multiply it by twelve. The second measure is calendar time: the days a return waits on the client and the number of returns extended only because a document was missing.

Where to start

Count one busy week before you buy anything: the uploads that came in and the follow-up messages your team sent. Those two numbers tell you whether the chase is worth automating. If extension season has just ended, last season's portal and mailbox history will give you the count.

Our five-day sprint builds a working prototype for $2,500 on sample tax documents with made-up figures, so no client return information leaves the firm before counsel has approved the design. It comes with a full refund if we do not find 10 staff hours a week. If the numbers hold, a build is from $7,500 per workflow, half to start and half when the acceptance criteria pass, and running it costs $1,200 a month.

Common questions