Should multi-location clients use a single rent expense account or separate accounts by location?

A single parent rent expense account split by class or location dimension. Separate accounts for each location bloat the chart of accounts and make consolidated reporting harder. Most modern accounting platforms support a location dimension that lets the firm filter the same account across locations. Use the dimension; keep the account count low.

How do you separate base rent from CAM, taxes, and insurance pass-throughs in coding?

Two parent accounts work for most clients: base rent and operating expense pass-through. Base rent holds the contractually fixed monthly amount. Operating expense pass-through holds CAM, taxes, insurance, and any other variable lease charges. This separation makes year-over-year analysis cleaner and isolates the variable charges that are most likely to need review.

What about percentage rent and reconciliation true-ups across multiple locations?

Percentage rent gets its own sub-account under base rent because it is contractually defined and tied to sales. CAM true-ups flow through the operating expense pass-through account in the period they relate to. Both should be coded by location dimension so the management report can show occupancy cost by location accurately.

How do you handle a CAM red flag when it appears on only one location's bill?

Same escalation as a single-location client. Code the bill by location, preserve the document, and flag the location where the issue appeared. The flag does not migrate across locations because each location has its own lease. The firm's consolidated review can compare patterns across locations and identify systematic landlord issues if one landlord controls multiple locations.

When does multi-location occupancy coding warrant a fractional CFO or controller engagement?

When the client operates from four or more locations, has more than $400,000 in annual occupancy expense, or has experienced two or more landlord billing disputes in the prior 24 months. At that point, the bookkeeping volume and the contract complexity exceed what a recurring monthly engagement typically covers, and a fractional controller engagement adds clean structure.

Multi-Location Clients: How to Keep Occupancy Coding Consistent

The client opens a fourth location. The chart of accounts that once fit on one screen now reads like a phone book. Three landlords, three lease types, four CAM reconciliation seasons. CAM means common area maintenance, the shared costs a landlord bills back. A reconciliation is the yearly statement that trues up what a tenant owes. The bookkeeper opens the GL in March and tries to recall which CAM bill goes with which location. And which one had the management fee question last year.

The fix is not memory. The fix is a coding structure. Make the location clear from the entry. Make the lease type clear from the account. Make the variable charges clear from the parent. Once the structure is right, the volume scales without the mess.

Occupancy expense: The total cost of occupying a leased commercial space, including base rent, CAM (common area maintenance), real estate tax pass-throughs, insurance pass-throughs, percentage rent if applicable, and any other lease-defined charges. For multi-location tenants, occupancy expense is reported by location for management reporting and aggregated for financial reporting.

The chart-of-accounts structure that scales

Three rules drive a clean multi-location occupancy chart of accounts.

First, use the location field, not the account. Modern platforms support a location or class field. These include QuickBooks Online, Xero, NetSuite, and Sage Intacct. Set the location field on every occupancy entry. Use the same parent account across locations. One rent expense account filtered by location reads cleaner than fifteen rent accounts named "Rent: Atlanta," "Rent: Dallas," and so on.

Second, split base rent from variable pass-throughs. Base rent is a fixed amount set in the lease. CAM, taxes, and insurance are variable and tied to landlord billing. The two act differently, so code them differently. Use two parent accounts: rent expense and operating expense pass-through. Add sub-accounts or classes from there if you need them for reporting.

Third, hold reconciliation true-ups in the period they cover. A true-up settles the gap between estimates paid and actual costs. Say a CAM true-up arrives in March 2026 for the 2025 lease year. The location field is the 2025 location. The period treatment follows the prepaid rent vs. accrual decision tree. The location and period are separate. Do not let the invoice month override the period the bill covers.

A working chart for a five-location retail client looks like this.

Account	Dimension	Use
Rent expense: base	Location	Monthly contractual base rent
Rent expense: percentage	Location	Sales-based percentage rent if applicable
Operating expense: CAM estimates	Location	Monthly CAM estimates as paid
Operating expense: CAM true-up	Location	Annual CAM reconciliation amounts
Operating expense: RE tax pass-through	Location	Property tax pass-throughs
Operating expense: insurance pass-through	Location	Insurance pass-throughs
Operating expense: other lease charges	Location	Anything else the lease authorizes

Seven accounts and five location dimensions give 35 coding combinations. That is cleaner than fifty accounts. The management report can pivot by location or by charge type with no chart rebuild.

How the AP team handles a multi-location landlord bill

