This article covers:
- Overview
- Integration Scenarios
- Additional Resources
- Flow of Data
- User Matching
- Field Mapping
- Employee Data
- Employee Leave Balances
- Payslips
Overview
Humanforce is a unified HCM suite designed for front-line and flexible workforces. Combining Humanforce Workforce Management, intelliHR and Datapay, together in the aim to elevate employee experience and simplify compliance. Humanforce is now offering customized integration among intelliHR, Humanforce Workforce Management and Datapay which opens up a new door of possibilities in the integration sector.
The flow of data between the three systems preferences intelliHR (iHR-in short) as the source of truth for core employee lifecycle data, while Workforce Management (WFM-in short) manages timesheets and leave, and Datapay produces payslips at the end of pay runs.
✅ intelliHR > WFM - New & Updated Employees
✅ intelliHR > Datapay - New & Updated Employees
✅ WFM > Datapay - Timesheets & Leave
✅ Datapay > WFM - Payslips
Integration Scenarios
There are a number of integration scenarios to account for.
-
Datapay NZ↔️Workforce Management
- Datapay AU↔️Workforce Management
-
Datapay NZ ↔️intelliHR↔️Workforce Management
-
Datapay AU ↔️intelliHR↔️Workforce Management
- Datapay NZ ↔️intelliHR
- Datapay AU ↔️intelliHR
Additional Resources
Flow of Data
intelliHR > WFM
- When a new job (new hire) is created in intelliHR, create new employee in WFM.
- When a job is updated in intelliHR, update employee in WFM.
- When a person is updated in intelliHR, update employee in WFM.
intelliHR > Datapay
-
When a new job (new hire) is created in intelliHR, create new employee in DataPay.
-
then the Datapay employee id is sent to WFM*
-
- When a job is updated in intelliHR, update employee in DataPay.
- When a person is updated in intelliHR, update employee in DataPay.
*assuming employee needs to be pushed to WFM (need to validate criteria for when an employee exists in WFM and Datapay)
💡Terminations are not automated via the Datapay API as intelliHR does not store the relevant information, e.g. Leave Types, Last Pay Run Date etc.
WFM > Datapay
- Timesheets are clocked, authorised and processed against the employee's assigned award profile in WFM. Then award-interpreted timesheet data, leave taken, and override rates are synced to Datapay NZ.
Datapay > WFM
- After payroll finalisation leave balances are updated in Datapay and can be synced to WFM.
Note, in WFM all leave is displayed in hours. -
After payroll finalisation payslips are available in Datapay and can be synced to WFM.
User Matching
3 fields are used across the three products to match employees, though only field, the employee number, is used within the UI of all three systems for matching and troubleshooting.
Employee Number
intelliHR | WFM | Datapay |
Employee Number |
Payroll Code |
Code |
intelliHR person Id
intelliHR | WFM | Datapay |
Id |
iHRGUID |
NOT REQUIRED |
Datapay employee Id
intelliHR | WFM | Datapay |
Custom Field: Datapay Id |
External Id |
Id |
Field Mapping
The following table contains recommended mappings when using all the three products (intelliHR + Humanforce Workforce Management + Datapay) together in Humanforce suite. For further details on all possible mappings, please refer to the source articles.
Employee Data
-
DATE EFFECTIVE
: the start date for new employees, update start date for updates. Where a field is not date effective in intelliHR, the date the change is made is used for updates. -
NOT REQUIRED
: indicates a field is not integrated to the specified system (does not necessarily mean that system does not contain an equivalent field). -
AU
: indicates a field relating to Datapay Australia. -
NZ
: indicates a field relating to Datapay New Zealand.
💡Note: the intelliHR > WFM fields are configurable on the integration configuration screen within Humanforce WFM (Management > Advanced > Integration Central).
Note: the intelliHR > Datapay fields are configurable by the integrations team during integration implementation. Employees are always created in Datapay unfinalised. Note that for managed payroll and client managed payroll this may be a consideration. More fields may be added in the future.
intelliHR Field | WFM Field |
DataPay Field | Notes |
Employee Number |
Payroll Code |
Code AU NZ
|
These codes match in the UI across all three systems allowing a consistent code that identifies an employee to be tracked in both systems. |
Person Custom Field: Datapay Id |
External Id |
Employee Id |
Datapay Employee Id is generated on employee creation from iHR, then passed back into WFM “External Id” for employee matching and back into iHR custom field “Datapay Id” for troubleshooting. |
Gender | Gender | Gender* AU NZ
|
Gender Name must match between systems. |
Title | Title | Title AU NZ
|
|
First Name |
First Name |
First Name AU NZ
|
|
Middle Name |
Middle Name |
NOT REQUIRED AU NZ
|
|
Last Name |
Last Name |
Last Name |
|
Preferred Name |
Short Name |
Known As |
Employee’s name as it will appear in the rostering screen in WFM and part of the employee’s display name in intelliHR. |
Date of Birth |
Birth Date |
Birth Date AU NZ
|
|
Primary Email Address | Email AU NZ
|
||
Primary Phone Number | NOT REQUIRED |
Work Phone AU NZ DATE EFFECTIVE
|
|
Home Address: Street |
NOT REQUIRED |
Street
|
|
Home Address: Suburb |
NOT REQUIRED |
Suburb |
|
Home Address: Post Code |
NOT REQUIRED |
Postal Code
|
|
Home Address: Post Code | NOT REQUIRED |
NOT REQUIRED NZ
|
|
Home Address: State | NOT REQUIRED |
Postal State |
|
Home Address: State | NOT REQUIRED |
City |
|
Home Address: Country | NOT REQUIRED |
Country
|
|
Start Date |
Employment Start Date |
Start Date |
The start date for new employees, update start date for updates. Where a field is not date effective in intelliHR, the date the change is made is used for updates. |
Company End Date |
Termination Date |
NOT REQUIRED |
Company end date of the primary Job. Concurrent Job not considered. Cancelling a company end date in iHR or adding a new primary job to an employee with a company end date will reactivate the employee in WFM, only on triggered integration. |
Custom Field: Pay Group
|
|
Pay Group |
Pay Group is matched by name within the relevant company. |
Business Entity
|
|
Company Id |
The ID of the company that the employee belongs to. Retrieved by matching |
Business Unit
|
Default Department |
Home Cost Box |
Homecost boxes are searched for a matching Business Unit name or by code. Must be the most-child homecost box of a homecost box tree. |
Position Title
|
Job Title |
Occupation |
|
Supervisor Person
|
|
Manager |
When updating this field, it will always be effective from today's date. This field is read-only for companies using the position-based reporting structure. |
Pay Grade
|
|
Pay Point |
|
Location
|
Default Location |
Region |
|
Work Class
|
|
Tenure |
|
Remuneration Schedule: Base Hourly Rate
|
|
Pay Rate |
Pay Rate sent from iHR to Datapay when remuneration type is set to Hourly Rate. |
Remuneration Schedule: Base Annual Salary
|
|
Pay Rate |
Pay Rate sent from iHR to Datapay when remuneration type is set to Annual Salary. |
Remuneration Schedule: Type |
|
Pay Rate Option |
Pay Rate Option determines how someone is paid in DataPay. |
Remuneration Schedule: Type |
|
Pay Setup |
Determines how an employee is paid, ennums change per company. Can be mapped from an intelliHR custom field instead. |
Person Custom Field: Ird Number |
|
Ird Number
|
Defaulted to 000-000-000. |
Person Custom Field: Tax Code |
|
Tax Code
|
Defaulted to M. |
Person Custom Field: Bank BSB“-”Bank Account Number |
|
Bank Account Number
|
In New Zealand, a bank account number is typically formatted in a three-part structure: XX-XXXX-XXXXXXX-XX: The first two digits (XX) represent the bank code. The second four digits (XXXX) represent the branch code. The next seven digits (XXXXXXX) are the actual account number. The final two digits (XX) are the suffix which identifies the specific account type or sub-account. |
Person Custom Field: Name On Bank Account |
|
Account Holder Name |
|
* Gender is mapped across via a lookup table that typically transforms values from intelliHR to DataPay based on the below:
intelliHR Gender Value | DataPay Gender Value |
Undisclosed | Unknown |
Male | Male |
Female | Female |
Non-Binary | Gender Diverse |
Other | Unknown |
Fall Back Value | Unknown |
Employee Leave Balances
-
Datapay NZ → Humanforce WFM
- For detailed mapping refer to the ⭧Datapay NZ: Native integration with Humanforce WFM article.
Payslips
-
Datapay NZ → Humanforce WFM
- For detailed mapping refer to the ⭧Datapay NZ: Native integration with Humanforce WFM article.
💡Tip: For information on how to connect and configure your DataPay custom integration; please contact your friendly Customer Success representative; or email straight through to our Integrations team for more information at integrations@intellihr.com