What We See Inside a Restaurant Group’sFinancials in the First 30 Days – and What It Tells Us

In the first week of every engagement, we look at the chart of accounts, because it is the structural foundation everything else flows through; and in most groups we enter, it was built — or imported from a previous system — with compliance as the primary objective, not management.

The compliance objective is met; the books close, taxes file, and the P&L satisfies the CPA. The management objective is not met, because compliance and management are different purposes that require different structures, and a chart of accounts designed for one rarely serves the other without deliberate redesign.

The tell is always in the line items; labor as a single expense category with no separation by role, food cost blended with paper goods, delivery revenue folded into general food sales without a separate line for platform fees. These structural choices mean the reports the business produces cannot answer the questions that actually matter — which location is running high on back-of-house labor, what the effective delivery margin looks like after commissions, how prime cost breaks down by concept rather than by portfolio.

We ask every group we enter the same question; how long does it take to close a period? The answers range from 7 days to 25 days, and groups on the longer end almost always offer the same explanation: the team is working hard, there is a lot of data to reconcile, and it just takes time.

When we look closer, the cause is almost always structural rather than operational; the close is long not because there is a lot of data, but because the data is assembled manually from disconnected systems. POS exports that have to be reformatted before they can be used. Payroll runs that do not connect to the accounting system. Vendor invoices that sit in an email inbox until someone processes them. Each manual step adds time and introduces the possibility of an error that will need to be found and corrected before the close is valid.

This is the pattern with the most direct and immediate financial consequence, because the gap between what the group thinks it knows about its prime cost and what is actually happening at the unit level is almost always larger than leadership expects.

We enter a group, look at the reporting structure, and find that prime cost is calculated and reviewed as a single portfolio number; the group knows its overall prime cost, but does not know the prime cost of Location 4 versus Location 11 versus Location 19. When we build that location-level view — which typically takes a few days of data work to construct — the variance is significant in nearly every case.

Third-party delivery now represents a meaningful share of revenue for most QSR and casual dining groups, and in most groups we enter, the accounting treatment of that revenue is somewhere between imprecise and structurally broken; platforms remit on their own schedule, net of fees, with commission structures that vary by market, by platform, and sometimes by location, creating a reconciliation gap that distorts location-level revenue figures and food cost percentages in ways that affect every management decision made from those numbers.

In the first 30 days, we always ask the same question; what happens if your controller leaves? The honest answer, in most groups, is that it would create a serious operational problem, because the close process lives in that person's head, the spreadsheet model was built by that person and maintained by that person, and the vendor relationships, the payroll schedule, and the reconciliation workflow are all dependent on that person's continued availability and institutional knowledge.