Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
7
7919benefits-of-a-outsourced-cfo-in-miami
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Issues 2
    • Issues 2
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Jobs
  • Issue Boards
  • Rosario Raley
  • 7919benefits-of-a-outsourced-cfo-in-miami
  • Issues
  • #2

Closed
Open
Opened Nov 20, 2026 by Rosario Raley@rosarioraley5
  • Report abuse
  • New issue
Report abuse New issue

Forecast vs projection in finance: what lenders expect to see


When you compare forecast vs projection in finance, the core difference is what each one rests on. A forecast estimates what is most likely to happen, based on current trends, signed contracts, and recent results. A projection shows what could happen if certain assumptions hold, such as opening a second location or raising prices. Lenders read both, and they expect each one to be labeled plainly and tied to the company's actual numbers.

Where the two terms split and where they overlap


In many small companies, the two words are used as if they meant the same thing. A bookkeeper may call the monthly budget a forecast, a bank template may label the same spreadsheet a projection, and a file inherited from a previous owner may mix both. Lenders do not work from one textbook. They care less about the label on the cover than about what each number is anchored to, so it helps to settle the vocabulary before anything is sent.


A forecast, in the sense most lenders mean, is the business's best estimate of what will happen over the coming months. It begins with recent actual results, follows the trends that are already visible, and counts commitments the company can point to, such as signed contracts or standing orders. It does not assume a sales push that has not started yet.


Consider a hypothetical building supplies distributor in Miami-Dade that sells mostly to general contractors. Its forecast for the next twelve months would start with the last six months of sales by customer, then adjust for jobs already scheduled and for the usual slowdown during the rainy season. Every adjustment would have a reason attached to it, and the owner could explain each one without reaching for optimism.


A projection starts from a question instead of a trend. What happens to cash if the distributor opens a branch in Broward County next year? What happens if its largest customer pays in sixty days instead of thirty? Projections are built to test these paths, so they usually include several versions. They can be useful, but they become misleading when the assumptions stay hidden inside the formulas.


The overlap is real. Both documents use the same basic structure: an income statement, a balance sheet, and a cash flow view. Both should start from the same actual balances at the point where the model begins. That starting point is the first thing a careful reader checks, because a model that does not begin where the books end has already lost credibility before anyone reads the assumptions.

What a lender reads first in your historical statements


Lenders usually begin by looking backward. They ask for recent annual and interim financial statements, often including the income statement, balance sheet, and cash flow statement, along with a schedule of existing debt. The exact list depends on the lender, the loan type, and the size of the request, so a checklist from one bank should not be treated as a rule for every bank.


The historical statements act as the anchor for everything that follows. A reader will compare the opening cash in the forecast with the bank balance, the receivables with the aging report, and the revenue trend with the last twelve months. When these do not match, the reader stops looking at the future and starts asking why the past is not consistent. That pause can cost more time than any single weak assumption.


Accounting method matters here too. A company that keeps its books on a cash basis and a lender that reads accrual statements will see different timing for the same work. For service and contract businesses, revenue recognition rules such as ASC 606 can move revenue into periods that differ from when money arrives. Software such as QuickBooks, NetSuite, or Sage Intacct can produce clean reports, but only if the chart of accounts stays consistent from one year to the next.


Seasonality deserves its own look. Tourism, construction, and trade businesses in South Florida often have months that run well above or below the rest of the year. A forecast that smooths these swings into a straight line looks wrong to any reader who knows the business, even when the annual total is reasonable. The historical monthly pattern gives the forecast its shape, and the lender expects to see that shape reflected.


There are limits to what historical statements can prove. If the books are months behind, or if the year-end adjustments were never finished, a lender will discount any forecast built on top of them. It depends on how clean the records are. A forecast cannot repair the past, and a rushed package often reveals more about the bookkeeping than about the plan.

How a forecast is built so a lender can follow it


A forecast that a lender can follow starts from drivers, not from one growth percentage. A driver is the operating fact that produces the number: how many customers buy each month, what the average order is, how prices change, how many people the company must staff, and how long customers take to pay. When the model is built from these pieces, each line can be questioned, and the reader can see where a change would matter most.


