i want you to read and understand below procedure carefully and prepare one single procedure for each activity shown in the system.

	
	
	
 

      

	
		

FA		

Desktop Procedure 

for
GA.4.2.11 IFRS 16
Common (CTA-Local)
                          
	






2023-09-29	

Table of Contents
1.	GENERAL DOCUMENT DESCRIPTION	6
2.	GENERAL PROCESS DESCRIPTION (SIPOC TABLE)	7
3.	PROCESS PRESENTATION ON T-ACCOUNTS	9
3.1.	Right of use – METRO as lessee (Lease-in)	9
3.2.	Right of use – METRO as lessor (Lease-out)	10
3.3.	Right of use – Buy out (METRO from lessee to owner of underlying assets)	11
4.	GENERAL PROCESS DESCRIPTION	12
5.	DETAILED STANDARD PROCESS DESCRIPTION (CASE STUDY)	12
5.1.	 Contract analysis in GSC PL	14
5.2.	 Check request for completeness and accuracy	17
5.2.1.	 Check template for creation of contracts	19
5.2.2.	 Check template for change of the contracts	24
5.2.3.	 ID Location check for new RE contracts	27
5.3.	Prepare data and send request back for additional information	32
5.4.	Check if  new contract has to be created	32
5.5.	Change contract in SAP RE-FX	34
5.5.1.	Time slice creation for manual changes	34
5.5.2.	Elongation of the contract	37
5.5.2.1.	Manual elongation	37
5.5.2.2.	Automatic elongation	40
5.5.3.	Earlier Termination	44
5.5.3.1.	Manual earlier termination	44
5.5.3.2.	Automatic earlier termination	44
5.5.4.	Indexation	44
5.5.4.1.	Manual indexation	44
5.5.4.2.	Automatic indexation	47
5.5.5.	Change of cost center	47
5.5.5.1.	Manual change of cost center	47
5.5.5.2.	Automatic change of cost center	50
5.5.6.	Incentive - reimbursement by the lessor	50
5.5.6.1.	Manual incentive – reimbursement by the lessor	50
5.5.6.2.	Automatic incentive – reimbursement by the lessor	52
5.5.7.	Impairment	53
5.5.7.1.	Manual impairment	53
5.5.7.2.	Automatic impairment	54
5.5.8.	Change of payment frequency	55
5.5.8.1.	Manual change of payment frequency	55
5.5.9.	Buy-out (from Right-of-Use to Owned Asset)	58
5.5.10.	Partner Change	64
5.5.10.1.	Manual partner change	64
5.5.10.2.	Automatic partner change	66
5.5.11.	Renewal	69
5.5.11.1.	Add renewal to contract	69
5.5.11.2.	Remove Renewal from contract	73
5.5.12.	Change of Company Code	74
5.5.13.	Location ID change	88
5.5.13.1.	Manual Location ID change	88
5.5.13.2.	Automatic Location ID change	89
5.5.14.	Purchase option	92
5.5.14.1.	Manual purchase option	92
5.5.14.2.	Automatic purchase option	95
5.5.15.	Delete last valuation	96
5.5.15.1.	Reverse last valuation	96
5.5.15.2.	Remove last valuation step	99
5.5.15.3.	Set deletion flag on contract	101
5.5.16.	Error handling	104
5.6.	Create new contract in SAP RE-FX	112
5.6.1.	Manually created	112
5.6.2.	Automatically created via macro	127
5.7.	 Perform simulation of valuation in SAP RE-FX	130
5.7.1.	 Check maintained contracts	131
5.7.2.	 Check status of valuation rule and valuation process	133
5.7.3.	Perform simulation of valuation in SAP RE-FX	137
5.8.	Investigate errors	138
5.9.	Resolve errors	140
5.10.	Create the ticket for technical support	145
5.11.	Perform valuation in SAP RE-FX	146
5.12.	Perform posting in SAP RE-FX	149
5.13.	Perform and post FX valuation in SAP RE-FX	156
5.14.	Perform and post liabilities/receivables maturity split in SAP RE-FX	162
5.15.	Perform posting in SAP FI-CO	168
5.15.1.	Posting via. csv upload	169
5.15.2.	Posting via interface	184
5.16.	Investigate errors	190
5.17.	Resolve errors	192
5.18.	Create the ticket for technical support	193
5.19.	 Perform reconciliation of SAP RE-FX with SAP FI-CO	193
5.20.	Investigate differences and perform corrections	204
5.21.	 Perform reconciliation in SAP FICO for all P&L accounts reported under specified Tagetik item(s)	206
5.22.	Investigate differences on P&L accounts	212
5.23.	Send result of initial reconciliation to LFI and ask for additional information	215
5.24.	 Post accrual for lease expenses	218
5.25.	Inform LFI about accrual posting	223
5.26.	Perform disposal check and posting	224
4.20.2.	MGFS (SAP S/4 HANA) approach	233
4.20.2.	Common (CTA) approach	237
5.27.	Group Reporting	241
5.28.	Archive documents and close the request	241
6.	APPENDIX	243
6.1.	Glossary (Including abbreviations)	243
6.2.	  Controls	244
6.2.1.	On-going controls	244
6.2.2.	Detective controls (sample checks)	245
6.3.	Attachments & Paths	246
6.4.	Document approval	252

 
1.	General Document Description
This document defines the flow of a business process by describing all activities that have to be executed in order to reach the aim of the process.
In order to have a clear definition of responsibilities and the resources necessary to execute the business process reliably, the activity descriptions are detailed by:
	Examples
	Responsible roles
	Resources (Input and output objects, documented knowledge, application systems)
Symbols that are used in this document are described in detail in document Desktop Procedure Creation & Management System.

 
2.	General Process Description (SIPOC table)

Supplier
(Requesting department)	
LFI Accounting Department
Inputs	SAP
Transactions	SAP RE-FX HS1: RECN, RECEISRULECN, RECEPR, RECEEP, OBJVAL, OBJREG, RECEISRECLASSIFY, YRE00FIEXPORT, YSDI, YRE00GLCNCCSUM, REISCNOA, 
SAP FI-CO: FB03, FAGLL03, FAGLB03, FBL3N  S_ALR_87012284, F-02, SM35, WE02, YCA00_IDOCLINK, S_ALR_87012284; F08
OneBW BT1: RAAOE
	Other Inputs	Excel templates
Process	Who?	GSC FA Clerk
	How?	In special SAP module (used among others for maintenance of leasing contracts) called RE-FX on dedicated HS1 line, postings of contracts valuation are performed. Those postings are monthly posting of contracts as well as termination and new contract addition and maturity split of liabilities and receivables.
Data from HS1 is posted in SAP module FICO LUCA line L01.
After both postings data is reconciled between both systems RE-FX and SAP to assure compliance of data.
When above activities are finished, notes for reporting purpose can be calculated and sent to LFI/responsible JEMEC team or posted.
	Why?	To post IFRS 16 related transactions in both in SAP RE-FX and Local SAP FICO and calculate notes for Group Reporting.
	When?	All postings must be done in agreed with LFI Accounting Department schedule

Outputs	Documents	Reconciliation file
P&L Reconciliation file
Disposal check file
Maturity split file
	Results of action	Posting related to IFRS 16 process are done in SAP RE-FX and SAP FICO
Customer	LFI Accounting Department


 
3.	Process presentation on T-accounts 
3.1.	Right of use – METRO as lessee (Lease-in)
 
3.2.	Right of use – METRO as lessor (Lease-out)
 
3.3.	Right of use – Buy out (METRO from lessee to owner of underlying assets)
 
4.	General Process Description
Goal of the Process: The goal of the IFRS 16 process is to ensure proper accounting and reporting of leases in line with the IFRS 16. It aims to provide a transparent view of a company's leasing activities, recognizing assets and liabilities on the balance sheet and ensuring accurate financial reporting.
Lessee Accounting: Lessees must recognize lease liabilities for most leases, with corresponding right-of-use (ROU) assets on the balance sheet.
Lease Liabilities: Calculated based on the present value of future lease payments, including options to extend or terminate the lease if these are deemed likely.
Right-of-Use Asset: Initially measured at the amount of lease liability plus initial direct costs, adjusted for any prepaid or accrued lease payments.
Tools: SAP Lease Management (SAP RE-FX) and SAP FICO, pre-built templates to facilitate compliance and reporting in line with the standard.
5.	Detailed Standard Process Description (Case Study)
The aim of this procedure is to describe the process of lease contract maintenance, postings related to leasing and calculation of notes related to IFRS 16. Contracts are maintained in special module – SAP RE-FX. Postings are performed also on SAP RE-FX and then transferred to SAP FICO. Process of transfer need to be checked because both systems should reflect each other. Calculation of notes is based on data from SAP RE-FX. All information related to IFRS 16 can be found on United under path below: https://metro-united.com/workspaces/lease-engine-ifrs-16/apps/content/welcome
 

 
5.1.	 Contract analysis in GSC PL
METRO BG	Request
METRO FR	Request

MAKRO CZ	Rulebook
METRO HR	Request

METRO DE	Request
METRO HU	Request

MAKRO ES	Rulebook
METRO IT	Request

METRO KZ	Request
METRO TR	Rulebook

MAKRO NL	Rulebook
METRO UA	Request

MAKRO PT	Contract
ES VTO	Rulebook

METRO SK	Rulebook
MAG	Rulebook

MIB	Rulebook
Eijsink	Request

Dish Digital	Rulebook
PL PropCO	Contract

Metro Digital	Rulebook
BE PropCO	Request

Aviludo	Request
SE JOHBECO	Request

METRO MARKETS DE	Request
Metro Logistics	Request

Pro á Pro ES	Request
METRO RS	N/A
If contract analysis centralized in GSC PL, documentation for new contract is delivered by LFI. If contract analysis is not centralized in GSC PL, inference of contract maintenance needs to be requested by sending data in standard template. How to read standard template is described in 4.2. Check request for completeness and accuracy of this procedure. Leasing contracts maintenance is performed on request from LFI sent via MSIT accordingly to Communication Rulebook for specific client. 
Data of all contact persons can be found in Communication Rulebook. Information about changes is not send in regular frequency. In case of emergency or MSIT is not working, e-mail received on common e-mail box is considered.  Each time request is received via e-mail GSC Fixed Assets Clerk needs to check in Communication Rulebook if requestor is authorized to send it. All required information about contracts MUST be provided by LFI in contract documentation attached in MSIT. After receiving the MSIT with request for creation of new contract, GSC Clerk perform documentation analysis.
In order to do that follow steps below.
1.	Go to MSIT and open received message. How to manage MSIT application can be found under path https://metro.sharepoint.com/sites/MSIT2
2.	Open file attached in message form LFI
3.	File will open- check if file contain all necessary data (below there is the example for contract document)
 
4.	Information what data MUST be reviewed can be found in Rulebook file for processed country. How to analyze contract can be found in mentioned rulebook. Path to rulebook can be found in chapter 5.3. Attachments & Paths.
5.	If all required data can be found in documentation, follow steps described in chapter 4.6. Create new contract in SAP RE-FX. In case of missing data follow steps described in chapter 4.3. Prepare the request and send for processing.
6.	After analyzing documentation, contract can be created. For creation of new contract follow chapter 4.6. Create new contract in SAP RE-FX of this procedure.
5.2.	 Check request for completeness and accuracy
METRO BG	Request
METRO FR	Request

MAKRO CZ	Rulebook	METRO HR	Request

METRO DE	Request
METRO HU	Request

MAKRO ES	Rulebook	METRO IT	Request

METRO KZ	Request
METRO TR	Rulebook
MAKRO NL	Rulebook	METRO UA	Request

MAKRO PT	Contract
ES VTO	Rulebook
METRO SK	Rulebook	MAG	Rulebook
MIB	Rulebook	Eijsink	Request

Dish Digital	Rulebook	PL PropCO	Contract

Metro Digital	Rulebook	BE PropCO	Request

Aviludo	Request
SE JOHBECO	Request

METRO MARKETS DE	Request
Metro Logistics	Request

Pro á Pro ES	Request
METRO RS	N/A Rulebook

If contract analysis is not centralized in GSC PL, inference of contract maintenance needs to be requested by sending data in standard template. Leasing contracts maintenance is performed on request from LFI sent via MSIT accordingly to Communication Rulebook for specific country. Information about changes is not send in regular frequency. In case of emergency or MSIT is not working, e-mail received on common e-mail box is considered.  Each time request is received via e-mail GSC Fixed Assets Clerk needs to check in Communication Rulebook if requestor is authorized to send it.  All required information about contracts MUST be provided by LFI in request standard template attached in MSIT. 
In order to check if request is received follow steps below.
1.	Go to MSIT and open received message. 
2.	Open file attached in message form LFI.
3.	File will open- check if file contain all necessary data. In order to do that follow steps described in chapter 4.2. Check request for completeness and accuracy.
In case of other form of request, follow country specific rulebook. Path to rulebook can be found in chapter 5.3. Attachments & Paths.
After receiving MSIT with request form LFI, GSC Clerk MUST check if all necessary data in template are filled in. In order to do that follow steps below.
Current template for requests can be found under path below https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/ProceduresNew/GA.4.2.11_IFRS16_Contracts%20Maintenance%20Template.xlsx?d=w19e36e68c60d40009cc233ff3731b944&csf=1&web=1&e=Yaaws4
1.	When file fill be open
 
1)	TEMPLATE CREATE- if template contain data on this tab, new contracts need to be created in SAP RE-FX. To create new contracts, follow chapter 4.6. Create new contract in SAP RE-FX.
2)	TEMPLATE CHANGE- if template contain data on this tab, contracts need to be changed in SAP RE-FX. To change existing contracts, follow chapter 4.5. Change contracts in SAP RE-FX.
5.2.1.	 Check template for creation of contracts 
Request for creating the contract will be provided in standard template in tab TEMPLATE CREATE. Follow below steps to verify the request.
1.	Open the file and check if below mandatory fields are updated:
 
1)	COMPANY CODE – MUST be filled in,
CONTRACT VS OBJECTS – MUST be filled in, points if contract has one or more than one objects:
	CONTRACT WITH SINGLE OBJECT – contract with one object,
	CONTRACT WITH MULTIPLE OBJECTS – contract with more than one object, MUST be chosen from drop down list
CONTRACT TYPE – type of contract, MUST be chosen from drop down list
CONTRACT START DATE – MUST be filled in, first day of the contract
CONTRACT END DATE - MUST be filled in, last day of the contract
CONTRACT NAME – name of the contract, max length: 66 characters. If same name will appear in more than one line, one contract with multiple objects will be created
OLD CONTRACT- Text field which allows to indicated connection to other contract in case new one is continuation of lease for the object which was also previously leased under different contract.
CONTRACT CURRENCY – currency of contract MUST be filled in in case of currency different than EUR
2.	Next check
 
1)	Check if for properties contracts LOCATION ID is filled in
 	NOTE: For reporting purposes ID Location is required for all real estate contracts. 

3.	Next, check
 
1)	Check if for contract types ME07- ME09 LESSOR NAME is filled in
 	NOTE: From 01.12.2023 for contract types ME07- Cars, ME08- Trucks and ME09- Other vehicle Business Partner field is required. Change of lessor doesn’t  require new time slice. 

4.	Check next part of the request:
 
1)	OBJECT NAME- name of object
COST CENTER – MUST be filled in
5.	Check next part of template
 
1)	FREQUENCY OF PAYMENT - fill in if it different than 1 in MONTHS 
PAYMENT FORM – fill in if is different than IN ADVANCE
CORRECTION OF DUE DATE AT START OR END- MUST be filled in if different than CORRECTION OF DUE DATE AT START AND END
6.	Check CONDITION DATA part
 
