How to audit inherited QuickBooks books before building a forecast.
A forecast inherits the books beneath it. Review cash, balances, exceptions, and the reporting story first. Then decide whether the numbers are ready to model.
Do not model a file until you know what is true in it.
Inherited books can produce a tidy P&L and still be unreliable. Unreconciled cash, aging that no longer reflects collection reality, stale balance-sheet accounts, and unresolved prior-period entries all flow straight into a forecast or board pack if nobody stops to investigate.
The first job is not to make the spreadsheet more sophisticated. It is to audit the close, find the exceptions, and establish the starting numbers you are willing to stand behind.
Start with the accounts that can quietly distort every later decision.
Cash and reconciliations
Confirm what has been reconciled, which statements exist, and whether the ledger balance can be explained by the available evidence.
Receivables and payables
Review aging for old balances, unapplied activity, duplicates, and amounts that need a collection or vendor decision rather than another report.
Balance-sheet accounts
Look for accounts that drifted, flipped sign, stopped clearing, or no longer have an owner and supporting schedule.
Period movement
Compare periods and trace unusual movements to the transactions behind them before treating a variance as an operating result.
Audit first. Model second. Explain third.
- 1. Establish the close boundary. Identify the period being relied on, the last issued package, and what support is available for the accounts that matter.
- 2. Pull the core reports. Review the P&L, balance sheet, trial balance, general ledger, AR aging, and AP aging as the starting set, then follow the exceptions.
- 3. Separate a question from a correction. Some issues need an answer from the client. Some need accounting treatment. Some are simply a report that needs to be saved before work continues.
- 4. Propose the work, then review it. Numbers Game can organize the exception and propose accounting work. A person decides the treatment and approves any write before it reaches the ledger.
- 5. Model only from the checked result. Once the team can explain the starting balances and material movements, use the books for a forecast, cash view, budget comparison, or board pack.
Three shortcuts that make an inherited file more dangerous.
Do not reconcile against a missing statement
A GL-only review can be useful, but it is not a bank reconciliation. Name the evidence that is missing rather than letting a report imply certainty.
Do not use a trailing report as last month’s issued pack
A report pulled today cannot show whether the version sent last month was later restated. Save the issued package if the comparison matters.
Do not let a forecast paper over exceptions
A model can make uncertainty look organised. If the books are not ready, the responsible answer is to identify the gap before producing a confident forecast.
Use Claude to investigate the file. Keep judgment with the firm.
Numbers Game gives Claude approved access to the QuickBooks Online and Xero companies a firm is authorized to manage. It can retrieve reports and activity, compare periods, surface exceptions, and prepare the work needed for review.
It does not turn an inherited file into a reliable one by assertion. The accountant, controller, or fractional CFO still decides whether the evidence is sufficient, what treatment is appropriate, and whether any proposed write should be approved.
Inherited QuickBooks books, answered directly.
Once the books hold up, use them for the next question.
Budget versus actual in Claude
Compare a checked close with the budget and focus on the variance that needs a conversation.
Deferred-revenue schedules for QBO Advanced
Build a forward revenue waterfall and tie it back to the balance sheet.
Claude for accounting firms
See how Numbers Game scopes client books and keeps proposed writes under human approval.
Audit the starting numbers before you advise from them.
Bring one inherited client file to a walkthrough and work through the review sequence your team would actually use.