Trim CAS Client Onboarding in 2026 [Benchmarks Inside]

The first thirty days of a Client Advisory Services engagement decide whether the relationship is profitable or painful. A new CAS client needs a signed engagement letter, a kickoff call, access to QuickBooks or Xero, bank-feed connections, payroll credentials, a chart-of-accounts cleanup, a recurring close calendar, and a document-request cadence — and most firms manage that gauntlet through a Karbon work item on one screen and a Liscio request thread on another, with the two never talking to each other. The result is a stack of half-finished onboardings where nobody can say, on any given Tuesday, which client is blocked on what.

This guide is about closing that gap: how to automate CAS client onboarding so that the moment an engagement letter is signed, Karbon spins up the onboarding work, Liscio sends the right document requests to the client, and the two systems stay in sync without a staff accountant copy-pasting status between them. The reason to fix this in the off-season is structural. Tax-prep capacity peaks at 85-95% utilization in March-April, according to Thomson Reuters 2025 Tax Season Pulse. When your team is already at the ceiling during busy season, an onboarding that leaks four hours of coordination per client is four hours you do not have. Build the automation now, in the trough, and it runs itself when the wave hits.

Below is the full recipe — the onboarding stages, where Karbon and Liscio each own a step, the integration triggers that move work between them, a worked example with real figures, benchmarks for how long the whole thing should take, and an honest read on when to skip automation entirely.

Key Takeaways

• CAS onboarding fails when Karbon (internal work) and Liscio (client-facing requests) run as two disconnected systems; the fix is event-driven sync, not a longer checklist.

• A signed engagement letter should be the single trigger that fans out the entire onboarding: Karbon work item, Liscio request set, and a recurring close calendar, all created at once.

• A well-instrumented CAS onboarding should reach "books live" in 8-12 business days, versus the 3-5 weeks most firms tolerate by default.

• The off-season is the time to build this, because busy-season capacity leaves no slack to absorb manual coordination overhead.

• Automate the routing and status sync; keep the judgment calls — scoping, pricing, the kickoff relationship — human.

TL;DR

Automating CAS client onboarding means letting a signed engagement letter automatically create the Karbon onboarding work, dispatch the matching Liscio document requests to the client, and keep both systems' statuses in sync so no step is silently stuck. Done well, it compresses onboarding from weeks to roughly 8-12 business days and frees your team from the copy-paste coordination tax — which matters most precisely when busy season has eaten all your capacity.

What "automated CAS onboarding" actually means

CAS client onboarding automation is the practice of using triggers and integrations so that a single client event — most often a signed engagement letter — kicks off every downstream onboarding task across your internal work manager (Karbon) and your client-collaboration portal (Liscio) without manual hand-offs.

That definition matters because most "onboarding automation" in accounting firms is really just a saved checklist template. A template still requires a human to remember to launch it, assign it, and chase every line item. True automation removes the remembering and the chasing: the engagement letter status changes, and the work appears, assigned, with client requests already sent.

The core insight is that Karbon and Liscio solve different halves of the same problem. Karbon orchestrates what your team does internally — the close calendar, the review steps, the capacity view. Liscio owns the client-facing surface — secure messaging, document requests, e-signatures, and the audit trail of who-asked-for-what. Onboarding is exactly the workflow that spans both surfaces, which is why it breaks down when they are not wired together.

Most firms still rely on at least one disconnected app in their onboarding stack, according to AICPA 2025 PCPS CPA Firm Top Issues Survey. Technology adoption is rising, but adoption is not integration — a firm can own Karbon, Liscio, QuickBooks Online, and a payroll platform and still move data between them by hand. The automation work is in the seams, not the apps.

Who this is for

This playbook is built for a specific firm profile, and naming it sharpens the decision.

If you onboard 20 or more CAS clients a year and already run Karbon, Liscio, or both, the integration pays back fast because the coordination tax compounds across every engagement. Firms in the $1.5M-$40M revenue band are the sweet spot: large enough that manual coordination genuinely hurts, small enough that they have not built a custom internal platform.

Red flags: Skip this build if you onboard fewer than 8 CAS clients a year, if your stack is still paper and spreadsheets with no API-addressable tools, or if your firm is under $500K in revenue where the engineering effort outweighs the time saved. At that scale, a disciplined manual checklist beats an integration you will not maintain.

The CAS onboarding stages, mapped to owners

