Changing the Lessee of Contract Components

Getting Started

Global Functions

Lucanet Lume

Data Hub

Administration

Extended Planning & Analysis (xP&A)

Consolidation & Financial Planning

ESG Reporting

Disclosure Management

XBRL Tagger

Lease Accounting

General Functions in Lease Accounting

User Roles in Lease Accounting

All Steps at a Glance

Basic Configuration for Lease Accounting

Selecting a Lessee

Collecting Data

Creating and Configuring Lessors

Creating and Configuring Contracts

Creating and Configuring Contract Components

Importing Data Automatically

Viewing Import History

Reversing Components

Changing the Lessee of Contract Components

Categorizing Components

Calculating Data

Creating Postings

Reversing Postings

Exporting Reports and Postings

Importing Postings into Consolidation & Financial Planning

Banking & Cash Management

Data Collection

Tax Compliance & Reporting

Glossary

With a change of lessee, you transfer an active, calculated contract component from one lessee to another lessee as of a transfer date — for example, when a lease is taken over by another company of your group. You do not have to enter the component again for the new lessee.

A change of lessee always produces two results:

The

source component

is terminated in its reporting entity on the transfer date and receives the component event status

Terminated by change of lessee

new component

is created in the target reporting entity as a copy of the source component and receives the status

Added due to change of lessee

. The master data dimensions you specify for the target — cost center, profit center, and accounting area — are applied to the new component.

At group level, the disposal in the source reporting entity and the addition in the target reporting entity balance each other out.

Because a change of lessee usually affects several components at once, you transfer the components with a file upload: download the template, enter one transfer per row, and upload the completed file in the Change of lessee workspace.

Lucanet Lease Accounting validates each row of the uploaded file individually. A transfer is only performed if all of the following conditions are met; otherwise, the row is rejected with the reason, and no data is changed for that row:

The source component is a regular lease, is active, and has been calculated.

The source reporting entity and the target reporting entity are different.

The target reporting entity, the target contract, and the master data dimensions specified for the target exist.

The transfer date is the first day of a month and is in the past.

The transfer date is within the lease term of the component, is not the start date of the component, and — for transition components — is after the transition date.

No component events exist on or after the transfer date.

The liability currency of the source component matches the currency of the target contract.

The exchange rates required for the currency translation are available (see

Exchange Rate Management

To transfer contract components to another lessee:

Navigate to Data collection | Change of lessee.

Displays the Change of lessee workspace with the Download template button and the file upload area. — The 'Change of lessee' workspace

Click Download template. The template is downloaded as an XLSX file and contains the ChangeOfLessee sheet with a description and an example for each column, as well as an Instructions sheet.

Enter one transfer per row in the ChangeOfLessee sheet. For each transfer, specify the transfer date, the company code, contract number, and component number of the source component, the company code, contract number, and component number of the target, and the cost center, profit center, and accounting area to be applied to the target component.

Upload the completed file in the Change of lessee workspace using drag and drop, or click browse and select the file. Only the XLSX format is supported.

Lucanet Lease Accounting processes the file in the background. Each valid row is transferred; each invalid row is reported with the reason, and the remaining rows are still processed.