Automations

Collect Tax Documents From Clients Without Chasing Them Through Email

A return needs eleven documents. The client sends four in one email, one as a photo taken at an angle, two more a fortnight later replying to the wrong thread, and then asks whether you got everything.

The short answer

The collection problem and the filing problem are the same problem, and email solves neither. A link sent to the client gives everything they upload one destination, and a workflow reads each document for the client, year and form type and files it — so the return's folder fills up as the client sends things rather than after somebody sorts an inbox. What is still outstanding becomes visible, which is the question that actually matters in February. Documents that arrive by email anyway are caught by the Email Attachment trigger, because some clients will always reply with an attachment.

Steps this uses

Email AttachmentFile UploadedOn a ScheduleRead Details from FileCheck File DetailsSave a CopyRenameMoveSend a Message

Before and after

What actually changes

As they arrive

  • IMG_2210.jpg
  • scan0001.pdf
  • document.pdf
  • Fwd: tax stuff.pdf

After the workflow

  • Okafor, D/2025/2025-w2-northwind.pdf
  • Okafor, D/2025/2025-1099-int-first-national.pdf
  • Okafor, D/2025/2025-1098-mortgage-interest.pdf
  • Okafor, D/2025/2025-k1-harlan-partners.pdf

Four documents sent over three weeks, in three formats, filed under one client and year as each one arrived.

Setting it up

Described once, then it runs

This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.

When a client sends a tax document by email or upload, save a copy, read the client, the tax year and the form type off it, rename it by year and form, and file it under that client and year. Message me the client and the form name as each one lands.

01

One destination per client

A link the client can use more than once, over five weeks, without an account. Every upload lands in the same place, which is what stops the return being assembled from nine email threads.

02

Let the document identify itself

The Read Details from File step reads the form type, the tax year and the taxpayer off the page. A W-2 photographed on a kitchen table is still a W-2, and OCR is what makes that true.

03

Catch the email route as well

Some clients reply with attachments regardless of what you sent them. The Email Attachment trigger and the Save a Copy step handle those identically, so both routes end in the same folder.

04

Report what is missing, not what arrived

The file request carries a checklist of what this return needs, and tracks each item per client as it arrives, so the outstanding list is produced rather than rebuilt. A list of what has arrived is reassuring and useless; a list of what has not is the one you work from.

Why email is the wrong container

An inbox is ordered by when things arrived and shared with every other conversation you are having. A return needs documents grouped by client and checked against a list, which is the one view email cannot give you. Every firm that runs collection through email ends up maintaining a parallel spreadsheet of who has sent what — and that spreadsheet is the actual product, built by hand, thrown away in May.

The photograph problem is real and mostly solvable

Clients photograph documents on kitchen tables, at angles, in bad light. OCR handles a flat, well-lit photograph of a printed form well, and a dark angled one badly. This is worth saying to clients directly, because a one-line instruction about laying the page flat does more for collection quality than anything downstream of it.

What it does not do

It collects, files and shows you the gaps. It does not prepare the return, populate a tax package, or know that this client has a new rental property and therefore needs a form they have never sent before. The list of what a client owes you comes from you; the system tracks it against what has actually arrived.

FAQ

Common questions

How do tax preparers collect client documents each season?

The workable pattern is one upload link per client, used repeatedly over several weeks, with documents filed under that client and year as they arrive and a list of what is still outstanding. Collecting through email means rebuilding that list by hand in a spreadsheet, which is the work most firms do not realise they are doing.

What if clients just email their documents anyway?

Some will, and that route has to work too. Attachments are captured from email, given a home, read and filed into the same client folder as the uploaded ones. A collection process that only works when clients follow instructions is not a process.

Can it read a photo of a W-2 taken on a phone?

Usually, with OCR. Quality depends on the photograph — a flat, well-lit page reads reliably and a dark, angled one often does not. Telling clients to lay the page flat in good light improves collection more than anything you can do afterwards.

Will it tell me which clients are still missing documents?

Yes, against the list of what each return needs. That list comes from you — the system cannot know a client acquired a rental property this year. What it does is track each item on the request's checklist as documents arrive, per client, so the gap is visible at any moment rather than counted.

One link, not nine emails.

Filed as it arrives, with what is missing still visible.

Build this workflow

5 GB free · No credit card required