> ## 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. # Banksia Release Notes The Banksia ’21 release for 2cloudnine Payroll has a number of exciting enhancements that are designed to improve your payroll experience. Below is an outline of the new features and updates that are included in the release. ### Create and Allocate Work Schedules Efficiently Managing schedules and rosters can be a complex and time-consuming process. With the introduction of *Work Schedules* functionality, users will be provided with advanced tools to greatly assist in reducing the workload normally involved in creating and applying *Work Schedules* for employees. With this new feature, users will be able to easily identify and create shift patterns detailing essential information such as *Start* *Time, End Times, Breaks* and *Total Hours* that will apply to a *Work Schedule* . These patterns can then be automatically replicated for an extended period of time resulting in a *Work Schedule* that details all shifts that will apply within a defined period. The *Work Schedules*, once all shift details are correct, can then be easily allocated against one or more *Assignment* records. Further, provided their time periods do not overlap, an *Assignment* can have multiple *Work Schedules* applied to it. For ease in management over shift days and shift times, users will be able to view, from the *Assignment*, all allocated *Work Schedules* and the individual shifts held within the schedule. This feature was released as a beta version in the Lilly Pilly ‘21 release. The non-beta version is now available. **Configuration Requirement** : **Optional**\ **User Story Reference Number(s):** SC-22924 (SC-31296, SC-31302, SC-31537, SC-31538, SC-31539, SC-31540, SC-31541, SC-31542, SC-31778, SC-31961, SC-32019, SC-32030, SC-32067, SC-32068, SC-32071, SC-32110) ***Related Documentation*** | Document | Document Type | Description | | :----------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Work Schedules Quick Reference Guide Index](/qrgs/index) | Quick Reference Guide - Index | An index document that lists and provides links to all Quick Reference Guides relating to Work Schedules. | | [Managing Work Schedules Key Information](/qrgs/work-schedules/qrg-managing-work-schedule-key-information) | Quick Reference Guide - Key Information Document | Outlines useful information relevant to the Work Schedule functionality and its setup at the system level. The document includes definitions, pre-requisites and other non-instructional information relating to Work Schedules. | | [Create Work Schedules](/qrgs/work-schedules/qrg-create-and-open-work-schedules) | Quick Reference Guide - Task Instructions | How to launch the Work Schedule Manager and create a new Work Schedule record. | | [Validate, Publish and Unpublish Work Schedules](/qrgs/work-schedules/qrg-validate-publish-and-unpublish-work-schedules) | Quick Reference Guide - Task Instructions | How to validate, publish and unpublish Work Schedules through the Work Schedule Manager. | | [Create and Manage Shift Records](/qrgs/work-schedules/qrg-create-and-manage-shift-records) | Quick Reference Guide - Task Instructions | How to create and manage Shift Records using the Work Schedule Manager. | | [Manage Weekly and Daily Shift Allocations](/qrgs/work-schedules/qrg-manage-weekly-and-daily-shift-allocations) | Quick Reference Guide - Task Instructions | How to allocate and manage weekly and daily shifts to a Work Schedule record through the Work Schedule Manager. | | [Manage Shift Allocations](/qrgs/work-schedules/qrg-manage-shift-allocations) | Quick Reference Guide - Task Instructions | How to allocate and manage shifts to a Work Schedule record through the Work Schedule Manager. | | [Searching and Opening Existing Work Schedules](/qrgs/work-schedules/qrg-create-and-open-work-schedules) | Quick Reference Guide - Task Instructions | How to launch the search and open an existing Work Schedule using the Work Schedule Manager. | | [Create and Manage Assignment Schedules](/qrgs/work-schedules/qrg-create-and-manage-assignment-schedules) | Quick Reference Guide - Task Instructions | How to create and manage **Assignment Schedules** to relate a **Published Work Schedule** to an **Assignment**. | The above related documentation also applies to the other Work Schedule related items listed within these Release Notes. ### Apply Work Schedule Information to Payroll Building on the functionality to effectively create and manage *Work Schedules*, existing payroll functions have also been updated to extend this feature right through to payroll. Now, where a *Work Schedule* is applied to an *Assignment*, key information held within the schedule will be used to enhance the payroll experience. Employees that use *Timesheets* will benefit from the information held within their allocated *Work Schedule* being carried forward to provide default values on their *Timesheets.* This change is aimed at facilitating more accurate reporting of actual hours worked, while making the submission and approval of *Timesheets* an improved and timely experience for both the employee and *Timesheet* approvers. Further, a new *Auto Pay Type* has been introduced for those employees not using *Timesheets* . Users will now have the additional option of calculating pay based on the scheduled hours. When applied during payroll, this autopay function will take information held on the *Work Schedule* and generate *Pay* *Transactions* based on the employee’s scheduled shift. Also, the auto pay functionality now has inbuilt tools to handle when a scheduled shift falls on a public holiday. Where this occurs, depending on the shift settings, the payment of the public holiday will automatically be transacted as either a paid day off or at the working public holiday rate. This feature was released as a beta version in the Lilly Pilly ‘21 release. The non-beta version is now available. **Configuration Requirement** : **Optional**\ **User Story Reference Number(s):** SC-22924 (SC-30740, SC-31904, SC-31905, SC-31906, SC-31907, SC-31909) ### Introduction of the Work Schedule Manager To simplify the *Work Schedule* functionality introduced as a beta version in the Lilly Pilly ‘21 Release, a new *Work Schedule Manager* has been provided. With the addition of this new tool, the complexities in managing *Work Schedules*, and their associated records which fall across multiple objects / record types, will be minimised. Along with simplifying the creation or modification of *Work Schedule* related records, the *Work Schedule Manager* will additionally provide an improved capability that enables users to search for existing *Work Schedules* and bulk allocate shifts to records. **Configuration Requirement** : **Conditionally Compulsory** Overall this item is optional, however, it is required when the Work Schedules functionality is in use **User Story Reference Number(s):** SC-22924 (SC-31770, SC-32397) ### Extend Work Schedules to Handle Part Day Leave Events There have been further improvements to the *Work Schedule* functionality in relation to how *Autopay* employees have their *Payee Leave Events* calculated. Initially, in the beta version of *Work Schedules*, when an *Assignment* is using both *Work Schedules* and *Autopay*, the number of hours applied to associated *Payee Leave Events* were automatically determined based on the hours of the *Work Schedule Entry* that applied to the same date. This did not cater for employees that were only taking leave for part of the shift. The ability to override the automatically determined hours has been introduced which will allow employees / users to define a *Part Day Leave Event* . When the override applies, the leave will be determined based on the hours defined on the *Payee Leave Event* . The balance of the *Work Schedule* *Item* hours less the *Payee Leave Event* hours will be paid as per the *Work Schedule Item* . This improvement has no impact on *Assignments* that are not using the *Autopay* and *Work schedules* functionality. **Configuration Requirement: Conditionally Compulsory** Overall this item is optional, however, it is required when the Work Schedules functionality is in use. **User Story Reference Number(s):** SC-22924 (SC- 32192) ### Improvements for Publishing and Unpublishing Work Schedules Once a *Work Schedule* has been published, there may be instances where users need to make changes to the record. To enable this, a new feature has been introduced to improve the beta version of *Work* *Schedules* and allow a user to unpublish a *Work Schedule* that has not already been related to an *Assignment Schedule* . This will allow users to then easily edit, or even delete, *Work Schedule* related records before republishing them for use. To prevent data corruption, in the event that the *Work Schedule* has been related to an *Assignment Schedule*, the unpublished function will not be available. Further to the above, new validation has been introduced to ensure that correct information is collected during the process of publishing a *Work Schedule* . **Configuration Requirement** : **Conditionally Compulsory** Overall this item is optional, however, it is required when the Work Schedules functionality is in use. **User Story Reference Number(s):** SC-22924 (SC-32093, SC-32192) ### Populate Default Values on Existing Timesheets From Work Schedules As part of the beta version of the *Work Schedule* functionality included in the Lilly Pilly ‘21 Release, there were changes introduced to help improve *Payroll* related processes based on the information held within a *Work Schedule* . One of these changes applied to generating pre-populated *Timesheets* based on the *Work* *Schedule Items* defined. Further improvements have been made to extend this functionality so now, if an *Assignment Schedule* relating an *Assignment* to a *Work Schedule* was created or updated, any existing unedited *Timesheets* with a Status of New will have their default values updated. Furthermore, if the *Public Holiday* defined on an *Assignment* is updated, the value held within any related *Assignment Schedules* will also be updated to match. This will in turn trigger an update of related *Timesheets* based on the *Work Schedule* / *Public Holiday* information. **Configuration Requirement** : **Conditionally Compulsory** Overall this item is optional, however, it is required when the Work Schedules functionality is in use for Timesheeting. **User Story Reference Number(s):** SC-22924 (SC-32126, SC-32443, SC-32353, SC-32075) ### Updates to Pay Batch Manager to Support Work Schedules To extend the *Work Schedules* functionality included in the Lilly Pilly ‘21 Release, the *Pay Batch Manager* *Manual Adjustment* functionality has been enhanced to also include a visual representation of any *Work* *Schedules* that apply for the *Payee Pay Batch / Pay Calendar Period* . This update means that for any *Payee* that has an *Assignment(s)* with related Assignment Schedule(s), the user will be able to view the scheduled hours of work, for that *Pay Calendar Period*, in a calendar format. This *Work Schedule Calendar* will provide ease in verifying Pay Batch calculation and adjustment details. **Configuration Requirement** : Not Required **User Story Reference Number(s):** SC-32314 (SC-32091) ### Meet Stapled Superannuation Legislative Requirements New New functionality has been introduced to assist in meeting the new Stapled Superannuation legislative requirements that come into effect on the 1st November 2021. A new Super Stapling button has been introduced to the Payee object. In the event that the Employee’s Stapled Super information needs to be retrieved from the ATO Online Services, this button can be used to determine if additional details need to be sent, via the Single Touch Payroll (STP) functionality, to allow the Employer access to the Employee’s Stapled Super information. If required, any required details will be sent in the form of a zero value STP Update. From there, the User can complete the normal STP Validation via the STP Manager and send the required update to the ATO. Once successfully received by the ATO, Users will be able to login to the ATO Online Services and lookup the Employee’s Stapled Super information. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-33022 ***Related Documentation*** | Document | Document Type | Description | | :----------------------------------------------------------------------------------------------------- | :---------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------- | | [Checking Stapled Superannuation Information](/qrgs/uncategorised/qrg-checking-stapled-superannuation) | Quick Reference Guide - Task Instructions | How to request Stapled Superannuation through the ATO using the Super Stapling Quick Action button on the **Payee** record. | ### New Deduction Calculation Type Improvements to the *Payee Deduction* functionality have been made to extend the *Deduction Rate Types* available. A new option, *Percentage of Taxable Gross*, has been introduced which will consider the total of all *Payment* and *Allowance P* ay *Transactions*, where the *Pay Code* is not exempt from withholdings (PAYG/GST) when performing the calculation to determine the deduction amount. **Configuration Requirement** : **Compulsory User Story Reference Number(s):** SC-31688 ### Apply One-Off Allowances and Deductions Directly During Payroll Update Enhancements to the *Pay Batch Manager’s Manual Adjustment* functionality in relation to one-off *Allowances* and *Deductions* have been made. Previously the users would have to create the respective *Allowance Records* and/or *Deduction Records* prior to processing them through the *Pay Batch* . Now, users will be able to save time by eliminating the need for *Allowance Records* and *Deduction Records* for one-off transactions and instead they will be able to create them through the *Manual Adjustment* page. To support this functionality, validation on the Payee Deduction Record that ensures the *Super* *Contribution Type* field is populated has been removed. Instead, the field will automatically populate *as* *either Salary Sacrifice* or *Voluntary Additional* based on if the defined *Pay Code* has a *Deduction Type* of *Pre-tax Deduction* or *Post-tax Deduction* respectively. Further to the above, the *Manual Adjustment* functionality has been extended to also allow for the definition of *Project Codes* against adjustments raised. **Configuration Requirement** : **Conditionally Compulsory** (Organisations that have 2cloudnine Payroll Australia Extension package installed must update to the latest version) **User Story Reference Number(s):** SC-31162, SC-31783, SC-32728 ### Customise the Payee Pay Batch’s Total Quantity Calculation Previously, the calculation of the *Payee Pay Batch’s Total Quantity* incorporated all *Pay Transactions* using *Payments Pay Codes* . To allow organisations to have more control over what is included in the *Total* *Quantity*, new functionality has been introduced to give them the ability to customise which *Pay* *Transactions* will be applied to the value. This functionality will allow users to determine, at a *Payment* or *Allowance Pay Code* level, if *Pay Transactions* that use the *Pay Code* will be added to the calculation. **Configuration Requirement** : **Compulsory User Story Reference Number(s):** SC-32094 ### Improved Overnight Interpretation Capability To support Modern Award adherence, the *Time Interpretation* logic that is used for situations where a shift occurs overnight has been extended. In addition to the existing overnight logic, users will be able to define if an overnight shift should be paid at the following day’s rate based on when the shift starts, or if it will be paid based on the breakpoint that the majority of the hours fall within. These new overnight options can be defined on a per-day basis via the *Interpretation Builders* . **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-31915, SC-32351 ### Define Alternative Pay Code for Saturday Frequency Breakpoints Further to the above mentioned changes, the *Interpretation Builders* have also been updated to cater for specifying different *Pay Codes* that will allow when *Frequency Breakpoints* are applied to Saturdays. This improvement means users can specify the standard *Pay Codes* to use plus optional alternative *Pay Codes* for Saturdays, Sundays and Public Holidays. If the user chooses not to populate the optional *Pay Codes*, the standard *Pay Code* will be used for all days the *Frequency Breakpoint* applies. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-31682 ### Ability to Override the ATO Income Classification Application New To ensure all *Payee Aggregates* are prepared with the correct *ATO Income Classification*, and to prevent errors in lodgments for Single Touch Payroll (STP), an update has been made to how *ATO* *Income Classification* information is determined and used during *Pay Batch* processing. The initial identification of the *ATO Income Classification* applied to a *Payee Pay Batch* will continue to originate from the relevant *Payee’s Withholding Record.* This value will then be copied down to the relevant *Payee* *Opening Balance* and *Pay Transaction* records. Users will be able to apply an override to the *ATO Income* *Classification* directly on *Opening Balance* and *Pay Transaction* records if required. With the introduction of these overrides, and to prevent conflicting *ATO Income Classification* details being provided for STP reporting, the *ATO Income Classification* held on the *Pay Code* will no longer be used. Furthermore, to ensure an *ATO Income Classification* is always provided within STP reporting, in the event that the record applies to a GST contractor, or the value is blank at the time of *Pay Batch Finalisation*, a default value of *Not Reportable* will be applied. **Configuration Requirement** : **Compulsory** This configuration is to be completed by a 2cloudine Payroll consultant as scheduled. **User Story Reference Number(s):** SC-32521 ### Define Opening Balances as Employer Additional Superannuation New New functionality has been introduced to allow Users to indicate on a *Superannuation Withholding* *Payee Opening Balance* if the value should be applied as *Employer Additional Superannuation* . When indicated, any corresponding *Payee Aggregates,* and in turn, Single Touch Payroll (STP) reports will identify the values as *Employer Additional Superannuation* . **Configuration Requirement** : **Compulsory** This configuration is to be completed by a 2cloudine Payroll consultant as scheduled. **User Story Reference Number(s):** SC-32685 ### View Key Information Directly From Payee Aggregate Records New New formula fields have been introduced to the *Payee Aggregate* records to display key information from related records so that it can be viewed from within one location. This will assist in reviewing *Payee* *Aggregate* results if the need arises. **Configuration Requirement** : **Compulsory** This configuration is to be completed by a 2cloudine Payroll consultant as scheduled. **User Story Reference Number(s):** SC-32968 ### General Updates to the Interpretation Builder Pages and Functionality There have been multiple improvements to the *Interpretation Builders* implemented to support ease in creating *Interpretation Rules* . These modifications extend the capability of the *Interpretation Builders* to ensure the functionality required for defining the various *Interpretation Breakpoints* and *Variations* is available. **Configuration Requirement** : **Compulsory User Story Reference Number(s):** SC-32264, SC-32311, SC-31617, SC-31680 ### Custom Set the Owner of Pay Transaction Records Record ownership is an essential part of the *Sharing Settings* functionality, however, ensuring the *Owner* is defined correctly on each record to meet an organisation's *Sharing Setting* requirements can be time-consuming. To assist in facilitating the efficient use of *Sharing Settings*, new controls have been introduced that allows System Administrators to define from where the owner of *Timesheet* related *Pay* *Transactions* (including *Timesheet Allowances* and *Timesheet Expenses* ), is derived. System Administrators will now be able to default the *Owner* as the user who created the record, the *Owner* of the related *Client* record or the *Owner* of the related *Assignment* record. **Configuration Requirement** : **Optional User Story Reference Number(s)** : SC-31525 ### Update to Timesheet related Pay Transactions for Payee Leave Events New An update has been made so that if a *Payee Leave Event* is related to a *Timesheet Entry* when the *Pay* *Transaction(s)* are created during *Timesheet Interpretation*, the *Payee Leave Event* field on the *Pay* *Transaction* is populated with the value on the related *Timesheet Entry.* **Configuration Requirement** : **Compulsory User Story Reference Number(s)** : SC-32157 ### Provide Greater Detail on Pay Advice Documents To allow for the creation of *Pay Advice* documents that have loading values separated from an employee’s ordinary hourly rate, improvements have been made to allow defining of different *Pay Codes* and *Assignment Rates* to be used for each loading component. Previously, only *Assignments* using the *AutoPay* option could specify their *Assignment Rates* at the level of detail to generate the necessary *Pay* *Transactions* to allow the higher level of detail on the *Pay Advice* . Enhancements have now been made to also cater for *Assignments* that use *Timesheets / Interpretation* *Rules* to determine the *Pay Transactions* created. The *Interpretation Builders* have been updated to allow for separate *Pay Codes* to be defined for the ordinary hours, casual loading and penalty loading. Where separate *Pay Codes* are defined, the *Time Interpretation* logic has been updated to create the necessary *Pay Transaction* to cater for the *Pay Advice* requirement. The logic will continue to use the *Pay Code /* *Assignment Rates* combination to determine the rates to be applied to the *Pay Transactions* so when in use, additional *Assignment Rates* will need to be created for the loading components. **Configuration Requirement** : **Compulsory User Story Reference Number(s)** : SC-30519 ### Provide Greater Detail on Invoice Documents In addition to the above detailed changes that will allow for *Pay Advice* documents to reflect the broken down rates of pay, the updates made can also allow for *Invoices* to be generated with the same level of detail. By default, only *Pay Transactions* generated for the *Pay Codes* specified for the ordinary hours will have Invoice Rates populated on them. Those generated for loading will have no Invoice Rate applied and will be set to not be invoiced. This means that *Invoices* will continue to generate with the same level of detail that they already have. If a higher level of detail is required, an additional setting on the *Invoice Setting* has been introduced to specify that related *Invoices* should provide the broken down level of detail. Where this is used, the *Pay* *Transactions* created for the loading components will have the *Invoice Rate* populated based on the defined value on the associated *Assignment Rate* and they will be set to be invoiced. **Configuration Requirement** : **Optional User Story Reference Number(s)** : SC-30519 ### Provide Greater Detail on a Timesheet’s Invoice Backing Sheet To provide more meaningful details to the Invoice recipients, there have been several improvements made to the existing package version of the Invoice Backing Sheet. Now, the Employee Notes that are included have been extended to not only cover comments made at the Timesheet level, but also those made at the Timesheet Entry level. Further, information about any Timesheet Allowances invoiced will also be provided on the Backing Sheet. In addition to the above, an option to extend the Approval History displayed on the Backing Sheet has also been introduced. Previously only the details on the final submission and approval for each Timesheet were included, however, there may be instances where a client requires the complete Approval History. To support this, a new option has been introduced to allow users to define, at an Invoice Setting level, if the Backing Sheet will include the full Approval History or only the final submission details. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-32389, SC-31929, SC-31902, SC-31660 ### Improved Invoice Creation Experience To provide users with improved functionality and time efficiencies while creating Invoices, updates have been made to the Invoice Generation Manager that will allow users to generate Invoices for multiple Invoice Entities at a time. Where previously Invoices were created on a per Invoice Schedule, per Invoice Entity basis, now users will be able to select the required Invoice Schedule then view, and multi-select from a full list of Invoice Entities that have items ready for invoicing. This update applies to both the Standard Invoice Filters and Transaction Filters invoicing methods. In addition to the above, to accommodate situations where the *Purchase Order Number* that is on the *Assignment* varies from the one of the *Pay Transaction*, updates have been made to the results table shown when *Transaction Filters* are used. Now the *Purchase Order Number* that is displayed will be derived from the *Pay Transaction* and not the *Assignment.* **Configuration Requirement** : Not Required **User Story Reference Number(s):** SC-31691, SC-32400 ### Greater Control Over Transactions included for Re-invoicing An enhancement has been made to the *Credit Re-invoice* page to assist users in working with the transaction lines that will be included within the new *Invoice* . The *Remove Transactions* feature allows users to select and *Remove Transactions* ( *Pay Transactions* or *Invoiceable Fees* ) from the list of transactions that are included when completing the Re-Invoice activities. As they are visually removed from the list, this will assist them in ensuring only the transaction lines required for the resulting invoice are handled. Where required, these removed transactions can then be picked up and handled separately in subsequent *Re-invoice* activities for the *Credit Note.* **Configuration Requirement** : Not Required **User Story Reference Number(s):** SC-32167 ### Automatically Update the Interpretation Rule on Timesheets New automation to streamline the process of updating the *Interpretation Rule* assigned to *Timesheets* has been provided. Now, when the *Interpretation Rule* defined on an *Assignment* is updated, all unprocessed *Timesheets* will also be updated to reflect the same *Interpretation Rule* . **Configuration Requirement** : Not required **User Story Reference Number(s):** SC-31076 ### Enable Bulk Delete of Timesheets A new feature to allow the bulk deletion of *Timesheets* that are not related to *Pay Transactions* has been introduced to the *Assignment* . When used, *Timesheets* related to the *Assignment* with a status of *New* and *Rejected* will be deleted along with any associated *Timesheet Entries, Payee Leave Events, Timesheet* *Items* ( *Timesheet Allowances* ) and *Expense* records. Additionally, there is the option to also include *Timesheets* with the status of *Submitted* and/or *Approved* in the bulk delete. Whether the *Submitted* and *Approved Timesheets* should be included in the deletion is defined on a per *Assignment* basis. To ensure data integrity, *Timesheets* that have related *Pay Transactions* will not be deleted with the bulk delete functionality. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-32125 ### Further Streamline Payee Allowance and Assignment Rate Updates The automation for creating *Payee Allowance Records* and *Assignment Rates* that was introduced in the Lilly Pilly ‘21 Release has been extended to provide further improvements in updating records based on changes to rate information. Improved functionality has been introduced to automatically identify *Assignments, Assignment Rates* and *Payee Allowance Records* that require updating based on changes to *Minimum Pay Rates* and *Template Group* . Updates will then be performed on an ongoing / scheduled basis. Further enhancements have also been included to allow the quicker update of records related to an individual *Assignment* for instances where waiting for the scheduled update to be performed is not suitable. These will also provide improved visual aids to allow the User to determine the progress of the update process while it is being performed. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-32255, SC-32257, SC-32265, SC-32266 ### Update to Terminology Customisation of Experience (Communities) Update An improvement to the custom label functionality that was introduced to allow the customisation of the terminology used within the standard *Experience (Communities)* components has been made. Previously, the same custom label related to the *Hours* values for both *Timesheets* and *Payee Leave Events* . Now, these have been separated to allow different overrides to be applied to *Timesheets* and *Payee Leave* *Events* . This update applies to both the *Employee and Approver Experience (Communities)* . **Configuration Requirement** : **Optional User Story Reference Number(s)** : SC-32334, SC-32674, SC-32754 ### Control if Leave Credits Are Available in Experience (Communities) New To provide more control over what *Leave* functionality is available within *Experience (Communities)*, an update has been made to define if *Leave Credits* are available. Now, a controlling field set on the *Leave* *Rule* will determine if an *Employee* can create, view and edit *Leave Credits* through the *Employee* *Experience (Communities)* . Likewise, the same field is used to determine if *Approvers* can view and approve / reject Leave Credits through the *Approver Experience (Communities)* . **Configuration Requirement** : **Compulsory User Story Reference Number(s):** SC-32560, CI-217796 ### Leave Capabilities Within Employee Experience (Communities) New General updates to the Leave functionality within *Employee Experience (Communities)* have been made to provide a better user experience when creating, editing and submitting *Leave Events.* Now, *Employees* have the ability to edit a newly created *Leave Event* without the need to re-enter / reload the page. Further, enhancements have been made to allow *Employees* to submit *Leave Events* for an *Assignment* that does not have an *End Date.* Additional updates have also been provided to improve how validation errors are handled within the page and the resulting impact on the *Employee* . **Configuration Requirement:** Not Required **User Story Reference Number(s):** SC-31488, SC-32348, SC-32565, SC-32239 ### Define Experience (Communities) Access to Future Dated Timesheets New The existing behaviour within Experience (Communities) is to only show Timesheets for the current calendar period and earlier. Now, new functionality has been introduced to allow Users to define, at a Timesheet Calendar level, if Employees will be able to view / edit / submit Timesheets for a future period. Likewise, Approvers will be able to view / approve / reject them. By default, Experience will continue to only show current and earlier Timesheets. If future dated timesheets are defined as visible on the Timesheet Calendar, only current or earlier Timesheets, plus those that fall within the time period defined, will be available. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-32996 ### Automatically Update the Primary Payee on the Contact Records To streamline the ongoing maintenance of the Primary Payee lookup field on the Contact record, new automation has been provided that will automatically update the selected record based on which Payee record is identified as the Primary Payee. This is particularly relevant when a Contact is related to multiple Payee records. **Configuration Requirement** : **Optional User Story Reference Number(s):** SC-31700 ### General Page Layout Updates to Payment Details and Pay Code Standard page layouts on the *Payment Detail* and *Pay Code* objects have been updated to add additional fields that were included in earlier releases, modify page layout level required field settings and remove fields that are no longer in use. **Configuration Requirement** : **Compulsory User Story Reference Number(s):** SC-32076, SC-31489, SC-31367 ### Minor Updates Minor updates in the following areas have also been provided. There are no configuration requirements, and these items will become available on the installation of the package. #### Contact, Payees and Assignments * A new validation has been introduced to prevent the deletion of a *Contact* record that is New related to one or more *Payees* User Story Reference Number(s): SC-32101 * A new validation has been introduced to prevent the deletion of a *Payee* record that is related New to one or more *Pay Transactions* User Story Reference Number(s): SC-32089 * Improvements to the triggers held on the *Assignment* object have been made to lower the New risk of hitting Salesforce governor limits when creating / updating *Assignments* User Story Reference Number(s): SC-32345 * The error message for the mandatory field validation on *Perm Assignment* has been updated New to include all current mandatory fields User Story Reference Number(s): SC-32408 * New lookup filtering on the *Interpretation Rule Template Group* lookup field on the New *Assignment* has been introduced so that only *Template Group* records with the record type of *Interpretation Rules* will be available User Story Reference Number(s): SC-32663 * Changes have been made to the *Assignment Rate / Minimum Pay Rate* functionality to New ensure it will also trigger when an update to an *Assignment* is made via custom code within the organisation ie workflows, process builders etc User Story Reference Number(s): SC-32887 * Updates have been made to the *Scheduled Job* for updating *Minimum Pay Rates* to ensure New that all records that require updating are selected to be updated User Story Reference Number(s): SC-32886 * Updates have been made to the *Assignment Rate / Minimum Pay Rate* functionality to New ensure that when changes to the *Assignment Rates* are made by the automated process, the *Assignments* are flagged as *Timesheets Pending Creation* so the *Create / Update Timesheets* *Scheduled Job* can make relevant changes to any *Timesheets* required User Story Reference Number(s): CI-21797 #### Payroll Calendars * The *Create Payroll Calendars* functionality has been updated to lower the risk of hitting New Salesforce governor limits when extending existing *Payroll Calendars* User Story Reference Number(s): SC-31956 #### Timesheets * The *Create Timesheet* functionality has been extended to cater for integrations requiring New *Timesheets* to be created without related *Timesheet Entries* User Story Reference Number(s): SC-32416 * The validations on *Timesheet Allowances* have been improved to ensure that *Maximum* New *Quantities* defined on the related *Payee Allowance Record* are adhered to User Story Reference Number(s): SC-31901 * Updates to the *Approver Notification* functionality have been carried out to ensure that when a rejected *Timesheet* is resubmitted, the *Approver* receives another notification advising of the resubmission User Story Reference Number(s): SC-31952 * Enhancements to the *Timesheet Import Tool* have been made so that the *Skip Manager* New *Approval* field on a *Leave Request (Payee Leave Event)* is automatically populated based on the same field on the related *Payee Leave Rule* User Story Reference Number(s): SC-31913 #### Time Interpretation * The *Pay Code Cap* functionality has been extended to cater for *Allowance Pay Codes* New User Story Reference Number(s): SC-32102 * Updates have been made to the *Interpretation Rule Calculation Logic* to provide for *Overtime* New *Allowances* User Story Reference Number(s): SC-32083, SC-31928, * The logic used when identifying the *Assignment Rate* to apply to a *Pay Transaction* has been New enhanced so that, in the event, there are multiple *Assignment Rates* identified, the one with the highest *Sort Order* will be applied User Story Reference Number(s): SC-31935 * The *Interpretation Rule Calculation Logic* has been updated to ensure the correct New interpretation for *Break Loading* is applied User Story Reference Number(s): SC-32429 * Improvements to the *Interpretation Rule Calculation Logic* have been carried out to handle New variations outside *Frequency Hours* User Story Reference Number(s): SC-32407 * Enhancements have been made to the *Interpretation Rule Calculation Logic* to allow for New partial payment of *Hourly Allowances* based on partial hours worked User Story Reference Number(s), SC-31337 * The *Interpretation Rule Calculation Logic* has been updated to cater for additional *Daily* and New *Frequency Hours* scenario User Story Reference Number(s): SC-32331 * *Timesheet Interpretation* related *Debug Logs* have been enhanced to improve details New provided when errors occur User Story Reference Number(s): SC-32230, SC-32228 #### Payee Exit * Updates have been made to the *Payee Exit Interface* to ensure the *Pay Rate* is displayed as a New number with 6 decimal places User Story Reference Number(s): SC-32434 #### Leave * Improvements to the *Leave Balance Transfer* functionality have been made to cater for New where the *Payee Leave Rule* that balance is transferring from is *Assignment Specific* User Story Reference Number(s): SC-32503 * Updates have been made to the *Leave Balance Transfer* functionality so that where multiple New *Payee Aggregate* records have been created at the same date/time, the record for the latest *Calendar Period* is selected when determining the balance available to transfer User Story Reference Number(s): SC-32955 * To accommodate Employees working split shifts, changes have been made to the validation New on *Payee Leave Events* to allow multiple *Payee Leave Events* with the same *Leave Type* to be created for the same day User Story Reference Number(s): SC-32962 #### Pay Advice * Refinements to the *Create Pay Advice* functionality have been provided to prevent the New creation of duplicate *Pay Advice Lines* where the *Leave Rate Multiplier* field on the *Pay* *Transaction* is blank User Story Reference Number(s): SC-32613 #### Payment Files * The *Pay Batch Manager’s Print Payment File PDF* capability has been extended so that the New PDF file can be generated irrespective of the *Approval Status* of the *Payment File* User Story Reference Number(s): SC-32159 #### Payee Aggregates * To ensure their relevant *Payee Aggregates* are calculated correctly, updates have been made New to accommodate Employees who move from being a *Working Holiday Maker* to any other *ATO Income Classification* within a financial year User Story Reference Number(s): SC-32617 * Improvements have been made to ensure when a *Payee* changes their *Superannuation* New *Fund* mid financial year, that the *Payee Aggregates* associated with both the new and previous fund are maintained and *Month to Date, Quarter to Date* and *Year to Date* values are calculated correctly User Story Reference Number(s): SC-32518, SC-32677 * Updates have been made to ensure that when a *Payee Pay Batch* is related to a combination New of *Superannuation Guarantee* and *Employer Additional Superannuation Pay Transactions*, the corresponding *Payee Aggregates* that are created during finalisation, reflect the correct superannuation type User Story Reference Number(s): SC-32519 * Improvements have been made to ensure that in the event of multiple *Payee Leave Rules* New applying to a *Payee Pay Batch*, during *Pay Batch Finalisation*, there is a *Payee Aggregate* record created for each *Payee Leave Rule* User Story Reference Number(s): SC-32683 #### Single Touch Payroll * To prevent ATO validation errors, *Single Touch Payroll* extracts have been updated so that New negative *Year To Date* Allowance or *Deduction* values will be replaced with zero User Story Reference Number(s): SC-32763 #### Invoiceable Fees * The *Create Transaction* functionality on the *Invoiceable Fee* has been updated to ensure the New correct *Invoice Setting* is applied to the new *Pay Transaction* User Story Reference Number(s): SC-32116, SC-32104 #### Invoicing * The *Compose Invoice Email* functionality has been updated to determine who the email is New sent from based on the *Send Invoice Email Setting* value * The *Invoice Email* functionality has been made to cater for sending *Expense* receipts / evidence as attachments with emails User Story Reference Number(s): SC-31563 * The *Re-Invoice* functionality has been updated to ensure users can edit the *Pay Code* on New transactions User Story Reference Number(s): SC-32505, SC-32340 * Updates have been made to the *Invoice Batch Manager* so that, when *Transaction Filters* are New used to generate *Invoices*, the *Pay Codes* that apply to the *Pay Transactions* displayed within the table are provided. User Story Reference Number(s): SC-32928 #### Employee Experience and Approver Experience (previously Communities) * Updates to improve the general usability on mobile devices New User Story Reference Number(s): SC-32820, SC-32831, SC-32832, SC-32833, SC-32834, SC-32836 #### Employee Experience (previously Communities) * General updates have been made to the *Timesheet* functionality available on mobile devices New to improve the *Employee’s* experience when scrolling through and interacting with *Timesheets* User Story Reference Number(s): SC-32558, SC-32337 * Updates to ensure that only enabled *Timesheet Allowances* records are available for use New within the *Employee Experience* User Story Reference Number(s): SC-32794 * Updates to the Submit and Recall functionalities to ensure Timesheet Allowances are locked / New unlocked for editing as required User Story Reference Number(s): SC-32621, CI-218086 #### Approver Experience (previously Communities) * The *Approver Timesheet* functionality available on mobile devices has been enhanced New through the introduction of the same *Timesheet* filtering options available for desktop users User Story Reference Number(s): SC-32565 * Enhancements have been made so that *Alternative Leave Approver* will now be able to view New and approve / reject *Leave Events* User Story Reference Number(s): SC-32359 * The date range that controls which *Timesheets* are available to view and approve / reject has New been extended to now show *Timesheets* that have been submitted with an *End Date* up to 366 days in the future User Story Reference Number(s): SC-32286 * *Approvers* that are authenticated users, now have the ability to enter notes against individual New *Timesheet Entries* which in turn will be visible to *Employees* within *Employee Experience* *(Communities)* User Story Reference Number(s): SC-31782 * The functionality to sort Timesheets by the Hours column on the Timesheet landing page has New been updated to ensure they are sorted correctly User Story Reference Number(s): SC-32720 * To meet Salesforce Winter21 security of guest users requirements, the Approver Notes New functionality has been disabled for Approvers that access the Approver Experience as a Guest user (those that use a link token). The functionality remains available for authenticated Approvers (those that log in with a username and password). User Story Reference Number(s): SC-32711 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 Banksia ‘21 Release for yourself. Refer to the **Upgrade Guide for the Banksia ‘21 Release** for further information on installation requirements, including pre and post-installation checklists, installation links and configuration instructions.