This package version requires the following mandatory packages in place before installation.

Enhancement 1 - Flexibility in managing Travel Allowances

An improvement in the design around managing travel allowances with adherence to the Australian Taxation office allowance calculation rules

Previously existing code logic:

• Skedulo Timesheet Approval with a Travel allowance was referring to the "ATO Allowance Type" defined in 2c9 payroll system.
• In the example screen: 
  • Object = Pay Code
  • Record = Travel
  • Field = Pay code name
  • Field Value = "Travel"
  • ATO Allowance type = "Car"

The logic that was previously used was to refer to "ATO Allowance Type" field value

Current Code Logic Fix:

• The travel allowance logic calculation has been enhanced to provide flexibility and thus use the "Allowance Name" as the parameter to send timesheet data over to 2c9 Payroll.
• In the example screen
  • Object = Pay Code
  • Record = Travel
  • Field = Pay code name
  • Field Value = "Travel"
  • ATO Allowance type = "Car"

Upon Installing this package, The logic that will be used is "Pay code Name" field value set.

Instructions:

As an Administrator (SF Administrator):

• Navigate to Custom Meta Data section in the Settings area

• Select "SAGE Integration Additional Settings Option from the list", click "Manage"

• Configure the Custom Meta Data setting exactly same as defined within the 2c9 Payroll system "Pay Code" object, "Pay Code Name Field"
  • Example:
    • If the Pay Code Name = "Travel allowance" in the "Pay Code Object"
    • Then: The Meta Data Setting should also be set to "Travel allowance"

As a Scheduler:

• No changes in the existing process.
• Schedulers will continue to approve the Skedulo timesheets containing Travel, Transport Allowance components as Normal.

As a Mobile Resource (Support Worker):

• No changes in the existing process.
• To continue to use the Travel & Transport form as normal

Enhancement 2 - Leave Events spreading over 2 pay periods

An update in the design around managing leave shifts (leave events) starting on a previous pay period and ending in the next pay period. 

How this works ?

Scenario: The current timesheet pay period ends on 22 Nov 2022, and the new Pay period starts on 23 Nov 2022

1. A mobile support worker S111 is rostered for a Job - J111 from 11pm on 22 Nov 2022 to 9am 23 Nov 2022
2. The support worker applies for any leave which is considered to be paid viz: Annual leave from 10pm to 11.30pm on 22 Nov 2022 
3. The leave applied is formally approved by the manager or scheduler in-charge
4. Skedulo system automatically removes the support worker S111 from the job J111 and a new leave shift or leave event is created - L111 for 25 Nov 2022 from 11pm to 9am
5. The leave event or shift is linked to the Job allocation record of the Job that was to be done by the support worker to maintain the uniqueness feature.
6. The leave shift or event can be seen in the "Related" listing of the Support worker (Resource Record) in salesforce.
7. The leave shift will have a reference of the leave type, timesheet of the current pay period that will be used to pay the support worker when the data is sent to 2c9 payroll as part of the timesheet approval.
8. On successful approval of Skedulo timesheet, the data along with the leave event is seen as a Timesheet entry in 2c9 Payroll with the Leave type clearly detailed so that the support worker is paid in the current timesheet period for the leave event / timesheet entry.

 As a Scheduler:

• No changes in the existing process.
  • Roster the jobs to support workers as normal
  • Approve any leave requests as normal.
  • Check for the presence of any leave events in the related list section of the resource record in Salesforce.
• Schedulers will continue to approve the Skedulo timesheets containing the jobs, activities and leave events.