Before automating anything, you need a clean map of the stages and which system owns each. The mistake firms make is automating the steps in the order they happen to think of them, rather than in dependency order. Onboarding is a dependency graph: bank-feed connection cannot start before portal access, which cannot start before the engagement letter signs.

The numeric-majority table above is doing real work: it tells you that the human-paced stages (engagement letter, ledger access, COA cleanup) dominate the timeline, while the system-to-system hand-offs should be instant. If a hand-off that should be instant is taking a day, that is your automation gap. The whole point of wiring Karbon and Liscio together is to drive every "Instant (automated)" row to actually be instant. Most automation initiatives stumble precisely on integration rather than the tooling itself, according to McKinsey 2024 automation research, which is why the seams between Karbon and Liscio — not the apps — are where the real onboarding gains live.

The integration recipe: trigger, action, sync

Here is the core of the automation, expressed as event-driven rules rather than a checklist. Each rule is a trigger in one system that fires an action in another.

This is where the integration layer earns its place. Karbon and Liscio both expose the events and actions above, but they do not natively chain across each other end to end — the "all requests fulfilled in Liscio advances the Karbon stage" rule is exactly the seam that breaks. This is the orchestration that US Tech Automations sits across: it listens for the Liscio request.completed event, checks that every document in the onboarding set is in, and only then moves the matching Karbon work item from "gather" to "cleanup" and notifies the assigned accountant. No staff member watches a thread to notice the last bank statement arrived.

The second place orchestration matters is the fan-out at the start. When the engagement letter signs, US Tech Automations creates the Karbon onboarding work, assigns it by client industry and team capacity, and triggers the correct Liscio document-request template — a SaaS client's request set differs from a construction client's — so the client receives a tailored, not generic, ask. One event, three coordinated actions, zero copy-paste. If you want to see how the upstream signing and intake piece connects, our walkthrough on how to automate accounting client onboarding with HubSpot, Karbon, and PandaDoc covers the pre-engagement-letter half of the funnel.

Worked example: a 12-client onboarding quarter

Consider a $6M CAS-focused firm onboarding 12 new clients in Q3, each at an average $2,400/month recurring fee. Before automation, each onboarding consumed about 5.5 hours of staff coordination — chasing documents, copying status between Karbon and Liscio, and re-sending requests — which is 66 hours across the quarter, or roughly $5,940 in fully-loaded staff cost at a $90/hour rate. After wiring the systems so the Liscio request.completed webhook advances the Karbon stage automatically, coordination dropped to about 1.5 hours per client (the kickoff call and judgment work that should stay human), saving 48 hours and pulling average onboarding time from 24 business days down to 11. The compounding part: those 12 clients represent $345,600 in annualized recurring revenue, and getting them to "books live" two weeks faster means the firm starts billing the monthly fee two weeks sooner on each — roughly $14,400 of revenue pulled forward, on top of the labor saved.

How long should CAS onboarding take?

This is the benchmark question firms most want answered, so here is a direct target table.

A firm running a disciplined integration between Karbon and Liscio should hit books live in 8-12 business days for a standard small-business CAS client. The clients that take longer are almost always blocked on the human-paced stages — slow credential handoff or a messy legacy ledger — not on the automation. Demand for these advisory engagements is climbing fast: employment of accountants and auditors is projected to grow about 6% through 2033, according to the U.S. Bureau of Labor Statistics, which means the onboarding volume you are systematizing now only increases. Roughly 30% of finance-team time is lost to coordination and rework, according to Deloitte 2024 finance-function benchmarking, and onboarding is where that loss concentrates because every step depends on the one before it.

For context on the broader close cadence these clients enter once live, a typical month-end close runs about 5-6 business days according to the Journal of Accountancy 2025 close-cycle benchmark — so an onboarding that drags past three weeks is consuming time you could have spent on two full close cycles.

A decision checklist before you build

Run through this before committing engineering time. Each "no" is a reason to simplify or wait.

• Do you onboard 20+ CAS clients a year? (Below that, manual wins.)

• Do you already run Karbon and Liscio, or one of them with budget for the other?

• Is your document-request set standardized enough to template by client type?

• Can someone own the integration's exceptions — the 1 in 10 onboarding that breaks?

• Have you mapped your stages in dependency order, not just listed them?

• Is there a clear "books live" definition everyone agrees on?

