How Tax Preparers Collect Client Docs

Every tax season, the same ritual plays out across thousands of accounting offices: a client emails a blurry photo of their W-2. Another attaches a PDF that bounces back -- too large for the mail server. A third sends their 1099 to an address you stopped using two years ago. Then the follow-up calls begin. The problem is not your clients. It is the channel.

What documents do tax preparers typically collect?

Tax preparers typically collect income statements (W-2s, 1099s, Schedule K-1s), prior-year returns, receipts for deductible expenses, mortgage interest statements (Form 1098), and identity documents. The exact set depends on the client -- a solo freelancer brings a 1099-NEC; a rental property owner adds depreciation schedules and lease agreements.

• W-2s and 1099s (NEC, INT, DIV, R, S, B)
• Prior-year federal and state returns
• Business income and expense records
• Form 1098 (mortgage interest statements)
• Receipts for charitable contributions, medical expenses, and education costs
• Identity documents and Social Security numbers for new clients
• Business owners: profit and loss statements, payroll records, depreciation schedules

The volume adds up fast for a busy practice. A sole practitioner managing 80 clients through tax season could be handling hundreds of individual documents -- each arriving through a different channel, in a different format, at a different time. Keeping track of what arrived, what is still missing, and which version is current becomes a job in itself.

Why does email fall short at tax time?

Email was built for messages, not for managing sensitive documents across dozens of clients simultaneously. Files arrive out of order, get buried in long threads, and your inbox becomes the only record of what you received -- with no reliable way to confirm the client sent the right version, or even the right year.

Practically, most corporate mail servers cap attachments at 10 to 25 MB, which means clients with multiple large files send several separate messages -- or compress files in ways that introduce errors. There is no delivery confirmation for an attachment the way there is for a certified letter. And if a client forwards your email to a spouse or business partner, you have no visibility into where that W-2 went.

There is also the version control problem. When a client sends a revised 1099 three days after the first one, you now have two files with similar names and no clear record of which supersedes which. Multiply that across 50 clients and the margin for error grows significantly.

The audit trail problem surfaces at year-end: you may struggle to reconstruct exactly who sent what, and when. That gap matters if a client disputes a filing, or if your practice is ever reviewed for data handling practices.

Are tax preparers required to secure client data?

Yes. Under the FTC Safeguards Rule, tax preparers qualify as financial institutions and must maintain a written information security plan -- known as a WISP -- covering how client data is collected, stored, and transmitted. IRS Publication 4557 outlines what that plan should address for tax professionals specifically.

In practice, a WISP for a tax practice documents how you collect client files, who on your staff can access them, how they are stored and transmitted, and how long they are retained. The Safeguards Rule sets out specific administrative, technical, and physical safeguards. The AICPA provides resources on data security for tax practices that go deeper into implementation guidance.

This post describes the regulatory landscape in plain language and is not legal or compliance advice. Consult your professional association or a qualified attorney for guidance specific to your practice and state.

What does a secure document collection workflow look like?

A secure workflow has three components: a controlled intake channel where clients upload directly rather than sending email attachments, per-client access controls so no client can see another client's folder, and a time-stamped audit log that records every upload, download, and preview.

In practice: each client receives a link to their own private folder on a portal that carries your firm's branding -- your logo and firm name, without any mention of a third-party tool. They log in, upload their documents, and you receive a notification. No file lands in your email inbox unannounced.

For a small practice, this changes the daily rhythm of tax season. Instead of opening 20 emails searching for a missing 1099, you check the portal: the document either arrived or it did not. If it did not, you send a reminder -- not another message in an already-crowded inbox.

The audit log answers the question clients -- and regulators -- occasionally ask: did you receive my documents? You can show exactly when each file was uploaded, who downloaded it, and whether it was previewed. For a practice that needs to demonstrate due diligence in data handling, that log is not a nice-to-have. It is the record.

What to look for in a portal for tax document collection

Prioritize: per-client folder isolation, direct upload by clients (not just downloads), email notifications when documents arrive, an exportable audit log, and branding that puts your firm's name on the portal your clients see -- not a third-party app's.

• Per-client access control: each client has their own login and folder; they cannot see other clients' files
• Client-initiated uploads: clients can push documents to you, not just receive deliverables
• Upload and download notifications: know when something arrives without checking manually
• Exportable audit trail: a log of who accessed what and when, in a format you can export for compliance purposes
• Your branding: your firm's logo and name on the portal, not a generic file-sharing brand
• Pricing by active client accounts, not seats: you should not pay extra because a client has multiple staff members accessing their folder

One point worth singling out: the pricing model. Most per-seat tools charge based on how many staff members a firm has. A tool priced by active client accounts works differently -- you pay based on how many clients you serve, not how many people in your office use the system. For a 3-person practice managing 60 clients, that distinction typically means a lower monthly cost.

How ProjectSend Cloud fits the tax prep workflow

ProjectSend Cloud gives each client their own login and file folder, under your firm's branding. Clients upload directly; you receive a notification. Every action -- upload, download, preview -- is logged with a timestamp. The Business plan includes audit log export to CSV. If you missed our launch post, it covers the thinking behind what we built and why.

ProjectSend Cloud is built on ProjectSend, the open source project (GPLv2) with 4.8M+ Docker downloads and 4,000+ active instances around the world. The same code runs in the hosted version and in self-hosted installs -- so your data is never locked in a proprietary format. Visit projectsend.org to read about the open source project and the team behind it.

The Free plan is a personal account at no cost -- 2 GB, a private link for every file, no credit card, no time limit -- enough to hand files over by link, but without client accounts. The Pro plan at $19/month gives you a portal of your own with 25 active client accounts and 100 GB of storage, which is what this workflow needs. See how it works for a full walkthrough of the client upload workflow.

Ready to move tax document collection off email? Start free on ProjectSend Cloud -- no credit card, no time limit -- or go straight to Pro for client accounts. Have questions? Our FAQ covers the most common ones.