Tod Pettis

Tod Pettis

Tod Pettis

  • ,
  • Accounting & Finance
  • Member Since: 20 Nov 2026

How to reforecast a budget mid year: three drivers to check

Learning how to reforecast a budget mid year starts with a concrete question: which numbers in the plan are no longer true? You keep the approved budget for comparison, replace closed months with actuals, and re-estimate the remaining months from three drivers: revenue timing, the cost base, and working capital. The rest of the plan can wait until the evidence says otherwise.



Start with the gap between plan and actuals, not the spreadsheet



The most common mistake in a mid-year review is opening a blank copy of the budget and rebuilding every line. That takes weeks, and it hides the question that matters. Before you change any formula, look at the gap between plan and actuals for the months that have closed. A gap tells you where an assumption was weak. It does not tell you the whole plan is broken.



Start with a simple comparison. For each major line, subtract the budgeted amount from the actual amount, then divide the difference by the plan to see its size relative to what you expected. Sort the largest differences to the top. In many growing companies, a handful of lines explain most of the movement, and the rest is noise that can wait.



The symptom that sends owners into a panic is a variance report that is red in every column with no explanation attached. When that happens, the cause is usually upstream of the forecast. Transactions may be coded to the wrong accounts, the books may close two weeks late, or the original budget may have been built top-down, with a revenue target and no line-level drivers beneath it. The correction starts with the books, not the model.



Consider a hypothetical services firm that budgeted $240,000 of revenue for the first half and recorded $205,000. The shortfall looks like a sales problem. Read the contracts, though, and you may find that two large engagements slipped from May into July. That is a timing difference. The work still happens, but it lands in another period, so a forecast that cuts the full-year number would be too pessimistic. The fix is different from the fix for lost customers.



Whether the gap is a timing problem, a volume problem, or a price problem changes what you should correct. It depends on which one you can prove from the source documents. Until you can, avoid changing the full-year target, because a number adjusted before the cause is known tends to be adjusted again next quarter.



Lock the closed months and decide what the reforecast must answer



A closed month should stop being an estimate. Once a month is closed, reconciled to the bank, and fractional CFO companies in Miami reviewed, its actuals become the base for everything that follows. A common error is to leave a closed month open for late adjustments while the reforecast is being built. The result is a moving base, and nobody can tell whether a change came from the business or from a journal entry made after the fact.



Next, decide what the reforecast has to answer. An owner deciding whether to add a salesperson needs a view of the next two or three quarters of revenue and cost. A lender checking whether the company can keep covenant headroom needs a different cut, with cash and debt service shown month by month. The question sets the horizon, the level of detail, and the lines that matter. It depends on what decision is waiting, and a reforecast without a decision behind it tends to grow until nobody reads it.



Set the scope before anyone edits a formula. A useful first version usually covers the full-year profit and loss for the lines that drive the decision, a headcount schedule, and a short cash view. Leave out lines that will not change the answer. Thinner is often better here, because every extra line is one more assumption someone has to defend when the numbers come back different.



Name the version and date it. A label such as "Reforecast 1, actuals through May" prevents the common problem of two spreadsheets circulating with slightly different numbers and the same file name. Keep the original budget unchanged in its own tab or file, and show it next to the new forecast. The comparison is part of the message: the reader needs to see what moved and what stayed the same.



Finally, decide whether a quick reforecast is enough or whether you need a rebuild. A quick version works when the business model has not changed and the gaps can be traced to a few drivers. A rebuild is needed when a product line was added or dropped, pricing changed, an entity was formed, or a large customer left. Doing too little leaves old assumptions in place. Doing too much delays the answer until it is no longer useful.



Driver one: revenue timing, not only the revenue total



The symptom here is a year-end revenue number that still looks reasonable while the monthly pattern does not match the bank account. Sales appear strong in one quarter, cash arrives late, and the owner cannot explain why the two do not line up. The cause is almost always timing. The moment revenue is recognized, the moment it is invoiced, and the moment the customer pays are three different events, and a budget that treats them as one will drift.



