You Opened 3 New Locations This Year. Now You Have 3 Sets of Books You Can't Trust.

Multi-location is a different financial discipline than single-location. The system that worked when you had one shop with one bookkeeper often stops working by three. The usual warning sign is a margin gap between locations that nobody can explain, because nobody can tell whether it comes from operations or from coding.

This is the architecture rebuild that fixes it.

Why one-location systems break at three

Single-location accounting can be sloppy and still work. There's only one P&L, one set of expenses, one customer base. Mistakes are obvious because numbers are small and nothing nets out.

Multi-location is different. The mistakes hide because expenses can be allocated wrong without breaking the consolidated total. A $20K expense miscategorized to the wrong location doesn't change the company P&L. Fictional example: if each location has $400K of revenue in the period, that one error makes one location look 5 points more profitable and another 5 points less ($20K / $400K = 5%). You'd never spot it in the consolidated view.

Level has not published a measured benchmark for the margin spread between best and worst locations. That includes how many multi-location operators would be in such a sample and how location margin would be defined, so this page does not cite a typical range. Some spread is real: locations have different service mixes, teams, and markets. But how much is real and how much is bookkeeping noise? Without proper architecture, you can't tell.

A practical test: move every allocated and miscoded item to a corporate/unallocated column. Then recompute each location's margin on direct revenue and direct cost only, and see how much of the gap survives.

The four mistakes that compound at multi-location

Mistake 1: Separate QuickBooks files per location

Each location has its own QuickBooks file. Locations send month-end totals to corporate. Corporate spreadsheets the consolidation.

What goes wrong:

• Chart of accounts drifts between files (different account names, different categorizations)
• Inter-company transactions are messy (location A sells to location B)
• Consolidation is manual, error-prone, late (often 30+ days after month-end)
• Comparing locations apples-to-apples is essentially impossible

This setup is common because each location often starts with its own file. For a single legal entity, it is usually the hardest to compare. If locations are separate legal entities, separate files can be correct. The fix there is a standard chart of accounts and a consolidation workflow, covered below.

Mistake 2: Shared QuickBooks file with no location classes

Single QuickBooks file. All transactions in one bucket. No way to slice by location.

What goes wrong:

• You can produce a company P&L but not a location P&L
• You're flying blind on which location is performing
• When one location underperforms, you can't diagnose why
• All decisions get made at the company level, missing local issues

Mistake 3: Location classes used inconsistently

Single QuickBooks file with location classes set up. Most transactions are coded. Some aren't.

What goes wrong:

• A "location P&L" is produced but it doesn't tie to the consolidated P&L because some expenses are uncoded or miscoded
• The numbers look reasonable until someone tries to add them up
• Managers stop trusting the location P&Ls because they don't match reality
• Eventually everyone defaults back to the consolidated view

Mistake 4: Dispatch / FSM software not feeding accounting

Each location runs its own FSM (ServiceTitan, BuildOps, Jobber, whatever). The FSMs all feed accounting differently, with different mappings, different sync issues.

What goes wrong:

• Revenue recognition timing varies by location (one location recognizes on dispatch, another on invoice, another on payment)
• Job-level cost data isn't comparable across locations
• Tech utilization stats are noisy because they're calculated differently
• You can't benchmark locations against each other on operational metrics

The right architecture

Three components, all working together.

Component 1: Single accounting system, location as a dimension

Here, a single system means one consistent accounting design. That can be one file for one legal entity, or reconciled books for separately formed entities with a consolidation workflow. A bank account or payroll run does not establish a separate legal entity.

Start with the legal structure, then pick the setup:

Confirm the specific capability of whichever product you choose with that vendor's current documentation and your CPA. This page does not certify any product's enforcement or elimination features.

Standardize:

• One chart of accounts across all locations and entities
• A location class or dimension on every transaction. Turn on any prompt or required-field setting your system offers. Then add a control that does not depend on the software: run an unclassified-transactions report before close, and resolve every unexplained unclassified item before close, retaining explicit corporate/shared-cost and approved allocation categories
• Standard naming for accounts (no "Marketing-Loc1" vs "Advertising-Loc2", pick one and use it everywhere)
• Intercompany transactions recorded to dedicated due-to/due-from accounts, with eliminations reviewed and documented at every close

This is non-negotiable: one design, applied everywhere. You can have multiple bank accounts, multiple FSMs, multiple physical offices. For a single legal entity, one file can simplify reporting; another architecture can work if it reconciles to one complete entity ledger.

