When to Escalate a CAM Issue: A Decision Framework for Accounting Teams
The hard part of catching landlord overcharges inside an accounting firm is not the detection. It is the decision about what to do once the bookkeeper notices something is off. Without a documented escalation framework, every flag becomes a partner-level conversation, which kills engagement margin, or no flag at all becomes a partner conversation, which means systematic overcharges run for years inside client portfolios. I built CAMAudit because the analytical work of CAM dispute detection is structured and repeatable, but the firm-side decision about when to escalate is what determines whether the work ever gets done.
This article is the framework I would put in the procedures manual for any CAS, fractional-CFO, or outsourced-controller practice serving commercial tenant clients. It defines the variance thresholds, the lease-provision triggers, and the moment a discrepancy becomes a formal audit.
CAM escalation framework: A documented decision rule that defines when a CAM discrepancy moves between role levels (bookkeeper, controller, partner) and between engagement modes (routine bookkeeping, advisory review, formal audit, dispute). The framework relies on two trigger types: dollar variance thresholds and lease-provision categories. Either trigger type fires escalation independently of the other, which is what prevents low-dollar definitional issues from being dismissed and high-dollar billing typos from consuming partner time.
The two-trigger structure
The framework runs on two parallel triggers because CAM issues fall into two distinct error categories with different decision economics.
A CAM finding has to clear neither trigger to stay at the current level. If it clears either, it escalates.
Dollar variance thresholds
The bookkeeper-to-controller threshold is the most important one, because it sets the volume of escalation a firm absorbs at the controller level. Setting it too low floods the controller; too high lets meaningful variances pass.
| Trigger level | Threshold (suggested) | Action |
|---|---|---|
| Bookkeeper handles | < $250/month variance, no provision flag | Resolve via direct email to landlord |
| Controller review | $250 to $1,500/month, or any reconciliation | Document finding, compare to lease, decide |
| Partner review | > $1,500 cumulative annual impact, or any contested response from landlord | Decide on dispute strategy |
Use these as sample points. Set your own limits from your firm's real data.
Lease-provision triggers
Five categories of lease provision trigger escalation regardless of dollar amount, because errors in these categories are almost always systematic rather than one-time.
Fee base. Check each fee line. The lease may bar some costs from the fee base. Test the fee against that list. See management fee overcharge.
Gross-up methodology. Any reconciliation that applies a gross-up to variable expenses for an under-occupied building. The standard requires gross-up to 95% occupancy, but the implementation details (which expense categories are variable, which fixed) produce frequent overcharges. See gross-up violation.
Base year calculation. Any office lease with a base year structure. An inflated base year amount produces a constant-dollar overcharge every subsequent year. This category triggers retrospective review across all years inside the audit window.
Controllable expense cap. Any retail lease with a controllable expense cap. The error pattern is calculating the cap against the wrong baseline year or applying it to the total expense pool rather than the controllable subset.
Capital expenditure passthrough. Any line item that could be a capital improvement charged through CAM. The IRS-vs-CAM distinction is methodological, and most leases have specific exclusion language that landlords routinely violate.
A finding that touches any of these five categories goes to the controller regardless of dollar size, because the per-line dollar size understates the cumulative impact.
"The mistake firms make is treating CAM variance like any other AP exception. A $200 variance in a phone bill is a $200 problem. A $200 variance in a CAM line item that ties to the management fee or the gross-up is usually a $5,000 problem hiding inside it. The framework has to catch the second one even when the dollar amount is small." - Angel Campa, Founder, CAMAudit
The reconciliation statement is always controller-level
There is one universal rule the framework includes regardless of variance size or provision category: the annual CAM reconciliation statement is always controller-level. The bookkeeper holds the true-up payment, attaches the lease abstract, and routes the package to the controller. The controller decides whether to pay, dispute, or extend the review.
The reason is simple. The reconciliation statement is the single document where every category of systematic overcharge surfaces. Skipping the controller review in favor of bookkeeper-level processing is the highest-cost mistake an accounting firm can make in a tenant engagement.
What the controller does next
When the controller receives an escalation (either a flagged monthly variance or a reconciliation statement), the controller-level workflow is:
- Read the relevant lease provisions. The lease abstract is the starting point; the executed lease is consulted when the abstract is ambiguous.
- Run CAMAudit. Upload the lease and the relevant statement. The platform produces a structured findings report covering the CAM detection rules with dollar impact and lease citations.
- Cross-check the findings. The controller validates each finding against the lease language, since automated detection is the starting point for analysis, not the conclusion.
- Quantify the cumulative impact. Sum findings across all years inside the audit-rights window.
- Brief the partner. If cumulative impact is above the partner threshold or the case has reputational complexity, the partner makes the dispute decision.
Decision points: variance, audit, dispute
The framework distinguishes three engagement modes the firm operates in.
Variance mode. A finding has been documented but is not being actively pursued. The accounting team logs the issue, includes it in the close package, and may use it as renewal-negotiation leverage. No formal action is taken.
Audit mode. The firm has decided to pursue the finding formally. The controller exercises the audit-rights provision in the lease, requests backup from the landlord, and produces a formal findings report.
Dispute mode. The firm has documented a concrete overcharge and prepares a dispute letter draft for client or counsel review, attaching the findings and the requested correction. This mode often involves coordination with the client's commercial real estate attorney.
The decision to move from variance to audit is a partner-level decision, because it triggers the audit-rights window timer and creates a documented record. The decision to move from audit to dispute is also partner-level. These are not bookkeeper-level decisions and the framework should make that explicit.
See the outsourced controller's CAM escalation matrix for the role-by-role detail and the CAS firm landlord bill review workflow for the upstream monthly process that feeds this framework.
When the framework is wrong
The framework is wrong in two situations. First, when the audit-rights window is closing soon. A finding inside a 60-day-to-deadline window escalates immediately regardless of dollar amount, because the option to dispute formally is about to expire. The controller's first action when receiving any reconciliation statement is to check the audit-rights deadline.
Second, when the landlord has previously contested a similar finding. A repeat dispute on a known-contested issue requires partner-level engagement from the start, because the firm is now operating in a relationship-management context, not a routine review context.
Outside those two exceptions, the dollar-and-provision two-trigger framework handles 95%+ of CAM findings cleanly across a typical CAS or outsourced-controller portfolio.
Frequently Asked Questions
What sends a CAM issue to the next reviewer?
Set the rule from client risk and firm policy. State when a bookkeeper sends work to a controller. State when a partner must check it. Put the rules in the list.
Which lease provisions automatically trigger escalation regardless of dollar amount?
Five provision categories trigger escalation regardless of dollar amount: management fee structure, gross-up methodology, base year calculation, controllable expense cap, and capital expenditure passthrough. These provisions are where systematic overcharges live and where bookkeeper-level interpretation produces high error rates. Any reconciliation statement that touches any of these categories goes straight to the controller.
When does a variance become a formal audit?
A variance becomes a formal audit when the controller has reviewed the finding, confirmed the lease provision interpretation, quantified the cumulative dollar impact across all years still inside the audit-rights window, and the partner has decided the recovery is worth pursuing formally. The transition from variance to audit is a deliberate decision point, not a default outcome.
Can the bookkeeper resolve any CAM issue directly with the landlord?
Bookkeepers can resolve narrow billing errors directly with the landlord (a missed escalation date, a typo in the monthly estimate, a duplicate charge). They should not negotiate definitional or methodological questions with the landlord because those conversations create informal positions that become hard to walk back. Methodological questions go through the controller and, if the dollar amount is material, the partner.
How does CAMAudit fit the escalation framework?
CAMAudit fits at the moment the variance becomes a controller-level review. Once the bookkeeper flags a finding or a reconciliation statement arrives, the controller uses CAMAudit to produce a structured findings report covering the CAM detection rules. The findings report quantifies the impact and cites the lease provisions, which is the analysis the controller would otherwise do manually. The partner uses the findings report to decide whether to pursue the dispute formally.