What is an expense stop in a commercial lease?

An expense stop is a dollar-per-square-foot threshold in a modified gross lease above which the tenant pays increases in operating expenses. If the stop is set at $12.00 per RSF, the landlord absorbs operating expenses up to that amount and the tenant pays any increase above it. Unlike a base year structure, which uses a reference year's actual expenses as the baseline, an expense stop uses a fixed dollar amount per unit of area. The tenant's exposure is the annual escalation above the stop, not the total expense.

How do expense stops differ from base year structures?

A base year structure sets the tenant's baseline as the actual operating expenses incurred during a specific reference year. Annual reconciliations then charge the tenant the difference between actual expenses for the current year and the base year expenses. An expense stop sets the baseline as a fixed per-square-foot dollar amount regardless of what actual expenses were in any particular year. Expense stops are typically used in modified gross leases where the landlord wants a defined threshold rather than a year-specific expense floor. The reconciliation mechanics, billing format, and dispute analysis differ for each structure.

What is the most common abstraction error for expense stop provisions?

The most common error is entering the stop amount in a standard "CAM charge" or "operating expense pass-through" field without capturing the threshold mechanism. This records that the tenant pays operating expenses but loses the information that payments only begin once actual expenses exceed the stop amount. Downstream teams then treat the provision as a simple pass-through, apply full recovery logic to all expense categories, and overestimate the tenant's actual obligation. The billing error compounds across years because the stop amount is the correct starting point for escalation calculations.

Can a lease have both an expense stop and a base year?

Yes, though it is uncommon and typically indicates a complex negotiated structure. Some leases use an expense stop for operating expenses but a separate base year for real estate taxes. Others use an expense stop in the original term and transition to a base year structure upon renewal. When both constructs appear in the same lease or lease history, the abstract must capture which applies to which expense category and for which lease period. Conflating them produces billing errors for every reconciliation during the affected period.

How does expense stop abstraction differ for office versus retail leases?

Expense stops are more common in office leases, particularly in markets where modified gross lease structures are standard. Retail leases more commonly use base year structures or full NNN pass-throughs. When an office lease uses an expense stop, the per-RSF amount is often negotiated relative to the landlord's actual expense level at lease execution, so abstractors should note whether the stop amount was above or below estimated actual expenses at execution. For retail leases with expense stops, the stop is sometimes set per gross leasable area rather than rentable area, and the denominator distinction matters.

Expense Stop Logic Treated as Ordinary CAM: The Abstraction Error

Modified gross leases use several different structures for allocating operating expense costs between landlord and tenant. Base year structures, full NNN pass-throughs, and expense stops each produce different financial outcomes for the same underlying expense data. When an abstractor treats an expense stop provision as a standard CAM pass-through, the threshold mechanic is erased from the record. What remains is a billing obligation without its controlling limit.

This article covers the mechanics of expense stop provisions, why they are structurally different from base year constructs despite serving a similar function, how the flattening error happens and what it costs downstream, and how to design abstract fields that capture both constructs accurately.

What an Expense Stop Actually Does

An expense stop is a per-square-foot dollar amount that defines how much of the building's operating expenses the landlord absorbs before the tenant's obligation begins. If the lease sets an expense stop at $11.50 per rentable square foot and the building's actual operating expenses for the year are $13.25 per RSF, the tenant pays the difference: $1.75 per RSF multiplied by their leased area.

The landlord's obligation is to absorb the first $11.50. The tenant's obligation is the increase above that threshold. This is a threshold structure, not a total recovery structure. The tenant never pays the full allocated operating expense. They pay only the amount that exceeds the stop.

This is meaningfully different from how a typical CAM pass-through in a NNN lease works. In a full NNN structure, the tenant pays their pro rata share of all operating expenses, typically including taxes and insurance, with no threshold and no floor. The landlord recovers the total allocated cost, not just the portion above a baseline.

The Structural Difference from Base Year

Base year structures and expense stops are both threshold-based, and abstractors commonly treat them as functionally equivalent. They are not.

A base year structure uses actual expenses incurred during a reference year as the baseline. If the base year was 2022 and actual operating expenses that year were $10.80 per RSF, the tenant pays the increase above $10.80 in all subsequent years. The base year amount is dynamic in the sense that it reflects what actually happened in that specific year, and it may include one-time costs, abnormal occupancy effects, or expense categories that shifted over time.

An expense stop uses a fixed contractual dollar amount. The stop does not depend on what expenses actually were in any particular year. The landlord and tenant negotiated a threshold and it applies throughout the term. There is no reference to a historical year's actual expenses; there is only the agreed stop amount.

