The Base Year Trap: What Controllers Need to Know Before Renewal
A base year lease looks like a tenant protection. The idea is that the tenant pays only the portion of operating expenses that exceeds what they were in the designated base year. Inflation happens; the building gets more expensive to run; the tenant's obligation grows only proportionally, not from dollar one. For more context, see spotting CAM overbilling as a controller.
In practice, the base year is one of the most reliably miscalculated elements in a CAM reconciliation. I built CAMAudit partly to automate the base year check because the error pattern is so consistent: the base is understated, the increment is overstated, and the tenant has been overpaying for years without anyone noticing.
Here is how base year leases work, where the errors appear, and what controllers need to verify.
Base year (CAM): A designated reference year in the lease whose actual operating expenses establish the baseline for the tenant's incremental CAM obligation. The tenant pays only the increase in operating expenses above the base year amount, applied to their pro-rata share. The lease specifies the year, whether the figure used is actual or estimated expenses, and any expense categories included or excluded from the base. A lower base year means a higher increment, which means higher CAM charges to the tenant.
How a Base Year Lease Is Supposed to Work
Take a law firm office tenant with a 10% pro-rata share in a building where the base year (2020) had actual operating expenses of $380,000.
In 2024, actual operating expenses are $440,000.
The increment is $440,000 minus $380,000, which equals $60,000. The tenant's share is 10% of $60,000, or $6,000 for the year.
If this were a pure NNN lease with no base year, the tenant's share would be 10% of $440,000, which is $44,000. The base year structure saves them $38,000 annually.
That only works if the base year number is correct. If the landlord uses $350,000 as the base instead of $380,000, the increment jumps to $90,000. The tenant's share becomes $9,000, an increase of $3,000 per year above what the lease actually authorizes.
Over a five-year lease term, that $30,000 per year error costs the tenant $15,000 cumulatively. On a 3-location retailer, multiply that across all three leases.
Error Pattern 1: Estimated vs. Actual Expenses
This is the most common base year error. The lease designates a specific year and says the base is "actual operating expenses" for that year. But the landlord uses the budget or estimated expenses, which are typically lower than actuals.
Why lower? Because budgets are set before the year begins. Actual expenses almost always come in higher due to unplanned maintenance, utility price increases, or insurance premium adjustments. A base year budget of $310,000 might have produced actual expenses of $332,000. Using the budget number understates the base by $22,000.
On a 10% pro-rata share, that $22,000 base error costs the tenant $2,200 per year. Every year. For the entire lease term.
The fix is straightforward: request the actual operating expense statement for the base year and compare it to the base figure the landlord is using.
Error Pattern 2: Using the Wrong Year
Some leases specify a base year that was the first full year of the lease term, or the year the lease was signed, or a specific calendar year by name. When the reconciliation uses a different year, the base is wrong by definition.
This happens more often at renewal than at initial lease execution. A tenant renews a lease in 2023, and the controller assumes the base year carries over from the original lease. But the renewal amendment reset the base year to 2022. Now 2022 expenses are the baseline, and depending on the direction of costs, that could work either for or against the tenant.
Controllers reviewing a renewal should specifically confirm: what is the base year under the renewed terms? Is it the same as the original lease, or has it changed?
Error Pattern 3: Post-Correction Recalculation
This is a subtler error. The base year expenses were originally calculated correctly, but the landlord subsequently corrected an expense item in the base year (perhaps an insurance audit adjustment or a utility true-up for that year). Instead of also adjusting the base year figure going forward, the landlord continued using the original uncorrected number.
If the correction increased base year expenses, using the lower uncorrected number understates the base and overstates the tenant's increment. If the correction decreased base year expenses, using the higher uncorrected number overstates the base and understates the increment, which actually benefits the tenant.
The point is that the base year number should reflect the final, corrected actual expenses for that year, not the preliminary figures from the reconciliation that was first prepared.
How the Error Compounds Over Time
The compounding effect is why base year errors matter more than their initial dollar amount suggests.
Consider a base year figure that is $18,000 too low. On a 12% pro-rata share, that $18,000 error costs the tenant $2,160 per year in additional CAM. Over a 7-year lease term, the cumulative overcharge is $15,120. Every year the error persists without correction, the total grows.
At renewal, this becomes especially significant. If the tenant signs a 5-year extension without correcting the base year error, they are agreeing to continue overpaying based on the wrong baseline for another five years.
I have seen our tool flag base year errors that traced back to the original lease commencement, producing a multi-year overcharge that had been paid without question. The reconciliation looked right in isolation because the math was internally consistent. The error was only visible when the base year figure was compared against the actual expense record for that year.
What to Verify Before Approving the Next Reconciliation
For any tenant on a base year lease, controllers should confirm four things when the annual reconciliation arrives:
The base year designation. What year does the lease specify? Has the lease been amended, and if so, did the amendment change the base year?
The base year figure being used. What number does the landlord apply as the base? This should appear in the reconciliation calculation, often as a deduction from the current year pool before the pro-rata calculation.
Actual vs. estimated. If the lease says actual expenses, request the operating expense statement for the base year. Confirm the figure matches.
Consistency year over year. If the same base year figure has been used for multiple years and it was recently found to be wrong, all prior reconciliations within the audit window may be disputable.
The Renewal Conversation
Controllers who advise clients on lease renewals should model the base year impact explicitly. If current expenses have risen significantly from the base year, a reset to a recent year's expenses as the new base could save the tenant a substantial amount. If expenses have declined or held flat, resetting may actually increase the tenant's future exposure.
The base year is a negotiating point. Most tenants do not know to ask about it. A controller who surfaces this issue before the client signs a renewal is providing value that goes well beyond bookkeeping.
Our tool flags base year errors automatically when a reconciliation is uploaded: the extracted base year figure is compared against lease terms, the increment calculation is verified, and any discrepancy between the stated base and the lease-authorized base is quantified. That gives the accounting team a specific number to bring into the conversation before renewal happens, not after.