> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.2cloudnine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Desert Flame '24 (includes Rate Calculator) - Release Notes

The Desert Flame '24 release for 2cloudnine Payroll has a number of exciting enhancements that are
designed to optimise existing processes. Below is an outline of the new features and updates that are
included in the release.

<Frame>
  <img src="https://mintcdn.com/2cloudnine-2edf05eb/EDjQiHb20EmtNY7H/images/generated/release-notes/desert-flame-24/2cloudnine-payroll-1-223-2-desert-flame-24-includes-rate-calculator-release-notes/desert-flame-24-release-notes-legend.png?fit=max&auto=format&n=EDjQiHb20EmtNY7H&q=85&s=60c8f97fe027b2caeb17b23e2eef880e" alt="Icons Legend" width="991" height="285" data-path="images/generated/release-notes/desert-flame-24/2cloudnine-payroll-1-223-2-desert-flame-24-includes-rate-calculator-release-notes/desert-flame-24-release-notes-legend.png" />
</Frame>

### Rate Calculator Integrations for Alternate Minimum Pay Rates <Badge color="gray">New</Badge>

Orgs that have implemented Alternate Minimum Pay Rate (MPR) will now be able to update Rate
Calculator values directly from MPR records.

To facilitate this, a new Rate Calculator Only section has been added to the MPR record, where Rate
Calculator Rates can be managed directly. With these new fields comes the ability to create new Margin /
Mark Up records directly via MPR. The Create Related Margin / Mark Up Records field allows you to
determine whether the values entered in Calculation Method, Margin Rate and/or Markup Rate fields
should be used to create new stand-alone Margin / Mark Up records. When not selected, automation will
instead create new Rate Calculator Rate records using the values entered. This new feature negates the
requirement to create and manage Margin / Mark Up Rates directly via Rate Calculator Templates,
drastically reducing the need for Rate Calculator Templates where Margin Rates differ.

A new lookup field has been created to indicate where MPR has been used to create new Rate Calculator
records. The Minimum Pay Rate field will be automatically populated on Mark Up / Margin and Rate
Calculator Rate records created via the process detailed above, so that the relationship between records
is clear.

The Rate Calculator Only section of MPR includes fields Custom Pay Rate 1, Custom Pay Rate 2, Rate
Entered, Calculation Method, Margin Rate and Mark Up Rate, which work in tandem with the
functionality described above.

Additionally, MPRs may now be assigned to new Rate Calculator Template Groups, further refining the
filter conditions for Pay Rates. Populating the Rate Calculator Template field on MPR records will allow
MPRs with the same Interpretation Rule, Award Classification and Award Levels to contain Pay Rates
specific to the Rate Calculator Template Group entered.

**Configuration Requirement** : **Optional**\
**User Story Reference Number(s):** SC-35960, SC-35931, SC-35984, SC-35989

### Introducing Mark Up / Margin Overrides <Badge color="gray">New</Badge>

Recent updates have enabled overrides to be applied on all Mark Up and Margin fields on Rate Calculator
Lines. This new functionality allows any type of custom margin calculation to be applied, providing
greater flexibility when managing rates and markups.

**Configuration Requirement** : **Optional**\
**User Story Reference Number(s):** SC-35518

### Batch Size Controls for Rate Calculator <Badge color="gray">New</Badge>

The ability to apply batch size restrictions to record processing for Rate Calculator and related
automation has been introduced. This new feature allows you to control batch sizes when creating and
managing Margin/Markup and Rate Calculator records from MPR, and ensures smoother processing and
better performance for all Rate Calculator functionality.

**Configuration Requirement** : **Conditionally Compulsory** (required if Rate Calculator in use) **User Story Reference Number(s):** SC-36458

### Enhancements for the Integrated Import Tool <Badge color="gray">New</Badge>

Updates to Scheduled Jobs have been deployed to allow additional records to be automatically
populated with unique identifiers, further streamlining the import process.

