abstract swish line in gradient colouring from pink to blue on a dark blue background

Integrations - External payroll

Data mapping/setup

Employees will be mapped using personal reference number in both applications. If multiple payrolls are being used, it would be sensible to set up a custom card in People First against the person to hold the payroll name.

Any People First custom cards used in the integration need to have the integration option enabled so event stream events for those custom cards get sent out.

 

Potential data that needs to go into external application

At some point, the People First data required by the payroll application to process the payroll, needs to be onboarded into the payroll application.

This data will/could include the following:

Person Data

  • Person Information
  • Bank Details
  • Drivers Details
  • Contact Details
  • Address
  • Custom Cards (Created to support any additional data that People First does not hold that’s mandatory in the system)

Employment Data

  • Job Information Card
  • Terms & Conditions
  • Schemes and Benefits
  • Hours and Basis
  • Working Pattern
  • Salary
  • Custom Cards (Created to support any additional data that People First does not hold that’s mandatory in the system)

Absence Data

  • Start Date
  • End Date
  • Start Date Type
  • End Date Type
  • Absence Type
  • Absence Reason
  • Duration
  • Supplementary Fields

The interface will go live at some date. We only need a snapshot of the data above for the relevant employees at that date to go into the payroll application.

There are several ways of obtaining and loading this data into the payroll application which will be listed here

A table showing methods of loading data into payroll and associated pros and cons.

 

MethodAdvantagesDisadvantages
PF Event Stream APIsSame method as going to use for BAU changes

Need to process events over all time yet only need data at go live date.

Not all required data covered by event stream, ie. S&Bs, driver details

PF OData APIs

Returns current data which is closer to what we need for onboarding.

Can make API calls per employee to make it more granu

Not all required data covered by OData APIs, ie. S&Bs, bank accounts.
PF ExportsNo development work required.Needs to be manually done by PF user with access.

 

The recommended option for onboarding depends on many things – the number of employees, the technical level of the developers/integrators, the capabilities of the payroll application etc.

If the payroll application has a file-based onboarding process, then it may be simple to just use People First exports and then manipulate the outputs into files for loading into the payroll application for the onboarding.

Looking for something specific?