1)	CONDITION TYPE – MUST be chosen form drop down list
CONDITION VALID FROM- to be filled in if different than CONTRACT START DATE
CONDITION VALID TO- to be filled in if more than one condition should be created for contract
UNIT PRICE – MUST be filled in
7.	Check next part of the template:
 
1)	PROBABLE END- if different end date is expected than CONTRACT END DATE
MEMO - in case some description should be included in Valuation parameters, max length: 100 characters
VALUATION TITLE- in case of Valuation title should be changed from default one
2)	CASH FLOW FROM- in case of different than CONTRACT START DATE
 	NOTE: If the information given in the file is not consistent with SAP RE-FX data, LFI needs to be informed and asked for the confirmation of correctness of data in the file.

5.2.2.	 Check template for change of the contracts
Request for changing existing contract will be provided in standard template in tab TEMPLATE CHANGE. Follow below steps to verify the request.
1.	Open the file and check if below mandatory fields are updated:
 
1)	COMPANY CODE – MUST be filled in, 
CONTRACT NUMBER – MUST be filled in,
CONTRACT NAME – in case of change of contract name
Check if for properties contracts LOCATION ID is filled in case of change
 	NOTE: For reporting purposes ID Location is required for all real estate contracts. 

2.	Next, check
 
1)	Check if for contract types ME07- ME09 LESSOR NAME is filled in
 	NOTE: From 01.12.2023 for contract types ME07- Cars, ME08- Trucks and ME09- Other vehicle Business Partner field is required. Change of lessor doesn’t  require new time slice. 

3.	Next, 
 
1)	OBJECT NAME- to be filled in in case of change of cost center
COST CENTER- - to be filled in in case of change of cost center
4.	Check next part of the request:
 
1)	FREQUENCY OF PAYMENT- filled in in case of change of frequency
PAYMENT FORM- chosen from drop down list if different than existing one
CONDITION TYPE- in case of change of unit price MUST be chosen form drop down list
CONDITION VALID FROM- to be filled in case of new condition
CONDITION VALID TO- to be filled in case of more than one new condition 
UNIT PRICE- to be filled in in case of new condition 
PROBABLE END DATE CHANGE- to be filled in in case of early termination of contract
CHANGE VALID FROM- MUST be filled in as a date from which change takes place
INTEREST CHANGE (YES/NO)-  MUST be chosen form drop down list YES if change require change of interest rate, NO in change do not require change if interest rate

 	NOTE: According to Group Policy interest Rate MUST be changed each time when end date is changed.
More details can be found in IFRS Accounting Guideline LEASES document on  https://metro.sharepoint.com/sites/intranet-mag-Lease-Engine-IFRS-16/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2Fintranet%2Dmag%2DLease%2DEngine%2DIFRS%2D16%2FShared%20Documents%2F03%5FFiles%2F11%5FAccounting%20Guideline%20IFRS%2016%2FMETRO%5FAccounting%5FGuideline%5FIFRS%2016%5F20200330%5Ffinal%20%281%29%2Epdf&parent=%2Fsites%2Fintranet%2Dmag%2DLease%2DEngine%2DIFRS%2D16%2FShared%20Documents%2F03%5FFiles%2F11%5FAccounting%20Guideline%20IFRS%2016 (page 22-23)

MEMO- text field to appear in time slice, field is empty by default
VALUATION TITLE- fill in if should be changed from default
END DATE- fill in only in case of change in end date, bot extension and elongation of contract
5.	If the information given in the file is not consistent with SAP RE-FX data, LFI needs to be informed and asked for the confirmation of correctness of data in the file. How to contact LFI is described in chapter 4.3.Prepare data and send request back for additional information 
5.2.3.	 ID Location check for new RE contracts
For reporting reasons all Real Estates contracts need additional information as ID Location. To prevent double usage of same ID for multiple contracts, check before creation of new  ME01-ME04 and ME11 contracts if requested ID Location isn’t already in use.
1.	Open file 4.2.11_ID Location check.xlsx
 
1)	Got to RESULT tab
2)	In column COMPANY CODE paste number from requested client
3)	In column ID LOCATION paste ID LOCATION from request
4)	In column COMMENT information if given ID require additional attention- come back to this column after all next steps related to this check are filled in 
2.	Go to SAP RE-FX and open YRE00_LOC_DISPLAY - Location Id details 
 
1)	Click on EXECUTE
 	NOTE: This table shows all ID Locations created in SAP RE-FX and needs to be performed for all Company Codes and possibles data. DO NOT limit data to only performed Company Code or requested ID Location.
3.	When report will generate, click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
4.	Go to YRE00GLCNCCSUM - Display of Cumulative GL as per Cont in SAP RE-FX
 
1)	COMPANY CODE- fill in processed client
2)	LAYOUT VARIANT- put /ID_CHECK
3)	Click on EXECUTE
5.	When report will generate, click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
6.	Go back to check excel file and RE-FX ID Location Table tab
 
1)	TECHNICAL- do not overwrite data in this column and make sure formulas are covering all data which will be pasted in columns B-D
2)	COMPANY CODE- paste data form first exported file
3)	LOCATION ID- paste data form first exported file
4)	LOCATION ID DESCRIPTION- paste data form first exported file
7.	Go to RE-FX Data tab
 
1)	TECHNICAL- do not overwrite data in this column and make sure formulas are covering all data which will be pasted in columns B-D
2)	COMPANY CODE, G/L ACCOUNT, CONTRACT NUMBER, COST CENTER, CONT. TYPE, LOCATION ID- paste data form first exported file
8.	Go back to first tab
 
1)	Check comments
WRONG COMPANY CODE- if comment occurred verify if data in column A is consistent with data RE-FX Data tab, if no check uploaded data and data form request.
Reusage of ID Location- Clarify with LFI - Contract Number: XXX- it means ID Location is already in use in SAP RE-FX. Generally, ID should not be doubled apart from a few cases like franchise companies. Each situation like this MUST be verified with LFI
Request creation of new Location ID- comment means given ID is not existing in SAP RE-FX and never been used. Request for creation of new ID should be done via e-mail to responsible departments because it also require Metro Properties DE involvement. More information can be found on UNITED.
Wrong Location ID- check length- ID Location MUST be 6 digits, template verifies if typo occurred
5.3.	Prepare data and send request back for additional information
In case of any questions/inaccuracies, local organization should be contacted via MSIT using option REWORK.
In case of technical problems contact Service Desk:
	Via MSIT (For more details regarding interaction tool see procedures under the following path: https://metro.sharepoint.com/sites/MSIT2 
	Via JIRA (using common mailbox: <PRESIDIO_ANONYMIZED_EMAIL_ADDRESS>)
In case of problems related to lack of accesses or missing cost centers in SAP RE-FX contact GSC support lease engine:
	<PRESIDIO_ANONYMIZED_EMAIL_ADDRESS> via JIRA ticket from path https://jira.metro.digital/servicedesk/customer/portal/251/create/310
5.4.	Check if  new contract has to be created
Based on tab filled in request template shared by LFI, decide if new contract needs to be created or existing one needs to be adjusted.
1.	Open file shared by LFI
 
5)	Open tab TEMPLATE CREATE
6)	Check if data related to creation is filled in, if it’s new contract needs to be created, if not, check another tab
2.	Open TEMPLATE CHANGE tab
 
1)	Check if data related to change is filled in, if it’s changes on contract needs to be done.
5.5.	Change contract in SAP RE-FX
5.5.1.	Time slice creation for manual changes
 	NOTE: From 01.12.2023 for contract types ME07- Cars, ME08- Trucks and ME09- Other vehicle Business Partner field is required. Change of lessor doesn’t require new time slice. 
 	NOTE: From 28.05.2024 for contract types ME01- Land with com. and build., ME02- Land without buildings, ME03- Buildings and ME11- Inter Company Location ID field is required. Change of Location ID doesn’t require new time slice. 

Before inserting changes on contract, new TIME SLICE MUST be created, to emphasize on system since when change occur. In order to do that follow steps below
1.	Go to transaction RECN - PROCESS CONTRACT.
 
2)	Double click on RECN - PROCESS CONTRACT.
2.	CONTRACT screen is visible.
 
1)	Fill in the COMPANY CODE and the CONTRACT number according to the request. How to find this data is explained in countries rulebooks, path to mentioned document can be found in chapter 5.3. Attachments & Paths.
Then press ENTER to display the lease contract subject to this change request.
3.	Contract is displayed, and next steps should be followed.
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab VALUATION PARAMETERS.
3)	Click on CUT TIME SLICE. New window is open.
4.	Complete next steps
 
1)	Fill in the VALID FROM date according to request from LFI
 	NOTE: Before inserting date given by LFI, check if proceeded data is correct. Date CHANGED VALID FROM other day than first of month can cause errors, that’s why recommended is to use first day of closing month as a date for creation of new time slice.
2)	Click on CONTINUE.
5.	Now other changes can be introduced.
5.5.2.	Elongation of the contract
5.5.2.1.	Manual elongation
To extend a lease contract manually follow steps below
1.	Follow 1-4 od chapter 4.5.1. Time slice creation for manual changes
2.	Stay on VALUATION PARAMETERS tab
 
1)	Switch to new created TIME SLICE
2)	PROBABLE END- insert new end date form LFI request
3)	New INTEREST RATE MUST be calculated in case of any date change on contract. Delete value form filed and press ENTER. New value will pop in automatically.
4)	Go to tab GENERAL DATA WITH FAST ENTRY
3.	Follow next steps
 
1)	CONTRACT TO- fill in new date, same as PROBABLE END on new TIME SLICE
2)	Go back to VALUATION PARAMETERS tab and follow steps
4.	Continue data changes as presented below
 
1)	Click on RULE COMPLETE
2)	Click on SAVE
3)	Go to VALUATION tab
5.	Go to VALUATION tab to set VALUATION RULE
 
1)	Click on PERFORM VALUATION.
2)	Enter VALUATION TITLE provided by LFI or leave untouched if change not required.
3)	Click on CONTINUE
6.	System will display window with VALUATION RESULT
 
1)	Go to tab CLEARING
2)	Check if contract ends with the date given in the excel file. If not, repeat the steps to find the issue and correct the contract. 
3)	Click on SAVE.
5.5.2.2.	Automatic elongation
To extend a lease contract automatically follow steps below
1.	Open the file macro file. The newest version of macro can be found under path: https://metro.sharepoint.com/sites/ContinuousImprovementGSC/MSERV%20PL%20Macro%20Repository/SAP%20RE-FX%20makro%20for%20contract%20creation%20and%20change_v2.0.xlsm
and go to sheet MAKRO_CHANGE
2.	Click on ENABLE CONTENT
 
3.	Open the source document basis of contracts change request. In case source data different than standard template, follow steps described in Rulebook. How to find this data is explained in countries rulebooks, path to mentioned document can be found in chapter 5.3. Attachments & Paths.
4.	Select all data for contracts extension.
5.	Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, PROBABLE END, TIME SLICE and INTEREST RATE CHANGE must be filled in.
6.	Log in to RE-FX system (HS1), then press button CHANGE CONTRACTS in the macro file
 
7.	SAP will inform twice about that macro want to connect with SAP. Click OK
 
8.	Makro will inform on which line contracts will be changed. Click on OK and macro will proceed.
 
9.	After macro entered changes into SAP window below will pop-up. Click OK.
 
10.	Makro will enter comments about changes.
 
1)	Columns A-B will be updated with SAP messages. In column A message will be Contract company code/contract number was changed. In column B message will be The valuation was run with identification…. If some other message will appear – read a message and analyze why contract cannot be changed. For example – cost center does not exist, in that case message in column A will be Cost center does not exist, contract not changed and in column B – Valuation not performed due to errors. In case cost center does not exist, create JIRA ticket under path https://jira.metrosystems.net/servicedesk/customer/portal/251/create/310 or if it is blocked – inform LFI.
5.5.3.	Earlier Termination
5.5.3.1.	Manual earlier termination
To earlier terminate a lease contract manually follow steps described in chapter 4.5.3.1. Manual elongation
 	NOTE: Before change of End Date, check if on Term tab Renewal exist. If yes, remove renewal. How to remove renewal is described in chapter 4.5.11.2. Remove Renewal from contract.


5.5.3.2.	Automatic earlier termination
To earlier terminate a lease contract automatically repeat all steps of chapter 4.5.3.2. Automatic elongation
5.5.4.	Indexation
5.5.4.1.	Manual indexation
Under path below Example of increase of rents introduced by Group can be found
https://metro.sharepoint.com/:x:/r/sites/intranet-mag-Group-Consolidation/_layouts/15/Doc.aspx?sourcedoc=%7B5380AA65-28C5-47AF-B035-653DA2CFE112%7D&file=Example%20of%20increase%20of%20rents.xlsx&action=default&mobileredirect=true
To perform an indexation for a lease contract manually follow next steps
First, follow steps form chapter 4.5.1. Time slice creation for manual changes, then follow steps below
1.	Contract is displayed, and next steps should be completed
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab CONDITIONS.
3)	Click on INSERT CONDITION(S).
4)	select CONDITION TYPE NAME according to the document source of this information provided in request from LFI. 
5)	Click on APPLY.
New field opens and data input is needed in the same tab for VALID FROM date and UNIT PRICE.
2.	Continue the filling of data in the same tab
 
1)	VALID FROM- according to request
2)	UNIT PRICE- according to request
3)	Go to the tab VALUATION PARAMETERS.
3.	Follow next steps in the same tab
1)	Click on SAVE.
4.	Repeat steps 2-3 from chapter 4.5.3.1. Manual elongation.
 	NOTE: To remove wrongly created condition, firstly reverse postings. How to reverse postings is described in chapter 4.5.14.1. Reverse last valuation and then remove chosen condition 
 
1)	Click on CHANGES BETWEEN DISPLAY <->CHANGE 
2)	Go to CONDITIONS tab
3)	Choose condition which should be deleted
4)	Click on DELETE CONDITION(S)

5.5.4.2.	Automatic indexation
To perform an indexation for a lease contract automatically follow next steps
1.	Repeat steps 1 to 3 from chapter 4.5.3.2. Automatic elongation.
2.	Select all data for contracts indexation.
3.	Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, CONDITION TYPE, CONDITION VALID FROM, UNIT PRICE, TIME SLICE and INTEREST RATE CHANGE must be filled in.
4.	Repeat steps 6 to 10 from 4.5.3.2. Automatic elongation.
5.5.5.	Change of cost center
5.5.5.1.	Manual change of cost center
To change a cost center of a lease contract manually follow steps below
1.	Follow steps form chapter 4.5.1. Time slice creation for manual changes
2.	Contract is displayed, and next steps should be completed
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab OBJECTS.
3)	Fill in the new COST CENTER in the ACCOUNT ASSIGNMENT field according to the request from LFI
4)	Go to tab VALUATION PARAMETERS.
 	NOTE: Additional steps on how to add the ACCOUNT ASSIGNMENT are described hereafter
 
5)	Click on the square to open the next window RESTRICT VALUE RANGE (1).
6)	Copy data according to request from LFI
7)	Click on START SEARCH, the following window will pop-up.
 
1)	Double click on the found COST CENTER.

3.	Repeat steps 2-3 from chapter 4.5.3.1. Manual elongation
5.5.5.2.	Automatic change of cost center
To change the cost center of a lease contract automatically follow steps below
1.	Repeat steps 1 to 3 from chapter 4.5.3.2. Automatic elongation
2.	Select all data for the change of cost center.
3.	Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, OBJECT NAME, COST CENTER, TIME SLICE and INTEREST RATE CHANGE must be filled in.
4.	Repeat steps 6 to 10 from chapter 4.5.3.2. Automatic elongation.
5.5.6.	Incentive - reimbursement by the lessor
5.5.6.1.	Manual incentive – reimbursement by the lessor
To perform the incentive transaction for a lease contract manually, follow steps below
1.	Follow steps form chapter 4.5.1. Time slice creation for manual changes
2.	Contract is displayed, and next steps should be followed
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab CONDITIONS.
3)	Click on INSERT CONDITION(S).
4)	select CONDITION TYPE NAME- in case of incentive transaction, V910 – CREDIT. INCENTIVES is the condition type to be selected.
5)	Click on APPLY.
New field opens and data input is needed in the same tab for VALID FROM date and UNIT PRICE.
1.	Continue the filling of data in the same tab
 
