Scaling to multiple locations? Your accounting needs to keep up

What changes when you open location 2, 3, or 5

Single-unit accounting is straightforward: one POS, one bank account, one P&L, one set of weekly numbers. Add a second location and you immediately need to answer questions the first unit never asked — which location drove food cost this week, which GM is running heavy on labor, where cash is piling up, and whether the new unit is profitable on its own or only on paper.

Multi-location operators often start by duplicating what worked at unit one — same POS, same vendors, same bookkeeper — and discover that consolidated reporting does not happen automatically. Each location generates its own sales, payroll, and invoices. Without structure in QuickBooks Online, everything lands in one bucket and unit-level decisions become arguments instead of data.

Scaling to five or more locations adds entity complexity — separate LLCs, shared commissary costs, intercompany transfers, and regional managers who need visibility without drowning in spreadsheets. Accounting has to be designed for multi-unit from the start, not retrofitted after the third opening.

Class tracking vs separate QuickBooks files

QuickBooks Online offers two common patterns for multi-location restaurants. Class tracking (or location tracking in QBO Plus/Advanced) puts all entities in one company file, with each transaction tagged to a location or class. Separate QBO company files give each legal entity its own books, with consolidation happening outside QBO or through reporting tools.

One file with classes works well when locations share ownership, vendors, and payroll infrastructure and you want one login with location-filtered P&L. Separate files fit when each location is its own LLC with distinct banking, tax reporting, and equity structure — common in franchise-style growth or investor-backed roll-ups.

There is no universal right answer. The wrong answer is mixing approaches — some expenses tagged by class, some locations in separate files, commissary charges handled inconsistently — so no report ties cleanly. FinAcct360 helps set up and maintain the structure that matches how you actually operate, then closes every unit every week.

Consolidated reporting without losing unit detail

Owners and regional managers need both views: unit-level P&L, food cost, and labor for each GM, and consolidated revenue, prime cost, and cash for the group. Weekly reporting should roll up automatically — not require someone to paste five spreadsheets into a master tab every Wednesday.

Consolidation also means consistent chart of accounts across units. If Location A posts produce to "Food COGS" and Location B posts the same vendor to "Cost of Goods Sold — Food," consolidated food cost is unreliable. FinAcct360 standardizes account mapping during onboarding so weekly KPIs compare apples to apples.

Intercompany and commissary flows need explicit rules. When a central kitchen bills units for prep, or units share a catering commissary, those transfers must post correctly or unit margins lie. Weekly closes catch drift in those transfers before they become year-end journal entry nightmares.

How FinAcct360 handles multi-location setups

FinAcct360 supports single-unit operators, multi-unit groups with one QBO file and class/location tracking, and multi-entity setups with separate QuickBooks company files consolidated in the client portal. Mike Davis-style operators with three distinct locations each with their own client record see consolidated KPIs alongside unit detail — the same experience whether you have two units or ten.

Each location gets the same seven-stage weekly close: POS validation, bank reconciliation, expense classification, payroll review, and KPI reporting. Accountants assigned to your group know your structure — which POS each unit runs, how deposits flow, and which classes or entities map where.

The client portal shows location comparison for multi-unit clients — revenue, food cost, labor, and prime cost side by side for the same week. You see which location led and which lagged without requesting a custom report from the bookkeeper.

POS, payroll, and banking across units

Multi-location POS setups vary: one Toast instance with revenue centers, separate Square accounts per unit, or a mix after acquisitions. FinAcct360 reconciles each unit's POS to its QBO location or entity every week — the same discipline as single-unit, repeated per connection.

Payroll may run centralized or per location. Either way, loaded labor must land in the right unit for labor percentage to mean anything. Bank accounts often multiply faster than GMs — operating accounts, reserve accounts, and credit cards per unit all need weekly reconciliation tied to the correct location tag.

Growth through acquisition makes this harder. When you buy an existing restaurant with its own QBO file, POS, and payroll vendor, consolidation does not happen on closing day. FinAcct360 maps each unit into a consistent reporting structure so your weekly numbers stay comparable as the group grows.

Grow without flying blind

Your accounting structure should be ready before location two opens — not rebuilt after location four underperforms and nobody knows why. Class tracking, entity setup, consolidated weekly P&L, and unit-level food and labor KPIs are infrastructure, not back-office luxury.

FinAcct360 builds and maintains that infrastructure on QuickBooks Online, with weekly delivery every Wednesday by 2 PM ET and accountants who specialize in restaurant multi-unit operations. Scale the restaurant group; we scale the close.