So I am aware you cannot change the subsidiary of ...
# general
j
So I am aware you cannot change the subsidiary of an employee who has transactions associated with them already. We recently moved onto One World, and our previously existing subsidiary (let’s call that “original co” is under a parent subsidiary (let’s call this “new parent co”). All historical employees & transactions records are under “original co”. We have some employees (with old expense reports) who should really live under “new parent co”. What’s the best method to resolve this, given that we have lots of other data associated with their internal id (e.g. custom records, communications, etc)? Making a brand new employee record for each doesn’t seem at all practical or useful.
t
create a new (archive) employee in oldco and attach the transactions to that record, then move the original record to new parent co
j
if I try to change the employee for an expense report, it decouples it from the associated payment record.
s
When dealing with a similar issue with customers and vendors, we did some tricks with merging duplicate records. I don't know if you can merge duplicate employees?
t
@jen yes but those can be re-associated I think
j
@Tristan Day I don’t see a way to link it back up.
t
Can you not apply the payment to the ER as if you were doing a standard reconciliation?
j
the payment is not editable
This liability payment cannot be edited while it has an Automated Clearing House transmission in process.</TD></TR><TR><TD class=text>&nbsp;</TD></TR><TR><TD class=text>&nbsp;To view the status of payments with ACH transmissions, go to Transactions > View ACH Vendor Payments Status.
nice formatting, netsuite
s
I had that problem once needed to create a brand new sub with new reporting currency. Had do replicate all employees to new sub, then added an * before the employee name in the old sub (eventually inactivated). Added a custom field in employee record to link old and new sub employee record. Eventually all the transactions (GL impacting) were migrated to new sub via JE. It was tricky and had to be quite careful.
127 Views