How to Run a 13-Week Cash Flow Process for a $2–10M Business

A 13-week cash-flow forecast is a short-horizon operating view of expected cash receipts, cash disbursements, and ending cash by week. It is not a substitute for a budget, a GAAP cash-flow statement, or a long-range plan. Its job is narrower: make the next several weeks visible enough for management to decide what needs attention now.

For a business in the $2M–$10M range, the mechanics are usually less important than the discipline around them. The forecast needs a known starting-cash number, a defensible view of when customers will actually pay, a complete view of committed outflows, an owner for each assumption, and a weekly meeting where variances change the next decision.

Start with the decisions, not the spreadsheet

Before adding rows, write down the decisions the forecast should inform. Common examples include whether payroll can be met without a draw, whether a large vendor payment can be released, whether collections activity needs escalation, or whether a planned hire should wait.

This keeps the worksheet from becoming a detailed but unused accounting exercise. A useful forecast creates a repeatable weekly question: what changed since last week, what does it do to ending cash, and who owns the next action?

The minimum structure

Use one column for the current week and twelve subsequent weekly columns. The weekly dates should use a consistent convention—often week ending Friday or Sunday—and should not move from one update to the next.

Section	What belongs there	Operating note
Beginning cash	Reconciled cash available at the start of each week	Start from a known bank or treasury balance, then document timing items.
Cash receipts	Customer collections, deposits, refunds, and other incoming cash	Forecast by expected receipt date, not invoice date.
Payroll and people	Payroll, taxes, benefits, and contractors	Use the actual pay calendar and identify one-off payments.
Cost of goods / direct spend	Inventory, freight, subcontractors, commissions, and direct costs	Separate committed spend from discretionary spend when useful.
Operating expenses	Rent, software, insurance, professional fees, and recurring vendors	Tie to payment terms and scheduled withdrawal dates.
Debt, taxes, and owner items	Debt service, tax deposits, and draws or distributions where applicable	Label these clearly; do not bury them in operating expenses.
Ending cash	Beginning cash plus or minus all weekly flows	This is the output to monitor and challenge.

The formula is simple: ending cash = beginning cash + receipts − disbursements. The hard part is making each component timely and traceable.

Build the first version in five working steps

1. Reconcile the opening cash position

Use the latest available bank, treasury, and payment-platform information. Record the timestamp and any known items that are not reflected in the balance yet. If cash is held in multiple accounts, decide whether the forecast shows total available cash, operating cash only, or both. The choice is less important than keeping it consistent and stating what “cash” means on the page.

2. Build receipts from the collections reality

Start with open accounts receivable, but do not assume every invoice will clear on its contractual due date. Review invoices with the sales or collections owner and place expected cash in the week it is expected to arrive. Separate large, uncertain, disputed, or past-due invoices so the meeting can focus on them.

For recurring revenue, use the actual billing and collection cadence. For project work, identify contractual milestones and the conditions that must be met before invoicing. A forecast is more useful when its uncertainty is visible than when it quietly turns a hope into a number.

3. Map known disbursements to their true payment week

Pull the payable aging, payroll calendar, debt schedule, tax calendar, purchase commitments, and recurring subscription list. Ask the operational owners about purchase orders, renewals, inventory commitments, commissions, or project payments that have not reached accounts payable yet.

The point is not to predict every expense perfectly. It is to avoid a predictable payment becoming a surprise because it was outside the general ledger at the time of the export.

4. Add assumptions and scenarios

For material receipts and disbursements, keep an assumptions tab or a notes column containing the source, owner, date reviewed, and confidence caveat. Then run only the scenarios management can act on. For example: a base case using current collection expectations, a downside case where specified large receipts arrive one or two weeks later, and a decision case for a known discretionary outflow.

Avoid multiplying scenarios until the team stops using them. A small number of clearly described scenarios is better than a dashboard full of unlabeled colors.

5. Install a weekly operating cadence

Set a fixed meeting time. Update bank cash, actual receipts, actual disbursements, new commitments, and changes in collection timing before the meeting. Compare last week’s forecast with actual results and ask why the largest differences occurred. Then log the decision, owner, and due date for each material action.

The forecast earns its place when it changes behavior: a customer follow-up happens, a payment is sequenced, a lender conversation starts early, or a hiring decision is made with clearer facts.

Separate operating cash from financing decisions

Show operating receipts and disbursements before any line-of-credit draw, owner contribution, equity proceeds, or other financing event. That subtotal answers an operating question: if the business runs as currently expected, what happens to cash? Show financing below it, with the expected timing and the condition required for it to occur.