1)	VALID FROM- according to request
2)	UNIT PRICE- according to request
3)	Go to the tab VALUATION PARAMETERS.
2.	Repeat steps 2-3 from chapter 4.5.3.1. Manual elongation
5.5.6.2.	Automatic incentive – reimbursement by the lessor
To perform the incentive transaction for a lease contract manually, follow steps below
1.	Repeat steps 1 to 3 from chapter 4.5.3.2. Automatic elongation
2.	Select all data necessary to perform the incentive transaction.
3. Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, CONDITION TYPE, CONDITION VALID FROM, UNIT PRICE, TIME SLICE and INTEREST RATE CHANGE must be filled in.
4. Repeat steps 6 to 10 from 4.5.3.2. Automatic elongation.
5.5.7.	Impairment
5.5.7.1.	Manual impairment
To perform the incentive transaction for a lease contract, follow steps below
1.	Follow steps form chapter 4.5.1. Time slice creation for manual changes
2.	Contract is displayed, and next steps should be followed
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab CONDITIONS
3)	Click on INSERT CONDITION(S)
4)	select CONDITION TYPE NAME- incase of impairment transaction, V800 – UNPLANNED DEPRECIATION is the condition type to be selected.
5)	Click on APPLY
New field opens and data input is needed in the same tab for VALID FROM date and UNIT PRICE.
1.	Continue the filling of data in the same tab
 
1)	VALID FROM- fill in according to request form LFI
2)	UNIT PRICE fill in according to request form LFI
3)	Go to the tab VALUATION PARAMETERS.
2.	Repeat steps 2-3 from chapter 4.5.3.1. Manual elongation
5.5.7.2.	Automatic impairment
To perform the incentive transaction for a lease contract manually, follow steps below
1.	Repeat steps 1 to 3 from chapter 4.5.3.2. Automatic elongation
2.	Select all data necessary to perform the impairment transaction.
3. Repeat steps 3 and 4 from chapter 4.5.6.2. Automatic incentive – reimbursement by the lessor
5.5.8.	Change of payment frequency
5.5.8.1.	Manual change of payment frequency
1.	Follow steps form chapter 4.5.1. Time slice creation for manual changes
2.	Go to CONDITION tab
 
1)	Click on INSERT CONDITIONS,
2)	Choose CONDITION TYPE according to the request,
3)	Click on APPLY
3.	Update data for new conditions:
 
1)	VALID FROM – fill in date according to the request
UNIT PRICE – fill in unit price according to the request
2)	Go to tab TERMS
4.	Follow next steps:
 
1)	FREQUENCY – Click on CREATE TERM button
2)	FREQUENCY – fill in according to the request
3)	Click on CONTINUE
5.	Repeat steps 2-3 from chapter 4.5.3.1. Manual elongation
5.5.9.	Buy-out (from Right-of-Use to Owned Asset)
Example of change right of use assets to owned assets introduced by Group can be found under path below.
https://metro.sharepoint.com/:x:/r/sites/intranet-mag-Group-Consolidation/_layouts/15/Doc.aspx?sourcedoc=%7B7542D2A9-AF78-43A1-8B4B-AFD0336CCF3B%7D&file=Examples%20of%20change%20right%20of%20use%20assets%20to%20owned%20assets.xlsx&action=default&mobileredirect=true
1.	Follow steps form chapter 4.5.1. Time slice creation for manual changes
2.	Contract is displayed, and next steps should be followed
 
1)	Open tab CONDITIONS
2)	Click on INSERT CONDITION(S)
3)	Select CONDITION TYPE NAME- in case of Buy-out transaction, V104– CREDIT- SIDE SURRENDER VALUE is the condition type to be selected and doble click on it.
3.	Follow steps 3-4 of chapter 4.5.6.1. Manual incentive – reimbursement by the lessor.
4.	Perform valuation posting on contract
 
1)	Go to VALUATION tab
2)	Click on POST VALUATION (IFRS 16_M)
5.	New window will appear- post valuation according to chapter 4.12. Perform posting in SAP RE-FX and 4.15. Perform posting in SAP FI-CO.
6.	In SAP FI-CO create new asset, according to request form LFI. How to create new Asset is described in procedure FA.1._Create_change asset master data  for processed client which can be found under path https://metro.sharepoint.com/sites/ProcedureManagementPortal/ProceduresNew/Forms/AllItems.aspx
7.	After creating new asset in SAP FI-CO, reposting from posted valuation to own asset accounts MUST be done. Go to ABSO - Miscellaneous Transactions
 
8.	Fill in data 
 
1)	COMPANY CODE- according to processed client
ASSET- number of created asset in step 6 of this chapter
2)	DOCUMENT DATE- according to request (day of buy-out)
POSTING DATE- according to request (day of buy-out)
POSTING PERIOD- in correspondence with POSTING DATE 
3)	TRANSACTION TYPE- according to rulebook, path to mentioned document can be found in chapter 5.3. Attachments & Paths and press ENTER
9.	New window will appear, fill in data
 
1)	AMOUNT POSTED- value from LFI request (acquisition value)
2)	OFFSETTING ACCOUNT- according to rulebook (check chapter 5.3. Attachments & Paths)
3)	TEXT- provided by LFI in request
4)	DOCUMENT TYPE- according to rulebook (5.3. Attachments & Paths)
5)	Click on LINE ITEMS
10.	New window will appear
 
1)	ORD. DEP.- value of cumulated depreciation based on data from request
2)	Click on NEXT to repeat steps for all areas
3)	After last area click on CONTINUE
11.	 New window will appear
 
1)	Verify correctness of data
2)	Click on CONTINUE
3)	Click on SIMULATE
12.	Review simulation and press CTRL+S to save posting.
 
 	NOTE: As values MUST be reported as historical values additional rebooking might be required on Balance Sheet to recognize Historical APC and DEP value.

5.5.10.	Partner Change
5.5.10.1.	Manual partner change
Partner change does not require TIME SLICE creation. In order to change lessor, follow steps below
1.	Go to 	PARTNER tab
 
1)	Click on DELETE SELECTED ASSIGNMENT
2.	New window will appear
 
1)	Click on ASSIGN NEW PARTNER and then LEASE ENGINE VENDORS
3.	New window will appear
 
1)	Click on CONTINUE
4.	New window will pop up
 
1)	Double click on PARTNER, according to request/contract documentation
5.5.10.2.	Automatic partner change
To change business partner with macro, follow steps below. 
1.	Open the file macro file. The newest version of macro can be found under path: https://metro.sharepoint.com/:x:/r/sites/ContinuousImprovementGSC/MSERV%20PL%20Macro%20Repository/SAP%20RE-FX%20makro%20for%20contract%20creation%20and%20change_v2.0.xlsm?d=w2bebaaafb0f446bcb6010997706a53e7&csf=1&web=1&e=z17npc and go to sheet MAKRO_CHANGE
1.	Click on ENABLE CONTENT
 
2.	Open the source document basis of contracts change request. This file could be standard template, country template, German template and other. How to find this data is explained in countries rulebooks, path to mentioned document can be found in chapter 5.3. Attachments & Paths
3.	Select all data for contracts extension.
4.	Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, LESSOR NAME must be filled in.
5.	Log in to RE-FX system (HS1), then press button CHANGE CONTRACTS in the macro file
 
6.	SAP will inform twice about that macro want to connect with SAP. Both times click OK
 
7.	Makro will inform on which line contracts will be changed. Click on OK and macro will proceed.
 
8.	After macro entered changes into SAP window below will pop-up. Click OK.
 
9.	When macro finish with changes
 
1)	Makro will enter comments about changes.
5.5.11.	Renewal
5.5.11.1.	Add renewal to contract
To extend a lease contract manually follow steps below
1.	Follow 1-4 od chapter 4.5.1. Time slice creation for manual changes
2.	Go on TERM tab
 
1)	Click on CREATE TERM and then choose RENEWAL
3.	Follow next steps
 
1)	RENEWAL TYPE- choose from dropdown list STANDARD RENEWAL RULE or INDIVIDUAL RENEWAL RULE
	In case of  STANDARD RENEWAL RULE follow next step
	In case of  INDIVIDUAL RENEWAL RULE follow step 5.
2.	Continue data changes as presented below
 
1)	Click on RENEWAL RULE 
2)	Choose RENEWAL RULE
3.	In case INDIVIDUAL RENEWAL RULE
 
1)	Click on APPEND ROW
2)	Choose renewal option according to request
3)	Fill in according to request
4.	Now activate renewal
 
1)	Go to VALUATION PARAMETERS tab
2)	Click on SIMULATE RENEWAL
5.	New window will appear
 
1)	Choose created renewal and click PROBABLE
2)	Click CONTINUE
6.	Valuate contract according to steps 14-15 chapter 4.6.1.1. Manually created.
5.5.11.2.	Remove Renewal from contract
1.	Go on TERM tab
 
1)	Click on RENEWAL 
2)	Click DELETE SELECTED TERM
5.5.12.	Change of Company Code
In case of transfer form one Company Code to another follow steps below:
1.	Firstly, close contract on Company Code form which transfer will be done. Go to transaction RECN - PROCESS CONTRACT.
 
1)	Double click on RECN - PROCESS CONTRACT.
2.	CONTRACT screen is visible.
 
1)	Fill in the COMPANY CODE and the CONTRACT number according to the request. Then press ENTER to display the lease contract subject to this change request.
3.	Contract is displayed, and next steps should be followed
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab VALUATION PARAMETERS.
3)	Click on CUT TIME SLICE. New window is open.
4.	Complete next steps
 
1)	Fill in the VALID FROM- first day month after month of closing of contract. For example, if contract PROBABLE END is 30.09.2023, then set VALID FROM as 01.10.2023.
2)	Click on CONTINUE.
5.	Stay on VALUATION PARAMETERS tab
 
1)	Switch to new created TIME SLICE
2)	PROBABLE END- insert new end date form LFI request. Last day of closing month- day before Time Slice valid from date.
3)	New INTEREST RATE in case of Company Code change MUST stay the same 
4)	Go to tab GENERAL DATA WITH FAST ENTRY
6.	Follow next steps
 
1)	CONTRACT TO- fill in new date, same as PROBABLE END on new TIME SLICE
2)	Go back to VALUATION PARAMETERS tab and follow steps
7.	Continue data changes as presented below
 
1)	Click on RULE COMPLETE
2)	Click on SAVE
3)	Go to VALUATION tab
8.	On VALUATION tab 
 
1)	Click on PERFORM VALUATION.
2)	Enter VALUATION TITLE provided by LFI or leave untouched if change not required.
3)	Click on CONTINUE
9.	System will display window with VALUATION RESULT
 
1)	Go to tab CLEARING
2)	Check if contract ends with the date given in the excel file. If not, repeat the steps to find the issue and correct the contract. 
3)	Click on SAVE.
10.	Next, create new contract in new Company Code
11.	Go to transaction RECN - PROCESS CONTRACT
 
1)	Double click on RECN - PROCESS CONTRACT
12.	CONTRACT screen is visible.
 
1)	Click on CREATE OBJECT.
13.	Fill in the following fields:
 
1)	CONTRACT TYPE- Open the arrow and select the contract type from the list according to the request. 
2)	Fill in the COMPANY CODE as per the request. 
3)	Select CONTINUE

 	NOTE: There are different CONTRACT TYPES that could be created in RE-FX system. Refer to the following list indicated in SAP RE-FX print screen:
 


14.	 Next screen for REC XXXX <NEW> CREATE: GENERAL DATA WITH FAST ENTRY opens, where XXXX stands for Contract type. Fill in the following fields:
 
1)	COMPANY CODE- according to request
2)	CONTRACT START-according to request, day after closing contract for old Company Code.
TO- according to request, same date as for closed contract
3)	CONTRACT NAME- according to request, same as for closed contract
4)	CONTRACT CURRENCY- according to request, same as for closed contract
5)	Go to the tab PARTNERS
15.	Follow steps 5-10 of chapter 4.6.1. Manually created and continue CONDITIONS tab 
 
1)	Choose V107- NET WORTH VALUE SPEC	
16.	New window will appear
 
1)	VALID FROM- set automatically, same as start of the contract
2)	UNIT PRICE- set value according to request, same as closing balance for closed contract.
17.	Follow next steps
 
1)	Click on INSERT CONDITION(S).
2)	Select condition type for monthly payment
3)	Click on APPLY.
18.	Continue the filling of data on tab
 
1)	CONDITION PURPOSE- It is generated automatically by the system.
2)	VALID FROM- It is generated automatically by the system.
3)	UNIT PRICE- according to request, same as for closed contract
4)	CURRENCY- is generated automatically by the system.
5)	FORMULA- is generated automatically by the system.
6)	Go to the tab VALUATION PARAMETERS.
19.	Continue with creation according to steps 13-17 of chapter 4.6.1. Manually created
20.	 System will display window with VALUATION RESULT
 
1)	Go to tab CLEARING:
2)	Check if contract ends with the date given in the excel file. If not, repeat the steps to find the issue and correct the contract. 
3)	Click on SAVE.
 	NOTE: Compare values on closed and new contract
 
1) On ASSETS tab check if RoU value for end of closed contract is the same as for opening on new contract. In case of major difference investigate what causes discrepancies and correct contract.
 
2) On SPECIAL FLOW tab check if equity values are the same on closed and new contracts.  In case of major difference investigate what causes discrepancies and correct contract.

5.5.13.	Location ID change
5.5.13.1.	Manual Location ID change
Location ID change does not require TIME SLICE creation. In order to change Location ID, follow steps below
1.	Go to 	GENERAL DATA WITH FAST ENTRY tab
 
1)	Click on CHANGES BETWEEN DISPLAY<->CHANGES 
2)	Fill in new LOCATION ID
3)	SAVE contract
5.5.13.2.	Automatic Location ID change
To change business partner with macro, follow steps below. 
1.	Open the file macro file. The newest version of macro can be found under path: https://metro.sharepoint.com/:x:/r/sites/ContinuousImprovementGSC/MSERV%20PL%20Macro%20Repository/SAP%20RE-FX%20makro%20for%20contract%20creation%20and%20change_v2.0.xlsm?d=w2bebaaafb0f446bcb6010997706a53e7&csf=1&web=1&e=z17npc
and go to sheet MAKRO_CHANGE
2.	Click on ENABLE CONTENT.
 
3.	Open the source document basis of contracts change request. This file could be standard template, country template, German template and other. How to find this data is explained in countries rulebooks, path to mentioned document can be found in chapter 5.5. Attachments & Paths.
4.	Select all data for contracts extension.
5.	Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, LOCATION ID must be filled in.
6.	Log in to RE-FX system (HS1), then press button CHANGE CONTRACTS in the macro file
 
7.	SAP will inform twice about that macro want to connect with SAP. Both times click OK
 
8.	Makro will inform on which line contracts will be changed. Click on OK and macro will proceed.
 
9.	After macro entered changes into SAP window below will pop-up. Click OK.
 
10.	When macro finish with changes
 
1)	Makro will enter comments about changes.
5.5.14.	Purchase option
5.5.14.1.	Manual purchase option
To add a purchase option for a lease contract manually follow next steps
1.	Go to transaction RECN - PROCESS CONTRACT.
 
1)	Double click on RECN - PROCESS CONTRACT.
2.	CONTRACT screen is visible.
 
