Most lease portfolios don't have too little data. They have too much of it, sitting in too many places, each version updated on a different day by a different person.
The original signed lease. The document capturing the first amendment. A spreadsheet someone built to track key dates for the properties they personally manage. The accounting system holding a separate abstraction for ASC-842. A folder of PDFs from the landlord's most recent CAM package. Each one is accurate at the moment it's created. None of them talk to each other.
That disconnect has a cost, and it's rarely visible until something goes wrong.
Where the Gap Shows Up
- Two teams, two versions of the truth. Real estate holds one record of the lease terms. Accounting holds another. AP has whatever the landlord's most recent invoice implies. When the three disagree, someone has to reconcile them manually — and until that happens, decisions get made on whichever version happened to be closest at hand.
- Amendments that exist in one place and not another. A lease gets amended. The signed document lands in a shared drive. The rent schedule spreadsheet doesn't get updated. Months later, the location is still being invoiced at the old rate, and nobody notices because the system generating the invoice was never told anything changed.
- Reporting that reflects yesterday's portfolio, not today's. A report pulled from disconnected sources is only as current as its slowest input. If one location's data hasn't been touched in months, the portfolio-wide summary quietly inherits that staleness, with no flag to indicate which numbers are current and which aren't.
- No way to answer a simple question quickly. “How many locations have a renewal option expiring in the next 90 days?” should take minutes to answer. When the answer requires checking five different systems and reconciling what each one says, it takes days — and by the time it's answered, the window may already be closing.
Why This Keeps Happening
Disconnected data isn't usually the result of one bad decision. It accumulates. A spreadsheet gets built to solve one team's immediate problem. A new tool gets added without retiring the process it was meant to replace. A location gets acquired with its own set of records that never fully merges into the existing system. Each addition made sense at the time. The sum is a portfolio where no single record can be trusted as complete.
What a Single Source of Truth Actually Requires
Fixing this isn't about picking a new piece of software and hoping the old data migrates cleanly. It requires:
- A defined system of record for lease terms, with every other document treated as a reference, not a competing source.
- A process for updating that record the moment a lease changes — not at the next scheduled review.
- Regular reconciliation between the lease record and the systems downstream of it, especially AP and accounting.
None of this is complicated in principle. It just requires someone whose job is to keep the record accurate, consistently, across every location — not as a side project alongside twenty other responsibilities.
The cost of disconnected lease data rarely shows up as a single event. It shows up as a slow accumulation of small discrepancies, each one small enough to overlook and consistent enough to add up.
Property Works keeps lease data centralized, current, and consistent across every location in your portfolio — so the answer to “what does the lease actually say” is always the same, no matter who's asking or which system they're looking at. propertyworks.com/contact