Payee Allowance records may now be updated with an External ID (ID) value using either a combination of
the Payee External Id / Payee Allowance Name, or the Payee External Id / Assignment External Id / Payee
Allowance Name.

Also, updates have been made to allow alternate date formats to be imported, for a better experience
when migrating data from Excel.

**Configuration Requirement** : **Optional**\
**User Story Reference Number(s):** SC-36476, SC-36479

### Improved Flexibility for Split / Broken Shift Logic <Badge color="gray">New</Badge>

Several new fields have been added to enable a greater level of flexibility to the way that Split / Broken
Shift Timesheet Entries are interpreted.

In addition to the existing Breakpoint fields, Penalty and Casual Loading Pay Codes may now be defined
individually for Saturdays, Sundays and Public Holidays. New fields have also been added to determine
whether Penalty or Casual Loading Pay Codes incurred across Split/Broken Shift Timesheet Entries
should be applied on top of Overtime Pay Codes, or only to Standard Hours.

Shift Start Time may now be used to interpret Split / Broken Shift Breakpoints on Shift End Interpretation
Rules due to the new field Apply Shift Start Time BP.

New logic has also been enabled to allow Split / Broken Shifts to be calculated according to the span of
hours between Timesheet Entries, instead of being applied each time multiple Timesheet Entries are
recorded for the same day. When Broken Shifts are enabled on an Interpretation Rule, and the new field
Calculate Span from Previous Shift is set to True, you will be able to define the Split / Broken Shift Reset
Hours that will be applied for Timesheet Entries that occur within a rolling 24 hour period. Without this
feature enabled, Split / Broken Shift Timesheet Entries will continue to be interpreted using Daily logic.

**Configuration Requirement** : **Conditionally Compulsory** (configuration only required if new features are implemented) **User Story Reference Number(s):** SC-33874, SC-36317, SC-35448, SC-35410

### Introducing Shift-Based Calculations <Badge color="gray">New</Badge>

Changes have been implemented to enable Overtime to be applied on a Shift basis, instead of being
interpreted according to the number of hours entered for a single day. When the new field Apply Shift
Based Interpretation is set to True, related Timesheet Entries will be grouped together and considered as
a single Shift, to enable Interpretation to determine Overtime entitlements according to the amount of
Standard Hours defined for each Shift.
In order to accomplish this new type of calculation, changes have been implemented to the way that
Timesheet Entries are assessed during Interpretation. Entries may now be interpreted using Shift Logic,
rather than Daily Logic, enabling Timesheet Entries associated with the same Shift to be grouped and
assessed together, rather than being grouped according to the day that they have been entered on.

The changes to Interpretation Logic implemented to accomplish this will impact Daily Overtime and
Minimum Hour calculations, which will flow on to impact Frequency calculations. The application of
Minimum Rest and Broken Shift may also change depending on the way that Timesheet Entries are
assessed and grouped. Please reach out to your Consultant if you require further detail regarding these
changes.

Additional considerations may also be necessary if you are required to make any additional changes to an
Approved Timesheet. Please refer to the appropriate vendor before making any changes to Approved
Timesheets populated via integration.

**Configuration Requirement** : **Conditionally Compulsory** (configuration only required if new features are implemented) **User Story Reference Number(s):** SC-36186, SC-34420, SC-36401

### New Breakpoints for Shift-Based Allowances <Badge color="gray">New</Badge>

Similar to the changes introduced for Overtime, a new Shift Allowance Breakpoint type has been created
so that Allowance Breakpoints may be created for Broken Shifts. This Breakpoint type enables Allowances
to be interpreted according to the quantity of hours elapsed between Timesheet Entries in a rolling 24
hour period. Included in this enhancement is the capability to associate different Allowance Pay Codes
with each Shift Allowance Breakpoint, to ensure applicable entitlements are associated with each
individual Shift Entry.

**Configuration Requirement** : **Conditionally Compulsory** (configuration only required if new features are implemented) **User Story Reference Number(s):** SC-35447

