← Back to Insights

Insight

Every Missing Form Has a Parent

Ariel Agor
•
Every Missing Form Has a Parent

Listen · Read by Ariel · click any word to jump

0:00 / —
· loading…

The extended deadline for 2025 individual returns falls this Thursday, October 15, 2026. CPA Practice Advisor ran a reminder on October 6 saying that "as many as 20 million Americans, roughly 15% to 20% of all filers" ask for extensions each year. Some of those extensions buy time to think. Most of them buy time to wait. Somewhere in a 12-person tax practice tonight, a senior preparer is writing the fourth polite email of the season to a client whose return is finished except for one piece of paper, and the client can't produce it because it hasn't been made yet.

I want to make one argument about that piece of paper, aimed at owners of 5 to 40 person CPA, EA and tax firms. Many of you are now looking at an AI agent to chase missing client documents (W-2s, 1099s, K-1s) so your staff stop sending reminder emails by hand. Good. Buy or build one. But most firms will point the agent at the wrong target. They will aim it at the client, have it send nicer emails more often, and call that automation. The client is usually not where the paper is stuck. Every missing form has a parent, an employer or a brokerage or a partnership or a trust that has to produce it first, and the agent that works is the one that knows who the parent is.

The reminder email was the wrong unit of work

Here is how document collection runs in most small firms. In January or February the firm sends an organizer, usually last year's list with blanks. Documents trickle into the portal. A staff member eyeballs what came in, compares it to last year's return, and sends a message listing what is still missing. A week later, maybe two, they send it again. In April the firm files extensions on everything still incomplete. Then the summer goes quiet and the same list of gaps wakes up in September.

Look at the reminder email as a piece of work. It carries no information the client didn't already have. It does nothing to the form's production. Its only job is to keep the gap on the client's mind, and it does that job at the price of a preparer's attention, which is the scarcest thing your firm owns between February and April and again between September and October 15.

The obvious AI move is to take the human out of the reminder. That saves the keystrokes. It also locks in the assumption buried in every reminder email, that the client is sitting on the document and just needs a push. For W-2s that is often right. The employer issued the form, it is in a drawer or an inbox, and a nudge with a portal link gets it. For a K-1 from a partnership on extension, it is wrong, and no amount of nudging changes it.

Every form has a parent

Sort the documents on your missing list by who has to act before the client can hand them over.

A W-2 has an employer as its parent. By the time you're chasing it, the parent has almost always finished. The form exists, the client has it or can download it, and the reminder works.

A 1099 has a payer as its parent: a bank, a brokerage, a platform, a client of a freelancer. Usually the parent has finished. Sometimes the parent issues a corrected form weeks later, which means the document you collected in February is no longer the right document, and nobody tells you.

A K-1 has a pass-through entity as its parent, and that parent has its own return to finish first. A guide from GTA Accounting Group published on March 25, 2026 puts it plainly: "Partnerships must file Form 1065, and S corporations must file Form 1120-S, before issuing K-1s to recipients." It lists the usual causes of delay, including tiered partnerships, entities with many owners, special allocations, and the extra Forms K-2 and K-3. None of those causes sit with your client. Your client is a relay. They are waiting for an envelope from a fund administrator or a family LLC's accountant, and your firm is waiting on them.

The K-1 is a supply chain problem

Once you see the parent, the chase changes shape. Chasing a K-1 means tracking a supply chain with three or four links: the entity's books, the entity's preparer, the entity's filing, the investor's inbox, and then your portal. Your client controls only one of those links, and usually the weakest.

Intuit's October 2026 checklist for tax professionals, published September 18 and written by Nadia Rodriguez, tells firms to confirm that "K-1 data from pass-through entities" is reconciled before the extended 1040 goes out, and to reach clients who "still owe information" before the 15th. Both are sensible. Both assume the information is somewhere the client can reach. For a large share of the files still open this week, it isn't.

A document agent that knows the parent does something a reminder never could. It asks the client a different question. "Have you received the K-1 from Harbor Street Partners?" becomes "Who prepares the return for Harbor Street Partners, and has the entity filed?" With the client's permission, the agent can then follow the parent's progress through the client, or draft a request for the client to send the entity's administrator. The question moves upstream. The wait gets a date attached to it, and dates can be planned around.

What changed on September 30

For years a small firm couldn't build any of this on its own data. Practice management systems kept client requests locked inside their own screens. You could configure their reminder cadence. You couldn't wire your own logic into the request object.

On September 30, 2026, Canopy announced an external API platform. According to CPA Practice Advisor's coverage that day, firms can now read, create and update core records from their own tools, and Canopy says it offers write access to client requests. Hanna Bjornn, Canopy's senior vice president of product, said: "We have built an all-in-one system, but that does not mean we are a closed system." The same article says Canopy is building an MCP server so AI assistants such as Claude can connect to Canopy directly. That part is future work and not a shipped feature, and Canopy limits full API access to its Premium plan.