1)	Fill in the COMPANY CODE and the CONTRACT number according to the request. How to find this data is explained in countries rulebooks, path to mentioned document can be found in chapter 5.3. Attachments & Paths.
Then press ENTER to display the lease contract subject to this change request.
3.	Contract is displayed, and next steps should be completed
 
1)	Click on CHANGE BETWEEN DISPLAY <-> CHANGE.
2)	Open tab CONDITIONS.
3)	Click on INSERT CONDITION(S).
4)	CONDITION TYPE NAME -fill in V104 Credit-Side Surrender Value
5)	Click on APPLY.
New field opens and data input is needed in the same tab for VALID FROM date and 
4.	Continue the filling of data in the same tab
 
1)	VALID FROM- regardless of the details provided, the purchase option will be settled with the final payment at the end of the contract.
2)	UNIT PRICE- according to request
3)	Go to the tab VALUATION PARAMETERS.
5.	Follow next steps in the same tab
1)	Click on SAVE.
6.	Repeat steps 2-3 from chapter 4.5.3.1. Manual elongation.
 	NOTE: To remove wrongly created condition, firstly reverse postings. How to reverse postings is described in chapter 4.5.14.1. Reverse last valuation and then remove chosen condition 
 
1)	Click on CHANGES BETWEEN DISPLAY <->CHANGE 
2)	Go to CONDITIONS tab
3)	Choose condition which should be deleted
4)	Click on DELETE CONDITION(S)

5.5.14.2.	Automatic purchase option
To perform an indexation for a lease contract automatically follow next steps
1.	Repeat steps 1 to 3 from chapter 4.5.3.2. Automatic elongation.
2.	Select all data for contracts indexation.
3.	Paste data into the macro file, in the tab MAKRO_CHANGE by following next steps
 
1)	COMPANY CODE, SAP CONTRACT NUMBER, CONDITION TYPE, UNIT PRICE, TIME SLICE must be filled in.
4.	Repeat steps 6 to 10 from 4.5.3.2. Automatic elongation.
5.5.15.	Delete last valuation
In case when change will have to be done in previous and already posted period, follow steps below.
5.5.15.1.	Reverse last valuation
1.	Start transaction RECN - PROCESS CONTRACT 
 
1)	COMPANY CODE – Company code in which contract exists
2)	CONTRACT – contract number
3)	Press ENTER
2.	Next window will appear
 
1)	Go to tab VALUATION
2)	Click on CANCEL VALUATION
3.	New window will show up
 
1)	FISCAL YEAR- current FY
2)	POSTING PERIOD- current period
3)	REVERSE LAST RUN ONLY- If there are more than one period to be reversed this line should be unticked, to reverse last valuation leave this field marked
4)	Choose REVERSAL IN CLOSED PERIOD and first day of current month
5)	Tick use GRID CONTROL
6)	MODE	- choose SIMULATION
7)	Click on EXECUTE
 	NOTE: ALWAYS remember to first use MODE SIMULATION before posting the valuations.
4.	Below window will appear
 
	Status of the simulation is GREEN, which means that reversal can be done without errors.
	If there are RED dots, click on Error Log to investigate the issue. How to handle issues related to valuation reversal is described in chapter 4.6.14. Error handling 
5.	Press F3 to go back to previous window
6.	Change MODE to UPDATE RUN and press F8 to proceed with the reversal.
  
7.	Repeat steps 4-5 of this chapter             
8.	After reversal of valuation, last valuation step MUST be deleted. In order to do that follow chapter 4.5.14.2.	Remove last valuation step
5.5.15.2.	Remove last valuation step
After reversing last valuation or before posting one on contract it is possible to delete last valuation step. In order to do that, follow steps below.
1.	Go to VALUATION tab
 
1)	Check status of valuation
	NOT YET POSTED (empty dot)- valuation was performed on contract but not posted yet, last valuation can be deleted
	POSTED ENTRIES EXIST (green dot)- valuation was already posted on contract, last valuation step cannot be deleted
	POSTED ENTRIES FORM PRELIMINAR (grey dot)- means that inserted change on contract is overlapping with already posted period, last valuation can be deleted and after that valuation from last period can be reversed.
2)	Click on DELETE LAST VALUATION STEP
2.	New window will pop up
 
1)	Click on YES
3.	Screen will back to VALUATION tab
 
1)	VALUATION STATUS FLAG will change for white with meaning that valuation status is OPEN
5.5.15.3.	Set deletion flag on contract
In case wrongly created contract it cannot be removed from the system yet can be deactivated. To do so, follow steps below
1.	Follow steps form chapter 4.5.14.1.	Reverse last valuation and 4.5.14.2. Remove last valuation step
2.	Set END DATE on GENERAL DATA WITH FAST ENTRY
 
1)	Put date one day earlier than current date 
3.	Go to VALUATION PARAMETERS tab
 
1)	Set same date in PROBABLE END
4.	Follow next steps
 
1)	Click on EDIT
2)	Go to CHANGES STATUS
3)	Choose ARCHIVE
4)	Click on SET DELETION FLAG
5.	After setting deletion flag
 
1)	SAVE contract
2)	SYSTEM STATUS- ACTV DLFL REL means that deletion flag was set and any other changes on contract cannot be done.

5.5.16.	Error handling
During contract maintenance or creation new one it might happen that some errors occur. Below examples of common errors with steps description how to handle such issues.
In case of creation of contract in foreign currency error regarding missing currency rule will show.
 
I error occur, follow steps below
1.	On contract in RECN - PROCESS CONTRACT transaction

 
1)	Go to POSTING PARAMETERS tab 
2)	Click on CRCYTRRULE 
3)	Choose FOREIGN CURRENCY 
2.	Perform valuation on contract once again
In case of changes done on old contract it might happen that error regarding liability closing balance pop up.
 
If error occur, follow steps below.
3.	On contract in RECN - PROCESS CONTRACT transaction
 
1)	Go to VALUATION PARAMETERS tab 
2)	Change DISPLAY MODE to CHANGE MODE
3)	Open CORRECTIONS tab on recent valuation
4)	Click on ADD CORRECTION
4.	New line will show below
 
1)	Open dropdown list
2)	Choose 03 CORR. CLEARING DUPLICATE
3)	Set value same as in error
5.	Next
 
1)	Choose valuation step from where error occur.
6.	Save contract and perform valuation on contract one again.
During changes on old contracts, error regarding not existing user might show up in SAP RE-FX.
1.	If error occur, follow steps below
 
1)	USER XXXX (where XXXX stands for user ID number) DOES NOT EXIST might pop up during valuation step calculation after changes on contract, follow steps below to resolve error	
2.	On contract in RECN - PROCESS CONTRACT
 
1)	Change mode to CHANGE form DISPLAY
2)	Go to EXTRAS
3)	Choose USER DATA
4)	In new window in PERSON RESPONSIBLE put own SAP RE-FX ID
5)	Click on SAVE
3.	Save contract and perform valuation on contract once again.
During reversal of valuation last step, error regarding posting date might pop up.
 
1.	To handle error, go back to initial screen described in 4.5.14.1.	Reverse last valuation
 
1)	Correct POSTING DATE and corresponding POSTING PERIOD if necessary
2)	Click on  EXECUTE
2.	For errors which cannot be handled by GSC Clerk create JIRA ticket under path: https://jira.metrosystems.net/servicedesk/customer/portal/251/create/310
5.6.	Create new contract in SAP RE-FX
5.6.1.	Manually created
Contracts created in SAP RE-FX can be divided on two types: Lease In- when a lessee (the company using the asset) enters into a lease agreement to acquire the right to use an asset from another party and Lease Out- when a company leases out an asset that it owns or lease (in case of sublease) to another party.
Lease out contracts are inserted in SAP RE-FX in case of sublease of leased contracts. Under path below booking example of a sublease classified as finance lease can be found.
https://metro.sharepoint.com/:x:/r/sites/intranet-mag-Group-Consolidation/_layouts/15/Doc.aspx?sourcedoc=%7B92638578-1D5D-4B99-A09B-4DBE5CDD3075%7D&file=Examples%20of%20recog-derecog%20receivables%20FL.xlsx&action=default&mobileredirect=true
To create new contract manually follow steps below:
1.	Go to transaction RECN - PROCESS CONTRACT
 
1)	Double click on RECN - PROCESS CONTRACT
2.	CONTRACT screen is visible.
 
1)	Click on CREATE OBJECT.
3.	Fill in the following fields:
 
1)	CONTRACT TYPE- Open the arrow and select the contract type from the list according to the request. 
2)	Fill in the COMPANY CODE as per the request. 
3)	Select CONTINUE

 	NOTE: There are different CONTRACT TYPE that could be created in RE-FX system. Refer to the following list indicated in SAP RE-FX print screen:
 


4.	 Next screen for REC XXXX <NEW> CREATE: GENERAL DATA WITH FAST ENTRY opens, where XXXX stands for Contract type opens. Fill in the following fields:
 
1)	COMPANY CODE- it is generated automatically by the system, to be checked if it the same as in LFI request
2)	CONTRACT START- copy form LFI request
TO- fill in according to LFI request
3)	CONTRACT NAME- fill in according to LFI request
4)	MAIN CONTRACT- fill in contract in case of Lease Out Sublease contracts.
5)	CONTRACT CURRENCY- it is generated automatically by the system, nevertheless, check if currency is same as in request. In case of different currency, insert one from request.
6)	LOCATION ID- in case of properties contracts, fill in given location
7)	Go to the tab PARTNERS
5.	On PARTNERS tab, in case of contract type: cars, trucks or other vehicle, fill in 
 
1)	Click on ASSIGN NEW PARTNER and then LEASE ENGINE VENDORS
6.	New window will appear
 
1)	Click on CONTINUE
7.	New window will appear
 
1)	Double click on PARTNER, according to request/contract documentation
8.	New window will appear
 
1)	Data for partner will appear on tab
2)	Click on OBJECTS
9.	On OBJECTS tab fill in
 
1)	Click on ASSIGN to add new object for the contract.
2)	Double click on COB CONTRACT OBJECT.
10.	New fields open in the same tab for CONTRACT OBJECT name and ACCOUNT ASSIGNMENT (COST CENTER). Continue the filling of data in the same tab:
 
1)	CONTRACT OBJECT- fill in according to LFI request
2)	ACCOUNT ASSIGNMENT (COST CENTER)- fill in according to LFI request
3)	Go to the tab CONDITIONS.
 	NOTE: Additional steps on how to add the ACCOUNT ASSIGNMENT are described hereafter:
 
1)	Click on the square to open the next window RESTRICT VALUE RANGE (1).
2)	Copy data from request
3)	Click on START SEARCH, the following window will pop-up.
On new window
 
1)	Double click on the found COST CENTER.
11.	 CONDITIONS tab is visible, Fill in the following fields
 
1)	Click on INSERT CONDITION(S).
2)	Select condition type as per the LFI input
3)	Click on APPLY.
 	NOTE: In case of Lease Out:
 
1)	Click on INSERT CONDITION(S).
2)	Select condition type as per the LFI input
3)	Click on APPLY.
New field opens and data input is needed in the same tab for UNIT PRICE.
12.	Continue the filling of data in the same tab
 
1)	CONDITION PURPOSE- It is generated automatically by the system.
2)	VALID FROM- It is generated automatically by the system and is the same as start date of the contract 
3)	UNIT PRICE- insert data form LFI request
4)	CURRENCY- It is generated automatically by the system.
5)	FORMULA- It is generated automatically by the system.
6)	Go to the tab VALUATION PARAMETERS.
13.	VALUATION PARAMETERS tab is visible, Fill in the following fields
 
1)	Click on CREATE TERM
2)	Choose IFRS 16
3)	Select line with created object COB 0010
14.	Continue in the same tab
 
1)	Click on the FLAG to set status to complete.
2)	SAVE the contract.
3)	Click on ACTIVATE to activate the contract.
15.	Continue by clicking on YES:
 
16.	 System will automatically open first tab GENERAL DATA
 
1)	CONTRACT – contract number is automatically generated.
2)	SYSTEM STATUS – field value is automatically changed to ACTV REL, which means that contract is active and will generate postings.
3)	Message STATUS WAS CHANGED appears.
17.	 Go to VALUATION tab to set VALUATION RULE
 
4)	Click on PERFORM VALUATION.
5)	Enter VALUATION TITLE provided by LFI
 	NOTE: Only a few clients require change of VALUATION TITLE. If change is not required or it’s not mentioned in rulebook, leave system message.
6)	Click on CONTINUE
18.	System will display window with VALUATION RESULT
 
1)	Go to tab CLEARING
2)	Check if contract ends with the date given in the excel file. If not, repeat the steps to find the issue and correct the contract. 
3)	Click on SAVE.
5.6.2.	Automatically created via macro
To create new lease-in contract automatically follow steps below:
1.	Open the file macro file. The newest version of macro can be found under path: https://metro.sharepoint.com/:x:/r/sites/ContinuousImprovementGSC/MSERV%20PL%20Macro%20Repository/SAP%20RE-FX%20makro%20for%20contract%20creation%20and%20change_v2.0.xlsm?d=w2bebaaafb0f446bcb6010997706a53e7&csf=1&web=1&e=z17npc
and go to sheet MAKRO_CREATE.
2.	Click on ENABLE CONTENT to enable macro.
 
3.	 Open request received from LFI and fill in macro file accordingly. 
4.	 Press button CREATE CONTRACTS in cell B1.
 
5.	SAP will inform twice about that macro want to connect with SAP. Both times click OK.
 
6.	After the contracts are created in SAP RE-FX the below message shall appear, click on OK.
 
7.	The contract data will appear in columns A:C:
 
1)	SYSTEM MESSAGE: CONTRACT CREATION – In column A, system adds a message informing about creation of contract in specified company code. The structure of comment is described as follow: Contract CCCC/XXXXXXXX was created. CCCC stands for Company code for which contracts is created, XXXXXXXX stands for number of new created contract.
2)	SYSTEM MESSAGE: VALUATION PREPARATION – In column B, macro inserts system message which informs about the valuation run.
3)	CREATED CONTRACT NUMBER – In column C, macro inserts numbers for new created contract.
5.7.	 Perform simulation of valuation in SAP RE-FX
METRO BG	4.7. Perform simulation of valuation in SAP RE-FX
METRO FR	4.7. Perform simulation of valuation in SAP RE-FX

MAKRO CZ	4.7. Perform simulation of valuation in SAP RE-FX
METRO HR	4.7. Perform simulation of valuation in SAP RE-FX

METRO DE	4.7. Perform simulation of valuation in SAP RE-FX
METRO HU	4.7. Perform simulation of valuation in SAP RE-FX

MAKRO ES	4.7. Perform simulation of valuation in SAP RE-FX
METRO IT	4.7. Perform simulation of valuation in SAP RE-FX

METRO KZ	4.7. Perform simulation of valuation in SAP RE-FX
METRO TR	4.7. Perform simulation of valuation in SAP RE-FX

MAKRO NL	4.7. Perform simulation of valuation in SAP RE-FX
METRO UA	4.7. Perform simulation of valuation in SAP RE-FX

MAKRO PT	4.7. Perform simulation of valuation in SAP RE-FX
ES VTO	4.7. Perform simulation of valuation in SAP RE-FX

METRO SK	4.7. Perform simulation of valuation in SAP RE-FX
MAG	4.7. Perform simulation of valuation in SAP RE-FX

MIB	4.7. Perform simulation of valuation in SAP RE-FX
Eijsink	4.7. Perform simulation of valuation in SAP RE-FX

Dish Digital	4.7. Perform simulation of valuation in SAP RE-FX
PL PropCO	4.7. Perform simulation of valuation in SAP RE-FX

Metro Digital	4.7. Perform simulation of valuation in SAP RE-FX
BE PropCO	4.7. Perform simulation of valuation in SAP RE-FX

