How controllers should review CAM reconciliation statements
The annual CAM reconciliation is one of the few year-end items where a controller can produce a quantifiable EBITDA outcome through review work alone. The reconciliation arrives, the accounts payable team books it, and unless someone with controller-level judgment looks at it against the lease, the company pays whatever the landlord billed. I built CAMAudit because the systematic comparison of a reconciliation statement against the lease provisions is the kind of analytical work that benefits from automation, and the savings that flow from that work are real and recurring. This article describes the controller-level review framework: the provisions that matter most, the materiality screen, and the documentation that supports both the close cycle and any subsequent dispute.
CAM reconciliation review: The controller-level analytical review of an annual CAM reconciliation statement against the executed lease, performed to verify that the charges billed comply with the lease provisions and that the calculation methodology is correct. The review covers pro-rata share, management fee base, gross-up, base year, controllable expense cap, and excluded category compliance. The output is a documented review file supporting accept or dispute decisions for each finding.
Why the controller, not AP, should run the review
The AP-level check on a CAM reconciliation answers a narrow question: does the math in the statement add up. The controller-level review answers a different question: does the statement comply with the lease. These are different questions with different evidence requirements.
The AP-level check verifies that the line items sum to the total, that the prior estimated payments are credited, and that the resulting true-up amount is consistent with the calculation. It does not verify that the management fee base is correct, that the pro-rata share denominator is the one the lease specifies, or that excluded categories are actually excluded. Those are lease-compliance questions that require reading the lease against the reconciliation, and they sit at a different level of professional judgment than the AP cycle.
In most multi-location organizations, the AP team is processing dozens or hundreds of reconciliation statements per year. Controller-level review is not feasible at that scale without infrastructure. Either the company accepts a base level of CAM compliance risk, or it deploys infrastructure that runs the systematic detection across all reconciliations and surfaces only the items that warrant controller-level judgment. CAMAudit is designed to be that infrastructure.
The provisions that drive the dollar outcome
After testing reconciliation samples through CAMAudit, the provisions that produce the largest dollar variances cluster into a small number of categories.
Management fee overcharges. The lease defines what the management fee is calculated on, typically a percentage of CAM expenses with specific exclusions. The most frequent error is the landlord calculating the fee on a base that includes excluded categories such as capital expenditures, real estate taxes, insurance, or other categories the lease places outside the fee base. Because this error recurs every year, the cumulative cost over a multi-year lease is material.
Pro-rata share denominator errors. The pro-rata share fraction allocates CAM to the tenant. The numerator is the tenant's leased square footage. The denominator is what the lease specifies, which may be total rentable area, total leased area, or total occupied area. When the landlord uses a denominator that is smaller than the lease specifies, the fraction inflates and the tenant overpays for every expense category allocated by the fraction. This is a systematic overcharge across the entire reconciliation.
Excluded service charges. Most leases enumerate categories that are explicitly excluded from CAM, such as costs incurred for the benefit of a single tenant, capital improvements, or marketing expenses. The reconciliation should not include those categories. Detection requires reading the lease's exclusion list and comparing it against the line items in the reconciliation, which is the kind of cross-document analysis that benefits from automation.
Base year and expense cap errors. Office leases with base year structures and retail leases with controllable expense caps both have provisions that limit the year-over-year increase in tenant CAM cost. Errors in the application of these provisions compound over the lease term and produce some of the largest cumulative overcharges. The controller should verify that the base year amount used is the one established in the original year and that any cap provision was applied to the correct expense categories.
The materiality screen
A controller-level review needs a materiality framework so that finding-level judgment is consistent across reconciliations. The standard practice is two thresholds: a line-level threshold and an aggregate threshold.
The line-level threshold is typically 1 to 2 percent of total CAM. Findings below this threshold are noted but not escalated. Findings above the threshold are documented in detail and considered for dispute.
The aggregate threshold is typically 5 percent of total CAM. If the sum of all findings exceeds the aggregate threshold, the reconciliation is escalated for formal dispute regardless of the individual line magnitudes.
Both thresholds should align with the broader materiality framework the company uses for close cycle and audit purposes. A controller running CAM reviews on a portfolio of leases benefits from documenting these thresholds once and applying them consistently, which produces a repeatable workflow that survives turnover in the AP team.
How CAMAudit fits the controller review workflow
The controller's review has three layers, and CAMAudit addresses the bottom layer.
| Layer | Work | Owner |
|---|---|---|
| Detection | Cross-document analysis of lease against reconciliation, applying 14 compliance rules | CAMAudit |
| Judgment | Materiality screen, dispute strategy, professional conclusion | Controller |
| Documentation | Review file with conclusions, citations, and audit trail | Controller |
CAMAudit ingests the lease and the reconciliation, runs the rules, and produces a structured findings report. Each finding cites the specific lease provision, shows the landlord's billed amount, shows the correctly calculated amount, and quantifies the variance. The controller takes that output and applies professional judgment: which findings are material, which warrant dispute, which can be addressed in a follow-up call with the property manager rather than escalating to a formal dispute letter draft.
The documentation layer is where the review file lives. The controller's review file should reference the CAMAudit findings report, document the controller's conclusion on each finding, and attach any supporting calculation that was developed during the review. This file supports the close cycle, supports any subsequent dispute correspondence, and supports the audit trail.
"The work that consumes a controller's time on CAM reviews is the systematic comparison: reading lease language and matching it against line items in the reconciliation. That is the layer that benefits most from automation. I built CAMAudit so that the controller's judgment time is spent on materiality and dispute strategy, which is where the value is." — Angel Campa, Founder, CAMAudit
Building the review file
A defensible review file has six elements. The controller produces this file once per reconciliation reviewed, and the format is consistent across the portfolio.
The first element is a summary of the lease, including the executed date, any amendments, the lease term, the pro-rata share fraction as specified in the lease, the management fee structure, the base year if applicable, and any cap provisions. This summary establishes the standard against which the reconciliation is being measured.
The second element is the reconciliation statement itself, including the line item detail and the total amount billed.
The third element is the findings, with each finding documented as: the lease provision involved, the landlord's billed amount, the correctly calculated amount, the dollar variance, and the controller's conclusion on the finding. Findings can be accepted, accepted with note, or escalated for dispute.
The fourth element is the materiality screen, documenting which findings exceeded the line-level threshold and what the aggregate finding total is relative to total CAM.
The fifth element is the dispute strategy, documenting which findings are being formalized into a dispute letter draft, which are being addressed informally with the property manager, and which are being accepted.
The sixth element is the supporting documentation: the calculation worksheets for each finding, any communication with the landlord, and the file references for the lease and reconciliation source documents.
This structure is repeatable, supports the close cycle, and produces an audit trail that withstands review by an external auditor or an in-house legal team.
Coordinating with AP and the property manager
The controller's review does not exist in isolation. It interacts with the AP cycle and with the property manager relationship.
On the AP side, the controller's review should run in parallel with AP processing of the reconciliation, not after AP has already approved payment. The right pattern is for AP to flag the reconciliation when it arrives, the controller to schedule the review against a timeline that respects the lease's audit rights window, and AP to hold or process payment based on the controller's conclusion. The lease's audit rights window varies by lease but is typically 60 to 180 days from receipt of the reconciliation, and the controller's review should land well inside that window.
On the property manager side, the controller's findings are the basis for the dispute conversation. Some findings are best handled informally: a phone call or email to the property manager, a request for the supporting calculation, and a billing adjustment in the next statement. Other findings warrant the formal dispute letter draft and the audit rights process. The controller's judgment on which path each finding takes is the bridge between the analytical review and the operational outcome.
A finance team that runs this workflow consistently across a portfolio produces a quantifiable EBITDA outcome year over year. The dollar amount depends on the size of the portfolio and the complexity of the leases, but for any multi-location commercial tenant, the cumulative recovery from a structured CAM review program is material.
When to escalate to a forensic engagement
The vast majority of CAM findings can be resolved through the controller's review and dispute correspondence. A small subset escalate to a forensic engagement, typically when the dollar amount is large, the lease provisions are complex, or the landlord disputes the findings in a way that requires expert-level analysis.
Indicators that a finding warrants forensic engagement include: cumulative overcharge across multiple years exceeding $50,000, complex provisions such as multi-year base year reset issues, gross-up methodology disputes, or controllable cap allocation across multi-tenant calculations, and a landlord response that disputes the methodology rather than the calculation. In these cases, the controller's review file becomes the analytical foundation for an engagement with a forensic CPA or a CAM specialist firm. See the white-label partner program for the platform that supports both controller-level and forensic-level workflows.
Frequently Asked Questions
What does a controller-level CAM reconciliation review look like?
A controller-level review goes beyond the AP-level math check. The controller verifies that the charges billed match what the lease permits, that the pro-rata share denominator is the one specified in the lease, that the management fee base excludes the categories the lease excludes, that gross-up provisions for under-occupied buildings were applied correctly, and that any base year or expense cap provisions were honored. The output is a documented review file showing the conclusion for each provision and the evidence relied on.
Which CAM provisions produce the largest overcharges in practice?
The provisions that produce the largest dollar overcharges are management fee calculations where the fee base includes excluded categories, pro-rata share denominators that understate occupied square footage, base year errors that compound over the lease term, and gross-up provisions that were not applied for partially occupied buildings. Management fee and pro-rata share errors recur every year of the lease until corrected, which makes the cumulative impact material.
How does a controller establish materiality on a CAM reconciliation?
Materiality on a CAM reconciliation is set at the line level relative to total CAM and at the aggregate level relative to total occupancy cost. Most controllers set a 1 to 2 percent line-level threshold and a 5 percent aggregate threshold for documentation purposes, with anything above the threshold escalated for dispute. The threshold is informed by the size of the lease and the materiality framework already in use for the broader close cycle.
What documentation should the controller retain from a reconciliation review?
The review file should include the lease and any amendments referenced, the reconciliation statement, the calculation worksheets supporting each finding, the citation in the lease for each finding, the controller's conclusion on whether to accept or dispute the charge, and any communication with the landlord or property manager. This documentation supports the period close, supports any subsequent dispute, and supports the audit trail if the company is audited.
How does CAMAudit fit into the controller's review workflow?
CAMAudit runs the systematic detection layer: it ingests the lease and the reconciliation statement, applies 14 compliance rules, and produces a structured findings report with lease citations and dollar variances. The controller uses that output as the analytical input to the review, applies professional judgment on materiality and dispute strategy, and produces the documented review file. The detection layer is the work that benefits most from automation; the judgment layer remains with the controller.