Automation

How do I automate client onboarding for an accounting firm?

Flow Mesh · · 6 min read

A new client says yes, and the work begins: an engagement letter to send and chase, an identity check, a list of documents to request, access to their Xero or QuickBooks file, a job set up in the practice management tool, a first invoice. In many 10 to 50 person firms, each step depends on someone remembering the next one. Onboarding takes weeks, and the client's first impression is a run of chasing emails.

The direct answer: automate onboarding as one chain that starts when the client accepts the proposal. A proposal tool generates and collects the signed engagement letter, acceptance creates the client record and the onboarding job, the practice management tool sends document requests with reminders that stop when the client responds, and a person checks the few steps that need judgment. Most of this is built from features your tools already have, connected in the right order.

The onboarding chain, end to end

  1. Proposal accepted and engagement letter signed, in one step.
  2. Client record created once in the system that owns client data, then passed to the others.
  3. Onboarding job created from a template, with tasks assigned to named people.
  4. Identity and engagement checks completed and recorded by a person.
  5. Documents and access requested from the client, with automatic reminders.
  6. Ledger access set up: the client's Xero or QuickBooks file connected to the firm.
  7. Billing started: first invoice or recurring billing set up from the accepted services.
  8. Kick-off meeting booked, and the job handed over to the team that does the work.

Step 1: proposal and engagement letter together

Sending a proposal, then a separate engagement letter, then chasing both is the slowest part of onboarding in most firms. Proposal tools built for accountants combine them. Ignition's Xero App Store listing, for example, says it creates a new client record in Xero or matches an existing one, turns each service line in the proposal into an invoice line item, and can create jobs and sync client information with Xero Practice Manager, as listed in October 2026. Similar tools exist for other practice management systems; check what your own stack supports before adding a new subscription.

Whatever the tool, set it up so that:

  • the engagement letter's terms are generated from the services selected, using templates your firm has approved,
  • acceptance and signature happen in one action for the client, and
  • acceptance is the trigger for everything that follows.

Have your professional body's guidance and your own lawyer or compliance lead review the engagement letter templates before automating them. Automation sends the wrong letter faster than a person does.

Step 2: create the client record once

The classic onboarding mistake is entering the same client three times: in the CRM, in practice management, and in the ledger. Decide which system owns the client record. In many accounting firms, the practice management tool (Karbon, Xero Practice Manager, TaxDome and similar) owns it, and the others receive it.

Then make sure each step searches before it creates. A proposal tool that matches existing clients, as Ignition's listing describes, helps. If you connect tools with Zapier or Make, add a lookup step on a stable key such as the client's email or company registration number. Our guide to Karbon, Xero and HubSpot for accounting firms covers which tool should own which record.

Step 3: an onboarding job from a template

Every new client should get the same onboarding job, created automatically when the proposal is accepted. Karbon publishes a free client onboarding template that uses client tasks to request initial information, followed by a kick-off meeting. Whatever tool you use, the template should contain:

  • each step above as a task with a named role (not "someone"),
  • due dates relative to acceptance, for example "documents requested within 2 days",
  • the internal checks that need a person, clearly marked, and
  • a final "handed over" task that closes onboarding and opens the first piece of real work.

Step 4: identity and engagement checks stay with a person

Most firms have to verify who the client is and record why they accepted the engagement, under the anti-money-laundering and professional rules that apply in their country. Automation can prompt these checks, collect the documents and store the result against the client. It should not decide them. Keep the acceptance decision as a task a named person completes, and check with your compliance lead or professional body what must be recorded and for how long.

Step 5: document requests that stop when the file arrives

Document collection is where onboarding stalls. The fix is a request system where each item is tracked separately and reminders stop automatically once it arrives.

Karbon's client requests are a good example of how this works, as documented in October 2026:

  • requests can be built into a work template, so every onboarding job sends the same list,
  • clients respond through a secure link without creating a login,
  • automatic reminders can be gentle (seven days before the due date, on the due date, then daily once overdue), urgent (daily) or custom,
  • reminders need a due date, and they stop after the fifth reminder or once the client completes the task.

If your tool has no equivalent, you can build a simpler version with a form tool and an automation platform: one form per request list, a reminder schedule, and a step that checks whether the form was submitted before sending each reminder. Avoid plain email chasing; nobody can see what is outstanding.

Keep the list short for the first request. Ask for what you need to start, and request the rest later in the job.

Step 6: ledger access

For Xero clients, the firm usually needs to be invited to, or to create, the client's organization. For QuickBooks Online clients, the client typically invites the firm as their accountant from within QuickBooks, and Intuit's troubleshooting article covers the common reasons an invitation will not connect. This step is hard to automate fully because the client must act inside their own account. What you can automate is the reminder: a client request with short, written instructions for their system, and a task for your team to confirm access once it works.

Step 7: billing from the accepted proposal

If the proposal tool creates invoices or recurring billing from the accepted services, use that and do not rebuild it elsewhere. If it does not, create a draft invoice from the accepted services and have a person approve it. Map each service to the right account code and tax rate once, and review the mapping before the first live invoice.

What to leave manual

Not everything should be automated. Keep a person on:

  • the decision to accept the client,
  • the identity and engagement checks,
  • any exception, such as a client with several entities or an unusual year end, and
  • the kick-off conversation itself.

A realistic way to start

Do not build the whole chain at once. Start with the step that costs the most time in your firm today, which is usually document collection or engagement letters, and get it running reliably for a month. Then connect the next step. Write down who owns each automation and where its error alerts go. The same approach works for other professional firms; our article on automating law firm client intake follows a similar chain.

How Flow Mesh helps

Our stack audit maps your current onboarding across proposal, practice management and ledger tools, gives each tool a verdict (keep, configure, consolidate or replace) and sets out the onboarding chain in a written scope. If you want us to build it, we quote it in writing after the audit and work inside your own accounts. See how we approach accounting firms for more detail.

Key takeaways

  • Treat onboarding as one chain triggered by the client's acceptance, not a list of separate chores.
  • Combine proposal and engagement letter, and have approved templates reviewed before automating them.
  • Create the client record once, in the system that owns it, and search before creating anywhere else.
  • Use document requests with reminders that stop when the client responds, instead of email chasing.
  • Keep client acceptance, identity checks and exceptions with a named person.

FREE CHECKLIST

The SaaS stack self-audit: 12 checks

The same questions our paid audit starts with. Work through them in an hour and see whether your stack is costing more than the subscriptions. We'll email you the checklist.

More articles

See all articles →