Aviludo	4.7. Perform simulation of valuation in SAP RE-FX
SE JOHBECO	4.7. Perform simulation of valuation in SAP RE-FX

METRO MARKETS DE	4.7. Perform simulation of valuation in SAP RE-FX
Metro Logistics	4.7. Perform simulation of valuation in SAP RE-FX

Pro á Pro ES	4.7. Perform simulation of valuation in SAP RE-FX
METRO RS	N/A
5.7.1.	 Check maintained contracts
To check if contracts were created and changed according to the request – go to the manual saved under below path and proceed with the verification: \\Dus30fsrb010-smb.r2.madm.net\ssc_szczecin\Departments\Division_GA\20. Team_FA\95. PROJECT - ALL COMPANIES\Standardization\20_Control points\72. Check correctness of contract creation and change.docx  
To check if created contracts are active, follow steps below
1.	Open YRE00CNSTATUS - Inactive/Active contracts in SAP RE-FX
 
1)	COMPANY CODE- insert number for processed client
2)	Mark INACTIVE CONTRACTS
3)	Click on EXECUTE
2.	New window will open
 
1)	Click on ENTERED ON column
2)	Click on FILTERS
3)	In FIRST ENTERED ON fill in from 1st  to last day of currently processed month
4)	Click on COPY
3.	When report will generate check if any data occur. If yes, that means that newly created contracts form column CONTRACT were not activated, and it MUST be done. How to activate contract is described in chapter 4.6.1. Manually created step 14. If report is empty it means all new contracts are active and next step can be performed.
 

5.7.2.	 Check status of valuation rule and valuation process
Report below (RECEISRULECN) displays valuation rules for the contracts. Make sure that the RULE STATUS and VAL. STATUS is marked as COMPLETE. Those contracts which are not marked as COMPLETE MUST be revised.
As soon as the master data, terms, payment frequency, conditions are up to date, the flag MUST be set to COMPLETE. The column VAL.STATUS demonstrates whether valuation has been already performed for the valuation rule. 
4.	Both flags – RULE ST. and VAL. STATUS – MUST be marked as completed.
  
5.	Go to transaction RECEISRULECN - INFORMATION SYSTEM- VALUATION RULES 
 
4)	COMPANY CODE – according to processed client
5)	Click on MULTIPLE SELECTION
6)	Choose EXCLUDE SINGLE VALUES tab
7)	Enter ME11 and ME52 to exclude intercompany contracts
8)	Press COPY
9)	CONTRACT VALIDITY – first day of closing month
10)	Layout – /CHECK CONTR  
11)	Click on EXECUTE.
6.	The report will be displayed
 
1)	Check column with RULE STATUS rule – it should be completed with white and black flag. Those contracts which are not marked as COMPLETE MUST be revised.
2)	Check VALUATION STATUS – it should be completed with white and black flag. Those contracts which are not marked as COMPLETE MUST be revised.
 	NOTE:   Valuation rule shows completeness of insertion of master data parameters in the contract like START/END DATES, object existing, condition, and confirming it with creation of term. In case status is incomplete GSC Clerk MUST check if master data were made, and flag was set to complete. If no, GSC Clerk has to correct and/or set up rule as completed.  

 	NOTE: Valuation status shows completeness of new valuation calculation. In case changes in master data were made, but no new valuation was calculated, the system will continue to post data based on previous valuation.

5.7.3.	Perform simulation of valuation in SAP RE-FX
This program conducts the leasing valuation for contracts and displays the results in a list. In case of any error messages, the contracts MUST be revised on a single contract level. 
1.	Start transaction RECEPR - PERFORM CONTRACT VALUATION.
 
1)	COMPANY CODE – write code for processed client
2)	Click on MULTIPLE SELECTIONS
3)	Choose EXCLUDE SINGLE VALUES tab
4)	Enter ME11 and ME52
5)	Press COPY
6)	CONTRACT VALIDITY – first day of closing month
7)	EXECUTION MODE – choose SIMULATION mode
8)	Click on EXECUTE
2.	Next window will appear
 
1)	Check column STATUS – it should be GREEN or with sign EQUAL (=) for all contracts. In other case, investigate what causes an error. Ho to deal with other statuses than green, is described in chapter 4.8. Investigate errors
2)	After checking STATUS click on LOG to review status. 
5.8.	Investigate errors
1.	Contracts with red dot status need to be revised and have completed valuation. 
 
2.	Next
 
1)	Double Click on contract number with RED status
2)	Read explanation of occurred error	
3.	How to react to given error is explained in 4.9. Resolve errors
5.9.	Resolve errors
During performing valuation errors can occur. To resolve specific issue, follow  steps below. 
1.	In case of RED STATUS valuation rule MUST be revised on alarmed contract. How to perform valuation and set both flags on one contract is described in chapter 4.6. Create new contract in SAP RE-FX.
 
2.	Red dots in LOG can show when valuation rule is not set- go back to contract and change valuation rule on COMPLETE
 
3.	 Contact GSC Service Desk Team to support identification of the error if necessary. How to ask for technical support is described in chapter 4.10. Create the ticket for technical support
4.	To resolve error regarding difference between clearing and expense, follow steps below
 
	In case of error with difference between clearing and expense, firstly check if RECEPR transaction was conducted correctly, meaning if CONTRACT VALIDITY was filled in. Error occurring for contracts with INCOMPLETE RULE DATA and OPEN VALUATION from the past and needs to be excluded from calculation. If error occurs on contract created in current month, investigate why rules are not done on contract. If should be, go back to contract and set flags on contract according to 4.6. Create new contract in SAP RE-FX
5.	To resolve error regarding +/- sign in the currency field, follow step below
 
	In case of error with different signs, contract end date was wrongly changed. To resolve issue valuation on contract MUST be deleted along with created time slice and end date MUST be changed according to procedure. How to delete last valuation on contract is described in chapter 4.5.14. Delete last valuation.
6.	In case of not defined account during valuation posting, follow steps below
 
	Check if intercompany contracts are excluded from posting, if not, go back to start of transaction and exclude contracts ME11, ME52
	In case of error occurring for contracts other than ME11 and ME52, contact with technical department and LFI.
7.	In case of not open period error, follow step below
 
	If information about closed period pops up, check if correct period was set during simulation. If not, go back and correct it. If yes, contact technical department to open period.
5.10.	Create the ticket for technical support
In case of errors created by LFI changes on contracts, contact with responsible person, according to Communication rulebook. In order to do that use REWORK in MSIT tool. Instruction how to use MSIT can be found under following path: https://metro.sharepoint.com/sites/MSIT2
In case of problems related to lack of accesses or missing cost centers in SAP RE-FX contact GSC support lease engine by creating ticket in JIRA by using link https://jira.metrosystems.net/servicedesk/customer/portal/251/create/310.
5.11.	Perform valuation in SAP RE-FX
METRO BG	4.11. Perform valuation in SAP RE-FX
METRO FR	4.11. Perform valuation in SAP RE-FX

MAKRO CZ	4.11. Perform valuation in SAP RE-FX
METRO HR	4.11. Perform valuation in SAP RE-FX

METRO DE	4.11. Perform valuation in SAP RE-FX
METRO HU	4.11. Perform valuation in SAP RE-FX

MAKRO ES	4.11. Perform valuation in SAP RE-FX
METRO IT	4.11. Perform valuation in SAP RE-FX

METRO KZ	4.11. Perform valuation in SAP RE-FX
METRO TR	4.11. Perform valuation in SAP RE-FX

MAKRO NL	4.11. Perform valuation in SAP RE-FX
METRO UA	4.11. Perform valuation in SAP RE-FX

MAKRO PT	4.11. Perform valuation in SAP RE-FX
ES VTO	4.11. Perform valuation in SAP RE-FX

METRO SK	4.11. Perform valuation in SAP RE-FX
MAG	4.11. Perform valuation in SAP RE-FX

MIB	4.11. Perform valuation in SAP RE-FX
Eijsink	4.11. Perform valuation in SAP RE-FX

Dish Digital	4.11. Perform valuation in SAP RE-FX
PL PropCO	4.11. Perform valuation in SAP RE-FX

Metro Digital	4.11. Perform valuation in SAP RE-FX
BE PropCO	4.11. Perform valuation in SAP RE-FX

Aviludo	4.11. Perform valuation in SAP RE-FX
SE JOHBECO	4.11. Perform valuation in SAP RE-FX

METRO MARKETS DE	4.11. Perform valuation in SAP RE-FX
Metro Logistics	4.11. Perform valuation in SAP RE-FX

Pro á Pro ES	4.11. Perform valuation in SAP RE-FX
METRO RS	N/A

After errors are resolved, mass valuation MUST be performed. In order to do that, follow steps below.
1.	Go back to transaction RECEPR - PERFORM CONTRACT VALUATION 
 
1)	EXECUTION MODE – change UPDATE RUN mode
2)	Click on EXECUTE
2.	Next window will appear
 
1)	Check column STATUS – After resolving errors STATUS should be green or with sign equal (=) for all contracts. 
2)	Click on BACK
5.12.	Perform posting in SAP RE-FX
METRO BG	4.12. Perform posting in SAP RE-FX
METRO FR	4.12. Perform posting in SAP RE-FX

MAKRO CZ	4.12. Perform posting in SAP RE-FX
METRO HR	4.12. Perform posting in SAP RE-FX

METRO DE	4.12. Perform posting in SAP RE-FX
METRO HU	4.12. Perform posting in SAP RE-FX

MAKRO ES	4.12. Perform posting in SAP RE-FX
METRO IT	4.12. Perform posting in SAP RE-FX

METRO KZ	4.12. Perform posting in SAP RE-FX
METRO TR	4.12. Perform posting in SAP RE-FX

MAKRO NL	4.12. Perform posting in SAP RE-FX
METRO UA	4.12. Perform posting in SAP RE-FX

MAKRO PT	4.12. Perform posting in SAP RE-FX
ES VTO	4.12. Perform posting in SAP RE-FX

METRO SK	4.12. Perform posting in SAP RE-FX
MAG	4.12. Perform posting in SAP RE-FX

MIB	4.12. Perform posting in SAP RE-FX
Eijsink	4.12. Perform posting in SAP RE-FX

Dish Digital	4.12. Perform posting in SAP RE-FX
PL PropCO	4.12. Perform posting in SAP RE-FX

Metro Digital	4.12. Perform posting in SAP RE-FX
BE PropCO	4.12. Perform posting in SAP RE-FX

Aviludo	4.12. Perform posting in SAP RE-FX
SE JOHBECO	4.12. Perform posting in SAP RE-FX

METRO MARKETS DE	4.12. Perform posting in SAP RE-FX
Metro Logistics	4.12. Perform posting in SAP RE-FX

Pro á Pro ES	4.12. Perform posting in SAP RE-FX
METRO RS	N/A

Before posting valuation of all active leasing contracts in SAP RE-FX module simulation of posting needs to be performed to check if data in the system is correct. Simulation is also performed to update values in case of any changes made to the contracts. If there will be no errors, the posting of IFRS 16 in SAP RE-FX can be performed. In case of any errors, the leases contracts have to be corrected.
1.	To prepare simulation of posting of IFRS 16 open HS1 line in SAP.
 
2.	Go to transaction RECEEP - POST VALUATION FOR CONTRACTS and fill in following fields.
 
1)	COMPANY CODE– fill in according to processed client, 
2)	CONTRACT TYPE- click on MULTIPLE SELECTIONS to exclude ME11 and ME52 contract intercompany type
 
	Go to tab EXCLUDE SINGLE VALUES
	Type in ME11 and ME52
	Press EXECUTE button
3)	MONTH FOR POSTING RUN – enter number of closing month according to calendar year and press ENTER
YEAR FOR POSTING RUN – click ENTER button and rest of positions connected with date such as posting, and document date will be filled in automatically. Alternatively, fill current calendar year.
DUE DATE- fill in last day of currently closed calendar month
4)	DOCUMENT HEADER TEXT- leave technical name generated by SAP RE-FX
POSTING DATE- check if in correspondence with MONTH OF POSTING
DOCUMENT DATE- check if in correspondence with MONTH OF POSTING
POSTING PERIOD- fill corresponding to POSTING DATE period of currently closed FY
POSTING RUN MODE – choose SIMULATION 
5)	Choose EXECUTE button
3.	Next window show all postings which system will post in chosen period.
 
1)	Choose ERROR LOG 
4.	New window will appear 
 
1)	Check status of controls If status is only yellow (WARNINGS- HIDE) and green (INFORMATION- HIDE) it means that SIMULATION OF VALUATION was performed without errors. If status showing any numbers with stop (TERMINATIONS- HIDE) and red (ERROR- HIDE), contracts with errors needs to be checked and corrected. 
2)	Click on BACK to display transaction start window
5.	After displaying transaction RECEEP - POST VALUATION FOR CONTRACTS
 
1)	POSTING RUN MODE – change to UPDATE RUN 
2)	Choose EXECUTE button
6.	Follow steps 3-4 of this chapter
7.	After performing posting of valuation on contracts, follow next steps. 
5.13.	Perform and post FX valuation in SAP RE-FX
METRO BG	4.13. Perform and post FX valuation in SAP RE-FX
METRO FR	4.13. Perform and post FX valuation in SAP RE-FX

MAKRO CZ	4.13. Perform and post FX valuation in SAP RE-FX
METRO HR	4.13. Perform and post FX valuation in SAP RE-FX

METRO DE	4.13. Perform and post FX valuation in SAP RE-FX
METRO HU	4.13. Perform and post FX valuation in SAP RE-FX

MAKRO ES	4.13. Perform and post FX valuation in SAP RE-FX
METRO IT	4.13. Perform and post FX valuation in SAP RE-FX

METRO KZ	4.13. Perform and post FX valuation in SAP RE-FX
METRO TR	4.13. Perform and post FX valuation in SAP RE-FX

MAKRO NL	4.13. Perform and post FX valuation in SAP RE-FX
METRO UA	4.13. Perform and post FX valuation in SAP RE-FX

MAKRO PT	4.13. Perform and post FX valuation in SAP RE-FX
VTO	4.13. Perform and post FX valuation in SAP RE-FX

METRO SK	4.13. Perform and post FX valuation in SAP RE-FX
MAG	4.13. Perform and post FX valuation in SAP RE-FX

MIB	4.13. Perform and post FX valuation in SAP RE-FX
Eijsink	4.13. Perform and post FX valuation in SAP RE-FX

Dish Digital	4.13. Perform and post FX valuation in SAP RE-FX
PL PropCO	4.13. Perform and post FX valuation in SAP RE-FX

Metro Digital	4.13. Perform and post FX valuation in SAP RE-FX
BE PropCO	4.13. Perform and post FX valuation in SAP RE-FX

Aviludo	4.13. Perform and post FX valuation in SAP RE-FX
SE JOHBECO	4.13. Perform and post FX valuation in SAP RE-FX

METRO MARKETS DE	4.13. Perform and post FX valuation in SAP RE-FX
Metro Logistics	4.13. Perform and post FX valuation in SAP RE-FX

Pro á Pro ES	4.13. Perform and post FX valuation in SAP RE-FX
METRO RS	N/A

1.	To perform valuation on contract in foreign currency, open transaction OBJVAL - Foreign Crcy Valuation - Val.Objects
 
1)	COMPANY CODE- fill in each Company Code separately
VALUATION KEY DATE- fill in last day of currently closed period
VALUATION AREA- fill in ALWAYS LE
2)	On POSTING tab
3)	Make sure that PERFORM TEST RUN is selected
4)	Go to VALUATION OBJECTS	
2.	On VALUATION OBJECTS tab
 
