The details in this article may be updated as the integration continues to evolve. To receive notifications about any changes or enhancements, click the Follow button at the top left of this article.
When Humanforce HR is integrated with Humanforce Workforce Management (WFM), key employee data can sync automatically across systems, reducing manual admin, improving data accuracy, and supporting compliance.
This article provides a detailed reference for all supported fields in the integration, including how they map between HR and WFM, the direction of data flow, and whether special configuration is required. It’s designed to help teams confidently configure, verify, and maintain their integration setup.
Use this guide to:
- Understand what data flows between Humanforce HR and WFM
- Confirm which fields are supported and how they map
- Check data ownership and configuration notes for each mapped field
Using the full Humanforce HCM Suite? If your organisation uses Humanforce HR, WFM, and Payroll, refer to the Humanforce HCM Suite integration overview for the recommended setup and field mapping across the full suite. The suite-level integration includes specific configuration requirements and forward-only data flows to support data consistency across all systems.
Integration flows
The integration between Humanforce HR and WFM uses a combination of real-time webhooks and scheduled synchronisation to keep employee data aligned across systems. This section outlines how data is transferred, when syncs occur, and what mechanisms control each flow.
HR → WFM
Changes made in Humanforce HR act as the primary trigger for data synchronisation. These updates flow to WFM through the following event-driven webhooks:
- Job Created Webhook: Triggered when an employee’s primary job is created in HR. This event initiates the creation of a new employee record in WFM and includes synced personal details, job information, and active qualifications.
- Person Updated Webhook: Triggered when an employee’s People or Job record is updated in HR. This includes changes to name, contact information, employment terms, or qualifications.
- Job Onboarding Payroll Completed: Triggered when an employee has updated their bank, tax or superannuation data in HR
- Qualification Instance Updated Webhook: Syncs qualification records from HR to WFM when a qualification is added, updated, or renewed—limited to records in a non-draft state with valid dates.
- Job End Date Finalised Webhook: When a job is formally ended in HR, this webhook sends the termination date to WFM.
- Person Deleted Webhook: Marks the employee as terminated in WFM when their HR profile is deleted.
All HR → WFM synchronisations follow the import mappings configured in Integration Central.
WFM → HR
For organisations with two-way sync enabled, WFM can also push updates into HR. These updates are triggered when records are saved in either the Employee Management or Change Approvals screens in WFM. The fields and rules for export are managed in the WFM → HR mapping setup within Integration Central.
This capability is currently in 🔐 Early Access. Contact Humanforce Support to enable this for your organisation.
Bulk synchronisation
In addition to real-time syncs, WFM supports bulk employee data synchronisation. This can be scheduled or manually triggered from WFM to import a complete dataset from HR, including:
- Current and historical job records
- Employee personal details
- Qualifications
- Termination dates
Bulk sync is recommended during initial implementation, after significant data changes in HR, or when you need to validate records across systems.
Icon Reference Table
| Icon | Meaning |
|---|---|
| 🔄 Alternate mapping available | Additional mapping options are available to support different setups. |
| ⚠️ Critical configuration note | Highlights behaviour or setup steps that may affect data syncing. |
| 🔷 Custom field required | Field must be created as a custom field before it can be mapped. |
| 📝 Default config possible | Default values are used when the source field in HR is empty. Defaults won’t apply if the field fails to map or returns no match. |
| 🔐 Early access | Feature is available for testing but not yet fully released. Opt-in required. |
| 🟡 Hidden field | Not visible in the UI but can be included in syncs via integration. |
| 🔗 Linked to auxiliary data | Value comes from a dropdown list that can sync via auxiliary data. |
| * Mandatory field | This field must have a value for the employee to be complete in the system. |
| ❌ Not integrated | Field is not currently supported for sync between systems. |
Auxiliary Data
Manually Maintain Auxiliary Data for Accuracy
Certain fields must be manually maintained in both Humanforce HR and WFM as they do not automatically sync. These include:
- Pay rates
- Gender
- Title
- Visa type
Regular updates to these fields help maintain consistency and prevent errors in reporting, compliance, and payroll processing.
Note that the HR Person field names need to be spelled identical to WFM field names. E.g. Corresponding field for "Clock-In Settings" in WFM needs to be setup exactly as "Clock-In Settings" in HR for it to appear in the options list in Integrations Central. It also supports Job and Job Remuneration Custom fields and these do not need to have field names matched.
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
| 🔷Pay Company | Pay Company | WFM → HR | |
| 🔷Employment Type | Employment Type | WFM → HR | |
| 🔷Default Location | Default Location | WFM → HR | |
| 🔷Default Department | Default Department | WFM → HR | |
| 🔷Default Role | Default Role | WFM → HR | |
| 🔷Default Area | Default Area | WFM → HR | |
| 🔷Default Award Profile | Default Award Profile | WFM → HR | |
|
❌Mapping not recommended 🔄Person & Job custom fields |
Period | WFM → HR | |
| 🔷Access Level | Access Level | WFM → HR | |
| 🔷Clock-In Settings | Clock-In Settings | WFM → HR | |
| Qualification Library Items | Qualifications | HR → WFM |
⚠️Review and finalise qualification settings in WFM after integration. Only qualification creations and renewals are processed (deletions are not supported). |
Employee Details
Matching and data validation
It is very important to note that the employee record between HR and WFM are linked using the Person UUID from HR. This linkage happens when an employee is successfully created in WFM for the first time. Thereafter, all updates published from HR for that Person UUID will be applied to the corresponding WFM employee.
In a scenario where the Person UUID cannot be found, the integration will attempt to find a similar employee in WFM using the matching criteria (mentioned in the employee details section for Person UUID) and if unsuccessful, will create a new employee.
This duplication scenario is a common occurrence in new rollouts of integration where WFM was connected with a UAT HR and then replaced with a Production HR. The Person UUID for the same physical employee between UAT and Production will be different hence a duplicate employee will created when moving from UAT to Production.
To avoid this, we recommend both WFM and HR to be in UAT. Further, we also recommend not using the actual employee records for testing, rather use mock employees that can be deactivated later.
Employment
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
| 🟡[Person UUID] | 🟡[intelliHRID] | HR → WFM |
⚠️Matches first on internal HR GUID. If unavailable, falls back to email, DOB, and first name & last name. A new employee record is created if no match is found. Note that the Person UUID is not visible on screen and is the key linkage between HR and WFM employees. |
|
Profile.Personal Information. Humanforce HR ID* 🔄Employee Number |
Personal Details.Personal. Employee Code* |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Personal Information. Humanforce HR ID* 🔄Employee Number (If using unique payroll codes) |
Employment.Employment. Payroll Code* |
HR → WFM WFM → HR |
Character limit: 100 |
|
🔷Jobs.Additional Details. Pay Company 🔄Jobs Fields |
Employment.Employment. 🔗Pay Company* |
HR → WFM | |
|
🔷Jobs.Additional Details. Employment Type 🔄Jobs Fields |
Employment.Employment. 🔗📝Employment Type* |
HR → WFM | |
|
❌Mapping not recommended 🔄Jobs Fields |
Employment.Employment. 🔗📝Default Period* |
HR → WFM WFM → HR |
|
|
🔷Jobs.Additional Details. Access Level* 🔄Jobs Fields |
Employment.Employment. 🔗📝Access Level* |
HR → WFM | |
|
🔷Jobs.Additional Details. Clock-in Settings* 🔄Jobs Fields |
Employment.Employment. 🔗📝Clock-in Settings* |
HR → WFM | |
|
🔐Jobs.Remuneration Schedule. Hours Per Cycle* 🔄Jobs fields |
Employment.Employment. Max Roster Hours |
HR → WFM |
⚠️This field must be mapped from the primary job in HR. Mapping from any other source will cause sync errors. Effective Date in WFM is set based on the Scope for Roster Hours (Min & Max) configuration. Character limit: 50 |
|
🔐🔷Jobs.Additional Details. Default Award Profile 🔄Jobs Remuneration |
Location,Department, Roles.Roles and Profiles. 🔗📝Default Award Profile* |
HR → WFM | ⚠️This field must be mapped from the primary job in HR. Mapping from any other source will cause sync errors. |
|
🔐Jobs.Position Arrangements. Pay Grade* |
Location, Department, Roles. Roles and Profiles. Default Pay Rate |
HR → WFM |
⚠️This field must be mapped from the primary job in HR. Mapping from any other source will cause sync errors. Matches based on Rate Name. All pay grades in HR should be mapped an exact match option in WFM. |
|
🔐Jobs.Remuneration Schedule. Base Hourly Rate* |
Location, Department, Roles. Roles and Profiles. Default Rate Override |
HR → WFM | ⚠️This field must be mapped from the primary job in HR. Mapping from any other source will cause sync errors. |
|
Job.Position Arrangements. Position Start Date* (primary job only) / Job Update Effective From (job updates) |
Location, Department, Roles. Roles and Profiles. Date Effective* |
HR → WFM | dd-mm-yyyy |
|
🔐Jobs.Remuneration Schedule. Hours Per Cycle* 🔄Jobs Fields |
Employment.Employment. Min Roster Hours |
HR → WFM |
⚠️This field must be mapped from the primary job in HR. Mapping from any other source will cause sync errors. Effective Date in WFM is set based on the Scope for Roster Hours (Min & Max) configuration. Character limit: 50 |
|
Jobs.Job Details. Company Start Date* (primary job only) |
Employment.Employment. Start Date* |
HR → WFM WFM → HR |
dd-mm-yyyy |
|
Jobs.Job Details. Company End Date (primary job only) |
Employment.Employment. Termination Date |
HR → WFM WFM → HR |
⚠️Reactivation occurs when primary job updates or termination cancellations are synced from HR. Always process terminations in HR. This will sync the termination date to WFM. Payroll terminations must still be handled manually. Employees terminated will not be updated in WFM from HR if their termination date is beyond the days configured in the Post-Termination Sync Duration configuration. dd-mm-yyyy |
|
Jobs.Position Details. Position Title* |
Employment.Employment. Job Title |
HR → WFM WFM → HR |
Character limit: 50 |
| ❌ |
Employment.Employment. Include in payroll export* |
HR → WFM | ⚠️Controls sync to payroll system and timesheet export. Defaults to True. |
| ❌ |
Employment.Employment. Verification Mode* |
HR → WFM | Set based on WFM System-Wide setting. |
Location, Department, Role
Managing LDRs and Secondary Roles
Only the primary job from Humanforce HR syncs to WFM. If an employee has more than one job (e.g. works multiple roles or locations), any non-primary (secondary) roles must be set up and maintained directly in WFM, these are not transferred through the integration.
Likewise, the employee’s Default Location, Department, and Role (LDR) for the primary job should be maintained in HR. If an employee works across multiple LDRs, you’ll need to manage these additional structures in WFM.
⚠️ The integration doesn’t support multi-contract setups (where a single employee holds multiple contracted jobs). If this applies to your business, speak to your Humanforce implementation team about alternative solutions.
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
🔷 Jobs.Additional Details. Default Location 🔄Jobs Native Fields |
Employment.Employment. 🔗📝Default Location*
|
HR → WFM | |
|
🔷 Jobs.Additional Details. Default Department 🔄Jobs Native Fields |
Employment.Employment. 🔗📝Default Department* |
HR → WFM | |
|
🔷Jobs.Additional Details. Default Role 🔄Jobs Native Fields |
Employment.Employment. 🔗📝Default Role* |
HR → WFM | |
|
🔷Jobs.Additional Details. Default Area 🔄Jobs Native Fields |
Employment.Employment. 🔗📝Default Area |
HR → WFM | Character limit: 50 |
Bank and Tax Information
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
🔷Profile.Payroll. Bank Name 🔄Jobs Fields |
Personal Details.Bank Account. Bank |
HR → WFM WFM → HR |
Character limit: 50 |
|
🔷Profile.Payroll. Bank BSB 🔄Jobs Fields |
Personal Details.Bank Account. BSB |
HR → WFM WFM → HR |
Character limit: 20 |
|
🔷Profile.Payroll. Bank State 🔄Jobs Fields |
Personal Details.Bank Account. Bank State |
HR → WFM WFM → HR |
Character limit: 50 |
|
🔷Profile.Payroll. Bank Account Name 🔄Jobs Fields |
Personal Details.Bank Account. Account Name |
HR → WFM WFM → HR |
Character limit: 50 |
|
🔷Profile.Payroll. Bank Account Number 🔄Jobs Fields |
Personal Details.Bank Account. Account No |
HR → WFM WFM → HR |
Character limit: 50 |
|
🔷Profile.Payroll. Bank Account Suffix 🔄Jobs Fields |
Personal Details.Bank Account. Suffix |
HR → WFM WFM → HR |
⚠️Relevant for New Zealand only. Character limit: 50 |
|
🔷Profile.Payroll. Tax File Number 🔄Jobs Fields |
Employment.Employment. Tax Id |
HR → WFM WFM → HR |
Character limit: 50 |
Personal Information
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
Profile.Phone Number. Primary Phone Number* 🔄Personal Phone Number |
Personal Details.Contact. Mobile |
HR → WFM WFM → HR |
Character limit: 20 |
|
Profile.Phone Number. Personal Phone Number* 🔄Primary Phone Number |
Personal Details.Contact. Phone |
HR → WFM WFM → HR |
Character limit: 20 |
|
Profile.Email Address. (Primary) Email* 🔄Personal Email |
Personal Details.Contact. |
HR → WFM WFM → HR |
Character limit: 128 |
|
Profile.Email Address. (Personal) Email 🔄(Primary) Email |
Personal Details.Contact. Email 2 |
HR → WFM WFM → HR |
Character limit: 128 |
|
Profile.Personal Information. First Name* |
Personal Details.Personal. First Name* |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Personal Information. Middle Name |
Personal Details.Personal. 🟡Middle Name |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Personal Information. Last Name* |
Personal Details.Personal. Last Name* |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Personal Information. Preferred Name |
Personal Details.Personal. 📝Roster Name* |
HR → WFM WFM → HR |
Character limit: 15 |
|
Profile.Personal Information. Date of Birth |
Personal Details.Personal. Birth Date* |
HR → WFM WFM → HR |
dd-mm-yyyy |
|
Profile.Personal Information. Gender* |
Personal Details. Personal. Gender* |
HR → WFM WFM → HR |
Matches based on Name or Export Code |
|
Profile.Personal Information. Title |
Personal Details. Personal. Title |
HR → WFM WFM → HR |
Matches based on Name |
Emergency Contact Information
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
People.Personal Information.Emergency Contact Details. Full Name |
Other Info.Emergency Contacts. Name |
HR → WFM WFM → HR |
Emergency Contact flag enabled by default on import in WFM. |
|
People.Personal Information.Emergency Contact Details. Relationship |
Other Info.Emergency Contacts. Relationship |
HR → WFM WFM → HR |
|
|
People.Personal Information.Emergency Contact Details. Phone Number |
Other Info.Emergency Contacts. Phone |
HR → WFM WFM → HR |
|
|
People.Personal Information.Emergency Contact Details. Email Address |
Other Info.Emergency Contacts. |
HR → WFM WFM → HR |
Address
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
Profile.Address. Country (Primary) |
Personal Details.Address. Country |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Address. Postcode (Primary) |
Personal Details.Address. Post Code |
HR → WFM WFM → HR |
Character limit: 10 |
|
Profile.Address. State (Primary) |
Personal Details.Address. State |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Address. Street Line 1 (Primary) |
Personal Details.Address. Address 1 |
HR → WFM WFM → HR |
Character limit: 50 |
|
Profile.Address. Suburb (Primary) |
Personal Details.Address. Suburb |
HR → WFM WFM → HR |
Character limit: 50 |
Visa Information
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
People.Personal Information. Work Right Type |
Employment.Employment. Visa Type |
HR → WFM WFM → HR |
⚠️Update setup with Max Hours on Student Visa in WFM. Matches based on Name. Character limit: 50 |
|
People.Personal Information. Work Right Expiry Date |
Employment.Employment. Visa Expiry |
HR → WFM WFM → HR |
dd-mm-yyyy |
Employee Qualification
| Humanforce HR field | Humanforce WFM field | Integration direction | Important notes |
|---|---|---|---|
|
Qualifications.Qualifications. 🔗Qualification Name |
Qualifications.Qualifications. Type |
HR → WFM |
Imports all (non-draft) qualifications from HR that are valid as of the webhook trigger date. Matches based on Name. Character limit: 50 |
|
Qualifications.Qualifications. Valid Until |
Qualifications.Qualifications. Expiry |
HR → WFM | |
|
Qualifications.Qualifications. Valid From |
Qualifications.Qualifications. Date Issued |
HR → WFM | |
|
Qualifications.Qualifications. Registration Number |
Qualifications.Qualifications. Certificate No |
HR → WFM |
Additional information
-
Related guides
- Learn what the integration does – Start with the Overview article to understand the capabilities and benefits of connecting HR to WFM.
- Set up the integration – See the Setup guide for step-by-step instructions on enabling and configuring the integration.
- Troubleshoot issues – Visit the Known issues guide to review current limitations and workarounds.