Purpose and Audience
This article helps you understand the Award Library testing content for each award. It's intended for individuals familiar with how a Humanforce Library Award may benefit their business and WFM implementation project.
Assumed Knowledge
To get the most out of this article, you should understand:
- What a modern award is - read about this ⭧here
- What a Humanforce Pay Type is - read about this ⭧here
For specific testing outputs, it's helpful to know:
- The award and how it applies to you - library award overviews can be found ⭧here
- Your payroll output needs
CSV Column Header Definitions
- Employee Code: Unique identifier for processing the time data. The specific award can be identified via this field. For example, AGED-FT-SW would represent the Aged Care Full Time Shiftworker award.
- First Name: Not needed for understanding the output.
- Last Name: Not needed for understanding the output.
- Start Date: Date the work starts.
- Start Time: Time the work starts on that day.
- End Date: Date the work ends. If the shift crosses midnight, it will be one day after start date.
- End Time: Time the work ends on that date.
- Break Date: Date of the break, if present. Blank if no break.
- Break Start: Time the break starts on that date.
- Break Duration: Duration of the break in minutes, as an integer. For example, 30 (not 30.0 or 0.5).
- Location Name: Location name of where the work was done. This can affect pay based on your setup.
- Department Export code: Department export code of where the work was done. This can affect pay based on your setup.
- Role Export code: Role export code of where the work was done. This can affect pay based on your setup.
- Shift Type Export Code: Export Code of the relevant shift type. Most will be "NORMAL", but exceptions can impact pay.
- Non-Attended: Indicates if the work is non-attended (e.g., On-Call or Sleepover scenarios). True means non-attended; Blank means attendance is assumed.
- Notes: Details of the specific unit test being conducted.
- Day of Week: Day of the week for the start date. This helps understand penalties without needing a calendar.
- The Rest: Paid hours for the roster item followed by columns for each unique pay type. Not all pay types are sent to payroll; some are for interpretation purposes.
Naming conventions for Pay Types
-
- Output to Payroll: Anything starting with ORD-, OT-, LEAVE- or representing the award (e.g./ SCHADS - Sleepover).
- Interpretation Aids: Anything starting with FLAG, COUNTER or WINDOW is used to capture events and enhance interpretation, but is not sent to payroll.
Testing Process
We use a comprehensive testing process directly on the roster, which does present some gaps that we intend to address in the future.
The current gaps include:
- Cannot test differences between a roster and a timesheet (e.g., an employee rostered from 12pm-6pm, but worked 12pm-7pm - commonly triggering overtime payment).
- Public Holiday not worked (PHNW) automations are not tested as they occur during Payroll processing (e.g., an employee has no timesheet, but was on a template 9am-5pm - commonly trigging PHNW payment).
- Minimum shift Engagement checks and automated shift changes are not tested as they occur during Payroll processing (e.g., an award stipulates casuals must be paid a minimum of 2 hours - commonly triggering a makeup of ordinary hours).
Questions
For questions not covered by an award's help article, the testing data, or this article, contact the Humanforce representative who provided the the testing content. If you are part of the Humanforce team, reach out to the Awards and Compliance Product Team.
You can find an example document attached below from the cleaning award!