1)	Mark VALUATE CONTRACT BALANCES
2)	Fill in LE in AGGREGATION LEDGER
3)	Lease In and Lease Out contracts MUST be performed separately. Choose LEASE LIABILITIES (RECL) in case of Lease In contracts or LEASE RECEIVABLES (RECR) in case of Lease Out contracts
4)	Lease In and Lease Out contracts MUST be performed separately. Fill in 2330770000 in case of Liabilities or 1151330000 in case of Lease Out contracts and receivables postings.
5)	Press EXECUTE
3.	New window will appear. Make sure that posting is done without errors. In case of any issue, resolve error and repeat Test run.
 	NOTE: If no data appears, it means that there are no foreign currency contracts for the given Company Code, and there is no need to run the transaction without test.

 
1)	Press GO BACK  to execute POSTING RUN
4.	After going back, new window will appear
 
1)	Go to POSTING tab
2)	Choose UPDATE RUN
3)	Click on EXECUTE
5.	New window will appear. 
 
6.	Repeat steps for Lease Out/Lease In contracts, depends on which ones was done firstly.
5.14.	Perform and post liabilities/receivables maturity split in SAP RE-FX
Before posting, check in matrix which scenario is related to processed client. 
METRO BG	Rulebook	METRO FR	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX

MAKRO CZ	Rulebook	METRO HR	Rulebook
METRO DE	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX
METRO HU	Rulebook
MAKRO ES	Rulebook	METRO IT	Rulebook
METRO KZ	N/A	METRO TR	Rulebook
MAKRO NL	Rulebook	METRO UA	Rulebook
MAKRO PT	Rulebook	VTO	Rulebook
METRO SK	Rulebook	MAG	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX

MIB	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX
Eijsink	N/A
Dish Digital	Rulebook	PL PropCO	Rulebook
Metro Digital	N/A	BE PropCO	Rulebook
Aviludo	Rulebook	SE JOHBECO	Rulebook
METRO MARKETS DE	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX
Metro Logistics	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX

Pro á Pro ES	4.14. Perform and post liabilities/receivables maturity split in SAP RE-FX
METRO RS	N/A

1.	In HS1 SAP line start transaction OBJREG - Regrouping of Valuation Objects  by double clicking it.
 
1)	COMPANY CODE – fill in according to processed client
VALUATION KEY DATE – last day of processed month
SORT METHOD – type REFX for Lease In contracts or LOUT for  Lease Out contracts
VALUATION AREA- fill in ALWAYS LE
2)	Choose PERFORM TEST RUN
3)	Mark FILL TRANSACTION CURRENCY AMOUNT
4)	Click on VALUATION OBJECT tab
2.	On VALUATION OBJECTS tab
 
1)	Fill in LE in AGGREGATION LEADGER
2)	Lease In and Lease Out contracts MUST be performed separately. Choose LEASE LIABILITIES in case of Lease In contracts or LEASE RECEIVABLES in case of Lease Out contracts
3)	Lease In and Lease Out contracts MUST be performed separately. Fill in 2330770000 in case of Liabilities or 1151330000 in case of Lease Out contracts and receivables postings.
4)	Click on EXECUTE
3.	New window will appear Make sure that posting is done without errors. In case of any issue, resolve error and repeat Test run.
 
 	NOTE: Values in OBJREG column “Posted Amt. CC. Crurr” needs to fit to values in RECEISRECLASSIFY (for respective contract), for foreign exchange contract this check will not work

4.	GO BACK  to execute POSTING RUN
 
5.	After going back, new window will appear
 
1)	Choose in POST DOCUMENTS IMMEDIATELY
2)	Click on EXECUTE 
6.	Repeat steps for Lease Out/Lease In contracts, depends on which ones was done firstly.
 	NOTE: In case of additional changes which could affect liability/receivables split, OBJREG SAP transaction MUST be performed once again. In case of multiple changes, perform Reset Reclassification (1) and run OBJREG again for all contracts, in case of singular changes, perform additional split on object level (2). 
 
 

5.15.	Perform posting in SAP FI-CO
After posting valuation in SAP RE-FX, data needs to transfer into SAP FICO.
There are a few methods of valuation posting in SAP FICO. 
Before posting, check in matrix which scenario is related to processed client. 
METRO BG	Posting via interface
METRO FR	Posting via interface

MAKRO CZ	Posting via interface
METRO HR	Posting via. csv upload

METRO DE	Posting via interface
METRO HU	Rulebook

MAKRO ES	Rulebook
METRO IT	Posting via interface

METRO KZ	Posting via. csv upload
METRO TR	Posting via. csv upload

MAKRO NL	Rulebook
METRO UA	Posting via interface

MAKRO PT	Posting via. csv upload
VTO	Rulebook

METRO SK	Posting via interface
MAG
	Posting via interface

MIB	Posting via interface
Eijsink	N/A
Dish Digital	Posting via. csv upload
PL PropCO	Posting via. csv upload

Metro Digital	N/A	BE PropCO	Rulebook

Aviludo	N/A	SE JOHBECO	Rulebook

METRO MARKETS DE	Posting via interface
Metro Logistics	Posting via interface

Pro á Pro ES	N/A	METRO RS	N/A

All templates can be found under path below
https://metro.sharepoint.com/sites/ProcedureManagementPortal
5.15.1.	Posting via. csv upload
Based on data exported form RE-FX csv file for valuation posting in FICO is prepared. Export data to excel file. Go to transaction YRE00FIEXPORT - Export FI documents in HS1 SAP line
1.	Go to transaction YRE00FIEXPORT - Export FI documents in HS1 SAP line
 
1)	COMPANY CODE- fill in number for processed company
2)	POSTING DATE- fill in from beginning of reported period to first day of next period 
3)	Press ENTER
2.	Report will generate
 
1)	Click on CHANGE LAYOUT
3.	Choose layout
 
1)	Choose layout /NN
2)	Click on ADOPT
4.	Click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
5.	Copy template from previous closing folder and paste it to folder for currently closed period 
6.	Open exported file
 
1)	Click on SORT & FILTER
2)	Choose FILTER
7.	Make sure that postings related to reversals of maturity split form previous month are excluded form posting for this month. To do so, follow steps below.
 
1)	Go to COLUMN F
2)	MARK positions related to reversal of maturity split
3)	Press OK
8.	Next,
 
1)	Go to COLUMN S
2)	MARK positions related to reversal of maturity split
3)	Press OK
9.	Remove rows with data related to reversal of maturity split form previous month. Mark all rows which MUST be excluded from this posting, click on right mouse button, and choose DELETE ROW
 
10.	Go to CONTRACT NUMBER in COLUMN V
 
1)	Unfilter all lease out contracts started with 50
2)	Press OK 
11.	Next, exclude data related to maturity reversal within next period
 
1)	Go to COLUMN S
2)	UNMARK positions related to reversal of maturity split
3)	Press OK
12.	Mark COLUMNS A-W and click CTRL+C
13.	Open file GA.4.2.11_IFRS 16 Monthly Posting_Common (CTA-Local) Template.xlsx, file itself contains several sheets: 
 
1)	LI SOURCE- export form SAP RE-FX with data for lease in contracts
2)	LI CSV- tab for csv creation for posting in FICO for lease in contracts
3)	LI RECONCILIATION- check between source and csv tab and data from SAP RE-FX and FICO after posting
4)	LI FICO DATA- tab for export from SAP FICO after posting
5)	LI MAPPING- mapping of HS1 accounts into local accounts with split to appropriate cost center and business area
6)	LO SOURCE- export form SAP RE-FX with data for lease out contracts
7)	LO CSV- tab for csv creation for posting in FICO
8)	LO RECONCILIATION- check between source and csv tab and data from SAP RE-FX and FICO after posting
9)	LO FICO DATA- tab for export from SAP FICO after posting
10)	LO MAPPING- mapping of HS1 accounts into local accounts 
 	NOTE: Data on tabs LI MAPPING and LO MAPPING needs to be adjusted to local requirements
14.	Go to LI SOURCE 
 
1)	Paste copied data to columns A-W by pressing CTRL+V
2)	In COLUMN X- BALANCE and COLUMN Y-LOCAL GL ACCOUNT are formulas, make sure that are dragged to end of data from RE-FX.
3)	POSTING KEY in COLUMN O is in text form, to formulas in columns X and Y works, data MUST be converted to number
 
1)	Go to tab DATA
2)	Click to TEXT TO COLUMNS
3)	Press FINISH
4)	Mark COLUMN U with G/L ACCOUNT and repeat last step as for column O
15.	Before posting, make sure that data in csv tab match data exported form SAP RE-FX. In order to do that, follow steps below.
 
1)	Go to LI CHECK tab
2)	Click right mouse button to REFRESH table SOURCE and repeat same step with CSV table
16.	Create CSV file by clicking FILE
 
17.	Click SAVE AS-> BROWSE
 
18.	 Save file under path from rulebook for current closed period. Choose an extension for the file CSV (COMMA DELIMITED)-> Click SAVE 
 
19.	Upload data to FICO. Go to transaction YGL01_U2P - Automatic postings with excel upload in SAP FICO line
 
20.	Fill in
 
1)	COMPANY CODE- number assigned to processed client
BUSINESS TRANSACTION- ALWAYS 0005
2)	Choose file name by clicking on white box icon on right side
21.	Choose csv file
 
1)	Choose path to file for upload
2)	Click OPEN
22.	After the file is chosen, click EXECUTE
 
23.	Following window will appear, Click SAVE to post a csv file.
 
24.	To add attachment to the posting double click the document number that showed after posting. 
 
25.	Choose SERVICES FOR OBJECT -> CREATE -> CREATE NOTE
  
26.	Create note

  
1)	TITLE OF NOTE type in POSTING OF IFRS 16
2)	Click CONTINUE
27.	Repeat process for liability reversal in next period, lease out contracts and Receivables reversal in next period.
28.	After posting, reconciliation MUST be performed to make sure that all data was posted in FICO. In order to do that follow steps in chapter 4.14. Perform reconciliation of SAP RE-FX with SAP FI-CO. If errors will oaccur during posting via csv, go to chapter 4.16 Investigate errors
5.15.2.	Posting via interface
Table with Interface names
METRO BG	2016_REFX_OUT	METRO FR	3152_REFX_OUT
MAKRO CZ	2824_REFX_OUT	METRO HR	N/A
METRO DE	2238_REFX_OUT	METRO HU	N/A
MAKRO ES	N/A	METRO IT	3363_REFX_OUT
METRO KZ	N/A	METRO TR	N/A
MAKRO NL	N/A	METRO UA	3482_REFX_OUT
MAKRO PT	N/A	VTO	N/A
METRO SK	2828_REFX_OUT	MAG	0421_REFX_OUT
MIB	1833_REFX_OUT	Eijsink	N/A
Dish Digital	N/A	PL PropCO	N/A
Metro Digital	N/A	BE PropCO	N/A
Aviludo	N/A	SE JOHBECO	N/A
METRO MARKETS DE	4116_REFX_OUT
4131_REFX_OUT	Metro Logistics	0143_REFX_OUT

Pro á Pro ES	N/A	METRO RS	3479_REFX_OUT


1.	Go to transaction YRE00FIEXPORTMIP – RE-FX- CREATE POSTING FLAT FILE in SAP RE-FX
 
2.	Follow next steps:
 
1)	COMPANY CODE – fill in processed Company Code,
2)	POSTING DATE – fill in range of posting month from first to last day,
3)	INTERFACE – fill in according to table above,
4)	Choose VALUATION & RECLASSIFICATION to transfer result of valuation, FX valuation if in place and maturity split done by automatic transaction OBJREG. 
 	NOTE:  Valuation as a result of RECEEP (and OBJVAL) and maturity split as a result of OBJREG transaction can be performed separately.
Depending what data needs to be transfer form RE-FX to FICO, form of posting in interface transaction should be chosen
 


1)	Click on EXECUTE
3.	After transferring postings to SAP FICO system, go to transaction YSDI – SDI – SYSTEM FOR DATA INTERFACES in SAP RE-FX
 
1)	CALENDAR YEAR – fill in current calendar year
2)	INTERFACE – fill in fill in according to table above 
3)	DATE OF ARRIVAL – fill in according to rulebook and press ENTER
4.	Report will appear. Wait for STEP 2 FINISHED in column STATUS to make sure that transfer between SAP RE-FX and FICO is done
 
5.	After processing data from RE-FX, perform processing data in FICO
Go to transaction SM35 – BATCH INPUT, SESSION OVERVIEW in dedicated line for processed company code in SAP FICO system to check if packages were transferred without errors.
 
6.	 Follow next steps
 

1)	SESSION - fill in name of interface and replace OUT by * and press ENTER
2)	STATUS – In case icon is NEW it means that data was transferred form SAP RE-FX and needs to be posted in SAP FICO. If icon is IN PROCESSING that means that posting in FICO is in progress. If status is PROCESSED, it means that postings were done without any errors. If status is ERRORS, it means that posting was not done, and data needs to be review. How to review errors is described in 4.16 Investigate errors
3)	Choose transfer from SAP RE-FX
4)	Click on PROCESS
7.	New window will appear
 
1)	Choose DISPLAY ERRORS ONLY,
2)	Click PROCESS
8.	Wait for status change to PROCESSED
 
9.	After posting, reconciliation MUST be performed to make sure that all data was posted in FICO. In order to do that follow steps in chapter 4.14. Perform reconciliation of SAP RE-FX with SAP FI-CO. If errors will oaccur during posting via csv, go to chapter 4.16 Investigate errors
5.16.	Investigate errors
During Posting via csv errors can occur. To investigate what caused and issue, follow step below.
1.	To investigate what caused and issue go to YGL01_U2P- Automatic postings with excel upload FICO line.
 
1)	Double Click on Icon with STOP to investigate what caused an error 
2.	When new window will appear
 
1)	Investigate error message. To resolve issue related to the message, follow steps in chapter 4.17. Resolve errors
During Posting via interface errors can occur. To investigate what caused and issue, follow step below.
3.	To investigate what caused and issue go to SM35- Batch Input Monitoring FICO line.
 
1)	Double Click on Icon with INCORRECT to investigate what caused an error 
4.	When new window will appear
 
1)	Go to LOG CREATED ON DD.MM.YYYY tab
2)	Investigate error message. To resolve issue related to the message, follow steps in chapter 4.17. Resolve errors
5.17.	Resolve errors
In case of any differences GSC Clerk MUST investigate what causes disparity.
In case of errors related to balance in import some lines from source are not included in csv tab or data from last month remain in the file. To resolve an issue, check in csv file if all formulas were dragged properly.
Regarding missing account, closed period, or not existing Cost Center in FICO, first, check if all formulas are properly assigned. If no, correct formulas and perform posting once again. If yes, contact with LFI for proper account to be mapped or new Cost Center.
In case of errors impossible to resolve on GSC side, follow steps in 4.18. Create the ticket for technical support
During package transfer it might happen that package will not transfer between systems. In case of that kind errors caused by missing package, investigate what was a source of error, follow 4.18. Create the ticket for technical support
Regarding missing account, closed period, or not existing Cost Center in FICO, follow steps in 4.18. Create the ticket for technical support
If errors refer to improper data indicated in YRE00FIEXPORTMIP– RE-FX- CREATE POSTING FLAT FILE, go back to transaction, correct data and perform upload once again
If interface was performed for all documents and supposed to be done only for limited data, reversal in FICO needs to be performed.
5.18.	Create the ticket for technical support
In case of problems related to lack of accesses or missing cost centers in SAP FICO contact GSC support lease engine by creating ticket in JIRA by using link https://jira.metrosystems.net/servicedesk/customer/portal/251/create/310.
5.19.	 Perform reconciliation of SAP RE-FX with SAP FI-CO
METRO BG	Rulebook	METRO FR	Rulebook
MAKRO CZ	Rulebook	METRO HR	Rulebook
METRO DE	Rulebook	METRO HU	Rulebook
MAKRO ES	Rulebook	METRO IT	Rulebook
METRO KZ	Rulebook	METRO TR	Rulebook
MAKRO NL	Rulebook	METRO UA	Rulebook
MAKRO PT	Rulebook	VTO	Rulebook
METRO SK	Rulebook	MAG	Rulebook
MIB	Rulebook	Eijsink	N/A
Dish Digital	Rulebook	PL PropCO	Rulebook
Metro Digital	N/A	BE PropCO	Rulebook
Aviludo	N/A	SE JOHBECO	Rulebook
METRO MARKETS DE	Rulebook	Metro Logistics	Rulebook
Pro á Pro ES	N/A	METRO RS	N/A

