Documente Academic
Documente Profesional
Documente Cultură
Version Number
1.2
18-Mar-14
Process Owner
Head, HR Operations
Applicability
Objective:
To define policy and procedure for employees who are getting transferred from offshore to onsite, from onsite
to offshore or from onsite to onsite on long term assignment
Scope:
Applicable to all employees on rolls of the organization, who are getting transferred from offshore to onsite,
onsite to offshore or onsite to onsite work locations.
Process Flow
Relieving Manager
Initiate Pre-Separation
with reason as Intl
Transfer in PeopleSoft
Employee
Employee/Relieving
Manager to provide
Transfer details in BPM
post 24 hrs of Pre-Sep
in PeopleSoft
Employee to clear No
dues in SSP
Immigration Team
Fitment SPOC
Upload
Documents
pertaining to
Transfer Country
NO
Manual Position
Check for
Mismatch in Job
profile
BPM Tool
Receiving Manager
Relieving Manager to
Provide the Position
Code in BPM
Position
Matched with
Current Job
Code
Confirm Effective
Date as per the
Law of Land
Record Activation in
PeopleSoft
YES
Receiving Manager/
Employee to confirm the
Travel, Arrival & Reporting
Dates post joining
1.2.
1.2.1.
Roles
Manager
Pre- Separation
The Relieving manager pre-separates the employee on PS with reason code Transfer to International Subsidiary
at least 7 working days prior to travel date.
Transfer Details
This activity will be available for both the Relieving Manager and the Employee. If one of them picks the activity,
it will not reflect in the others work queue. The details to be entered are Client, Project, salary, date of travel,
date of arrival at other shore, date of reporting at other shore, transfer city and receiving manager on BPM Tool.
The additional fields for the offshore to onsite transfer are visa type and whether the employee has been
transferred to the same country before through MphasiS.
Position details
The Relieving Manager gets an activity in BPM to enter the Position Code which would be used for the record
activation of the employee.
For Apps tower, the position code can be created with the guidance of the Position Creation Re-engineering
(PCR) document wherein the Delivery Manager can create the Position in BPM. BPM will generate a 4 digit
Position reference number. Post 4 hrs of providing the Position details in BPM, Managers can view the
PeopleSoft Position Code which will be 7 digits. This 7 digit PS position number should be input in Provide
Position Code activity which will reflect under the Relieving Managers work queue.
For all other towers, the Relieving Manager should create Position Code in PeopleSoft. Please follow the
PeopleSoft Position Creation help card for the same. Once the Manager creates a new position, it flows to the
next level Managers work queue and then to the next level etc. based on the Org Structure. Position Creator
will be able to see the status in PS as Submitted to: (Manager) and once all levels of approvals are done,
Headcount status will be Open and Position Status will reflect as Approved. Each level of Manager will be able
to view the pending Position Approval under their Work List in PeopleSoft. The Position Code will not flow from
PeopleSoft to BPM. Once the Position Code is approved in PeopleSoft, under Provide Position Code details
activity in BPM work queue, just provide the 7 digit Position Number (excluding the prefixed 0) and complete
the activity.
1.2.2.
Employee
Course Name
Reference
comm_26_a03_b1.0 hours
s_enus
Global Travelert
scorm12_adayana_gci
pd_19_a01_bs_enus
41322
Transfer Details
This activity will be available for both the Relieving Manager and the Employee. If one of them picks the activity,
it will not reflect in the others work queue. The employee has to enter the details like Client, Project, date of
travel, date of arrival at the onsite location, date of reporting at the onsite location, transfer city and receiving
manager name on BPM Tool. If the Last Working Date in pre-separation is modified in PS, the employee and the
Relieving Manager will get this activity again and will need to redo the entire process. The additional fields for
the onsite to India transfer are visa type, and whether the employee has been transferred to the same country
before through MphasiS.
LCA
If the transfer country is USA and the visa type is H1B Visa Type, there will be an activity to check whether the
employee has the LCA for the traveling city and the address of workplace. If the visa team confirms that the LCA
city and transfer city do not match, employee gets an activity on the tool. He has to change the traveling city, or
apply for the LCA to the current traveling city or he may have to do both.
International Transfer Process Document |
No Dues Completed
No dues clearance should be completed by the employees on SSP Tool. The clearance for international transfer
should be taken from Admin, Operation, System Support, Training, Library, Visa, Legal, Payroll, HR Ops, Account,
Fixed Assets and Transportation Departments.
1.2.3.
Immigration Team
1.2.4.
Fitment
Salary fitment is finalized (Specific to USA, fitments shall be finalized considering LCA Salary) and uploaded on
BPM Tool. Once this activity is completed,
BPM trigger goes to Employee and Relieving Manager as information that fitment activity is closed.
BPM trigger goes to the Sending Manager with fitment details.
1.2.5.
BPM Tool
1.2.6.
1.2.7.
HD shared services team will conduct the online survey for all employees who have travelled from India to
Onsite post 15 days. The report will be published back to IHR team.
Process Flow
Relieving Manager
Employee/Relieving Manager
to provide Transfer details in
BPM post 24 hrs of Pre-Sep
in PeopleSoft
Relieving Manager to
Provide the Position
Code in BPM
Employee to enroll
for Medical
Insurance, if
applicable
Fitment SPOC
Immigration Team
Employee
Assignment Letter
gets generated
automatically
BPM Tool
Receiving Manager
Manual Position
Check for Mismatch
in Job profile
Position
Matched with
Current Job
Code
Confirm Effective
Date in BPM
Record Activation in
PeopleSoft
YES
Receiving Manager/
Employee to confirm the
Travel, Arrival & Reporting
Dates post joining
2.2.
2.2.1.
Roles
Manager
Pre- Separation
The Relieving manager pre-separates the employee on PS with reason code Transfer to International Subsidiary
at least 7 working days prior to travel date.
Transfer Details
This activity will be available for both the Relieving Manager and the Employee. If one of them picks the activity,
it will not reflect in the others work queue. The details to be entered are Client, Project, salary, date of travel,
date of arrival at other shore, date of reporting at other shore, transfer city and receiving manager on BPM Tool.
The additional fields for the offshore to onsite transfer are visa type and whether the employee has been
transferred to the same country before through MphasiS.
Position details
The Relieving Manager gets an activity in BPM to enter the Position Code which would be used for the record
activation of the employee.
For Apps tower, the position code can be created with the guidance of the Position Creation Re-engineering
(PCR) document wherein the Delivery Manager can create the Position in BPM. BPM will generate a 4 digit
Position reference number. Post 4 hrs of providing the Position details in BPM, Managers can view the
PeopleSoft Position Code which will be 7 digits. This 7 digit PS position number should be input in Provide
Position Code activity which will reflect under the Relieving Managers work queue.
For all other towers, the Relieving Manager should create Position Code in PeopleSoft. Please follow the
PeopleSoft Position Creation help card for the same. Once the Manager creates a new position, it flows to the
next level Managers work queue and then to the next level etc. based on the Org Structure. Position Creator
will be able to see the status in PS as Submitted to: (Manager) and once all levels of approvals are done,
Headcount status will be Open and Position Status will reflect as Approved. Each level of Manager will be able
to view the pending Position Approval under their Work List in PeopleSoft. The Position Code will not flow from
PeopleSoft to BPM. Once the Position Code is approved in PeopleSoft, under Provide Position Code details
activity in BPM work queue, just provide the 7 digit Position Number (excluding the prefixed 0) and complete
the activity.
2.2.2.
Employee
Transfer details
This activity will be available for both the Relieving Manager and the Employee. If one of them picks the activity,
it will not reflect in the others work queue. The employee has to enter the details like Client, Project, date of
travel, date of arrival at the onsite location, date of reporting at the onsite location, transfer city and receiving
manager name on BPM Tool. If the Last Working Date in pre-separation is modified in PS, the employee will get
this activity again and will need to redo the entire process. The additional fields for the onsite to India transfer
are visa type, and whether the employee has been transferred to the same country before through MphasiS.
The employee has to confirm the travel date, arrival date, and reporting date on BPM tool as soon as he reaches
the new location to enable activation of his PeopleSoft records. If delayed, this will have a direct impact on
salary processing and record activation. This activity will be available for both the Receiving Manager and the
Employee. If one of them picks the activity, it will not reflect in the others work queue.
2.2.3.
Immigration Team
Petition handover
Petition handover is completed on BPM Tool post receiving documents from the employee.
2.2.4.
Fitment
Salary fitment is finalized and uploaded on BPM Tool. Once this activity is completed,
BPM trigger goes to Employee and Relieving Manager as information that fitment activity is closed.
BPM trigger goes to the Sending Manager with fitment details.
2.2.5.
BPM Tool
2.2.6.
Process Flow
Relieving Manager
Initiate Pre-Separation
with reason as Intl
Transfer in PeopleSoft
Employee
Employee/Relieving
Manager to provide
Transfer details in BPM
post 24 hrs of Pre-Sep in
PeopleSoft
Immigration Team
Fitment SPOC
Relieving Manager to
Provide the Position
Code in BPM
Upload Documents
pertaining to
Transfer Country
NO
No Dues waived
off manually in
BPM
BPM Tool
Receiving Manager
Manual Position
Check for Mismatch
in Job profile
Position
Matched with
Current Job
Code
Confirm Effective
Date in BPM
Record Activation in
PeopleSoft
YES
Receiving Manager/
Employee to confirm the
Travel, Arrival & Reporting
Dates post joining
3.2.
3.2.1.
Roles
Manager
Pre-Separation
The Relieving manager pre-separates the employee on PS with reason code Transfer to International
Subsidiary at least 7 working days prior to travel date.
Transfer Details
This activity will be available for both the Relieving Manager and the Employee. If one of them picks the activity,
it will not reflect in the others work queue. The details to be entered are Client, Project, date of travel, date of
arrival at other shore, date of reporting at other shore, transfer city and receiving manager on BPM Tool. The
additional fields for the onsite to India transfer are visa type and whether the employee has been transferred to
the same country before through MphasiS.
Position details
The Relieving Manager gets an activity in BPM to enter the Position Code which would be used for the record
activation of the employee.
For Apps tower, the position code can be created with the guidance of the Position Creation Re-engineering
(PCR) document wherein the Delivery Manager can create the Position in BPM. BPM will generate a 4 digit
Position reference number. Post 4 hrs of providing the Position details in BPM, Managers can view the
PeopleSoft Position Code which will be 7 digits. This 7 digit PS position number should be input in Provide
Position Code activity which will reflect under the Relieving Managers work queue.
For all other towers, the Relieving Manager should create Position Code in PeopleSoft. Please follow the
PeopleSoft Position Creation help card for the same. Once the Manager creates a new position, it flows to the
next level Managers work queue and then to the next level etc. based on the Org Structure. Position Creator
will be able to see the status in PS as Submitted to: (Manager) and once all levels of approvals are done,
Headcount status will be Open and Position Status will reflect as Approved. Each level of Manager will be able
to view the pending Position Approval under their Work List in PeopleSoft. The Position Code will not flow from
PeopleSoft to BPM. Once the Position Code is approved in PeopleSoft, under Provide Position Code details
activity in BPM work queue, just provide the 7 digit Position Number (excluding the prefixed 0) and complete
the activity.
10
3.2.2.
Employee
Transfer details
This activity will be available for both the Relieving Manager and the Employee. If one of them picks the activity,
it will not reflect in the others work queue. The employee has to enter the details like Client, Project, date of
travel, date of arrival at the onsite location, date of reporting at the onsite location, transfer city and receiving
manager name on BPM Tool. If the pre-separation date is modified in PS, the employee will get this activity
again and will need to redo the entire process. The additional fields for the onsite to India transfer are visa type,
and whether the employee has been transferred to the same country before through MphasiS.
LCA
If the transfer country is USA and the visa type is H1B Visa Type, there will be an activity to check whether the
employee has the LCA for the traveling city and the address workplace. If the visa team confirms that the LCA
city and transfer city do not match, employee gets an activity on the tool. He has to change the traveling city, or
apply for the LCA to the current traveling city or he may have to do both.
If the employee opts to apply LCA, he gets another activity to enter the LCA reference no. which he gets when
applying for LCA in the Visa Management System (VMS)
11
3.2.3.
Immigration Team
3.2.4.
Fitment
Salary fitment is finalized (Specific to USA, fitments shall be finalized as per LCA) and uploaded on BPM Tool.
Once this activity is completed,
BPM trigger goes to Employee and Relieving Manager as information that fitment activity is closed.
BPM trigger goes to the Sending Manager with fitment details.
3.2.5.
BPM Tool
3.2.6.
12
13
As part of International Transfer process, International Transfer SPOC will update the City/State in PeopleSoft
for the employees who are travelling to US, Canada and Australia if the same is initiated through BPM. For this
updation in PeopleSoft, City/State will be considered as confirmed by the Manager or the Employee while
closing the Transfer activities in BPM.
For any future changes in the City/State of the employee, Manager should update it in Address for Payroll
Processing tab in PeopleSoft. This is applicable for US, Australia & Canada and for the State Transfers in the
same countries as this will be considered for accurate CCA calculation and tax computation. Manager should do
this City/State updation in PeopleSoft within 7 days of the transfer as there will be no backdated updations
considered for payroll
6.1.2.
14
For Onsite to Offshore transfers, employees will not be able to login to LAAS to mark the attendance and
Managers will not be able to regularize the attendance for as many days as the transfer activities are delayed.
For Offshore to Onsite transfers, if the records are not regularized on a timely basis, LAAS will consider the
employee as continuously absent and this will trigger for the AWOI process (Absent With-Out Information)
Supporting Documents:
City-State Update on PeopleSoft Help Card
Mandatory Details on PS_ Onsite Salary Process
PeopleSoft Pre-Separation_ Help Card
International Transfer Process FAQs
PeopleSoft Position Creation Help Card
Version
Number
Date
Sections
Affected
1.0
1-Oct-2011
1.1
1.2
13-Mar2013
18 - Mar 2014
----------------------
15