13-Week Cash Forecast Downloads

The Owner Hotline · with Huumans · November 12, 2026

Build your 13-week cash forecast with AI

Everything from today’s demo: the sample QuickBooks reports for Smith Automotive and the exact prompt we used. Try it on the sample first, then run it on your own numbers.

Free · No sign-up · Works in Claude with file uploads

How to Use It

Three steps, about ten minutes.

You don’t need any AI experience. You need five reports from QuickBooks and a Claude account.

1. Get the five reports

Use the sample files in the download, or run these from your own QuickBooks Online, all as of the same date, and export them to Excel:

  • Balance Sheet
  • A/R Aging Detail
  • A/P Aging Detail
  • Transaction List by Date, filtered to your bank account, for the last 90 days
  • Profit and Loss by Month, accrual basis, for the last 12 months

2. Attach them in Claude and paste the prompt

Start a new chat, attach the five files, and paste the prompt below. Change the “About my business” details to your own: your minimum cash level, how often you file GST/HST, and any big payments you know are coming. Claude builds an Excel workbook and a two-page PDF summary you can hand to your banker. It takes a few minutes.

3. Check it, then keep it current

Start with the Data checks and Assumptions tabs: they show what Claude found in your books and what it had to estimate. Every number in the workbook is a formula you can trace. Run it again each week with fresh reports, and take the data checks to your bookkeeper.

Smith Automotive Inc. is a fictional auto repair and tire shop. Every name and number in the sample files is made up.

Before You Connect Anything

Downloads first. Connectors with care.

You can skip the downloads by connecting Claude straight to QuickBooks. Two things to know first. Intuit’s standard connector is US-only today and can’t read your bills or bank transactions, so it can’t build this forecast. The more capable connectors can, but the same access that reads your reports can also send invoices, void transactions and change your books.

That’s why the prompt tells Claude to read only. Keep that line in, and check what any connector can do before you switch it on.

The Prompt

Copy it, paste it, change the details.

The “About my business” section is filled in for Smith Automotive so the sample works straight away. Replace it with your own details before you run it on your books.

