Operating expense pass-through leakage in a CRE acquisition occurs when lease language appears to support recovery of controllable costs, but the actual billing structure prevents those dollars from reaching NOI. The result is a gap between what is contractually recoverable and what is actually collected. In diligence, that gap is easy to miss.
For buyers, the implication is straightforward: underwriting can look materially better than post-close reality. Even a modest annual shortfall in recoveries can translate into meaningful value erosion when capitalized across a hold period. In medical office, complex retail, and office portfolios, that risk is amplified by specialized operating costs, layered lease amendments, and reimbursement structures that are more complex than those in standard office assets.
In practice, leakage emerges when the lease says one thing and the accounting logic does another. A lease may permit recovery of controllable CAM subject to a defined cap, but the way that cap is implemented over time—especially after multiple amendments—can suppress recoveries without drawing attention during a conventional review. Across a complex multi-tenant asset portfolio, small under-recoveries at the tenant level can compound into a significant drag on asset performance.
Leakage rarely sits in one obvious clause. More often, it appears in the interaction between CAM caps, amendment history, and third-party service obligations.
A common pattern looks like this: an original lease establishes a non-cumulative cap on controllable CAM tied to a base year. A later amendment resets the base year, excludes certain services from the cap, and adds an exception for amortized capital improvements. A subsequent amendment grants temporary relief to a major tenant during a build-out period. The accounting system, however, continues applying the original cap logic as if none of those revisions occurred.
From the outside, the recoveries may appear reasonable. Year-over-year increases may remain within an expected range. But the underlying calculation can still be wrong. The system may fail to reflect a reset base year, apply exclusions at the building level instead of the tenant level, or cap expenses that should have remained outside the cap altogether.
Vendor contracts can deepen the problem. Janitorial, waste, HVAC, and other service agreements often contain annual escalators or minimum commitments that do not align with lease reimbursement mechanics. If a service contract increases faster than what the lease permits the owner to recover, the spread becomes a recurring unrecoverable expense. That exposure may not be obvious in a high-level lease abstract, but it is very real in the cash flow.
The challenge is not that these conflicts are unusual. It is that they are easy to overlook when teams are working through a large document set under a compressed closing timeline.
Complex multi-tenant buildings introduce operating costs and use patterns that are not easily handled by generic CAM assumptions. Tenants may require extended HVAC hours, specialized janitorial protocols, biohazard disposal, enhanced security, or higher utility intensity. If those costs are not isolated correctly in the lease and reconciliation process, they can create recurring leakage.
Typical pressure points include:
These are not abstract drafting issues. They affect how recoveries perform over time. If the lease structure, amendment history, and vendor economics are not reconciled together, buyers can inherit an asset with structurally lower recoverability than underwriting assumed.
Most acquisition lease reviews are designed for speed and coverage, not forensic reconstruction. The process usually focuses on confirming economic terms, checking term dates, reviewing a sample of reconciliations, and identifying obvious exceptions. That approach is necessary, but it is not sufficient for uncovering pass-through leakage.
The reason is simple: leakage usually lives in the math, not the headline fields.
A traditional abstract may identify that a lease includes a controllable CAM cap. It may even note the percentage. What it often does not do is reconstruct how that cap operates over time, how later amendments changed it, whether exceptions apply by tenant or by expense type, or whether the billing system has implemented those changes correctly.
In complex multi-tenant portfolios, that gap becomes more pronounced because the lease stack often reflects years of operational change. Buyers are not reviewing a single static document. They are reviewing versioned logic spread across:
Under time pressure, teams naturally rely on sampling and heuristics. That can identify overbilling risk or unusual language, but it often misses underbilling exposure that is embedded in the asset’s operating history.
In one medical office acquisition, the buyer encountered a familiar diligence issue: a lease and operating history that appeared orderly at a high level, but contained meaningful complexity once reimbursement mechanics were reviewed across the full document set.
Rather than stopping at abstracted lease fields, the diligence process reconstructed how the reimbursement framework actually operated over time, including cap mechanics, amendment-driven changes, expense carve-outs, and the interaction between lease rights and third-party service obligations. Those findings were then tested against historical operating expenses and billing assumptions.
That review highlighted several potential sources of leakage, including reimbursement terms that had evolved through amendment history, medical-specific costs that required more precise allocation, and vendor contract economics that did not fully align with expected recovery patterns.
Once quantified, those issues gave the buyer a stronger basis to refine underwriting, prioritize post-close billing adjustments, and better understand where recoverability risk sat within the asset.
The broader takeaway is straightforward: in CRE acquisitions, value is often shaped not just by what the lease says in isolation, but by how lease language, amendments, operating history, and vendor obligations work together over time.
Protecting against pass-through leakage does not require a longer memo. It requires a more disciplined workflow.
A practical approach includes five steps:
Define the recovery thesis before opening the data room.
Document the recovery assumptions embedded in underwriting, including the expected reimbursement profile for controllable OpEx and the cap structures that support it.
Reconstruct lease logic, not just lease fields.
For major tenants, map how reimbursement mechanics work across the full document set: cumulative or non-cumulative caps, base year resets, exclusions, carve-outs, and amendment-specific overrides.
Crosswalk vendor contracts against reimbursement limits.
Identify service agreements with escalators, minimums, or specialized scopes that may outpace what the lease permits you to recover.
Use automation where document logic becomes too dense for manual review alone.
The goal is not just to extract text, but to convert lease provisions into structured obligations that can be tested against actual operating history.
Quantify the impact.
Translate each mismatch into economics: annual under-recovery, underwriting impact, and the specific steps available post-close to correct or mitigate it.
In complex multi-tenant asset acquisitions, OpEx pass-through leakage is rarely a headline issue until after closing. By then, it is no longer a diligence question. It is an asset management problem.
The advantage goes to buyers who treat recoveries as a logic exercise rather than a clerical one. When you reconcile lease structure, amendment history, vendor economics, and historical billing together, hidden leakage becomes visible before it becomes permanent.
The example above is illustrative, but the diligence issues are real and recurring in complex multi-tenant assets. If you want to see how these issues can surface in practice, download the ABJNY case study or book a diligence demo.
The objective is simple: make recovery risk visible before it is embedded in your basis.