How Controllers Catch CAM Overbilling Before the Client Notices
The most valuable thing an outsourced controller or fractional CFO does for a commercial real estate client is surface an issue before the client surfaces it themselves. CAM overbilling is uniquely well-suited to this kind of value delivery because it''s technical, recurring, and easy for the client to miss. I built CAMAudit because the analytical work is high-leverage, and controllers who install a detection process into their service delivery convert routine financial oversight into visible advisory value. The workflow below is what I''ve seen work in firms that take this mandate seriously.
Controller-Level CAM Detection: The structured process by which an outsourced controller or fractional CFO installs CAM overbilling review into the service delivered to a commercial real estate client. The process operates at three cadences (monthly, quarterly, annual), uses the lease as the governing document, and produces a documented findings record at each cadence. The goal is to surface landlord billing issues before the client raises them, converting CAM oversight from a reactive question into a proactive control.
Why this is the controller''s mandate, not just the bookkeeper''s
The bookkeeper''s job ends when the books are accurate as to what was paid. The controller''s job begins where accuracy meets defensibility: are the books not just accurate but also reflective of what the client should have paid under their contracts. The CAM reconciliation is a contract compliance question dressed up as a billing line.
Three properties of CAM overbilling make it the controller''s territory.
It''s a contract interpretation question. The lease defines what the landlord may charge. The reconciliation states what the landlord did charge. The difference, if any, requires interpretive judgment about provisions, exclusions, caps, and gross-up mechanics. This is analytical work, not operational work, and it sits at the controller level.
It involves materiality assessment. Not every detected variance is worth disputing. A $400 finding on a $200,000 reconciliation may not be worth the engagement cost; a $4,000 finding usually is, and an $18,000 finding always is. The materiality call is the controller''s.
The output drives client communication. The findings memo that goes to the client is a controller-level deliverable. It frames the issue, recommends action, and supports the client''s decision-making. A bookkeeper can produce the underlying data; the controller produces the document the client uses.
The three-cadence detection workflow
A controller serving a client with commercial leases runs detection at three cadences that nest into one another.
Monthly: estimate verification and outlier flagging. During monthly close, the bookkeeper (or the controller for smaller engagements) verifies that each property''s estimate payment matches the expected amount and flags any non-routine charges. This is the monthly CAM advisory moment. Outliers get coded to a holding account, and the controller decides on the disposition during the next quarterly review.
Quarterly: year-to-date trend analysis. The controller reviews the cumulative CAM expense for each property against the budgeted figure derived from the prior year''s reconciliation plus expected escalation. A material variance, in either direction, triggers investigation. The quarterly review also addresses any holding-account items from the monthly process, deciding whether to dispute, accept, or request additional information.
Annual: full reconciliation review. When the year-end reconciliation arrives, the controller runs a complete review against the lease for each commercial lease in the portfolio. The output is a formal findings memo: each detected issue with the lease citation, the dollar variance, and a recommended action. The memo goes to the client with a meeting to walk through the findings and agree on disposition.
The three cadences interlock. Monthly catches outliers in real time, quarterly tracks cumulative trend, and annual closes the loop with a comprehensive review. A finding that surfaces in any cadence is documented in a way that the next cadence can reference, so issues don''t disappear between checkpoints.
What the controller looks for that the bookkeeper might miss
The bookkeeper''s monthly check catches operational issues: estimate mismatches, special assessments, retroactive adjustments. The controller''s deeper review surfaces analytical issues that require lease interpretation.
Management fee base composition. The lease defines the management fee as a percentage of CAM expenses with specific exclusions from the fee base. The bookkeeper may not know which categories are excluded; the controller does. A management fee of 4% applied to $400,000 of CAM expense including categories the lease excludes can overstate the fee by $2,000 to $4,000 per year, every year for the lease term.
Pro-rata denominator manipulation. The lease specifies the denominator. The reconciliation uses a number that may or may not match. Catching the discrepancy requires reading both documents side by side, recalculating the ratio, and validating against the lease. This is controller work.
Controllable expense cap calculation. Many leases cap year-over-year growth in controllable CAM expenses. Verifying compliance requires identifying which categories are controllable under the lease, calculating the year-over-year change for each, and comparing against the cap. The calculation is straightforward but requires careful attention to the lease language.
Base year drift in office leases. In office leases with base year mechanics, an inflated base year produces a compounding overcharge across every year of the lease. The controller validates the base year amount during the original lease commencement period and revalidates if any reconciliation surfaces unexpected variance. A $3,000 base year error compounds to $30,000 over a 10-year lease.
Gross-up methodology. Office lease gross-up provisions require careful application: variable expenses get grossed up to the assumed occupancy level, fixed expenses do not. A landlord who grosses up everything inflates the expense pool. The controller verifies the methodology against the lease.
The controllers who deliver the most visible value to commercial real estate clients are the ones who walk into the annual review meeting with a structured findings memo and walk out with a client decision on each finding. The work feels like financial advisory because that''s what it is. CAMAudit was built to compress the analytical phase so the controller can spend their billed hours on materiality assessment and client communication, not on manual line-by-line lease comparison.
Presenting findings to the client
The controller''s findings memo follows a consistent structure that protects both the analysis and the relationship.
Executive summary. A short paragraph stating the total dollar variance identified, the number of findings, and the controller''s recommended action.
Findings detail. For each finding: the lease provision (section reference), the landlord''s billed amount, the corrected amount under the lease, the dollar variance, and the controller''s confidence level. Each finding stands on its own so the client can evaluate one without referencing the others.
Recommended action. For each finding: dispute, accept, request additional information, or escalate to specialist (such as a real estate attorney or forensic CPA for material disputed items).
Context and risk assessment. A brief discussion of the relationship dynamics with the landlord, the cost of pursuing each finding relative to its dollar value, and any cross-finding patterns that suggest systematic billing issues.
The memo goes to the client in advance of a meeting, not as a surprise. The meeting is for decision-making, not for discovering findings.
How CAMAudit supports the controller workflow
The platform produces the analytical output that a controller would otherwise produce manually. Each finding includes the lease citation, the landlord''s figure, the corrected figure, the variance, and a structured explanation of the rule that surfaced it. The output is a defensible foundation for the controller''s findings memo.
What the platform does not do is the materiality assessment, the client communication, or the dispute strategy. Those remain controller work. The platform replaces the most time-consuming and least leveraged part of the workflow, which is the manual reading of lease against reconciliation. The controller''s billed hours go to the analytical and relational work that defines the controller engagement.
For firms running CAMAudit across a multi-client portfolio, the platform also produces consistent output structure across clients, which lets the firm build standardized findings memo templates and client communication rhythms.
See the white-label partner program for pricing tiers designed for outsourced accounting firms with varying engagement volumes.
The discipline that makes CAM detection a service line
The controller-level CAM detection workflow becomes a defined service line, not just an occasional analysis, when three things are true.
The engagement letter prices CAM advisory work explicitly (either bundled into the controller fee at a defined level of service or as an add-on with stated rates). The client knows that CAM review is a service the firm delivers. The work is documented in working papers, communicated through a structured findings memo, and revisited in regular advisory meetings.
That''s the difference between a firm that occasionally catches an overcharge and a firm that has installed CAM oversight as part of its product. The second firm retains clients longer, expands engagements faster, and produces a level of visible value that the client points to when asked why they work with the firm.
Frequently Asked Questions
Why is it the controller's job to catch CAM overbilling?
The controller owns financial accuracy. CAM overbilling is a financial control issue: the books reflect what was paid, and what was paid was determined by the landlord's billing rather than by what the lease authorizes. If the controller does not install a detection process, the books faithfully record the overcharge and the financial statements understate operating margin. Catching the overcharge is squarely within the controller's mandate, and surfacing it before the client raises the question signals a level of operational rigor that retains and expands the engagement.
What detection workflow does a controller install for a client portfolio with commercial leases?
A typical workflow has three components. Monthly: a quick estimate-vs-budget check on each leased property during close, with any non-routine charges flagged and validated against the lease. Quarterly: a deeper review of year-to-date expense trend and any significant cumulative variance from budget. Annual: a full reconciliation review against the lease for each commercial lease in the portfolio, producing a formal findings memo for the client. This three-cadence structure surfaces issues at the appropriate level of detail.
How does a controller present a detected overcharge to the client?
The presentation should be calm, factual, and decision-oriented. State the finding: the lease provision, the landlord's billed amount, the corrected amount, the dollar variance. State the recommended action: dispute, accept, or request additional information. Provide the documentation that supports the finding. Avoid emotional framing. The client's job is to make the dispute decision; the controller's job is to provide the analytical foundation.
What's the difference between controller-level review and bookkeeper-level review?
The bookkeeper's review is operational: tie the estimate payments, code the categories correctly, document non-routine items. The controller's review is analytical and strategic: validate the lease interpretation, assess materiality, decide on escalation path, and produce the client communication. A well-run firm has both layers operating in sequence so that bookkeeper-level findings reach the controller already documented and ready for analytical review.
How does CAMAudit support the controller's detection workflow?
CAMAudit produces the structured findings output that a controller would otherwise spend hours producing manually: each detected issue with the lease citation, the dollar variance, and the explanation of the underlying rule. The controller spends their time on validation, materiality assessment, and client communication, which is the highest-leverage use of controller-level expertise. The platform replaces the manual line-by-line lease comparison that consumes the most controller time.