1 Multi unit franchisee cash flow planning: 13 week view by unit
mariquisenberr edited this page 3 hours ago


Multi unit franchisee cash flow planning is the practice of forecasting the cash each location brings in and sends out over the next 13 weeks, then adding the units together to see where the group stands. Get this in place first, before you decide on new hires, equipment or a second location.

This matters most when your units do not earn or spend on the same calendar. A seasonal location and a steady one can both look healthy on a monthly total while one of them runs short every February. A 13-week view makes that gap visible while there is still time to act.
What a 13-week view by unit shows that a monthly total hides
A monthly profit and loss statement tells you how the group did last month. It does not tell you whether the second unit will cover its rent on the first Monday of next month. Those are different questions, and owners who answer only the first one often learn about a shortfall after the money has already left the account.

Thirteen weeks is a useful horizon for most small multi unit groups. It is long enough to show a seasonal dip, a royalty payment and a lease renewal in the same view. It is short enough that the numbers stay tied to actual bookings, known supplier terms and the staff schedule you already have. Longer forecasts tend to rest on guesses that nobody revisits.

The "by unit" part is where the value sits. Totals blend a strong location with a weak one. A group can show healthy cash at the consolidated level while one unit draws down its reserve every week. If you cannot see that unit on its own line, you will move money from one place to another without knowing why.

Decide what the forecast must answer before you build it. Useful questions are whether any unit falls below its minimum cash in the next 13 weeks, which week that happens, and which obligation triggers it. A forecast that answers those three questions is worth the time. One that only fills a grid is not.

Be clear about what the view cannot do. It cannot predict a slow season nobody has seen yet, or a sudden change in local traffic after a road closes or a competitor opens nearby. It shows the cash you can see now, arranged by week, so the gaps become visible. Treat it as a planning tool, not a promise about the future.
Set up the unit ledger before you build any forecast
Before the first projected dollar goes into a cell, get your books into a shape that supports unit-level reporting. Each franchised location needs its own accounts or, at minimum, its own class or location tag in your accounting system. A package such as QuickBooks can handle class tracking for a small group, and larger groups often move to NetSuite or Sage Intacct as the unit count grows. The tool matters less than the discipline of tagging every transaction the same way.

Start with a clean opening balance for each unit's bank account. Reconcile each account to its bank statement, then record that balance as the starting point of the forecast. If the opening number is wrong, every week after it inherits the error. Many owners skip this step because it feels like bookkeeping, but it is the foundation of the whole exercise.

Next, work through a short setup list:

Confirm which bank accounts belong to which unit, and whether any account is shared. Map each recurring expense to one unit, and flag costs shared across units, such as corporate software or a regional manager's pay. Agree on a minimum cash balance for each unit, the amount that must stay in the account before anything else is spent. Set the week that starts the forecast, and keep that date fixed for the whole cycle. Write down who owns each unit's numbers, so that questions go to one person.


Shared costs are the usual trouble spot. Allocate them with a simple rule and write the rule down. Splitting by sales share, by unit count or by headcount can all work. What matters is that the rule stays stable, benefits of a outsourced CFO in Miami so that changing it does not make last quarter look better or worse than it was.

Florida adds a layer that owners sometimes overlook. Sales tax is filed with the Florida Department of Revenue, and the filing schedule depends on the tax liability of each registration. If each unit files separately, each unit needs its own sales tax line and its own due date. Check your own registrations and your own dates, because the schedule is not the same for every business.
Forecast weekly receipts for each unit from its own sales pattern
Receipts are where most forecasts fail, because owners project the sales they hope for instead of the sales they have seen. Start with the last full year of actual deposits or point-of-sale totals for each unit, not the annual budget. Look for the shape of the year: the holiday spike, the slow weeks that follow it, and the summer dip if your market has one.

Card settlements and bank deposits do not always line up with the day of sale. Card money can arrive a day or more after the transaction, and cash may be deposited on a different day than the register closes. Forecast receipts on the day the money lands in the account, not the day the sale happened. That is the number that pays bills.

Use the historical pattern, then adjust it for what you know. If a unit is adding a service line next month, give that line its own row and a note about where the estimate came from. If a construction project is blocking the entrance to a location, say so in the note and reduce the expected traffic. Every adjustment should be visible, so that someone else can question it later.

