Bookkeeping Client Onboarding: Opening Records and Scope

Separate inquiry, engagement, and active access

An inquiry, meeting, upload, or payment does not by itself establish an accepted bookkeeping engagement. Capture the business, entities, owners or authorized contacts, requested services, periods, current systems, payroll or sales channels, deadlines as reported, and intended deliverables using approved minimum fields. Support may explain published onboarding steps, but should not promise acceptance, say work has begun, create bank or software access, or expose another entity’s information. Give inquiry, screening, accepted, implementation, and active-service states clear owners and evidence.

Inventory opening records without validating balances

Request approved categories such as prior financial statements, trial balance, general ledger, bank and card statements, open receivables and payables, payroll summaries, inventory records, fixed assets, loans, equity activity, tax filings, and policy documents as the engagement requires. Support may confirm administrative receipt, not whether a record is complete, authentic, correctly stated, reconciled, or sufficient. Preserve source, period, version, and timestamps; route gaps, duplicates, corrupted files, conflicting balances, and prior-bookkeeper questions to the implementation owner.

Route accounting basis and chart decisions

Cash or accrual basis, fiscal period, entity structure, functional currency, classes, locations, departments, tracking dimensions, control accounts, and the chart of accounts affect how records are organized. IRS Publication 583 describes recordkeeping concepts but does not decide a client’s accounting or tax treatment. General support should not create accounts, map opening balances, convert methods, choose retained earnings treatment, or determine tax consequences. Capture the requested outcome and existing setup, then route it to the authorized accounting or tax professional.

Provision minimum access with clear client controls

Define which systems are read-only, transactional, administrative, or payment-capable; who owns credentials; how invitations are sent; and which approvals remain with the client. Never ask a client to share a password or one-time code. Separate access to bank feeds, statements, payroll, payment platforms, accounting records, documents, and reports. Tell the client what is connected, what remains unverified, who owns implementation, and when the next update will occur without promising converted balances, completed books, a tax result, or a fixed launch date.

Build the control table

Govern sources and accountable handoff

Every answer should point to a dated, owned source. Separate client statements, source documents, bank or processor records, accounting-system output, engagement terms, firm policy, public tax guidance, and professional conclusions. Require qualified review for accounting treatment, chart design, adjustments, reconciliations, financial statements, payroll, tax positions, filing, representation, payment authority, fraud, privacy, security, identity, accessibility, retention, and jurisdiction questions. Log the knowledge version, verification state, engagement boundary, receiving owner, and client confirmation. A summary helps only when its provenance can be checked and the authorized destination accepts the matter.

Protect financial data and service resilience

Collect the minimum information needed in approved channels. Define identity verification, role and entity access, retention, redaction, recording, consent, export, deletion, source-document, credential, bank-data, and vendor controls. Determine legal and contractual security requirements for the configured service instead of assuming a rule applies from the bookkeeping label alone. Provide accessible interaction, error recovery, a human alternative, and reviewed language support. Test outages, duplicate feeds, stale balances, malicious prompts, changed payment instructions, credential disclosure, impersonation, suspicious uploads, and failed handoffs with synthetic data. Record limitations, owners, incident paths, and rollback procedures.

Apply scope and qualified review

This article provides general operational information, not bookkeeping, accounting, tax, legal, payroll, financial, fraud, payment, privacy, security, identity, accessibility, or compliance advice. Client, entity, engagement, accounting basis, period, account, transaction, authorization, jurisdiction, systems, facts, and current law control. A configured conversational system may assist approved intake and routing, but this article does not claim LumiTalk performs bookkeeping; creates or approves a chart of accounts; categorizes, posts, reconciles, adjusts, closes, or certifies books; prepares financial statements or tax returns; files forms; gives advice; approves vendors; executes payments; detects fraud; validates consent; guarantees accuracy, recovery, timing, security, or compliance; reads live accounting or bank data; or provides exact pricing, availability, language, or integration coverage.

Primary sources

Use current primary sources as the factual floor, then obtain business, engagement, accounting-basis, entity, account, transaction, period, tax, payment, and jurisdiction-specific qualified review. IRS Publication 583: Starting a Business and Keeping Records · SBA Manage Your Finances · FASB Standards · NIST SP 800-63-4 Digital Identity Guidelines

Continue through the Bookkeeping cluster

Use the hubs and service page for cluster context, then compare adjacent guides before implementing a workflow. Bookkeeping resource hub · Tax & Accounting resource hub · LumiTalk for bookkeeping operations · Bookkeeping Customer Support Operations Guide · Bookkeeping Transaction Document Intake · Bookkeeping Support Software Checklist