Every property is an entity. Every lease is a rule set.
Change strategy, cutover checklists and business requirements for property-sector ERP. The thing that makes this sector its own discipline is structure: entities created and closed on a deal cadence, and lease and recovery terms that behave like configuration rather than like documents. Walk the five decisions, find your seat, then run the two-minute check.
Five calls that decide a property-sector program
Set early, and close to immovable once transactions land on them. Pick a decision.
The structure gets designed around the current portfolio, which is the one thing guaranteed to change.
Design the entity and property hierarchy for acquisition and disposition churn from the start, and test it against a hypothetical deal before signing off.
Entities in this sector are created and closed on a deal cadence. A structure that requires a reorganization to absorb an acquisition will get one, repeatedly, and each reorganization breaks comparability in reporting. Testing the design against a hypothetical acquisition and a hypothetical disposal costs an afternoon and saves years.
What happens to our structure when we buy three properties and sell one?
Lease terms, escalations, recovery calculations and exclusions live in documents, and the system gets configured from a summary of them.
Treat lease and recovery terms as configuration with an owner, and reconcile a sample against source documents before go-live.
Recovery calculations decide what tenants are billed and what the owner keeps. Configured from a summary, they will be approximately right, and approximately right is the kind of error that survives for years and then arrives as a tenant dispute or an audit adjustment covering multiple periods.
Who has reconciled configured recovery logic against actual lease documents?
Property management, lease administration and facilities systems already run, each with its own owner and its own version of the property record.
Name a client-side owner for each interface and agree the master for each shared record before design.
The recurring failure is two systems each holding a property or lease record and neither being definitively the master. Reconciliation then becomes a monthly manual task that nobody scoped, and the numbers diverge slowly enough that it is noticed late.
For each shared record, which system is the master, and who decided?
The plan targets a technical readiness date. Rent and recovery billing runs on a cycle tenants expect, and a wrong invoice reaches a customer.
Sequence cutover so the first billing cycle has slack, and staff that cycle as part of the program.
A wrong or late tenant invoice is a commercial and relationship problem, not a systems one, and it is the moment every lease and recovery decision gets tested at once. It deserves the same treatment a parallel payroll run gets in workforce-heavy sectors.
Who is staffed to run the first full billing cycle after cutover, by name?
Conversion scoping proposes limiting history to hold the schedule, which is reasonable in many sectors.
Decide historical retention with the people who handle disputes and audits, and write down what will no longer be answerable.
Lease history, recovery reconciliations and capital project records get asked about years later, often in a dispute. A limited conversion is defensible if somebody decided it deliberately and documented what was given up. It is indefensible if it was a schedule decision nobody surfaced.
What questions will we be unable to answer after cutover, and who signed that off?
What those five mean for the chair you sit in
Property programs get judged by owners, lenders and tenants. Each seat's exposure, the early sign, and the question worth asking this quarter.
Property truth lives in more than one place
Property, lease and facilities systems each hold a version of the record, and without a named master the reconciliation becomes a permanent manual task. The structural exposure is churn: a hierarchy that cannot absorb an acquisition produces a reorganization, and each one breaks comparability in your reporting.
No one can say which system is master for the property and lease records.
Which system is master for each shared record, and who decided?
Recovery logic decides real money
Recovery calculations determine tenant billing and owner economics. Configured from summaries rather than reconciled against documents, errors persist quietly and surface as multi-period adjustments or disputes. The first billing cycle after cutover is where all of it gets tested simultaneously.
Nobody has reconciled configured recovery logic to a sample of actual leases.
How many leases have we reconciled configuration against, and what did we find?
A small team carries a large estate
Property organizations run lean corporate functions supporting a wide estate, so the same handful of people are named on the program and the day job at once. That constraint decides your realistic pace more than the software does, and it is rarely modeled in the plan.
The same names appear on the program org chart and on the month-end close.
Who is on both the program and the close, and what have we backfilled?
Four drifts, and none of them announce themselves
Illustrative weighting from what these programs surface in practice, not a benchmark. The ranking is the point, not the heights.
All four look like normal operations while they mature. That is why they survive hypercare and become permanent features of the ledger.
Five questions worth more than a readiness assessment
Answerable from memory, scored on this page, nothing captured and nothing emailed.
These five are the start of the instrument. A full review also covers capital project accounting, intercompany design, the property systems inventory and the first-close plan. Or skip the tooling and book the program review.
Putting a portfolio on a new platform?
Pre-SOW, mid-build, or stabilizing after a rough first billing cycle. I sell no software and staff no builds, so these questions get asked out loud. Tell me where the program is and I will tell you what I see.