Tax document collection that chases clients so your staff do not have to
We build a document collection workflow that generates each client's request list from the job type and what they sent last year, sends a secure upload link through your portal, matches uploads to outstanding items, chases on a schedule that firms up as the deadline approaches and marks the job ready for preparation when everything is in. A typical build costs $1,000 to $2,500 per workflow and takes three to four weeks.
The problem
Why tax season stalls on missing documents
Every return and year-end begins with the same request and the same wait. Staff email a list, the client replies with half of it, the rest arrives by text, post and a forwarded bank email, and someone keeps track in their head of what is still missing.
At peak season this is the bottleneck for the whole firm. Prepared returns sit waiting on one missing form, and the reminders that would have cleared it never went out because everyone was busy preparing the returns that were complete.
What we build
What our tax document collection software includes
Request lists per client
Lists built from the job type and last year's documents, so a landlord, a sole proprietor and a company each get the right items.
Secure upload link
One link to your portal or document store per client, never documents by plain email.
Upload matching
Each file matched to its checklist item; unreadable or unexpected files flagged for staff.
Escalating reminders
A schedule that becomes more direct as the deadline nears, by email and text if the client agreed.
Ready-to-prepare signal
The job moves to ready in your practice system when every item is in or waived.
Outstanding list for managers
A weekly list of who still owes what, ordered by deadline.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Job opens
A new return or year-end job generates the client's request list.
-
02
Automated
Request sent
The client gets a checklist and secure upload link.
-
03
Automated
Uploads matched
Files are matched to items and reminders go out for what is missing.
-
04
Staff review
Staff query
Staff check flagged files and call clients who are stuck.
-
05
Accountant or partner decides
Preparation decisions
Whether information is sufficient for the return is decided by the accountant.
How it behaves
How automated document chasing behaves
What the client sees
- A short list of exactly what the firm needs this year
- A secure upload link that works on a phone
- Reminders that stop as soon as they upload
What staff see
- Jobs moving to ready without manual checking
- Flagged files that need a person
- A weekly outstanding list by deadline
What the automation does
- Builds lists from job type and last year
- Matches uploads to items
- Escalates reminders and never judges sufficiency
Edge cases and fallbacks
- Client sends documents by email anyway
- Staff drop them into the portal and the item clears.
- Client says an item does not apply this year
- Staff waive it and the reminder stops.
- Unreadable photo of a form
- Flagged for staff to ask for a clearer copy.
- Portal or messaging outage
- Reminders pause and resume, and the manager gets an alert.
Architecture
Tax document collection for an accounting firm at a glance.
- Input
- Logic and services
- Output
- AI step
- People
- Data
How it flows
- 1 A new job and last year's documents give the workflow the client's personalised request list.
- 2 The client receives the list with a secure link to the portal and reminders on a set schedule.
- 3 Uploads are matched to each item; anything unclear is flagged for staff.
- 4 When every item is in or waived, the job is marked ready to prepare.
Project planner
How the project runs, phase by phase.
Tax document collection & automated chasing project plan
Typical time to launch: about 3 weeks, then support
-
01
Discovery
2 to 3 days
Job types, current request lists, portal, deadlines and how reminders are sent today.
-
02
Design
2 to 3 days
Item lists per job type, reminder schedule, matching rules and status changes.
-
03
Build
About 1 week
List generation, portal requests, matching, reminders and the outstanding list.
-
04
Shadow run
About 1 week
A pilot group of clients receives requests while staff check every match.
-
05
Launch
1 to 2 days
Roll out to all jobs of that type.
-
06
Support
Ongoing
New job types and reminder wording each season.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Job types, item lists and reminder schedule.
$200 – $450
-
Build
List generation, matching, reminders and status changes.
$550 – $1,250
-
Integrations
Portal, practice system and messaging.
$150 – $400
-
Testing and shadow run
Pilot clients and match checking.
$75 – $250
-
Launch and training
Roll-out and staff walkthrough.
$25 – $150
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Portal, messaging and n8n costs are billed to you directly.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Client portal: Your portal vendor's own plan.
- Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing).
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
What pushes cost up
- Systems without an API, or with integration access that must be requested from the vendor
- Writing data back into your core system rather than only reading from it
- Several locations, brands or very different processes to support
- Custom apps, dashboards or a voice line on top of the workflows
What keeps cost down
- One location and one clear process to start with
- Cloud software with a documented API
- Using tools you already pay for instead of adding new ones
- Approved wording and sample data ready at the start
Privacy and consent
Rules we design for, with the sources.
US: tax return information
Section 7216 rules restrict how preparers use and disclose tax return information. Documents stay inside the firm's systems and contracted processors.
Source: www.law.cornell.eduUS: Safeguards Rule controls
The Safeguards Rule requires encryption of customer information in transit and at rest, multi-factor authentication and oversight of service providers, which shapes how uploads are handled.
Source: www.law.cornell.eduUS: reminder texts
Texts to mobile numbers are covered by the TCPA rules; we only text clients who gave their number for that purpose and honour STOP replies.
Source: www.law.cornell.eduUK: Making Tax Digital for Income Tax
From 6 April 2026 sole traders and landlords with qualifying income over £50,000 are in scope, falling to £30,000 from April 2027 and £20,000 from April 2028, so record requests become more frequent.
Source: www.gov.ukFree tools
Try these first, free.
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
- 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
- 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
- 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.
How scope stays under control
- Product backlog
- Every feature, fix and question in one prioritised list you can see at any time.
- Acceptance criteria
- Plain-language conditions for "done" on each item, agreed before work starts.
- Change requests
- New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
- User acceptance testing (UAT)
- Before launch your team tests the real workflow against the acceptance criteria and signs off.
Tools we use
Project manager / Scrum master
Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.
Business analyst
Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.
Automation engineer
Builds the n8n workflows, integrations, AI steps and error handling.
Backend developer
Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.
Frontend / mobile developer
Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.
QA engineer
Tests every workflow against the acceptance criteria, including edge cases and failure paths.
DevOps engineer
Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.
Who does what at each phase
- Free call
- Project manager, business analyst
- Understand the problem, check it is worth automating and outline a rough range.
- Discovery
- Business analyst, automation engineer
- Map the current process, systems and data, and agree success measures.
- Design
- Business analyst, automation engineer, backend developer
- Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
- Sprints
- Automation engineer, developers, QA
- Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
- UAT and launch
- QA, DevOps, project manager
- Your team tests and signs off, we switch on, monitor closely and train the team.
- Support
- Automation engineer, DevOps
- Stabilisation window, then optional monthly care with monitoring and changes.
A point of contact
One person who can answer questions and approve decisions, with about an hour a week during the project.
Access
Admin or API access to the systems involved, created as separate accounts with the least access needed.
Sample data
Real but non-sensitive records (or de-identified ones) so we can design and test against reality.
Approved wording
Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.
Vendor agreements
Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.
Time for testing
A few hours from the people who will use the system, for the demos and user acceptance testing.
Working system
Workflows, integrations and any apps running in your accounts, under your keys.
Documentation
Workflow specification, data-flow map, run book and exported workflow files.
Training
A walkthrough for the team and a short recorded video for new starters.
Handover
All access, credentials and code handed over; you can keep us or take it in-house.
Stabilisation window
Fixes for anything that does not meet the agreed acceptance criteria after launch.
Support options after launch
No plan
You run it yourselves after the stabilisation window and contact us when you need a change.
Monthly care
Monitoring, error alerts, small changes and updates each month, with an agreed response time.
Priority care
Faster response times for business-critical workflows and a monthly review call.
How a project moves through our team
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Tax document collection & automated chasing questions, answered.
Software that asks clients for the documents a return or year-end needs, gives them a secure place to upload, tracks what is still missing and reminds them. Most portals do part of this; we connect the portal to your practice system and add the personalised lists and chasing.
No. We use TaxDome, Canopy, SmartVault or the portal you have, and automate the requests and follow-ups around it.
It can recognise what a file is and match it to a checklist item, and flag files that look incomplete. It does not decide whether the information is right for the return; your staff do.
You choose. A common pattern is a reminder every week, more often in the final fortnight, then a personal call. Every reminder stops the moment the item arrives.
Yes. Quarterly updates mean more frequent record requests, and the same lists and reminders can run on a quarterly cycle.
Share of jobs ready before the internal deadline, average days waiting on clients and how many reminders it takes per job.
Free 20-minute call
Want this for your accountant?
Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.
More for accountants
All servicesCRM for accounting firms: pipeline to signed engagement
Every enquiry from your website, referrals, calls and partners in one CRM pipeline, with proposals, follow-ups and a hand-off into your practice system the moment an engagement is signed.
From $1,000 · About 4 weeks Details
Client onboarding, engagement letters & due diligence
Turn a signed proposal into a complete client file: engagement letter for e-signature, identity and ownership evidence, prior-accountant details and a risk summary ready for the partner.
From $1,000 · About 4 to 5 weeks Details
Bookkeeping automation & bank reconciliation triage
Unreconciled bank lines grouped and given a suggested category with a reason, missing receipts turned into one client query, and month-end exceptions summarised for review.
From $1,000 · About 4 to 5 weeks Details