QuickBooks Setup Checklist

QuickBooks setup checklist matters because a new file can feel clean before the business has tested the monthly controls behind it. In a South African SME, the setup usually has to support bank feeds, VAT treatment, source documents, management reporting, and future accounting handoff from the start.

QuickBooks setup is not only a software task. It is a bookkeeping design task.

If the setup is rushed, the file may still process transactions, but the business can quickly inherit weak opening balances, unclear coding, missing support, and reports that do not answer the owner's questions.

The setup areas to confirm before go-live

1. Business and reporting structure

Confirm the legal entity, trading name, reporting periods, financial year, VAT status, and management reporting needs.

2. Users and permissions

Decide who can process transactions, who can approve changes, who can review reports, and who should have advisor access.

3. Bank feeds and import method

Plan how bank and card activity will enter the file, how duplicate imports will be avoided, and who checks feed completeness.

4. Chart of accounts and coding rules

The account list should match the business model. It should not be copied blindly from an old file if the old file was already messy.

5. VAT settings and tax codes

VAT setup should match the business's registration status and actual transaction types. The setup should support review, not only capture.

6. Documents and month-end workflow

The business needs a rule for where invoices, receipts, approvals, and explanations will live before the first month gets busy.

QuickBooks setup planning table

If one of these rows is vague, the setup is not ready for reliable monthly use.

The pre-setup checklist

Before creating or relying on the file:

1. Confirm the business details and reporting calendar.
2. List every bank, card, payment gateway, and clearing account.
3. Decide which old balances must move into QuickBooks.
4. Review the existing chart of accounts for duplication or weak categories.
5. Confirm VAT registration status and common VAT-sensitive transactions.
6. Decide who owns documents, approvals, and missing support.
7. Agree what the first month-end review must prove.

This is the work that prevents a setup project from becoming a cleanup project.

Opening balances and source records

Opening balances should not be treated as a data-entry detail. They become the base of the new file, so weak balances can create months of follow-up.

Review:

• bank balances at the agreed start date
• customer and supplier balances
• VAT control and recent VAT returns where relevant
• loans, fixed assets, and director or shareholder balances
• old suspense or clearing balances that should not be imported casually

If old balances cannot be explained, log them separately. Do not let unknown history become part of the new file without review.

Bank-feed setup checks

Bank feeds are useful only when they are complete and reviewed.

For each account, confirm:

• whether the account will connect through a feed or import
• who checks that feed activity is complete
• whether historical transactions are being imported
• how duplicate transactions will be identified
• how transfers between accounts will be matched

After connection, compare the QuickBooks balance to the bank statement. A connected feed is not the same as a reconciled account.

VAT setup checks

VAT settings should support the business's actual filing and review process.

Use the VAT reconciliation checklist once the first month is active. Setup only matters if it supports later review.

Document workflow setup

The best QuickBooks setup still fails when documents arrive late or live in scattered inboxes.

Decide:

• where supplier invoices will be stored
• how receipts and card slips will be submitted
• who explains unusual bank transactions
• how approvals are recorded
• how the bookkeeper will know a document is still missing

This workflow should connect to the bookkeeping documents checklist. The accounting file is only as strong as the support behind it.

First-month review checklist

The first month after setup should be reviewed more closely than a normal month-end.

Check:

1. bank feeds or imports are complete
2. opening balances agree to support
3. coding rules are working in practice
4. VAT codes are being used consistently
5. document flow is being followed
6. reports answer the owner's basic questions
7. open items are logged instead of ignored

This is where the business proves that the setup works as a monthly system, not only as a new login.

Common setup mistakes

QuickBooks setup usually goes wrong when the business:

• imports old balances without review
• gives too many users broad access
• leaves VAT settings unchecked
• builds the chart of accounts around convenience instead of reporting
• starts processing before the document workflow is clear
• skips the first-month review

Those mistakes can make the file look active while the control layer remains weak.

When setup should pause for cleanup

Sometimes the safer move is to stop and clean the source records before going live.

Pause the setup if:

• the old bank reconciliation is incomplete
• debtor or creditor balances cannot be explained
• VAT differences are unresolved
• historical owner or loan balances are unclear
• the business cannot identify what should move into the new file

That does not mean QuickBooks is the wrong platform. It means the source records need attention before the platform can help.

Reports to test before handover

Before the setup is treated as complete, test the reports the business will actually use. This prevents a common problem: the system is technically active, but the reports still do not answer the questions management asks every month.

Review at least:

1. profit and loss by the categories management expects
2. balance sheet with bank, VAT, debtor, creditor, loan, and owner balances reviewed
3. customer balances with old items explained
4. supplier balances with missing invoices listed
5. VAT report checked against expected transaction treatment
6. cash report or bank summary that agrees to reconciled accounts

If these reports are weak, the setup is not finished. The issue may be chart-of-accounts design, opening balances, document flow, user behavior, or the way transactions are being coded.

User-role and approval checks

QuickBooks setup should also define practical responsibility. Too much access can create uncontrolled changes. Too little access can slow the month down because the right person cannot complete a task.

Use a simple responsibility table:

The exact roles can differ by business, but the setup should not leave approval and review responsibilities vague.

What should be documented after setup

The handover should leave a short setup note. It does not need to be complicated, but it should help the next reviewer understand the file.

Record:

• the go-live month and cutoff date
• connected bank accounts and any manual import rules
• key opening balances and unresolved old items
• VAT setup assumptions
• document workflow rules
• users with access and their role
• first-month review findings

This prevents the setup knowledge from staying inside one person's memory. It also makes later cleanup, handover, or accounting review easier.

How this page should be used

Use this checklist with:

• QuickBooks bookkeeping checklist
• QuickBooks month-end review
• small-business bookkeeping system checklist
• cloud accounting services

A good QuickBooks setup should leave the business with clearer monthly control, not only a new software file.