Keep the weeks you are least sure about in a range. A single point estimate hides risk. Build a base case that follows the historical pattern and a weaker case that assumes the slowest recent weeks repeat several times in a row. You do not need a complicated model for this. Two rows per unit are enough to show the spread.

Leave out anything that depends on something that has not happened yet, such as one large order, a new corporate account or a promotion you have not run. Put those items in a separate note. When they arrive, move them into the base case. This habit keeps the base case honest and stops the forecast from flattering the group.
List every outflow by unit, including the ones that land on fixed dates
Outflows are easier to forecast than receipts, but owners still miss the large ones. Start with the fixed items: rent, loan payments, insurance premiums, payroll and software subscriptions. Each has a due date, which means you can place it in the correct week. Assign each fixed item to the unit it belongs to, and mark the week it leaves the account.

Franchise-specific charges need their own attention. Royalties, marketing fund contributions and technology fees follow the franchise agreement, and their timing can differ from the rest of your bills. Read your agreement and list each charge with its trigger, whether that is a percentage of sales, a flat amount or a monthly fee. Then place it in the week the franchisor collects it, not the week you remember it.

Variable costs usually follow sales. Product, labor hours and card processing fees rise and fall with volume. Link them to the receipts row for the same unit, so that a weak week reduces both sides of the forecast. This is the difference between a forecast that gets worse with the business and one that stays optimistic on the expense side.

Do not forget the irregular items. Equipment repairs, license renewals, tax filings, seasonal hiring rounds and trade show deposits all arrive at uneven times. Keep a list of known irregular payments for the full 13 weeks and review it every week. A surprise that appears on a list you already keep usually means the list was not reviewed.

Payroll deserves its own check. Confirm the pay calendar, the taxes withheld and the timing of the tax deposits for each unit or for the group. A payroll week that lands on a low receipts week is the most common cause of a short balance. Flag those weeks so they stand out when you review the forecast.
Roll the forecast forward each week and record what changed
A 13-week forecast is useful only if it stays current. Each week, drop the week that just ended, add a new week at the far end, and replace the projections for the closed week with actual figures. This is called a rolling forecast, and it keeps the horizon at 13 weeks without a full rebuild each time.

Set a fixed weekly routine and keep it short. Most small groups can run this sequence:

Pull the bank balance for each unit on the same morning each week. Compare actual receipts and payments with the forecast for the week that just closed. Write one sentence for each variance above the threshold you agreed on. Update the remaining weeks for any change in known timing or known amounts. Check the lowest projected balance for each unit and note the week it occurs.


Record each variance with a reason, not just a number. A receipts shortfall caused by a dining room closed for two days is different from one caused by weaker demand. The first is temporary and the second may repeat. A short note tells you which assumption to revise, and over several cycles those notes become the best local planning data you have.

Keep a variance log with dates and names. If a supplier moves a payment from the first of the month to the fifteenth, write that down on the day you learn it. Owners who skip this step often find that the forecast changed without anyone deciding to change it, and then the group loses track of why it looks different from last week.

Watch for drift. If the forecast misses in the same direction for several weeks, the method is wrong, not the luck. Common causes include an old sales pattern, a timing error on receipts, or a cost allocated to the wrong unit. Fix the cause in the model and keep going. Do not average the errors away, because the average hides the pattern you need to fix.
Compare units side by side to decide where cash should go
Once every unit has its own line, you can compare them. The useful question is not which unit earns the most. It is which unit has the thinnest cushion, which one turns cash fastest, and which one depends on help from the others. Those answers shape what you do with spare cash, delayed hires and new spending.

The table below compares three hypothetical units on the same attributes. Use the same columns for your own units, and fill them from your forecast rather than from memory.

Unit Weekly cash pattern Lowest projected week Main fixed obligation Action before the low week

Unit A (hypothetical, mature) Steady deposits with little seasonal swing The week after a quarterly insurance payment Rent and loan payment Keep the reserve intact and avoid new commitments that week

Unit B (hypothetical, seasonal) Strong in peak months, thin in the off season The slowest month, when payroll falls due Payroll Schedule staffing around the slow weeks and move discretionary buys

