Client onboarding for accounting firms: from signed agreement to first delivery

A client signs on Tuesday. Their profile is complete by Wednesday. On Friday, someone notices that the opening payroll balances are missing, the previous bookkeeper has not finished the prior month, and nobody has reserved review time. The firm has collected information, but it has not yet established a workable engagement.

Onboarding means getting a new client ready for service. It does not end when you send a welcome email. The team must be able to prepare, review and explain the first agreed work, then repeat the service in later periods. The steps below suggest a process for an accounting or bookkeeping firm. They are not approvals that software enforces automatically.

Agree on the first work due before requesting documents

Begin with an outcome and a period. “Monthly bookkeeping” is too broad to schedule. “Prepare the October management package, review it internally, and discuss exceptions with the owner by the agreed date” identifies something the team can accept or decline. Name what the first package includes and what remains outside scope.

Separate the service start date from the first period being processed. A November start may include an October close and a separately priced cleanup of September. Without that distinction, historical corrections quietly consume the time reserved for recurring work.

Ask the engagement lead to confirm these four facts with the client:

• The legal entity or individual receiving each service, not just the contact's display name.
• The first reporting period and the specific outputs promised.
• The client's document deadline, the firm's review window and the delivery date.
• Who can approve scope changes, resolve accounting questions and receive final material.

A useful onboarding record carries those decisions forward. It should not force the preparer to reconstruct the sales conversation from an old proposal.

First: agree on the services and responsibilities

Before starting the main work, follow the firm's steps for accepting a client. Confirm which services are included and excluded, who does what, the fees and how you will communicate. Get the required signatures. Resolve disagreements about work for earlier periods. Follow the professional rules that apply to your firm. This article is not a legal checklist for accepting a client.

Record unresolved matters explicitly. A client's request to add payroll is not the same as the firm accepting responsibility for the next pay run. Identify who handles the approaching run until the new arrangement is confirmed. Silence is a poor transition plan when an employee's wages or a statutory deadline is involved.

Bookwits Sign can help prepare a signing request, choose recipients, assign fields and track completion. The partner or person leading the work still checks whether the agreement and permissions are sufficient. A signature completes one step. It does not prove that the team has everything needed to start.

Second: check access and starting records

Use a readiness checklist organized by deliverable, not an indiscriminate request for every document the client has ever received. For an initial monthly close, request the relevant statements, outstanding transaction support and opening records. For payroll coordination, identify the payroll provider and the approved opening and year-to-date information needed by the person actually processing payroll.

Distinguish “invitation sent,” “access accepted” and “required information available.” They are different events. Have the responsible staff member confirm the needed access through the outside system's proper process. Do not collect a client's banking password or assume that a portal invitation authorizes CRA representation.

Bookwits Documents supports organizing client-context files and sharing selected folders. Use that structure to keep source records, engagement material and final outputs distinguishable. Confirm the right client, company and period before uploading; two companies with the same owner do not share an accounting identity.

For each missing item that holds up work, name who will act, what they will do and how the delay affects delivery. “Waiting for records” does not say enough. Try: “The client's controller will send the September payroll summary. The payroll specialist will check the opening totals before the first October pay run.”

Third: set aside time to prepare and review the work

Once you have the essential information, estimate the time to do the work and review it. A new client often needs extra time for learning, questions and corrections. Later months may not need that time. Keep this one-time setup effort separate from the regular budget. Otherwise, the first month's extra hours can make later overruns hard to explain.

Create work with a named assignee and due date. Where useful, split preparation, technical questions, review and client delivery into subtasks. The Bookwits Tasks guide documents those basic building blocks and recurring schedules. It does not establish that the application will automatically block a dependent task until another is approved.

Record a clear decision for the team: ready, ready with an agreed exception, or not ready. Someone must approve an exception and agree on any change to the promised work or date. Do not mark a client ready just to finish the onboarding list.

Reserve review time before promising a delivery date. An available preparer does not solve a reviewer bottleneck, and a calendar appointment does not make missing source records appear.

An original first-cycle example: a late payroll handover

Suppose a fictional practice agrees to start coordinating a retailer's monthly bookkeeping on November 2. The first output covers October. Its internal plan allows six hours of preparation, two hours of review and one hour for the delivery conversation: nine hours in total. Payroll processing remains with the existing provider until a separate transition is approved.

The retailer supplies bank statements promptly but cannot produce the payroll liability reconciliation. The lead does not declare onboarding complete because the client has uploaded “most” documents. Instead, the lead records the missing reconciliation, asks the existing provider for the supporting report through an authorized contact, and reserves a follow-up discussion.

The team can still inspect the available records and identify other exceptions. It cannot represent the payroll balances as checked. If the missing evidence threatens the agreed date, the lead discusses a revised delivery or a clearly limited preliminary discussion with the client. The scope decision is documented; it is not disguised by changing a task colour.

A checklist names what you need. The next step is a decision: if something is missing, can the work still go ahead? Someone must assess the effect, not just tick a box.

Finish with a recurring owner, not a closed welcome task

After review, deliver the agreed output and explain outstanding issues in language the client can act on. Confirm where final documents live, which questions require an answer and when the next cycle begins. The client should know the next document deadline without needing to reread the engagement letter.

Then hold a short team handover. Compare actual hours with the estimate. Remove setup steps needed only once, but keep checks and information needed every period. Name the client's ongoing contact and a backup. Check the company and dates on the next period's tasks. Do not copy the first month's unusual issues without reviewing them.

Bookwits can bring client context, tasks, documents, requests and signing work into the same practice-coordination environment. The firm supplies the judgement: whether records reconcile, whether an authorization is valid, whether the promised scope is achievable, and whether the client is ready for recurring service.

Onboarding is complete when that judgement has been made and handed over—not when the final welcome message leaves someone's inbox.