This separation prevents a positive ending balance after a draw from hiding an underlying shortfall. It also gives leadership a clearer conversation. Operating actions might include accelerating a collection, sequencing inventory, pausing discretionary spend, or changing the timing of a purchase. Financing actions might include a facility draw, lender communication, or an owner decision about additional capital. Neither category should be silently used to solve the other.

For a credit facility, include only capacity that is genuinely available under the current facts. Note any borrowing-base calculation, covenant, reporting requirement, lender approval, collateral condition, or internal approval that could affect access. A forecast can show a planned draw without asserting that the draw is certain.

Review variances by cause, not only by total cash

Preserve the prior forecast long enough to compare it with actual bank movement. Classify each material difference as a timing variance, amount variance, scope change, or omission. A collection that arrives a week late is a timing variance. A customer short-pay is an amount variance. A repair that was never in the plan is an omission. A new commitment that changes the expected activity is a scope change.

Then ask what the variance says about the underlying operating process. A late receipt can point to a disputed invoice, an incomplete delivery milestone, a billing error, or an unclear collections owner. A surprise payment can indicate that purchasing, operations, and accounts payable do not share commitments soon enough. The aim is not to blame the preparer. It is to update the assumption, assign the response, and improve the evidence used at the next review.

Illustrative variance review

Assume a forecast expected $60,000 from a customer in the current week, but only $20,000 arrived. The cash variance is $40,000, yet the useful question is why. If the remaining amount is tied to an unresolved acceptance issue, moving it one week forward without a customer action plan does not improve the forecast. Record the revised timing, the responsible owner, the next customer contact, and the condition that would make the receipt probable. The next forecast should reflect that evidence.

A focused first-week implementation plan

On the first day, agree the forecast’s purpose, the definition of available cash, the weekly date convention, and the people responsible for collections, payments, payroll, and financing information. Request the minimum inputs and record access gaps immediately.

On days two and three, reconcile the starting balance and make a first pass at receipts and disbursements. Mark unverified assumptions rather than waiting for a perfect input set. Review material invoices, payroll dates, taxes, debt, and purchase commitments with the accountable owners.

On day four, separate operating activity from financing, add the assumptions register, and identify the weeks most sensitive to a small number of events. Prepare direct questions for those receipts, payments, and financing conditions.

On day five, hold the first review. Confirm the next two weeks, decide the action list, and schedule the recurring meeting. The initial forecast will contain uncertainty; a disciplined update and variance process is how it becomes decision-useful.

What to flag each week

Flag items that change the timing, liquidity, or controllability of cash:

• A single receipt that materially affects minimum cash and has no confirmed collection action.
• A vendor, tax, payroll, or debt payment that is missing a date, owner, or funding source.
• A pattern where collections repeatedly land later than the forecast.
• A forecast that assumes a financing event, owner contribution, or asset sale that is not committed.
• A negative or uncomfortably low ending-cash week without a documented response plan.
• A difference between accounting cash, bank cash, restricted cash, and cash that is actually available for operations.

These are management flags, not a prediction that a business will fail. The forecast should trigger questions and responsible actions, not create false certainty.

Common failure modes

Using revenue instead of collections. Revenue may be earned before cash is received. Put the receipt in the week cash is expected.

Treating the first forecast as final. The first version is a baseline. Improve it through weekly forecast-versus-actual review.

Ignoring payments outside accounts payable. Payroll, taxes, debt, bank fees, subscriptions, commissions, and owner transactions can matter as much as vendor invoices.

Hiding uncertainty in a single number. Label the uncertain receipt or payment and specify what would confirm or change it.

Building a report without a meeting. A forecast without an owner, cadence, and action log is often just a spreadsheet.

A practical weekly agenda

1. Confirm opening cash and material timing items.
2. Review prior-week forecast versus actual receipts and disbursements.
3. Review the next two weeks in detail; scan the remaining horizon for large changes.
4. Challenge the material collections assumptions with the accountable owner.
5. Confirm decisions, actions, owners, and due dates.
6. Preserve a dated copy or change log so the team can learn which assumptions repeatedly fail.

Where this fits in a first-90-days finance plan

The forecast is often one of the first operating tools a finance leader stabilizes, but it depends on basic data access and clear ownership. A structured financial-stack audit can reveal whether bank access, billing data, payables, payroll, and reporting systems are reliable enough to support the forecast. The forecast then becomes an input to the first-90-days operating framework, where near-term cash decisions are connected to close, reporting, controls, and planning work.

When an engagement is being scoped, the forecast’s condition also affects the work required. See how to scope and price a fractional CFO retainer for a method that separates recurring leadership work from remediation or implementation work.

Educational note

This article describes an operating method, not a promise of liquidity or financial advice. For accounting presentation and financial-statement questions, consult the applicable professional standards and a qualified accounting professional.