The practical implications for reconciliation review are significant. For a base year structure, the reviewer needs to know the base year's actual expense total and verify it against the landlord's prior reconciliation records. For an expense stop, the reviewer needs only the stop amount and the current year's actual expenses. But the reviewer cannot perform either analysis correctly without first knowing which structure the lease uses.

How the Flattening Error Happens

The flattening error occurs at the field selection stage. Most lease abstract templates include a CAM pass-through field and, often, a separate base year field. When an abstractor encounters a modified gross lease with an expense stop, the template suggests either "tenant pays CAM" or "base year." Neither option perfectly describes a stop amount.

Some abstractors enter the stop amount in the base year field, reasoning that it functions like a baseline. Others enter it in a general notes field and mark the CAM pass-through field as applicable. Others enter "see notes" in the CAM field and record the stop amount only in the analyst comments.

Each approach loses the threshold mechanic in a different way. The base year field approach misidentifies the stop amount as a historical expense total, which will produce wrong calculations when someone attempts a base year reconciliation analysis. The notes-only approach means the stop amount is present in the record but not structured as a queryable field. The "see notes" approach leaves the structured fields empty and the threshold value inaccessible to any downstream automation.

Field Design for Expense Stop Abstracts

Accurate field design for expense stop provisions requires a lease structure classification field that precedes the economic detail fields. The classification field should allow values including: full NNN; NNN with base year; modified gross with expense stop; modified gross with base year; gross (no pass-through); and other.

Once the structure is classified, the relevant economic fields become conditional. For a modified gross lease with expense stop, the required fields are:

Stop amount per RSF or per unit of measurement, expressed as a dollar figure.

Stop amount basis, noting whether the stop is per rentable square foot, per gross leasable area, or per some other unit.

Expense categories subject to the stop, since some leases apply the stop to all operating expenses while others apply it only to maintenance and management costs, with taxes and insurance handled separately.

Expense categories excluded from the stop, particularly when real estate taxes or insurance have separate billing structures.

Whether the stop amount escalates over the lease term, since some modified gross leases include annual increases to the stop amount.

For a base year structure, the required fields differ: base year calendar year, base year actual expense total if available or reference clause if not, occupancy normalization threshold, expense categories subject to base year escalation, and whether taxes have a separate base year.

The classification field must be completed before any of the downstream economic fields, because the interpretation of every subsequent field depends on knowing which structure applies.

What Downstream Teams Need

A lease admin team managing a portfolio with a mix of NNN, base year, and expense stop leases needs the structure classification to apply the correct billing logic for each lease. Without it, they must re-read the lease each time a reconciliation arrives to determine whether to compare against a historical base year or a fixed stop amount.

A CAM reviewer evaluating whether a reconciliation was calculated correctly needs to know whether the landlord should have charged the full allocated expense amount or only the increase above the stop. An incorrect structure classification will produce a false clean result in the review because the wrong billing model is being applied to the numbers.

For lease abstraction firms that offer downstream review services or white-label audit capabilities, expense stop identification is a quality gate. A portfolio-wide data pull that correctly classifies all leases by structure allows downstream review to apply the right analysis to each lease type without individual file review. Getting the structure classification right at abstraction time is significantly cheaper than reconstructing it at review time.

Abstraction Notes for Transitional Structures

Some leases use an expense stop during the initial term and transition to a base year structure upon renewal. Others begin as full NNN and convert to a base year structure when the tenant exercises an option. These transitional structures require the abstract to record both the original and the current structure, with the effective date of the transition.

When the current structure was established by an amendment and the original abstract predates that amendment, the amendment catch-up review must update the structure classification field and all downstream economic fields. An amendment that converts an expense stop to a base year effectively changes the billing model for every reconciliation from the amendment effective date forward. Leaving the original stop amount in the field while noting the conversion only in comments produces exactly the same downstream failure as missing the stop amount in the first place.

The structure classification approach described here addresses the root cause of expense stop flattening: templates that do not present modified gross lease structures as distinct from NNN or base year structures. When the template forces a binary choice between CAM pass-through and base year, abstractors will pick the closest fit rather than flagging the misclassification. A well-designed template anticipates the full range of structures found in commercial real estate and provides appropriate fields for each.

Firms applying this guidance can run a free audit through CAMAudit to verify how the detection engine handles these clauses on a real reconciliation statement.

Expense Stop Logic Treated as Ordinary CAM: The Abstraction Error