If you answered yes to most of these, the build is justified. If you stalled on standardization, fix that first — automating a chaotic request set just produces chaos faster. Our guide on the 8 steps to onboard a CAS client is a good place to lock the stages down before you wire anything together.

Common mistakes that quietly kill onboarding automation

The most expensive mistake is the second-to-last: when status lives in both Karbon and Liscio and the two disagree, staff stop trusting either and fall back to asking each other in Slack — which is the manual coordination you were trying to kill. The entire value of the integration is collapsing status to one trustworthy source. If you preserve the worked-example webhook discipline — Liscio fires request.completed, the Karbon stage advances, and that is the only path that moves the work — the two systems cannot drift, because only one of them is allowed to advance the state.

When NOT to use US Tech Automations

Automation is not always the right answer, and pretending otherwise erodes trust. If you onboard fewer than eight CAS clients a year, a clean shared checklist in Karbon alone will outperform any integration you would not bother to maintain — the per-client coordination is real, but it is too infrequent to justify the build and upkeep. If your firm needs only a client portal and document collection without internal work orchestration, Liscio on its own already covers that and you do not need an orchestration layer above it; our TaxDome vs. Liscio client-portal comparison walks through that lighter-weight choice. And if your onboarding genuinely varies so much per client that no two are alike — bespoke holding-company structures, multi-entity consolidations — the exceptions will outnumber the rules, and a human-led process beats an automation that breaks every other engagement.

Glossary

Frequently asked questions

How long should CAS onboarding take?

A standard small-business CAS onboarding should reach "books live" in 8-12 business days once Karbon and Liscio are integrated. Manual, checklist-free processes commonly run 3-5 weeks, and the difference is almost entirely coordination overhead — the chasing and copy-pasting between systems that automation removes. The human-paced stages (credential handoff, ledger cleanup) set the floor; everything else should be instant.

Do Karbon and Liscio integrate natively?

They expose the events and actions you need, but they do not chain end-to-end across each other out of the box. Karbon orchestrates internal work and Liscio owns the client surface, so the "a completed Liscio request advances a Karbon stage" logic requires an orchestration layer that listens to one system's events and acts in the other. That seam is exactly where US Tech Automations advances the Karbon stage when Liscio reports a request set is fully fulfilled.

What should trigger the whole onboarding?

A single event — the engagement letter being e-signed in Liscio — should be the trigger that fans out everything else. From that one signature, the Karbon onboarding work gets created and assigned, the matching document-request set goes out to the client, and the recurring close calendar gets scheduled. Using one trigger keeps the process from starting in five different places and stalling when someone forgets to launch a step.

Is it worth automating if we only use Karbon, not Liscio?

Partly. Karbon alone lets you template and assign internal onboarding work, which removes the "remember to launch it" problem. But the client-facing half — document requests, secure messaging, the audit trail of what you asked for and when — is where onboarding actually stalls, because clients are slow to respond. Without a portal like Liscio, you still chase documents by email, which is the larger time sink. The full payback comes from connecting both halves.

How do we keep status from drifting between the two systems?

Designate one system as the source of truth for each stage and only allow one automated path to advance the state. In this recipe, a completed Liscio request set is the only thing that advances the Karbon stage from "gather" to "cleanup." Because exactly one rule moves the work forward, the two systems cannot disagree — there is no second, manual path for someone to update one side and forget the other.

What does this cost to run?

The recurring cost is the orchestration layer plus your existing Karbon and Liscio subscriptions; the build cost is mostly mapping your stages and request templates once. The payback is in coordination hours saved per onboarding — dropping from 5-6 hours to under 2 — which at 20+ onboardings a year compounds quickly. You can see how that scales in our breakdown of how mid-market firms save 40 hours monthly on AP with the same event-driven approach.

Build it before busy season

CAS onboarding is the workflow where the work is easy and the coordination is brutal, and the coordination tax is invisible until you measure it. The fix is not a longer checklist — it is wiring the engagement-letter signature to fan out the Karbon work and Liscio requests, and letting a single completed-request event advance the stage so status never drifts. Do that and you compress weeks into days, start billing recurring fees sooner, and stop bleeding capacity you cannot spare in March.

The reason to build now is the off-season trough: every hour you save per onboarding is an hour returned to your team during the next peak. If you want help mapping your stages and standing up the Karbon-to-Liscio sync, see US Tech Automations pricing and onboarding options and the playbook for getting your first integrated onboarding live this quarter.