Long Voyage.

I.

The Peculiar Position

"The identity of a product is not always defined by its architects. Sometimes the market decides — and the architects discover what they built only afterwards."

SAP RE-FX was never a failed product. It has survived, adapted, and remained quietly indispensable to a significant constituency of users. What it has never managed is to answer, with any conviction, the question of what it actually is.

This is not an accident of poor design. SAP has always excelled at linear processes — procurement, production, sales — domains where goods move, invoices get posted, and transactions close. Real estate does not behave like an industrial product. It is not manufactured, consumed, and replaced. It is an asset that generates value from itself — indefinitely, if properly maintained. The underlying logic is closer to that of a bank or investment house than to anything found on a factory floor.

That RE-FX exists at all is therefore something of an achievement — and one that owes more to the quality of its engineering than to the clarity of its mandate. It does its job very well — at least that is what we can say as consultants, since nobody outside of SAP has ever seen the programme code. Rumour has it that after fifty years of uninterrupted service a golden card arrives, bearing the transaction code that reveals it. Nobody has qualified yet — though some, on both sides of the consulting divide, must be getting close.

SAP's first real estate module — Classic RE, introduced around 1990 — had the advantage of a narrow focus: German residential property management. Base rent, service charges, ancillary cost settlement, one contract per unit. The transition to RE-FX in the early 2000s replaced that specificity with flexibility — the suffix says as much. Multiple units per contract, lease-in as a first-class scenario, elastic enough for divergent legal regimes. But flexibility is a capability, not a direction. The question that Classic RE never had to ask — flexible for whom? — now stood open and would remain so for a remarkably long time.

SAP's first attempt at an answer was to extend RE-FX toward the physical reality of buildings — room reservation, floor plan integration via Visual Enterprise, rudimentary space management. The room reservation function travelled a considerable distance across multiple release cycles without ever quite arriving anywhere useful — an Odysseus who never found his Ithaca. These were attempts to find identity through functional expansion. The expansion did not produce one.

That this question was ultimately answered not by SAP but by the circumstances surrounding it is perhaps the most instructive observation. There is, within this pattern, one notable exception. It will require its own discussion.

II.

The Identity Problem

Specialised real estate software tends to know what it is. Yardi, the global market leader in property management, serves landlords — and everything in its architecture reflects that singular focus. At the national level, the picture is sharper still. In Switzerland, specialised providers cover residential management with a depth that includes the legally mandated indexation mechanisms required by Swiss tenancy law — processes that in RE-FX must be built from scratch. It is an old problem in software: open the product to everyone, and you risk losing the home markets to those who never left.

But this concerns only the lease-out side — the companies whose core process is holding property and extracting yield from it. On the other side of the equation sit the corporates — organisations for which real estate is, after salaries, often the second-largest factor on the balance sheet, yet never the core business. The same company may own production facilities with unexploited letting potential while simultaneously leasing hundreds of branch offices simply to function. A substantial exposure on both sides — and one that, for much of its history, was not recognised at board level for what it represented. One might observe that this particular blind spot was not confined to the clients.

Two constituencies, then. Real estate companies, for whom letting is the business. Corporates, for whom property is a cost to be managed. RE-FX was capable of serving both, in configurations so different they barely resemble each other. And a question that SAP at no point answered with a conscious strategic choice: which of these two is RE-FX actually for?

The answer, when it finally came, would not come from SAP.

III.

IFRS 16 and the Compliance That Shaped RE-FX

The International Financial Reporting Standard 16, mandatory from 2019, changed the accounting treatment of leases in a way that was transformative for RE-FX. Where operating leases had previously been recognised as periodic charges in the income statement — a monthly outflow and little more — IFRS 16 demanded their capitalisation on the balance sheet: right-of-use assets, corresponding lease liabilities, amortisation schedules. What had been invisible to investors and analysts became visible overnight.

For RE-FX, the consequence was immediate. Organisations that had never considered themselves real estate players were forced to behave like them. Fleet operators, retailers, logistics companies, professional services firms, manufacturers, banks, insurers — all suddenly needed a system to model, calculate, and report lease obligations at scale. RE-FX, already embedded in the SAP ecosystem, was the available answer.

This should be said clearly: IFRS 16 did not validate RE-FX as a product. It rescued it as a platform. The identity question — lease-in or lease-out, real estate company or corporate, or even a chimera of both — was not resolved. It simply became less urgent. The compliance use case displaced the strategic one, and RE-FX became, for a significant part of its user base, a lease accounting engine with a large quantity of unused capability sitting quietly alongside it.

The conclusion is difficult to avoid: RE-FX's current position was arrived at rather than chosen.

IV.

Planon — The Right Decision

SAP's announcement in 2023 of a global partnership with Planon was, for many in the industry, a strategic surprise. It should not have been.

The underlying logic is correct — perhaps even overdue. Facility management, space optimisation, maintenance workflows, CAFM, IWMS: these are operationally intensive, spatially granular domains that require interfaces built for operators on-site, not for back-office administrators. The decision to delegate this to a specialist rather than continuing to develop it internally is, on its merits, the right one.

Both parties retain what they do best: SAP keeps contracts, postings, valuations, and compliance logic. Planon retains operational granularity. The bet is asymmetric — and it is a good bet.

The more interesting question is what SAP does with what remains.

V.

LUM — The Diamond in the Drawer

If the partnership with Planon represents SAP's most visible recent decision in the RE-FX landscape, the Land Use Module represents its most conspicuous non-decision — and, on examination, the more consequential one.

LUM records that a piece of land exists, what sits on it, and who is responsible for it. The administrative history is maintained down to the Liegenschaftsbestandsverzeichnisfortschreibungsbeleg.

The need it addresses is not German. It is universal: road authorities, railway companies, utilities, telecommunications operators, former state monopolies, national infrastructure portfolios — on every continent.

A modular, country-adaptable system is not a vision. It is an engineering task. And not a particularly large one.

VI.

What Remains

The remaining question is whether SAP can invest in what it can do with the same resolve with which it has delegated what it cannot. These are not the same capabilities. The first is risk management. The second is vision.

LUM is not a problem to be managed. It is a product to be built — modular, country-adaptable, and aimed at a global market that currently has no comparable offering within any major ERP ecosystem. The engineering effort is modest. The addressable constituency is not. The diamond is in the drawer.