Corporate real estate management software: what it is, and why landlord systems do not fit

Corporate real estate management software is the set of systems a company uses to manage the property it occupies in support of its own business: the leases, the occupancy cost, the space, the facilities, the capital projects and the transactions. CoreNet Global defines corporate real estate itself as "the real properties that house the business activities of an organization that owns or leases and manages real estate incidental to its primary business, which is not real estate" (CoreNet Global).

That last clause does the work. The real estate is incidental. It is where the business happens, not what the business is, and every design decision in this software category follows from that.

Corporate real estate is not commercial real estate#

The two terms get used interchangeably and the systems do not interchange at all. CoreNet Global states the distinction in one sentence: "the goal for commercial real estate is to generate a return and the goal for Corporate Real Estate is to support the business."

Follow that through to the software. A platform built to generate a return is organised around the asset, because the asset is the thing that appreciates, produces income and eventually gets sold. Its core objects are the property, the rent roll, the tenant and the yield. A platform built for an occupier cannot be organised that way, because the occupier does not own most of its estate, cannot sell it, and captures no yield from it. What the occupier holds is a set of obligations with dates and costs attached, and a set of decisions about whether to keep holding them.

So the natural core object for an occupier system is the lease and what it commits the company to, not the building and what it earns. That sounds like a semantic distinction until you try to answer an occupier question in a landlord system and find there is nowhere to put the answer.

What the corporate real estate function actually owns#

Worth setting out, because the software map follows the responsibility map. CoreNet Global describes corporate real estate professionals as managing "a corporation's global real estate footprint" and driving "location strategy, occupancy planning, portfolio management, space optimization, and workplace innovation to support business goals," across offices, data centres, manufacturing, logistics, retail and more.

In day to day terms that resolves into a fairly consistent list. Knowing what the company has committed to and by when. Paying only what the leases require. Meeting accounting and disclosure obligations. Keeping sites open and compliant. Delivering new locations and refits. Deciding what to renew, consolidate, relocate or exit. CoreNet's own framing of portfolio management ends with the line that captures the whole job: "the goal of CRE is to provide the right space, in the right place, at the right time."

The seven categories, and what each is for#

No single product covers all of this well, which is why most occupiers run several and reconcile between them. This is the map.

The pattern worth noticing is that the lease record sits underneath five of the seven. The tax pass-through you are checking, the escalation you are paying, the repair you are about to dispatch and the disclosure you are about to file all resolve back to a clause. When the lease data is wrong or stale, the failure surfaces somewhere else entirely, as a payment, a work order or an audit comment, which is why the cause is so rarely diagnosed.

Why landlord-first systems feel wrong in an occupier's hands#

Several of the best known platforms in this space were built landlord-first and extended toward occupiers later. They work, and plenty of large occupiers run them. The friction is consistent and it is worth naming, because buyers tend to assume they are using the system badly rather than using a system built for a different job.

The data model puts the property at the centre, so an occupier ends up managing leases as attributes of buildings rather than buildings as consequences of leases. Recoverability runs the wrong way: a landlord system is designed to bill CAM out, while an occupier needs to check CAM coming in. Reporting defaults to income and yield rather than committed cost and flexibility. And the awkward questions, whether this charge matches the clause, whether this option is still live, whether this repair is ours, sit outside the model entirely, because for a landlord they are not questions.

The broader category picture, including where landlord and investor systems fit, is in commercial real estate software.

How to evaluate it#

Feature checklists are close to useless here, because every vendor ticks every box and the differences only appear in month four. Five questions separate the field.

1. 01Can it trace an answer to its source? When the system says the escalation is 3.5 percent capped at 4, can it show the clause it read that from, in the document, without someone opening a PDF? Everything else in this list depends on that one.
2. 02What happens when the lease changes? An amendment should propagate to the schedule, the accounting, the critical dates and the pass-through checks. If it propagates to one of them, you have four registers to keep in step by hand.
3. 03Does it handle the obligations, not just the dates? Critical dates are the easy part. Repair allocations, exclusions, caps, audit rights and notice requirements are where the money is, and most systems store them as free text if at all.
4. 04Can it check as well as record? A system that tells you what you paid is a ledger. A system that tells you what you should have paid is worth buying.
5. 05Where does it meet the ERP? Lease accounting output, AP and the general ledger have to reconcile, and the integration is usually where implementations run long.

Portfolio scale changes the weighting. Under fifty leases, most of this can be run competently on spreadsheets and discipline. Past a few hundred, spread across jurisdictions and lease forms, the reconciliation between systems becomes the job, and the case for a single record underneath them becomes financial rather than aesthetic. That threshold question is covered in real estate portfolio optimisation.

Who owns it, and where it sits#

Corporate real estate software rarely has one owner, which is the root of a lot of duplicated data.

Lease administration usually sits with the corporate real estate team. Lease accounting sits with finance or technical accounting. Facilities sits with operations or FM. Capital projects sits with construction. Financial operations touches accounts payable. Each has its own system, its own vendor relationship and its own version of the site list, and the version differences are exactly where cost leaks.

The practical arrangement that works is a single lease record owned by one team, with the other systems reading from it rather than keeping their own copy. That is less a software decision than a governance one, and it tends to be settled by whoever is accountable for occupancy cost. What makes it possible is the underlying record being accurate and current, which is lease abstraction work, and portfolio strategy is where the decisions it enables get made.

The short version: corporate real estate software exists because occupiers have a different problem from owners. CoreNet has been saying so for years. The software market is still catching up.