Component 2: Location-level P&L produced monthly

Within 10 business days of month-end:

• Each location has a complete P&L (revenue, COGS, opex, net income)
• All locations roll up to a clean consolidated P&L
• Variance to budget by location, not just by company
• Rolling 12-month view per location

This requires the chart of accounts and class structure to be tight. You can't produce a clean location P&L if the data isn't tagged correctly.

What to track per location:

• Revenue by service line
• Direct labor and direct materials
• Allocated overhead (using a defensible methodology, direct labor hours, revenue, etc.)
• Net contribution to corporate

Component 3: Job/transaction-level operational data feeding accounting

Whichever FSM you run at each location must feed accounting consistently. Standard mapping:

• Each valid invoice maps once to AR tagged to the location; revenue recognition and cash collection are reconciled separately
• Timesheets supply job/location allocations that reconcile to payroll costs, without posting duplicate payroll expense
• POs track committed cost. Receipt, vendor bill or another qualifying accrual creates the payable under your accounting policy, not the PO alone
• Customer master is shared across locations (so you can see "Customer X buys from us at 3 locations")

If your FSMs are inconsistent across locations (one uses ServiceTitan, another uses BuildOps), this is the hardest part. Plan FSM standardization as its own project. The 6-12 month duration is a planning assumption, not a measured figure, and it runs longer than the 60-day accounting cleanup below. Until then, consistent mappings from each FSM to accounting are the minimum for comparable operational data.

The 60-day cleanup playbook

If you're sitting with the four mistakes and want to fix them, the 60 days below cover the accounting side. FSM standardization, if you choose it, starts here but finishes on its own longer timeline.

Days 1-15: Standardize the chart of accounts

Pick one chart of accounts. Force every location to migrate to it. The pain is one-time; the benefit is forever.

Days 16-30: Set up location classes / dimensions

For a single legal entity, evaluate a suitable single ledger and location dimensions, including your current edition, before deciding migration is necessary. For separate legal entities, keep each entity's books and build the consolidation workflow instead. Then tag the trailing 12 months of transactions with their location, so the reconstruction in the next step has data. Ask your CPA before editing periods that are already closed or reported on a return. Reclassing through dated journal entries or reporting-only mappings may be safer. Yes, this is grunt work. Yes, it's worth it.

For going forward: turn on whatever class prompt or required-field setting your system supports, and make the zero-item unclassified-transactions report a close requirement. No unexplained untagged transactions; explicitly retain corporate/shared costs and documented allocations.

Days 31-45: Reconstruct location P&Ls

With everything tagged, produce P&Ls for the trailing 12 months by location. Compare. The first time you see them, the variance will surprise you. Some locations will look much better or worse than you thought.

This is the data that should be driving your management decisions, not gut feel.

Days 46-60: Operational integration

Decide on a single FSM standard (or accept that you'll have multiple but enforce consistent mappings to accounting). Within 60 days, the realistic deliverable is the mapping and the decision, not a completed FSM migration. Establish standard tech utilization, job profitability, and customer-level metrics, with written definitions, that work across all locations.

After 60 days, you have:

• A controlled accounting consolidation: either one accounting file or reconciled legal-entity files, with source operational records linked for drilldown
• Location-level P&Ls
• Comparable operational data definitions, with full comparability once FSM mappings are consistent
• The ability to diagnose which location is the leak

What "good" looks like at scale

For a service business with 3+ locations:

• Monthly close in 10 business days for ALL locations + consolidated
• Location P&Ls plus a corporate/unallocated column match the company P&L within rounding (for multiple entities, after documented eliminations)
• Same KPIs reported per location (revenue per tech, gross margin, customer concentration, etc.)
• Quarterly business reviews at the location level, not just company level
• Each location manager has access to their own P&L and operational dashboard

If you don't have this, you're flying blind on where your growth is coming from and where it's leaking. Many owners find out only when they try to sell or raise capital, when due diligence forces the issue.

Calculate your multi-location readiness in 2 minutes or book a free 30-min audit, we'll review your current accounting + FSM setup, including legal-entity structure, and outline what the 60-day accounting rebuild and any longer FSM work look like in your specific case.

Related reading

• Should I open another business location?
• Job Costing for Contractors, pillar guide
• QuickBooks at $5M: scaling pain
• When to outgrow QuickBooks
• Why your QuickBooks reports lie
• Bookkeeping cleanup for service businesses