Commercial real estate accounting runs on spreadsheets. Not because property managers are behind the times. Because the software that was supposed to replace spreadsheets does not do the work.
Yardi, MRI, AppFolio, and QuickBooks are general ledgers. They store transactions. They do not read leases, interpret obligations, or determine what should be billed. That work still happens in Excel, by hand, every month.
This article examines why spreadsheets persist, where they break down, and what the missing layer looks like.
The Spreadsheet Dependency
Every commercial property manager knows the pattern:
- A lease is signed. The key terms are extracted into a spreadsheet.
- An invoice arrives. It is coded in the accounting system, but the CAM recovery calculation happens in Excel.
- Month-end approaches. Bank statements are downloaded. Reconciliation happens in a spreadsheet that someone built years ago.
- A tenant moves in or out. The pro-rata share is calculated by hand.
The accounting software records what happened. The spreadsheet determines what should have happened. The gap between the two is where revenue is lost.
Why Accounting Software Does Not Solve the Problem
Commercial real estate software was built to store data, not to interpret it.
Yardi and MRI are property management and accounting platforms. They track rent rolls, process payments, and generate reports. They do not read a 50-page lease and extract the CAM cap language. They do not compare the lease obligation to the actual billing. They do not flag that a tenant's pro-rata percentage changed three years ago and the spreadsheet was never updated.
QuickBooks is a general ledger for small business. It tracks income and expenses. It does not know that a specific expense is recoverable under Lease Section 4.2 but excluded under Lease Section 7.3. It does not compute a gross-up for a partially occupied building.
AppFolio serves residential and small commercial. It handles rent collection and maintenance requests. It does not manage NNN reconciliations or escalation compounding across a 100-tenant retail center.
These systems are databases. They answer "what did we record?" They do not answer "what should we have recorded?"
Where Spreadsheets Break Down
Spreadsheets fail in predictable ways:
Version control. The CAM reconciliation spreadsheet is on someone's desktop. Last year's version is on a shared drive. The version with the corrected formula is in an email attachment. Which one is current?
Formula errors. A cell reference breaks when a row is inserted. A cap calculation references the wrong year. An escalation formula uses the wrong base. The error compounds silently until an auditor finds it.
Key-person dependency. The controller who built the spreadsheet knows how it works. When that person leaves, the knowledge leaves with them. The new controller inherits a file with no documentation and no audit trail.
Scale failure. A spreadsheet that works for 5 properties breaks at 50. A manual process that works for 20 tenants fails at 200. The error rate increases with complexity, not linearly but exponentially.
No audit trail. When a tenant disputes a charge, the spreadsheet shows the result. It does not show the lease clause that authorized the charge, the calculation that produced it, or the person who approved it.
The Missing Intelligence Layer
The problem is not accounting software. The problem is the missing layer between the lease and the ledger.
That layer does four things:
- Reads the lease. Extracts obligations, dates, caps, exclusions, and recovery rights. Not as a summary, but as a structured rule set.
- Interprets the obligation. Determines what the lease requires: Is this expense recoverable? What is the tenant's pro-rata share? Is there a cap? What is the escalation formula?
- Reconciles to the ledger. Compares what the lease requires to what the accounting system recorded. Identifies variances before they become permanent.
- Stages the correction. Prepares the billing adjustment or journal entry with full documentation. A human approves before anything posts.
This is not a replacement for Yardi or QuickBooks. It is the layer that makes them work correctly.
The Spreadsheet Is a Symptom
Spreadsheets persist because the alternative is manual review of every lease, every invoice, every reconciliation. That is not scalable. The spreadsheet is the workaround.
The fix is not to ban spreadsheets. The fix is to automate the work that spreadsheets are doing poorly.
Komod.ai reads the lease, interprets the obligation, reconciles to the ledger, and stages the correction. The spreadsheet becomes a report, not a calculation engine. The controller reviews exceptions instead of building formulas.
Conclusion
Commercial real estate accounting relies on spreadsheets because the software stack has a gap. General ledgers record transactions. They do not interpret leases. The interpretation happens in Excel, by hand, with predictable error rates.
The solution is not better spreadsheet training. It is an intelligence layer that reads leases, applies the rules, and reconciles to the ledger automatically.
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.