A landlord runs three of the client''s five locations and bills monthly. Some bills are combined invoices that cover several locations. Some are per-location invoices.

For combined invoices, the AP team enters one bill with several lines. Each line is tagged to the right location. This keeps the AP audit trail and gives clean per-location reporting. For per-location invoices, the whole bill goes to one location.

Three habits make this easy.

Use a standard memo format. Every occupancy bill memo follows the same template. List the location, the lease year if it is a reconciliation, and a brief note. "Atlanta: 2025 CAM true-up" or "Dallas: May 2026 base rent." Six months later, the memo tells the story when someone reviews the GL.

Use standard vendor names. If one property management company runs several locations, the AP vendor record is that company, not the location. The location field carries the location detail. This avoids vendor record bloat.

Track reconciliations by location. Keep a simple workpaper with one row per location and one column per reconciliation year. Note date received, amount, period covered, flags raised, and status. For a 10-location client this is a 10-row sheet. It ends the "did we ever review the 2024 reconciliation for the Phoenix location" question at year-end.

"Multi-location coding is not harder than single-location coding once the structure is set. It is just more entries against the same structure. The mistake is letting each location''s coding evolve independently until five locations have five different ways of representing the same charge type." - Angel Campa, Founder, CAMAudit

When a CAM red flag shows up at one location

A client with five leases gets five different CAM patterns. A red flag at the Houston location does not touch the Boston location. The flag is location-specific because the lease is location-specific.

The escalation is the same as for a single-location client. Code the bill. Preserve the document. Escalate the flag. The location field makes this clearer. The controller or specialist sees exactly which lease and location are at issue.

Multi-location clients add one thing: the ability to spot patterns across sites. Two cases are worth watching.

The first is the same landlord across many locations. Say one property management company runs three of the client''s five locations. A method issue shows up at one, like a management fee figured on gross rather than net. The management fee is what the landlord charges to run the property. Check the other two. The same manager often uses the same method across its portfolio. CAMAudit''s detection runs on each reconciliation on its own. The firm''s rollup step looks for the cross-location pattern.

The second is the same property type across many locations. Say two locations sit in similar shopping centers. One shows a 14 percent year-over-year CAM increase and the other shows 4 percent. That gap is worth a question. The locations are separate, but the benchmark is useful.

These cross-location reviews are firm-level work, not bookkeeping. They sit with the controller or partner. They fit a quarterly review, not a monthly one.

Reporting that the client actually uses

Multi-location clients want to see occupancy cost three ways.

The first is per location, by month. This is for operations. It shows which locations run over budget on rent and CAM each month.

The second is per location, year over year. This is for real estate strategy. It shows which locations get more expensive faster than the rest.

The third is total, by charge type. This is for category management. It shows whether CAM costs grow faster than base rent across the portfolio.

The chart structure above makes all three reports with no custom mapping. The location field drives the first two reports. The parent account structure drives the third. A 15-minute dashboard build at the start pays for itself at every monthly close.

For clients who want it, occupancy cost as a percent of revenue is the higher-level metric. That means linking the location field to revenue tracking. Most retail and service-business platforms support this out of the box.

When the engagement scope expands

A few signs show a multi-location job has outgrown standard bookkeeping scope.

The client has four or more locations. It routinely sees one or two CAM red flags per reconciliation cycle. The firm spends 90 minutes per cycle on escalation work that does not bill cleanly.

The client opens locations faster than the firm can onboard new leases. New leases land in the GL with no abstracts. The coding gets ad hoc.

Two or more landlord billing disputes have come up in the past 24 months. The client wants more proactive review.

At that point, three options open up.

The first is a fractional controller engagement. The firm adds a controller layer. It owns the occupancy review across all locations. It serves as the escalation point for the bookkeeping team.

The second is a CAM-specific advisory engagement. This is a separate, scoped engagement for lease compliance review. Bill it quarterly or per reconciliation. CAMAudit runs the systematic detection.

The third is an external CAM specialist referral. For high-volume or complex disputes, refer the work to a specialist with deeper CRE skill. The firm stays focused on bookkeeping.

The right answer depends on the firm''s skills and the client''s appetite for fee. The structural answer is the same. Multi-location occupancy coding deserves more care than the default chart of accounts suggests. The firm that builds the structure early scales the relationship without burning out the close team.

Multi-location clients are some of the highest-value work an accounting firm carries. The coding structure is what keeps them sustainable.

Multi-Location Clients: How to Keep Occupancy Coding Consistent