## About my business (example: replace with your own details) - Business name: Smith Automotive Inc. - My QuickBooks reports run to (the last day my books are up to date): November 8, 2026 - Forecast starts on (the Monday after that): November 9, 2026 - Minimum cash I want in the bank at all times: $40,000 - Sales tax: Ontario HST, 13%, filed quarterly - Card and POS sales reach my bank: the Monday after each sales week - Sales growth to assume: 0% (sales follow last year's pattern) - Big payments I know are coming (exact date, amount, what): January 15, 2027, $14,800, garage insurance renewal (Ridgeway Insurance Brokers); December 31, 2026, $6,000, corporate income tax instalment - Anything else you should know (a customer who won't pay, a loan ending, a price increase): none ## What I need Build me a 13-week cash flow forecast from the attached QuickBooks reports: an Excel workbook I can work in, and a PDF summary I can share. I want to know which week my cash is lowest, whether it drops below my minimum, which payment causes it, and what I can do about it, cheapest options first. Attached reports (from QuickBooks Online, as of the same date): 1. Balance Sheet 2. A/R Aging Detail (what customers owe me) 3. A/P Aging Detail (bills I owe) 4. Bank transaction list for the last 90 days (Transaction List by Date, filtered to my bank account) 5. Profit and Loss by Month, accrual basis, last 12 months or more *(If you are connected to my QuickBooks instead, run these same five reports yourself, all as of the date in "About my business", not today's date. The bank list covers the 90 days up to that date.)* ## Ground rules - Use only the numbers in the reports and the details I gave above. - **Follow the method below exactly, every time.** It is written so that the same reports always give the same forecast. Where it gives a rule, use that rule even if you think another approach is better; put your suggestion in Data checks instead. Never add a cash item, lever or adjustment the method doesn't ask for. - Do not do arithmetic in your head: build the workbook with formulas so every number can be checked. - If you are connected to my QuickBooks instead of reading files: **read only**. Do not create, change, send or delete anything, and do not use any lending or loan tools. - Do not recommend a specific lender, loan or financial product. If financing might be needed, say "talk to your accountant or lender" and stop there. ## How to build the forecast (fixed method) **Data checks first.** In a "Data checks" tab, list: invoices more than 90 days past due; suppliers paid regularly from the bank who have no bills in A/P; anything that looks duplicated or odd; and any place where the method below didn't fit my data. Tell me about these first, in plain words. Data checks never change the numbers. Then build each cash line with these rules. "The bank list" means the 90-day bank transaction list. Dates are calendar dates; a week runs Monday to Sunday; week 1 starts on the forecast start date. 1. **Opening cash** = the total of the bank accounts on the Balance Sheet. 2. **Monthly sales** = Total Income for the same month last year in the P&L by Month, times (1 + the growth % above). For the month the forecast starts in, subtract the Total Income already recorded this month. Spread each month's remaining sales evenly over its remaining days (from the forecast start date, or the 1st of later months). 3. **Paid-on-the-spot share** = card/POS deposits in the bank list for the last two complete calendar months before the report date, divided by (Total Income for those two months × (1 + tax rate)). Invoiced share = 1 minus that. Use these two shares for every month. 4. **Sales paid on the spot**: for each sales week, add up that week's daily sales × paid-on-the-spot share × (1 + tax rate). The cash arrives on the day given above (for "the Monday after each sales week", the following Monday). Sales from before the forecast start are already in the bank. 5. **Customer payment terms and days to pay**: terms = due date minus invoice date on that customer's open invoices in the A/R Aging Detail. Days to pay = the larger of (a) the terms and (b) the age of the customer's oldest open invoice on the report date, **plus 7 days**. Round to whole days. (They haven't paid the oldest invoice yet, so assume at least another week.) 6. **Doubtful invoices**: an open invoice more than 90 days past due, or any past-due invoice from a customer with no payment in the bank list. Leave them out of the forecast. 7. **Open customer invoices**: each arrives on its invoice date plus that customer's days to pay. 8. **Future customer invoices**: for each week, that week's sales × invoiced share × (1 + tax rate), split across customers in proportion to their open A/R balances (doubtful invoices excluded). Each is dated the Wednesday of the sales week and arrives that many days to pay later. Keep rows that land after week 13 in the Detail tab; they just aren't counted. 9. **Bills in A/P**: each paid on its due date. Overdue bills: paid on the forecast start date. 10. **Regular payments** (payroll, remittances, rent, leases, loan payments, utilities, software, fees, owner draws, and suppliers paid without bills): a payee paid at least twice in the bank list at a steady interval. Amount = the average of its last three payments (or all of them if fewer). Cadence = the usual gap, rounded to weekly, every two weeks or monthly. Next dates = continue from the last payment on that cadence (monthly: same day of the month). If one payee has different kinds of payment (the Receiver General's payroll remittances, sales tax and income tax; a bank's loan payment and service charge; a payroll company's net pay and its fee), split them by memo and treat each as its own payee. Use the exact dates; don't move a date that falls on a weekend. A payee paid once is regular only if the P&L by Month shows the same expense every third month; then it is quarterly, three months after the last payment. Don't add a regular payment for a cost that's already a bill in A/P for the same period. 11. **Monthly supplier statements** (a supplier paid around the same day each month for the last three months whose memo or bills show it sends a statement, whether paid by bill payment or straight from the bank; these go in the "Suppliers not yet billed" row, and this rule wins over rule 10): forecast each statement not yet in A/P at the average of the last three payments, paid on the same day of the month as the last payment. Suppliers who bill only now and then: nothing beyond their A/P bills. List them under Data checks as a risk. 12. **Sales tax**: payment = the sales tax balance on the Balance Sheet (it already includes every invoice and bill dated up to the report date, including the bills in A/P), plus tax on forecast sales from the forecast start to the end of the current filing period, minus the tax in supplier costs **dated** from the forecast start to the end of the period. Those costs are the regular payments under rule 10 and the monthly statements under rule 11 for rent, leases, utilities, phone, software, advertising, supplies, parts, payroll service, professional and disposal fees (not wages, remittances, loans, insurance, bank or card fees, owner draws or government payments). A regular payment is dated the day it's paid; a monthly statement is dated the last day of the month it covers, even though it's paid the next month. Tax in a payment = amount × rate ÷ (1 + rate). Paid one month after the period ends. 13. **Known payments** from "About my business": on the exact date and amount given. They replace any matching pattern you found (don't count anything twice). 14. Nothing else. No other annual or irregular items, no growth, no extra purchases. If you think something is missing, put it in Data checks. ## The workbook (Excel, .xlsx) Use exactly these tabs, in this order: - **Summary** (first tab, prints on one landscape page): my one-page cash flow summary. Full spec below. - **Assumptions**: business name, forecast start date, opening cash, minimum cash, GST/HST rate and frequency, scenario settings (delay weeks = 3; downside sales cut = 15%). Every other tab refers to these cells. - **Detail**: one row per expected cash item. Columns: Category, Description, Source (which report), Expected date, Amount (+ in, − out), Confidence (High/Medium/Low), Week (formula from date and start date), Week if delayed (formula: +delay weeks for the two largest customer receipts), Amount in downside (formula: cuts on-the-spot sales by the downside %). - **Forecast**: 13 weekly columns with week-start dates. Rows, in this order: Opening cash; receipts by category (Sales paid on the spot, Open invoices, Future invoices, Other receipts); Total receipts; payments by category (Payroll, Payroll remittances, Bills in A/P, Suppliers not yet billed, Rent and leases, Loan payments, GST/HST, Income tax, Insurance and annual items, Other operating, Owner draws); Total payments; Net cash flow; Closing cash; Minimum cash; Above/(below) minimum. Every amount is a SUMIFS on the Detail tab. Closing cash cells turn red below the minimum. - **Scenarios**: closing cash by week for Base, Delayed (the two largest single customer receipts in weeks 1 to 13, open or future invoices, each 3 weeks later) and Downside (sales paid on the spot × 85%), with the lowest week and lowest balance for each. Add a line chart of the three scenarios against the minimum. - **Levers**: exactly the four levers defined below, each with the dollar effect and the week it helps. Add a row showing closing cash by week with all the cheap levers applied, and a line chart of that against the base forecast and the minimum. - **Data checks**: the problems you found. ### The Summary tab (one page) Write it for an owner, not an accountant: short sentences, no jargon. Top to bottom: 1. **Title**: "[Business name]: 13-week cash flow summary", the forecast period, and the date the reports run to. 2. **Four headline numbers**, as formulas linked to the Forecast tab: opening cash; lowest closing cash and the week it happens; how far above or below my minimum that is; total cash in and total cash out over the 13 weeks. 3. **The chart**: one combined chart by week, with cash in as green columns, cash out as red columns (shown as negatives), closing cash as a dark line, and my minimum as a dashed line. Label the axis in dollars and the weeks by their start date. 4. **What's happening**: three or four plain sentences on why cash moves the way it does, and the one or two payments that cause the low point. 5. **Biggest payments ahead**: the five largest single payments in the 13 weeks (date, who, amount), pulled from the Detail tab. 6. **What you can do, cheapest first**: a small table of the four levers (action, dollar effect, week it helps), ending with the financing line from the Levers tab. 7. **Fix with your bookkeeper**: the top three data checks, one line each. 8. **Footer**: "This is a forecast, not a promise. Update it weekly. Check the Assumptions tab." Set the print area to this content, landscape, fit to one page wide by one page tall. Nothing on this tab may spill onto a second page. The levers, exactly these four, in this order (no others): 1. **Collect overdue invoices**: every past-due invoice that isn't doubtful and is forecast after week 2 arrives in week 2 instead; doubtful invoices are collected in week 3. The dollar effect shown is the doubtful amount (the only new cash); say that the rest is timing only. 2. **Move one supplier payment**: the single largest A/P bill paid in the lowest week moves 4 weeks later. 3. **Pause owner draws**: every owner draw in the 13 weeks is not taken. 4. **Delay spending that can wait**: advertising and professional fees in weeks 5 to 13 move past week 13. Then the financing line: if the lowest closing cash with all four levers is below my minimum, the amount to discuss is the shortfall rounded up to the next $5,000, from the first week below the minimum. Also show the same figure without lever 2. If it isn't below the minimum, say no financing is expected. ## The PDF cash flow summary (portrait, for my banker or advisor) As well as the workbook, give me a PDF I can hand to my banker, lender or advisor: **US Letter, portrait, two pages at most**. It must use exactly the same figures as the workbook. Calculate them in Python from the same Detail rows, and check that the lowest balance, lowest week and 13-week totals match the workbook's Summary before you finish. Use reportlab for the layout and matplotlib for the chart. Keep the design plain and professional: one accent colour, no emoji, and money shown as $12,345. **Page 1: Summary** 1. **Header**: "[Business name]", "13-Week Cash Flow Forecast", the forecast period, and "Prepared [today's date] from QuickBooks reports as of [report date]". 2. **Four key figures in a row**: opening cash; lowest projected balance and its week; position against the minimum cash level; total receipts and total payments over 13 weeks. 3. **The chart**, the full width of the page: by week, receipts as green columns, payments as red columns (negative), the closing balance as a dark line, and the minimum cash level as a dashed line. Week start dates go on the x-axis and dollars on the y-axis, with a legend. 4. **Commentary**: four to six sentences in a measured, factual tone, suitable for a lender. Cover the seasonal pattern, the main receipts and the main payments that drive the low point, and when it occurs. 5. **Planned actions**: a short table of the four levers from the workbook (action, amount, timing), and the resulting low point if they are all taken. End with one sentence giving the financing line from the Levers tab. Leave it out if none is needed. **Page 2: Detail** 6. **Weekly cash flow table**: one row per week (week starting, opening balance, receipts, payments, net cash flow, closing balance), with a totals row. Highlight in light red any week that closes below the minimum. 7. **Largest scheduled payments**: the five largest single payments (date, payee, amount). 8. **Key assumptions**: five or six bullets covering sales basis, customer payment timing, sales tax, payroll, supplier statements, and the known payments I gave you. 9. **Sensitivity**: one line each for the Delayed and Downside scenarios (lowest balance and week). 10. **Footer on both pages**: "Unaudited management forecast prepared from QuickBooks Online reports. Actual results will differ. Page X of 2." Leave out the data-quality issues for my bookkeeper. They belong in the workbook, not in a document for a lender. ## What to tell me in the chat Keep it to a few lines: the lowest week, the lowest balance against my minimum, the main cause, and "open the Summary tab first; the PDF is ready to share." Then list any assumptions I should double-check. Everything else belongs in the workbook and the PDF.

