TASS is a payroll platform favoured by primary schools and high schools in Australia due to its simplicity. TASS is ideal for these schools as it allows HR records to be managed alongside student and parent records.
intelliHR has built a custom integration layer that is available for users of TASS. The integration will take new hires in intelliHR and send them to TASS, creating a new employee in TASS in the process.
This article covers:
- What the integration will do
- What data can be mapped from intelliHR to TASS?
- Connection & Set-up Costs
What will it do?
- When a person is hired in intelliHR, person and job information is automatically sent to TASS.
- A new employee is subsequently created in TASS based on the information sent across from intelliHR.
- When a person or job is updated in intelliHR, the employee is updated in TASS.
Common Considerations:
-
In order to build this integration you will need to have the following API access with TASS;
-
API ‘employee HR’ licence (required for the person & Job Create)
-
API 14 ‘data upload utility’ licence (required for the Person/Job update)
-
- Changes in TASS to employee records do not flow back to intelliHR.
- The integration does not automate terminations.
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 TASS environment.
3. TASS will consume the fields sent across and store these values against a newly created employee in TASS.
Data Mapping
Below is a list of employee (from the intelliHR profile tab) fields that can be mapped across from intelliHR to TASS. Where "Custom Field" is stipulated as the intelliHR field, a custom field will need to be created within intelliHR. For more information on how to do this; refer to our Custom Field article.
| intelliHR Field | TASS Field |
| Title | Salutation |
| Last Name | Surname |
| First Name; Middle Names | Given Names |
| Preferred Name | Preferred Name |
| First Name; Last Name | Initials |
| Gender | Sex |
| Date of Birth | Birth Date |
| Street | Address 1 |
| Suburb | City |
| State | State |
| Postcode | Postcode |
| Employee Number | Employee Code |
| Primary Email Address | |
| Primary Phone Number (Can be mapped to any of the associated TASS fields listed). | Phone (H) Phone (W) Mobile Phone |
| Custom Fields |
Marital Status Drivers License etc. |
|
Emergency Contact Name Emergency Contact Relationship |
Next of Kin Name Next of Kin Relationship |
Below is a list of job (from the intelliHR job tab) fields that can be mapped across from intelliHR to TASS.
| intelliHR Field | TASS Field |
| Work Type | Status |
| Company Start Date | Start Date |
| Position Title | Position Title |
| Supervisor (Employee Number) | Supervisor Code |
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 TASS admin settings and confirmation of tenant region.
- Field Mapping: As per the section above; ensuring all fields are mapped correctly between intelliHR and TASS.
- 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.