Every assumption needs a source. The distributor's collection period, for example, should come from the receivables aging report, not from the owner's sense that customers usually pay on time. Supplier terms should come from invoices and vendor agreements. Staff costs should come from payroll records and any hiring plan the company has actually approved. An assumption without a source is a hope, and lenders treat hopes as risks.


For the short term, many businesses use a 13-week cash forecast. It lays out receipts and disbursements week by week for roughly one quarter, and it is updated every week by replacing the forecast with actual results and rolling the window forward. The monthly twelve-month view and the 13-week view should connect, so the reader can trace how a weekly squeeze shows up in the longer model. A useful forecast package usually covers these areas:

Revenue, broken down by the drivers that produce it Cost of sales and operating expenses, with fixed and variable costs separated Payroll timing, including bonuses and seasonal hiring Taxes and other recurring obligations, on the dates they are due Planned capital spending and how it is paid for Debt payments, including interest and principal


Working capital is where many forecasts fail in quiet ways. Receivables, inventory, and payables determine how much cash the business needs to keep operating, and a sales increase can consume cash before profit appears on the income statement. A distributor that grows quickly may buy inventory weeks before its customers pay. Lenders look hard at this relationship because it explains why a profitable company can still run short of money.


Finally, a forecast needs version control. The file should show who prepared it, the date, and what changed since the last version. When a number moves, the reader should be able to see whether the change came from new actual results, a revised assumption, or a correction. That history makes the model easier to trust, and it also protects the owner when someone asks why last month's plan looked different.

When a projection is the right tool and how to label it


It depends on the question. A projection fits decisions that have not happened yet, such as a new branch, a large equipment purchase, a hiring wave, or a sale process that may take a year to reach a buyer. In each case, the owner needs to see how the company would look under a specific path, and a single forecast of the current trend cannot show that.


A useful projection usually includes at least two cases. A base case reflects the assumptions the owner considers realistic, and a downside case shows what happens if the most important drivers move the wrong way. Some owners add a third case for the upside, but the downside case is the one lenders study most closely. The model should name the one or two assumptions that drive most of the result, then test them with a sensitivity analysis that shows how much the outcome changes when each one moves.


Labeling is where honesty becomes visible. A page marked "Projection: second branch opens in month nine, assuming the lease is signed" tells the reader exactly what is being tested. A page marked "Forecast" with the same numbers suggests that the owner expects them, which is a stronger claim. Lenders can accept a projection, but they dislike a projection that has been dressed up as a forecast, because it implies more confidence than the evidence supports.


Back to the hypothetical distributor. Its owner wants to open a Broward County branch, so the projection includes the lease cost, a ramp period of several months before sales reach a steady level, the cost of hiring a branch manager, and the inventory needed to stock the new location. Each of these is an unknown, and the model lists each one with its basis. The base case assumes the branch reaches its planned sales level more slowly than the owner would like, which is a deliberate choice that makes the plan easier to defend.


The biggest risk with projections is that they describe things the company has never done. The distributor has never run a branch, so its ramp period is an estimate, not a memory. A good projection says so and does not present a new location as a certainty. It also avoids treating the projection as a promise about the outcome, because no model can guarantee how a new location, a loan, or a sale will turn out.

Side by side: what each document answers


The easiest way to see the difference is to set the two documents next to each other on the same criteria. The table below is a simplified comparison, and real packages may blend the two. The point is not to pick a winner. Each document answers a different question, and a lender reads them differently for that reason.

Criterion Forecast Projection

Starting point Recent actual results and current commitments A decision or scenario the company has not yet taken

Main question What is most likely to happen if current trends continue? What would happen if this path is taken or this event occurs?

Typical horizon Weekly for the near term, monthly for about a year Often one to several years, matched to the decision

Number of versions Usually one current version, updated regularly Usually several cases, such as base and downside

What a lender checks Tie-out to actuals, plausibility of drivers, working capital Whether assumptions are sourced, how sensitive the result is, and how repayment holds under stress


Reading the table, the most important row is the starting point. A forecast that begins from the last actual balance sheet can be checked against records the lender can already see. A projection begins from a choice, so its credibility depends on how well the choice is explained and how carefully the assumptions are sourced. Many weak packages fail because they mix the two starting points without saying so.