Same Answer Every Time

Want the math done by code? Use the skill.

A prompt asks Claude to work out your forecast, and two runs can come out a little different. The skill hands every calculation to a Python script that follows one written method, so the same reports always give the same forecast, to the cent. Claude collects your reports and your details, runs it, and explains the result.

1. Download the skill

One zip file. Inside: the instructions for Claude, the Python scripts, and the method written out in plain English, so you (or your accountant) can see exactly how every number is worked out.

2. Add it to Claude

In Claude’s settings, find Skills and upload the zip as it is. Code execution needs to be turned on.

3. Attach your five reports and ask

Start a new chat, attach the same five QuickBooks Online reports, and ask for a 13-week cash forecast. Claude asks for your details once (minimum cash, sales tax, big payments coming), then gives you the Excel workbook and the two-page PDF.

Download the skill (.zip)

Try it on the Smith Automotive sample reports first. Built for QuickBooks Online exports. It reads your reports and never changes your books.

Exercise 2

Match every bank line to its receipt.

Claude reads your bank statement, searches your email and Google Drive for the invoice or receipt behind each payment, saves a copy, and gives your bookkeeper one spreadsheet: every line coded, with the tax split out and the paperwork status marked. Anything it isn’t sure about, it asks you first.

1. Set up a working folder

