PrismHR to ClientSpace Client sync

The PrismHR API import functionality enables initial and ongoing data imports from PrismHR to ClientSpace. The import process uses the following:

  • Scheduled process HRPImportInitialSync.
  • On the Client Master, the field Sync with PrismHR (Import). You must enable the option (select) to import the data.
  • API Configuration > Additional Parameters: ExcludeCompanyFromSync=0: The Company Initial import map IS included in the Sync if the map is active.
  • company_initial import map

For questions about this import configuration, log an Extranet case.

When the scheduled process runs, it:

  • Locates any Client with Sync with PrismHR selected (and a Client Number is present on the Client Master).
  • Scheduled process HRPImportInitialSync creates a Pending import queue record for each INITIAL Employee, Employment and I9 import map for every employee associated with a Client. This ensures that when the PrismHR INITIAL Import runs, the Pending import queue records are processed first and in this order: Employee, Employer, and I9.

Note: ONGOING imports resume after the INITIAL import queue records have completed.

  • For each Client, executes the INITIAL imports for all active INITIAL import maps.
  • When completed, the system clears the Sync with PrismHR option and saves the Client Master using biz logic (HRP pipeline), Biz Logic only.

Why use?

The Sync with PrismHR (Import) option is great for cleaning up any one-off clients that failed to import due to errors during the initial import.