Skip to content
Multi-location restaurant group financial dashboard
Bookkeeping Financial Reporting Financials

The Complete Guide to Multi-Location Restaurant Financials

Ryan Handel
Ryan Handel

Short answer: The financial reporting problems that show up when a restaurant group grows past two or three locations are almost never about the software. They're about inconsistency: a different chart of accounts at each store, sales recorded differently by each POS, payroll split across entities, vendors invoicing whichever location is convenient, and intercompany transfers nobody reconciles. Fix the structure first (one chart of accounts, one sales journal format, one close calendar, one vendor process, entity-level books that consolidate cleanly) and the reporting problems mostly disappear. Then the software choice is easy.

I've watched a lot of two-location operators become six-location operators, and the finance conversation changes in a predictable way. At one location you want to know if you made money. At three you want to know which store is winning and why. At six you want a package you can hand to a lender, a partner or a new director of operations without a twenty-minute explanation. This guide is the structure that gets you there, in the order I'd build it.

What financial reporting challenges do multi-location restaurant operators actually face?

When I ask growing groups what's wrong with their reporting, the answers cluster into six problems. Notice that none of them are "we need a better dashboard."

  1. Stores aren't comparable. Location A books paper goods to supplies, location B books them to COGS. Location C runs a different POS with different sales categories. Side-by-side comparison is meaningless until the categories match.
  2. Sales don't reconcile. Delivery payouts, gift cards sold at one store and redeemed at another, catering deposits, and processor fees all make "sales" a fuzzy number if the sales journal isn't built the same way everywhere.
  3. Payroll crosses entities. A GM who covers two stores, a shared catering team, or a central kitchen means labor has to be allocated, and most groups either do it by feel or not at all.
  4. Vendors and AP are fragmented. Each store gets its own invoices, pays on its own schedule, and the group has no consolidated view of what it owes or what it's paying per case across stores.
  5. Intercompany balances are never cleared. Store A paid store B's produce invoice. Corporate covered a payroll shortfall. Those become "due to / due from" balances that sit on the balance sheet for years.
  6. Consolidation happens in a spreadsheet. Someone exports five P&Ls and pastes them together, so the consolidated view is always a week late and always slightly different from the sum of the parts.

How should a growing group structure its books?

Here's the order of operations. Do these in sequence, because each one depends on the one before it.

Step 1: One chart of accounts, applied everywhere

Build one restaurant-specific chart of accounts and make it non-negotiable at every location. Sales broken into food, beverage (with alcohol separate if you serve it), delivery, catering and other. COGS matched to those sales categories. Labor split into front of house, back of house, management, payroll taxes and benefits. Occupancy, operating expenses and delivery platform fees on their own lines. If a new location wants a special account, the answer is usually no. Comparability is worth more than precision on a small line.

Step 2: One sales journal format, from the POS

Every store should produce a daily or weekly sales journal in the same layout: gross sales by category, discounts and comps, sales tax collected, tips collected, and tenders (cash, card, delivery platforms, gift cards) so each tender reconciles to its own deposit. If your locations run different POS systems, the journal format is where you normalize them. We covered the mechanics in why your sales and bank deposits don't match and the delivery reconciliation guide.

Step 3: Entity-level books that roll up

Most groups end up with an LLC per location, sometimes a management company on top. Keep a full set of books for each entity, on the same chart of accounts, and consolidate at the reporting layer rather than merging the books. That keeps your tax filings clean, keeps partners with different ownership percentages happy, and still gives you one group P&L. Intercompany transactions get their own accounts and get cleared monthly, not annually.

Step 4: One close calendar

Pick monthly or 13 four-week periods (we prefer periods for restaurants, and explain why in 13-period accounting for restaurants) and close every location on the same schedule with the same deadline. A group can't have a consolidated close that's faster than its slowest store, so the calendar is what forces discipline on invoice submission and inventory counts. Our standard is a finished P&L within five business days of period close, for every entity, so the consolidated package is ready the same week.

Step 5: Centralized vendor and payment process

Route all invoices through one intake process, code them to the right location and account, approve them against a rule set, and pay on one weekly run. That gives you consolidated AP, per-location purchasing visibility, and the ability to negotiate on group volume. If you're still paying from each store's checkbook, read the complete guide to restaurant AP automation before you add another location.

What do consolidated financial statements show a restaurant group?

Consolidated statements are the group's financials as if it were one business: every entity's P&L and balance sheet added together, with the money that only moved between your own companies taken out. They're how you see the whole group at once, and how a lender or partner will read it.

  • Consolidated P&L. Sales, COGS, labor, operating costs and profit for the whole group, with each location in its own column next to the total. The columns show you which stores carry the group; the total shows what the group actually earns.
  • Consolidated balance sheet. Cash, inventory, payables, loans and equity across every entity, so you can see the group's real cash position and debt load instead of piecing it together from five bank logins.

Location view vs entity view

These are two different cuts of the same books, and a group needs both. The location view is operational: one column per store, so you can compare prime cost, labor and margin between restaurants. The entity view is legal and tax: one set of statements per LLC, which is what your CPA files from and what partners with different ownership stakes are paid from. Usually the two line up one to one, but not always. A management company, a central kitchen or a commissary is an entity with no dining room, and two concepts can share one LLC. Set up your chart of accounts and location tracking so the books can produce both views without a spreadsheet.

Intercompany eliminations

