Cash planning during a leadership gap: what to check weekly

Cash planning during a leadership gap works when one person reviews the same set of numbers every week, whether or not a senior finance leader is in the room. Done well, the company knows its cash position, the payments and receipts due in the next few weeks, and which decision is waiting on a figure nobody has checked yet. The gap still exists, but it stops being a surprise.

Who owns the weekly cash review when no finance leader is in place

The first question is not which numbers to track. It is who will open the file on Monday morning and who will be expected to explain a gap on Friday. In many growing companies, that person is the owner, an operations manager, or a bookkeeper who already handles deposits. None of those choices is wrong, but each carries a different level of judgment, and the review changes shape depending on who runs it.

A bookkeeper is strong at confirming what has already happened. The bank feed, the open invoices, and the bills entered this week are their territory, and a careful bookkeeper will catch a deposit that was posted twice. What they often lack is the authority to say that a planned hire should wait. That decision belongs to someone who can weigh the company’s priorities against the cash that will actually be available.

An owner usually has the authority but not always the time or the habit. Founders tend to check the bank balance when something feels tight, which is a reactive pattern. A weekly review asks for a fixed slot, the same agenda, and a short written note, so the owner sees a trend instead of a single number. Without that structure, the review becomes a mood check.

A fractional or interim finance leader can take this role on a set schedule, and that is one reason companies choose the model. Some businesses prefer to keep the routine inside the team and bring in an outside leader only for the monthly forecast or a lender conversation. Neither arrangement fits every company. The useful test is whether one person is clearly accountable for the answer to the question: what changes next?

Write the owner’s name next to the review before anything else. Then write who approves a payment that breaks the forecast, and who can pause discretionary spending. If those three roles belong to three different people, the review will still happen, but decisions will sit in a queue until someone notices.

The five weekly checks, in the order to run them

A weekly review does not need dozens of metrics. It needs a short list that answers the same questions every time, so a change stands out. Start with the ending bank balance, reconciled to the ledger, because every other number depends on it. If the bank and the books disagree, fix that before looking at anything else.

1. Confirm the bank balance against the general ledger, and note any unreconciled items older than a week.
2. List cash receipts expected over the next several weeks, by customer, with the date each one is promised.
3. List cash payments due in the same window, grouped by payroll, taxes, rent, loan payments, and vendors.
4. Compare last week’s actual receipts and payments with the forecast, and write one sentence on the largest gap.
5. Identify the one decision that depends on next week’s cash, such as a hire, a purchase, or a delayed vendor payment.

The fifth check is the one most reviews skip. A forecast that does not change any decision is a report, not a planning tool. Ask what would happen if the largest receipt slipped by two weeks, and write down the answer before the meeting ends. That exercise takes minutes and shows whether the company has room to absorb a delay.

Keep the list in the same order each week. Consistency makes changes easier to see. When the order shifts, reviewers spend their time finding numbers instead of reading them, and small problems slip past. A shared sheet, or the reporting module of an accounting system such as QuickBooks, NetSuite, or Sage Intacct, can hold the same layout, provided someone maintains it.

The checks also reveal what you cannot see yet. If you cannot list next month’s receipts by customer, the problem is probably not the forecast. It is the sales records, the invoice dates, or the contract terms that feed it. Note these gaps as items for finance operations work, not as failures of the weekly meeting.

Once the routine is set, keep the review short. The first few weeks will run longer while the data is cleaned up. If it keeps running long after that, the inputs are the problem, and a longer meeting will not fix them.

How a rolling forecast keeps the next few weeks honest

A rolling forecast is a view of the next several weeks, updated every week as the window moves forward. Its value is not precision. Its value is that each week you compare what you expected with what happened, and you adjust the assumptions that were wrong. Over time, the gap between plan and actual becomes a learning tool rather than an embarrassment.

Each element carries a judgment. Collections are the hardest, because they depend on customers who may pay late, dispute an invoice, or ask for a payment plan. Treat the expected date as a scenario, not a promise, and keep a second line showing cash if the largest customer pays a couple of weeks later. That line is often the most useful one in the whole forecast.

