Skip to main content

We have two companies, each with one site.  A couple employees are transferring from one to another, and we'd like to know if there is a "best practices" we can follow to avoid complications or mistakes along the way.  Specifically:

1) Shop Floor Workbench - Can a single employee, in one of the companies but with access to both, clock in/out of operations for each company?

2) Cost accounting - I believe org assignment for a given employee is the (passive) driver of directing costs to the appropriate GL.  For a single person, migrated from one company to the other, do we have to create a new Employee File for them in the new company?  Should we term the Employee File in the older company?  Or would we want to keep the old employee file active to allow logins to SFW for Company A operations?

Are there any best practices guidelines for this type of use case?

Thanks.

​@okinney : I assume that when employee is transferring from one company to another company, they need to perform clock-in and clock-out operating in new company.

You should create new employee file in new company with correct validity dates and terminate the employment in old company.

The Person ID should remain same in this case, so they may be allowed to access their data in previous company as well based on validity dates.

Thanks

 

Reply


Terms & ConditionsCookie settings