There is a version of ASC-842 that is manageable. A contained portfolio, consistent lease structures, a stable team, and a system that has been kept current. For organisations in that position, the standard is demanding but not disruptive.
Then there is what happens when a business grows fast.
Acquisitions bring leases that were tracked in someone else's system, or not tracked in a system at all. New market entries introduce landlords with unfamiliar lease structures and jurisdiction-specific quirks. The team responsible for lease accounting is the same size it was when the portfolio was half as large.
The standard does not change as the portfolio grows. The exposure does.
When finance leaders think about the complexity that comes with portfolio growth, the instinct is often to focus on the number of leases. More leases mean more remeasurements, more disclosures, more records to maintain. That is true, but it is not the most significant source of complexity.
The more consequential challenge is variability.
A portfolio of 200 leases where every lease follows the same structure, the same rent escalation mechanics, and the same renewal option framework is demanding but manageable. A portfolio of 80 leases where the structures vary significantly across asset class, geography, and landlord is more complex by almost every measure.
Variability creates judgement calls. What lease term is appropriate when a renewal option is reasonably certain to be exercised for some leases but not others? How should variable rent components be treated when lease terms differ across locations? How does a modification to one lease in a group of related leases affect the accounting for the others?
These are not edge cases. They are the ordinary challenges of a growing, diversified real estate portfolio. And they are significantly harder to manage without experienced people and systems designed to handle them.
For businesses that operate across multiple legal entities, ASC-842 compliance becomes a consolidation exercise as well as a lease accounting one. Each entity may have its own lease population, its own chart of accounts, and its own reporting timeline. Producing consolidated disclosures requires reliable data from all of them.
When lease data is maintained in separate systems or separately managed spreadsheets across entities, consolidation becomes a manual process completed under time pressure at each reporting period. The risk of inconsistency is high and the time required is substantial.
Purpose-built lease accounting software that supports multi-entity structures allows consolidated reporting to be generated from a single platform. The practical benefit is not just efficiency. It is reliability, because the consolidated figures are drawn from the same underlying data rather than reconciled from multiple independent sources.
This is a detail that gets overlooked during initial ASC-842 implementation and creates problems at scale, particularly in the restaurant and retail sectors.
Businesses that operate on a 52/53-week fiscal year, or on a 4-4-5 or 4-5-4 calendar structure, have lease accounting periods that do not align with the calendar year. When lease accounting software calculates amortisation, remeasurement adjustments, and rent expense on a calendar-month basis, the figures require manual translation at every reporting period to fit the company's actual fiscal structure.
At small portfolio sizes, that translation is manageable. At scale, it is a recurring source of reconciling items that consumes finance team time and creates audit questions.
The right system handles the fiscal calendar the business actually uses, not the one that is easiest to programme.
Staying in control as a portfolio grows is not primarily a technology question, though technology matters. It is a process and people question.
The organisations that manage ASC-842 well at scale tend to share a few characteristics. Lease events are captured promptly, not batched for periodic updates. Remeasurements are triggered automatically when modifications are recorded rather than scheduled manually. Documentation is attached to records at the time of the event rather than assembled later. And there is clear ownership of the lease accounting process across real estate, finance, and operations teams.
That combination of good process and appropriate systems means that growth adds complexity that is manageable rather than complexity that is uncontrolled.
The warning sign that control is being lost is not usually a dramatic failure. It is a pattern of small problems: schedules that are slightly off, documentation that takes too long to produce, remeasurements that are completed after the close rather than as part of it. Each of those on its own is minor. Together, they indicate that the process is not scaling with the portfolio.
The best time to address lease accounting infrastructure is before a growth event, not after. An acquisition that doubles the portfolio in 90 days is not the moment to discover that the existing system cannot handle the volume or the structural variation of the new leases.
A scalability assessment of the current lease accounting environment gives finance leaders an honest view of where the gaps are and what investment is needed to maintain control through a period of growth. That kind of preparation is considerably less disruptive than the alternative.
To request a scalability assessment for your portfolio, contact Property Works at https://www.propertyworks.com/contact