### Enhanced Interpretation for Sleepover Entries <Badge color="gray">New</Badge>

As with the improvements made for Split / Broken Shift Interpretation, additional options are now
available for Sleepovers. Timesheet Entries may now be interpreted with defined Penalty and / or Casual
Loading Pay Codes created specifically for Saturday, Sunday and Public Holiday Time. New fields have
been added to Sleepover Breakpoints to facilitate this enhancement.

Another change introduced is the ability to define the minimum entitlements for Wake Up Timesheet
Activities. When Apply Wake Up Interpretation is enabled, the new field Wake Up Minimum Hours will be
required so that Interpretation is able to calculate the sum of Total Hours of Wake Up across a Shift to
determine whether or not the Wake Up Minimum Hours have been reached, and if not, what
entitlements to apply for this Time.

An additional field is also available when Sleepover Interpretation is applied. Sleepover Minimum Paid
Hours enables Timesheet Entries involving Sleepover activities to be interpreted using Shift Logic and
calculated separately from Daily Hours, according to the hours entered in this field.

**Configuration Requirement** : **Conditionally Compulsory** (configuration only required if new features are implemented) **User Story Reference Number(s):** SC-33813, SC-35452, SC-35456

### New Overtime Calculations in Time Breakpoints for Daily Standard Hours <Badge color="gray">New</Badge>

Enhancements have been made to provide greater flexibility within the Interpretation Rules Builder. This
change allows users to determine whether Overtime relating to Time Breakpoints should be included or
excluded from Daily Standard Hours calculations.

To accommodate this requirement, the existing field Include Time Breakpoints in Overtime has been
re-named to Include Time BPs in OT - Freq Std Calcs. A new field Include Time BPs in OT - Daily Std Calcs
is available when Include Time BPs in OT has been selected. These fields are enabled for use on all
Interpretation Rule Record Types, excluding Daily.

**Configuration Requirement** : **Conditionally Compulsory** (configuration only required if new features are implemented) **User Story Reference Number(s):** SC-31737

### Updated Shift Interpretation for Minimum Rest Hours <Badge color="gray">New</Badge>

Changes have been made that enable Minimum Rest periods to be interpreted on a Shift basis, rather
than a Daily basis. This means that Minimum Rest will be assessed according to the time elapsed
between every Timesheet Entry for each Shift (which could cross midnight) instead of being applied to all
Timesheet Entries on a single day, whenever there is one Entry that does not meet Minimum Rest.

To opt-out of Shift Interpretation for Minimum Rest and continue to use Daily Interpretation instead, a
new field Apply Minimum Rest To Same Day Entries has been created and will be available from the
Break Loading and Minimum Rest Rules section on all Interpretation Rule Record Types excluding Daily.

**Configuration Requirement** : **Conditionally Compulsory** (configuration only required if new features are implemented) **User Story Reference Number(s):** SC-35443

### Maintain Data Integrity for Interpretation Rules <Badge color="gray">New</Badge>

Changes have been implemented to uplift data management practices for Interpretation Rules.
Breakpoints will now be deleted alongside their related Interpretation Rules, unless they are being
referenced by another Interpretation Rule. For example, deleting an Interpretation Rule will also delete all
the Breakpoints associated with that record, except for any Breakpoints that are being used by a related
Variation. Scripts will be provided as part of this change, to allow for Org cleanup of any existing
Breakpoints orphaned by previously deleted Interpretation Rules.

**Configuration Requirement** : **Optional**\
**User Story Reference Number(s):** SC-35078

### Integrated Import Tool Refinements <Badge color="gray">New</Badge>

Thanks to recent updates, the Integrated Import Tool can identify and exclude Timesheets and Timesheet
Entries created or updated by other integration processes (such as Field Service) from being populated
with External IDs via Scheduled Jobs.

