Overview
- Why second-location bookkeeping problems don't surface until month five or six, not right away
- The five specific setup mistakes that cause it — chart of accounts, shared costs, labor tracking, blended bank accounts, and single-location reporting
- A side-by-side comparison of what worked at one location versus what breaks at two
- A checklist to run through if you're already several months into a second location and something feels off
Why the problems don't show up right away
The first month or two after opening a second location are usually consumed by the opening itself: hiring, training, working out kinks, and an owner who's physically present at both locations far more than will be sustainable long-term. Total revenue is up, which feels like validation, and it's easy to read that as things going well.
By month three or four, the initial routines settle in, but the underlying setup issues, an unrebuilt chart of accounts, shared costs nobody's actually allocating, labor recorded as one lump number, are still invisible in a monthly total. Total revenue and total expenses can look completely normal even while the two locations' individual pictures are quietly wrong.
By month five or six, there's usually enough accumulated data that someone, the owner, a bookkeeper, or an accountant preparing a quarterly review, actually looks at the location-level detail and finds a gap too large to ignore.
The five mistakes that surface by month six
Mistake 1: The chart of accounts wasn't rebuilt for multiple locations
A single-location chart of accounts usually has no location dimension at all, because it's never needed one. Add a second location without restructuring, and every transaction lands in the same undifferentiated accounts. There's no clean way to produce a location-level P&L after the fact, because the data was never captured with a location attached to it in the first place.
What to do instead: every transaction should carry a location tag, class, or department from the first day the second location opens, not reconstructed months later from memory and bank statements.
Mistake 2: Shared costs were never actually allocated
Management salary, central purchasing, marketing, insurance, and sometimes a shared prep kitchen or commissary all benefit both locations, but they often get recorded entirely against whichever location happens to pay the bill. Six months in, this shows up as one location looking artificially unprofitable, because it's absorbing costs that belong partly to the other one, while the other location looks artificially strong.
What to do instead: pick a specific allocation method, percentage of sales, headcount, or square footage are all reasonable depending on the cost, and apply it the same way every month. The exact method matters less than picking one and actually using it consistently.
Mistake 3: Labor wasn't tracked by location
Managers and staff who split time across both locations, or a single payroll run covering everyone, often get recorded as one combined labor expense. By month six, labor cost percentage per location is effectively a guess, which makes it impossible to tell whether one location is overstaffed, understaffed, or running exactly as expected.
What to do instead: track hours and pay by location at the time payroll is actually entered, not reconstructed later from schedules or best recollection.
Mistake 4: Bank accounts and cash flow got blended
Running both locations through one shared bank account feels simpler in the early months. It also means the business can look like it has healthy cash overall while one location is quietly draining the other, and nobody notices until the gap is significant.
What to do instead: separate bank accounts, or at minimum clear per-location cash tracking within one system, so each location's actual cash position is visible on its own, not just as part of a combined total.
Mistake 5: Reporting stayed built for one location
A P&L format built for a single restaurant doesn't automatically produce a side-by-side comparison once there are two. Without that direct comparison, an owner ends up eyeballing two separate reports rather than seeing them next to each other, and the kind of allocation errors described above are much harder to spot without that side-by-side view.
What to do instead: build reporting that shows both locations next to each other from the start, not two standalone reports that require manual comparison.
Single-location setup vs. what two locations actually need
| Area | What worked for one location | What breaks at two | What to do instead |
|---|---|---|---|
| Chart of accounts | No location tagging needed | All activity blends together; no clean per-location P&L is possible | Add a location tag or class to every transaction from day one |
| Shared costs | Fully absorbed by the one location that existed | Dumped onto whichever location happens to pay the bill | A documented allocation method, applied the same way every month |
| Labor | One combined payroll expense | Impossible to see true per-location labor cost or staffing efficiency | Track hours and pay by location at the time of entry |
| Cash | One bank account, one cash position | One location can drain the other without anyone noticing | Separate accounts, or clear per-location cash visibility |
| Reporting | A single P&L | No side-by-side comparison; misallocations stay invisible | Location-level reporting built to compare side by side |
What to check if you're already six months in
The fastest way to check is to run through the five mistakes above as a checklist against your own books, rather than treating this as a separate diagnosis. Pull each location's P&L and try to put them side by side. If you can't do that cleanly, that's mistake five showing up. From there, check whether any shared cost has actually been allocated at all, or whether it's all landed on one location by default, that's mistake two. Check whether labor is broken out by location or still blended into one number, that's mistake three. Check whether your cash visibility is actually separated or just combined into one running total, that's mistake four.
Frequently asked questions
How should I set up my chart of accounts for a second restaurant location?
Add a location dimension, tag, or class to every account so transactions can be filtered and reported by location, rather than building an entirely separate, duplicate chart of accounts for each location.
How do I allocate shared costs across locations?
Pick one consistent method, percentage of sales, headcount, or square footage are all reasonable depending on the cost, and apply it the same way every month. The specific method matters less than choosing one and staying consistent with it.
How do I know which location is actually profitable?
You need three things working together: location-tagged transactions, a consistent shared-cost allocation, and labor tracked by location. Without all three, a location-level P&L is really just an estimate, not a reliable number.
Is it too late to fix this if it's already been six months?
No, but it usually means going back and reallocating the months already recorded, not just correcting things going forward. The earlier this gets addressed, the less retroactive untangling is required.
Do I need completely separate books for each location?
Not necessarily separate books, but transactions do need to be tagged or classed by location within one consistent system, so each location can be reported on separately whenever it matters.
What to do next
If your second location still feels messier than it should six months in, that's usually a setup problem, not an effort problem. The Food Bookkeeper helps growing restaurant groups rebuild their chart of accounts, shared-cost allocation, and reporting before it becomes a much bigger project at location three.
