QuickBooks Online Month-End Workflow: Reconcile, Review, and Close
A QuickBooks Online month-end workflow turns recorded transactions into a reviewed set of financial reports. Set the reporting scope, reconcile supporting detail, document corrections, and approve the package before protecting the closed period.
Define the close before opening reports
Record the company, period-end date, reporting basis, currency, preparer, reviewer, and deadline. Keep that scope consistent across every report. A receivables report at one date cannot explain a balance sheet from another date. A cash-basis profit and loss report also answers a different timing question from an accrual-basis report.
This is a software-focused companion to the Month-End Close Checklist. Use that checklist for the broader close process. Product menus and access depend on your QuickBooks version, country, and role; use the current Intuit documentation for account-specific controls.
Use a deliberate sequence
| Stage | Work in or around QuickBooks | Evidence to retain |
|---|---|---|
| 1. Complete | Collect source documents and review transactions through cutoff | Missing-document list and cutoff review |
| 2. Reconcile | Reconcile bank and card accounts to statements | Statement, reconciliation, and outstanding-item review |
| 3. Tie detail | Review receivables, payables, and other account schedules | Same-date supporting schedules tied to the ledger |
| 4. Adjust | Record supported, approved corrections and accruals | Calculation, explanation, support, and approval |
| 5. Review | Evaluate final reports and unusual movements | Reviewer notes and resolved questions |
| 6. Close | Approve the package and apply appropriate closing controls | Final report version and post-close change process |
Review the bank feed, then reconcile
Confirm each downloaded item represents a real event and has the right treatment. Match transactions already recorded so they are not added twice. Review transfers, loan activity, owner transactions, and net processor deposits carefully. A recognizable bank description is not sufficient evidence of the accounting classification.
In the reconciliation workflow, select the correct account and use the statement ending date and balance. Check the beginning balance before selecting cleared transactions. Investigate differences and unexpected changes to previously reconciled items. Do not create an unexplained expense simply to make the difference disappear.
Worked example: two sides of a reconciliation
An original illustration: the statement ends at 12,400. There is a 900 deposit in transit and 1,100 of outstanding checks. The bank-side adjusted balance is 12,400 + 900 − 1,100 = 12,200.
QuickBooks shows 12,250 before a 50 bank fee has been entered. Record the supported fee in the appropriate period and account. The adjusted book balance is 12,250 − 50 = 12,200. Both sides now agree. Outstanding checks and deposits in transit are already recorded book items; do not enter them again merely because they have not cleared.
The mathematical agreement is only one control. Inspect the age and validity of outstanding items and confirm that the bank account belongs to the company. A reconciliation can balance while an expense is coded to the wrong account.
Tie receivables and payables to the ledger
Run the relevant customer and vendor balance or aging detail at the same cutoff and suitable reporting basis as the balance sheet. Check unapplied payments, credits, negative balances, old items, and transactions posted directly to control accounts. Explain differences instead of assuming the report titles mean their scope is identical.
For example, a balance sheet shows accounts receivable of 8,700, but customer detail shows 8,200. The unexplained 500 is a reconciliation exception. Check report dates, filters, basis, and direct ledger postings before deciding what correction is appropriate. Do not simply add 500 to the customer report or write off a customer balance to force agreement.
Review the rest of the balance sheet
Use schedules appropriate to the business for prepayments, fixed assets, loans, deposits, payroll liabilities, taxes, and other material balances. A bank reconciliation does not establish whether these accounts are correct. Assess cutoff for services received but not billed, costs paid in advance, and revenue-related obligations using the applicable accounting policy.
Every proposed adjustment needs a business explanation, supporting calculation, accounts, date, and reviewer. Confirm the effect on reports after posting it. Do not replace normal customer or vendor transaction workflows with journal entries merely because they seem faster.
Approve reports and control later changes
Review the balance sheet, profit and loss, cash-flow reporting, and relevant detail together. Investigate unexpected variances, unusual negative balances, suspense accounts, and transactions that lack support. Save a dated final package with the company and period clearly identified; verify those details before sending it.
After review and approval, authorized administrators can use available closing-date controls. Intuit documents an Exceptions to Closing Date report for identifying subsequent changes. A closing date is not an immutable lock: define who can approve corrections, how changed reports are identified, and when a revised package must be issued. Use the audit log as part of investigating who changed a transaction and what changed.
Frequently asked questions
Does an empty bank feed mean the month is closed?
No. You still need statement reconciliations, account support, cutoff checks, adjustments, and report review.
Should I adjust every reconciliation difference to an expense?
No. Investigate the cause. Only record a correction when the underlying event and accounting treatment are supported.
Why can receivable detail differ from the balance sheet?
Different dates, basis, filters, unapplied items, or direct control-account postings can contribute. Reconcile the scopes before correcting records.
Can reports change after a closing date is set?
They can if authorized changes occur. Use an approval process, applicable exception reporting, and audit history to identify and review them.
Sources and further learning
Official documentation reviewed November 3, 2026. Worked examples, learning sequences, and practice answers are original teaching illustrations. Product interfaces and availability can vary by version, platform, plan, and region.