The most common mistake is putting projected numbers in the same columns as actual numbers without a visible break. A reader who sees a clean line running from January actuals into July estimates may assume the July figures are as solid as the January ones. Shading, headers, and a clear line between actual and estimated periods prevent this. The cost of adding them is small, and the benefit to trust is large.


A single lender package often contains both documents. A common structure is a historical summary, a current forecast for the next year, and one or two projections tied to the specific use of the loan. Each section should carry its own label, and the summary page should explain how the sections connect. When the forecast supports the projection, the reader can follow the chain without guessing.


Not every lender wants the same format. Some ask for a standard template, and others want the owner's own model with supporting schedules. It depends on the institution and on how much detail the loan officer expects. Asking the lender early what it wants to see saves rework, and it signals that the owner understands the process.


For the distributor, the labeled package made the difference between a confusing stack of spreadsheets and a document a lender could actually read. The forecast showed the business as it runs now. The projection showed the branch as a question with clear conditions. Neither document pretended to be the other, and that clarity gave the lender something concrete to test.

What lenders and investors check before they trust either one


Before a reader studies the growth story, the reader runs a few consistency tests. Do the opening balances match the latest statements? Does the first forecast month continue from the last actual month without an unexplained jump? Do margins look plausible compared with the history? These checks take little time, and a failure on any of them makes the rest of the package harder to accept.


Loan agreements often include financial covenant terms, which are conditions the borrower must keep meeting while the loan is outstanding. A covenant may set a minimum level of liquidity or limit how much debt the company can carry relative to its earnings or equity. The levels vary a great deal from one loan to the next, so the forecast should be tested against the specific covenant, not against a general sense of what a healthy company looks like.


Investors ask somewhat different questions. They want to know how quickly the company uses cash, how long the current funds will last, and what the money will pay for. A forecast that shows the runway clearly, along with the milestones the new capital is meant to reach, gives an investor something to evaluate. A vague statement about growth does not.


Sensitivity appears in almost every serious conversation. A lender may ask what happens if collections slow by several weeks, if a major customer leaves, or if a supplier raises prices in the middle of a busy season. The owner does not need a perfect answer, but should be able to show which levers are available, such as cutting discretionary spending, drawing on a credit line, or delaying a hire. Having these answers ready signals that the owner has thought past the optimistic case.


Documentation ties it all together. Each assumption should carry its source, the person who prepared the model should be identifiable, and any uncertainty should be stated in plain words. Honest uncertainty tends to build more trust than false precision. A model that says "we do not yet know how long the new branch takes to reach steady sales" is more useful than one that pretends to know to the decimal.

Where forecasts and projections usually break down


The most frequent error is applying one growth rate to the whole year. A rate that looks reasonable for annual revenue can hide the fact that sales in one season are far lower than in another. For a construction or tourism business, a flat growth line can also hide the timing of payroll and supplier payments. The model may show a healthy year while the bank balance dips badly in one or two months.


Another common problem is leaving out items that come due on fixed dates. Payroll taxes, insurance premiums, rent, and loan payments do not follow the revenue curve, so a model that spreads them evenly will misstate the cash position. The 13-week view is useful here because it forces each payment onto a specific week. A lender who sees a forecast with no timing for taxes or debt payments will assume the model was built too quickly.


Working capital is often ignored. A company may show profit growth while its receivables stretch out and its inventory piles up. The cash needed to carry that growth does not appear as an expense, so the income statement can look strong while the bank account weakens. A careful model tracks receivable days, inventory turns, and payable terms, and it links them to the cash forecast.


Revenue timing can also create confusion. Under ASC 606, revenue may be recognized as performance obligations are satisfied, which can differ from the date a customer pays. A business that collects deposits or retainers may show revenue in one period and receive the cash in another. The forecast should explain this difference, because a lender comparing the reported revenue line with the bank deposits will notice any gap that goes unexplained.


Finally, models go stale. A forecast built in one season and never updated after month-end close will drift away from reality, and the reader will eventually notice. How often a model needs refreshing depends on how fast the business changes. Many companies refresh the near-term cash view every week and the longer forecast every month, and they note the date of each update so nobody mistakes an old model for a current one.

