Accounting firm automation: what small firms should automate first

Automation here means a rule that runs the same way every time: send this request when a job starts, remind the client on a calendar, file the upload, ping the preparer. It is the work AICPA describes as copying data between systems, sending the same emails, and linking one action in one tool to the next action in another. (How to build automations in your small firm)

It is not:

• An AI that prepares, files or signs a return. A CPA still does that.
• A new practice system you have not finished setting up. Fix the process on paper first.
• A Zap that posts to a client without anyone reading it.

If you want the process behind document requests, start with how to get clients to send tax documents on time. This page is about the order you should build in.

Score each repeating task on three questions. Write the answers down. Do not argue them from memory.

Then apply three filters:

• Does work downstream wait on it? Document collection almost always wins because preparation cannot start.
• Is there a clear stop rule?"Stop reminding when the checklist is complete" is a good rule. "Use judgement" is not.
• Can a person still catch it? If the output goes to a client, a person at the firm reads it first.

AICPA's own starting advice is the same shape: pick a well documented, routine task, test it with sample data, then expand. Client onboarding is their worked example: a form comes in, records get created, a welcome email goes out. (How to build automations in your small firm)

This is an illustrative week, not a client story. Picture a six person tax and bookkeeping firm in February: two CPAs, two preparers, one admin, one owner who still reviews. They keep a simple log for five days. Minutes are what they counted, not a promise of hours you will get back.

The first three share a pattern: they happen a lot, the path is known, and a bad outcome is a wrong folder or a reminder that names an item you already have. You can see those. A bad 1040 you cannot.

Work these in order unless your log clearly says otherwise.

1. The first document request

When a job starts, send one request with the itemised list, the date and one upload link. In TaxDome that is a stage automation: the job enters a stage, the organizer goes out, and if automove is on the job moves when the client finishes. The firm owner and admins can set that up by default. Other staff need the Manage pipelines access right. (Automations explained) The list itself still has to be built from last year's return. That part is a person, at least the first time. See the collection system and the TaxDome chasing workflow.

2. Reminders that stop

Timed nudges that name only what is still missing, and that stop the moment the client is complete. If your tool can only remind on the whole request, have a person rewrite the outstanding list after the first two sends. Do not stack a new reminder on top of a client question that is sitting unanswered.

3. Filing what arrived

One folder per client, one year, one document type. If the file name is readable, drop it in. If the year is wrong or the scan is unreadable, park it for admin. This is a good second automation because nobody outside the firm sees the mistake, and it makes the missing list honest.

4. New client setup

Create the record in practice software, billing and document storage, make the folder, send the engagement letter, send the portal invite. AICPA treats this as the beginner automation for a reason: it is the same steps every time. (How to build automations in your small firm)

5. Internal handoffs

When documents are complete, create the preparer task. When the preparer marks ready, create the reviewer task. Do not auto assign the hardest returns. A manager still picks who gets the K-1 with three states.

6. Invoice reminders

A short sequence after the due date, then a person for anyone who disputes the fee. Keep the copy dull. Do not let a tool offer a write off.

• Anything on the return. Figures, positions, extensions as a tax decision, signing, filing. A tool can extract a number into a checklist. A CPA decides whether it is right.
• Judgement replies."That does not apply to me." "I already sent it." "We sold the rental." A person reads those.
• Phone calls. After two ignored reminders, call. Do not add a fifth email.
• A messy process. If two people file the same document in two places, automation will file it in both, faster. Write the rule down first.
• Client data in a consumer chatbot. If you are evaluating an AI product, use the buyer checklist before anyone pastes a W-2 into it.

One task, fully working, beats five half built rules. If the first task is document chasing and you would rather not staff it in March, that is the work a tax season operator is set up to run, with your team approving what goes out. If the work is many client ledgers rather than 1040s, use how a small firm runs books for many client companies and what a CAS firm can automate per client.

Download the priority worksheet. It is a spreadsheet with common firm tasks already listed and columns for how often, minutes, whether it repeats, whether a client sees it, what happens if it is wrong, and whether it is first, soon or later. Add your own rows from the week you logged.

Fill it from the sent folder, the pipeline and the time sheet, not from a meeting. The tasks at the top of a real week are usually not the ones people volunteer in a planning session.