Disbursements are easier to plan but harder to change. Payroll and loan payments are usually fixed, while some vendor spending, travel, and marketing can move. Separating those groups shows the real room the company has. A forecast that presents every payment as equally urgent hides the choices that actually exist.

Ask what changes next after every forecast update. If the answer is nothing, the forecast may be correct, but it is not doing its job. If the answer is a specific decision, such as delaying a hire, drawing on a credit line if the company has one, or asking a supplier for different terms, write it down with an owner and a date.

Watch for forecasts that never change. A model that shows the same ending balance week after week usually means the team is copying last week’s numbers forward instead of updating them. A small, honest change each week is a healthier sign than a perfectly stable table.

Receivables and payables: where weekly reviews usually stall

Receivables and payables sit at the center of most weekly cash problems, and they are the parts of the review most likely to be outdated when the meeting starts. An aging report is only as good as the last time someone updated it. Before the review, confirm that invoices went out, that disputes are logged, and that payment promises were recorded.

Collections that keep slipping

Start with the top few customers by open balance. For each one, note the invoice date, the due date, any dispute, and the last contact. A customer who has paid two invoices late in a row is not a surprise. That pattern belongs in the forecast, with a lower likelihood of on-time payment than the terms on paper suggest.

Some slippage comes from the company’s own process. Invoices sent in batches at month end, purchase orders missing from the file, or unclear contact names on the customer side can delay payment for weeks. If the weekly review finds the same cause twice, it belongs on the operations list, not only in the forecast.

Payments you can time without damage

Payables work differently. The goal is not to stretch every vendor, because strained supplier relationships can cost more than a late payment saves. A practical approach is to sort vendor bills into three groups: those that carry penalties or service interruption if paid late, those that can move within agreed terms, and those that can be renegotiated with short written notice.

Every change to a payment date should appear in the forecast the same week. Delaying a bill without recording it is how a company discovers, weeks later, that two payments landed on the same day. Keep a short log with the vendor name, the original date, the new date, and the person who approved the change.

The review should also ask whether the company pays early out of habit. Some businesses pay on receipt by default because nobody ever set the terms. Checking this once a month, rather than every week, is usually enough to catch it without adding noise to the routine.

Payroll, taxes, and fixed commitments that cannot slide

Some payments cannot move without consequences, and a weekly review should treat them as fixed before it discusses anything discretionary. Payroll is the obvious example. Federal payroll taxes withheld from employees and owed to the government follow their own deposit schedules, and late deposits bring penalties. Missing them is one of the few cash decisions that can create direct problems with agencies.

For a company in Massachusetts, the review should include state withholding and unemployment contributions alongside federal deposits. Confirm the due dates with the payroll provider or the company’s tax advisor instead of relying on memory. Sales and use tax, if the company collects it, follows its own filing calendar. The goal is not to memorize every rule. It is to make sure each due date appears in the forecast before the money is needed.

Loan payments, rent, and insurance premiums are fixed too, though their timing can be less visible. A debt schedule that lives in a separate file, or an annual insurance bill, can fall outside the weekly view. Build one list of fixed commitments and check it against the bank each week. Anything missing from that list is a question for the owner.

Fixed does not mean invisible. Some agreements include covenants, such as a minimum cash balance written into a loan. Those need their own line in the review. If the forecast shows the company near that threshold, the decision is no longer just operational. It belongs with the owner and with whoever negotiated the agreement.

For each fixed item, keep a plain note on how many days of cash it needs and what would happen if it arrived late. This is not a formal reserve policy. It is a clear statement that lets the team act before a deadline forces the choice.

What lenders, investors, and buyers will ask for from your weekly numbers

Companies preparing a loan request, a first funding round, or a sale often find that their weekly cash habits matter to outsiders. A lender wants evidence that the business can explain its cash position without a long search. An investor looks for a forecast that matches the company’s history. A buyer’s diligence team tests whether the numbers can be reproduced from source records.

Start by making the weekly files usable as evidence. Each forecast should carry a date, a version, and a note on what changed since the last one. Actual figures should trace back to bank activity and ledger entries. None of this guarantees a loan approval, an investment, or a closed sale, because those depend on factors outside the company’s control. What it does is reduce the number of questions that stall a process.