New Status and Error Messages have also been added to Imported Records to provide more precise
feedback in scenarios where import has failed due to missing or incorrect Integration Import User
credentials. This configuration is mandatory for the use of Integrated Import Tool functionality.

Additionally, changes have been made to how Import Tool automation handles Org identification to
ensure a more seamless integration experience.

**Configuration Requirement** : **Conditionally Compulsory** (mix of compulsory & optional upgrades if Integrated Import Tool has been implemented - no configuration required if not implemented.) **User Story Reference Number(s):** SC-36389, SC-36412, SC-36362

### Updates for Page Layouts <Badge color="gray">New</Badge>

Due to a number of functional changes over the course of the current Release, updates have been made to the fields displayed on Page Layouts across a number of records.

A new OnCost Settings section has been added to the Temp Assignment Page Layout. Industry, Risk Classification and Employment Cost Template Group fields have been added to this section, and existing Location and Rate Calculator fields have also been moved to this new section.
The Timesheet Activity Project Code Page Layout has been updated so that the Client field is no longer displayed, and the Template Group object has been assigned Page Layouts that are specific for each Template Group record type.

Work has also been completed to convert Visualforce pages into Lightning Web Component (LWC) pages. This has been implemented to take advantage of the heightened security standards offered as a part of Salesforce's upgraded security models.

Existing buttons have been converted to LWC Actions with built-in validation messages displayed on screen as actions are completed. When a LWC button is selected, a pop-up window will be launched to confirm the action selected and validate the success or failure of the action, before directing users to return to the original screen and refresh the page to view updated data.

A number of Assignment, Account and Invoice Page Layouts have now been updated with LWC Action buttons replacing the existing buttons to uplift and streamline functionality. The Create Rate Calculator button has also been removed from the Assignment record, as a part of these Page Layout cleanup activities.

**Configuration Requirement**: **Compulsory** **User Story Reference Number(s):** SC-33425, SC-36123, SC-36125, SC-36134, SC-36273, SC-36179

### Enhance Data Processing and Validation with New Integrated Import Tool <Badge color="gray">Update</Badge>

The new Integrated Import Tool is now available for use. This tool has been created to provide an
enhanced data import experience thanks to updated features enabling data to be processed at higher
volumes with greater complexity. New control and validation features are also offered, along with more
agile customisations. A key feature of the integration is the ability for data import features to be scaled
and customised according to business requirements. Jitterbit integration also enables users to receive
automatic feature updates deployed directly to their Org, without the need to manually install package
updates.

This new version of the Import Tool exists separately from the original Import Tool, and has been
integrated directly into existing Salesforce UX. It currently supports data import for Timesheet, Timesheet
Allowance Item and Pay Transaction record types.

Further improvements have been implemented for those already utilising the Integrated Import Tool, to
refine system processes for a better import experience.

New validations have been implemented to prevent data from being uploaded more than once using the
same CSV. Updates have been made to further improve the capacity to process higher volumes of data
for Timesheet Entries, Timesheet Allowances and Pay Transactions using Bulk API.

Existing validations have been amended to ensure that commas cannot be inserted when External IDs
are populated, and changes have been made to the Scheduled Jobs responsible for generating and
populating the External IDs used as unique identifiers by the Integrated Import Tool. Updates to
Timesheet and Timesheet Entry records will now only be triggered when there are records ready to be
populated, and will only run for records up to 90 days old. New Scheduled Jobs have also been created to
populate External IDs for Assignment, Payee, Payee Leave Rule, Payee Allowance and Project Code
records.

**Configuration Requirement** : **Conditionally Compulsory** (mix of compulsory & optional upgrades if Integrated Import Tool has been implemented - no configuration required if not implemented.)\
**User Story Reference Number(s):** SC-31308, SC-35850, SC-35966, SC-35967, SC-35968, SC-35970, SC-35969, SC-35877, SC-35878, SC-35879, SC-36293, SC-36351

### Updated Bulk Entry Options for Payroll Reconciliation <Badge color="gray">New</Badge>

