How to automate new client onboarding for a bookkeeping practice

This short guide from AR Labs is for owners of small bookkeeping and accounting practices who want to automate new client onboarding: collecting the details, documents and system access needed to start work, with reminders and a check that the file is complete. New clients rarely send everything at once, and the first weeks go on chasing statements, logins that do not work and questions nobody asked.

Published evidence about bookkeeping onboarding is limited, and we have not built an onboarding system for a practice. This guide therefore rests on our general method for mapping a business process before automating it and on the published features of client-request tools. It sets out the method and leaves the lists to your practice, which knows them better.

What to change

Today the bookkeeper is often the only checklist: one email lists what is needed, items arrive by email over weeks, and gaps surface during the first month's work.

flowchart TD
  S["Client signs engagement letter"] --> R["One request: form, secure uploads, access invitations"]
  R --> M["Reminders for missing items only"]
  M --> A["Items arrive in one place"]
  A --> C{"Named person checks: complete and usable?"}
  C -->|"wrong or unclear item"| F["One specific request back to client"]
  F --> A
  C -->|"complete"| K["Status: ready to start"]

The target flow. The diamond is a person's decision; the tools do the sending and reminding.

Client-request tools such as Content Snare already provide templated requests, uploads from a phone, reminders that keep going until every item is in, and rejection of a single wrong item (Content Snare). Your practice-management software may have onboarding checklists or a client portal of its own. Check what you already pay for before adding anything.

Step 1: Write the onboarding list for each client type

What to do. For each kind of client you take on (for example sole trader, limited company with payroll, charity), list what you need under three headings: details (business details, year end, VAT or sales-tax status, payroll arrangements, who approves what), access (accounting software, bank feeds, payroll, receipt apps) and documents (prior-period accounts, recent statements, open invoices). Mark each item "needed to start" or "needed later".

Why. Reminders and a completeness check only work from a written list, and the split stops onboarding stalling on items that can wait.

• List written for each client type
• Each item marked "to start" or "later"
• List checked by whoever does the first month's work

Step 2: Use a safe route for each kind of item

What to do. Ask for details through a form and for documents through a secure upload in a portal or request tool, not as email attachments. For system access, use the invitation or user-sharing feature each system provides, so the client invites your practice as its own user. Never ask a client for a password, and never store one in a form, spreadsheet, email or automation tool.

Why. A shared password lets you act as the client in their bank or software, with nothing to show which of you did what; an invited user can usually be given limited rights and removed when the work ends. Client records are personal and financial data, so data-protection law and your professional body's rules apply to how you collect, store and share them. Tell clients how their information is held, keep only what you need, and check the rules that apply to your practice. Automate the collection of details and documents; keep credentials and payment details out of any automated flow.

• Details by form, documents by secure upload
• Access by invitation only; no passwords requested or stored
• Clients told how their information is stored and used
• Data-protection duties checked for each tool in the route

Step 3: Send one request, with reminders for missing items

What to do. Send a single request covering everything in the "to start" list, each item with a due date. Set reminders to list only the outstanding items, stop when an item arrives, and offer a call if the client is stuck.

Why. One visible list is easier for a client than a trail of emails, and reminders about only the missing items chase without nagging.

• One request per new client, with due dates
• Reminders name only outstanding items
• Every reminder offers a way to reach a person

Step 4: Check the file before work starts

What to do. When the "to start" items are in, a named person checks each one is usable: statements cover the right period, access works, details are consistent. Only then mark the client "ready to start". After each onboarding, note what was late, wrong or missing from the list, and update the list.

Why. A tool can record that a file arrived; a person has to judge that it is the right file. For example, statements that stop a month short of the start date get one specific request for that month.

• Named person checks usability, not just arrival
• "Ready to start" set deliberately
• List updated after each onboarding

How far to go

Most practices can stop at configuring a client-request or practice-management tool. Connecting it to your practice-management record, so a signed engagement letter sends the request automatically, is the next step if details are being re-typed. Anything beyond that, such as a guided intake that asks follow-up questions, should come only after the steps above have run for a while and should still exclude credentials and payment details. Keep a personal welcome; automate the chasing.

AR Labs offers this kind of discovery and design work to owner-run businesses; more about us is on the about page.