For many companies in the United States, the recognition point is set by ASC 606, the revenue standard under U.S. GAAP. Under that standard, revenue follows the transfer of promised goods or services to the customer, which can happen over several months on a long project or a subscription. A contract signed in March may produce revenue across several later months, even if the first invoice went out in March. Read the contract before you read the invoice.



The correction is to rebuild the revenue driver by contract or by customer group, not by a single annual target. For each agreement, record the items that move the timing:




  • Contract start date and end date

  • Billing schedule, including deposits and milestone payments

  • Recognition pattern, whether over time or at a point in time

  • Renewal or slippage assumption, with a stated reason



It depends on how many agreements you have. A company with a few large contracts can model each one, and the effort pays off because a single slipped start date can move a quarter. A company with hundreds of small customers is better served by a cohort or run-rate model, grouped by start month or product, with a renewal rate taken from its own history. Both approaches are valid. What fails is a single line that says revenue grows by some percentage over the prior year without a reason.



A hypothetical software reseller with annual maintenance contracts renewing in March offers a simple test. If its budget spread renewals evenly across twelve months, the reforecast would show a false pattern, and any monthly variance would look like a sales miss. Rebuilding the renewals by their actual dates shows whether the first-half gap is real or simply a calendar effect. The test is quick to run, and skipping it can start a long argument about a gap that was never real.



Driver two: the cost base, split into fixed costs, committed costs and discretionary costs



The symptom is spending that runs above plan with no single culprit, followed by a proposed cut across every department. Across-the-board cuts feel fair and fast, but they often hit the wrong lines. The cause is usually a budget that groups everything under operating expenses, so nobody can see which costs can move in the next two months and which cannot.



Classify every cost line into one of three groups before you change any number. Fixed costs stay roughly the same regardless of activity in the short run, such as rent and base salaries. Committed costs are obligations already signed, such as software subscriptions with notice periods, insurance premiums, and equipment leases. Discretionary costs can be started, paused, or stopped within the period, such as marketing programs, travel, and outside consultants. The groups behave differently, so the reforecast should show them in separate rows.



Discretionary spending is the easiest to cut on paper, and that is the trap. A paused marketing program may lower cost this quarter while reducing the pipeline that produces revenue next year. Committed costs look fixed but are not always visible in the budget at all. A vendor contract with a ninety-day notice period cannot be stopped in July if the notice was due in April. Check the signed agreements, not only the ledger, before you assume a saving.



Open hiring plans need the same care. A requisition with a planned start date is a cost change waiting to happen. If the company has delayed three open roles, the reforecast should move their start dates and show the effect on payroll and benefits. Deleting the roles removes the option to hire again without explaining why the plan changed.



Recurring price increases deserve a line of their own. Many vendors apply annual escalators, and an insurance renewal or a software contract can rise on a fixed date that the original budget missed. Put the escalation dates in the cost driver table next to the amounts. A cost that rises mid-year because of a contract clause is a different problem from one that rises because someone approved more spending, and the correction for each is different too.



The trade-off is real. Cutting discretionary spend protects cash quickly, but it can weaken the revenue driver you are also trying to keep on plan. Hold back on any cut that touches sales or delivery capacity until you have compared it with the revenue timing you rebuilt in the previous section. A saving that lowers next quarter's revenue is not a saving.



Driver three: working capital and the cash the P&L does not show



The symptom is a profit line that looks steady while the bank balance keeps falling, or a payroll week that arrives before the owner expected it to be tight. Owners often read this as a sign that the forecast is wrong. Usually the forecast is fine for profit and incomplete for cash. Working capital is the timing gap between when the business earns money and when cash actually moves.



The cause sits in three places. Receivables grow when customers take longer to pay than the terms say. Inventory grows when stock is bought ahead of demand. Payables shrink when suppliers are paid sooner, sometimes to protect a discount or a relationship. None of these changes shows up in net income, so a profit-only reforecast will miss them entirely. A company can be profitable on paper and short on cash in the same month.



