A bookkeeping onboarding checklist helps you prepare the records, access, and business context a bookkeeper needs to begin recurring work. Before handing over files, identify what is ready, what is missing, and what needs a decision. The goal is not to make every historical entry perfect; it is to give the bookkeeping team a clear starting point and a reliable way to resolve uncertainty.

Discuss your bookkeeping setup

What should you decide before onboarding begins?

Start with a one-page scope note. Name the legal entity or entities, the date work should begin, the first reporting period, and the people responsible for providing records and answering questions. If there are multiple entities, explain which bank accounts, cards, payroll records, and revenue streams belong to each one. Do not assume that similar names mean the transactions can be combined.

Separate ongoing monthly bookkeeping from historical cleanup. A business may need current transactions recorded each month while older reconciliations or opening balances are investigated in a separate phase. Write down the period where regular records are believed to be dependable and the last month each account was reconciled. If that date is unknown, say so rather than presenting it as confirmed.

List the tasks you expect to be included and the tasks that need separate confirmation. These can include transaction categorization, bank and card reconciliation, accounts payable or receivable tracking, payroll entries, sales tax records, financial statements, and year-end support. Bookkeeping, tax preparation and filing, and advisory work are not automatically the same engagement. The bookkeeping services page is a starting point for discussing the type of recurring work you need; confirm the actual scope and terms directly.

Also record constraints that shape timing: a lender request, board meeting, tax-preparation deadline, financing close, or internal review date. A deadline is useful context, but it does not establish that all records needed to meet it are available. Ask what must be supplied, by whom, and by when, and decide how incomplete items will be reported.

How do you prepare account access safely?

Make an inventory of the systems that contain financial information. Common examples include accounting software, bank and credit-card portals, payment processors, payroll, invoicing, bill payment, expense management, and document storage. For each, note the system name, the business entity, the administrator, the purpose, and a safe identifier such as the last four digits of an account. Keep passwords, authentication codes, full account numbers, and recovery details out of the inventory.

Ask which permissions are needed for the agreed tasks. Read-only access may be appropriate for some records; other work may require permission to create or edit accounting entries. A bookkeeper should not automatically receive authority to move money, approve bills, change bank details, add users, or alter payroll. Keep payment approvals and administrator ownership with the people the business has designated.

Use the institution’s user-management feature when available. Give each person an individual account, use the smallest permission set that supports the work, and avoid sending shared credentials through ordinary email or chat. If a system has no suitable delegated access, ask about the approved secure method before sharing anything. At the end of an engagement or when responsibilities change, review users and remove access that is no longer needed.

Record any access blocker in a short list: the system, the missing permission, who can grant it, and the expected next step. For example, “Operating account ending 4821: statements available, transaction access not yet granted; owner to invite bookkeeper.” This is clearer and safer than sending a password with no explanation.

Which records belong in the first handoff?

Begin with the current accounting file or an export, recent financial statements, and the statements needed for the first period of work. Include bank and card statements, reconciliation reports, the chart of accounts, and general ledger detail when available. Label every file with the entity and period. A document called “final” is less useful if no one can tell which month or version it represents.

Include lists of open customer invoices, credits, deposits, unpaid vendor bills, and vendor credits when they matter to the work. Add loan or line-of-credit statements that show balances and activity. For businesses with inventory or fixed assets, gather the schedules and records used to support those balances. Avoid sending unrelated personal documents merely because they are in the same folder.

If prior-year tax returns, accountant-prepared statements, or year-end entries may help explain opening balances, provide them with clear labels and a note about their status. Distinguish entries already posted in the accounting file from proposed adjustments or items still under review. A tax return can be a useful reference, but it does not by itself prove that every balance in the current books agrees with the return.

Federal recordkeeping guidance depends on the records and circumstances involved. Consult the Internal Revenue Service for official information and ask a qualified tax professional about your situation. A general onboarding list cannot determine the specific retention obligations of every business.

How should you explain the way money moves?

Statements show dates and amounts, but often not the purpose of a transaction. Write a concise explanation of the business’s revenue channels, payment timing, processor settlements, refunds, fees, transfers, loans, owner activity, and unusual purchases. The goal is to connect transactions to evidence and business context, not to prescribe an accounting treatment when the facts are incomplete.

