Datacom's DataPay platform is a cloud-based enterprise payroll and human resource software solution. It manages confidential employee personal and financial data, and is always updated to follow the latest regulations, legislation and highest security levels of confidential information.
intelliHR has built a custom integration layer that is available for users of DataPay. This is available for both users of DataPay AU and DataPay NZ. The integration will take new hires in intelliHR and send them to DataPay. This integration also sends any updates made to a person or job record on intelliHR and makes the associated updates in DataPay.
This article covers:
- What the integration will do
- What data can be mapped from intelliHR to DataPay?
- Connection & Set-up Costs
What will it do?
✅ When a new job (new hire) is created in intelliHR, a new user is created in DataPay.
✅ When a job is updated in intelliHR, the associated user is updated in DataPay. Optionally, allow temporary Changes. See field mapping for more details.
✅ When a person is updated in intelliHR, the associated user is updated in DataPay.
Common Considerations:
- The integration won't handle rehires. This needs to be resolved via business process (i.e. manually or other workaround).
- When a job is ended in intelliHR, termination of the associated user does NOT occur in DataPay.
- DataPay changes will not flow back into intelliHR.
-
Datapay’s API does not natively allow temporary changes. However, the integration can optionally end date a temporary change, and re-instate the information on the record prior to the temporary change. See field mapping for a list of applicable fields.
Flow of Events
1. A HR administrator will create a new employee and new job in intelliHR upon the hiring of a new staff member. (Alternatively, a connected ATS system will pass through the new candidate details into intelliHR and create a new person and job in intelliHR in the process).
2. The integration will find all of the necessary and included person and job fields in intelliHR (stipulated in the Data Mapping section) and send the values of these fields to the connected DataPay environment.
3. Before performing step 4, the integration will take the business unit code from intelliHR and find a matching homecost box ID in DataPay, and in turn return the company ID that the employee should belong to in DataPay.
4. DataPay will consume the fields sent across and store these values against a newly created user in DataPay.
5. The integration will continue to "listen" for updates to any of the fields stipulated below in the Data Mapping section. If it hears a change in intelliHR it will consume the new data value and place it into the according DataPay user field.
Data Mapping
Below is a list of employee (from the intelliHR profile tab) fields that can be mapped across from intelliHR to DataPay.
| intelliHR Field | DataPay Field |
| Employee Number | Code |
| Gender | Gender* |
| Title | Title |
| First Name | First Name |
| Last Name | Surname |
| Date of Birth | Birth Date |
| Primary Email Address | Email Address |
| Primary Phone Number | Mobile Phone |
| Street | Street |
| Suburb | Suburb |
| City | City |
* 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 |
Below is a list of job & remuneration (from the intelliHR job tab) fields that can be mapped across from intelliHR to DataPay.
| intelliHR Field | DataPay Field |
| Business Entity | Company ID |
| Company Start Date | Start Date |
| Business Unit | Home Cost Box ID |
| Position Title | Occupation |
| Supervisor Job ID | Manager ID** |
| Pay Grade | Pay Point |
| Location | Region |
| Work Class | Tenure |
| Base Annual Salary / Base Hourly Rate | Pay Rate |
| Remuneration Type | Pay Ration Option* Pay Setup |
* The below stipulates the DataPay Pay Rate Option that is defined via the Remuneration Type stipulated in intelliHR:
- Annual Salary (intelliHR) → FTE (DataPay)
- Hourly Rate (intelliHR) → Basic Hourly Rate (DataPay)
** Manager ID updates are not date effective and cannot be configured as apart of a temporary change / update.
Connection & Set-up Costs
Steps required to connect the integration and the costs associated are quoted on a case-by-case basis as this integration is facilitated by an intelliHR custom integration layer.
intelliHR will provide a quote that factors in some of the following activities to ensure that the integration is sustainable for each client.
- Authentication Testing: Requires the client to retrieve an API key from within DataPay admin settings and confirmation of tenant region.
- Field Mapping: As per the section above; ensuring all fields are mapped correctly between intelliHR and DataPay.
- Pre-Deployment & Post-Deployment Consultations: This includes testing the integration with the client to identify use cases and field mapping requirements.
- Deployment: The end-to-end building of the complete integration/automation process.
- Housing & Maintenance: Which party will be hosting the integration (intelliHR vs. Client)? What effort will be required to troubleshoot and maintain the integration long-term?