A single-tenant NNN property is simple. One lease, one recovery calculation, one reconciliation. A 100-tenant retail center is not simple. One hundred leases, one hundred sets of rules, one hundred recovery calculations, one hundred reconciliations.
The complexity is not linear. It is exponential. Each lease has different terms: different pro-rata percentages, different caps, different exclusions, different base years, different escalation schedules. A system that works for 10 tenants fails at 100.
This article explains why lease-specific rules are required at scale and what happens when generic assumptions are used instead.
The Complexity Problem
10 tenants, 10 leases:
- 10 pro-rata percentages
- 10 escalation schedules
- 10 CAM caps or no caps
- 10 exclusion lists
- 10 base years
A controller can track this in a spreadsheet. The spreadsheet has 10 rows. The formulas are manageable. The review takes an hour.
100 tenants, 100 leases:
- 100 pro-rata percentages
- 100 escalation schedules
- 60 leases with caps, 40 without
- 100 different exclusion lists
- 80 different base years
- 25 leases with gross-up requirements
- 15 leases with percentage rent
- 10 leases with cotenancy clauses
The spreadsheet has 100 rows. The formulas reference other formulas. The review takes days. The error rate is not 10x. It is 100x.
Where Generic Assumptions Fail
Pro-Rata Percentages
Generic assumption: All tenants pay the same percentage per square foot.
Reality: Tenant A pays 12.5% of total leasable. Tenant B pays 12.5% of occupied. Tenant C pays a fixed percentage. Tenant D pays a percentage that excludes the anchor. Tenant E pays a percentage that changes when the anchor expands.
The failure: The generic assumption overcharges some tenants and undercharges others. The property absorbs the difference or faces refund claims.
Escalations
Generic assumption: All leases escalate at 3% annually.
Reality: Tenant A escalates at 3% fixed. Tenant B escalates at CPI with a 5% cap. Tenant C escalates at CPI with a 2% floor. Tenant D escalates 10% every 5 years. Tenant E has no escalation for the first 3 years, then 5% annually.
The failure: The generic assumption applies the wrong rate to half the tenants. The overcharges create refund liability. The undercharges create permanent revenue loss.
CAM Caps
Generic assumption: All tenants have a 5% controllable expense cap.
Reality: Tenant A has a 5% cumulative cap. Tenant B has a 5% non-cumulative cap. Tenant C has no cap. Tenant D has a cap on CAM but not on taxes. Tenant E has a cap that excludes snow removal.
The failure: The generic assumption applies a cap to tenants who do not have one and applies the wrong cap structure to tenants who do. The property overbills some tenants and underbills others.
Exclusions
Generic assumption: All leases exclude capital improvements and depreciation.
Reality: Tenant A excludes capital improvements and depreciation. Tenant B excludes capital improvements, depreciation, and executive salaries. Tenant C excludes capital improvements over $5,000. Tenant D excludes specific categories: legal fees, marketing, and leasing commissions. Tenant E has no exclusions.
The failure: The generic assumption includes expenses that should be excluded and excludes expenses that should be included. The CAM pool is wrong for every tenant.
The Scale Math
| Metric | 10 Tenants | 50 Tenants | 100 Tenants |
|---|---|---|---|
| Lease terms to track | 50 | 250 | 500 |
| Monthly calculations | 10 | 50 | 100 |
| Annual true-up calculations | 10 | 50 | 100 |
| Potential error points | 500 | 2,500 | 5,000 |
| Review hours per month | 2 | 10 | 20 |
| Error rate (manual) | 2% | 5% | 10% |
| Annual error cost | $5,000 | $25,000 | $100,000 |
At 100 tenants, the manual process produces $100,000 in annual errors. The review process requires 20 hours per month. The controller spends half their time on reconciliation and half on everything else.
The Lease-Specific Rules Requirement
Managing 100 different leases requires a system that stores and applies 100 different rule sets:
Rule storage. Each lease's terms are stored as structured data: pro-rata percentage, escalation schedule, cap structure, exclusion list, base year, gross-up requirement.
Rule application. Every calculation uses the specific lease's rules, not a generic assumption. Tenant A's cap is applied to Tenant A. Tenant B's exclusion is applied to Tenant B.
Rule updates. When a lease is amended, the rules are updated. The system tracks the amendment and applies the new rules from the effective date.
Rule validation. Every calculation is validated against the lease clause that authorizes it. The citation is stored with the result.
Conclusion
A 100-tenant property with 100 different leases is not a bigger version of a 10-tenant property. It is a different problem. The complexity is exponential. Generic assumptions fail. Lease-specific rules are required.
The fix is not more spreadsheets. It is a system that stores 100 rule sets and applies them correctly every time.
Komod.ai is an AI-native operating layer for the commercial real estate back office. The platform reads leases, invoices, and bank activity; performs deterministic calculations; and stages completed work for human approval. Nothing posts without you.