When one of your entities pays another, the group as a whole hasn't earned or spent anything. Consolidation removes those transactions so they don't inflate sales or expenses. The common ones in restaurant groups:

  • Management fees. The management company charges each store a fee. It's income for one entity and an expense for the others, and it nets to zero at the group level.
  • Shared purchasing. One entity buys for several stores and bills them back, or a central kitchen sells product to the restaurants. Without an elimination, the group counts the same sale and cost twice.
  • Loans between entities. Store A covers store B's payroll, or the parent company funds a new opening. That's a receivable on one balance sheet and a payable on the other, and the two should match to the penny every period.

If the two sides of an intercompany balance don't match, something got booked on one side and not the other. Find it before you consolidate, not after.

What should a group review every month?

Once the consolidated statements are ready, walk them in the same order every period:

  1. Consolidated profit against budget and last year, then the location columns to see which stores drove the change.
  2. Prime cost by location, looking for the store that's drifting.
  3. Consolidated cash and debt, and whether the group can cover payroll, rent and vendors through the next quarter.
  4. The intercompany schedule: every balance should match its other side and be shrinking, not growing.
  5. Shared costs and management fees, to confirm they were allocated on the stated basis.

What should the monthly reporting package contain?

Once the structure is right, the package is straightforward. This is what a six-location group should be able to open, in one place, within a week of period close.

ReportLevelWhat it answersFrequency
P&L by location, side by side, with percentagesLocation and consolidatedWhich stores are winning and where the margin gap isPeriod
Prime cost trendLocationIs COGS plus labor drifting, and at which storeWeekly and period
Balance sheet by entity, with intercompany scheduleEntity and consolidatedWhat each entity owns and owes, and who owes whom inside the groupPeriod
Cash position and 13-week cash viewConsolidatedCan the group cover payroll, rent and vendors through the quarterWeekly
Delivery platform reconciliation summaryLocationGross delivery sales, fees, refunds and chargebacks per platformPeriod
AP aging and vendor spend by categoryConsolidated with location detailWhat's owed, what's overdue, what each store pays per unitWeekly
Weekly KPI flashLocationSales, labor and purchases against last week and budget, before the period closesWeekly

If you only build two of these, build the side-by-side P&L and the weekly KPI flash. The first is how you manage the group; the second is how you catch problems before the period P&L makes them permanent. We wrote a template for the flash in the restaurant weekly flash report.

How do you handle payroll and shared costs across locations?

Allocate, don't guess. Shared labor (a regional manager, a catering team, a central kitchen) should be booked to a shared-services entity or cost center and allocated to locations on a stated basis: hours worked, sales, or a fixed percentage. Write the basis down and apply it the same way every period. The same rule applies to shared marketing, insurance and software. The goal is that each location's P&L reflects its real cost to operate, so a store that looks profitable is actually profitable after its share of the overhead.

When do you need software built for multi-location groups?

Later than most people think. In my experience, QuickBooks Online with one file per entity, a consistent chart of accounts, and a reporting layer on top can carry a group a long way, often into the low double digits of locations, provided the bookkeeping is disciplined. Platforms like Restaurant365 or Sage Intacct earn their cost when you have in-house accounting staff to run them, need inventory and labor in the same system as the ledger, or are past that size. We compared the options in best Restaurant365 replacements for small groups. The short version: buy structure first, software second.

Is your group's reporting still living in a spreadsheet?

FIXE is restaurant bookkeeping software with the bookkeeper included, trusted by 600+ restaurant locations. Book a demo and we'll show you what a side-by-side package looks like for your group.

Book a demoTake the free Health Score

Frequently asked questions

What financial reporting challenges do multi-location restaurant operators face as they grow?

Inconsistent charts of accounts across stores, sales journals that differ by POS, payroll and shared costs that cross entities without allocation, fragmented vendor payments, uncleared intercompany balances, and consolidation done by hand in spreadsheets. Each one makes locations harder to compare and the group harder to finance.

Should each restaurant location have its own set of books?

Yes, if each location is its own legal entity, which is the common structure. Keep full entity-level books on a shared chart of accounts and consolidate at the reporting layer. That preserves clean tax filings and partner reporting while still producing one group P&L.

What are consolidated financial statements for a restaurant group?

They're the group's P&L and balance sheet presented as if every location and entity were one business, with transactions between your own companies (management fees, shared purchasing, loans between entities) eliminated. They give you and your lender one view of what the group earns, owns and owes, with location columns that show which stores drive the result.

How do you consolidate financials for a restaurant group?

Standardize the chart of accounts and close calendar first, book intercompany transactions to dedicated accounts, then produce consolidated statements that sum the entities and eliminate intercompany balances. With consistent books this is a report, not a project. With inconsistent books it's a monthly spreadsheet exercise that's always slightly wrong.

How fast should a multi-location group get its consolidated P&L?

Within five to ten business days of period close, with the location-level statements finished first. The consolidated view can't be faster than the slowest store, which is why a single close calendar with hard deadlines matters more than any software feature.

Can an outsourced bookkeeping service handle multi-entity restaurant groups?

A restaurant-native one can, and for growing groups without in-house accounting staff it's often a better fit than hiring a controller and buying a platform. Look for entity-level books on a shared chart of accounts, a stated close timeline that applies to every entity, consolidated AP with location coding, and side-by-side reporting as standard output. That's how FIXE runs books for groups, and you can see plan pricing per location on the pricing page.

More on Reading Your P&L and Reports

About the author
is the co-founder and CEO of FIXE. He spent more than 20 years in the restaurant industry before starting FIXE, which now does the books for 600+ restaurant locations. Connect with Ryan on LinkedIn.

Share this post

{{ footer_js() }} {{ js_integration_body_end() }}