Payment processors illustrate why context matters. A deposit into the bank may be a net payout after fees, refunds, reserves, or adjustments rather than the same amount as gross sales. Provide settlement reports that show the components and the payout date. If the accounting system already contains a sales summary, identify which report supports it and whether it covers the same date range as the bank deposit.

For transfers between business accounts, identify both sides. Without that information, a deposit can look like revenue even when it is simply a movement of the business’s own cash. For loan proceeds, supply the statement or agreement that identifies the lender and balance. For owner-paid business expenses, provide the receipt and explain who paid, when, and how reimbursement was handled, if known.

Prepare a vendor note for charges that are recurring, unusually large, or difficult to identify. Include the vendor, typical purpose, the invoice or receipt location, and a contact who can answer questions. If a subscription charge changes, state what you know about the change and leave the cause open if you do not know it. A clear “needs confirmation” is more useful than a confident guess.

What customer, vendor, and payroll information is relevant?

Provide only the information needed for the agreed work. Open invoices and customer credits help explain amounts expected from customers. Unpaid bills and vendor credits help describe amounts owed. If deposits are collected before work is complete, explain how the business tracks them and provide the supporting reports or agreements that are available.

Identify where approval status is recorded and who may approve spending. The bookkeeping record should not be confused with approval authority. If an invoice is in a system but has not been approved, make that status visible rather than treating it as ready for payment. Likewise, identify who can confirm whether a disputed customer balance is still collectible or whether a vendor credit has been applied.

For payroll, identify the provider, the employing entity, the relevant bank account, and the reports needed to understand payroll activity. Share sensitive employee data only through an approved process and only to the extent required for the work. Clarify who handles payroll administration, who reviews payroll reports, and who is responsible for any associated filings. Do not treat access to payroll records as authorization to change compensation or submit payroll.

If sales tax applies, identify the states or jurisdictions the business believes are relevant, the filing periods, and who handles returns and payments. Include notices or filed returns that relate to the bookkeeping period. The bookkeeping handoff can help organize source information, but it should not be treated as a determination of registration, nexus, or filing obligations.

How do you track missing records and unresolved questions?

Maintain an open-items log instead of burying uncertainties in email. For each item, record the period, account or transaction, amount if known, what is established, what is missing, who can answer, and the next action. Add the supporting document or system location once the question is resolved. If the answer comes from memory rather than a record, label it that way.

• Missing statement: identify the account and month, name the person who can download it, and set a follow-up date.
• Unexplained deposit: record the date, amount, account, and any related processor or customer record; assign someone to verify the source.
• Old customer credit: note the customer, original period, balance, and available correspondence; ask the person who manages the relationship what is known.
• Loan balance differs: compare the accounting balance with the lender statement, note the date of each figure, and request the payment or adjustment history.
• Unclear vendor charge: save the receipt or statement line, identify the likely business owner, and leave the classification open until evidence is available.

Mark each item as blocking, important but not blocking, or informational. A missing bank statement may prevent reconciliation for a month. A question about a minor expense may not prevent other accounts from being reviewed. This distinction helps set expectations without hiding the issue. When an item is resolved, preserve the answer and supporting source so it does not have to be rediscovered during the next close.

Tell the bookkeeper about material changes that affect the records: a new bank account, a change in entity structure, financing, a new processor, a billing-system migration, or a new payroll provider. Include effective dates, relevant agreements, and who owns the transition. A change midway through a month may explain why the same transaction appears differently across reports.

How should you set reporting expectations?

Identify who will use the reports and what decisions they support. A founder reviewing cash availability may need a different discussion than a finance lead preparing a monthly package for internal managers. Name the intended readers, the reporting period, and the questions the reports should help answer. Potential outputs may include a profit and loss statement, balance sheet, cash-related schedules, or general ledger detail, depending on the agreed work.

Ask how the reporting basis will be presented and how open items will be disclosed. If some figures are preliminary because records are missing, readers should be able to distinguish those figures from reconciled balances. Clarify whether reports are expected after all statements arrive or whether an interim view may be useful sooner. Do not assume that a report is complete merely because it has been exported.

Agree on a monthly rhythm with practical handoff dates. For example, the business might set an internal target to upload statements and receipts soon after month-end, designate a person to answer questions during the following review, and set a report date that allows time to resolve discrepancies. The exact schedule depends on the volume and condition of records. Agree on what happens when a required statement or answer is late.

