Intercompany Leases: Elimination in SAP Group Reporting

Intercompany leases are everywhere: a real estate entity leases office space to operating companies, a fleet entity leases vehicles and equipment to sister companies, a holding company owns production assets used by subsidiaries. In the consolidated financial statements, none of these leases exist – the group simply owns and uses its own assets.

Under the old lease standards, operating leases between group entities largely eliminated themselves: rent expense on one side, rent income on the other. Under ASC 842 and IFRS 16, that symmetry is gone. This article explains why, and what it means for elimination design in SAP Group Reporting.

Why Intercompany Leases No Longer Eliminate Automatically

The lessee and the lessor now account for the same lease differently:

The lessee recognizes a right-of-use (ROU) asset and a lease liability. Under IFRS 16, it records depreciation and interest. Under ASC 842, it records depreciation and interest for finance leases, and a single straight-line lease cost for operating leases.

The lessor in an operating lease keeps the underlying asset on its balance sheet, depreciates it, and recognizes lease income. In a sales-type or finance lease, it derecognizes the asset and recognizes a net investment in the lease.

Intercompany leases do not eliminate automatically on consolidation. The balance sheet items on both sides have no natural counterpart, and the income statement items rarely match in amount or timing.

What the Group View Must Look Like

From the group's perspective, the result is straightforward:

• the underlying asset stays on the consolidated balance sheet at the owner's carrying amount, with its normal depreciation,

• no ROU asset, lease liability, lease receivable, or net investment remains,

• no intercompany lease income, lease expense, interest, or ROU depreciation remains,

• related deferred tax effects are adjusted where relevant.

If the lessor has classified the lease as sales-type or finance and derecognized the asset, the group must reinstate the asset at its original carrying amount and eliminate the selling profit. The asset never left the group.

Typical Elimination Pairs

The elimination has to be designed item by item. Common pairs include:

• Lessee lease liability against lessor lease receivable (finance and sales-type leases) or against the lessee's ROU asset where the lessor has no receivable (operating leases),

• Lessee ROU asset – eliminated in full,

• Lessee interest expense and ROU depreciation (or single lease cost) against lessor lease income or interest income,

• Lessor net investment and selling profit – reversed, with the underlying asset reinstated.

The amounts on both sides will differ. The lessee's depreciation and interest pattern is not the lessor's straight-line income. These differences have to land somewhere – in a defined difference item, with a clear rule for whether they go to profit or loss or to equity.

How SAP Group Reporting Supports This

SAP S/4HANA for Group Reporting offers the building blocks:

• Partner unit: Elimination relies on the partner consolidation unit, so no dedicated intercompany accounts are required – but every intercompany lease posting must carry the trading partner.

• Reclassification methods: Rule-based elimination (task 2041 for payables and receivables, task 2011 for revenue and cost, task 2021 for other income and expense) eliminates values by FS item and partner, with offsets to keep each consolidation unit in balance.

• ICMR-integrated elimination (task 2042): Elimination methods link a reconciliation case in Intercompany Matching and Reconciliation with posting rules. Differences can be broken down into transaction, translation, and other differences.

• Posting levels: Reported data sits at posting level 00. Two-sided eliminations post at posting level 20.

Elimination only runs on data translated into group currency, so currency translation must be complete first.

Design Decisions That Matter

1. Capture the partner at the source.

The lessee side often comes from RE-FX, the lessor side from SAP Revenue Accounting and Reporting (RAR) or other revenue processes. Both must post with the partner company. Without the trading partner, the elimination cannot find the posting.

2. Define dedicated FS items for lease balances.

ROU assets, lease liabilities, lease income, and net investments should be identifiable as separate FS items. Mixing them with other balances makes rule-based elimination imprecise.

3. Match before you eliminate.

Intercompany leases are a good candidate for ICMR. The lessee's liability and the lessor's receivable will rarely match exactly. Matching shows whether differences come from timing, classification, or errors.

4. Handle classification differences.

The same intercompany lease can be operating for the lessor and on-balance-sheet for the lessee, and classification can differ between US GAAP and IFRS. The elimination logic must cover each combination, per accounting principle.

5. Keep the underlying asset clean.

If the lessor retired the asset in FI-AA because of a sales-type classification, the group needs a consistent way to reinstate it, including its depreciation going forward.

Common Pitfalls

• Partner information missing on RE-FX or RAR postings.

• Eliminating the lessee side but not reversing lessor selling profit.

• No defined difference item, so mismatches end up in random accounts.

• Treating intercompany leases as a year-end topic instead of a monthly close task.

Related Articles

• Intercompany Revenue and Profit in Inventory Elimination

• Multi-GAAP Consolidation: US GAAP and IFRS in One System

• Lease-In and Lease-Out: Connecting SAP CLM and RAR

The Bottom Line

Under ASC 842 and IFRS 16, intercompany leases need deliberate elimination design. SAP Group Reporting provides partner-based reclassification, ICMR-integrated elimination, and clear posting levels – but the quality of the result depends on partner data at the source, dedicated FS items, and rules that reflect how both sides actually account for the lease. Design it once, and it becomes a routine close step.

Consolidating intercompany leases in SAP? Talk to our experts.