Standardizing Occupancy Coding Across a Multi-Entity Client Portfolio
One CAS firm partner showed me a multi-entity client. They opened four QuickBooks files in tabs. Each one had a different chart of accounts. Same client, same operating company, four entities, four ways to code occupancy expenses. Entity one put it all in 6100 Rent. Entity two split rent and CAM. Entity three had a 6210 Property Taxes account that nobody used. Entity four ran the landlord through accounts payable as one line each month. The memo field did the work the chart of accounts should do.
This is the hidden cost of portfolio CAS work. The firm cannot benchmark. It cannot produce clean roll-up reports. It cannot spot odd occupancy charges until the coding drift gets fixed. I built CAMAudit because the detection layer needs clean inputs. Clean inputs start with one standard chart of accounts. The GL has to put the right dollars in the right buckets first.
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 is rarely a skill problem. It is a process problem. Entities get set up at different times, often by different people. Each setup copies whatever the last entity used. Within eighteen months the firm has five slightly different charts of accounts. None of them is written down.
A few common causes show up again and again.
Mid-year setup with no coding check is one. An entity gets imported with opening balances mid-period. The accounts from the prior bookkeeper rarely get checked against the firm standard. They just become the entity's accounts.
Landlord invoice format is another. Some landlords send one line 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 that varies by landlord.
Lease and invoice mismatch is a third. The lease may say the tenant pays base rent plus CAM plus taxes plus insurance. The invoice may bundle it all into "monthly rent." With no lease abstract on file, the coding follows the invoice, not the lease.
No written standard is the most common cause. The standard lives in the head of the senior bookkeeper. When that person is on vacation, drift happens.
The minimum viable occupancy coding standard
Five accounts handle nearly every retail, office, and industrial tenant. More than that is noise. Less than that 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 under base rent. For tenant improvement amortization, add 6150 TI Amortization. Amortization spreads a one-time cost over several years. Everything else stays in this five-account frame.
The most important rule is simple. Never put CAM and base rent in the same account. They reconcile in different ways. They dispute in different ways. They get audited in different ways. A combined account hides the most expensive line in the occupancy stack.
Where the location dimension belongs
Multi-entity clients usually have many physical locations. Sometimes they share landlords or shopping centers. The common mistake is to copy the chart of accounts for each location. That makes a tree like 6100-A Rent, 6100-B Rent, 6100-C Rent for every account. It bloats the chart and makes roll-up reports break.
Use a class or location field instead. The accounts stay the same across entities. The location field carries the detail. QuickBooks Online uses Classes or Locations. Xero uses Tracking Categories. NetSuite has Subsidiaries and Locations built in. The rule is the same in every system. Detail belongs in the location field, not in the chart.
"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
A firm rolls out a new coding standard on an old portfolio. The first question is always whether to restate prior periods. The answer depends on what the firm needs to report going forward.
For most CAS work, restate the last twelve months at a minimum. This gives the firm a clean rolling year for variance review. It also lets the next CAM reconciliation match properly coded prior estimates. Going back further is usually worth it only in two cases. The client is in an active CAM dispute, or the firm is building trend analysis for advisory meetings.
The steps are simple. 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. Then book reclass entries. Write down the mapping logic so the next bookkeeper can repeat it. The journal entry is non-cash and non-tax, which keeps the restatement clean.
The quarterly drift check
Standards drift the moment no one enforces them. The cheapest fix is a quarterly check at the close.
The check has four steps.
Step one. Pull the trial balance for every entity. Filter to the 6000-7000 occupancy range.
Step two. Check that each entity has activity in the same accounts. Say entity A has activity in 6110 CAM but entity B does not. Either entity B has no CAM, which you confirm 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. Confirm each one hit the standard accounts.
Step four. Log anything off-standard in a coding exceptions list. Queue it for correction.
Once the standard is in place, this check takes thirty minutes per portfolio at the close. The first time takes longer because exceptions pile up. By the second or third quarter, drift is rare.
What the standard enables for advisory work
A clean coding standard is more than housekeeping. It is the base for the higher-margin advisory work the firm wants to sell.
CAM reconciliation review becomes a real service line. The firm can pull a clean prior-year accrual and compare it to the landlord's true-up in minutes. A true-up settles the gap between estimates paid and actual costs. Portfolio benchmarking becomes possible because occupancy cost per square foot lines up across entities. ASC 842 compliance stays maintainable because the lease accounting subledger ties to the GL with no manual work. That rule sets how leases show up on the books. Advisory meetings get real because the firm can show occupancy as a percent of revenue across entities and sites. It is no longer one rent line buried in the P&L.
The firms that win in CAS treat coding standards as a deliverable, not back-office work. The standard is what lets the firm scale advisory hours without new hires.
Rolling the standard out without breaking the engagement
The hardest part of standardizing is not technical. It is the talk with the client. The client signed up for bookkeeping, not a chart of accounts redo. Any change to their financials will raise questions.
A few moves work well here.
Frame it as a reporting upgrade, not a fix. The current coding is not wrong. It is just inconsistent. The new standard gives the client reports they could not get before.
Show the deliverable. Build a sample 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 out the rest over a quarter. A big-bang rollout across ten entities in one week creates ten questions at once.
Document everything. Write the coding standard down. Put it in the firm wiki, the engagement letter, and the client reporting package. A written standard is real. An unwritten one is just a habit.
A standard chart of accounts is the base that lets every other occupancy service run well. CAM reconciliation review, lease abstract reconciliation, ASC 842 upkeep, and benchmarking all assume the GL is structured. Get the structure right first. Then the advisory layer multiplies the bookkeeping work. It does not become a new project every quarter.