Tracking categories such as department, location, project, or product are useful only when source information is captured consistently and someone will use the resulting breakdown. Before asking for a new category, state the decision it will support and who will apply it to transactions. A project report built from incomplete tags can create false precision rather than better visibility.

Keep actual results separate from budgets and forecasts. If management wants a forecast, fundraising preparation, or board reporting, define that work separately from transaction recording and agree on the inputs and assumptions. Reliable monthly books can provide a foundation for those discussions, but the additional analysis is not automatically part of bookkeeping.

What does a useful handoff packet look like?

Build an index before uploading a large folder. For each file, record its entity, period, type, status, storage location, and owner. Do not put full account numbers, passwords, or authentication codes in the index. Keep documents grouped by entity and period where that makes review easier, and label drafts, corrected versions, and final statements clearly.

Use ordinary names that explain contents, such as “Operating account statement – March 2026” or “Payroll summary – second pay period, April.” Avoid vague labels such as “scan 4” or “new file.” If a document replaces an earlier version, note that it is corrected and retain the original only where the business’s recordkeeping process calls for it. Do not silently overwrite a file that someone may already have reviewed.

Before sharing, check that files open, pages are readable, and date ranges are complete. Confirm that a spreadsheet includes the relevant tabs and that formulas or filters have not hidden material rows. For a bank statement, check that opening and closing balances and all pages are present. For a processor report, confirm it covers the settlement period needed to explain the deposits.

Preserve original records in a business-controlled repository where practical. Share the smallest useful set for the first period, then add material in response to specific questions. This reduces confusion and limits unnecessary exposure of personal or confidential information. Ask how access to the shared location can be reviewed or removed if the engagement changes.

How can you prepare for a clean first month?

A compact kickoff can turn a pile of files into an actionable starting plan. Use the following sequence to check readiness:

1. Confirm the entity and date range. Make sure the bookkeeping file, bank accounts, payroll, and source records refer to the same business and period.
2. Agree on the boundary. Write down recurring tasks, historical cleanup needs, exclusions, expected outputs, and any deadlines.
3. Review access. Confirm who owns each system, what permissions are necessary, and which approvals remain with the business.
4. Match records to accounts. For each bank or card account, identify statements supplied, the last reconciled period, and the first period to be worked.
5. Explain transaction patterns. Note revenue channels, processor settlement timing, transfers, loans, owner activity, and unusual transactions.
6. Assign questions. Give each unresolved item an owner, a source to check, and a next action.
7. Set the reporting cadence. Agree when records arrive, how questions are handled, and when reports can reasonably be reviewed.
8. Review the first cycle. After the first month, record what was missing, what caused delay, and what should change in the handoff routine.

Consider a business with two bank accounts, one card, and a payment processor. The owner supplies the bank statements and sees that the processor’s weekly payouts do not match the sales report totals. Instead of labeling the difference as a bookkeeping error, the owner provides the settlement report, which shows fees and refunds deducted before payout. The open-items log records the dates and any remaining mismatch. The bookkeeper can then compare like periods and identify whether timing, fees, or missing information explains the difference.

Now consider a business that has recently opened a second bank account. The old bookkeeping file contains transactions from the original account, but the new statements start halfway through a month. The handoff should identify the account’s opening date, the business purpose, the owner who can grant access, and whether any funds were transferred from the original account. It should also state which transactions remain unclassified. This prevents the first review from treating a transfer as new revenue or assuming the account existed for the full month.

Which onboarding choices can create avoidable confusion?

• Sending every file without an index. A large volume of unsorted records can hide the few documents needed to start. Begin with the agreed period and add records as questions arise.
• Calling a balance final when it has not been reconciled. Label the status and identify the last completed review period.
• Sharing credentials instead of granting access. Use designated users and scoped permissions whenever possible; keep authentication codes private.
• Mixing entities or personal transactions without explanation. State which business owns an account and identify known owner activity separately.
• Assuming a tax return proves the books are complete. Supply it as context, but reconcile the relevant bookkeeping records and confirm any differences.
• Giving a deadline without naming the needed inputs. List the statements, approvals, and answers required to support that date.
• Asking for tracking detail without a consistent source. First decide how tags will be captured and who will maintain them.
• Leaving questions in several places. Keep one open-items log so the team can see status, ownership, and next steps.