This one runs in Cowork in the Claude desktop app, because it saves files. Choose a folder and put two things in it:

  • your bank statement (PDF) for one month
  • your chart of accounts, exported from QuickBooks to Excel

If you have a coding rules file from last month, add that too. If not, Claude starts one.

2. Connect your own Gmail and Google Drive

Turn on the Gmail and Google Drive connectors. The prompt tells Claude to read only: it never sends, moves or deletes anything. One limit to know: the Gmail connector can read an email but can’t download its attachments, so those lines are marked “Attachment to download” with a link to the email.

3. Paste the prompt and answer its questions

Change the “About my business” details to your own. Claude asks all its questions in one list. Your answers are saved as coding rules, so next month it asks less.

Download the sample files (.zip)

Smith Automotive’s sample bank statement, chart of accounts and coding rules, plus the finished spreadsheet from our test run, so you can see what you’ll get. The sample inbox isn’t included: connect your own.

## About my business (example: replace with your own details) - Business name: Smith Automotive Inc. - Bank statement to work on: Northern Credit Union, Business Chequing 4417, October 2026 (in the working folder) - Sales tax: Ontario HST 13%. Financial services, insurance, payroll and government payments have no HST. - Where my paperwork lives: Gmail (receipts and invoices emailed to me) and the Google Drive folders "Receipts" and "Agreements" - My chart of accounts: "Smith Automotive - Chart of Accounts.xlsx" in the working folder - My coding rules from last time: "Smith Automotive - Coding Rules.xlsx" in the working folder (if there isn't one, start a new one) ## What I need Go through every line on my bank statement, find the paperwork that supports it, save a copy in my working folder, and give me one Excel spreadsheet my bookkeeper can work from. Each line needs a reference number, the account it should be coded to, the tax, and whether we have the paperwork. ## Ground rules - **Read only in my email and Drive.** Never send, reply, forward, delete, archive, label or move anything. Never create anything in Gmail or Drive. - Save files only in my working folder. - Don't guess. If you're not sure what something is or how to code it, propose an answer and ask me. Ask all your questions together, once, not one at a time. - Never invent a document, a vendor, an amount or a tax number. If you can't find the paperwork, say so. ## How to do it 1. **Read the statement.** List every line with its date, description and amount. Give each line a reference: the year and month, then a two-digit line number (for example 2610-01, 2610-02). Check that the opening balance plus deposits minus withdrawals equals the closing balance before you go on. 2. **Apply my coding rules.** For each line whose description matches a rule, use that rule's vendor, account, tax treatment and the place it says the paperwork is. 3. **Find the paperwork for each withdrawal.** Search Gmail and then Google Drive. Use the vendor name (and short versions of it), the exact amount (with and without the comma and dollar sign), and dates from about 30 days before the bank date to 5 days after. A match needs the right vendor and the right amount. A date alone isn't enough. Ignore quotes, newsletters and anything that isn't a bill, invoice, statement or receipt. - Deposits don't need a receipt. Identify who paid (from the description) and code customer payments to Accounts Receivable and card settlements to sales. - Some lines never have an invoice: bank fees (the statement is the record), rent or leases paid under an agreement, loan payments and transfers. Say which document covers them (for example the lease schedule in Drive), or that none is needed. 4. **Save a copy of each document in the working folder**, in a folder called `Supporting documents/[year-month]/`, named `[reference] [vendor] [amount].pdf`: - **If the document is a file you can download** (for example a PDF in Google Drive), save that file. - **If the email itself is the receipt** (an HTML receipt or e-bill), save the email as a PDF showing who it's from, the date, the subject and the full body. - **If the invoice is an attachment you can't download,** save the email as a PDF anyway, note the attachment's file name, and mark the line "Attachment to download" with a link to the email, so I can grab it in one click. Check Google Drive for a copy first. 5. **Code everything.** Use my coding rules first. For anything new, pick the best account from my chart of accounts, say why in a few words, and set the tax treatment. When a document shows the tax, use that amount; otherwise work it out from the rate. Then **ask me to confirm every new or uncertain item in one list**: reference, date, amount, what you think it is, the account and tax you propose, and why. Wait for my answers before you finish. 6. **Update my coding rules file** with every answer I confirm: the bank description text to match, vendor, account, tax, where the paperwork is, any notes, "Confirmed by" (my name) and today's date. Keep the existing rules. Save it with the same name, so next month you won't need to ask again. ## The spreadsheet (Excel, .xlsx), saved in the working folder Name it `[Business name] - [Bank account] - [Month] - Coded transactions.xlsx`, with these tabs: - **Transactions**: one row per statement line, in statement order. Columns: Reference, Date, Bank description, Money out, Money in, Vendor or payer, Account, Tax treatment, Net amount, Tax, Paperwork status, Document (a clickable link to the saved file), Where found (Gmail, Drive, Bank statement, None), Email link, Notes for the bookkeeper. Paperwork status is one of: **Found and saved**, **Attachment to download**, **No document needed**, **Missing**. Colour-code the status column (green, amber, grey, red). Freeze the header row and add filters. Net plus tax must equal the bank amount on every line. - **Summary**: statement opening and closing balance and the check that they tie; how many lines have each paperwork status; totals by account; total tax paid. - **Missing and to-do**: every line that is Missing or Attachment to download, with what to do about it (who to ask, what to download). - **Coding rules used**: which rule matched each line, and which lines needed my confirmation. ## What to tell me in the chat First, the list of questions in step 5, and nothing else. After I answer: how many lines were matched, how many documents were saved, what's missing or needs downloading, and where the files are. Keep it short.

