Abide by the new 2022/2023 Pay As You Go Tax Tables EOFY New
To make sure your PAYG employees are taxed correctly, the 2022/2023 Pay As You Go (PAYG) Tax Tables have been added to the Bulk Data Creation Extension package so they can easily be created as PAYG Withholding Rules. The new tax rates come into effect on 1 July 2022 and therefore, will apply to the first payroll from next financial year. It is suggested you complete this task before 1 July 2022. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33667
Updates to the 2022/2023 Lump Sum D and ETP Rates EOFY New
From 1 July 2022, the Lump Sum D and ETP Rates have been updated by the ATO. To assist with the ease of updating the information, the relevant Withholding Rules and Items have been added to the Bulk Data Creation Extension package. The new Lump Sum D Withholding Rules and Items amount is $11,591 plus $5,797 for each completed year of service. The new Withholding Rules and Items will apply to the life benefit termination payment and death benefit termination payment cap. They will increase to $230,000. As changes will apply to your first payroll of the new financial year, it is suggested you complete this task before 1 July 2022. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33523
Adhere to the 2022/2023 Superannuation Changes EOFY New
In light of the 2022/2023 Superannuation changes to the SGC rate and threshold amounts, new Super Withholding Rates have been added to the Bulk Data Creation Extension package. These Withholding Rules specify that the SGC Rate is applied at 10.5%, Minimum Monthly Earnings threshold is $0.00 and Maximum Contribution Base is $60,200.00. As these come into effect on the 1 July 2022, they will apply to your first payroll of the new financial year. It is therefore suggested you complete this task before 1 July 2022. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33453
2023 Public Holiday Available Via Bulk Data Creation New
The 2023 Public Holidays have been added to the bulk data creation package for use when creating bulk Public Holiday Calendars. If your organisation has an existing Public Holiday Calendar, the installer is prompted to choose which state and territory holidays are to be created for on a per calendar basis. If you don’t have existing Public Holiday Calendars, they will be created automatically on installation of the package. Note that the public holidays available through the Bulk Data Creation package are only those that apply to capital cities. No regional public holidays are included for automatic creation and will have to be created manually. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33121
Timesheet Interpretation and the Ability to Define Sleepovers New
Some Modern Awards, especially Social, Community, Home Care and Disability Services Industry (SCHADS) Award 2010, have Sleepover conditions that apply to employees who are required to sleep overnight at premises where the client for whom the employee is responsible for is located. Previously, Sleepovers were handled by the user creating an Interpretation Variation. Now, an improvement has been made to Timesheet Interpretation functionality so that users can define the conditions / breakpoints (including Minimum Rest requirements) directly on the Interpretation Rule. A new section has been introduced to Interpretation Builders called Split/Broken Shift and Sleepover Rules to cater for this. When Time Interpretation is completed, if Sleepover activity is selected on the Assignment, it will adhere to the rules which are set in the Interpretation Rule. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33595, SC-33608
Introduction of Interpretation Rules Frequency Pay Code Caps New
Previously, the Time Interpretation’s Pay Code Cap functionality could only be applied on a daily basis. The functionality has now been extended to offer Frequency Pay Code Caps. The Frequency Pay Code Caps work the same as the Daily caps, except they apply to the entire Timesheet period. Both Daily and Frequency Pay Code Caps can be defined in the same Interpretation Rule. During Time Interpretation, any Pay Code Cap will automatically proceed to the next breakpoint and if there is no next breakpoint, then the Timesheet Interpretation will stop payment of the Pay Code. For example, Allowance Pay Transactions with a Frequency Pay Code Cap applied will stop being paid for the remainder of the timesheet period when the Pay Code Cap is reached. Configuration Requirement : Optional User Story Reference Number(s): SC-31656The Ability to Define Interpretation Allowances For Payment During Leave New
Some Interpretation Allowances do not apply when employees are on leave. For example, if an employee is on annual leave, a laundry allowance isn’t payable. To allow for this, the Time Interpretation functionality has been improved to now enable users to define, through the Interpretation Rules, if an Interpretation Allowance should be paid on a per Leave Type basis. Interpretation Builders have been updated to include a new section called Allowance Junction Rules which contains an Allowances/Leave Junction tab. In this tab, users can define which Interpretation Allowances and Leave combinations will be paid during Time Interpretation. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-32148, SC-33610
Define Interpretation Allowances For Payment Using Timesheet Activities New
Some Interpretation Allowances are only relevant when certain Timesheet Activities apply. For example, Sleepover Allowance is only applied if a Sleepover Timesheet Activity is present. To allow for this, the Time Interpretation functionality has been improved to allow users to define, through the Interpretation Rules, if an Interpretation Allowance should be paid on a per Timesheet Activity basis. Timesheet Activities are currently 24hrs Care Shifts, Broken Shifts, Excursions, Overtime Round Up Shifts, Sleepovers and Wake Up Shifts. Interpretation Builders have been updated to include another tab under the Allowance Junction Rules called Allowances/Timesheet Activity Junction. In this tab, users can define which Interpretation Allowances and Timesheet Activity combinations will be paid during Time Interpretation. The logic used for performing Time Interpretation has been updated so that, by default, Allowances won’t be considered for Timesheet Entries with a related Timesheet Activity. If an Allowance needs to be paid on any Timesheet Activity, the Allowance Rule must be defined via the Interpretation Builders. Once that is done, an Allowance/Timesheet Activity Junction should be created, via the Allowance Junction Rules, to form a connection between the Allowance and the Timesheet Activity Types.. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33103, SC-33610
Update to the Minimum Paid Hours When Variations Apply New
Enhancements to the Time Interpretation functionality have been undertaken so that when a Variation applies, the Minimum Paid Hours defined on the Variation will always be the ones that are used instead of the parent Interpretation Rule. To provide consistency, the Variation Minimum Paid Hours values are to be used regardless of whether the values are lower or higher than those set on the parent Interpretation Rule. Due to this, it is recommended that the existing variances records be checked to make sure the Minimum Paid Hours values are correct. Configuration Requirement : Optional User Story Reference Number(s): SC-33145Enhancement to When Minimum Rest is Applied New
Improvements have been made to the Minimum Rest logic in the Time Interpretation functionality. Now, when determining if a Minimum Rest applies, the previous Timesheet Entry is checked, and if it was for any type of Leave, Minimum Rest is not interpreted. Furthermore, a new field has been introduced to the Interpretation Rule and Interpretation Builders called Apply Minimum Rest on Overtime. If this field is set to ‘No’ the Minimum Rest logic will continue to apply as it currently does. If the Apply Minimum Rest on Overtime field is set to ‘Yes’, in determining if a Minimum Rest applies, the previous Timesheet Entry is checked, and unless an Overtime Breakpoint has been applied at the end of the shift, Minimum Rest is not interpreted. If on the previous Timesheet Entry an Overtime Breakpoint is applied at the end of the shift, the Minimum Rest logic will continue to apply as it currently does. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33075
Enhancements to the Split / Broken Shifts Logic New
Improvements have been made to the Timesheet Interpretation functionality’s Split / Broken Shifts logic (Broken Shifts). A new field has been introduced to the Interpretation Rule and Interpretation Builders, called Broken Shift Breakpoint Application, that allows users to define Breakpoints logic that will be applied to any Broken Shifts. The user can continue to use the current logic when performing the Broken Shift calculations. The users can choose to set the Breakpoint that will be used when conducting calculations on both the Timesheet Entries, and is determined from the Breakpoint that applies to Timesheet Entry 1 or Timesheet Entry 2. For example, if the Shift End Interpretation Rule is used and the Broken Shift Breakpoint Application is set to Timesheet Entry 1, when performing Timesheet Interpretation, the Shift End Time of Timesheet Entry 1 will be used to determine the Breakpoint that applies to it. The exception to this is if the Timesheet Entries fall on a weekend or Public Holiday, or the overnight proportion falls on a weekend or Public Holiday, then the weekend and Public Holiday breakpoints will apply. Alternatively, the user can set the Broken Shift Breakpoint Application to Define Breakpoint and setup a new Breakpoint, in the Split / Broken Shift and Sleepover section of the Interpretation Builder. Within this section there is a Split / Broken Shift Standard Breakpoint tab, to define the Pay Code to the used in a per Day basis. When performing Timesheet Interpretation, the Day that applies to the Timesheet Entry is determined and it selects the corresponding Pay Code that is defined on the Breakpoint. For example, if the Timesheet Entry Day is determined to be Saturday, the Saturday Pay Code defined on the Breakpoint will be applied. The exception to this is, if the Timesheet Entry was overnight, then the Overnight logic will apply to the Timesheet Entry instead. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-32967, SC-33608
Control When Broken Shift Logic Will Apply New
New improvements have been made for users to have control over when the Split / Broken Shift (Broken Shift) logic will apply. To accomodate this a new field has been introduced to the Interpretation Rule and Interpretation Builders, called Broken Shifts Timesheet Activity Required. If set to ‘No’, the Broken Shift logic will continue to apply as it is currently (including the Enhancements to the Split / Broken Shifts Logic outlined above). If the Broken Shifts Timesheet Activity Required is set to ‘Yes’, the Broken Shifts logic will only apply to Timesheet Entries which are related to a Broken Shift Timesheet Activity. If the Timesheet Entry does not have a Broken Shift Timesheet Activity related to it, the Broken Shift logic will not apply. Configuration Requirement : CompulsoryUser Story Reference Number(s): SC-33226, SC-33608
Save Time With The Update Rate Manager
Managing the bulk change of pay rates can be a time consuming process. With the introduction of the Update Rate Manager, users will be provided tools that can assist in reducing the time required to complete rate updates, while also simplifying the process. With this new feature, users will be able to bulk update pay rate information on Minimum Pay Rates and Assignment Rate Template records. Furthermore, where required, associated invoice rates can also be bulk updated on Assignment Rate Template records. These rates can be updated based on a percentage (%), dollar value ($) or by entering a new rate. Configuration Requirement : Optional User Story Reference Number(s): SC-32296 (SC-31853, SC-32306, SC-32304, SC-32303, SC-32302, SC-32301, SC-32299, SC-32298, SC-32297, SC-32295)Provide Enhancements to Rate Calculator (Beta*)
For Staffing organisations, a new enhanced version of the Rate Calculator has been developed to further improve rate calculation capabilities. This Beta version of the Rate Calculator will facilitate further ease in setting up rate calculators ready for use, while also providing other time saving functionality such as the ability to apply Rate Calculator (no employee) and Rate Calculator Templates either directly though the Rate Calculator or from an Assignment. Users can now also create a Rate Calculator Template without the need to define Margin / Mark Up records. In addition to the above, Minimum Pay Rate functionality has been incorporated into the Rate Calculator to simplify the definition and maintenance of rates based on an Award Classification and Award Level. *:This is a beta release of the Rate Calculator functionality and additional updates and improvements will be included over the releases for 2022. Configuration Requirement : Optional User Story Reference Number(s): SC-32852 (SC-32916, SC-33083, SC-32917, SC-32915, SC-31784, SC-31780, SC-31773, SC-33042, SC-32918, SC-33041, SC-33043)Automation of Template Group Population on Assignments
New functionality has been introduced to automate the population of the Assignment Rate and Payee Timesheet Allowance Template Group fields on the Assignment. A new custom setting has been introduced and, when set to true (checked), on creation of an Assignment it will be assessed and have the fields automatically populated where appropriate. To meet the criteria the template group field(s) must be blank and the Interpretation Rule field must be populated. The Template Group records need to have the exact same name as the Interpretation Rule for it to automatically be selected for population on the assignment. Configuration Requirement : Optional User Story Reference Number(s): SC-32953Define Overtime Pay Codes for Minimum Rest and Break Loading
Timesheet Interpretation functionality has been updated to now allow for the definition of an overtime pay code on both Minimum Rest and Break Loading breakpoints. When populated, the pay code will be used when hours fall within Time Breakpoints and Time Breakpoints are considered “Overtime” (Include_Time_Breakpoints_In_Overtime__c = Yes). This improvement provides for a consistent interpretation of minimum rest times and/or break loading regardless of if the hours worked fall within a standard breakpoint or a time breakpoint. Configuration Requirement : Optional User Story Reference Number(s): SC-32783 (SC-32790, C-32919, SC-32755)Improved Timesheet Interpretation for Allowances
The existing functionality for defining Allowances for timesheet interpretation only catered for Daily and Frequency based Allowances. Now, the Timesheet Interpretation / Allowance functionality has been expanded to include a new weekly allowance type. This means that Weekly Allowances can be defined, independent of Frequency Allowances, to be applied to all timesheet frequencies including fortnightly and monthly. The new Weekly Allowance interpretation offers the same configuration options regarding thresholds and overtimes as currently exists for Frequency Allowances. Configuration Requirement : Optional User Story Reference Number(s): SC-32783 (SC-32790, C-32919, SC-32149)Define Penalty Time Bands in Hourly Rates Timesheet Interpretation
Currently, when defining Hourly Rate Interpretation Rules, for each day a standard start and end time is defined with one set of time breakpoints to outline the treatment of penalty / overtime hours worked outside of that time range. Now, in addition to this existing functionality, a new alternative interpretation type has been introduced that will allow standard time and time of day based penalty / overtime to be defined within multiple different time ranges. This will allow for scenarios where what is classified as standard, penalty and overtime may differ based on the time of day the Employee works. Configuration Requirement : Optional User Story Reference Number(s): SC-32783 (SC-32790, C-32919, SC-32222)Updates to Frequency Overtime Calculations Where Leave Applies
To ensure adherence to Fair Work Australia requirements, how Frequency Overtime is applied within Timesheet Interpretation has been updated to cater for scenarios where the Employee has taken leave during the timesheet period. Now, in the event that Leave is configured to apply to Frequency Overtime calculations, if the combination of working hours and leave hours reaches Frequency Overtime, the overtime hours will be applied to the last working day of the timesheet period. This means that if Leave is taken at the end of the Timesheet period, and that day is configured to contribute to Frequency Overtime, instead of applying the overtime to the Leave Timesheet Entry, it will be applied to the most recent Non-Leave Timesheet Entry within the Timesheet. In the event that leave is not configured to apply to Frequency Overtime calculations, there are no changes to how Timesheet Interpretation is applied. Configuration Requirement : No configuration required User Story Reference Number(s): SC-32783 (SC-32790, C-32919, SC-31681)Improved Handling of Interpretation Rule Scenarios
Enhancements have been made to Interpretation Rules and the Timesheet Interpretation functionality to cater for and provide consistent, automatic treatment of additional edge case scenarios relating to minimum hours and overnight shifts. This includes when the span of hours worked falls outside of the defined standard hours and the Employee has not met minimum hours requirements, and also when Employees have not had the defined minimum rest time and the dates fall between two timesheet periods. For example, the rest time between the last Timesheet Entry of a Timesheet and the first Timesheet Entry of the following Timesheet is not long enough. The handling of overnight shifts has been updated to handle when a break is taken over the midnight period. In addition to the above updates, general improvements have been applied to improve error handling and reporting to users. Configuration Requirement : Not required User Story Reference Number(s): SC-32774, SC-32758, SC-32660, SC-32957, SC-32169Improved Superannuation Deduction Capability
Currently, when defining Superannuation Deductions, the deduction was directed to the same Superannuation Fund as their Employer contribution is paid. New functionality has been introduced to give employees the option to direct their deduction to a different fund than their employer contributions are made. Configuration Requirement : Optional User Story Reference Number(s): SC-32142Override Superannuation Minimum Age requirements
New functionality has been introduced to allow users to override the minimum age requirements for when calculating Superannuation. This improvement will allow users to calculate and pay contributions for Employees that are under 18 years of age and would otherwise not meet the minimum working hours requirement. This is controlled via a field in the Payee Withholding Rule which means the override can be applied on a per payee basis. Configuration Requirement : Optional User Story Reference Number(s): SC-33092Customise What is Displayed on Pay Advice Documents
New customisation options for Pay Advice documents have been introduced. Users will now have the ability to automatically hide sections within the pay advice where there is no data to be shown. This functionality is set on a per Pay Advice Template basis so Users can choose which templates will hide blank sections and which will show them anyway. Further, the ability to customise the information provided on Pay Advice documents based on the Pay Code applied has also been introduced. Users can define, at a Pay Code level, if information pertaining to the Pay Transactions using these Pay Codes will not be displayed within the Pay Advice document. This will be useful in the instances where pay codes have been created / used for informational / calculation purposes but that information does not need to be provided to the Employee. Configuration Requirement : Optional User Story Reference Number(s): SC-32616, SC-32100Validating Leave Availability When Creating Payee Leave
New optional functionality has been introduced to provide users with the ability to validate payees leave balances whilst creating Payee Leave Events. This improvement, which can be configured at a Leave Rule level, will prevent Payee Leave Events from being created / updated if there is not a sufficient leave balance available to take the leave. For internal payroll users, the ability to override the validation on a per Payee Leave Event basis has also been provided. This will allow internal users to still create Payee Leave Events where there is not enough leave balance available if the need arises. Through allowing the validation to run and then having the user manually select to override, it means that the user will be aware that the payee did not have sufficient leave available. This is intended to prevent records being created for leave where there was insufficient leave available without users knowing. It is suggested that the field to override the validation should not be made available to Experience (Communities) Users / Employees. Configuration Requirement : Optional User Story Reference Number(s): SC-33190, SC-30928Improved Automatic Experience (Communities) User Creation
Improvements have been made to the functionality that automatically creates Experience (Communities) users so payees that already have login details created are skipped. This change will result in the automatic process completing at a quicker speed, therefore reducing delays in creating login details for Payees who require them. Further, updates have been made to the automatic creations, and the follow-up functionality which automatically assigns permission sets to new Experience (Communities) users, to provide improved error handling and error reporting. Configuration Requirement : Not required User Story Reference Number(s): SC-32368, SC-32708, SC-32367New Deduction Record Page Layouts
To provide for an improved, record type based allocation of Deduction Record page layouts, new layouts have been introduced. These include General Deductions (TC9PR General Deduction Record Layout), Purchased Leave Deductions (TC9PR Purchased Leave Deduction Record Layout), PAYG Deductions (TC9PR Withholding Deduction Record Layout) and Superannuation Deductions (TC9PR Withholding Deduction Record Layout). These new layouts can be assigned to record types as needed. Configuration Requirement : Optional User Story Reference Number(s): SC-3301Automated Back Pay (Pilot Program*)
A new Pilot Program has been launched to develop and trial new Back Pay functionality. The first stage of this trial relates to the automatic calculation of back pay for Timesheet based Employees. The intention is to provide users with an easier avenue to identify Assignment Rates that are related to a Back Pay and define the pay requirements. Then, during Pay Batch Calculation, the Back Pay will automatically be allocated to / calculated for the historic periods to which they belong. This will ensure that the accuracy of statutory calculations are maintained. The next phase of the Pilot Program, to be included in a 2022 release, will relate to back pay for Non-Timesheet (Auto_Pay) based Employees.- The Automated Back Pay functionality will be released as part of a pilot program for selected organisations to trial and test the functionality against their needs. During the pilot program, additional updates and improvements will be introduced. If you would like your organisation to take part in the pilot program, and have resources available that can be dedicated to testing and providing feedback, please contact your Project Manager.
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.Payment Entity
- The Payment Entity lookup fields on the Assignment, Payment Detail and Payment File have had their lookup filters updated to use the Record Type ‘Developer Name’ instead of the Record Type ‘Label’ New
Contact, Payees and Assignments
- A new optional lookup filter has been introduced on the Payee Deduction record’s Pay To Withholding Record field to make it easier for users to select a Payee Withholding Record for the same Payee as is defined on the Payee Deduction record
Minimum Pay Rate and Assignment Rates
- Updates have been made to further optimise code relating to minimum pay rate automation to reduce the risk of hitting Salesforce governor limits
Timesheets
- Updates have been made to Timesheet Entries so that, in the event that the Timesheet Entry is related to a Work Schedule, it will not be marked as edited unless the Timesheet Entry and those detailed on the work schedule do not match
- General code optimisation to improve the processing of ‘rollup summaries’ held on the Timesheet
Expenses
- New validation has been introduced to ensure when an expense record is created/updated the defined Total Including Tax is a greater value than the Total Tax
Leave
- Improvements have been made to the validation of Payee Leave Event records to cater for when it is related to a Timesheet Entry. Now there may be multiple Payee Leave Event records created for the same date, however, the time range indicated on the associated Timesheet Entries must not overlap
- General improvements to the Leave balance forecast tool to provide for more accurate leave forecasts
- Updates to Leave balance forecasting have been made to ensure the validation that checks the employee has sufficient leave, doesn’t include leave that has already been processed New
Time Interpretation
- Frequency Allowance functionality has been extended to now allow the definition of start thresholds within Interpretation Rules. These thresholds can be based on hours worked, overtime hours worked and days worked
- Updates have been made to ensure that all Daily Allowances defined in the Interpretation Rule are assessed and, when necessary, resulting pay transactions are created
- Updates have been implemented to the Transactions Process functionality to populate the Pay Multiplier field on any resulting Timesheet Allowance Pay Transactions New
- Improvements have been made so that when a Pay Code is changed on an existing Pay Transaction, the Pay Rate and Assignment Rate automatically updates to reflect the new Pay Code New
- Updates have been made to Time Interpretation functionality to ensure that overtime hours are not counted as ordinary hours when performing calculations New
- Updates have been made to ensure that the Minimum Paid Hours, set on Interpretation Rules and Variations, are handled correctly when Frequency Overtime applies New
- Enhancements were made to the Timesheet Interpretation functionality to handle Broken Shift logic for Timesheet Entries that are outside the span of hours defined in the Interpretation Rule. New
- Updates have been made to the Timesheet Interpretation functionality to ensure shifts that commence on Saturday and finish on Sunday (overnight), have any Frequency Overtime applied calculated correctly New
- General improvements have been made to the Interpretation Builder to make it more user friendly New
Pay Batch and Pay Batch Manager
- Improvements have been made so that when processing a Pay Batch, Pay Transactions created from an Assignment Rate (Auto-Pay Employees) no longer have the record type automatically set to ‘Payment’ but will instead be populated with the record type of the associated Assignment Rate
- Additional Filter options have been introduced to the Pay Batch Manager to enable users to filter records displayed within the Review section based on the Gross Pay or Net Pay.
- Updates have been made so that when users create manual adjustment pay transactions for superannuation they will only be presented with Payee Withholding records for AU Super where the superannuation fund field is not blank. This will ensure the user is only able to select records where the required information for SuperStream is provided
- Enhancements have been made to the Work Schedule calendar view, available within the Pay Batch Manager Manual Adjustments page, so that it is now displayed dynamically based on the frequency of the Pay Schedule belonging to the Pay Batch
- Updates have been made to ensure that when Manual Adjustments are created via the Pay Batch Manager, the Pay Multiplier on the resulting Pay Transaction is automatically applied correctly
- Updates have been made to the variance report to ensure the accuracy of Quantity, Gross and Net variances reported
- Improvements have been made to the Pay Batch Manager so that non-taxable payment amounts will no longer be included in the calculation of protected earnings when payee’s deductions are calculated New
- The calculations used when calculating Payee Leave Events for auto pay employees has been updated to ensure that the resulting values are correct when leave is taken over more than one pay period New
AU Lodgements
- Updates have been made to the Superannuation Lodgement functionality to prevent the Tax Free Amount and Tax Amount being null or 0 so that the data extract meets the SuperChoice API requirements New
- A reconciliation tool has been added for 2cloudnine to use in reconciling payroll data. A beta version of this will be released for customers to use next year. New
Invoicing
- Updates have been made to the validation of the various Invoice Email CC fields held on the Account, Assignment and Invoice objects to cater for new, longer email address formats
Employee and Approver Experience (previously Communities)
- To extend the new functionality introduced in the Banksia ‘21 release that allows Employees to submit future dated timesheets, a pop up warning message has been added to Approver Experience to draw an Approvers attention to the fact they are approving a future timesheet in the event one is submitted.
- Updates have been made to improve the Leave Balance Forecast tool available to Employees within Employee Experience
- Updates have been made in-line with the Salesforce Winter21 security of guest user requirements, to ensure Approvers that access the Approver Experience as a Guest user (those that use a link token) can continue to approve / reject Expense Claims as needed
Security
- The Aus Lodgement Permission Set has been updated to include missing fields from the Payee Withholding and the Payee Deduction Record Objects New