SyncLinx and AccountLinx are applications used to import relevant entity data (employees, locations, cost codes, etc.) to populate ExakTime Connect and export time data for payroll and job costing with compatible payroll/job-costing applications. SyncLinx/AccountLinx are currently designed for use with a single ExakTime Connect account as a one-to-one relationship (i.e., a single copy of SyncLinx/AccountLinx configured for a single ExakTime Connect Account).
In the event that an organization must have multiple ExakTime Connect accounts, such as a holding company with multiple subsidiaries, each with its own ExakTime Connect account, using a single copy of SyncLinx/AccountLinx can be difficult, as it would require setting up the connection for SyncLinx/AccountLinx to the appropriate ExakTime Connect account before use. Failure to properly set up the connection between SyncLinx/AccountLinx and ExakTime Connect can result in cross-contamination of sensitive company data (e.g, incorrect data being imported via SyncLinx or time data being exported into the incorrect accounting/job-costing application).
To mitigate these situations, we highly recommend that each installation and configuration of SyncLinx/AccountLinx be localized to a single computer/environment with a one-to-one setup. If you need to set up SyncLinx/AccountLinx for a second or more ExakTime Connect accounts, it is recommended to set up another copy of SyncLinx/AccountLinx on another computer/environment to lessen the chances of cross-contamination of sensitive company data.
In the event that the incorrect data is imported into ExakTime Connect with SyncLinx, the data can only be deactivated, as entities cannot be deleted. If the incorrect time data is exported from ExakTime Connect to your accounting/job-costing application with AccountLinx, the time data must be deleted from the application, as AccountLinx is unable to "reverse" an export.