How Controllers Catch CAM Overbilling Before the Client Notices
The best thing an outsourced controller or fractional CFO can do is catch an issue before the client does. CAM overbilling is a great fit for this. It is technical. It repeats every year. The client rarely catches it. I built CAMAudit because the analysis is high-value work. Controllers who build a detection step into their service turn routine oversight into visible advisory value. The workflow below is what I have seen work in firms that take this 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 job, not just the bookkeeper's
The bookkeeper's job ends when the books match what was paid. The controller's job starts where accuracy meets defensibility. Do the books reflect what the client should have paid under their contracts? The CAM reconciliation is a contract compliance question dressed up as a billing line.
Three things make CAM overbilling the controller's turf.
It is a contract reading question. The lease defines what the landlord may charge. The reconciliation shows what the landlord did charge. The gap, if any, takes judgment about provisions, exclusions, caps, and gross-up rules. Gross-up means adjusting variable costs to a set occupancy level. That is analysis, not data entry. It sits at the controller level.
It needs a materiality call. Not every variance is worth a dispute. A $400 finding on a $200,000 reconciliation may not clear the engagement cost. A $4,000 finding usually does. An $18,000 finding always does. That call is the controller's.
The output drives client talks. The findings memo is a controller deliverable. It frames the issue, recommends action, and helps the client decide. A bookkeeper can pull the data. The controller writes the document the client uses.
The three-cadence detection workflow
A controller serving a client with commercial leases runs detection on three cadences. Each one feeds the next.
Monthly: check estimates and flag outliers. During monthly close, the bookkeeper checks that each property's estimate payment matches the expected amount. On smaller engagements, the controller does it. They flag any odd charges. This is the monthly CAM advisory moment. Outliers go to a holding account. The controller decides what to do with them at the next quarterly review.
Quarterly: review the year-to-date trend. The controller compares each property's running CAM expense to the budget. The budget comes from the prior year's reconciliation plus expected escalation. A big variance, up or down, gets a closer look. The quarterly review also clears the holding-account items. The controller decides to dispute, accept, or ask for more information.
Annual: full reconciliation review. When the year-end reconciliation arrives, the controller runs a full review against the lease. They do this for each commercial lease in the portfolio. The output is a formal findings memo. Each issue lists the lease citation, the dollar variance, and a recommended action. The memo goes to the client. A meeting walks through the findings and agrees on next steps.
The three cadences lock together. Monthly catches outliers right away. Quarterly tracks the running trend. Annual closes the loop with a full review. A finding from any cadence is documented so the next one can reference it. Issues do not slip between checkpoints.
What the controller catches that the bookkeeper might miss
The bookkeeper's monthly check catches operational issues. Think estimate mismatches, special assessments, and back-dated adjustments. The controller's deeper review catches issues that take lease reading.
Management fee base. The lease sets the management fee as a percentage of CAM expenses. It also names items left out of the fee base. The bookkeeper may not know which items are out. The controller does. A 4% fee on $400,000 of CAM, including items the lease excludes, can overstate the fee by $2,000 to $4,000 a year. That repeats every year of the lease.
Pro rata denominator. The lease sets the denominator. Pro rata share is the tenant's slice of the cost pool. The reconciliation may use a number that does not match. To catch it, read both documents side by side. Recompute the ratio. Check it against the lease. That is controller work.
Controllable expense cap. Many leases cap year-over-year growth in controllable CAM expenses. To check it, find which items are controllable under the lease. Compute the year-over-year change for each. Compare against the cap. The math is simple, but it takes close reading of the lease.
Base year drift in office leases. Some office leases use a base year. An inflated base year creates an overcharge that compounds every year of the lease. The controller checks the base year amount at lease start. They check it again if a reconciliation shows an odd variance. A $3,000 base year error compounds to $30,000 over a 10-year lease.
Gross-up method. Office lease gross-up rules take care. Variable expenses get grossed up to the assumed occupancy level. Fixed expenses do not. A landlord who grosses up everything inflates the pool. The controller checks the method against the lease.
The controllers who deliver the most visible value walk into the annual review with a clear findings memo. They walk out with a client decision on each finding. The work feels like financial advisory because it is. I built CAMAudit to shrink the analysis phase. That way the controller spends billed hours on materiality and client talks, not on reading the lease line by line.
Presenting findings to the client
The controller's findings memo follows a steady structure. It protects both the analysis and the relationship.
Summary. A short paragraph. State the total dollar variance, the number of findings, and the recommended action.
Findings detail. For each finding, list the lease provision (section reference), the landlord's billed amount, the corrected amount under the lease, the dollar variance, and your confidence level. Each finding stands alone. The client can judge one without reading the others.
Recommended action. For each finding, pick one: dispute, accept, ask for more information, or escalate to a specialist. A specialist could be a real estate attorney or forensic CPA for large disputed items.
Context and risk. A short note on the landlord relationship, the cost to chase each finding against its dollar value, and any pattern across findings that points to a billing problem.
The memo reaches the client before the meeting, not as a surprise. The meeting is for decisions, not for finding things out.
How CAMAudit supports the controller workflow
The platform produces the analysis a controller would otherwise do by hand. Each finding includes the lease citation, the landlord's figure, the corrected figure, the variance, and a clear note on the rule that flagged it. That gives you a defensible base for the findings memo.
The platform does not do the materiality call, the client talks, or the dispute strategy. Those stay controller work. It replaces the slowest, lowest-value step: reading the lease against the reconciliation by hand. Your billed hours go to the analysis and the client relationship that define the engagement.
Run CAMAudit across many clients and the output keeps the same structure for each one. That lets your firm build standard findings memo templates and a steady client rhythm.
See the white-label partner program for pricing tiers built for outsourced accounting firms at different volumes.
What turns CAM detection into an offering
CAM detection becomes a real offering, not an occasional check, when three things are true.
The engagement letter prices CAM advisory work on its own. You can bundle it into the controller fee at a set service level. Or you can add it on with stated rates. The client knows CAM review is a service your firm delivers. The work lives in working papers. It goes out in a clear findings memo. You revisit it in regular advisory meetings.
That is the gap between a firm that sometimes catches an overcharge and a firm that has made CAM oversight part of its product. The second firm keeps clients longer. It expands engagements faster. It shows visible value the client names when asked why they stay.
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.