Where document collection stalls

Every return waits on one more document, and your staff spend their mornings asking for it. The client says it was sent, the portal says it was not, and the email thread says something else again.

Add it up across a client list and the chase becomes a job of its own. Someone keeps the spreadsheet of who owes what, someone writes the reminders, and someone opens an attachment to find last year's statement. None of that is accounting. All of it is tracking.

Tracking is work software does well. Collection tends to stall in the same four places, and each one has a fix you can build.

  • The request is a paragraph of prose, so the client cannot tell which items matter.
  • Documents arrive by email, portal, text message and drop-off, with no single place to look.
  • Nobody can see who is still missing what without opening a spreadsheet.
  • Reminders depend on whoever remembers, so some clients are chased twice and others never.

This post shows how to automate the request, the reminder and the filing while your people keep the review. Done well, the payoff is faster turnaround, fewer staff hours spent on reminders and more returns through the same preparers. A partner stays in control of every consequential step.

What document collection automation covers

It covers four jobs: request, match, remind and flag. The system sends each client the checklist for their engagement, matches what comes back to that list, reminds clients about open items and flags anything wrong or unreadable. Your staff keep every judgment call.

From the client's side, it is one message with a short list and one button. They upload each file against its checklist item, answer not applicable where it fits, and see what is still open. They never have to learn a new system, and nobody sends them a fresh email for each missing item.

Who does what in document collection
StepThe systemYour staff
RequestBuilds the checklist from the engagement and sends it with an upload linkApproves the checklist templates once, then reviews exceptions
ReminderSends a short note listing only open items, on a set schedule, and stops on any replyAnswers client questions and makes the phone call after the last reminder
Match and fileMatches each upload to a checklist item, names it by rule and files itConfirms any match the system is unsure about
Quality checkFlags blurry, wrong-year, partial and password-protected filesDecides whether to ask again or work around the gap
StatusShows which clients are complete and how long each has waitedDecides when to hold a return, call a client or plan an extension

That split is the safeguard. Nothing the system does changes a return, deletes a file or contacts a client outside the templates a partner approved. Every send and every file move is logged on the client record.

It does not decide whether a document is right for the return, whether a return can go ahead with an item missing, or when to file an extension. Those calls stay with a preparer or a partner. The system's job is to put the facts in front of them early, with the client's history attached.

Start with one checklist per engagement type

The checklist is the whole system. If it is vague, every reminder will be vague. Start with your highest-volume engagement, say individual returns, and write the list of documents a preparer needs before opening the file. A starting list follows.

  • Last year's return and organizer, so every question can start from what you already know.
  • W-2s and 1099s from every employer, bank, brokerage and payer.
  • Mortgage interest and property tax statements.
  • Brokerage and retirement account statements, with every page.
  • K-1s from partnerships, S corporations and trusts, which may arrive late.
  • Business income and expense reports for self-employed clients.
  • Receipts for childcare, education and charitable gifts.

Mark each item as required, if applicable, or due by a date. Then ask the client a yes, no or not applicable question about every item that depends on their situation. An item with no answer stays open forever, while an item answered not applicable closes itself.

Build next year's list from this year's return. A client with rental income gets the rental questions again, and a client who sold a house gets a different set. Keep the prior-year organizer attached to the client record, because it is the best source for what to ask.

Set up the client data before you write a single reminder. For each client the system needs the engagement type, the assigned preparer, a primary contact, a preferred channel and last year's checklist. That data usually already sits in your practice management software. Anything missing is a one-time cleanup, and it is worth finishing before the first message goes out.

Send the checklist with the signed engagement letter, so the request goes out the day the client commits. If those letters still go out by hand, the engagement letter workflow is a natural first step.

After individual returns, repeat the exercise for business returns, payroll clients and monthly bookkeeping. A bookkeeping client owes you bank and card statements every month, so the request becomes a standing reminder on a monthly rhythm. The monthly bookkeeping workflow covers that case.

What a chase costs today

Put a number on it before you build anything. Say your firm has 150 individual clients, each needs three reminders on average, and each reminder takes five minutes to write, send and log. That is 150 times 3 times 5, or 2,250 minutes.

Divide by 60 and you get 37.5 hours. Say an hour of staff time costs the firm $40. The reminders alone cost $1,500 a season, and that is before anyone opens a spreadsheet to find out who is still missing a 1099.

The larger cost is the calendar. A return waiting on one statement holds a preparer's slot and pushes other work toward the deadline. Some of those returns end up on extension because of a single missing item. Automating the reminders gives those 37.5 hours back to review work and gets returns to the preparer sooner.