All templates can be found under path below
https://metro.sharepoint.com/sites/ProcedureManagementPortal 
After performing valuation posting in both systems SAP RE-FX and SAP FICO, it is necessary to prepare comparison of done postings. In order to do perform reconciliation of values per accounts between two systems is prepared, follow steps below, contingent on SAP FICO line in use.
1.	Open the file GA.4.2.11_IFRS 16 RE-FX vs FICO Reconciliation_Common (CTA-Local) Template.xlsx, there are several tabs
 
1)	RE-FX SOURCE DATA- tab divided on two, for data extracted from SAP RE-FX
FICO SOURCE DATA- tab dedicated for source data form FICO after monthly posting
RIGHT OF USE- reconciliation part for RoU accounts 
P&L- reconciliation part for P&L accounts
MAPPING- mapping of accounts
1.	To export data from RE-FX, go to YRE00GLCNCCSUM - Display of Cumulative GL as per Cont
 
1)	Fill in COMPANY CODE
2)	POSTING DATE TO- fill last day of closing period
3)	Click on MULTIPLE SELECTIONS on G/L
4)	Put 1* and 2*
5)	Click on COPY
6)	Click on EXECUTE
2.	New window will appear
 
3.	Click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
4.	Go back to start of YRE00GLCNCCSUM - Display of Cumulative GL as per Cont
 
1)	Fill in COMPANY CODE
2)	Click on MULTIPLE SELECTIONS on G/L 
3)	Put 3* 
4)	Click on COPY
5)	POSTING DATE fill inf rom 1st October of current FY till last day of currently reported period
6)	Click on EXECUTE
5.	New window will appear
 
6.	Click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
7.	Copy paste data from first exported file to RE-FX SOURCE DATA tab to COLUMNS A-H- dedicated to RoU
 
8.	Copy paste data from second exported file to RE-FX SOURCE DATA tab to COLUMNS K-R- dedicated to P&L
 
9.	Open S_ALR_87012284 - Financial Statements in FICO line
 
1)	COMPANY CODE- fill in each company code SEPARATELY,
2)	FINANCIAL STATEMENT VERSION- fill 0CTA 
3)	REPORTING PERIODS- fill in range from 1 to the current period,
4)	ALV GRID control MUST be selected- this will create a report easily exportable to MS Excel file,
5)	Click on EXECUTE
10.	Following window will appear:
 
1)	Click on CONTINUE
11.	New window will appear
 
12.	Click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
13.	Copy paste data from second exported file to FICO SOURCE DATA tab to COLUMNS A-G- dedicated to P&L
 

14.	Check if in COLUMNS F-G on tab RIGHT OF USE there are no differences. If no, reconciliation for RoU is done and next steps can be done, if there are a differences, go to next chapter 4.20. Investigate differences and perform corrections

 
15.	Check if in COLUMN F on tab P&L there are no differences. If no, reconciliation for P&L is done and next steps can be done, if there are a differences, go to next chapter 4.20. Investigate differences and perform corrections
 

5.20.	Investigate differences and perform corrections
In case of difference on one of accounts, investigation what caused discrepancies must be performed
1.	Go to FAGLL03 - G/L Account Line Items (New) in FICO
 
 	NOTE:  If  FAGLL03- GENERAL LEDGER -> ACCOUNT -> DISPLAY/CHANGE ITEMS (NEW) is not in use in local line, use  FBL3N - G/L Account Line Items and layout similar to described in procedure below. 
1)	G/L ACCOUNTS – copy paste account number form reconciliation file which causes an issue
COMPANY CODE – fill in according to processed client
2)	Click on EXECUTE or press F8
2.	Investigate positions posted on account to find what causes a difference
 
3.	If roots of difference are in wrongly performed posting of valuation or maturity split, perform reversal double posting or post missing positions.
4.	If roots of difference are in postings done by LFI, for example related to IAS 40, add comment in last column of given reconciliation file
5.21.	 Perform reconciliation in SAP FICO for all P&L accounts reported under specified Tagetik item(s)
Before posting, check in matrix which scenario is related to processed client. 
METRO BG	Rulebook	METRO FR	Rulebook
MAKRO CZ	Rulebook	METRO HR	N/A
METRO DE	N/A Rulebook	METRO HU	Rulebook
MAKRO ES	N/A	METRO IT	N/A
METRO KZ	N/A	METRO TR	N/A
MAKRO NL	N/A	METRO UA	Rulebook
MAKRO PT	Rulebook	VTO	N/A
METRO SK	Rulebook	MAG	N/A
MIB	N/A	Eijsink	N/A
Dish Digital	N/A	PL PropCO 	Rulebook
Metro Digital	N/A	BE PropCo 	Rulebook
Aviludo	N/A	SE JOHBECO	N/A
METRO MARKETS DE	N/A	Metro Logistics	N/A
Pro á Pro ES	N/A	METRO RS	Rulebook

P&L account reconciliation is a process which MUST be performed. The aim of the control is to verify if postings on P&L Clearing accounts posted from SAP RE-FX are the same as with invoices for lease payments. 
1.	Open file GA.4.2.11_IFRS 16 P&L Reconciliation_Common (CTA-Local) Template.xlsx
 
1)	FICO VALUES- tab for source data from SAP FICO
2)	ACCOUNT CHECK- check of balances on accounts which are taken in consideration in this process
3)	CHECK- check of balances on Cost Center level to perform P&L reconciliation for specified Tagetik items
4)	ACCRUALS DATA- tab for result investigation to perform corrections
5)	ACCRUALS POSTING- tab for semi-automatic mass posting of accruals
6)	ACCOUNTS- tab for local account mapping
1.	Open transaction FAGLL03 - G/L ACCOUNT LINE ITEM DISPLAY G/L VIEW
 	NOTE:  If  FAGLL03- GENERAL LEDGER -> ACCOUNT -> DISPLAY/CHANGE ITEMS (NEW) is not in use in local line, use  FBL3N - G/L Account Line Items and layout similar to described in procedure below. 

 
1)	G/L ACCOUNTS – click on MULTIPLY SELECTION.
2)	Paste accounts in SELECT SINGLE VALUES tab from GA.4.2.11_IFRS 16 P&L Reconciliation_Common (CTA-Local) Template.xlsx tab ACCOUNTS column C
3)	Click on EXECUTE or press F8.
4)	COMPANY CODE – fill in according to processed client
5)	Mark ALL ITEMS and fill POSTING DATE – beginning of current FY to last day of closing month.
6)	LAYOUT – /P&L RECON
7)	Click on EXECUTE or press F8
2.	Export generated report and save in temporary location by clicking LIST-> EXPORT-> SPREADSHEET…
 
3.	Copy file ACCRUALS POSTING TEMPLATE from previous month and store it in location for currently closed period.
4.	Copy paste exported file to FICO VALUES tab in ACCRUALS POSTING TEMPLATE.XLSX 
 
5.	Go to ACCOUNT CHECK tab
 
1)	Click right mouse button to REFRESH table 
6.	Check balances on accounts. If balance is not equal to 0 it means on given account here is lack of postings related to invoices of calculation of payments form RE-FX and further investigation needs to be performed. 
 
7.	Go to CHECK tab
 
1)	Click right mouse button to REFRESH table
8.	Further investigation needs to be done to check what caused a difference. How to perform investigation I described in next chapter: 2.22. Investigate differences on P&L accounts
5.22.	Investigate differences on P&L accounts
In case of any incoherence between invoices posted in SAP FI-CO and clearing posted form SAP RE-FX, follow steps below.
1.	Open transaction FAGLL03 - G/L ACCOUNT LINE ITEM DISPLAY G/L VIEW
 	NOTE:  If  FAGLL03- GENERAL LEDGER -> ACCOUNT -> DISPLAY/CHANGE ITEMS (NEW) is not in use in local line, use  FBL3N - G/L Account Line Items and layout similar to described in procedure below. 

 
1)	G/L ACCOUNTS – click on MULTIPLY SELECTION.
2)	Paste accounts in SELECT SINGLE VALUES on which difference occurs
3)	Click on EXECUTE or press F8.
4)	COMPANY CODE – fill in according to processed client
5)	Mark ALL ITEMS and fill POSTING DATE – beginning of current FY to last day of closing month.
6)	LAYOUT – /P&L RECON
7)	Click on EXECUTE or press F8
2.	When report will generate, manually review what caused and discrepancies. 
 
3.	If issue is related to lack on monthly posting of valuation, go to 4.15. Perform posting in SAP FICO and perform missing posting. If issue is related to wrongly performed P&L reconciliation, go back to 4.21. Perform reconciliation in SAP FICO for all P&L accounts reported under specified Tagetik item(s). If difference is relate to missing invoice postings, go to 4.23. Send result of initial reconciliation to LFI and ask for additional information
If posting is incorrect reversal with same posting date should be made. To do so proceed with steps below.
1.	Go to transaction FB08 - Reverse Document in SAP FICO
 
2.	New window will appear
 
1)	DOCUMENT NUMBER – document number of incorrectly posted accrual/provision
COMPANY CODE – fill in code for processed client
FISCAL YEAR – current fiscal year
2)	REVERSAL REASON – 02
POSTING DATE – same as posting date for accrual
POSTING PERIOD – in correspondence with POSTING DATE
3)	Press DISPLAY BEFORE REVERSAL
3.	Below window will pop up:

1)	REVERSAL REASON – 02
2)	POSTING DATE – same as posting date of incorrect accrual/provision
3)	Click REVERSE to confirm and reverse document.
4.	When document is reversed it will be show in below information about posting:
 
5.23.	Send result of initial reconciliation to LFI and ask for additional information
After performing P&L reconciliation, result of that needs to be shared with LFI. In order to do that, follow steps below.
1.	Go to ACCRUALS DATA. In COLUMNS A-F there are formulas. Make sure that all formulas are dragged to end of pasted data.
 
2.	Create separate file from sheet ACCRUALS DATA
3.	Click with the right button of the mouse on the name of the sheet and select  MOVE OR COPY.
 
4.	The following screen will appear.
 
1)	In the field TO BOOK select the option NEW BOOK.
2)	Tick the field CREATE A COPY.
3)	Click OK. The data will be moved to a separate Excel book. 
5.	Click CTRL+S to save the file.
6.	The following screen will appear.
 
1)	Select the directory to save the file in folder for the current period 
2)	Change the file name to ACCRUAL POSTING
3)	Change the file type to EXCEL WORKBOOK (*.XLSX).
4)	Click SAVE
7.	LFI responsible person needs to be contacted. In order to do that use REWORK in MSIT tool. Instruction how to use MSIT can be found under following path: https://metro.sharepoint.com/sites/MSIT2
5.24.	 Post accrual for lease expenses
Before posting, check in matrix which scenario is related to processed client. 
METRO BG	Rulebook	METRO FR	N/A
MAKRO CZ	N/A	METRO HR	N/A
METRO DE	N/A	METRO HU	Rulebook
MAKRO ES	N/A	METRO IT	N/A
METRO KZ	N/A	METRO TR	N/A
MAKRO NL	N/A	METRO UA	Rulebook
MAKRO PT	Rulebook	VTO	N/A
METRO SK	N/A	MAG	N/A
MIB	N/A	Eijsink	N/A
Dish Digital	N/A	PL PropCO 	Rulebook
Metro Digital	N/A	BE PropCo 	Rulebook
Aviludo	N/A	SE JOHBECO	N/A
METRO MARKETS DE	N/A	Metro Logistics	N/A
Pro á Pro ES	N/A	METRO RS	Rulebook

In case of missing posted invoice as a result of investigation after P&L account reconciliation accrual in the amount of missing invoice MUST be booked. In order to do that, follow steps below
1.	Go to tab  ACCRUALS POSTING in the excel file
  
2.	Click with the right button of the mouse on the name of the sheet and select  MOVE OR COPY.
 
3.	The following screen will appear.
 
1)	In the field TO BOOK select the option NEW BOOK.
2)	Tick the field CREATE A COPY.
3)	Click OK. The data will be moved to a separate Excel book. 
4.	Click CTRL+S to save the file.
5.	The following screen will appear.
 
1)	Select the directory to save the file in folder for the current period 
2)	Change the file name
3)	Change the file type to CSV (COMMA DELIMITED) (*.CSV).
4)	Click SAVE
6.	Upload data to FI-CO. Go to transaction YGL01_U2P - Automatic postings with excel upload in SAP FI-CO line
 
7.	Fill in
 
1)	COMPANY CODE- number assigned to processed client
BUSINESS TRANSACTION- ALWAYS 0005
2)	Choose file name by clicking on white box icon on right side
8.	Choose csv file
 
1)	Choose path to file for upload
2)	Click OPEN
9.	After the file is chosen, click EXECUTE
 
10.	Following window will appear, Click SAVE to post a csv file.
 
11.	To add attachment to the posting double click the document number that showed after posting. 
 

5.25.	Inform LFI about accrual posting
After postings are done, inform LFI in accordance with the Communication Rulebook
about it via e-mail, like in the example below together.
 
5.26.	Perform disposal check and posting
After valuation posting in both systems, check for ended contracts needs to be done. To perform check, follow steps below.
METRO BG	4.19. Perform disposal check and posting
METRO FR	Rulebook
MAKRO CZ	4.19. Perform disposal check and posting
METRO HR	N/A
METRO DE	4.19. Perform disposal check and posting
METRO HU	4.19. Perform disposal check and posting

MAKRO ES	4.19. Perform disposal check and posting
METRO IT	4.19. Perform disposal check and posting

METRO KZ	4.19. Perform disposal check and posting
METRO TR	4.19. Perform disposal check and posting

MAKRO NL	4.19. Perform disposal check and posting
METRO UA	4.19. Perform disposal check and posting

MAKRO PT	Rulebook	VTO	4.19. Perform disposal check and posting

METRO SK	4.19. Perform disposal check and posting
MAG	4.19. Perform disposal check and posting

MIB	4.19. Perform disposal check and posting
Eijsink	N/A
Dish Digital	4.19. Perform disposal check and posting
PL PropCO 	Rulebook
Metro Digital	N/A	BE PropCO 	N/A
Aviludo	N/A	SE JOHBECO	N/A
METRO MARKETS DE	N/A	Metro Logistics	N/A
Pro á Pro ES	N/A	METRO RS	N/A
Every quarter contracts that already ended are to be disposed. Values posted on depreciation and acquisition are equal and can be cleared by rebooking between the accounts. Source data are generated from SAP RE-FX HS1 line. Every proposal of disposal should ALWAYS be approved by LFI (following communication rulebook) before posting. 
1.	Open GA.4.2.11_IFRS 16 Contract Disposal_Common (CTA-Local) Template.xlsx
2.	Go to tab DISPOSAL VALUES:
 
1)	Check number of contracts from previous month.
3.	Now go to sheet ARCHIVE:
 
	Make sure contract numbers from previous month are included in the table, if not add them on the end of the list.
4.	Go back to sheet DISPOSAL VALUES and Delete all contract numbers from COLUMN A.
 
5.	Now go to SAP RE-FX to download necessary report:
6.	Start transaction YRE00GLCNCCSUM - DISPLAY OF CUMULATIVE GL AS PER CONTRACT  & COST CENTERS
 
