What to Look for in Accounting Client Onboarding Software

A firm decides it is time to buy client onboarding software. Every engagement starts with the same chase: request the documents, wait, ask again, discover a file is for the wrong year, and only then hand a preparer something they can work with. Search for a fix and you get ranked lists of the “best” tools, most of them written by the vendors being ranked.

Those lists are a poor place to start, because the product is the least important decision you will make. Before you shortlist a product, decide three things: whether the software you already own does this, what data security you are legally required to demand of any vendor, and how the tool handles the clients who never finish. A firm that answers those three questions can evaluate any shortlist quickly; a firm that skips them buys a portal and keeps the same chase.

This guide is written for a US accounting or professional-services firm — a managing partner, firm administrator, or operations leader who onboards individual and business clients each cycle and wants preparers to receive work-ready files. It walks through the three decisions in order and gives you a scoring method you can apply to whatever tools you are considering.

Compare providers on evidence with the open AI vendor evaluation scorecard.

First check what your practice management system already does

Many US firms already run an all-in-one practice-management platform — a system such as the ones profiled in vendor round-ups like this “Top 6” list — that already includes a client portal, document requests, engagement letters, and e-signature. A separate onboarding tool then duplicates capability you are paying for and adds one more login for staff and clients.

The published comparisons rarely help here, because they mix standalone onboarding tools with all-in-one platforms and never tell you which you already own. Several widely shared best onboarding software lists are published by vendors, quote no prices, and are written for UK, EU or Australian firms whose anti-money-laundering duties differ from US rules. For example, an “8 best” round-up leans heavily on know-your-customer and identity-verification features and cites UK and EU providers and GDPR — useful signals for a British firm, less so for a US tax practice.

So the first decision is not which product but configure, buy, or redesign: turn on and standardize the onboarding features in the system you already have, add a dedicated tool because your platform genuinely cannot do it, or fix the manual process and definitions first so you are not automating a broken handoff. Write down which one you are choosing and why before you take a single demo.

The data security you are required to demand from any vendor

This decision is not optional, and it disqualifies vendors before features matter. The FTC Safeguards Rule classifies tax preparation firms as financial institutions and requires a written security program with a designated qualified individual, encryption of customer information in transit and at rest, multi-factor authentication for anyone accessing customer information, and the selection of service providers that can maintain appropriate safeguards. The breach-notification duty took effect in May 2024.

The IRS reinforces this for anyone handling taxpayer data: it states that tax professionals are required by law to have a Written Information Security Plan, advises contracting a service provider that maintains safeguards, and publishes a free template (Publication 5708) covering employee management, information systems, and detecting and managing failures.

Read together, these mean an onboarding vendor is a service provider handling your clients’ Social Security numbers and financial records, so your own legal obligation flows to it. Before you compare features, require encryption in transit and at rest, multi-factor authentication for anyone who can open client files, and a written description of what the vendor may read or change. Ask for a current SOC 2 report or equivalent independent evidence, its data-retention and disposal terms, and its breach-notification commitment. A vendor that cannot answer these has already failed, whatever the demo looked like.

What actually separates the tools once security passes

Once two or three tools clear the security bar, the marketing features converge and the useful differences are narrow. Judge them on how the work actually moves:

• Structured requests tied to a definition of complete. Can you define, per service line, exactly which documents make a file ready to start — and does the tool track against that definition rather than just collecting uploads?
• Write-back to your systems. Does it push the client record and documents into your practice-management or tax software, or does someone rekey them? A portal that only stores files moves the chase; it does not remove it.
• Client-side friction. Will an 80-year-old individual client and a busy controller both complete it on a phone without a new password each time? The best-designed workflow fails if clients abandon it.
• Where exceptions surface. When a client uploads last year’s return or skips a form, does the tool route that to a named person, or does it sit in a queue no one owns?

Identity verification, watchlist screening, and anti-money-laundering checks dominate the vendor lists because so many are written for markets where accountants carry statutory obligations to run them. A US tax or accounting firm should decide whether it actually needs those modules or is paying for a compliance feature its own rules do not require, and read a page linked to your firm’s real duties — the operating problems on our accounting page assume US practice and delivery.

A decision method: configure, buy, or redesign

The configure, buy, or redesign decision and the six-part scoring approach below are Clairvance's own review method, not a validated benchmark, a ranking of products, or a guarantee of any result. Give every candidate the same brief — one service line, its current systems, representative inputs, and the definition of a complete file — and then score it.

Score each candidate from zero to three on six things that decide whether onboarding actually gets faster. Zero means the requirement is missing or unsupported; one means a general explanation; two means a specific demonstration on your example; three means evidence verified against your stated requirement.

1. Security evidence — independent proof, not assurances.
2. Integration write-back — does data reach your system of record without rekeying?
3. Completeness definition — does the tool know when a file is ready, per service line?
4. Exception routing — does a stuck client reach a named owner with a next action?
5. Client-side friction — will your least technical client finish unaided?
6. Ownership and exit — can you export your data and clients and leave without losing the history?

A missing critical requirement — usually security or exit — is not offset by a high total elsewhere; keep it outside the average and treat it as a gate. A demo that scores well on presentation but cannot show write-back on your own example is a two at best.

The following figures are a labeled hypothetical that shows how to reason about capacity; they are not a measured Clairvance result or a promised saving. Suppose a 25-person firm onboards 400 individual clients each tax season, and each client today takes six separate staff touches — an initial request, two follow-ups, a document sort, a completeness check, and a handoff note — before a preparer starts. That is roughly 2,400 touches concentrated into a few weeks. If a well-configured workflow removes the two routine follow-ups and the manual sort for the 70 percent of clients whose files arrive cleanly, it frees about 280 clients × 3 touches, or 840 touches, from the busiest weeks. That is recovered capacity in the season, not cash saved and not a headcount reduction; whether it becomes earlier delivery, more review time, or clients served depends on decisions the software does not make.

Who owns the client who never finishes

The part the tool cannot decide is the one that stalls onboarding. Software sends reminders; it does not choose when to stop chasing, when to escalate to the partner, or whether to begin work on a partial file. Every onboarding design needs a named owner for the client who goes quiet, a rule for how long a file waits before a person intervenes, and a definition of “ready” that a human confirms.

A green “complete” status on a dashboard is not a work-ready file. It means the requested boxes were filled, not that the documents match the engagement, cover the right period, or belong to this client. Buying software without assigning that ownership simply relocates the bottleneck from the inbox to the portal.

How to run the comparison without buying on the demo

Run the comparison, do not watch it. Give each vendor the same brief and the same representative — not live production — examples, and include the messy cases: a duplicate upload, a prior-year document, a photo instead of a PDF, a business return mixed in with a personal one. Ask how the system handles a missing document and an unavailable integration, and who receives the exception. Require the provider to explain what evidence would make it recommend configuring the platform you already own instead of buying its tool.

Score each vendor on the same six criteria on the same day, record the artifact and the open question next to each score, and decide: select, request more evidence, run a bounded trial, or decline. The tool you pick matters far less than starting from those three decisions — what you already own, the security you must demand, and who owns the client who never finishes.