A new screen flow has been created to enable the upload of CSV files when
completing Payee Aggregate Reconciliation for FBT. Once uploaded, automation will attempt to format
the CSV, then validate and import the data. Upon successful import, one Reconciliation Item will be
created for each row of data imported, and data will be displayed on the screen flow UI with editable YTD
values.

**Configuration Requirement** : **Optional** **User Story Reference Number(s):** SC-34959

### Updates to Permission Set Access Levels & Security <Badge color="gray">Update</Badge> <Badge color="gray">New</Badge>

Over the course of this Release, a number of changes have been implemented for
Permission Sets, including updates to existing Permission Sets, associated Licences, and the introduction
of new Permission Sets.

In order to enable greater flexibility and access control, individual product Permission Sets have now
been created and packaged with access to all product Fields and Objects. Please be advised that
additional configuration is required to enable access to Standard Salesforce Objects and Fields, to
ensure continued access for all Payroll activities.

For any Org utilising Permission Sets to provision access, please reach out to your 2cloudnine Partner or
representative to discuss the activities required to update access levels.

A Community Plus Permission Set has been created for use with Orgs utilising Customer Community
Plus licences, to ensure continuity of access across all licence types without the need for the creation of
additional custom Permission Sets. All Orgs with Community Plus licences implemented will need to
ensure that Sharing Settings have been set up according to Salesforce guidelines, in order to retain full
Read and Modify access to required objects and fields.

Permission Sets for the Employee Community have also been updated to align with new naming
conventions. The existing Approver User Permission Set has been renamed to the 2cloudnine Approver
User Permission Set, and the Employee Community Permission Set is now referenced as the 2cloudnine
Employee Community Permission Set. Access levels have also been updated, to ensure new Permission
Sets provision access to all required functionality.

Further changes have been implemented to ensure continued access for Guest Users when creating
Community Users from Contact Records using particular 3rd party software. All Permission Sets assigned
to users requiring automatic Community User creation when Contacts are added will need to be updated
to enable Custom Metadata Types for Community Settings.

Additionally, existing Payroll Permission Sets have been updated to include access for Rate Calculator
Fields and Record Types, as well as new Payroll Fields and Record Types added in recent releases.

**Configuration Requirement** : **Conditionally Compulsory** (compulsory upgrades if Permission Sets in use, optional upgrades also available.)\
**User Story Reference Number(s):** SC-36218, SC-35527, SC-36153, SC-36245, SC-36106, SC-36182, SC-36222, SC-36235, SC-36238

### Important Notice for Desert Flame Upgrades <Badge color="gray">New</Badge>

The latest version of 2cloudnine Payroll has been developed to include multiple
improvements to functionality, access and security, as documented on the following pages.

Before planning for upgrade, please be advised that there are several core 2cloudnine packages that
MUST be upgraded concurrently with Payroll, due to functionality interdependencies.

### Introduction of Alternate MPR Functionality <Badge color="gray">New</Badge>

Improvements have been made to provide more flexibility when organising your
Minimum Pay Rates (MPR). These allow you to create child records to a parent Minimum Pay Rate for
creation of Assignment Rates related to Project Codes and Timesheet Activities. Previously, you had to
use the Assignment Rate Template Group, now you can use child Minimum Pay Rates to define sets of
rates that are needed to be created for the Project Code/TSA combination. You are also able to determine
a different Pay Rate for child records.

Furthermore, we have also allowed the ability to specify particular Pay Codes that have a differing rate to
the standard Minimum Pay Rate, using the Pay Code field on the Minimum Pay Rate record (previously
labelled Allowance Pay Code Field). For example, if you have a higher duties Pay Code that needs a
different rate, you are able to create a Minimum Pay Rate for this Pay Code which will be used instead of
the parent Minimum Pay Rate for the Assignment Rate automation. We have also made troubleshooting
easier by relating the Minimum Pay Rate record used during Assignment Rate Automation to the
Assignment Rate record when it is created.