These issues do not mean a business must delay onboarding until its records are flawless. They mean the handoff should distinguish verified facts from estimates, missing evidence, and decisions that still need an owner.

What should you confirm with a bookkeeping provider?

Use the first conversation to test whether the proposed process fits the business. Ask which entities and periods are covered, how historical cleanup is scoped, what source records must be supplied, and what the business must do each month. Confirm who will answer questions, how exceptions are escalated, and what reports are expected. Ask how the provider handles incomplete statements or unclear transactions and whether the work pauses, proceeds with disclosed gaps, or follows another agreed approach.

Clarify the boundary between bookkeeping and related services. A bookkeeping engagement may help organize records and prepare a dependable base for tax work, but this does not automatically mean corporate income-tax returns will be prepared or filed. Confirm who is responsible for tax preparation, payroll administration, sales-tax filings, payment approvals, and financial decisions. Put the division of responsibilities in writing so each party knows what remains with the business.

If the business uses several financial tools, list them and ask how the proposed workflow will use the available data. Function describes a connected, service-assisted financial workflow and publishes examples including QuickBooks, Stripe, Gusto, Bill, Ramp, and Brex. That does not establish that every integration, account, or process applies to every engagement. The platform overview can provide background; verify the specific tools and responsibilities that fit your setup.

Pricing and scope should be compared on the same basis. Advertised starting prices may be subject to expense limits, eligibility, billing terms, onboarding fees, or a minimum commitment. Custom cleanup or multi-entity work may need separate discussion. The pricing page describes public options, but the actual order and engagement terms control the work. Do not treat any starting figure as a universal quote.

For additional context about the firm and its services, read the About Function page. For an unresolved scope or handoff question, the contact page is the appropriate place to ask about a conversation. A clear discussion should result in a shared list of responsibilities, needed access, first-period records, and open questions.

What questions should you ask at kickoff?

• Which entities, accounts, and periods are included in the proposed work?
• What cleanup is included, and what requires a separate scope?
• Which reports will be delivered, on what schedule, and with what treatment of unresolved items?
• Who supplies bank, card, processor, payroll, and invoice records, and by what date?
• Which system permissions are required, and which payment or administrative actions remain with the business?
• Who resolves unclear transactions, and where will answers and supporting documents be recorded?
• How are payroll, tax preparation, tax filings, and sales-tax responsibilities divided?
• How should the team handle late records or a transaction that cannot be confirmed?
• What should be reviewed after the first close to improve the next month’s process?

Write down the answers and circulate the agreed version to everyone who owns a task. This reduces the risk that an employee assumes the bookkeeper will upload a statement, while the bookkeeper assumes the business will do it. Update the list when systems, staff, entities, or responsibilities change.

Frequently asked questions

Do my books need to be perfect before onboarding?

No. Share what exists and identify what is incomplete, uncertain, or unreconciled. Ask whether historical cleanup is included, how it will be scoped, and what can begin while older questions remain open.

How far back should I provide records?

That depends on the first period of work, opening balances, and the last reconciled month. Provide the current file and the records needed for the agreed starting period, then disclose older gaps that may affect current balances. Confirm the exact range with the provider.

Should I email passwords or one-time codes?

No. Use system permissions or the approved secure access process. Do not send passwords or authentication codes through ordinary email or chat, and review access when responsibilities change.

Is bookkeeping the same as tax preparation?

No. Bookkeeping organizes and records financial activity; tax preparation and filing are distinct responsibilities that should be confirmed separately. Tax-ready records do not mean a tax return has been prepared or filed.

What if I cannot explain a transaction?

Record its date, amount, account, source document, and what you have checked. Assign someone to investigate it and leave the treatment open until there is enough information to support a conclusion.

What is the most useful next step?

Start by listing the entities, systems, first reporting period, and last reconciled month. Gather the essential statements and accounting records, then create an open-items log with an owner for each gap. When the scope and responsibilities are clear, the handoff can support a practical first cycle without pretending that uncertain information is settled.

Talk with Function about your bookkeeping handoff

After the kickoff, review what arrived late, which questions repeated, and whether the reporting schedule gave enough time to resolve them. Use those observations to make the next month’s handoff more consistent.