The integration mentioned in this article is currently under development, and the details provided are subject to change. To stay updated on any modifications or enhancements, click the "Follow" button located at the top left corner of this article under the heading.
Who is Humanforce Payroll?
Humanforce is a unified HCM suite designed for frontline and flexible workforces. Combining workforce management, HR, payroll, and wellbeing, together in the aim to elevate employee experience and simplify compliance. With features like mobile apps, automated workflows, and employee engagement tools, Humanforce helps organisations improve efficiency, reduce costs, and attract & retain top talent. Whether you're in retail, hospitality, healthcare, or another industry with a dynamic workforce, Humanforce offers a customisable suite to meet your specific needs.For more details, you can visit ⭧Humanforce's official website.
What this article covers
This article outlines the functions and options available through API-based integration between Humanforce Workforce Management (WFM) and Humanforce Payroll (Payroll) in Humanforce Cloud. It is crucial to set up the integrations correctly to prevent data issues. If you require assistance or are unsure about setting up the integration, please reach out for help before starting to avoid additional fees for support packages.
What does the integration do?
The integration between Humanforce WFM and Humanforce Payroll facilitates the transfer of crucial employee data, ensuring accuracy and efficiency in workforce management.
Here's what the integration accomplishes:
-
Auxiliary Data
-
Humanforce Payroll → Humanforce WFM
- Public holidays, LDRs, pay rates, and pay types are transferred from Payroll to WFM.
-
Humanforce Payroll → Humanforce WFM
-
Employee Personal Details:
-
Humanforce Payroll → Humanforce WFM
- Newly created employees and updates made to the employee's details are sent to WFM in a bulk sync that can be scheduled or manually run through Integration Central (IC).
- Termination dates entered in Payroll will sync to WFM.
-
The integration prioritizes updating existing employees in WFM before creating new ones, using the following matching logic:
-
Match WFM's Payroll Code to the incoming Employee Number in Humanforce Payroll.
-
If no match is found, identify the closest match based on Date of Birth, First Name, Last Name and Payroll Company (all attributes must match).
-
If neither approach yields a match, create a new employee.
-
-
Humanforce WFM → Humanforce Payroll
- New employees created in the WFM Onboarding module or Employee Management screen, create a new employee in Payroll.
- Note, an employee will not be active in Payroll until all payroll-specific fields (e.g. Tax details, leave accruals, etc) are completed directly in Payroll.
- Updates made to employee's details from the Employee Management screen or via the Change Approval process will flow through to Payroll.
- New employees created in the WFM Onboarding module or Employee Management screen, create a new employee in Payroll.
-
Humanforce Payroll → Humanforce WFM
-
Payroll Export
-
Humanforce WFM → Humanforce Payroll
- 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 Payroll.
-
Humanforce WFM → Humanforce Payroll
-
Employee Leave Balances
-
Humanforce Payroll → Humanforce WFM
- After payroll finalisation leave balances are updated in Payroll and can be synced to WFM.
-
Humanforce Payroll → Humanforce WFM
-
Payslips
-
Humanforce Payroll → Humanforce WFM
- After payroll finalisation payslips are available in Payroll and can be synced to WFM.
-
Humanforce Payroll → Humanforce WFM
Humanforce HCM Suite Integration between Humanforce HR, WFM, and Payroll
For HCM Suite Customers: Data synchronisation between Humanforce HR, Humanforce WFM, and Humanforce Payroll is seamlessly managed through the Employee Data Forwarding feature. This ensures a unified data flow across the suite, reducing manual intervention and improving consistency.
For more information on the suite integration, refer to Humanforce Suite Integration or see the Employee Data Forwarding section.
Prerequisites
Before proceeding with the integration, ensure that the following prerequisites are met:
-
Humanforce Cloud Customer: Access to this integration is exclusive to Humanforce Cloud customers.
-
API Credentials: Obtain API credentials from Humanforce Payroll with comprehensive permissions to facilitate data exchange between the platforms. Ensure to note the system you are integrating with when requesting the API. i.e. Humanforce WFM or Humanforce HR.
-
Source of Truth: Humanforce Payroll serves as the primary repository for employee data, unless Humanforce WFM onboarding is used, in which case WFM becomes the source of truth.
- Change Approvals: The "Changes Require Approval" permission must be enabled for changes to flow via the Change Approvals page into Payroll.
Best Practices and Tips
- Simplify employment types in WFM to improve reporting and reduce administrative overhead. Employment Types: Fulltime, FulltimeLL (with Leave Loading), PartTime, PartTimeLL, and CAS (Casual).
- Send timesheets for worked and leave hours for all employees, including salaried (autopaid) staff. This can be achieved by creating Master Templates for salaried staff, loading them into rosters, and using a data exchange task to auto-create timesheets based on these rosters for employees with the "Timesheet Autocreate" flag enabled.
- Ensure that awards are configured to cap hours per period for payment for full-time and part-time employees.
- Roster Max Hours, Locations, Departments, and Roles should be managed within the WFM system.
- Provide cost center mapping to Payroll for accurate timesheet cost mapping; if not provided, the employee's default cost center in Payroll will be used.
- Ensure the shift type in WFM is set to Enable Accruals when importing leave balances.
Known Issues / Gaps
-
Variable Amount Allowances
- Issue: If an allowance is set as a variable amount in payroll and the export dollar figures are set/managed in WFM, the dollar value is not sent to Payroll in the payroll export.
- Status: Work in progress, expected resolution by the end of June.
- Workaround: Set up the pay element in Payroll as an allowance amount by unit, with the dollar value being held and managed in Payroll. If the value is unknown and entered at the time of the shift, set up the value in Payroll as $1, allowing the manager to add the required total value in WFM.
-
Role Revision Date
- Issue: When a new employee has a role assigned, the role effective date defaults to 01/01/1900. On save, the rate does not flow from WFM to Payroll, as dates before the employee's start are not accepted in Payroll.
- Status: An investigation is underway to address this issue.
- Workaround: Manually update the role effective date in WFM to the employee's start date to allow the rate to flow through to Payroll.
-
Employees with New Zealand addresses not be created or updated in HF PAYROLL from WFM when State is set to non-standard value in HF Payroll
- Issue: If a NZ address of an employee has State field set in WFM, then it needs to match exactly what HF Payroll supports in the State drop-down. Complexity here is that NZ does not have a concept of state (or as NZ calls them REGIONS) in their addresses yet this is critical for payroll processing for deducing public holidays. This is further exasperated when HF HR is added the mix where the state field cannot be manually adjusted.
- Status: Investigation in progress to identify a solution.
- Workaround: If WFM-HF PAYROLL integration only, then manually adjust state to match regions in NZ. If HF HR-WFM-HF PAYROLL, then NO WORKAROUND.
Integration Setup
Detailed step-by-step setup instructions for the Humanforce Payroll integration can be found in this article ⭧Set up Humanforce Payroll integration.
API Documentation
Humanforce WFM uses its REST API to push and pull data between the systems. More information on the Humanforce REST API is available in this article ⭧Humanforce REST API Overview.
Integration Workflow
Follow these steps to set up the integration between Humanforce WFM and Humanforce Payroll:
-
Prepare your data:
- Create Auxiliary Data:
- In WFM: Create Access Level, Clock-in Setting, Qualification Types, Visa Types, Location, Department, Role, and Area in WFM.
- In HF Payroll: Create Public Holidays, Pay Rates and Pay Type.
- In both systems: Create and match Gender, Title, Pay Company, Employment Type, and Award Profiles in both WFM and Payroll.
- Create or upload employee records in Humanforce WFM.
- Create Auxiliary Data:
-
Set Up Integration:
- Obtain API credentials for Humanforce Payroll. ⭧Learn how in this article - HF staff only
- Set up the integration in WFM > Integration Central. ⭧Learn how in this article.
- Test the connection and resolve any errors.
-
Configure Mapping:
- Employee Import
- Enable employee details, leave balances, pay slips and auxiliary data sync for accurate data transfer. Supported mapping ⭳below.
- Employee Upload
- Enable employee details mapping for accurate data transfer. Supported mapping ⭳below.
- Payroll Export
- Enable cost centre mapping, if required.
- Match the WFM pay types to relevant export behaviour, payroll pay element and settings of Payroll.
- To ensure Under-18 employees are paid correctly under the statutory superannuation guarantee rules, you will need to ensure the relevant pay types have an export behaviour = element, setting of Factor of Rate and have the tickbox ticked to send dates for under 18 employees.
- Optionally, schedule automatic data synchronisation.
- Employee Import
-
Review and Troubleshoot:
- Monitor the import log and address any errors for a successful data transfer.
Employee Data Forwarding (Available for use in Early Access)
Overview
Humanforce is excited to introduce the Employee Data Forwarding feature, which enables seamless data synchronisation across multiple integrations within Humanforce Workforce Management.
Key Benefits
- Seamless Integration: Connect Humanforce products (Humanforce HR, Humanforce WFM, and Humanforce Payroll) and supported third-party integrations.
- Automatic Updates: Ensure that data changes made in HR are automatically forwarded from WFM to Payroll, eliminating the need for manual updates.
- Improved Data Consistency: Minimise the risk of data inconsistencies and reduce manual data entry efforts, maintaining up-to-date records across all systems.
Getting Started
With Employee Data Forwarding, you can link Humanforce HR, WFM and HF Payroll systems together.
For detailed setup instructions and more information, please refer to the Employee Data Forwarding documentation.
Supported Data Mapping
This integration facilitates data transfer between Humanforce WFM (WFM) and Humanforce Payroll (HFP) in two main categories:
- Auxiliary Data: Auxiliary data serves as the admin list for specific employee data fields, ensuring consistency across systems. This includes information like public holidays, location, department, role, pay rates, and pay types, which are transferred from HFP to WFM.
- Employee Details: This includes employee information such as personal details, and employment details, which can be transferred in both directions between the two systems.
- Payroll Export: Once timesheets are processed in the WFM payroll screen, the timesheet data can be uploaded to Humanforce Payroll.
- Employee Leave Balances: Employee leave balances are checked and pulled every time the Humanforce Payroll integration central task runs in WFM.
- Payslips: The payslip import is triggered as part of the integration when the Humanforce Payroll integration central task runs in WFM.
Auxiliary Data
The table below illustrates fixed mappings. Note, these fields can be enable or disabled on the integration configuration screen within Humanforce WFM (Management > Advanced > Integration Central).
Field Name - HF WFM |
Field Name - HF Payroll |
Transfers |
Important Notes |
Public Holidays
|
Public Holidays
|
HFP→WFM |
Default PH Type = "Default" Default Colour = Yellow - #ffff00 |
Location Department Role |
Levels(1:M) Levels(2:M) Levels(3:M) |
HFP→WFM |
Levels must be named Location, Department, Role. Code or Name can be used as a unique identifier for import based on selection. |
Org Structure |
Org Structure LCODE/DCODE/RCODE |
HFP→WFM |
Imported based on code. |
Pay Rates
|
Pay Rates
|
HFP→WFM |
Name is the unique identifier. |
Pay Types
|
Pay Elements
|
HFP→WFM |
PayType will be treated as either Units, Factor or default to Multiplier with 0 Name is the unique identifier. |
Employee Details
The following tables will take you through which employee data fields can be transferred via the API.
Some fields are configurable in the integration configuration screen in WFM (Management>Advanced>Integration Central).
- Where field details are noted as "Summary Entity Model", ensure the values held in the auxiliary list match between systems.
Integrated Data
Field Name |
Field Name HF Payroll - tab.section. field name [api name] |
Integration Direction |
Important Notes Field Details |
Personal Details.Personal. Employee Code* |
Employee.Employment. Employee number* |
HFP→WFM |
Only imports for new employees. PayrollCode is the unique identifier for the employee sync 50 character max |
Employment.Employment. Payroll Code* |
Employee.Employment. Employee number* |
WFM→HFP HFP→WFM |
PayrollCode is the unique identifier for the employee sync 100 character max |
Personal Details.Personal. Title |
Personal.Personal. Title |
WFM→HFP HFP→WFM |
The Title in WFM must be configured to match the below values from HFP.
Summary Entity Model |
Personal Details.Personal. First Name* |
Personal.Personal. First name* |
WFM→HFP HFP→WFM |
30 character max |
Personal Details.Personal. Last Name* |
Personal.Personal. Last name* |
WFM→HFP HFP→WFM |
30 character max |
Personal Details.Personal. Roster Name [ShortName]* |
Personal.Personal. Preferred name |
WFM→HFP HFP→WFM |
Employee’s name as it will appear in the rostering screen. 15 character max |
Personal Details.Address. Address 1 |
Personal.Personal. Address Line 1* |
WFM→HFP HFP→WFM |
50 character max |
Personal Details.Address. Address 2 |
Personal.Personal. Address Line 2 |
WFM→HFP HFP→WFM |
Second line of an employee’s home address 50 character max |
Personal Details.Address. Suburb |
Personal.Personal. Suburb / City or Town* |
WFM→HFP HFP→WFM |
50 character max |
Personal Details.Address. State |
Personal.Personal. State / Region* |
WFM→HFP HFP→WFM |
50 character max |
Personal Details.Address. Post Code |
Personal.Personal. Postcode* |
WFM→HFP HFP→WFM |
10 character max |
Personal Details.Address. Country |
Personal.Personal. Country* |
WFM→HFP HFP→WFM |
50 character max |
Personal Details.Personal. Birth Date [DateOfBirth] |
Personal.Personal. Date of birth* |
WFM→HFP HFP→WFM |
dd-mm-yyyy |
Personal Details.Personal. Gender |
Personal.Personal. Gender* |
WFM→HFP HFP→WFM |
Gender Name must match in all systems.
Note, If a value is detected other than Male/Female, the system will default the gender field to "Not Stated" in Humanforce Payroll. Matched by Name on import to WFM |
Personal Details.Contact. Mobile |
Personal.Personal. Private Mobile |
WFM→HFP HFP→WFM |
20 character max |
Personal Details.Contact. Phone |
Personal.Personal. Private Phone |
WFM→HFP HFP→WFM |
20 character max |
Personal Details.Contact. Phone 2 [SecondaryPhone] |
Employee.Employment. Work Mobile |
WFM→HFP HFP→WFM |
Alternate phone number for the employee 20 character max |
Personal Details.Contact. |
Personal.Personal. Private email* |
WFM→HFP HFP→WFM |
128 character max |
Personal Details.Contact. Email 2 [SecondaryEmail] |
Employee.Employment. Work email* |
WFM→HFP HFP→WFM |
Alternate E-mail for the employee 128 character max |
Personal Details.Bank Account. Bank [BankName] |
Pay Distribution.Pay Distribution. Branch Name |
WFM→HFP HFP→WFM |
Optional to import 50 character max |
Personal Details.Bank Account. BSB [BankBSB] |
Pay Distribution.Pay Distribution. BSB Code* |
WFM→HFP HFP→WFM |
Optional to import 20 character max |
Personal Details.Bank Account. Account Name [BankAccountName] |
Pay Distribution.Pay Distribution. Account Name* |
WFM→HFP HFP→WFM |
Optional to import 50 character max |
Personal Details.Bank Account. Account No [BankAccountNumber] |
Pay Distribution.Pay Distribution. Account No.* |
WFM→HFP HFP→WFM |
Optional to import 50 character max |
Personal Details.Bank Account. Suffix [BankAccountNumberSuffix] |
Pay Distribution.Pay Distribution. Account Suffix.* |
WFM→HFP HFP→WFM |
Optional to import Only relevant for New Zealand bank accounts. 50 character max |
Employment.Employment. Employment Type |
Pay.Work Pattern Section. Work Pattern* |
WFM→HFP HFP→WFM |
Employee Status is defaulted to manual. Automatic status applies when the Employment Type name includes "auto". E.g "Salary auto" Summary Entity Model |
Employment.Employment. Tax Id |
Tax.Tax. Tax File Number* |
WFM→HFP HFP→WFM |
If the Tax ID is removed from WFM, it will not update in HFP, as the API does not accept empty values. Employee’s tax identification code. |
Employment.Employment. Pay Company* |
PayrollName* |
WFM→HFP |
Integration task selected based on employee's Pay-company |
Employment.Employment. PayPeriod name* |
PayRule* |
WFM→HFP |
Pay period assigned to the pay company |
Employment.Employment. Default Location* |
Org/Cost.Org/Cost. Location[Level 1] |
WFM→HFP HFP→WFM |
Recommended to manage in WFM only Export codes need unique identifiers - consultant responsibility. Imports on name. Uploads on Code. Optional to import Summary Entity Model |
Employment.Employment. Default Department* |
Org/Cost.Org/Cost. Department [Level 2] |
WFM→HFP HFP→WFM |
Recommended to manage in WFM only Export codes need unique identifiers - consultant responsibility. Imports on name. Uploads on Code. Optional to import Summary Entity Model |
Employment.Employment. Default Role* |
Org/Cost.Org/Cost. Role [Level 3] |
WFM→HFP HFP→WFM |
Recommended to manage in WFM only Export codes need unique identifiers - consultant responsibility. Imports on name. Uploads on Code. Optional to import Summary Entity Model |
Employment.Employment. Start Date* |
Employee.Employment. Hired Date [Service Start Date] |
WFM→HFP HFP→WFM |
Export WFM→HFP: Start Date → Hired Date Import HFP→WFM: Hired Date → Start Date dd-mm-yyyy |
Employment.Employment. Leave Accrual Start |
Employee.Employment. Service Start Date |
WFM→HFP HFP→WFM |
Export WFM→HFP: Leave Accrual Date → Service Start Date Start Date → Service Start Date if Leave Accrual Date is empty Import HFP→WFM: Service Start Date → Leave Accrual Date when Service Start Date is different from Hired Date Service Start Date = Hired Date enable "Use Start Date" checkbox in WFM dd-mm-yyyy |
Employment.Employment. Termination Date |
Employee.Employment. Termination date |
HFP→WFM WFM→HFP |
Note, employees will be created or updated in HF Payroll whenever they are updated or added in WFM, regardless of whether their termination date is in the past, present, or future. dd-mm-yyyy |
Employment.Employment. Max Roster Hours [RosterMaxHours] |
Pay.Work Pattern Section.Work Pattern. FteHoursPerWeek |
HFP→WFM |
Recommended to manage in WFM only Effective Date in WFM is set to the start date of the current Pay Period of the Employee’s Pay Company. 50 character max |
Location, Department, Roles.Roles and Profiles. Date Effective [RoleRevisionDateEffective]* |
Pay.Rate Section. Rate Set Effective Date |
WFM→HFP HFP→WFM |
dd-mm-yyyy |
Location, Department, Roles.Roles and Profiles. Default Award Profile* |
Employee.Employment. Award Agreement |
WFM→HFP HFP→WFM |
Award Profile Name and must match in all systems. Summary Entity Model |
Location, Department, Roles.Roles and Profiles. Default Pay Rate |
Pay.Rate Section. Rate Set |
WFM→HFP HFP→WFM |
If "Hourly Rate" exists in the employee table then this is used, otherwise the "Rate Set" is used. Not updated from WFM if Job Classification exists. Optional to import Summary Entity Model |
Location, Department, Roles.Roles and Profiles. Default Rate Override [DefaultHourlyRate] |
Pay.Rate Section. Amount |
WFM→HFP HFP→WFM |
If "Hourly Rate" exists in the employee table then this is used, otherwise the "Rate Set" is used. Not updated from WFM if Job Classification exists. |
Other Info.Emergency Contacts. Name |
Contact Name |
WFM→HFP HFP→WFM |
Emergency flag enabled by default on import. Optional to import |
Other Info.Emergency Contacts. Relationship |
Relationship |
WFM→HFP HFP→WFM |
Optional to import Details on how the emergency contact is related to the employee. |
Other Info.Emergency Contacts. Phone |
Phone |
WFM→HFP HFP→WFM |
Optional to import |
Other Info.Emergency Contacts. |
|
WFM→HFP HFP→WFM |
Optional to import |
Employment.Employment. Include in payroll export* [ExportPays] |
|
HFP→WFM |
Default set to True Indicates whether the employee’s timesheet data should be sent to payroll the payroll system or not. |
* Mandatory field
New Employee Defaults (HF Payroll to WFM Employee Import)
The following fields allow once-off values to be selected for newly created employees when importing employees from HF Payroll to WFM.
Field Name - WFM tab.section.field name |
Field Details |
Personal Details.Personal.
|
|
Employment.Employment.
|
Summary Entity Model |
Employment.Employment.
|
|
Location, Department, Roles.Roles and Profiles.
|
Summary Entity Model |
* Mandatory field
Non-Integrated Data
The following fields are not available to map between the two systems, so need to be maintained in the source system if required.
Humanforce WFM fields
Field Name - WFM tab.section.field name |
Field Details |
Award Profile Override.Shift Gap.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Employment.Employment.
|
|
Location, Department, Roles.Departments.
|
|
Location, Department, Roles.Roles and Profiles.
|
|
Location, Department, Roles.Roles and Profiles.
|
|
Location, Department, Roles.Roles and Profiles.
|
|
Other Info.Emergency Contacts.
|
|
Other Info.Emergency Info.
|
|
Other Info.Other Info.
|
|
Other Info.Other Info.
|
|
Personal Details.Bank Account.
|
|
Personal Details.Contact.
|
|
Personal Details.Diversity.
|
|
Personal Details.Personal.
|
|
Qualifications.Qualifications.
|
|
* Mandatory field
Humanforce Payroll fields
Field Name - HFP tab.section.field name |
Field Details |
Employment.Employment.
|
|
Org/Cost.Employee Default Cost Centres.
|
|
Pay Distribution.List of Pay Distributions.
|
|
Pay.Pay.
|
|
Tax.
|
* Mandatory field
Payroll Export
Timesheet Upload API Integration
The Humanforce Payroll Timesheet Upload API allows you to upload timesheet data directly into the payroll system, ensuring a seamless and efficient process. This section provides detailed information on how to configure and use this integration.
-
Endpoint:
/Api/Timesheet
- Method: POST
-
The API accepts the following input parameters:
Parameter Name Description Accepted Values IsAppend
Indicates if the export should append or override data. True; False LoadStandardPayElements
Used when loading into Pay Adjustment only. True; False FileFormat
The format of the export data. “json” FileContent
Content of the export file formatted according to FileFormat
.A string representing the file content in csv or json format
Field Descriptions
Field Name | Field Type | Remarks | Translation Applicable |
---|---|---|---|
Payroll Name* | 50 char | Must be a valid payroll name | |
Employee Number* | 10 char | Must be a valid employee number | |
Pay Element Description* | 50 char | Must be a valid Pay Element | Y |
Hours/Qty | 9(8).9(2) | Required for specifying number of Hours or Units of the pay element | |
Date From | Date | Required if Pay Element is a leave Pay Element | |
Date To | Date | Required if Pay Element is a leave Pay Element | |
Amount | 9(12).9(2) | Required for specifying the amount of Allowances/Deductions | |
Percentage | 9(3).9(2) | Applicable to percentage type elements | |
Cost Centre | 30 char | Must be a valid cost centre if supplied | |
Rate Amount | 9(8).9(5) | Used if rate is to be overridden. Cannot be present if Rate Set is present | |
Rate Set Description | 50 char | Used if rate is to be overridden. Cannot be present if Rate Amount is present. Must be a valid rate set. | Y |
LSL Average Hours Per Week | 9(3).9(2) |
Applicable for LSL Pay Element to override LSL Average Hours Per Week. (NZ payroll only) |
* Mandatory field
Cost Centre Mapping
Cost centre mapping (CCM) is a crucial step in integrating Humanforce WFM with Humanforce Payroll. It ensures that timesheet data is accurately matched to the corresponding cost centres in Humanforce Payroll.
Activating Cost Centre Mapping (CCM):
-
Navigate to the Payroll Export section and access "Cost Centre Mapping" on the second tab.
-
Select the appropriate source(s) for the cost centre codes, such as:
- Location ExportCode
- Role Name
- <Custom Cost Centre Mapping Name>
This list includes built-in sources, with the option to custom cost centre mappings can also be configured and will appear by their names.
-
Reorder the mapping when using a combination of sources by dragging and dropping using the
icon to the left of each source.
-
Default Values: If a combination of timesheet attributes does not resolve to a cost centre map string, a default value (if set) will be used instead of sending a blank string.
-
Separators: Choose the required type of separator for cost centres as defined in Payroll, such as:
-
Slash /
-
Dot .
-
Further Resources:
- How to import Cost Centre Mapping through Integration Central?
- How do I update Cost Centre Mappings? (Back Office). Note, this will be available in web early 2025.
Employee Leave Balances
Field Name - HF WFM |
Field Name - HF Payroll |
Transfers |
Important Notes |
Shift Type Export Code |
Leave Type |
HFP→WFM | The ShiftType ExportCode in Humanforce must match the LeaveType in Humanforce Payroll to successfully import. Default Type on import = "Balance" |
Hours |
Entitlement |
HFP→WFM | All entitlements for leave are treated as hours. Balances sent in days or weeks will currently be treated as hours. e.g., 1 week sent, 1 hour will be available. |
|
Leave. LSL Average Hours Per Week |
HFP→WFM |
Used in leave balance conversions for AU customers. Learn more ⭳below. |
|
Leave. NZ Average Days Per Week |
HFP→WFM |
Used in leave balance conversions for NZ customers. Learn more ⭳below. |
Humanforce Payroll offers the option to convert leave balances between different units (weeks, days, hours) during the import and export processes. This functionality is available for specific countries and leave types, allowing for accurate data transfer between Humanforce WFM and Humanforce Payroll.
Australia: Long Service Leave Conversion
For Australian customers, the integration supports converting long service leave balances between weeks and hours.
Import Process:
- Applies only when the task country is set to "Australia"
- Applies only to the leave type "Long Service Leave"
- Applies only when the leave unit is set to "Week"
- If the "Import Long Service Leave as hours" setting is enabled, the leave balance (in weeks) is multiplied by the employee's
LslAverageHoursPerWeek
value from Payroll to convert it to hours. - If the
LslAverageHoursPerWeek
value is null, this leave type is skipped for the employee, and a warning is logged.
Timesheet Upload Process:
- Applies only when the task country is set to "Australia"
- Applies only to the leave type "Long Service Leave"
- If the "Upload Long Service Leave as weeks" setting is enabled, the leave hours from the timesheet are divided by the employee's
LslAverageHoursPerWeek
value to convert them back to weeks. - If the
LslAverageHoursPerWeek
value is null, a warning is logged, and the leave is uploaded in hours without conversion.
New Zealand: Leave Balance Conversion
For New Zealand customers, the integration supports converting leave balances between weeks and days.
Import Process:
- Applies only when the task country is set to "New Zealand"
- Applies to all leave types
- Applies only when the leave unit is set to "Week"
- If the "Convert leave from weeks to days" setting is enabled, the leave balance (in weeks) is multiplied by the employee's
NzAverageDaysPerWeek
value from Payroll to convert it to days. - If the
NzAverageDaysPerWeek
value is null, this leave type is skipped for the employee, and a warning is logged.
Timesheet Upload Process:
- Applies only when the task country is set to "New Zealand"
- Applies to all leave types
- If the "Convert leave from days to weeks" setting is enabled for the selected leave mapping, the leave hours from the timesheet are divided by the employee's
NzAverageDaysPerWeek
value to convert them back to weeks. - If the
NzAverageDaysPerWeek
value is null, a warning is logged, and the leave is uploaded without conversion.
Payslips
Field Name - HF WFM |
Field Name - HF Payroll |
Transfers |
Important Notes |
Payroll Code | Employee Number | HFP→WFM | The employee's WFM PayrollCode is sent to the Payroll API to request the payslips and must match their employee code within Payroll. |
First Name / Last Name | First Name / Last Name | HFP→WFM | The name on the payslip is matched to the employee name in WFM, and if it already exists, the import is skipped to avoid duplicate payslips. |
Payroll date/ Pay Period | Period Dates | HFP→WFM |
|