When using Parent and Child Minimum Pay Rate records you will need to transform all Template
Assignment Rates into Child Minimum Pay Rates and archive all existing Assignment Rates within the
Assignment Rate Template Group. This functionality is unable to be used with both child records and
Assignment Rates within the Assignment Rate Template Group.

Existing MPR functionality (i.e. Update Rates) may still be utilised to manage the creation and update of
Assignment Rates, but upgrading to the new Alternate MPR structure is recommended for superior
processing and general feature enhancements. Please reach out to your 2cloudnine Partner or
representative for support prior to upgrading, as a number of data transformation activities are necessary
to align existing data with the new model.

**Configuration Requirement** : **Optional**\
**User Story Reference Number(s):** SC-35740, SC-35605, SC-36171, SC-36175

### New Enhanced Import Type for Integrated Import Tool <Badge color="gray">New</Badge>

The Integrated Import Tool has been upgraded to enable Enhanced Import Types,
allowing users to import data using the customised Enhanced CSV Templates available for Timesheet
and Allowance Imported Record Types.

The Enhanced Import Type for Timesheets has been customised to exclude data related to Paid Breaks
and Employee Comments from being imported, while Enhanced Allowance Imports are customised to
exclude references to the related Timesheet External ID. The Enhanced Import Type is not currently
available for Pay Transaction Imported Records.

The Enhanced picklist value is now available for selection from the Import Type field when creating or
editing Imported Records.

**Configuration Requirement** : **Compulsory** (if using the Integrated Import Tool) **User Story Reference Number(s):** SC-35973

### Removal of Import Tool Legacy Tabs <Badge color="gray">New</Badge>

With the introduction of the new Integrated Import Tool, clean-up actions have been
implemented to remove outdated legacy Import Tool tabs from the 2cloudnine Import Tool app.

Users who have upgraded from the original Import Tool to the new Integrated Import Tool will notice the
Timesheet Import Tool, Pay Transaction Import Tool, and Assignment Import Tool tabs have been
removed, as imports completed via the Integrated Import Tool will utilise the Import Records object to
facilitate all data imports.

**Configuration Requirement** : **Compulsory** **User Story Reference Number(s):** SC-36162

### Changes to General Ledger Journal creation process <Badge color="gray">New</Badge>

A new automation has been created to replace the existing functionality used for the
creation of Cost of Payroll and Leave Accrual Journals. This functionality may be utilised for Orgs that are
unable to activate Process Builders due to the changes made by Salesforce regarding their use in the
future.

**Configuration Requirement** : **Conditionally Compulsory**\
**User Story Reference Number(s):** SC-36140, SC-36243

### Take Advantage of Optimised Assignment Rate Management

Expired Assignment Rates may now be easily managed, thanks to a new field added to the Assignment
Rate object. The field Expiring AR Status can be used to create filtered List pages for the Assignment
record, so that the status of Assignment Rates may be determined at a glance.

The Status of this field will be automatically populated when Rate Updates occur to reflect whether an
Assignment Rate is Expiring or has Expired. Any records that cannot be expired automatically will be
flagged with the Status of Expiring Failed.

A new field has been added to enhance filtering and optimise processing times for Minimum Pay Rate
(MPR) automation. The Archiving Status field may be populated on Assignment Rates manually, by data
load or via custom process, to ensure records are excluded from future MPR updates.

**Configuration Requirement** : **Conditionally Compulsory**\
**User Story Reference Number(s):** SC-33686, SC-33685, CI-239618

### Utilise New Automation for creation of Invoice Calendar Periods

As per the existing functionality for Calendar Period creation, 2cloudnine Payroll now has the capability to
automatically create Calendar Periods for Invoice Calendars triggered via third-party applications.

The new field Generate Invoice Calendar Periods will be automatically populated when the system
detects an Invoice Calendar created by a third-party integration. The Invoice Calendar Id will be captured
for the new record, and new Invoice Calendar Periods will be created and related to the Calendar.

