Case Study 1: Why the Restaurant P&L Has Its Own Shape

The industry wrote its own chart of accounts, and the reason is a genuine argument about what a statement is for

Background

Open the default chart of accounts in almost any general-purpose bookkeeping package and you will find a structure built for a business that buys things, marks them up, and sells them. Revenue at the top. Cost of goods sold beneath it. Then a long alphabetical list of expenses — advertising, bank charges, depreciation, insurance, rent, salaries, utilities — and a net income figure at the bottom.

That statement is perfectly correct. It is also nearly useless to a restaurant manager on a Monday morning, and the reason is instructive.

The foodservice industry's answer is a purpose-built framework, published and periodically revised through the National Restaurant Association as the Uniform System of Accounts for Restaurants (commonly abbreviated USAR). Its central contribution is not a list of accounts. It is an ordering principle: group costs by who controls them and on what timescale, then subtotal at the points where a manager can actually act.

The operating issue: three things the generic statement gets wrong

It scatters the two costs that matter most. In an alphabetical expense list, food purchases and payroll sit in different places with unrelated items between them. But Chapter 1 established that prime cost — cost of sales plus total labor — is the number that predicts survival, and it is a subtotal. A statement that never computes it forces the manager to compute it themselves every week, which means most weeks nobody does.

It buries the distinction between what a manager can change and what they cannot. Rent is fixed the day the lease is signed. Food cost is decided this week, in the walk-in, by portioning and purchasing and counting. A statement that lists both as "expenses" is telling a general manager that their performance and their landlord's escalation clause are the same kind of fact. They are not, and a manager evaluated on the combined figure is being held responsible for a signature they may not have made. The USAR structure answers this with a controllable income subtotal — revenue less cost of sales, labor, and other controllable expense — which is, in effect, the line a unit manager should be judged on.

It reports too late to be operational. A monthly statement produced by an outside bookkeeper three weeks after period close describes a world seven weeks gone. Chapter 1 computed what that delay costs: seven weeks of a four-point overrun on a \$23,000-a-week restaurant is roughly \$6,400, and — worse — seven weeks of the cause running unchecked and becoming habitual. The industry's answer is not a better monthly statement. It is a weekly flash report that deliberately sacrifices precision for speed, which is a genuinely unusual thing for an accounting framework to endorse.

What it shows

First, that a chart of accounts is an argument about what to measure, not a filing system. Every grouping decision encodes a claim about who is accountable for what. Putting workers' compensation inside the labor line rather than in insurance — which Chapter 8 established for Bellwether at \$12,035 — is not a technicality. It puts workers' comp inside prime cost, which means a safety failure shows up in the number the operator watches weekly. Put it in "insurance" and it disappears into a line nobody reviews until renewal.

Second, that the industry framework exists because restaurants are structurally unusual, not because accountants were being fussy. Very few businesses simultaneously carry perishable inventory that must be physically counted, employ a large hourly workforce whose cost is decided shift by shift, collect tax they never own, and operate on a four-to-six-point margin. Each of those demands a reporting choice the generic statement does not make.

Third — and this is the limit — the framework does not make the statement true. A restaurant can adopt USAR groupings perfectly and still report a food cost that is invented, because nobody counted the walk-in. Chapter 11 made this point about the "purchases ÷ sales" shortcut and Chapter 13 made it about the physical count. The chart of accounts determines where a number goes. It has nothing to say about whether the number is real.

Outcome

The USAR groupings are now effectively the industry standard, and their vocabulary — cost of sales, prime cost, controllable income, occupancy — is what lenders, brokers, accountants, and multi-unit operators expect to see. A restaurant that presents a generic alphabetical statement in a loan application or a sale process is, at minimum, making the reader work harder than they need to, and is frequently signalling that nobody in the business reads it operationally.

Practically, most independents now run a hybrid: standard bookkeeping software configured with a foodservice chart of accounts, monthly statements from a bookkeeper for tax and compliance, and a weekly flash report the operator builds themselves because no accountant will produce something that fast.

Lesson

Group your accounts by who controls the cost and on what timescale — then subtotal where you can act.

That single sentence is the whole of the framework's contribution, and it is portable to any business. For a restaurant it produces four specific commitments:

1. Cost of sales and labor at the top, with prime cost as a subtotal, because that is the number Chapter 1 said predicts survival.
2. Controllable separated from non-controllable, so a manager is judged on what they decide.
3. Occupancy as its own line, because it explains why two restaurants at the same prime cost are in completely different positions — a point Chapter 1's Figure 1.4 made and Chapter 20's 66.3% prime-cost scenario later depended on.
4. A weekly report that is fast and approximate, sitting alongside a monthly one that is slow and exact, because they answer different questions.

And the caveat that keeps the whole thing honest: a well-structured statement built on an uncounted walk-in is a well-structured guess.

Discussion questions

1. The USAR framework's core move is grouping by controllability rather than alphabetically. Name a business outside foodservice where the same reordering would change how managers behave, and say what its "prime cost" would be.

2. Chapter 8 put workers' compensation inside the labor line rather than in insurance, which places it inside prime cost. Argue that this is the right treatment. Then argue it is misleading, and say which argument you find stronger.

3. This case study claims a monthly statement delivered three weeks late "describes a world seven weeks gone." Work out the arithmetic for Bellwether at \$29,808 a week and a three-point overrun. Is the number large enough to justify building a weekly report by hand?

4. The framework endorses a report that is deliberately approximate. Under what circumstances is a fast wrong number more useful than a slow right one — and when is it dangerous?

5. A bookkeeper tells you the foodservice chart of accounts is "non-standard" and offers to convert you to their default. Draft your reply in three sentences.

6. The lesson concedes that a chart of accounts says nothing about whether a number is real. Given that, what is the minimum set of physical procedures a restaurant needs before its statement means anything? Answer using Chapters 11 and 13.