On this page Jump to section
A cash-flow reporting packet should let an owner distinguish recorded cash movements from expectations about what happens next. Assemble the reports, bank evidence, and outstanding questions into a dated package rather than combining everything into one unexplained spreadsheet.
Define what the packet must answer
Ask which company, accounts, currency, and reporting period the owner wants reviewed. Confirm the report settings with the accountant and record them on the cover sheet. A historical report and a forecast have different purposes; label both explicitly if the owner requests both.
Keep the original exports unchanged. Working annotations belong in a separate schedule with references back to those exports. Name files with the period and preparation date so last month's packet cannot be mistaken for the current one.
Assemble a compact evidence set
| Packet component | Preparation detail |
|---|---|
| Report index | Report name, period, settings, and export time |
| Cash account support | Account identifier, statement coverage, and reconciliation status |
| Movement notes | Source references for significant or unexplained changes |
| Forward-looking inputs | Expected receipt or payment dates, source, and owner confirmation |
| Open questions | Specific decision needed, responsible person, and review deadline |
Separate a confirmed bank movement from a customer payment promise. The latter may inform a forecast but does not establish that cash has arrived. Keep transfers between included accounts identifiable so the reviewer can assess their presentation without confusing them with outside receipts.
Example: an expected collection is late
In an illustrative weekly packet, a customer promised payment on Friday but the bank evidence does not yet show receipt. Record the promise, the date checked, and the follow-up owner. Keep the historical report unchanged and identify the uncertain receipt in the forecast inputs.
Do not move the receipt date or mark the item collected simply to make the forecast agree with an earlier expectation. Ask the owner which assumption to use in the next forecast version and retain the prior version.
Review the package before circulation
Check account coverage, dates, filenames, and access to supporting documents. State unresolved reconciliation questions on the cover sheet instead of presenting every figure as final. Keep sensitive account records in the approved storage system and share only with the intended reviewers.
Use the cash-flow supporting schedule for movement details and the scenario input register for assumptions. QBOAssistant can prepare and maintain the package; the owner and accountant interpret the results and approve decisions.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.