**Configuration Requirement** : No configuration required. **User Story Reference Number(s):** SC-35575

### Adopt Enhanced Timesheet Processing

Enhancements have been made to the way that Timesheets with related Assignment Rates are
processed, to ensure a more seamless experience with integrated solutions.

Changes have been implemented to ensure that the Status of unprocessed Assignment Rates does not
impact the success of Timesheet Interpretation. This mitigates the dependency for synchronisation
between the insertion of Timesheets via integration, and the creation of Assignment Rates by system
automation, to deliver faster and more effective Timesheet Interpretation.

**Configuration Requirement** : **Compulsory**\
**User Story Reference Number(s):** SC-35353

### Customise Field Labels on Pay Advice PDFs

Further customisations are now available to tailor how data is displayed on Pay Advice PDFs.
Users will be able to override the default names of the field labels for Payroll ID, Total Earnings and Total
Net fields. Relabelling these fields enables greater flexibility, and ensures any PDFs generated for
Employees and/or Contractors report more suitable descriptions for payments received.

**Configuration Requirement** : **Compulsory** **User Story Reference Number(s):** SC-36040

### Automate Picklist Value Enablement for Payee Allowance Templates

Payee Allowance Templates have been uplifted to ensure that the picklist value Rate Per Quantity
Worked is enabled automatically upon installation. Upon initial introduction previously, this value
required manual enablement before becoming available for all record types.

**Configuration Requirement** : **Optional**\
**User Story Reference Number(s):** SC-36067

### Minor Updates

Minor updates in the following areas have also been provided. There are no configuration requirements
and these items will become available on installation of the package.

#### Timesheet Processing and Interpretation <Badge color="green">update</Badge> <Badge color="gray">New</Badge>

* Minor enhancements have been made to Broken Shift Logic, Frequency calculations, Sleepover Interpretation and Variations to improve general functionality.

  **User Story Reference Number(s):** SC-36632, SC-36658, SC-36659, SC-36678, SC-36744, SC-36186

* Changes have been made to ensure that Project Codes are more accurately associated with Timesheet Entries occurring across midnight. Previously, some instances were identified where Project Codes were not populated when Time was entered twice for the same day. This issue is now resolved.

  **User Story Reference Number(s):** SC-36272

* New validations have been created to prevent Interpretation Rules from being Finalised without all Standard Hours populated, to avoid errors being generated during Timesheet processing.

  **User Story Reference Number(s):** SC-35287

* New Validations will cause Timesheets to fail if the associated Interpretation Rule does not have defined Pay Code Caps for all related Breakpoints. A Debug Header has been created to inform Payroll Users of the missing data, so that the issue can be corrected prior to the creation of Pay Transactions.

  **User Story Reference Number(s):** SC-34537

* A new Debug Header has been added to flag any instances where Assignment Rates cannot be identified for Interpretation Breakpoints during Timesheet processing.

  **User Story Reference Number(s):** SC-35917

* Interpretation logic for Minimum Paid Hours has been refined to ensure Time of Day Breakpoints consider the Standard Minimum Paid Hours during calculations.

  **User Story Reference Number(s):** SC-35846

#### Pay Batch Manager

* A security issue was preventing the batch from running which updates the 'Became Most Recent' fields on Payee Aggregates and the 'Current Leave Balance' field on Payee Leave Rules after a Payment File has been Released. This has been resolved.

  **User Story Reference Number(s):** SC-36430

* An error has been resolved that was preventing the 'Client' filter from being applied correctly during Pay Batch creation if the Client filter was populated in Step 1 of the Pay Batch Creation process.

  **User Story Reference Number(s):** SC-36441

* Updates have been made to ensure that the Pay Batch Manager Bulk Add feature has the capability to add auto-pay Employees to existing Pay Batches in all scenarios.

  **User Story Reference Number(s):** SC-35719