Exercise 3

Same AI, same numbers, one extra file.

AI reads your numbers well. What it can’t know is the story behind them. A one-page context file changes the advice you get. See it on a sample business first, then build one for your own.

Download the Rivermark sample (.zip)

Rivermark Exteriors is a fictional roofing and siding contractor. Every name and number is made up.

1. Run it cold

Download the sample files. Start a new chat, attach Rivermark - Profit and Loss and Balance Sheet.xlsx, and paste this. Read the answer and keep the chat open.

You're an experienced accountant. I've attached the profit and loss and balance sheet for one of my clients. Give me your analysis of how this business is doing, and tell me what I should be raising with the owner at our next meeting.

2. Run it again, with context

In the same chat, attach Rivermark - Client Context.md and paste exactly the same prompt again.

3. Compare the two answers

The first answer is good. That’s the trap. It sees the strong November and December, the wage jump in April and the line of credit, and it describes them accurately. The second one knows what they mean:

  • The year-end revenue was one hailstorm, not a channel to chase.
  • The April wage jump was a second crew the work never filled.
  • The line of credit always cleared by June. This is the first year it didn’t.
  • The consulting fees go to the owner’s brother-in-law, with no agreement.
  • The owner wants to sell in about five years, and there’s almost no equity.

Ask yourself which answer you’d act on.

