SAP RE‑FX, CLM and IFRS 16: choosing the right deployment model

RE‑FX and CLM: parallel development with a long-term perspective

RE‑FX has been established as SAP's commercial real-estate management solution since 2004. CLM is already available in parallel and is being developed progressively; its current functional focus is lease accounting and IFRS 16.

• Today: In Private Cloud and on-premise, RE‑FX and CLM can run separately or in parallel. Public Cloud provides the independent CLM scope.
• Functional scope: RE‑FX continues to cover the broader commercial real-estate management scope. CLM is not currently functionally equivalent and is being expanded in line with SAP's roadmap.
• Maintenance: RE‑FX is part of the respective SAP S/4HANA release and generally follows its product lifecycle. From SAP S/4HANA 2023, SAP provides seven years of mainstream maintenance per release.
• Long-term perspective: SAP has published an innovation commitment for S/4HANA until the end of 2040. Until then, at least one S/4HANA release is intended to remain in maintenance.

Two decisions: product scope and operating model

CLM and RE‑FX are not interchangeable labels. CLM focuses on contract and lease-accounting processes; RE‑FX adds commercial real-estate management. Only after selecting the product scope should the deployment model be chosen.

CLM and RE‑FX: compare product and deployment separately

CLM and RE‑FX are different functional scopes. The product must therefore be selected before the deployment model.

Which solution is available in each edition?

Product availability by deployment model

Product	Public Cloud	Private Cloud	On-premise
Contract and Lease Management (CLM)	✓ AvailableIndependent, standardised cloud scope focused on lease accounting.	✓ AvailableCLM as a separate functional and licensed scope.	✓ AvailableCLM as a separate functional and licensed scope.
Flexible Real Estate Management (RE‑FX)	— Not includedRE‑FX is not part of SAP S/4HANA Cloud Public Edition.	✓ Separately availableCommercial real-estate management; not equivalent to CLM.	✓ Separately availableCommercial real-estate management; not equivalent to CLM.
Parallel operation of CLM and RE‑FX	— Not applicablePublic Cloud provides the independent CLM scope only.	✓ PossibleCLM and RE‑FX can run in parallel with the required licences and activation; their functional scopes remain separate.	✓ PossibleCLM and RE‑FX can run in parallel with the required licences and activation; their functional scopes remain separate.

What functional scope does the selected product provide?

The matrix shows the typical standard scope. Licensing, activated components, country coverage and release level must be verified in the specific customer system.

✓ Available△ Limited / verify— Not included

CLM Public Cloud compared with CLM and RE‑FX in Private Cloud and on-premise