The announcement matters for a reason bigger than one vendor. When the request object becomes writable from outside, the logic deciding who to chase, about what, and when can live in your firm instead of in the vendor's settings page. Your firm's knowledge of which clients hold interests in which partnerships, and which of those partnerships were late last year, finally has somewhere to act. That knowledge sits today in a preparer's memory, or in a spreadsheet named something like "K1 tracker FINAL v3". It can become the rules your agent follows.

Other vendors are moving the same way. Karbon announced tax workflows at its Karbon Next event on June 4, 2025, including integrated client organizers built with StanfordTax and automated extension management, and it described planned agents that would sit in task lists, fetch data, update statuses and talk to clients. Plenty of vendor blogs now describe the standard pattern: the agent watches open requests, sends scheduled reminders and escalates people who don't respond. That pattern is fine. It is also the pattern every firm will have by next spring, so it gives you no edge. The edge sits in what the agent knows about each document's parent.

How a document-chasing agent for a tax firm should work

What follows is a design, the one I would put in front of a 5 to 40 person practice today. Nothing here gives tax advice. The agent requests documents and tracks them, and it stops there.

Last year's return is the spec

Start from last year's return. Every W-2, 1099 and K-1 on the prior-year return is an expected document for this year, and each one has a parent you can name. Build a ledger with one row per expected document: client, form type, parent entity, how the client got it last year, when it arrived last year, and who at your firm owns the file.

That ledger is the most valuable artifact in the whole system, and it belongs to your firm. Leave it out of a vendor's black box. If you switch practice management platforms in 2028, the ledger comes with you. If you can write it into your platform through an API, as Canopy now allows, good. Keep the master copy somewhere you control.

Arrival dates from last year are the real prize. Suppose a client has held a stake in the same real estate fund for four years and its K-1 has never arrived before late August. Your agent shouldn't send that client a single February reminder about it. It should note the expected date, check in once in early summer, and save its energy for documents that are actually late against their own history. Lateness is relative to the parent's habits, and only a ledger can measure that.

Chase by parent, then by client

