What automated client onboarding looks like at a CPA firm

What the manual version actually costs

Most small firms still run onboarding by hand. Layer3labs' 2026 guide to accounting client onboarding automation cites the AICPA's 2025 Practice Management Survey: roughly 65% of firms with fewer than 20 staff still rely on email-based onboarding with no automation at all. Layer3labs' guide also estimates a typical manual intake runs 12 to 18 separate steps across 4 to 6 different systems, with every handoff a place where the file can stall for days.

The hours behind those steps add up across a year. Layer3labs estimates firms with 2 to 20 staff lose 2 to 4 hours of staff time per new client to tasks a system could otherwise handle. Using its own example, Layer3labs notes a firm bringing on 150 new clients a year at 4.2 hours each spends roughly 630 staff hours annually just on getting people in the door, before any billable work starts. Layer3labs also reports that small firms which automate onboarding, document collection, and billing commonly see 20 to 35% fewer admin hours per engagement, though the range depends on how much of the process actually gets automated. Most of that time sits inside the document chasing that eats every busy season, not the judgment calls only a CPA can make.

There is a client-facing cost too. TaxDome, which sells onboarding and practice management software itself, reports survey figures showing 71% of accounting clients value efficient onboarding, and one in five say they would pay up to 50% more for faster service. A vendor citing numbers that favor its own product is not neutral evidence, but the underlying operational point holds up: a client waiting on a checklist notices the delay, and starts to wonder if their return will get the same treatment.

How the workflow actually runs

Picture a continuous loop instead of a passive portal. A client signs the engagement letter in Ignition. That signature is the trigger: a system reads the completed event, creates the client record and the first job in Karbon or Jetpack Workflow, and sends a document request built from the return type rather than a generic list. Nobody at the firm has to remember to start any of those steps by hand.

Then the workflow waits, but not passively. If a required document has not arrived in three days, it sends a reminder automatically. If the file still has not arrived after the second reminder, it escalates the task to a staff member instead of firing off a third automated email the client will ignore anyway. Deciding when a machine should stop nudging and hand the problem to a person is the part most client portals skip. The same pattern shows up in automated certificate of insurance requests: reminders work for a while, and then a direct phone call works better.

Once the requested documents are in, a KYC or AML check runs against them, the same kind of identity and risk check firm compliance already requires before work can start. If the check clears, the first job opens on its own in the practice management tool, and nobody has to remember to kick it off. If it flags anything unusual, the workflow stops and waits for a person to review it, every time. A compliance flag is the kind of decision a system should never make by itself, because a wrong autonomous call there costs far more than a late document ever would.

Where this sits next to Karbon, Canopy, Ignition and Jetpack Workflow

None of these established tools are the wrong choice for a firm. Karbon and Jetpack Workflow template the internal tasks, checklists, and deadlines inside a firm. Canopy and Ignition handle the client side: e-signature collection and billing.

What most of these platforms do not do on their own is watch the space between them: notice that a signed engagement letter in Ignition has not produced an active job in Karbon yet, or that a client's portal upload does not match the specific file type the checklist asked for. That watching-and-deciding layer sits directly on top of a firm's existing software stack. It does not replace the underlying tools. How workflow automation differs from a system that can decide and escalate on its own is worth reading before adding either kind of tool to your operations.

We build and run these cross-system loops the way we run our own operations: as scheduled jobs that check their own results and keep going without anyone watching. Right now that is 230+ scheduled jobs across 60+ live integrations, running continuously.

What reporting looks like once onboarding is automated

When the intake sequence runs automatically, the weekly status report becomes one table with a row per client, built from timestamps. When the engagement letter is signed, the job is created, the reminders go out, and the documents arrive, each step writes down that it happened. Instead of a partner asking staff where new clients stand, the status table shows which step each client is on, how many days have passed since the engagement letter was signed, which documents are still outstanding, and whose turn it is to act.

What the status table counts matters. FlowRunner, a workflow software vendor writing for finance leaders, argues that, for finance, client onboarding is graded by four things: countersignature of the engagement letter, a client record that matches the legal entity, a correct first invoice, and a reconciled first payment. A report that stops tracking when documents are received stops right before the part finance cares about. Adding the last three items as columns turns a basic status list into something a firm can act on, such as spotting a client who has sent every document but still has no invoice raised.

Each reader at the firm gets a different cut of that same table. Partners get an exceptions view sitting on top of it: clients stuck on one step beyond a time limit the firm sets, and clients waiting on a partner's decision. Staff see a clean daily list of the follow-ups they own. The client gets a short plain message showing how many documents have arrived and which items are still missing, instead of writing in to ask. Jetpack Workflow's own guide describes manual onboarding as a loop of back-and-forth emails, missing signatures, and incomplete forms. A clear status message that confirms what has arrived removes a large share of those emails.

The limits of automated reporting are practical. A report is only as reliable as the events behind it, so every handoff has to write down that it happened. If the signed engagement letter never produced a job in the practice management tool, the weekly report should show a signed letter with no open job after a set number of days, which is the exact gap between tools described earlier in this post. The report records timestamps and flags stalled files. It does not decide whether a chronically late client is worth keeping.

What still needs a person

Some parts of client onboarding should always stay manual past a certain point. Engagement letter terms that fall outside the standard template, or a KYC compliance flag on a new client, need a partner's judgment, not another automated retry. A system that guesses on either one creates far more cleanup work than it saves.

The honest version of any onboarding automation project starts with mapping the firm's process first: separating which steps are genuinely repetitive and rule-based from which ones need someone experienced to make a judgment call. How to evaluate an AI automation vendor covers the questions worth asking before handing any part of this over, client onboarding included.

Two things worth checking yourself

Pull your last ten new-client files and count the emails required to get from a signed engagement letter to the first return actually starting work. Some firms will check their folders and find three. Others will find something closer to Layer3labs' estimate of 12 to 18 separate steps. Either way, that internal number, not a general industry estimate, is the one that tells you where automating intake would actually help your team this season. For the clients you are onboarding right now, check a second thing: can someone on staff name each client's current step and the oldest item still missing without searching an email inbox? If not, a weekly status report built on those files would be guessing.