1)	COMPANY CODE – fill in company code for which check is performed.
2)	POSTING DATE – fill in last day of closing month.
3)	G/L – fill in 103* to include all GL accounts starting with these digits.
4)	Click on EXECUTE.
7.	When report is generated:
 
1)	Mark column AMNT. IN LOC. CUR.
2)	Click on TOTALS
8.	 After adding a total row
  
1)	Mark now column CONTRACT NUMBER.
2)	Click on SUBTOTALS.
9.	Report is ready to be exported:
 
1)	Click LIST.
2)	Choose EXPORT.
3)	Click on SPREADSHEET...
10.	Save the report in the same folder as template for check with name SAP RE-FX DISPOSAL VALUES.XLSX.
11.	Open the exported report. Go to disposal template Contract disposal template.XLSX, sheet SAP RE-FX:
  
12.	Starting from cell B2 delete all previous data and paste new one from exported report.
  
1)	Filter YES in column K.
2)	Copy contract numbers from visible yellow cells.
13.	Go to sheet DISPOSAL VALUES:
 
1)	Paste contract numbers in column A.
2)	Formulas in columns B and C calculates part of values to be disposed from SAP RE-FX.
3)	Formulas in columns D and E calculates part of values to be disposed from restatement values.
4)	Columns F and G shows sum of values to be disposed, which should be posted in SAP FICO.
5)	Columns H and I maps SAP RE-FX accounts to specific contract.
14.	Go to REISCNOA - Info System: Objects for Contracts
 
1)	COMPANY CODE- fill in CoCode for processed client
2)	CONTRACT- click on MULTIPLE SELECTIONS
3)	SINGLE VALUES- paste contract numbers from DISPOSAL VALUES tab COLUMN A
4)	Press COPY
5)	Click on EXECUTE
15.	New window will appear
 
1)	Press CHOOSE LAYOUT
2)	Press /COST CENTER
16.	Click on LIST->EXPORT->SPREADSHEET to save file in temporary location
 
17.	Go to PROFIT CENTER tab 
 
1)	Paste data from exported file to COLUMNS A-H
2)	In COLUMN I there are formulas, make sure thy cover pasted data
18.	Next
 
1)	Column J - FICO ACCOUNT APC maps appreciation account from SAP FICO for specific contracts, on which values should be posted.
2)	Column K shows value to be posted on account from column J.
3)	Column L shows transaction type to be used while posting amount on account from column J.
4)	Column M - FICO ACCOUNT DEP maps depreciation account from SAP FICO for specific contracts, on which values should be posted.
5)	Column N shows value to be posted on account from column M.
6)	Column O shows transaction type to be used while posting amount on account from column M.
7)	Column P shows text, which should be used in posting.
19.	Send an email to LFI with proposal of disposal booking file for approval. After approval will be granted proceed with further steps.
 
4.20.2.	MGFS (SAP S/4 HANA) approach
1.	Go to tab  DISPOSAL POSTING in the excel file
  

2.	Data for posting is prepared automatically 
3.	Create separate file from sheet DISPOSAL POSTING:
4.	Click with the right button of the mouse on the name of the sheet and select  MOVE OR COPY.
 
5.	The following screen will appear.
 
1)	In the field TO BOOK select the option NEW BOOK.
2)	Tick the field CREATE A COPY.
3)	Click OK. The data will be moved to a separate Excel book. 
6.	Click CTRL+S to save the file.
7.	The following screen will appear.
 
1)	Select the directory to save the file in folder for the current period 
2)	Change the file name to CONTRACT DISPOSAL
3)	Change the file type to EXCEL WORKBOOK (*.XLSX).
4)	Click SAVE
8.	 Go to SAP FICO (L01 system)
9.	 Go to transaction YCA00_U2P - AUTOMATIC POSTINGS WITH EXCEL UPLOAD
 
1)	Mark DOCUMENTS POST
2)	COMPANY CODE- fill in with CoCode for processed client 
3)	FILE PATH- choose path to saved .xlsx file
4)	Click on TEST RUN
5)	Click on EXECUTE
10.	New window will appear
 
1)	Make sure in MESSAGE LOG that no errors message appears, if not it means that issue with posting occurred and needs to resolved
2)	Click BACK
11.	Next 
 
1)	 Choose FINAL RUN
2)	Click on EXECUTE
12.	New window will appear
 
1)	Make sure that in MESSAGE LOG there is text Document posted successfully
4.20.2.	Common (CTA) approach
1.	Go to tab  DISPOSAL CSV in the excel file
  

2.	Data for posting is prepared automatically 
3.	Create CSV file from sheet DISPOSAL CSV:
4.	Click with the right button of the mouse on the name of the sheet and select  MOVE OR COPY.
 
5.	The following screen will appear.
 
4)	In the field TO BOOK select the option NEW BOOK.
5)	Tick the field CREATE A COPY.
6)	Click OK. The data will be moved to a separate Excel book. 
6.	Click CTRL+S to save the file.
7.	The following screen will appear.
 
5)	Select the directory to save the file in folder for the current period 
6)	Change the file name to CONTRACT DISPOSAL
7)	Change the file type to CSV (COMMA DELIMITED) (*.CSV).
8)	Click SAVE
8.	 Go to SAP FICO
9.	 Go to transaction YGL01_U2P - AUTOMATIC POSTINGS WITH FB01 FOR EXCEL UPLOADS  
  
1)	Type number for processed client in cell for COMPANY CODE
2)	Type 0005 in cell for BUSINESS TRANSACTION
3)	Click on the sign to choose csv to post.
10.	Following window will appear
  
1)	Choose a file to be posted from the path for current month
2)	Click OPEN
11.	 After the file is chosen, click EXECUTE
 
 	NOTE: FILE NAME including full location path should not be longer than 128 characters.
12.	Click SAVE to post a csv file.
 
13.	To add attachment to the posting double click the document number that showed after posting.
 
14.	Following window will appear
 
1)	Choose SERVICES FOR OBJECT 
2)	Select CREATE…
3)	Click CREATE NOTE
15.	In the field TITLE OF NOTE type in POSTING OF IFRS 16 and confirm by pressing ENTER. 
 
5.27.	Group Reporting
After performing all activities related do IFRS 16, as a reporting requirements, notes calculation needs to be done. To perform calculation, follow steps described in separate procedure.
5.28.	Archive documents and close the request
After postings are done, inform LFI according to Communication rulebook- path to be found in 5.4. Communication Rulebook. In order to do that use REWORK in MSIT tool. Instruction how to use MSIT can be found under following path: https://metro.sharepoint.com/sites/MSIT2
In case of MSIT error, e-mail can be use as communication tool. Below, excample of  e-mail to LFI
 

After performing all activities there is need to store all documents.
Documentation for contract maintenance, valuation postings, reconciliation, notes calculation and disposal check store under path according to rulebook for processed client.
 

6.	Appendix
6.1.	Glossary (Including abbreviations)
GSC- Global Solution Center
FA- Fixed Assets
JEMEC- Journal Entry & Month End Closing
LFI- Local Finance Accounting Department
MEC- Month End Closing
FY- Fiscal Year
IFRS 16- International Financial Reporting Standard 16
RE-FX- Flexible Real Estate Management
FI-CO- Financial Accounting & Controlling
M- Monthly
Q- Quarterly
Y- Yearly
FL- Finance Lease
LI- Lease In
LO- Lease Out
EU- European Union
ROU- Right-Of-Use
MTP- Mid-Term Planning
P&L- Profit and Loss
MGFS- Metro Group Finance Solution
CC- Cost Center
CoCode- Company Code
PO- Process Owner
6.2.	  Controls 
6.2.1.	On-going controls
Control name 	How to be documented? 	Error handling	Control details are described in chapter:
Check request for completeness and accuracy	Requests received via MSIT are stored in the MSIT archive solution. All requests are available for later review. After the posting is performed, number of MSIT is added to the asset note. Communication flow is appointed in the Communication Rulebook.	In case GSC FA Clerk spots the error/missing information in the visual check of the request, request is sent back to the originator for clarifying. 	4.3. Check request for completeness and accuracy
Perform simulation of valuation in SAP RE-FX	GSC FA Clerk performs simulation of valuation and checks if calculated values are consistent with standard approach. If any errors occur during the simulation, GSC FA Clerk investigates the reason and solves it.	In case of any doubts GSC FA Clerk contacts with LFI for confirmation. In case of any technical issues contact Service Desk team or Lease Engine team.	4.7 Perform simulation of valuation in SAP RE-FX
Perform reconciliation of SAP RE-FX with SAP FI-CO	After posting are completed GSC FA Clerk creates the reconciliation between data posted in SAP RE-FX and data transferred and posted into SAP FICO. Reports are saved on shared drive for later review.	If there are any inconsistencies GSC Clerk checks if all data was transfer correctly and contact with local finance if differences are result of LFI postings. 	4.13. Perform reconciliation of SAP RE-FX with SAP FI-CO
Perform reconciliation in SAP FICO for all P&L accounts reported under Tagetik #3*52320000	After all posting are completed GSC FA Clerk creates the reconciliation between clearing accounts and posted invoices. Reports are saved on shared drive for later review.	If there are any inconsistencies local finance will be informed, to decide if any corrections need to be performed.	4.15. Perform reconciliation in SAP FICO for all P&L accounts reported under Tagetik #3*52320000
ID Location check for new RE contracts	Before RE contract creation GSC FA Clerk perform check if ID Location stated in request template isn’t already used in SAP RE-FX	If there are any inconsistencies local finance will be informed, to decide if any corrections need to be performed.	4.2.3. ID Location check for new RE contracts

6.2.2.	Detective controls (sample checks)
Control name 	How to be documented? 	Error handling	Control details are described in:
n/a	n/a	n/a	n/a

6.3.	Attachments & Paths
	Path to Procedure Management Portal
https://metro.sharepoint.com/sites/ProcedureManagementPortal/ProceduresNew/Forms/AllItems.aspx
	Path to Rulebook for METRO BG
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B81FCFC17-FB64-4D20-94F5-AFB4A8AE41BA%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20BG.xlsx&action=default&mobileredirect=true
	Path to Rulebook for MAKRO CZ
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B4A4C08E6-7A98-458E-B4FD-A05EC1F2619A%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20CZ.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO DE
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B4EA5E83F-0B0E-4C50-B8CF-5E6E1525F9B5%7D&file=GA.4.2.11_IFRS16_Rulebook%20MDE.xlsx&action=default&mobileredirect=true
	Path to Rulebook for MAKRO ES
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BBB8AC28E-3840-4CEB-A8D7-0EDB3A051D97%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20ES.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO KZ
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BA6FB789D-16C5-43C1-BC88-D8C79FC214FD%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20KZ.xlsx&action=default&mobileredirect=true
	Path to Rulebook for MAKRO NL
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B3009E705-B7BA-4791-9FFD-32C08BD00C0E%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20NL.xlsx&action=default&mobileredirect=true
	Path to Rulebook for MAKRO PT
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B1E52F197-C647-4E86-9DF6-139E95191A2F%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20PT.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO SK
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BDF821DD6-C5B3-49B2-A60B-B3EFF8594A74%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20SK.xlsx&action=default&mobileredirect=true
	Path to Rulebook for MIB
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B738B4CC2-3BA6-4B6E-980A-A43C42F6D560%7D&file=GA.4.2.11_IFRS16_Rulebook%20MIB.xlsx&action=default&mobileredirect=true
	Path to Rulebook for Dish Digital
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B70A6E036-E986-44D4-AFE5-7A256C76E0C1%7D&file=GA.4.2.11_IFRS16_Rulebook%20HOSPITALITY.xlsx&action=default&mobileredirect=true
	Path to Rulebook for Metro Digital
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BC3F94B51-CC9C-480D-B249-55DAED55C995%7D&file=GA.4.2.11_IFRS16_Rulebook%20Metro%20Digital.xlsx&action=default&mobileredirect=true
	Path to Rulebook for Aviludo PT
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B64E401C3-F2F2-4F2A-A134-B7F6523BA4C0%7D&file=GA.4.2.11_IFRS16_Rulebook%20Aviludo%20PT.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO FR
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B49329E81-784E-4101-A072-5BF5FD4A619C%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20FR.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO HR
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B8CCF5AFB-7A76-4AAD-8D29-E2150BE1DA47%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20HR.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO HU
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B974D0CAC-5627-4B97-9A60-C033BFD610AE%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20HU.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO IT
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BAC271176-3302-40CC-918C-6F56D1E4DC56%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20IT.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO TR
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BF8056123-0623-43AA-BC2F-9819A15F219B%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20TR.xlsx&action=default&mobileredirect=true
	Path to Rulebook for METRO UA
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BB7DEB049-32E9-4C68-9F6F-4DAC6CD3725D%7D&file=GA.4.2.11_IFRS16_Rulebook%20MCC%20UA.xlsx&action=default&mobileredirect=true
	Path to Rulebook for ES VTO
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BB1F134C6-F778-4BEF-9FEE-D3C6365F2735%7D&file=GA.4.2.11_IFRS16_Rulebook%20ES%20VTO.xlsx&action=default&mobileredirect=true
	Path to Rulebook for MAG
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BAB47B5AB-CFA2-47BC-9D67-BCAC2B7C7A52%7D&file=GA.4.2.11_IFRS16_Rulebook%20MAG.xlsx&action=default&mobileredirect=true
	Path to Rulebook for Eijsink
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B70A6E036-E986-44D4-AFE5-7A256C76E0C1%7D&file=GA.4.2.11_IFRS16_Rulebook%20HOSPITALITY.xlsx&action=default&mobileredirect=true
	Path to Rulebook for PL PropCO 
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BFF3C6226-A8F9-4D43-AD3D-62AAB8DE74DB%7D&file=GA.4.2.11_IFRS16_Rulebook%20PL%20PROPCO.xlsx&action=default&mobileredirect=true
	Path to Rulebook for BE PropCO 
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7BA74EAD1D-5EE3-4BC7-8CEE-1DB56E886620%7D&file=GA.4.2.11_IFRS16_Rulebook%20BE%20PROPCO.xlsx&action=default&mobileredirect=true
	Path to Rulebook for SE JOHBECO
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/_layouts/15/Doc.aspx?sourcedoc=%7B37A5DDB1-7442-4800-9A15-B7C533FE0DDE%7D&file=GA.4.2.11_IFRS16_Rulebook%20JOHBECO_SE.xlsx&action=default&mobileredirect=true 
	Path to Rulebook for METRO MARKETS
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/ProceduresNew/GA.4.2.11_IFRS16_METRO%20MARKETS%20Rulebook.xlsx.xlsx?d=w8118cea32f54444eadfaa0ad961ada7a&csf=1&web=1&e=brqknE
	Path to Rulebook for ES Pro a Pro
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/ProceduresNew/GA.4.2.11_IFRS16_ES%20Pro%20a%20Pro%20Rulebook.xlsx.xlsx?d=w903144ddd8844035b9a4ae53ced9de90&csf=1&web=1&e=COUHOq
	Path to Rulebook for DE Metro Logistics
https://metro.sharepoint.com/:x:/r/sites/ProcedureManagementPortal/ProceduresNew/GA.4.2.11_IFRS16_METRO%20LOGISTICS%20DE%20Rulebook.xlsx.xlsx?d=wbeb74e0c44c841f88b74d4da42c603fe&csf=1&web=1&e=pNnWd4
	Path to MSIT Tool
https://metro.sharepoint.com/sites/MSIT2 
 
6.4.	Document approval
General information	Approver
Procedure
Version	Date – when PO Approval was initiated	Change description	Procedure Author	Process Owner
1.0	29.09.2023	I version of the procedure
	Anna Bukiel	Fabio De Cenzo
2.0		Procedure adjustment to new Process Map	Anna Bukiel	Fabio De Cenzo
3.0