Group the open items by parent before you group them by client. When eleven of your clients hold K-1s from the same fund, you have one problem, and an agent that sends eleven separate reminders has misunderstood it. One question, put through one client who will cooperate (or through the fund's investor relations portal, if the client has given you access), tells you whether all eleven are coming next week or next month.

For W-2s and ordinary 1099s, chase the client directly, since the parent has already done its part. Here the agent's job is low-friction persistence: a short message, a direct upload link, a reply to "which one do you mean?" that names the employer and the tax year, and a stop as soon as the document lands. Most firms will see their first hours come back here, because this is where the hand-written reminders pile up.

For corrected 1099s, the agent's job reverses. It watches for a second version from a parent that already delivered once. Say a brokerage issues corrected forms each March. The ledger flags every client with an account there, and the agent asks each one, once, whether a corrected form arrived. That single question saves a lot of amended-return work.

The agent asks, it never advises

Draw the line in writing and build it into the agent's instructions. The agent may say which document is missing, who usually issues it, and how to upload it. It may not say whether the client needs to report something, whether a form applies to them, or what a number means. Every question that sounds like advice goes to a named person at the firm, with the client's message attached and the ledger row linked.

Clients will test the line. "Do I even need to send this one, I sold that stock at a loss?" is a tax question dressed as a logistics question. The agent should recognize the shape, answer that a preparer will reply, and create a task. Several vendor guides on agents for accounting firms say the same thing: anything resembling tax, financial or filing advice goes straight to a licensed professional. Make that rule the first one in your spec. A firm that lets its chaser drift into advice has given a liability to a system that can't hold one.

Escalation stays a human decision

The agent decides when to ask. A person decides when to stop asking and file an extension, call the client, or drop a problem client. Build a weekly digest grouped by parent, showing each open document, its age against last year's arrival, and the agent's last contact. Your managers should be able to read it in ten minutes and make the calls that need judgment.

The consent wall you will hit

Tax firms carry a constraint that most AI enthusiasm skips over, and you should design for it from the first day.

The Tax Adviser, the AICPA's journal, ran "Tax ethics and risk management: Common questions and answers, Part 1" on August 31, 2026, by Tara E. Adams and James J. Newhard. On Section 7216 it says that for Form 1040-series information, "a separate disclosure in the format specified in Rev. Proc. 2013, 14 must be signed by the taxpayer(s)." It says an "email, text, or phone call is generally inadequate" to release that kind of client information, and it recommends "portals and encrypted emails" for secure transfer. It also notes that outsourcing, whether direct or through a software vendor, raises Section 7216 release questions. Part 2, on the use of AI tools, is scheduled for the November issue.

The IRS Office of Professional Responsibility issued introductory guidelines on responsible AI use on June 24, according to an August 4 report on LetsDataScience that cites CNBC. That report says the guidance "does not directly address disclosure to clients," and that the AICPA is telling preparers to "err on the side of caution by disclosing their AI use to clients."

Put those together and you get three design rules. First, the agent should move as little return information as it can. A request that says "we still need your 2025 K-1 from Harbor Street Partners" contains less sensitive data than one that quotes last year's figures, and it works just as well. Second, documents should land in your secure portal, never in an email thread the agent is reading. Third, get the consents and the AI disclosure signed now, at the start of the next engagement cycle, as separate documents. Retrofitting consent onto clients in the middle of February is the worst way to learn this.

The consent wall is also a reason to own the architecture. If the logic, the ledger and the message templates sit in your firm, you can show exactly what information the agent touched and why. If they sit inside four vendors' default workflows, you are trusting four configuration screens you didn't write.

October is the cheapest month to start

The deadline Thursday will close out most of the year's extended 1040s. It will also leave behind the best dataset your firm makes all year: a complete record of which documents arrived late, from which parents, and how many touches each one took.

Intuit's October checklist suggests updating client organizers or portals for the next cycle and sending clients "a light-touch check-in" about the January deadlines for W-2s and 1099s. Treat that as a starting gun. The weeks after October 15 are the only quiet window in a tax firm's calendar with the past season's memory still fresh. The pain is still in your preparers' heads. In February it will be buried under new returns.

Here is a rough way to size the prize, offered purely as illustration. Say your firm has 600 individual returns, and on average each one needs four reminder messages across the season, each taking five minutes once you count looking up what's missing. That comes to 200 hours of skilled staff time spent typing variations of "just following up." Suppose the agent takes over the W-2 and ordinary 1099 chase completely and halves the touches on K-1s by grouping them by parent. You get most of those hours back, and they come back in the weeks when every hour costs the most. Change my numbers for yours. The shape of the result usually survives.

The hours matter less than the extensions. When the chase follows parents, you know in March which returns will be blocked by K-1s and which are blocked by a client who hasn't opened the portal. Those two situations need different conversations. The first can be planned around. The second needs a phone call from a person the client trusts. Firms that can tell them apart in March will file fewer reflexive extensions in April and walk into October with fewer files open.

Build the map, then buy the messenger

You can buy the messenger. Every practice management vendor will sell you an agent that sends reminders, and by next tax season most of them will be competent. The messenger was never the scarce part. What your firm alone holds is the map: which clients hang off which parents, which parents run late, which forms get corrected, which clients answer texts and which answer only to a partner's voice. That map comes from years of your own seasons, and right now it lives in people who will someday retire or leave.

Architecting this means writing the map down as data, connecting it to the request systems that now accept outside writes, drawing the no-advice line in the agent's instructions, and settling consent before the first message goes out. It is a few weeks of serious design work done in the quiet weeks after October 15. Skip it and you'll get a faster version of the old process, where a machine sends the same doomed reminder about a K-1 that the fund administrator hasn't finished.

Agor AI Advisory does this work with small firms: we build the ledger from your prior-year returns, design the chase logic by parent, wire it into the platform you already run, and write the consent and escalation rules so your preparers keep their judgment and lose the typing. The firms that do this in October get a different January. Schedule a strategic consultation with us today.

Sources

Who is actually holding the form up

This verifies the post's claim that a reminder email only works when the form's parent has already finished, by sorting each form type by who must act first. After 15 seconds the reader should see that W-2s and ordinary 1099s are client problems, while K-1s and corrected 1099s are parent problems.

  • A reminder email carries no information the client didn't already have, and it can't change when the form gets made.
  • The client is usually not where the paper is stuck. Every missing form has a parent that has to produce it first.
  • W-2s are a persistence problem. K-1s are a supply chain problem.
ParentHas the parent usually finished?What the agent should do
W-2A reminder works here. This is where hand-written follow-ups pile up and where most firms recover their first hours.EmployerAlmost always yes. The form exists and the client has it or can download it.Chase the client directly with a short message and an upload link, and stop when the document lands.
1099 (ordinary)A reminder usually works, but the payer may issue a corrected form weeks later without telling anyone.Payer: bank, brokerage, platform, or a freelancer's clientUsually yes.Chase the client directly, naming the payer and the tax year, and stop when the document lands.
1099 (corrected)The February document may no longer be the right one. One question per client avoids amended-return work later.Payer that already delivered once, such as a brokerage that issues corrections each MarchDelivered once, but a second version may still be coming.Flag every client with an account there and ask each one, once, whether a corrected form arrived.
K-1Nudging the client cannot speed this up. The client is a relay, and the useful output is a date to plan around.Pass-through entity (partnership or S corporation) that must file its own return firstOften no. The entity must file Form 1065 or 1120-S before issuing K-1s.Ask who prepares the entity's return and whether it has filed. Group open items by parent and ask once.

Source: The post's own sorting of W-2, 1099 and K-1 documents by parent, including the GTA Accounting Group guide (March 25, 2026) on partnerships filing Form 1065 and S corporations filing Form 1120-S before issuing K-1s. · verified · as of 2026-10-13

Want this kind of automation working for your business?

Agor AI designs and ships the systems these posts describe, scoped in weeks, not quarters.

Book a Free Strategy Call