Functional area	CLM Public Cloud Lease accounting	CLM Private Cloud / on-premise	RE‑FX Private Cloud / on-premise
Product and process focus	△ Cloud scopeStandardised capture, valuation and posting of lease contracts with an IFRS 16 focus.	✓ Lease accountingContract and lease-accounting scope with greater configurability than Public Cloud.	✓ Commercial real-estate managementReal-estate objects, leases, conditions, postings and integrated lease accounting.
Real-estate master data and portfolio hierarchy	△ CLM object referenceCLM references and generic rentable objects for contract and valuation scope; no comprehensive real-estate portfolio hierarchy.	△ Contract-related scopeObject references for lease contracts but no complete commercial RE‑FX portfolio scope.	✓ RE‑FX object modelBusiness entities, land, buildings, rental objects and other commercial object structures.
Lease and real-estate contracts	△ StandardisedLease contracts for capture, valuation and financial posting.	✓ CLM contractsLease-in/lease-out and configurable contract and valuation processes within CLM scope.	✓ RE‑FX contractsComprehensive real-estate contract types with conditions, partner roles, terms, options and posting processes.
IFRS 16 lessee accounting	✓ Core functionStandardised contract valuation and financial postings within the approved cloud scope.	✓ ComprehensiveLease accounting with extensive configuration and FI-AA integration.	✓ ComprehensiveRE‑FX lease accounting integrated into commercial real-estate management.
ASC 842, local GAAP and parallel valuations	△ Verify scopeVerify valuation rules by release, country and activated scope.	✓ ConfigurableMultiple accounting standards and valuation rules can run in parallel.	✓ ConfigurableParallel valuations within RE‑FX lease accounting.
Account determination, flow types and posting logic	△ StandardisedApproved derivation from valuation rule through flow type and account symbol to G/L account.	✓ FlexibleExtensive CLM account determination and configurable posting logic.	✓ Maximum flexibilityRE‑FX account determination, reference flow types, n:n assignments and extensions.
Indexation, rent adjustment and sales-based rent	△ Scope- and country-dependentFree and index-based condition adjustments are available in documented Public Cloud Best Practice scenarios. Sales-based rent is documented as country-specific scope 3F4; the scope is not equivalent to the complete RE‑FX adjustment methods.	△ Verify CLM scopeContract adjustments within the applicable CLM and valuation scope; not equivalent to RE‑FX.	✓ RE‑FXIndex, stepped and other adjustment methods plus sales-based rent processes.
Service-charge and operating-cost settlement	△ Cost SettlementSimplified cost distribution; no complete commercial service-charge settlement and not automatically compliant with DACH legal requirements.	△ Verify licence/scopeNot automatically part of a CLM lease-accounting scope.	✓ RE‑FXSettlement units, participation groups, apportionment logic and integrated adjustment processes.
Space, occupancy and usage management	△ Object reference, not space managementUsable and rentable objects can be assigned to contracts. Native area calculation, occupancy planning and workplace management are not documented as CLM core scope; SAP specifically provides integration with Planon for this purpose.	— No full space managementCLM remains focused on contract and lease-accounting processes.	✓ Commercial RE‑FX scopeSpace and usage structures; not a complete CAFM solution.
Technical facility management / CAFM	△ SAP EAM available; CAFM separateSAP S/4HANA Cloud Public Edition provides Maintenance Management with functional locations, equipment, notifications, orders and maintenance plans. This separate EAM scope is not part of CLM and does not replace a complete CAFM solution.	△ External integrationNo CAFM in CLM; SAP EAM/PM or an external CAFM system is required.	△ External integrationRE‑FX is commercial; SAP EAM/PM and external CAFM systems are integrated.
Planon Real Estate Management	✓ Standard integrationExternal third-party system; documented integration through SAP Master Data Integration and UI integration.	✓ IntegrablePlanon can be connected through documented SAP integration scenarios.	✓ IntegrablePlanon can be connected as an external real-estate/CAFM system.
SAP Business Technology Platform (BTP)	△ Extension platformBTP enables apps, workflows and integrations but does not expand native CLM scope.	△ OptionalSide-by-side extensions, integration and clean-core scenarios.	△ OptionalAdditional integration, app and extension platform.
Reporting and analytics	△ Cloud standardFiori apps, CLM Dashboard and released CDS views.	✓ BroadCLM evaluations, Fiori, embedded analytics and bespoke reports.	△ Classic and customer-specificRE‑FX evaluations, classic information systems and bespoke reports; modern analytics are available only selectively.
Fiori UX and released data models	✓ Fiori-firstStandardised Fiori interfaces and released CDS views within the respective Public Cloud scope.	△ Release- and scope-dependentFiori apps, embedded analytics and technical data models depend on the release and activated scope.	△ Limited coverageIndividual RE‑FX Fiori apps are available. The broad core remains SAP GUI-oriented; a complete, publicly released RE‑FX CDS data model is not available.
Product development and roadmap	✓ Strategic innovation pathCloud- and IFRS 16-oriented development along the SAP roadmap.	△ Incremental expansionCLM continues to be developed in parallel; the current focus is lease accounting and IFRS 16.	△ Maintenance and selective changesThe strategic innovation focus is on CLM. RE‑FX is maintained within the S/4HANA lifecycle; public evidence supports selective, release-related and regulatory changes, but no comprehensive modernisation roadmap.
APIs, BAdIs and extensions	△ Released extensionsReleased APIs, communication scenarios, key-user and cloud BAdIs.	✓ ExtensibleCLM BAdIs, APIs and customer extensions according to operating model.	✓ ExtensibleRE‑FX BAdIs, BAPIs, RFC, IDoc, OData and custom code.
Best suited for	Standardised lease accountingIFRS 16-oriented scenarios without comprehensive commercial real-estate management.	Configurable lease accountingMore complex lease contracts and valuations without the complete RE‑FX real-estate scope.	Commercial real-estate managementReal-estate objects, contracts, settlement and lease accounting in a broader RE‑FX scope.

Private Cloud and on-premise: comparable product scope, different operating model

SAP describes the functional scope of Private Edition as comparable to SAP S/4HANA on-premise. The key differences therefore lie less in CLM or RE‑FX and more in operations, infrastructure, release control and technical responsibility.

Operating-model comparison for CLM and RE‑FX

Criterion	Private Cloud	On-premise
Functional basis	✓ Comparable S/4HANA scopeCLM and RE‑FX can run individually or in parallel.	✓ Comparable S/4HANA scopeCLM and RE‑FX can run individually or in parallel.
System and infrastructure model	Single tenant / managed cloudDedicated customer instance; infrastructure at SAP or a hyperscaler depending on contract.	Customer-operatedInfrastructure in the customer data centre or with a provider selected by the customer.
Operating responsibility	Shared / contractually definedSAP or the agreed provider owns defined technical operations; the customer remains responsible for processes, Customising and tests.	Customer-ownedCustomer owns infrastructure, basis operations, maintenance, security and technical organisation.
Release and upgrade control	Contractual lifecycleUpgrades are jointly planned within the SAP lifecycle; deadlines and operating windows apply.	Maximum scheduling controlCustomer selects upgrade timing within maintenance and product support.
Customising and extensions	✓ HighClassic Customising, BAdIs and custom code are possible; clean-core and contractual operating boundaries apply.	✓ MaximumBroadest technical access to Customising, custom development and system configuration.
Direct technical access	△ ControlledOperating-system, database and basis access follows the managed-service contract.	✓ Fully controlledCustomer controls system, database and infrastructure access.
Migration	✓ Greenfield and system conversionExisting S/4HANA/ERP landscapes can be transformed depending on starting point.	✓ Greenfield and system conversionNew implementation or customer-controlled system conversion.
Best suited for	Comparable functional scope with outsourced technical operations and a cloud contract model.	Maximum technical control and full customer-owned operating responsibility.