Unit C (hypothetical, new) Receipts still ramping toward the base case Early in the cycle, after the lease clears Lease and build-out loan Delay nonessential purchases until receipts reach the base case


After the table, read it for the pattern, not the single cell. A unit with a thin cushion does not necessarily need a fix, and it may only need a timing change, such as moving a purchase or asking a supplier for different terms. A unit that draws down its reserve every week needs a deeper look. Decide what each unit can handle on its own before you consider moving cash from one to another.

Moving cash between units is a decision with rules. Some franchise agreements, loan covenants and internal policies limit transfers, and some lenders expect the borrowed funds to stay with the entity that borrowed them. Read those limits before any transfer. Write down the reason and the week in the forecast, so the transfer shows up where it belongs.

Be wary of the group view that hides a problem. A healthy consolidated balance can sit alongside a unit that is short every other week. If you use the total to justify new spending, you may be funding one location with another without making a deliberate decision. Keep the unit view in front of you whenever you decide where the money goes.
Use the forecast in lender and investor conversations
A lender or investor wants to know whether the business can meet its obligations and what happens if sales slow. A 13-week view by unit answers both questions in a form they can check. It does not guarantee a yes, but it makes the conversation concrete. Bring the forecast with the assumptions written next to each line, not in a separate memo nobody reads.

Prepare three items before the meeting: the forecast with its base and weaker cases, a short note on the main assumptions, and the variance log from the last several cycles. The variance log matters because it shows that you compare plans with results. Many owners leave it out, and that is a mistake, because it is the evidence that the forecast is tested.

Expect questions about the weakest week and what you would do about it. Have an answer ready. You might say you would delay a hire or defer a purchase, and that the reserve in each unit covers the gap. Say only what you have actually agreed to do. A promise you cannot keep damages the relationship faster than a thin balance does.

Be clear about what is historical and what is projected. Lenders often ask for financial statements prepared under the accounting standards the business uses, and an outside accountant may review them. Keep the forecast separate from the statements and label each one. If a lender asks for reports on a set schedule, match your forecast cycle to that schedule so the numbers can be compared directly.

Investors read the same forecast with a different question: how the cash supports growth and how much runway the plan leaves. Show each unit's contribution to that runway, and say which units you would expand, hold or fix first. That answer is more useful than a single growth figure, and it avoids promising results you cannot control.
A worked example: one hypothetical three unit franchisee reads its 13-week view
Consider a hypothetical franchisee with three units in South Florida. Unit A is a mature location with steady weekly deposits. Unit B is seasonal, with stronger weeks in the winter tourist months and a slow stretch in the summer. Unit C opened recently and is still building its receipts. The owner wants to know whether to hire a second shift manager for Unit B before the slow stretch arrives.

The owner starts with the unit ledger. Each bank account is reconciled, and a minimum cash balance is set for each unit. Receipts for Units A and B come from the last full year of deposits. Receipts for Unit C come from its first months Benefits Of A Outsourced Cfo In Miami actual sales, with the base case set below its early pace. Fixed obligations go into the weeks they leave the account, including the quarterly insurance payment for Unit A and the lease for Unit C. Royalties go into the week the franchisor collects them.

The forecast shows that Unit B's lowest balance falls in the ninth week, when a payroll run and a loan payment land together. Unit C dips below its minimum in the fourth week, which is a timing problem rather than a sales problem. Unit A holds steady throughout. The owner now knows which unit needs attention and when, which is more than a single consolidated total could have shown.

The owner delays the Unit B hire by a few weeks, which keeps the new payroll out of the lowest week. The owner also moves a discretionary equipment purchase for Unit C to the week after its lease clears. Both changes go into the variance log with dates and reasons. Cash is not moved from Unit A to cover Unit C without a documented decision and a check of any loan limits that apply.

Each week after that, the owner rolls the forecast forward, compares actual results with the base case, and updates the notes. If Unit B's summer receipts come in below the weaker case, the owner has a clear trigger to act, and Unit A's reserve is no longer the only plan. The example shows the method at work: a unit-level view, a fixed weekly routine and decisions written down before the money is due. It promises no particular result, but it gives the owner the timing to act.