Your numbers will differ. Count the reminders your staff send in one week, multiply by the minutes each takes, and you have your own figure. Set it against a build that typically runs $1,000 to $5,000, flat rate or $50 an hour.

Record one more number before you change anything: the days from request sent to checklist complete, for last season's returns. That baseline is how you will know, at the end of the next season, whether the system earned its keep.

Set reminder rules clients will tolerate

A reminder that repeats the whole checklist gets ignored. A reminder that names the two items still missing gets answered. Each message should list only what is open, carry one upload link and come from a named person at your firm. A schedule to start from follows, with every day count open to change.

  1. Day zero: the request goes out with the checklist, the upload link and a plain deadline.
  2. Day three: the first reminder lists only the items still open.
  3. Day seven: a second reminder goes to the client and, if you hold one, a second contact.
  4. Day ten: the system creates a task for a staff member to call, with the open list on screen.
  5. Day fourteen: a partner sees every client still open and decides whether to hold, call or plan an extension.

Send only during business hours, and skip weekends unless a client prefers otherwise. Any reply stops the sequence and lands with the right staff member, because a reply usually holds a question. Give staff a switch to pause one client, such as the client who is traveling or already on the phone with a preparer.

Plan for households. A married couple is one return and two inboxes, so store a second contact on the client record and decide who hears what. Both can get the first request, and the person who usually uploads can get the nudges. Ask clients which they prefer when the first request goes out.

Keep the tone plain and a little warm. Say what you need, why it blocks the return and what happens next, in three sentences or fewer. Leave deadline warnings out of the first two reminders. The phone call on day ten is where urgency belongs.

Match and file what comes back

When a file arrives, the system checks it against the checklist, names it the same way every time and files it in the right client folder. A naming rule such as client, year and document type is worth more than it sounds. Anyone in the firm can then find any file.

Matching works best when clients upload against a checklist item in your portal. For files that arrive by email, the system suggests a match and a staff member confirms it. Reading the numbers off a document is a separate, optional step. Add it later if your preparers want it.

What gets flagged to a person

  • A scan that is blurry, cut off or rotated.
  • A document from the wrong tax year.
  • A statement with pages missing.
  • A password-protected file that arrives without the password.
  • A file the system cannot match to any client or checklist item.

Each flag carries the client's name, the checklist item and the reason, so a staff member can act without opening five tabs. A re-request template, approved once, can go out on its own for simple cases like a cut-off scan. Anything stranger goes to a person.

Decide the folder rule once. One folder per client per year, with subfolders by document type, keeps the filing predictable. When a file lands in the wrong place, the log shows where it came from and a staff member moves it.

Finally, give staff one status view: every client, every open item, days waiting. It replaces the spreadsheet, and it is what a partner reads on Monday morning to see which returns are at risk of missing their deadline.

Decide who approves what

Give the system the narrowest access that does the job. It can read the client list and engagement type, send messages from approved templates, and write to the document folder. It cannot change a return, touch billing or delete a file.

Run the first two weeks in approval mode. A staff member skims a short list each morning before any reminder goes out, and a partner signs off on the templates and the schedule. When the list stops surprising anyone, loosen the approvals one step at a time.

Plan for the day something breaks. If the portal connection drops, the system should stop sending and alert a named staff member. The checklist stays untouched, so the firm can work by hand until the fix. Ask for that behavior in writing before launch.

Keep the log readable. Each send, each reply and each file move is recorded with a date, so a partner can open any client and see exactly what happened. When a client says they never got the request, the answer is one click away.

What to do this week

You can start without building anything. Spend this week gathering the facts that decide whether a build is worth it and what it should do first.

  1. Pick one engagement type, such as individual returns, and write its checklist.
  2. Count the reminders your staff send in one week, and the minutes each one takes.
  3. List the reasons a file comes back unusable, and write the plain request that fixes each one.
  4. Decide who makes the call after the last reminder, and who decides on an extension.
  5. Book the free workflow walkthrough, and bring the checklist and the counts.

A realistic first month runs like this. Week one writes the checklist and the templates. Week two connects the portal and runs in approval mode on a handful of clients. Weeks three and four widen the group while you read the numbers below, so you know what to tighten before the next busy season.

Three numbers to watch after launch

  • Days from request sent to checklist complete, compared with last season.
  • Reminders still sent by hand each week.
  • Returns held up by a single missing item.

A first build for one engagement type typically runs $1,000 to $5,000 and takes a few days to a month, with a written quote first. See how the same flow works across a firm on the document collection workflow page, and the rest of the practice on the accounting firms page.