The correction is to link the reforecast to balance sheet assumptions. For a service company, that usually means the typical number of days it takes to collect and the typical number of days it takes to pay suppliers, both measured over the last two or three closed quarters. For a company that holds stock, add an inventory assumption tied to the sales plan. Compare each assumption to actual results from the closed months. If the reforecast assumes collections will improve while the aging report shows them slowing, the assumption needs a reason or a change.



Payment terms are where a business can trade cash for growth without noticing. Offering 60-day terms instead of 30 may win a larger account, and that can be a reasonable decision. But the reforecast has to show the cash delay, not just the revenue. A hypothetical distributor whose summer orders double while its customers pay on longer terms will report strong sales and a weak bank balance, and both statements can be true at once. The forecast should make that visible before the bank does.



It depends on how much cash cushion the business has and how quickly it can move its collections. A company with a deep credit line can absorb a slow quarter. A company without one needs the cash view to be precise, because a missed payroll or a missed tax payment is a different kind of problem from a lower profit line. Decide which situation you are in before you choose how detailed the working capital section should be.



Choosing who runs the reforecast: accountant, controller, fractional CFO, or interim CFO



The right person to run the reforecast depends on what is broken. A company with late or unreliable books does not have a forecasting problem yet. It has a close problem, and the forecast will inherit every error in the ledger. A company with clean books but no one to interpret them has a different problem, and it may need someone who can turn the numbers into decisions. The four common options serve different stages, so it helps to compare them side by side.








Read the table in sequence. If the books are not closing reliably, the first purchase is the close, not the strategy. An owner who hires a fractional CFO companies in Miami CFO to rebuild a forecast on top of a late ledger will spend hours reconciling numbers that should have been reconciled at month-end. Fix the bookkeeping gap before you shop for strategic help. That order can feel slower, but it saves time.



The owner can run a light reforecast alone when the business is simple, the ledger is clean, and the decisions are few. The risk is structural. The same person sets the assumptions, approves the spending, and checks the variance. That is a lot of roles for one reader, and bias tends to creep in where it is hardest to see. A second reader, such as a controller or an outside reviewer, catches the assumption nobody challenged.



When you evaluate a provider for any of these roles, objective criteria help more than polished language. Ask whether the scope can grow or shrink as the business does. Ask whether the person has worked in your industry and what that experience covers, without accepting a general claim as proof. Ask how strategic decisions are supported and what investor or lender reporting looks like in a sample. Ask about the timeliness and accuracy of monthly reports, and request an anonymized example of a monthly package before you sign anything.



Be careful with any promise that sounds like a guaranteed result. No one can promise the outcome of a financing, a sale, or a loan negotiation, and a provider who does is not giving you a fair picture. The honest question is what the work will produce for your company, given its books, its contracts, and its timeline. A good answer names the deliverables and the limits. A weak answer names only the outcome.



Pairing the reforecast with a 13-week cash flow forecast



The reforecast answers where the year will land. A 13-week cash flow forecast answers a narrower question: will the company meet its obligations over the next three months? The two work on different horizons and different levels of detail, and they should agree where they overlap. A profit forecast can look healthy while the 13-week view shows a short week in the middle of the quarter. Both are useful, and neither replaces the other.



Build the 13-week view in weekly columns. Start with the opening bank balance, then list expected receipts by customer or by collection group, using the payment patterns from the working capital section. Add disbursements by payment run: payroll dates, rent, vendor batches, loan payments, and tax payments such as quarterly estimated taxes where they apply. End each week with a closing balance and a minimum cash line you set in advance. That line is the number that triggers action.



Refresh the view every week against the bank statement. Keep the variance for each week, and compare it with the forecast you made the week before. The accuracy of the view is a useful measure of your drivers. If receipts keep arriving a week late, the collections assumption is wrong, and the reforecast should change too. If disbursements keep moving, check whether payment runs are scheduled the way the forecast assumes.