Expect outside readers to ask about variance. If the forecast missed by a wide margin in several weeks, they will want to know why. A short variance log, with a plain explanation kept each week, is more persuasive than a clean-looking forecast with no record of how it was built. Honest notes about past misses build more confidence than a table that never seems to be wrong.

Working capital questions come up quickly. Who pays the company, how long collection takes, how much inventory or work in progress sits on the balance sheet, and how payables are timed. A weekly review that already tracks those items makes the diligence conversation shorter. If revenue recognition matters for the company’s reporting, ASC 606 governs how revenue is recognized, and the weekly view should not contradict figures prepared under it.

Not every company needs a full transaction file. A business that only wants a line of credit may need less than one preparing for a sale. The right depth depends on the request in front of you, so ask the lender or advisor what they expect before building more than the situation requires.

Controls that keep a weekly review from becoming guesswork

A weekly review is only as reliable as the controls behind the numbers. Without them, the forecast rests on whoever last updated the spreadsheet, and nobody can tell whether a missing payment was delayed or forgotten. Controls do not need to be heavy. They need to be consistent and visible to the people who rely on them.

Start with bank reconciliation. Each account should be reconciled to the ledger on a set schedule, with the preparer and the reviewer named. The person who records payments should not be the only person who checks the bank statement. Where headcount is small, that split can be hard to achieve, so the owner can take the review step even if a bookkeeper does the work.

Set approval thresholds for payments and changes. A simple rule, such as requiring the owner’s approval above a set amount or for any new vendor, prevents many surprises. The amount itself is a company decision. What matters is that it is written down, so nobody has to decide case by case under pressure.

Access and tools matter as well. Accounting systems such as QuickBooks, NetSuite, and Sage Intacct each handle user roles differently. A company running SAP S/4HANA typically manages the same question through its own ERP administrators, at a larger scale. Whatever the system, check who can edit bank rules, approve bills, and export reports. Shared logins make it impossible to trace a change back to a person.

Document the routine itself. A one-page description of the weekly review, its inputs, its owner, and its outputs means the process survives a vacation, a staff change, or a new interim leader. Companies already working toward ISO 9001 often have document control habits they can reuse here. Continuity is the point. A review that depends on one person’s memory is a single point of failure.

Worked example: one hypothetical services firm and its first weekly checks

Consider a hypothetical services firm in the Boston area with a small team, a founder who leads sales, a bookkeeper who keeps the ledger current, and no finance leader on staff. The firm is considering a credit line, and one large customer often pays late. Nobody has owned the weekly cash review since the last controller left.

In the first week, the bookkeeper reconciles the operating account and finds two deposits recorded in the wrong month. The owner asks for the forecast and sees that the coming weeks look comfortable on paper. The review, however, shows that the late customer’s invoices make up most of the expected receipts, so the comfortable picture depends on one payment date.

The team makes three changes. It adds a second line to the forecast showing cash if the late customer pays two weeks later. It lists payroll taxes, the loan payment, and insurance as fixed items with their due dates. It logs a vendor payment the owner chose to move, with the approver’s name and the new date.

What changes next? The scenario shows that the firm can cover fixed payments in the delayed case, but with only a small margin. The owner decides to hold a planned equipment purchase until the overdue receivable clears, and asks the bookkeeper to send a reminder on the open invoices every Monday. That is a decision with an owner and a date, which is exactly what the review should produce.

In the following weeks, the review runs shorter because the inputs are cleaner. The bookkeeper flags a new dispute on one invoice, and it goes onto the operations list. The owner asks whether the credit line would be needed if the customer paid on time, and the forecast answers that question directly. The firm does not yet know whether the lender will approve the line, and the review does not pretend otherwise.

The example does not describe the right model for every company. A firm with more staff might give the review to an internal controller, and a larger one might keep the routine in-house while bringing in a fractional CFO to review the forecast each month. The checks stay the same. Who runs them, and how much outside leadership the company needs, depends on its stage and the decisions in front of it.