QuickBooks Online Implementation: Company Setup, Accounts, Banks, and Opening Balances

• Freeze the fiscal year, accounting method, company identity, tax assumptions, cutover date, reporting dimensions, and close ownership before loading operational data.
• Govern account type, detail type, hierarchy, currency, status, and opening-balance treatment as accounting decisions; do not turn a legacy account list into an unquestioned import file.
• Connect each real bank or credit-card account to the intended QuickBooks Online account and choose a download start date that does not overlap imported or manually entered transactions.
• Release only after representative opening balances, transactions, reports, bank-feed review, reconciliation, role access, evidence retention, and rollback steps pass a documented pilot close.

Review the chart of accounts as a reporting model, not a file-conversion artifact. For each proposed account, approve the name, account type, detail type, number if used, parent or subaccount relationship, currency, tax relevance, active status, reporting purpose, source-system mapping, and owner. Current Intuit guidance explains that account type controls where an account appears on the financial statements. A familiar legacy label placed under the wrong type can therefore distort balance-sheet or profit-and-loss presentation even when the imported amount is correct.

Clean the import before loading it. Remove exact duplicates, resolve near-duplicate names, retire unused accounts according to policy, normalize hierarchy, and identify system-created or integration-required accounts. Current Intuit guidance supports importing lists and specifies a list-first order, beginning with the chart of accounts before customers, vendors, employees, classes, locations, products, and services. It also warns that some imports cannot be undone in bulk. Test a small representative file, preserve the source and mapping, review the import screen, and reconcile the resulting record count.

Choose an opening-balance method for every balance-sheet account. Current Intuit guidance defines an opening balance as the real-world balance on the date tracking begins and uses Opening Balance Equity to offset entries. Connected bank and credit-card accounts may derive their starting point from the chosen download date; manually created balance-sheet accounts can accept an amount and As of date; imported chart accounts require their balances separately. If older transactions are later added without adjusting the opening balance, the same money may be counted twice, so involve the accountant before changing that history.

• Reconcile the imported account count, hierarchy, types, inactive state, and currency to the approved mapping workbook.
• Use statements, loan schedules, fixed-asset records, subledgers, and an approved trial balance as evidence for starting values.
• Track unresolved opening balances by account, amount class, owner, evidence, and disposition instead of forcing suspense items closed.
• Do not use Opening Balance Equity as a permanent unexplained bucket; require an accountant-reviewed clearing plan.
• Block duplicate customer, vendor, product, and account records before transactions depend on the wrong master record.

Prepare a bank-connection matrix before anyone signs in to a financial institution. For each checking, savings, credit-card, or other supported account, record the masked bank identity, intended QuickBooks Online account, business owner, connector, start date, statement cycle, opening-balance method, known pending items, and review owner. Current Intuit guidance states that accountants cannot connect a client's bank for them; the client must perform the connection. Never ask the client to send banking credentials or verification codes to an implementation technician.

Select the feed start date against the cutover ledger, not by choosing the largest history window available. Banks provide different download ranges. If the conversion already contains transactions through a date and the feed starts before it, the Pending or For review queue can include overlapping activity. Preserve the imported or manually entered transaction as the accounting record, then match the downloaded item when appropriate. Categorizing the download as new when the record already exists can duplicate revenue, expense, transfer, payment, or deposit activity.

Run controlled bank-feed tests. Confirm that each bank tile maps to the correct register, that downloaded items remain outside the books until reviewed, that a known existing transaction produces a reasonable match candidate, and that a genuinely new low-risk item can be categorized to the intended account. Test transfers as both sides of one movement, combined deposits against the clearing process, credit-card payments, fees, refunds, and a transaction near the cutoff. Then reconcile the first statement from its opening or beginning balance through a zero difference.

• Use masked account references in tickets and screenshots, and keep statements in the approved evidence repository.
• Prove which date is the last converted transaction and which date is the first bank-feed transaction.
• Review suggested categories and matches; automation is a proposal, not accounting approval.
• Investigate connection errors before disconnecting, because an unsafe reconnect can create duplicate downloads.
• Require a successful statement reconciliation before treating the bank connection as production-ready.

Approve the company identity, subscription, fiscal year, accounting method, tax assumptions, home currency, cutover date, reporting dimensions, bank and integration scope, source populations, close owner, primary admin, and accountant. Record those decisions before loading data so configuration and accounting history are not improvised during import.

No. Review every account's name, type, detail type, number, hierarchy, currency, active state, reporting purpose, and mapping. Remove duplicates and resolve obsolete accounts before import. Because account type affects financial-statement presentation, the accountant should approve the target design rather than accepting legacy labels as sufficient evidence.

Do not assume it does. Current Intuit guidance explains that imported chart accounts need their opening balances entered separately. Define the method by account, preserve the source statement or schedule, reconcile the resulting entry, and have an accountant review any later attempt to add history before the chosen start date.

Choose a date supported by complete source records, preferably aligned to a statement or reporting boundary. State the last date included in the prior system and the first date entered or downloaded in QuickBooks Online. Document timezone, outstanding items, late-clearing transactions, and the bridge between the closing and opening balances.

Use representative opening balances, customers, vendors, income, expenses, bills, payments, transfers, deposits, bank-feed matches, new categorizations, reports, role tests, and a full statement reconciliation. Record expected and actual results, evidence, exceptions, owners, approvals, stop conditions, and rollback steps before broad release.

Lock only after the implementation team and accountant review completeness, reconcile the accounts through the intended date, resolve or accept exceptions, preserve cutover evidence, and confirm who may approve prior-period changes. A lock is a safeguard against later edits; it does not prove the imported balances were correct.

Involve the accountant before choosing accounting method, tax treatment, account types, opening-balance entries, conversion bridges, journal entries, prior-period changes, suspense clearing, or reconciliation adjustments. Technical staff can validate product behavior and evidence flow, but they should not invent accounting treatment for uncertain balances or transactions.