The tools depend on how much manual work your team can keep up with. Many small and mid-sized companies run the 13-week view in a spreadsheet, which is transparent and cheap to change. Others use planning software such as Adaptive Insights or Prophix for budgets and forecasts, connected to a ledger such as NetSuite, Sage Intacct, QuickBooks, or Epicor. Larger groups may already run SAP S/4HANA. Choose based on where the data lives and who will maintain it, not on what a demo looks like.



When the 13-week forecast is consistently wrong, do not start by blaming the method. Check the source data first. Are receipts recorded when cash arrives, or when an invoice is entered? Are vendor payments released in the batch the forecast assumes? A large share of forecast error often comes from timing in the bookkeeping rather than from the business itself. Fix the data, and the forecast tends to improve without any change to its structure.



Keeping lender, investor and audit materials consistent with the revised numbers



Once a loan negotiation, a funding round, or a sale process is on the calendar, the reforecast stops being an internal tool. Others will read it, compare it with other documents, and ask about the gaps. A lender who sees one revenue figure in the covenant package and a different figure in the board deck will want an explanation before discussing terms. Consistency is the first thing a careful reader checks.



Map each reforecast assumption to its source. A revenue assumption should point to the contracts and billing schedule. A payroll assumption should point to the payroll register and the hiring plan. A cash assumption should point to the bank statements and the aging report. Keep a change log with the date, the person who changed the assumption, and the reason. The log helps internal review, and it is the kind of record that auditors and diligence teams often request when they reconcile numbers over time.



Investors and buyers usually want a bridge between the original budget, the reforecast, and the actual results. The bridge explains each movement in categories such as timing, volume, price, and cost, and it ties back to the general ledger. Preparing it in advance is more useful than assembling it during diligence under time pressure. A bridge explains what changed. It does not, by itself, change the outcome of any negotiation, and it should not be presented as if it did.



Take a hypothetical company preparing for a possible sale. During the reforecast it finds that one large contract was recorded differently in the management accounts than in its audit-ready schedules, so first-half revenue looks higher in one document than in the other. Correcting the difference before outreach is easier to explain than explaining it during diligence. The correction may also change the story the company tells, and that is a reason to address it early, not a reason to hide it.



The trade-off runs in one direction. Do not present a reforecast that is more optimistic than the actuals support, even when a valuation conversation or a loan deadline makes that tempting. A forecast that the next quarter's results contradict damages credibility more than a cautious forecast that the company later beats. Keep the reforecast tied to evidence, and label the assumptions that depend on events not yet in hand.



What to verify before you present the revised numbers



Before the revised forecast leaves your desk, check these items. Each one is a test the numbers should pass, not a guarantee that the forecast will be right.




  1. Every closed month ties to the bank statements and the general ledger, with no open adjustments.

  2. Revenue timing matches contract start dates, billing schedules, and the recognition pattern for each agreement.

  3. Committed costs match signed contracts, including notice periods and scheduled escalators.

  4. Working capital assumptions match collection and payment patterns from the last two or three closed quarters.

  5. The version name, date, scope, and comparison to the original budget appear on the first page.

  6. The 13-week cash view agrees with the reforecast's cash assumptions for the same months.



Start with the single driver that has the largest unexplained gap, and fix it before moving to the next one. Trying to correct all three at once makes it hard to tell which change moved which number. Once the largest gap is explained, the next one is usually easier to see, and the reforecast becomes a sequence of checked assumptions rather than a single rewritten file.



If the answer to which numbers are no longer true is most of them, the problem is probably the books, not the forecast. In that case the next conversation should be about the close, the coding of transactions, and the reporting calendar. A reforecast built on reliable records is worth more than a faster one built on guesses, and that is the standard to hold the revised numbers against.


Details

Phone CB
Email Address tod_pettis85@dashz.top
Gender Female
Salary 14 - 91
Address 3032

Cookies

This website uses cookies to ensure you get the best experience on our website.

Accept