Client Accounting Onboarding Checklist for Bookkeeping Firms

Good client onboarding is not an administrative handoff. It is the first accounting control in the engagement.

If scope, opening balances, access, or client responsibilities remain unclear, the first month-end close becomes an investigation. The team reconstructs decisions from email, reviewers cannot tell whether a difference is new or inherited, and the client experiences requests as a series of surprises.

This checklist gives bookkeeping firms and client accounting services teams a practical route from signed engagement to repeatable monthly delivery. It complements our broader guide to managing multiple client ledgers but focuses only on the onboarding period.

It is general operational guidance. Adapt it to the engagement, applicable accounting framework, privacy obligations, professional standards, and local legal or tax requirements.

Define “onboarded” before collecting documents

A client is not onboarded when the portal invitation has been sent. Onboarding is complete when the firm can perform the agreed service without relying on undocumented assumptions.

Set five exit criteria before work begins:

• the signed scope and delivery timetable are translated into working instructions
• the accounting record has a verified starting point
• required systems and source documents are accessible
• client and firm responsibilities have named owners and deadlines
• the first reporting cycle can enter normal preparation and review

Phase 1: Confirm acceptance, scope, and ownership

Start with the commercial agreement, but convert it into information the delivery team can use.

Engagement checklist

• Confirm the legal entity or entities covered by the engagement.
• Record the agreed services and explicit exclusions.
• Identify the accounting framework, reporting basis, and financial year-end.
• Record filing, management-reporting, payroll, and tax deadlines relevant to the work.
• Define the expected deliverables and delivery frequency.
• Name the client sponsor, day-to-day contact, preparer, reviewer, and escalation owner.
• Record materiality or review thresholds used by the firm, where applicable.
• Document how scope changes and out-of-scope requests will be approved.

For firms performing engagements under IAASB standards, client acceptance and continuance form part of the quality-management system described in ISQM 1. Even where that standard does not apply, its risk-based principle is useful: the decision to serve a client should be deliberate, documented, and consistent with the firm's capabilities.

Phase 2: Build a controlled information request

Request information once, in a structured list, with an owner and due date for every item. A generic “send us your accounting records” email creates ambiguity for both sides.

Core information checklist

• Legal name, registration details, addresses, and tax identifiers
• Ownership and key contact information appropriate to the engagement
• Prior-period financial statements and trial balance
• General ledger detail for the agreed comparative period
• Chart of accounts and tracking categories
• Bank, card, payment-processor, loan, and petty-cash statements
• Open customer invoices and supplier bills at the transition date
• Fixed-asset, inventory, payroll, tax, accrual, and prepayment schedules where relevant
• Details of connected applications and recurring data imports
• Existing accounting policies, recurring journals, and known unresolved items

Use a secure channel suitable for financial and personal data. Avoid collecting documents “just in case.” Ask for what the engagement requires, define how long it will be retained, and restrict who can access it.

Track each request as Not requested, Requested, Received, Validated, or Not applicable. “Received” is not the same as “usable.”

Phase 3: Establish the opening accounting position

Opening balances are the dividing line between inherited history and the firm's current work. Record that line clearly.

Opening-balance checklist

• Agree the opening trial balance to the approved prior-period financial statements or other accepted source.
• Confirm that total debits equal total credits after import.
• Reconcile bank and card balances to statements at the transition date.
• Tie receivables and payables control accounts to their detailed ageing reports.
• Tie fixed assets, loans, inventory, payroll liabilities, and tax balances to supporting schedules where relevant.
• Confirm retained earnings and current-year results rolled forward correctly.
• Map legacy accounts to the new chart without silently changing their economic meaning.
• List unsupported, disputed, or unreconciled balances separately.
• Record who approved opening adjustments and retain the supporting evidence.

Do not force an inherited difference into a suspense account simply to make onboarding appear complete. Assign it an owner, risk level, proposed treatment, and resolution date. If the engagement permits work to begin before resolution, state which reports or decisions may be affected.

Phase 4: Configure the ledger without erasing client context

Standardise setup conventions across the firm, but preserve each client's economic reality.

Ledger-configuration checklist

• Confirm the base currency, financial year, tax settings, and reporting basis.
• Review the chart of accounts for duplicates, obsolete codes, and reporting gaps.
• Configure departments, projects, funds, locations, or other tracking dimensions required by the scope.
• Set invoice, bill, credit-note, and journal numbering rules.
• Define approval thresholds and period-locking responsibilities.
• Configure recurring transactions only after their source and treatment are verified.
• Connect bank feeds and other integrations to the correct legal entity and account.
• Test at least one complete data flow from source to ledger and report.

Bank-feed access is not proof that the opening balance is correct. Treat connection, historical import, reconciliation, and feed health as separate checks. For detailed matching controls after onboarding, read Why Bank Reconciliation Is Broken.

Phase 5: Grant access by responsibility

Create access from the role design, not from the quickest available template.

The NIST definition of least privilege provides a practical rule: a user or process should receive only the access needed to perform its assigned task.

Access checklist

• List every person and connected system that needs access.
• Assign client scope separately from functional permissions.
• Separate preparation, review, approval, and administration where the engagement requires it.
• Require individual accounts; do not share credentials.
• Enable multi-factor authentication where available.
• Record the owner and purpose of every integration or service account.
• Test a standard staff role and a client role before go-live.
• Set a process for changing and revoking access.

Phase 6: Rehearse the first close

Do not wait until the reporting deadline to discover that a client cannot provide a required schedule.

Walk one representative period—or a controlled sample—through the intended workflow:

• Confirm expected source data arrives through the agreed channel.
• Process representative bank, revenue, expense, payroll, and adjustment transactions.
• Route an exception to the client and retain the response.
• Complete a preparer-to-reviewer handoff.
• Generate the agreed reports and confirm their dimensions and comparisons.
• Test approval and period-locking steps.
• Record any work still performed outside the standard workflow.

Then hold a short readiness review. Classify every remaining issue as blocks go-live, can be resolved during the first cycle, or accepted limitation. An accepted limitation needs an owner, effect, and review date—not just a note that everyone is aware of it.

For the recurring procedure after onboarding, use the Month-End Close Checklist.

The onboarding handoff record

End onboarding with one concise handoff that the preparer and reviewer can both use. It should contain:

The engagement owner should approve the handoff. The first monthly team should not have to infer whether onboarding is actually finished.

A simple measure of onboarding quality

Avoid judging onboarding by speed alone. A fast setup that creates three months of rework is not efficient.

Track a small set of operational signals through the first two closes:

• opening issues discovered after go-live
• repeated requests for information already requested during onboarding
• access corrections after work begins
• first-close items returned because the agreed treatment was undocumented
• days blocked by missing client-owned inputs

Review the pattern, not just the number. One late document may be incidental; the same missing schedule across several new clients indicates a weak onboarding request.

How this checklist was prepared

NewLedger's editorial team prepared this checklist from the product's multi-company setup, imports, permissions, reconciliation, approvals, reporting, and period-control workflows. We reviewed the control principles against public guidance from IAASB and NIST, linked above.

The checklist is intentionally system-neutral and does not claim that every item applies to every client. Firms should add jurisdiction-specific acceptance, privacy, tax, anti-money-laundering, independence, and professional requirements where relevant.