Standardizing Occupancy Coding Across a Multi-Entity Client Portfolio
The first time I sat with a CAS firm partner reviewing a multi-entity client, I watched them open four QuickBooks files in tabs and squint at four different chart-of-accounts trees. Same client, same operating company, four entities, four versions of how occupancy expenses got coded. Entity one had everything in 6100 Rent. Entity two split rent and CAM. Entity three had a separate 6210 Property Taxes account that nobody was using. Entity four routed the landlord through accounts payable as a single line each month with the memo field doing the work of the chart of accounts.
This is the silent tax on portfolio CAS work. The firm cannot benchmark, cannot produce clean roll-up reports, and cannot spot occupancy anomalies until coding drift gets fixed. I built CAMAudit because the detection layer needs structured inputs, and structured inputs start with a standardized chart of accounts. Before any landlord reconciliation can be audited efficiently, the GL needs to put the right dollars in the right buckets.
Occupancy Coding Standard: A written rule set that defines which general ledger accounts capture each component of a tenant's occupancy expense across an entity portfolio. The standard typically covers base rent, CAM and operating expenses, property tax pass-throughs, insurance pass-throughs, tenant-paid utilities, and percentage rent. The goal is consistent classification across every entity so consolidated reporting, variance analysis, and reconciliation review work without manual re-mapping.
Why coding drifts in the first place
Coding drift across a multi-entity portfolio is rarely a competence issue. It is a process issue. Entities get onboarded at different times, often by different team members, and each onboarding pulls from whatever the previous entity used as a template. Within eighteen months, the firm has five subtly different versions of the same chart of accounts and no documented standard.
A few common drivers:
Mid-year onboarding without a coding pass. When an entity gets imported with opening balances mid-period, the accounts that came over from the prior bookkeeper rarely get reviewed against the firm standard. They just become the entity's accounts.
Landlord invoice format variation. Some landlords send a single line item for rent plus CAM. Some send separate invoices. Some send a quarterly reconciliation as a one-line credit or charge. The bookkeeper codes what they see, and what they see varies by landlord.
Lease vs. invoice mismatch. The lease may say the tenant pays base rent plus CAM plus taxes plus insurance. The invoice may bundle everything into "monthly rent." Without a lease abstract on file, the coding follows the invoice rather than the lease structure.
No documented standard. The most common driver. The firm has an implicit standard living in the head of the senior bookkeeper. When that bookkeeper is on vacation, drift happens.
The minimum viable occupancy coding standard
Five accounts handle nearly every retail, office, and industrial tenant. Anything beyond this is noise; anything less hides line items that matter for reconciliation review.
| Account | Captures |
|---|---|
| 6100 Base Rent | Fixed monthly rent per the lease, before any pass-throughs |
| 6110 CAM / Operating Expenses | Common area maintenance billed by the landlord, including monthly estimates and annual reconciliations |
| 6120 Property Taxes (Pass-Through) | Real estate taxes billed by the landlord as a tenant pass-through |
| 6130 Insurance (Pass-Through) | Building insurance billed by the landlord as a tenant pass-through |
| 6140 Utilities (Tenant-Paid) | Utilities the tenant pays directly or that the landlord passes through separately |
For percentage rent leases, add 6105 Percentage Rent as a subaccount of base rent. For tenant improvement amortization, add 6150 TI Amortization. Everything else stays in this five-account skeleton.
The single most important rule: CAM and base rent are never combined in the same account. They reconcile differently, they dispute differently, and they get audited differently. A combined account hides the most expensive line in the occupancy stack.
Where the location dimension belongs
Multi-entity clients usually have multiple physical locations, sometimes shared landlords, sometimes shared shopping centers. The mistake firms make is duplicating the chart of accounts to capture location, which produces a tree like 6100-A Rent, 6100-B Rent, 6100-C Rent for every account. This explodes the chart and makes consolidated reporting brittle.
Use a class or location dimension instead. The accounts stay identical across entities. The location dimension carries the granularity. QuickBooks Online uses Classes or Locations. Xero uses Tracking Categories. NetSuite has Subsidiaries and Locations natively. Whatever the system, the principle is the same: granularity belongs in dimensions, not in the chart.
After testing reconciliation samples through CAMAudit, the cleanest portfolios I see are the ones where every entity has the same five-account structure and uses a Location class to identify which physical site the expense belongs to. The reconciliation review takes a fraction of the time because the data is already structured.
"The portfolio that takes the least time to audit is always the one with the most boring chart of accounts. Boring means standardized. Standardized means we spend our hours on the reconciliation logic instead of remapping accounts." — Angel Campa, Founder of CAMAudit
Restating prior periods when the standard rolls out
When a firm imposes a new occupancy coding standard on an existing portfolio, the question is always whether to restate prior periods. The answer depends on what the firm needs to report on going forward.
For most CAS engagements, restate the trailing twelve months at minimum. This gives the firm a clean rolling year for variance analysis and lets the next CAM reconciliation get reviewed against properly coded prior estimates. Restating further back is usually only worth the time when the client is in active CAM dispute or when the firm is producing trend analysis for advisory meetings.
The mechanic is straightforward: pull the GL detail for the prior period, map each transaction to the new standard using the landlord vendor and invoice type as the key, and book reclassification entries. Document the mapping logic so the next bookkeeper can replicate it. The journal entry is non-cash and non-tax, which keeps the restatement clean.
The quarterly drift check
Standards drift the moment they stop being enforced. The most efficient enforcement mechanism is a quarterly check at the close.
The check has four steps:
Step one. Pull the trial balance for every entity in the portfolio. Filter to the 6000-7000 occupancy range.
Step two. Verify each entity has activity in the same accounts. If entity A has activity in 6110 CAM but entity B does not, either entity B has no CAM (verify against the lease) or entity B's CAM is miscoded.
Step three. Spot-check the largest landlord vendor in each entity. Pull the last three months of transactions and confirm each one hit the standardized accounts.
Step four. Document anything off-standard in a coding exceptions log and queue it for correction.
This check takes thirty minutes per portfolio at the close once the standard is in place. The first time, it takes longer because exceptions accumulate. After the second or third quarter, drift becomes rare.
What the standard enables for advisory work
A standardized occupancy coding standard is not just a hygiene improvement. It is the precondition for the higher-margin advisory work the firm wants to sell.
CAM reconciliation review becomes a real service line because the firm can pull a clean prior-year accrual and compare it to the landlord's true-up in minutes. Portfolio benchmarking becomes possible because occupancy cost per square foot is comparable across entities. ASC 842 compliance becomes maintainable because the lease accounting subledger ties to the GL without manual reconciliation. Advisory meetings become substantive because the firm can show occupancy as a percentage of revenue across entities and locations, not just a single rent line buried in the P&L.
The firms that win in CAS are the ones that treat coding standards as a service deliverable, not as bookkeeping back-office work. The standard is what lets the firm scale advisory hours without adding headcount.
Rolling the standard out without breaking the engagement
The hardest part of standardizing across a portfolio is not technical. It is the change-management conversation with the client. The client signed up for bookkeeping, not a chart-of-accounts overhaul, and any reorganization of their financials will surface questions.
A few rules I have seen work:
Frame it as a reporting upgrade, not a correction. The current coding is not wrong, it is just inconsistent. The new standard lets the firm produce reports the client could not get before.
Show the deliverable. Build a sample consolidated occupancy report under the new standard before the rollout. Walk the client through what they will see at the next quarterly meeting. The deliverable sells the work.
Phase the rollout. Start with the largest entity, prove the standard works there, then roll to the rest of the portfolio over a quarter. A big-bang rollout across ten entities in the same week creates ten simultaneous client questions.
Document everything. Write the coding standard down. Put it in the firm's internal wiki, the engagement letter, and the client-facing reporting package. The standard exists when it is written; otherwise it is just a habit.
A standardized chart of accounts across the portfolio is the foundation that lets every other occupancy advisory service work efficiently. CAM reconciliation review, lease abstract reconciliation, ASC 842 maintenance, and benchmarking all assume the underlying GL is structured. Get the structure right first, and the advisory layer becomes a multiplier on the bookkeeping engagement rather than a new project every quarter.