Who should own the model, and what to ask before hiring help


Ownership shapes the quality of the package. The owner usually makes the decisions the model describes, so the owner must understand the assumptions. A controller often maintains the books and produces the actual results that anchor the forecast. A fractional or outsourced CFO may build the forecast, explain the trade-offs, and prepare the lender package, working part-time with the company. Each role carries a different scope, and the right arrangement depends on the size of the company and the complexity of the financing.


When you interview a provider, ask how they separate forecasts from projections in their own work. A provider who cannot explain the difference clearly may produce documents that blur the two. Ask how they tie their models to the actual balances, who reviews the assumptions, and how often the models are updated after each close. These questions reveal habits that matter far more than a polished sales presentation.

How do you label forecasts and projections, and where does each label appear in the package? How do you confirm that the opening balances match the latest statements and the bank records? Which assumptions do you document with sources, and who signs off on them? How often do you refresh the 13-week view and the longer forecast? What do you include in a lender or investor package, and what do you expect from the company? How do you handle state and local tax filings in Florida, and who is responsible for them?


Be cautious with any provider who promises a specific loan approval, a funding date, or a sale price. No honest advisor can guarantee those outcomes, because lenders and buyers make their own decisions. Pricing and timelines for outsourced finance work also vary by scope and by company, and this article does not state any figures for them. Ask for a clear description of what is included, then compare proposals on the same terms.


Timing matters as much as the choice of provider. The best moment to build a clean forecast is before the loan conversation starts, not during it. A company whose books are several months behind may need to close those periods first, and that work takes time regardless of who does it. It depends on how far behind the records are, so an honest assessment of the books is the first step, before any promises about the package.


For businesses in Florida, the finance function also has to account for state and local obligations, which differ from one county to another. Florida has no personal income tax, but businesses still face other filings and payment schedules that belong in the cash forecast. The owner should confirm the specifics with a licensed tax professional, since the rules and their application depend on the company's structure and activities.

Worked example: one hypothetical loan package, from start to finish


Consider the same hypothetical building supplies distributor in Miami-Dade. It wants a credit line to buy inventory before its busy spring season, and it is also considering a Broward County branch. The owner asks for a package that a lender can read without guessing. The example below is illustrative only. It uses no real figures, and each step shows how the labels, sources, and tie-outs fit together.

Tie-out. The preparer starts from the latest balance sheet and checks that the bank balance, the receivables aging, and the inventory count match the statements. Any difference is explained in writing before the model is built, so the lender does not find it first. Near-term view. The company prepares a 13-week cash forecast, labeled as a forecast. It shows a stretch in one month when supplier payments fall due before large customer receipts arrive, which is exactly the kind of timing gap a lender wants to see. The credit line is sized against that low point, not against the average month. Scenario for the branch. The branch is shown as a projection, labeled with its condition: it opens only if the lease is signed and the branch manager is hired. The projection includes a base case with a slower ramp than the owner hopes for and a downside case where a major contractor pays later than expected. Each assumption carries its source, such as a signed lease term or a payroll estimate from the company's own pay rates. Sensitivity and repayment. The owner tests the two or three drivers that move the result most, such as collection timing and branch sales. The package then shows how the loan payments would be met under each case, and what the company would cut or delay if the downside case happened. The lender can see the plan, the risk, and the response in one place. Packaging and version control. The final file lists the date, the preparer, the sources, and a short note on what changed since the last version. It separates the historical summary, the forecast, and the projection into clearly labeled sections. The owner sends it with a short list of questions the company still cannot answer, such as the exact ramp period benefits Of a outsourced Cfo in miami the branch, because stating those openly makes the rest of the package easier to believe.


The example shows the central point of the whole article. A forecast tells the lender what the business expects from its current path, and a projection tells the lender what happens if the business takes a new one. When each is labeled, sourced, and tied back to real records, the lender can judge the company on its own terms. That is what makes the package credible, and it leaves the decision where it belongs, with the lender and the owner.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: rosarioraley5/7919benefits-of-a-outsourced-cfo-in-miami#2