QuickBooks Month-End Review
Use this QuickBooks month-end review to check reconciliations, VAT treatment, documents, open items, and reporting readiness before sign-off.
- A QuickBooks month-end review should happen after processing but before management relies on the reports.
- The review should test reconciliations, VAT codes, documents, old balances, and unresolved exceptions.
- A month should not be treated as closed if old items remain unexplained or source support cannot be traced.
- The review is strongest when exceptions are logged with owners instead of hidden inside the file.
QuickBooks month-end review matters because processing activity is not the same as a closed month. A South African SME may have bank feeds, matched transactions, and invoices inside QuickBooks, but the file still needs review before management, VAT work, or accounting handoff can rely on the numbers.
The month-end review is the control step between activity and trust.
If the review is skipped, small issues become recurring issues. Old bank items, unclear VAT codes, missing supplier invoices, and weak customer allocations may stay hidden until the next SARS deadline or year-end request.
What the QuickBooks month-end review should prove
The review should answer six practical questions:
- Are the bank and payment accounts reconciled?
- Are the main customer and supplier balances explainable?
- Are VAT-sensitive transactions supported and coded properly?
- Are missing documents visible?
- Are open items assigned to someone?
- Can the month be used for reporting without another quiet cleanup?
If the answer to the last question is "not yet", the file should not be treated as closed.
A simple month-end review table
| Review area | What to test | Result needed |
|---|---|---|
| Bank | Statement and QuickBooks balances agree | Reconciled or exception logged |
| Customers | Receipts and debtor balances make sense | Old items explained |
| Suppliers | Bills and payments are complete | Missing invoices listed |
| VAT | Tax codes and support are reviewed | VAT report can be supported |
| Documents | Evidence is attached or stored clearly | Gaps assigned |
| Reporting | Reports reflect reviewed balances | Month can be used or qualified |
The table is deliberately simple. The discipline is in doing it every month.
Step 1: Confirm processing completeness
Start by confirming that the transaction set is complete enough for review.
Check:
- bank and card feeds have updated
- imported transactions have not duplicated feed activity
- customer invoices and receipts are captured
- supplier bills and payments are captured
- payroll or journal entries that affect the month have been posted
If processing is incomplete, review cannot solve the problem. The file first needs a complete transaction base.
Step 2: Review bank and payment reconciliations
QuickBooks can help match transactions, but the reviewer still needs to confirm whether the month agrees to external support.
Review:
- bank account balances against statements
- card or payment gateway clearing balances
- transfers between accounts
- old unmatched or excluded items
- manually imported transactions
Do not normalize old unmatched items. If they remain unresolved, they should appear in the open-item register.
Step 3: Review customer and supplier balances
Customer and supplier reports can look tidy while allocations are still weak.
For customers, check:
- receipts sitting unallocated
- duplicate customer accounts
- credit notes or write-offs without explanation
- old balances outside normal trading terms
For suppliers, check:
- unpaid bills that may already have been settled
- missing supplier invoices
- duplicate supplier records
- payments posted without enough source support
These checks protect both cash visibility and year-end handoff.
Step 4: Review VAT treatment
VAT should be reviewed before filing pressure starts.
| VAT item | Review action |
|---|---|
| Sales VAT | Check output VAT treatment against sales type |
| Supplier VAT | Confirm input VAT is backed by valid support |
| Exclusions | Review no-VAT or exempt treatment for reasonableness |
| Credit notes | Confirm adjustment support exists |
| VAT control | Compare the report to the bookkeeping review |
Use the VAT reconciliation checklist when VAT differences are the main issue. QuickBooks can produce VAT reports, but the business still needs to support the treatment.
Step 5: Check document support
The month-end review should expose missing evidence before it becomes a deadline problem.
Ask:
- can major supplier costs be traced?
- are unusual expenses explained?
- are customer credit notes supported?
- are owner or director transactions documented?
- can the accountant or SARS reviewer follow the record trail?
If the answer is no, record the gap. Do not mark the month clean just because the transaction is posted.
Step 6: Build an exception note
The reviewer should leave a short note for the month.
It should include:
- the period reviewed
- the bank accounts reconciled
- the main unresolved items
- who owns each item
- whether reports can be used without qualification
This does not need to become a long report. It needs to be specific enough that the next review does not start from memory.
QuickBooks month-end exception register
Use a small register:
| Exception | Account affected | Owner | Blocks sign-off? |
|---|---|---|---|
| Missing supplier invoice | |||
| Old bank item | |||
| VAT code query | |||
| Customer allocation issue |
This helps management see whether the month is improving. If the same exception appears repeatedly, the business has a process problem, not only a bookkeeping task.
Red flags before sign-off
Do not treat the month as closed if:
- the bank does not reconcile
- VAT-sensitive items have no support
- reports depend on unexplained balances
- old customer or supplier items keep rolling forward
- open items have no owner
- the reviewer cannot explain the main balances
Those are signs that the file still needs work before it supports decisions.
How QuickBooks review supports the wider close
QuickBooks month-end review should sit inside the wider month-end bookkeeping checklist.
The wider close asks whether the business has current records, clean reconciliations, complete support, and visible open items. The QuickBooks review applies those same controls inside the platform.
That matters because software-specific activity can distract from the real question: can the business rely on the month?
When the review finds repeated problems
Repeated problems should trigger workflow changes.
Examples include:
- bank feeds that are never checked against statements
- the same VAT coding errors every month
- missing support arriving after reports are sent
- customer and supplier balances nobody owns
- a chart of accounts that keeps creating vague categories
At that point, use the QuickBooks bookkeeping checklist and QuickBooks setup checklist together. One checks the live month. The other tests whether the underlying setup still supports the business.
Management report checks after review
Once the review is complete, reports should still be checked for reasonableness before they are sent out.
The reviewer should scan:
- revenue movements that do not match the owner's understanding of the month
- expense categories that have unusual spikes or missing recurring costs
- debtor balances that do not match expected collections
- supplier balances that may include missing invoices or duplicated bills
- VAT, loan, payroll, or owner balances that need explanation
- profit or cash movements that depend on unresolved exceptions
This step is not about rewriting the bookkeeping. It is about deciding whether the report should be issued cleanly, issued with notes, or held back until a blocking item is fixed.
How to compare one month to the next
A good QuickBooks review should make each month easier than the last. If the same questions keep appearing, the business is not learning from the review.
Use a simple trend check:
| Review signal | Improving month | Problem month |
|---|---|---|
| Bank differences | Fewer old items remain | Differences roll forward again |
| Missing documents | Gaps are smaller and named early | Documents are chased after reports |
| VAT review | Codes are consistent | VAT treatment needs repeated repair |
| Balances | Old items are resolved or explained | Ageing reports keep carrying unknowns |
| Reporting | Reports need fewer notes | Management still distrusts the file |
If the problem month pattern repeats, the business should review the process behind QuickBooks. The issue may be document timing, unclear ownership, weak setup, or a bookkeeping scope that is too light for the volume of work.
Who should receive the review note
The review note should go to the people who can act on it. That usually includes the owner or finance lead, the bookkeeper, and the accountant or advisor where accounting or VAT work depends on the month.
The note should be short:
- month reviewed
- accounts reconciled
- key report concerns
- open items and owners
- sign-off status
This keeps the review practical. It also stops month-end knowledge from staying hidden inside the software file.
How this page should be used
Use this review with:
- monthly bookkeeping services
- QuickBooks bookkeeping checklist
- QuickBooks setup checklist
- bookkeeping software support
The right outcome is a clear month-end decision: ready, ready with exceptions, or not ready yet.