Key message: CLM and RE‑FX are not the same. Public Cloud provides an independent CLM scope. In Private Cloud and on-premise, CLM or RE‑FX can be used as different functional and licensed scopes. A deployment decision therefore does not replace product selection.

SAP S/4HANA Cloud Public Edition: fit-to-standard with a defined scope boundary

Contract and Lease Management in Public Cloud supports standardised lease-contract and valuation processes with an IFRS 16 focus. RE‑FX is not part of this edition. CLM Public Cloud does not provide a comprehensive commercial real-estate management scope. Configuration, apps, roles, APIs and extensions follow the approved cloud scope.

Suitable when: processes can largely adopt the standard, regular releases are accepted and deviations can be covered through approved cloud extensions or connected solutions.

Verify: scope items, country coverage, lease-in and lease-out, valuation requirements, account determination, APIs, migration and required DACH processes. CLM Public Cloud must be assessed as an independent product scope and does not replace comprehensive commercial real-estate management.

Private Cloud: CLM or RE‑FX depending on functional scope

SAP S/4HANA Cloud Private Edition can run CLM and RE‑FX individually or, with the required licences and activation, in parallel. CLM addresses contract and lease-accounting processes; RE‑FX adds commercial real-estate management. Even in parallel operation they remain separate functional and licensed scopes. Clean-core principles, release planning, testing and technical operating boundaries still apply.

Suitable when: the selected CLM or RE‑FX scope must support complex leasing or commercial real-estate processes while defined technical operations remain outsourced.

On-premise: CLM or RE‑FX with maximum operating responsibility

CLM and RE‑FX can also run individually or in parallel on-premise. Their product scopes remain separate. This operating model offers the broadest scope for Customising, BAdIs, bespoke developments, direct data integration and release control. That freedom also increases responsibility for infrastructure, security, maintenance, regression testing and upgrades.

Suitable when: highly individual CLM or RE‑FX processes are business-critical and the organisation can sustain infrastructure, operations and development itself over the long term.

IFRS 16: separate the accounting requirement from SAP product scope

IFRS 16 defines the accounting for leases. Whether and how completely an SAP product automates those requirements is a separate product and implementation question. The system decision must therefore start from the accounting design: identification, initial and subsequent measurement, modifications, index changes, discounting, right-of-use asset, lease liability, closing and evidence.

Effective since 2024: Lease Liability in a Sale and Leaseback

The IASB amendment adds subsequent-measurement requirements for sale-and-leaseback transactions. It applies for annual periods beginning on or after 1 January 2024; earlier application was permitted. It is particularly relevant where variable lease payments exist and does not change the accounting for ordinary leases outside sale-and-leaseback.

System impact: entities need to identify affected transactions, calculation methods, historical data and posting logic. For SAP RE‑FX or CLM, projects must demonstrate whether the required subsequent measurement is supported in standard, corrected through notes or delivered by an additional solution. A generic statement of IFRS 16 support is insufficient.

IASB review in 2026: planned work, not new mandatory rules

In July 2026 the IASB concluded through its Post-Implementation Review that IFRS 16 is generally working as intended. It nevertheless decided on further work:

• Research into higher-than-expected costs of lessee accounting, especially remeasurements for index- or rate-dependent payments, discount rates and possible simplifications.
• A narrow-scope project on rent concessions where a lessor forgives lease payments that are already due.
• Potential future improvements to disclosures about lease-related cash flows.

Important: as at 2 September 2026 these PIR topics are not new mandatory IFRS 16 requirements. They belong in accounting and system monitoring but must not be implemented as if already effective. A separate sale-and-leaseback issue involving a single-asset entity was removed from the maintenance pipeline and may only return through a future agenda consultation.

Project decision matrix

• Process fit: Which real-estate and lease processes must remain unchanged, and which can adopt standard practice?
• Accounting: Which IFRS 16, local GAAP and, where relevant, ASC 842 scenarios require evidence?
• Extensions: Are classic Customising, BAdIs and bespoke apps required, or are approved cloud APIs sufficient?
• Integration: Which data originates in CAFM, procurement, finance, asset accounting, consolidation or third-party systems?
• Operations: Who owns releases, regression tests, SAP notes, security and closing controls?
• Road map: How will future IASB projects be monitored, assessed and implemented only after finalisation?

Note: This article provides a general professional perspective and does not replace entity-specific accounting, legal or system advice. Product scope and availability must be verified in the relevant system and contract. All information is provided without warranty.

← All news