4. Build one for your business

Start a new chat and paste this. Answer quickly; bullet fragments are fine. Type “that’s all I have time for” whenever you need to stop. Save what it writes and attach it whenever you ask AI about your business, and share it with your accountant.

You're helping me build a short context document about my business, so AI tools can give me advice that fits how my business actually works. Interview me, one question at a time, waiting for my answer before asking the next. Keep each question short. Don't comment on my answers, just move to the next question. Ask these, in order: 1. What does the business do, what does it sell, and roughly how big is it? 2. What type of entity is it, and when does the fiscal year end? 3. What software do I run, and what doesn't talk to what? 4. What does my year look like: busy season, slow season, cash squeeze? 5. Who does my books and taxes, and what do I do myself? 6. How long have I been in business, and what's changed recently? 7. What am I trying to build, and what worries me? 8. What would a new manager take a year to learn about this business? 9. Which numbers in my books need explaining: one-off events, family on the payroll, unusual deals? 10. What decision have I been putting off? When I've answered them all, or the moment I say "that's all I have time for", write the context document from whatever I've given you, under these headings: Entity and fiscal year; Business model; Software; Seasonal pattern; Who does what; History and recent changes; Goals and worries; Things the numbers don't show; Open decisions; Open questions to confirm. Where I didn't get to a question or my answer was thin, mark that section "unknown: confirm" rather than padding it. Keep it to one page.

Next Step

Want help setting this up for your business?

If you’d like a second pair of eyes on your forecast, or help turning it into a weekly habit with your bookkeeper, book a call.

Book a call

Are you an accountant or bookkeeper? Take the AI Readiness Scorecard.

Presented by Peter McCarroll, The AI Accountant, with Colin Knoll, Huumans.