How to Configure Worked Hours Loading

What This Feature Does

Worked Hours Loading emits an additive parallel loading line for every worked hour, alongside the ordinary worked-hours line, priced at a configurable percentage of each worked line's own base (1×) rate. The worked line itself is untouched — the loading is a separate, individually coded line, so payroll systems (such as MYOB, KeyPay, and Xero) receive the loading as its own coded amount rather than baked into a combined multiplier.

The primary use case is a casual loading — for example, an EBA that pays casual workers a 25% loading on every ordinary hour. Instead of ORD 38h @ $62.50, the export shows ORD 38h @ $50.00 plus Casual Loading 38h @ $12.50.

Worked Hours Loading is configured per Rule Group inside a pay rate document.

When It Applies

Worked Hours Loading is available on every rule group, regardless of how the document's rate tree is structured (unlike Higher Duty Settings, which requires a role-based tree). It is off by default and only emits loading lines once enabled.

Key Concepts

Enabled Toggle

Worked hours loading is off by default. Each rule group has an enable/disable toggle so you can turn it on only where an agreement requires it. Configuration is preserved while disabled, so toggling off and back on does not lose the percentage or pay item mapping.

Configuration Fields

When enabled, the loading is defined by:

How the Loading Is Priced

The loading line is always a percentage of the line's own base (1×) rate, never of an overtime multiplier:

• An ordinary hour at base pays the base line plus a loading line at base × loadingRate%.
• An overtime hour at 1.5× pays the 1.5× overtime line plus (when the overtime toggle is on) a loading line at the same base × loadingRate% — the overtime multiplier does not inflate the loading.
• A worked hour paid off a shift or activity-specific rate is loaded off that rate's base, not the document's default base.

Because the loading line stores its per-hour rate (not the base amount), rate × hours = amount always reconciles with the line total in the review table and exports.

Which Hours Are Loaded

How to Configure Worked Hours Loading

1. Open a pay rate document from the Pay Rate Documents tab
2. Navigate to the Rule Groups section
3. In the Worked Hours Loading area, click "Configure Loading"
4. Toggle Enable worked hours loading on
5. (Optional) Enter a Loading name — defaults to "Casual Loading"
6. Enter the Loading rate (% of base) (e.g. 25)
7. Turn Apply loading on overtime hours on only if the agreement loads overtime too
8. Select the Loading pay item the loading line should be coded to
9. Click "Save"

When enabled, the Rule Groups tab shows a summary badge with the loading percentage, name, pay item, and whether overtime is included.

Example

A casual EBA: base $50, casual loading 25%, coded to CASUAL_LOAD, overtime toggle off. A worker records 38 ordinary hours plus 7 hours of weekly overtime (at 1.5×) in a week.

The result is:

• ORD × 38h @ $50.00 — the ordinary worked line
• Casual Loading (25%) × 38h @ $12.50 — the loading line (38 × $12.50 = $475.00)
• OT × 7h @ $75.00 — the overtime line (1.5× base), with no loading line because the overtime toggle is off

If the overtime toggle were on, the 7 overtime hours would also receive a Casual Loading (25%) × 7h @ $12.50 line — still 25% of base ($12.50/h), not of the $75 overtime rate.

How It Interacts with Other Rules

Worked hours loading runs as an additive post-pass, after overtime, shift-rule, time-of-day and RDO processing are final. It never modifies the worked lines — it only adds parallel loading lines. As a result it stacks cleanly with other loading mechanisms without double-counting:

• A Shift Rule using the Loading application method already emits its own loading line; worked hours loading adds its casual loading alongside — both computed off base, neither loading loaded again.
• Daily/weekly overtime loading and time-of-day loading behave the same way.

Because it runs after the RDO pass, the loading matches the ordinary hours actually paid after any RDO accrual reduces the ordinary line.

Tips

• Match your agreement: Set the rate to the casual-loading percentage in your award or EBA (commonly 25%).
• Overtime is opt-in: Leave Apply loading on overtime hours off unless the agreement explicitly loads overtime.
• Pick a pay item with a description: The loading line's cost-code name column in exports and reports comes from the pay item's description — a pay item with no description renders blank there.
• Re-process to apply: Enabling or changing worked hours loading only affects future rate calculations. Already-processed timesheets must be re-processed for the loading lines to appear.
• Disable instead of delete: Turn the toggle off to pause loading while keeping the percentage and pay item for later.

What's Next

• Return to Rule Groups to configure other rule types
• Compare with Shift Rules and their Loading application method
• Configure Cost Code Linking so the loading pay item maps correctly for export
• Set up Higher Duty Settings for role-based daily re-coding