* Pay Batch Manager optimisations have been completed to ensure the Status listings for related Payment Files reflect the most up-to-date information.

  **User Story Reference Number(s):** SC-34153, SC-35501

#### Minimum Rest Interpretation

* Updates have been implemented to LWC's for the Interpretation Rule Builder to address a rare Break Loading, Minimum Rest and / or Frequency component error generated when attempting to Finalise new Interpretation Rules.

  **User Story Reference Number(s):** SC-36394

* Adjustments have been made to Minimum Rest calculations for same day Entries and Overnight Logic.

  **User Story Reference Number(s):** SC-35167, SC-35560

* Changes have been made so that Minimum Rest Breakpoint application is assessed the same way for all Timesheet Entries, regardless of whether they are populated on the same Timesheet.

  **User Story Reference Number(s):** SC-35858

#### Broken Shift Interpretation

* Adjustments have been made to Broken Shift Logic to address an instance where Broken Shift entitlements were linked with a duplicated Timesheet Entry without a Broken Shift Timesheet Activity. This issue is now resolved.

  **User Story Reference Number(s):** SC-35074

* Updates have been made to improve the Interpretation of Broken Shift Timesheet Entries crossing midnight.

  **User Story Reference Number(s):** SC-35373, SC-35563

#### Leave and Allowance Interpretation

* Leave Breakpoints entered in the Interpretation Rule Builder will be displayed with the name of the related Leave Rule, to simplify troubleshooting and identification of Breakpoints.

  **User Story Reference Number(s):** SC-35328

* Logic has been updated to ensure that Daily Allowances are only processed once per day during Timesheet Interpretation, regardless of the amount of Entries each day that meet the qualifications for Daily Allowances.

  **User Story Reference Number(s):** SC-34304

* Hourly and Shift Time Calculation Methods have been modified so that Overnight Breakpoints are assessed separately from Leave Breakpoints.

  **User Story Reference Number(s):** SC-35174

#### Overtime Interpretation

* Frequency Overtime logic has been enhanced for multi-entry days to ensure Overtime is attributed to Entries in the order that they occur.

  **User Story Reference Number(s):** SC-35561

#### Pay Transactions

* General improvements have been made to the Clone Pay Transaction functionality available when processing Adjustments using the Pay Batch Manager.

  **User Story Reference Number(s):** SC-35133

* Updates have been made to the way automation populates the Payroll Processed Date on Superannuation Pay Transaction records, to ensure the necessary data is identifiable and reportable.

  **User Story Reference Number(s):** SC-35155

#### Rate Calculator

* Rate Calculator Validation will now provide the reference number for any relevant Debug Headers generated if data errors are identified for Rate Calculators or related records.

  **User Story Reference Number(s):** SC-35083

#### Rates Automation

* Validations for Rates Automation have been improved. The Create Assignment Rates LWC now allows the automatic creation of Assignment Rates without Award Levels present, so long as the Award Classification and Assignment Rate Template Group and Interpretation Rule are populated.

  **User Story Reference Number(s):** SC-35511

#### Superstream Reporting

* Updates to the contact information listed on Superstream exports ensure that any mobile numbers recorded on the Employee Contact are reported where needed.

  **User Story Reference Number(s):** SC-32566

#### Timesheet Allowances

* Updates have been made to optimise the way data is displayed within the Allowances tab of the Timesheet Manager.

  **User Story Reference Number(s):** SC-35792

#### Payee Leave Events

* Improvements have been made for Payee Leave Events, to ensure the status is automatically populated during Timesheet Interpretation.

  **User Story Reference Number(s):** SC-33729

#### Invoice Emails

* Enhancements to the efficiency of emailing Invoice PDFs in bulk via the 'Send Email' button available when viewing Invoices in List View.

  **User Story Reference Number(s):** SC-33292, SC-35845

<Tip>
  Take advantage of these new features and improvements now. Talk to your Partner Provider or System Administrator about upgrading so you can experience the benefits of the **Desert Flame '24 Release** for yourself.
</Tip>
