Payroll Processing

TechnologyOne Human Resource and Payroll

LATEST RELEASE - May 2020

Package Description

The Payroll Processing package is used to manage the payment of salaries, wages and allowances, deductions, superannuation and taxation to employees on an individual or group basis. The package can also generate pay advices, bank download files, pay advices, and legislated reporting requirements for an individual or a group of employees.

Calculate or adjust pays for individual employees

Calculate pays for multiple employees

Generate pay advices for individual or multiple employees

Generate bank download file for individual or multiple employees

Generate Australian PAYG payment summaries and generate electronic TFN declarations to be transmitted to the ATO

Generate New Zealand IRD electronic reporting details to be transmitted to the IRD

Package Functions

The Payroll Processing Package includes the following functions:

Adjust Payroll for Employee	Load PAYG Payment Summaries
Adjust Back Pay for Employee	Adjust PAYG Payment Summaries
Process Leave Accrual for Employee	Electronic PAYG Payment Summaries
Process Termination Pay for Employee	Electronic TFN Declarations
Calculate Payroll by Group	IRD Electronic Deduction Form(IR 345)
Bank Download	IRD Employer Monthly Schedule(IR 348)
Pay Advice	IRD KiwiSaver Employment Details(KS1)

RELEASE May 2020.5

HRPC-2332 - Backpay processing - nett pay calculated is incorrect

HRPC-2367 - NZ legislative Payday Reporting changes - Mandatory 1 April 2021

HRPC-2391 - Termination Pay - Australian LSL accrual calculation incorrect when Initial load taken amounts are specified

HRPC-2759 - Payroll & Superstream log files are writing to $LOG, not $PAYLOG

HRPC-2761 - Back pay processing - $AU region tax calculation is not correct

HRPC-2332 - Backpay processing - nett pay calculated is incorrect

Functional Issue

Backpay processing is not generating the correct timesheet back payment when there is a mid-period pay rate change, the timesheet period is weekly and the pay period is fortnightly. NOTE: The issue does not occur if the timesheet and pay period have the same start/end dates.

Functional Verification

1. For an Australian employee whose calculation method is "Timesheet Only", and whose timesheet period is NOT the same as their pay period. E.g. the pay period is fortnightly while the timesheet period is weekly 2. For the next regular pay to be calculated, ensure the associated timesheets have the work days entered 3. Navigate to Adjust Pay and calculate the regular pay period 4. Confirm that all of the entered timesheets are paid correctly. n.b. The pay process will create timesheet generated pay items based on the timesheet period. 5. Perform a retrospective, mid-pay period change to the employee's entitlements. E.g. Create new employee entitlements that contain an increase to the base pay and have an Effective Date mid-way through the processed pay period 6. Navigate to Manual Backpay 7. Specify the backpay criteria ensuring that the employee impacted is selected and the backpay processing period includes the pay calculated in steps 1-4 8. Process the backpay 9. Review the backpay calculation results and confirm that: a. the timesheet pay items are reversed as at the old pay rate b. the timesheet units before the pay rate increase are re-paid at the old rate correctly c. the timesheets units from the effective date of the pay rate increase are paid at the new pay rate correctly d. the total Nett pay for the backpay is generated correctly.

Solution Implemented

The manual back pay process was updated to ensure pay items generated from timesheets are processed correctly when the timesheet period and pay periods differ and a retrospective, mid-pay period pay rate change is performed (either employee entitlements or employment condition). NOTE This is specific to scenarios where the timesheet periods are weekly, the pay period is fortnightly (or monthly) and the period end dates of these are not aligned.

HRPC-2367 - NZ legislative Payday Reporting changes - Mandatory 1 April 2021

Functional Issue

The NZ IRD has applied changes to Payday reporting which become mandatory from 1 April 2021 for employers. Refer to NZ IRD website for more information on Payday reporting via the Upload EI file.

Functional Verification

1. As Payroll Officer, navigate to a pay calculation function. i.e. Adjust Pay for employee or Calculate Payroll by Group 2. Once the employee is Paid, confirm that the action link to 'Preparing Payday Upload File for IRD' is visible 3. Select the 'Prepare Payday Upload File for IRD' link 4. Confirm that the main criteria of the calculated pay is loaded. i.e. Pay Period End Date, Company, Document Type, Pay Group, Id Number(s) selected for pay calculation NOTE - Only selected employees will be loaded into 'Prepare Payday Upload File' and available for inclusion in the payday file. - If no employees are selected from the Pay Calculation function, then the default for Payday processing will be to include ALL employees in the pay period that are Paid. 5. Submit processing 6. On completion of the job, review the log for errors and warnings 7. Review the generated csv payday file for correctness. By default this file is saved with the default naming format of 'Payday_<CompanyCode>_<PPED>.csv'. E.g. 'Payday_1_15Apr2019.csv'. 8. Confirm that the employee pay masters are updated to reflect the Submission Status (SUCCESS) and Submission ID (payday file name). The Submission Status is visible in the Pay calculation functions as well as the Pay Transactions data analyser. 9. Confirm that the selected employees are included unless excluded due to errors or warnings. 10. Confirm details and amounts are correct for the Pay Period and criteria specified. 11. Confirm the new fields are included and contain correct values for : - Hours Paid (NOTE can be reported as zero if not captured. e.g. employee is paid in Day units) - SLCIR Deduction - SLBOR Deduction - Employee Share Scheme (ESS) - Prior Gross and Payee Adjustment (NOTE These fields are not currently supported and will have zero values). NOTE - Do NOT open the csv file in MS Excel and re-save, as this may adjust the file formatting required by the IRD. E.g. date formats, IRD '00000000' - If multiple Paid Dates are detected in the one Pay Period, the Paid Date will be appended to the file name. E.g. Payday_1_15Apr2018_PD19Apr2018.csv' and 'Payday_1_15Apr2018_PD20Apr2018.csv' - Amounts are for the pay period only (not YTD or calendar month as per the EMS). - The IRD do NOT accept negative amounts in Payday reporting. Any employee who has any negative amounts for the pay period will be excluded from the Payday report. A warning message is returned and the employee's Submission Status will be set to FAIL. - Function parameters are available to default Taxation Supplier and Destination Folder values into 'Prepare Payday Upload File for IRD'.

Solution Implemented

The NZ IRD Payday process and csv file has been updated as per the IRD specifications 1 April 2021. Changes include: 1. Header record indicator = HEI2 2. Extra lines are no longer required for SLCIR and SLBOR deductions as this file now has separate fields for SLCIR and SLBOR deductions 3. A separate line is not required for Employee Share Scheme (ESS). Any ESS amounts are now recorded in the Employee Share Scheme field 4. Employee name is reported in the preferred format: 'first_name last_name' 5. Hours paid for the paydate are reported (NOTE Only if the employee has been paid in the Hours unit type, otherwise zero value Hours Paid is reported). NOTE only to employers: 1. KiwiSaver employment details (KED) form is no longer required and will not be accepted by the IRD from 1 April 2021. 2. The IRD portal now accepts compressed zip files. Refer to IRD website for guidelines and restrictions. 3. Prior to 1 April 2021, employers can continue to submit the 2019 version of Payday file. Contact Technology One Support if you require instructions to submit the earlier version.

HRPC-2391 - Termination Pay - Australian LSL accrual calculation incorrect when Initial load taken amounts are specified

Functional Issue

The Australian termination pay process is not calculating the total LSL accrual correctly when an initial load for the employee's LSL accrual includes leave taken for one or more of the ATO LSL tax periods. E.g. pre 1978, 1978-1993, post 1993. i.e. The calculation required by the ATO is based on total LSL days accrued within the relevant tax periods minus days taken.

Functional Verification

1. For an Australian employee with a hire date prior to 1993 and a first job with an effective date after the hire date. E.g. Job Effective Date 1-Jan-2010 and Date of Hire 1-Feb-1990 2. Ensure the employee's entitlements include a calendar LSL accrual 3. For the LSL accrual, add an Initial Load with an Accrual Start Date set to the Hire Date, specify a non-zero accrual balance and any pro-rata, and specify Leave Taken amounts in the pre 1993 and post 1993 tax periods 4. Terminate the employee in the current year and calculate the termination pay 5. Review the calculation audit section for the termination LSL components 6. Confirm the LSL accrual balance is summed correctly by including the initial load taken totals to obtain the total LSL accrued as at the initial load effective date 7. Confirm the LSL components are calculated correctly per the ATO requirements 8. Review the pay items and confirm the LSL components are generated correctly.

Solution Implemented

The Australian termination pay process has been modified to include the leave taken amounts entered in the ATO tax periods of the initial load to the total initial balance of the LSL accrued.

HRPC-2759 - Payroll & Superstream log files are writing to $LOG, not $PAYLOG

Functional Issue

Some payroll services including SuperStream are writing their logs into the default server folder '$LOG' instead of checking for a custom payroll server folder as specified by $PAYLOG or PAYLOG. i.e. one secured for payroll users

Functional Verification

1. SuperStream - Navigate to your 'Prepare SuperStream Contributions' function - Start Processing - Open Server Folder viewer - Confirm that the log is written into the correct directory. i.e. the first valid server folder found to be defined in the order of priority: a. HR_PAY_LOG_DIRCODE System Variable b. $PAYLOG Server Folder c. PAYLOG Server Folder (custom override) d. $LOG Server Folder (default log directory) 2. Update Paid Date - Navigate to the Update Paid Date function - Enter criteria and process the required Update Paid Date - Open 'View Last Job Detail Menu' - Confirm that the log is written into the correct directory. 3. Delete Pays by Group - Navigate to the 'Delete Pays by Group' function - Process a pay deletion that is required - Open 'View Last Job Detail Menu' - Confirm that the log is written into the correct directory.

Solution Implemented

Three payroll process functions have been modified to ensure that their log file is written to the required Payroll server folder prior to defaulting to the $LOG server folder. This is based on the first valid server folder defined in the order of priority: 1. HR_PAY_LOG_DIRCODE System Variable 2. $PAYLOG Server Folder 3. PAYLOG Server Folder (custom override) 4. $LOG Server Folder (default log directory) NOTE For the full functionality of this change the latest Ci packages must be installed for HRP Core and Payroll Processing.

HRPC-2761 - Back pay processing - $AU region tax calculation is not correct

Functional Issue

The Manual Back Pay process is not correctly processing TSL/HELP causing the back pay to generate without any nett pay. The processing date of the back pay is being used for Tax and Study Loans back pay calculation instead of each associated back paid pay period. The pay period date narrated on the tax calculation section of the log is incorrect.

Functional Verification

1. For an Australian employee who is currently on Tax Scale 2 and repaying a Study and training loan 2. Calculate the next ordinary pay period for this employee 3. Pay the pay period with the respective paid date 4. Generate a new entitlement set effective within the pay period that has been paid, increase the base pay entitlement amount by 5% 5. Calculate a manual back pay the covers the paid ordinary pay period for the employee. Ensure the back pay pay period end date and expected paid date are after the ordinary pay period's dates 6. Review the back pay processing log, in particular the employee's tax calculation section of the log 7. Confirm the tax calculation for the ordinary pay period above has been processed per the original pay's period end date and paid date 8. Review the Study and Training loan calculation for the back pay 9. Confirm the calculation is done per the total repayment income for the pay period end date and paid date 10. Confirm the total Study and Training loan calculated is reduced by the amount deducted within the original ordinary pay calculation.

Solution Implemented

The manual back pay process has been corrected to ensure the Australian PAYG tax calculation and Study and Training loan repayment is calculated correctly for the back pay as per the impacted ordinary pays dates (Paid Date, Pay Period End Date).

RELEASE May 2020.4

HRPC-2765 - $AU ATO Budget legislative changes effective 13/10/2020

HRPC-2765 - $AU ATO Budget legislative changes effective 13/10/2020

Functional Issue

1. The Australian normal tax scales are to be updated effective from 13/10/2020. 2. The Seniors and Pensioners Tax Offsets (SAPTO) scales are to be updated effective from 13/10/2020. 3. The Australian Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) Other Scales are to be updated effective from 13/10/2020. 4. The Working Holidays Makes (WHM) other scales are to be updated effective from 13/10/2020. 5. The maintain Tax Scales function does not allow a negative value to be entered in the Details grid column (B).

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace 2. Navigate to the Manage Payroll Tab 3. Navigate to the Australian Tax Scales (Tax Scales -> $AU - Australia). 4. Confirm that new Tax scales are available for the 13 October 2020 - Tax Scale Codes 1 - 6 inclusive. 5. Navigate to the Australian Tax Scales (Tax Scales -> $AU - Australia) - the SAPTO scales are included with the normal scales. 6. Confirm the new SAPTO scales are available from 13 October 2020 - Tax Scale Codes 'CPL', 'ILL' & 'SGL'. 7. Navigate to the Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) income thresholds (Other Scales -> $AU - Australia -> AU_HELP - HELP): 8. Confirm that new Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) income thresholds are available for the 13 Oct 2020. Note: The separate SFSS scales are now obsolete and will not be updated. 9. Navigate to the Working Holiday Makers thresholds (Other Scales -> $AU - Australia -> AU_WHM): 10. Confirm that the Working Holiday Makers thresholds are available for the 13 October 2020. 11. Navigate to the Australian Tax Scales effective 13 October 2020, tax scale code 1 (Tax Scales -> $AU - Australia -> 13/10/2020 -> 1). 12. Confirm the scale Details row for the Earnings (X) Less Than '515.00' is displaying a column (B) value of '-1.9003'. 13. Maintain the scale's Details row in step 12 and enter a negative value for the column (B). 14. Confirm the column (B) field will allow a negative value to be entered. 15. Save the scale change. 16. Confirm the scale is saved without any errors raised and the amended negative column (B) value is saved. 17. Maintain the row in step 12 and enter the correct column (B) value '-1.9003'. Save the scale to ensure the tax is withheld correctly.

Solution Implemented

1. Added new Australian Tax Scales effective 13 October 2020 (refer to ATO website). 2. Added new Australian SAPTO scales effective 13 October 2020 (refer to ATO website). 3. Added new Study and Training Support Loans (HELP,VSL,SFSS,SSL,TSL) scales effective 13 October 2020 (refer to ATO website). 4. Added new Working Holiday Makers scales effective 13 October 2020 (refer to ATO website). 5. Changed the Tax Scales Details grid column (B) to allow a negative value to be entered and saved. NOTE: To ensure that these new tax details are loaded into your database(s) for releases 2019A onward: 1. Ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server. 2. Alternatively, for On-Premise installations, a Package Finalise can be executed after applying this update. 3. If the scales are still not updated after the above two solutions, please run the 'HR & Payroll Load Region Data' function for region $AU and N for Test Mode. NOTE: If employers have not taken the Legislative release updates for Payroll beyond May 2017 (2017A) then the above tax scales changes must be done manually. Additionally, the negative value in column (B) for Tax Scale Code '1' requires the execution of a pre-approved datafix (refer Knowledge Base article). Once the correction has been applied, the negative column (B) value will be displayed and applied to the tax calculation correctly. However, attempting to save further changes to the Tax Scale 1 will result in an error due to the negative value for column (B). To resolve this, the latest release of the package Payroll Processing is required (i.e. containing changes for Budget 2020). Please refer to the Customer Community for the Knowledge Base article for further manual configuration details.

RELEASE May 2020.3

HRPC-38 - Unable to calculate Leave accrual for employee with inactive job account component

HRPC-2260 - Backpay adding negative deductions to net pay causing an overpayment - Cannot complete Pay Posting

HRPC-2311 - Job details error when mid-pay position change and WHOLE_PRD deduction is inactive at pay period end date

HRPC-2338 - Missed pay earnings (OTE) in SGC calculation for the calendar month when first pay is less than $450

HRPC-2501 - NZ Alternate Leave processing taken balance incorrectly

HRPC-2549 - ComSuper EPSC and Cents per KM rates for the 20/21 financial year (late updates)

HRPC-2575 - STP Zeroing YTD - enhancement to zero against previous employee Payroll Ids

HRPC-2592 - STP OTE - only including Doc Types P and Z

HRPC-38 - Unable to calculate Leave accrual for employee with inactive job account component

Functional Issue

When an employee has an account component change for an active accrual code (either via job or entitlements), the leave accrual calculation can fail with a 'invalid account number' error if the old account component is made inactive after the last accrual calculation.

Functional Verification

1. From Employee Maintenance, modify an existing employee by adding a new job detail or entitlement that specifies a new ledger account for an accrual E.g. a new Cost Centre is defined on the employee's new job. Alternatively, a new account is defined on the employee's accrual code in a new set of entitlements 2. From Financials, change the accrual's previous account component to be Inactive 3. From Payroll, run the leave accrual calculation process for the employee 4. Confirm the accrual calculation succeeds and that no errors are returned regarding the previous and inactive ledger account component associated with the accrual code 5. Review the accrual pay items created by the process 6. Confirm the pay item's costing for the accrual period that is covered by the inactive account component has been generated with the current costing for that accrual code. NOTE The current costing for an accrual code is retrieved if account errors occur for accrual period dates occurring prior to the accrual processing date.

Solution Implemented

The Accrual process has been updated to use the current account for an accrual pay component if an inactive account is detected while calculating a previous accrual period for the employee's accrual code. E.g. LSL which spans many years of Financial periods.

HRPC-2260 - Backpay adding negative deductions to net pay causing an overpayment - Cannot complete Pay Posting

Functional Issue

The back pay process was generating incorrect net pay items which resulted in out of balance pack pays for New Zealand employees who have child support deductions being processed within the back pay period.

Functional Verification

1. For a NZ employee. with a child support deduction in their entitlements (i.e. deduction pay component with a NZ child support configuration) 2. Ensure at least 2 ordinary pay periods for the employee have been calculated and confirm that the child support is deducted for both pay periods 3. Make a retrospective change to the base pay entitlement of the employee 4. Navigate to the Manual Back Pay function 5. Specify the back pay criteria for the employee including the 2 calculated pay periods 6. Ensure the child support pay component is included in the selected pay components to process 7. Calculate the manual back pay 8. Review the back pay generated 9. Confirm the net pay item generated is for the correct amount 10. Confirm the pay balances. i.e. total payments less deductions including the net pay totals zero 11. Post the back pay and confirm the payroll posting process completes without errors.

Solution Implemented

The back pay process has been changed to ensure the generated net pay item is correct for New Zealand employees with child support deductions being processed within the back pay.

HRPC-2311 - Job details error when mid-pay position change and WHOLE_PRD deduction is inactive at pay period end date

Functional Issue

If an employee has a deduction in their entitlements which is configured for processing Whole Period only (WHOLE_PRD config code) and they receive a mid-pay period job change (e.g. position), the pay calculation will fail with an error message for no job found. E.g. Employee '12345' does not have any job details effective as at '28-Jul-2020' for Position 'P800'.

Functional Verification

1. For an employee whose active entitlements include a Deduction to be calculated on Whole Period only 2. Assign the employee to a different position in a new job record dated mid-pay period 3. Generate new entitlements ensuring that the Whole Period Deduction is no longer included 4. Calculate the employee's next regular pay loading Entitlements 5. Confirm that pay calculates successfully and a warning is received advising that the Deduction for Whole Period is not included (as it is not included in active entitlements for the employee at the Pay Period End Date).

Solution Implemented

The Pay calculation process (InputLoader) has been modified to issue a warning message for Whole Period Deductions that are not included due to mid-pay period changes and are no longer in the active entitlements. NOTE: If the employee is to be paid the allowance/deduction per the entitlement as at the pay period start, the pay item can be manually entered and the pay period re-calculated.

HRPC-2338 - Missed pay earnings (OTE) in SGC calculation for the calendar month when first pay is less than $450

Functional Issue

Incorrect SGC may be calculated when an employee has earned less than $450 (SGC monthly minimum) in the first of multiple pays calculated for the same Paid Date. e.g. a Correction and regular pay are calculated and paid on the same date. However, the subsequent pays of the calendar month do not correct the underpaid SGC by including all the employee's OTE of the calendar month.

Functional Verification

1. For an employee earning less than the SGC minimum $450 in their first pay of the calendar month 2. Calculate a Correction Pay prior to calculating the first ordinary pay period of the month NOTE Ensure this Correction Pay has less than $450 OTE and so does not incur SGC 3. Proceed to calculate the employee's regular pay which exceeds $450 OTE and so incurs SGC NOTE Both the Correction pay and regular/ordinary pay will be paid on the same date NOTE As the Correction pay is not yet finalised by being Paid, the regular pay does not include it in the OTE for the calculated SGC 4. Process a Bank Download including both the Correction and regular pay - for the same Paid Date 5. Calculate the employee's next regular pay due for payment within the same Calendar month. i.e. Expected Paid Date is within the same calendar month 6. Confirm that the SGC calculated has included the entire calendar month OTE and therefore corrects the previously underpaid SGC from the first Correction pay.

Solution Implemented

The Australian Superannuation calculator has been corrected to ensure that all OTE of a calendar month are included when calculating SGC. This ensures that any underpaid SGC within the calendar month is corrected in subsequent pays of the month. NOTE When the SGC rate is changed it will be applied to all OTE of the calendar month that the rate change is made. Alternatively, if an actual mid-month rate change is required and is not to be applied to the entire calendar OTE paid to employees, then new super funds must be created and assigned to the employees.

HRPC-2501 - NZ Alternate Leave processing taken balance incorrectly

Functional Issue

The NZ leave accrual conversion for Hours to Days is incorrect for an employee with an ad hoc leave accrual not defined on the employee entitlements and the pay is re-calculated without selecting the load timesheets calculation option.

Functional Verification

1. Locate an Employee with an daily ad hoc accrual not defined within the employee entitlements. e.g. Alternate Leave accrued via timesheet entry 2. Approve leave of multiple days to be reduced from this accrual 3. Navigate to Adjust Pay and Load the pay period that includes the approved leave 4. Calculate the pay with Load entitlements and timesheets selected 5. Review the calculation audit and confirm the Hourly leave taken is converted to the correct number of leave in Days 6. Review the employee's accrual details and confirm the correct number of days are recorded within the leave taken transactions 7. Re-calculate the pay without selecting the Load timesheet option 8. Review the calculation audit and confirm the Hourly leave taken is converted to the correct number of leave in Days 9. Review the employee's accrual details and confirm the correct number of days are recorded within the leave taken transactions.

Solution Implemented

The pay calculation process has been changed to ensure the Hour to Day leave conversion is correct for ad hoc accruals which are not defined on the employee entitlements.

HRPC-2549 - ComSuper EPSC and Cents per KM rates for the 20/21 financial year (late updates)

Functional Issue

The Commonwealth Superannuation Corporation (CSC) Employer Productivity Superannuation Contribution (EPSC) rates have been published for the 2020 - 2021 financial year. The Australian Tax Office (ATO) have published an update to the approved reimbursement rate for the Cents per Kilometre Reimbursement thresholds (CPKR) effective 01/07/2020.

Functional Verification

EPSC Scales Update: 1. Log into the Payroll Officer workplace 2. Select the Manage Payroll tab 3. Navigate to the EPSC Productivity Component scales (Payroll Management -> Other Scales -> $AU - Australia -> AU_EPSC - Productivity Component) 4. Confirm the scales effective 01/07/2020 are defined 5. Confirm the scale details are defined per the CSC website. CPKR Scale Update: 1. Log into the Payroll Officer workplace 2. Select the Manage Payroll tab and expand the Other Scales section within Payroll Management 3. Expand the $AU - Australia region section of the other scales 4. Confirm the $AU region includes the scale type 'AU_CPKR - Cents per Kilometre Reimbursement' 5. Expand the AU_CPKR scale type and confirm the scale has details effective 01/07/2020 6. Confirm the scale details are column (X) - maximum value, column (A) - 5,000.0000, and column (B) - 0.7200 7. Column (A) represents the annual tax free kilometres threshold and column (B) represents the ATO approved reimbursement rate. NOTE: The tax free kilometres threshold remains unchanged at 5,000 km.

Solution Implemented

Updated the systems Other Scales to include the latest EPSC scales. Updated the systems Other Scales to include the latest CPKR scales approved reimbursement rate. NOTE: To ensure that these new tax details are loaded into your database(s): 1. For EAS users, ensure that the latest Core Suite - Common package is installed 2. Ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server 3. For On-Premise installations, a Package Finalise can be executed after applying this update 4. If the scales are still not updated after the above, please run the 'HR & Payroll Load Region Data' function for region $AU and N for Test Mode.

HRPC-2575 - STP Zeroing YTD - enhancement to zero against previous employee Payroll Ids

Functional Issue

New payroll customers moving to TechnologyOne's STP payroll solution, may need to zero the STP employee YTD amounts at the ATO for the current financial year from the TechnologyOne payroll system. i.e. were not able to do so from the previous/old payroll system. This can be achieved via the function, STP Correction to Zero Employee YTDs at ATO. However, if the employee payroll identifiers (Id Number) have been changed as part of the new implementation, the previous system's Payroll Identifiers must be submitted in the STP update details. A new corrective option for the STP Zero YTD function is required to support this scenario.

Functional Verification

1. Navigate to Prepare STP Correction to Zero Employee YTDs at ATO function NOTE Search to find this shipped STP corrective function. The user may require access to be given. 2. Specify the As at Paid Date and the company or Id Number of one employee to process 3. Select the correction option for Transitioning between BMS Identifiers. i.e. a new payroll implementation requires zeroing of the employee YTD at the ATO under the previous BMS Identifier 4. Enter the previous BMS Id being transferred from 5. Select the new correction option to Load Previous Payroll Identifiers for employees NOTE This option is only applicable when Transitioning BMS identifiers. The previous employee identifiers must be already be loaded into the Reference Id of each employee. i.e. an alternative id that can be entered directly in Employee Maintenance or via employee import. 6. Perform the processing 7. Prepare the report to Review the STP Zero YTD Update details 8. Confirm that the previous Payroll Identifiers have been loaded for all employees included. NOTE The employee's current Id number will remain loaded if there is no Reference Id entered in their master file 9. Navigate to the STP submit function 10. Sign and submit the employee's STP details 11. Confirm that the STP Zero Employee YTDs event is submitted to the ATO. i.e. Submission Status is updated accordingly through the process stages. NOTE This can be reviewed in the STP data analysers or by running the Review STP report again. 12. Employees can confirm that their ATO MyGov Income Statement has amounts zeroed (i.e. originally entered from the previous payroll system).

Solution Implemented

The STP Corrective function to Zero Employee YTDs at the ATO has been enhanced to support loading the Payroll Identifiers from the previous system. NOTE Previous Payroll Ids must be entered into the employee master file field Reference Id which can be maintained manually or via import. If necessary, the Reference Id can be changed for the purpose and duration of zeroing the YTDs at the ATO, then restored to other required values (via employee import or maintenance after completing the STP correction).

HRPC-2592 - STP OTE - only including Doc Types P and Z

Functional Issue

The STP OTE amount reported is restricted to employee pays of Document Types P (Payroll) and Z (Termination); and excludes imported pays (row status 70). This is incorrect as adjustments to OTE should also be included in the reported STP OTE YTD. E.g. via Correction, Bonus, Misc, Other Pay, or non-P doc types used as employee's regular pay. The OTE amount reported should be defined by pay component configuration only (config codes SUP_ORDHRS less SUP_REDUCE). Refer to ATO guidance on SGR 2009/2 for OTE inclusions. NOTE An employee's OTE YTD amount is only reported in STP when there has been no SGC (Superannuation liability) included in their YTD pays. MyGov Income Statements do NOT include or display reported OTE, only actual SGC employer payments.

Functional Verification

1. For an employee with no paid SGC in their YTD pays. E.g. Correction pays reversed previous incorrect payments resulting in zero values for the employee's Gross, Tax and SGC YTD amounts. 2. Navigate to any STP Prepare function. e.g. Update Employee YTD or EOFY Finalisation 3. Process the STP details for this employee 4. Run the Review STP report 5. Confirm that the employee's SGC is zero and that an OTE is included and correct (based on configured payments to identify Ordinary hours applying to Superannuation Guarantee).

Solution Implemented

STP OTE calculation process has been updated to ensure all paid OTE payments of any document type are included. OTE amounts paid are identified with the pay component config codes - SUP_ORDHRS less SUP_REDUCE.

RELEASE May 2020.2

HRPC-2605 - Leave liability is not calculating for number of employees

HRPC-2605 - Leave liability is not calculating for number of employees

Functional Issue

Leave Liability is not calculated for employee accruals that have an Accrual Start Date prior to the current Date Hired.

Functional Verification

1. For an employee who is on an accrual that has an Accrual Start Date prior to their current Date of Hire. E.g. LSL 2. Navigate to Calculate Leave Liability function 3. Process the employee's leave liability 4. Confirm the employee's calculated leave liabilities includes all the employee's accruals that are configured for leave liability inclusion (i.e. pay component config code LLIAB_INCL).

Solution Implemented

The Leave Liability calculation has been corrected to ensure all accrual codes are included regardless of the Accrual Start Date when they are configured for Leave Liability (LLIAB_INCL). Only active accruals in current entitlements will be included in accrual processing.

RELEASE May 2020

HRPC-1496 - PNG - Changes in Taxation to Long Service Leave 1 Jan 2018

HRPC-1624 - Leave Liability continues to increase for employees with service-based accruals who have not worked in the period. e.g. Casuals or on LWOP.

HRPC-1682 - Maximum super contribution quarterly base requires an override option

HRPC-1690 - Leave Liability Calculation - performance improvement by restricting Accrual Forecast to LL accrual pccs

HRPC-2068 - InvalidCastException on Import Termination Pay Document

HRPC-2254 - Single Touch Payroll - Correction to Zero Employee YTDs at ATO

HRPC-2315 - Pay import errors for inactive positions caused by mid-period job change

HRPC-2363 - SGC double paid when employee has retrospective change of fund occurring before last pay Paid Date

HRPC-2366 - NZ legislative changes effective 1 April 2020

HRPC-2387 - IRD Payday Submission functionality for STC/Student Loan rates not correct.

HRPC-2393 - PG region issues with AL/LSL termination tax calculation

HRPC-2399 - Application error when trying to pay an employee under 18

HRPC-2411 - NZ Retro CiA Leave on Public Holiday reversing base pay at wrong rate

HRPC-2475 - PNG Termination Post 93 LSL Withholding Discount Accrual Rate Limit

HRPC-2509 - $AU ATO legislative changes effective 01/07/2020

HRPC-2572 - Option to not display the super paid date on pay advice

HRPC-1496 - PNG - Changes in Taxation to Long Service Leave 1 Jan 2018

Functional Issue

Papua New Guinea Legislative changes at 1 Jan 2018 to Long Service Leave ($PG region). On Termination, PNG employees who have Long Service Leave (LSL) accrued since 1993 and have 5 or more years of service, will have a discounted withholding rate applied to their post '93 termination Long Service Leave (LSL). As advised by the PNG IR these rates are: 1. Termination LSL Leave Accrued less than 5 years - withhold at the marginal rate (annualised option) 2, Termination LSL Leave accrued 5 years to less than 9 years - withhold at 15% 3. Termination LSL leave accrued 9 years to less than 15 years - withhold at 8% 4. Termination LSL leave accrued 15 years and more - withhold at 2%.

Functional Verification

1. For a PNG employee who has long service leave with a work period of 15 years or greater and is terminating their employment 2. Create a termination activity for the employee 3. Calculate a termination pay for the employee 4. Review the calculation audit for the employee termination pay 5. Confirm the termination pay has calculated the post '93 LSL correctly 6. Confirm the termination pay has calculated the discounted post '93 LSL withholding rate as 2%. NOTE: The discounted withholding rate is limited to an LSL accrual rate of 6 months leave per 15 years of service.

Solution Implemented

The $PG region termination pay process was updated to process post '93 LSL at the discounted withholding rate per the IRC table of rates: 1. Termination LSL Leave Accrued less than 5 years - withhold at the marginal rate (annualised option) 2, Termination LSL Leave accrued 5 years to less than 9 years - withhold at 15% 3. Termination LSL leave accrued 9 years to less than 15 years - withhold at 8% 4. Termination LSL leave accrued 15 years and more - withhold at 2%. NOTE: 1. All of the above discounted withholding rates are limited to the accrual rate of 6 months leave per 15 years of service. The excess of this accrual rate limit will be withheld at the marginal rate. 2. The pre '93 withholding rate of 2% remains unchanged.

HRPC-1624 - Leave Liability continues to increase for employees with service-based accruals who have not worked in the period. e.g. Casuals or on LWOP.

Functional Issue

The Leave liability process is using forecast leave balances for employees on service-based accruals who have not worked in the period. e.g. from work patterns or timesheet formats. This artificially inflates the leave liability for employees on unpaid leave or casuals who have not worked during the liability period (e.g. calendar month).

Functional Verification

1. Navigate to Control Variable Maintenance and ensure the new control variable for Forecast Service Based Leave Liability (HR_LLIAB_SRVFCAST) is set to No (the default value) 2. Identify an active, casual employee who has not worked in the liability period (e.g. month). This employee must have a current service-based accrual in their entitlements. Alternatively, identify an employee on unpaid leave (LWOP) during the liability period (i.e. who has not recorded service hours contributing to their accrual) 3. Navigate to Calculate Leave Liability for Employee 4. Proceed to calculate Leave Liability for the identified employee(s) 5. Confirm that the Leave Liability result is correct for the employee and has not inflated the accrual liability incorrectly. i.e. with an additional forecast balance based on work pattern, timesheet or default working hours. NOTE For an employee who has not worked during the liability period, their service-based accrual liability will be based on the actual accrual balance.

Solution Implemented

The Leave Liability process has been modified to ensure service-based accrual liability is not inflated for employees who have not worked during the liability period. e.g. Casuals or those on LWOP. In this scenario, the current accrual balance is used for the liability instead of a forecast balance. A new Control Variable has been shipped - Forecast Service Based Leave Liability (HR_LLIAB_SRVFCAST) with a default value of No. If preferred, the user can change this value to Yes thereby forcing a forecast accrual calculation for Leave Liability processing of all employees. i.e. reverting to the previous leave liability calculation which forecasts service-based accruals from work patterns of employees who have not been paid service hours in the period.

HRPC-1682 - Maximum super contribution quarterly base requires an override option

Functional Issue

Effective-dated Maximum Super contribution quarterly base requires an override to allow employees to contribute past the quarterly amount.

Functional Verification

1. For an employee who will exceed the current ATO threshold for the SGC quarterly maximum contribution. e.g. $57,090 - as defined in the 1/7/2020 effective-dated Other scales for $AU (AU_SUP_BAS). 2. Navigate to Default Control Variable Maintenance 3. Confirm the new variable is available - HR_SUP_BASE_MAX_OVR - Override Maximum Quarter Base for Super Guarantee 4. Override with a new maximum amount allowed for SGC contributions per employee. e.g. $80,000 5. Calculate several pays for the employee (within 3 months) 6. Confirm the employee's generated SGC contribution has exceeded the ATO's maximum and is capped as per the value set in the control variable override (HR_SUP_BASE_MAX_OVR).

Solution Implemented

A new control variable has been implemented to allow employees to exceed the ATO maximum quarterly base for SGC, and set an overriding Quarterly SGC maximum base. HR_SUP_BASE_MAX_OVR - Override Maximum Quarter Base for Super Guarantee

HRPC-1690 - Leave Liability Calculation - performance improvement by restricting Accrual Forecast to LL accrual pccs

Functional Issue

The Leave Liability calculation processes the accrual forecasts of all accruals of the employee(s), instead of only those configured for Leave Liability via the LLIAB_INCL configuration code.

Functional Verification

1. Navigate to Pay Component Maintenance 2. Open the accrual Pay Components and ensure only those ones valid for the Leave Liability have the configuration code LLIAB_INCL selected. e.g. Annual Leave 3. Navigate to the Calculate Leave Liability - for Employee or Group 4. Calculate the next period 5. Navigate to the Calculation Audit of one or more included employees and confirm that only the accruals selected for Liability are included in the accrual forecasts. e.g. Annual Leave.

Solution Implemented

The Leave Liability calculation process has been enhanced to only forecast those accrual codes that are selected for Liability (via the LLIAB_INCL configuration code in Pay Component Maintenance). NOTE If using Combined Accrual Rules, ensure that all accrual codes involved are configured for Leave Liability for them to be included in this process and liability figures (with config code LLIAB_INCL).

HRPC-2068 - InvalidCastException on Import Termination Pay Document

Functional Issue

An exception can occur when Importing a termination pay for an employee who does not have an associated Termination record. i.e. Termination Date after Date of Hire and on or prior to termination pay period end date.

Functional Verification

1. For an active employee without a Termination record beyond their Date of Hire 2. Prepare an pay import file with a termination pay for that employee 3. Process the import file 4. Confirm that there is no exception error returned 5. Confirm that the import log contains a message telling that the employee must be terminated prior to calculating their termination pay. NOTE If required, manually delete the empty termination pay master from Process Termination Pay for Employee.

Solution Implemented

The payroll import process has been enhanced to check for an associated employee termination date when importing termination pays.

HRPC-2254 - Single Touch Payroll - Correction to Zero Employee YTDs at ATO

Functional Issue

A new corrective STP Update function is required to enable employers to zero the YTD amounts of employees at the ATO for a given BMS/ABN/Branch. This may be necessary for scenarios where successful STP submissions were made in a Financial Year, but the payroll employer is: - Transitioning from an old BMS (previous payroll solution) - Correcting an incorrect ABN used for a payroll Company (but was accepted in the ATO systems) - Correcting an incorrect Branch used for an ABN of a payroll Company (but was accepted in the ATO systems) NOTE The ATO systems have not rejected the previous STP submissions in all these scenarios. i.e. Passed ATO Access manager registration checks of STP events. This can be caused by the ATO systems: 1. accepting the incorrect Branch Nbr supplied in STP events, and replacing it with a Branch Nbr they have located as registered for the ABN, OR using the default branch 001. 2. accepting an ABN in an STP event that is registered for BAS (or other) but NOT PAYG withholding.

Functional Verification

This process function is a variation of the existing STP function, “Prepare STP Update Employee YTD for ATO”. This new update function prepares a corrective STP Update event that ZEROES employee YTD amounts for either a single employee or company. NOTE This corrective STP Update function can be accessed directly if needed by the Payroll Officer. i.e. One of the scenarios listed has occurred and the employee YTD amounts need to be zeroed at the ATO to avoid duplication of MyGov Income Statement YTDs. The requirement to use this function is rare and commonly required only once (per company or new installation), therefore this function is not included in menu lists for STP or Payroll Processing. This corrective STP Update can be run for a single employee or all employees of a selected company. After preparing the STP data, the user then submits the details to the ATO via SBR2 transmission supported by the product infrastructure (the Standard Business Reporting framework used by the ATO for STP). Refer to linked function 'Submit STP Correction to Zero Employee YTDs at ATO'. IMPORTANT: Ensure that the Zeroing Update event has been reviewed and submitted to the ATO PRIOR to running any subsequent corrective STP UPDATE Employee YTDs event. e.g. Transferring YTDs from an incorrect Branch to the correct Branch. Running any type of STP Update event (Update YTD, EOFY, Zeroing YTD) for a specific Paid Date will replace any unsubmitted Update events of the same Paid Date and other main criteria - Paid Date, Company, Pay Group, Id Number. i.e. will be detected as a re-run or correction. Prerequisites: 1. The customer must be registered with both ATO and TechnologyOne for STP before being able to make submissions to the ATO. I.e. The ATO will return with errors if a relationship between all parties is not detected in their systems. 2. Only zeroing YTD amounts for employees that have been Paid in the Financial Year of the As At Paid Date entered will be included in STP reporting data. 3. The payroll officer must have Payroll Corrective Access on their User Authorisations to either: - Allow Reprocessing of Finalised Pays; or - Allow Reprocessing of PAYG Summaries 4. The payroll officer will be limited to the companies and employees that they have security access to. 5. STP is only applicable to Australian payroll companies. i.e. companies assigned to other regions will be excluded from STP processing. Key Fields The 'As At Paid Date' is mandatory. Additional Processing Options There are several user options provided to specify what criteria is to be used to ‘STP Correction to Zero Employee YTD Amounts’. I.e. what employees are to be included: - By Employee – optional. Allows a single employee’s details to be corrected with the ATO. - Select Company to Process (that the user has security access to) – mandatory; including when an employee Id Number is specified as they may have worked for more than one company in the year. Type of Correction: One of 3 corrective options must be selected by the user: • Transitioning between BMS Identifiers • Correcting Branch Number for Company ABN • Correcting Company ABN BMS Id to zero amounts from: Only modifiable if selected option = “Transitioning between BMS Identifiers”. This value will be loaded automatically with the currently stored BMS Id in TechOne payroll system regardless of the correction option chosen. When transitioning between BMS Ids, the user can confirm this value or enter/modify it with the old BMS Id from their previous payroll solution (also as shown in MyGov). i.e. in the event they are choosing to continue STP using the newly generated BMS Id from TechnologyOne Payroll. Company ABN to zero amounts from: Modifiable for all correction options. Loads automatically with the ABN of the selected Company. The user can modify this value if they are correcting a previously transmitted ABN under the BMS Id (either entered or the current T1 HRP value used in STP events). Branch Number to zero amounts from: Modifiable for all correction options. Loads automatically with the Branch Number of the selected Company. The user can modify this value if they are correcting a previously transmitted Branch Number for the Company (as per ABN) under the BMS Id (i.e. as modified for the previous system’s BMS Id or for the current T1 HRP BMS Id being used in STP events). Taxation Supplier The user must select a Taxation Supplier if: 1. they wish to submit the STP Pay Events across multiple Companies under a single Intermediary ABN, or 2. they are providing Payroll services for their registered payroll companies. In this scenario, the payroll agent must have received a written Declaration from each Payroll Company that they service. NOTE If the payroll officer does not select a Taxation Supplier, but does have access to multiple payroll companies that they are authorised to pay and submit STP pay events, then each STP Pay Event will contain only a Declaration for the payroll ABN/Branch with the user’s details as the authorised representative. i.e. There will be no Intermediary Declaration details included in the STP pay event. Each company will be processed as if individually signed and declared by the same individual. Links to other Functions After preparing the STP Pay period data, the payroll officer will proceed to the next steps of reviewing the data (optional) prior to submitting the prepared Update STP to the ATO (via SBR2 infrastructure). • Review STP Zero YTD Update Report • Submit STP Correction to Zero Employee YTDs at ATO

Solution Implemented

New STP Corrective functions have been shipped to Prepare and Submit 'STP Correction to Zero Employee YTDs at ATO'. A new report has been shipped and linked to these functions to review the STP data prepared - 'Review STP Zero YTD Update Report'.

HRPC-2315 - Pay import errors for inactive positions caused by mid-period job change

Functional Issue

The pay import process only acknowledges valid pay items for the positions found to be active as at the Pay Period End Date of the imported pay. Therefore if an employee has a mid-pay period change of position, an import of their pay will fail for those pay items related to the old position they held at the start of the pay period.

Functional Verification

1. For an existing employee who changes position mid-pay period. i.e. Job Effective Date occurs prior to the next Pay Period End Date 2. Create a payroll import file for the employee that includes pay items for both the previous position and their new position. i.e. for the active Pay Period that contains their mid-pay period job and position change 3. Navigate to the HR and Payroll Import function and Import the file 4. Confirm that the file is imported correctly for both old and new position pay items.

Solution Implemented

The Payroll import functionality has been enhanced to assign the appropriate pay item dates based on the imported employee's positions in all their active Jobs occupied during the pay period represented by the imported Document Type.

HRPC-2363 - SGC double paid when employee has retrospective change of fund occurring before last pay Paid Date

Functional Issue

An Australian employee's SGC can be overpaid (i.e. doubled) if they have changed Superannuation fund(s) retrospectively with an Effective Date prior to their last pay's Paid Date. i.e. On the employee's next pay, the change of Super Fund Code prevents the super calculation from detecting the previous pay period's SGC contribution when it occurred in the same calendar month (e.g. pays paid within 1 Sept - 30 Sept). As a result, the current pay period's SGC contribution to the new Super Fund code is inflated. e.g. doubled.

Functional Verification

1. For an Australian employee who has been previously paid and is changing their Superannuation fund which pays their SGC contribution 2. Ensure the Effective Date of the employee's new Superannuation Details is dated PRIOR to their last pay's Paid Date. i.e. a retrospective superannuation fund change 3. Calculate the next pay which has a Paid Date within the same calendar month as the last pay. E.g. Paid Date 5 Sep 2019 and next Paid Date 21 Sep 2019 4. Confirm that the pay's SGC amount is correct for the current pay period and new fund. i.e. SGC amount has not been inflated.

Solution Implemented

The Australian Superannuation calculator has been enhanced with additional checks to ensure all calendar month SGC contributions are considered regardless of Fund code.

HRPC-2366 - NZ legislative changes effective 1 April 2020

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2020: 1. The ACC earners levy scales have been updated as at 1 April 2020. 2. The Student Loan repayment threshold has been amended as at 1 April 2020. 3. Inland Revenue have advised for employees who have supplied an IR330/330C certificate, the STC tax code has been renamed to Tailored Tax Code (STC). 4. Inland Revenue have advised that the ESCT withholding rate for employees who have commenced in the previous tax year is to be based on the current financial year's estimated income.

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2020 and are for the correct percentage and maximum levy. The Earners Levy percentage for 1 April 2020 is 1.39% for annual income less than $130,911 and the maximum levy is $1,819.66. 2. Calculate an ordinary pay after the 1st April 2020 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Student Loan Changes: 1. Verify the Student Loan scales (NZ_SL) exist for 1 April 2020 and are for the correct percentage and maximum levy. The Student Loan percentage for 1 April 2020 is 12.0% (A) for annual income greater than $20,020 (X). 2. Calculate an ordinary pay after the 1st April 2020 for an employee with tax code M SL. 3. Review the calculation audit. 4. Confirm the new Student Loan repayment threshold was used for the tax calculation. The Tailored Tax Code (STC) name change: 1. Load the current tax details for an employee. 2. Select the Tax Code drop down combo. 3. Confirm the STC tax code description has changed to 'STC - Tailored Tax Code'. NOTE: As Tax Scale Standard code descriptions can be modified per installation, only new sites will receive this update via the shipped system data. Existing sites can manually maintain the 'TAX_SCALE_CODE' standard code type to modify the description of the code Id 'STC' accordingly. ESCT withholding rate for new employees within the previous financial year: 1. Locate an employee whose hire date is within the previous financial year and is entitled to Kiwisaver. 2. Load the first ordinary pay period after the 01/04/2020. 3. Calculate the pay period with entitlements loaded and process options tax, superannuation and banking selected. 4. Review the ESCT section of the calculation audit. 5. Confirm the estimated income for the current financial year has been generated, including estimated company Kiwisaver contributions. 6. Confirm the estimated income is correct. 7. Open the employee maintenance function for the employee. 8. Review the Superannuation Tax - Estimated tax year income section of the function. 9. Confirm the estimated income calculated within the pay has been saved to this section. 10. If the estimated income calculated within the pay is incorrect, the correct values can be saved here for the next pay calculation.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2020: 1. The ACC Earners Levy tax scales have been updated and apply to pay on or after 1 April 2020. 2. The Student Loan tax scales have been updated and apply to pay on or after 1 April 2020. 3. The STC tax code was renamed to Tailored Tax Code. 4. The ESCT estimated income calculation was changed for employees hired within the previous tax year.

HRPC-2387 - IRD Payday Submission functionality for STC/Student Loan rates not correct.

Functional Issue

IRD Payday submission file and New and Departing Employee incorrectly reports a Tax Code of STC when an employee has a Specified Tax Code. i.e. instead of reporting their actual tax code which may include a Student Loan. E.g. M SL

Functional Verification

1. For a NZ employee with Tax Details that has the Tax Code = STC Special Tax Code selected and a Specified Tax Code including a student loan, e.g. M SL 2. Generate the New and Departing Employee report 3. Confirm that the reports Tax Code field for the employee loads their Specified Tax Code. e.g. M SL (i.e. not STC) 4. Calculate and Bank Download the current pay for the employee 5. Prepare the IRD Payday Upload File for the pay 6. Confirm that the Payday report field value for Tax Code also reports the employee's Specified Tax Code. e.g. M SL.

Solution Implemented

The Payday submission file and New and Departing Employee report have been corrected to load an employee's Specified Tax Code instead of reporting the STC (Special Tax Code) code.

HRPC-2393 - PG region issues with AL/LSL termination tax calculation

Functional Issue

The $PG termination calculation had issues with the processing of Long Service Leave (LSL): 1. The initial load pre/post '93 leave taken for the LSL was not included within the accrual totals retrieved for the termination. 2. The initial load pre/post '93 leave taken for the LSL was not processed correctly by the termination calculation process. 3. The marginal tax calculation was incorrectly calculating tax rate changes retrospectively.

Functional Verification

1. For a terminating PNG employee with LSL included within their accruals 2. Create an initial load for the LSL as at the most recent accrual calculation date, as well as the accrual and pro-rata balances add the pre/post '93 LSL taken within the respective fields 3. Confirm the initial load has been saved correctly 4. Create a termination activity for the employee 5. Calculate the termination pay for the employee 6. Review the termination leave section of the termination pays calculation audit 7. Confirm the initial load pre '93 LSL taken has been included within the LSL calculation 8. Confirm the initial load post '93 LSL taken has been included within the LSL calculation 9. Confirm the initial load balances and leave taken values are applied correctly and the final total LSL paid out is correct 10. Review the tax calculation section of the calculation audit for the termination leave, located after the termination leave section 11. Confirm the total termination leave that is being withheld at the marginal rate is correct 12. Confirm the marginal withholding calculation is correct.

Solution Implemented

The $PG region termination calculation process was updated to ensure LSL initial load leave taken and marginal tax calculation issues were resolved.

HRPC-2399 - Application error when trying to pay an employee under 18

Functional Issue

An application error can occur on payroll calculation for a new employee who is under 18 years old and their pay is the second within a calendar month that takes them over the SGC minimum earnings limit ($450).

Functional Verification

1. For a new Australian employee under the age of 18 years old 2. Ensure the employee has Superannuation Details for a fund that includes SGC superannuation 3. Ensure that the employee's first pay within a calendar month includes a Base Pay total amount of less than the SGC Minimum earnings (e.g. $450) 4. Calculate this first pay and confirm that no SGC contribution has been deducted (due to the SGC minimum) 5. Finalise this pay 6. Calculate the employee's next regular pay which falls within the same calendar month 7. Ensure that the employee's second pay for the month includes Base Pay payments that now take their earnings over the SGC Minimum earnings (e.g. $450) 6. Calculate this second pay 7. Confirm that the pay calculates successfully and now includes the SGC contribution pay item.

Solution Implemented

The Australian Superannuation calculator has been updated to correctly calculate the monthly base earnings of an employee who is under the Minimum Age and exceeds the SGC minimum earnings in the second pay of their first working Calendar month. NOTE the Minimum Age and SGC limits are configured in the Default Control Variables.

HRPC-2411 - NZ Retro CiA Leave on Public Holiday reversing base pay at wrong rate

Functional Issue

The pay calculation process generates reversal base pay items for retrospective Ci Anywhere leave being processed. If the leave period included a public holiday the base pay reversal rate maybe incorrect as the public holiday can paid at a different rate.

Functional Verification

1. Calculate a pay period that includes a public holiday 2. Confirm the base pay and public holiday are paid correctly. Finalise the pay 3. Approve Ci Anywhere annual leave for a period within the pay that includes the public holiday 4. Confirm the Ci Anywhere timesheet entries created include the public holiday is to be paid per the expected public holiday pay component. 5. Calculate the following ordinary pay period, select load timesheets and entitlements. 6. Confirm the annual leave is paid per the Ci Anywhere timesheets, including the public holiday. 7. Confirm the process has generated base pay reversal pay item(s) for the annual leave days. 8. Review the Ci Anywhere timesheet loading section of the calculation audit. 9. Confirm the public holiday included within the retro leave has been narrated as being excluded from the pay. 10. Confirm the process has stamped all retro Ci Anywhere timesheet entries, including the public holiday, as paid. Note: The process will not create any pay item(s) for public holidays that are within Ci Anywhere retro leave.

Solution Implemented

The pay calculation process was changed to ensure retrospective Ci Anywhere leave timesheet entries do a base pay reversal pay item on the correct pay component for public holidays.

HRPC-2475 - PNG Termination Post 93 LSL Withholding Discount Accrual Rate Limit

Functional Issue

The PNG post '93 LSL termination process was unable to calculate the employee's accrual rate limit when the ordinary pay period had not been defined for the period the termination is within. NOTE This issue can be resolved through the application by calculating one or more employee regular pays for the Pay Period End Date, thereby creating the pay period master record required for the termination process.

Functional Verification

1. Create a termination activity for a PNG employee with LSL accrued 2. Review the maintain pay period for the pay group the employee is assigned to 3. Confirm the pay period has not been defined for the period that the termination is within. i.e. no other pays have been calculated for that pay period 4. Calculate the termination pay 5. Review the withholding rate for post '93 LSL section of the calculation audit 6. Confirm the withholding rate for post '93 LSL has been calculated correctly 7. Confirm the audit indicates the LSL accrual rate limit has been calculated correctly.

Solution Implemented

Changed the PNG termination process to ensure the post '93 LSL accrual rate limit calculation completes successfully when no ordinary pay period has been generated for the period that the termination pay is within.

HRPC-2509 - $AU ATO legislative changes effective 01/07/2020

Functional Issue

1. The Australian Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) Other Scales are to be updated from 1 July 2020 2. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2020 3. The Maximum super contribution base amount will increase from 1 July 2020 4. The indexed ETP cap amount will increase from 1 July 2020.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace 2. Navigate to the Manage Payroll Tab 3. Navigate to the Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) income thresholds (Other Scales -> $AU - Australia -> AU_HELP - HELP): 4. Confirm that new Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) income thresholds are available for the 1 July 2020. Note: The separate SFSS scales are now obsolete and will not be updated. 7. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Scales -> $AU - Australia -> AU_GRTFL): 8. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2020. 9. Navigate to the Maximum Super Contribution Quarterly Base (Other cales -> $AU - Australia -> AU_SUP_BAS): 10. Confirm that the Max Quarterly Base is $57,090.00 - details scale column (B). 11. Navigate to the Employment Termination Payment (ETP) CAP Amount (Other Scales -> $AU - Australia -> AU_ETP_CAP): 12. Confirm that the ETP Cap Amount is $215,000.00 - details scale column (B).

Solution Implemented

1. Study and Training Loans (HELP,VSL,SFSS,SSL,TSL) for the 2020-2021 financial year (refer to ATO website). 2. New Australian Genuine Redundancy Tax Free Limit thresholds have been added for the 2020-2021 financial year (refer to ATO website). 3. The Other Scale for the Superannuation Maximum Quarterly Base has been updated effective 1 July 2020 (to 57,090.00) 4. The Other Scale for the ETP Cap Amount has been updated effective 1 July 2020 (to 215,000.00). 5. The Commonwealth Superannuation corporation (CSC) have NOT published the new EPSC rates for 1 July 2020, we will provide an updated release when the new rates are published. IMPORTANT NOTE At time of this publication the ATO had not released updated Tax Scales 2020-21 for the medicare levy threshold changes. These will be released as soon as they become available. ETA Post October 2020 budget. As per every EOFY, legislative Tax Scales can be updated or added manually by users. Please refer to the Customer Community for the EOFY Knowledge Base articles for further details. NOTE: To ensure that these new tax details are loaded into your database(s) for releases 2019A onward: 1. Ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server. 2. Alternatively, for On-Premise installations, a Package Finalise can be executed after applying this update. 3. If the scales are still not updated after the above two solutions, please run the 'HR & Payroll Load Region Data' function for region $AU and N for Test Mode. NOTE: If employers have not taken the Legislative release updates for Payroll beyond May 2017 (2017A) then the above tax scales changes must be done manually. Additionally, the DEFAULT control variable values for ETP Cap and Super Quarterly Max must be updated manually after 30 June 2018. i.e. These Control Variable values are obsolete and no longer updated from the 1/7/2017 values: 1. HR_SUP_BASE_MAX 2. HR_ETP_CAP

HRPC-2572 - Option to not display the super paid date on pay advice

Functional Issue

Ci Anywhere payroll processing does not support setting the expected superannuation payment date field as part of the pay advice process as it is no longer required to be displayed on pay advices. As some customers may still be using this in Ci, an option to show or hide this label is required.

Functional Verification

1. Calculate a pay for an employee in Ci Anywhere 2. Using the document definition '$P1PAYADAU', produce a pay advice 3. Verify the Expected Superannuation Payment Date label is not displayed in the generated pay advices

Solution Implemented

The shipped Australian Pay Advice templates have been modified to include an option to hide the Expected Superannuation Payment Date label. This is done via a system variable (HR_PAYSLIP_SUPDATE) that is created by the Ci Anywhere Pay Advice process.

RELEASE November 2019

HRPC-99 - Employee Superannuation ordinary pay contribution amount updated by Termination process

HRPC-498 - The Calculation Audit is confusing explaining NZ IRD ESCT calculation

HRPC-615 - Casual Loading is not showing in Pay Calculation Report

HRPC-656 - Payslip not always showing the period entitlement of a roster-based accrual

HRPC-706 - Deleted payroll does not delete manually entered Leave taken lines

HRPC-822 - Security issue in Calculate Manual Back Pays by Group Function

HRPC-1049 - Pay includes pay items that have no pay calculation date and/or are not included in the pay nett and tax amounts

HRPC-1302 - Termination Pay Run excluding annual leave pay out

HRPC-1343 - Super contribution YTD adjustment not showing on the payslip

HRPC-1539 - NZ 8% Term Pay - History pay not pro-rata'd for mid-period anniversary

HRPC-1598 - The amount calculator for AWE under the NZ Holidays Act 2003 calculates rates based on average hourly earnings over the year (instead of average weekly earnings).

HRPC-1605 - Manual Back Pay - include previous Back Pays in Manual Back Pay process

HRPC-2043 - STP Termination PAY event - Period Gross amount not equal to Taxable Income pay items

HRPC-2057 - Payroll Transaction Drilldown enquiry doesn't display Payroll Transactions for Balancing Transactions in GL Account

HRPC-2069 - Single Touch Payroll - Duplicated inclusion of employee YTD Tax

HRPC-2085 - SAVE has been removed as an ‘Action to Perform’ from the Adjust Pay screen for paid pays

HRPC-2088 - Com Super EPSC Scales Effective 01/07/2019

HRPC-2090 - Payslip Format - IRD Number field placement - Privacy Issue Raised.

HRPC-2107 - Cents per Km reimbursement can't assess threshold from timesheet lines

HRPC-2114 - Payroll Pay Span now totals 100% and total base pay amount match employee entitlements when pay period has multiple Work Patterns

HRPC-2144 - Update Paid Date - ensure that uncalculated pays are not updated by the process

HRPC-2147 - TFN efile v4.0 - warning on payee email addresses due to missing dots

HRPC-2150 - ATO 2019 changes to merge Study and Training Support Loans

HRPC-2161 - STP - Commencement Date in UPDATE events

HRPC-2163 - STP - Lump Sum D not reported when only ETP in FY

HRPC-2167 - STP EOFY/YTD Update where employee worked for 2 companies in the financial year

HRPC-2176 - STP - Lump Sum A type does not match payment when multiple terminations

HRPC-2182 - Rerunning TFN eFile failing

HRPC-2189 - NZ IRD KED (KS1) process errors for employees on Contributions Holiday

HRPC-2273 - Manual Back Pay does not correctly apply rate increases to pays that include leave adjustments

HRPC-2331 - No Superannuation when ordinary hours are not worked on primary position

HRPC-2343 - Australian Termination recalculation removes the leave paid out on termination

HRPC-99 - Employee Superannuation ordinary pay contribution amount updated by Termination process

Functional Issue

The termination pay process is recalculating the ordinary employee superannuation per the pay component configuration while calculating the termination leave pay out. As the leave has already been generated, the ordinary employee superannuation is being inflated by these extra earnings.

Functional Verification

1. For a New Zealand employee with Superannuation and regular pay owing 2. Terminate the employee 3. Process the Termination Pay 4. On the Calculation Options, uncheck Superannuation and recalculate 5. Ensure that Pay Item Rate and Amount of Base and Superannuation Pay Items are correct. Specifically, that the superannuation from the normal pay has not been recalculated and inflated to include termination earnings.

Solution Implemented

Additional validation has been added to ensure the Superannuation pay items are not recalculated.

HRPC-498 - The Calculation Audit is confusing explaining NZ IRD ESCT calculation

Functional Issue

The NZ ESCT section of the calculation audit can narrate the wrong KiwiSaver contribution rate in some circumstances. E.g. reporting a ESCT rate of 0.02746 in a termination pay when the rate used was 0.03.

Functional Verification

1. Calculate a termination pay for a New Zealand employee with KiwiSaver contributions 2. Confirm the ESCT section of the calculation audit has narrated the correct contribution rate.

Solution Implemented

The NZ superannuation process has been corrected to accurately report the NZ ESCT rate used in the pay calculation.

HRPC-615 - Casual Loading is not showing in Pay Calculation Report

Functional Issue

Pay items are excluded from the Pay Calculation report when the Pay Component Type of a pay component code has been changed.

Functional Verification

1. For scenarios where the Payroll Officer has changed the Type of a Pay Component after it has been used in employee pays NOTE This practice is not advised as it may have several ramifications in payroll and reporting. 2. Navigate to the Pay Calculation report 3. Complete the criteria for a pay period prior to the change of the pay component 4. Confirm that the report correctly includes the changed pay component and its values for the pay period.

Solution Implemented

The Pay Calculation reports have been modified to rely on the configured Type of the pay components included. i.e. not the Pay Component Type saved at the time of pay calculation. NOTE The Pay Component Maintenance function of package Payroll Management will be enhanced to avoid this change of configuration, by preventing a change of Pay Component Type once a pay component code has been used in employee pays.

HRPC-656 - Payslip not always showing the period entitlement of a roster-based accrual

Functional Issue

In the Pay Advice, an employee's Period Accrual value is not always shown for manual/roster-based accruals. E.g. Banked RDO accrual is increased in a normal pay. This occurs if the accrual process for the employee is run after the pay and for the same date (Pay period end date).

Functional Verification

1. For an employee receiving a roster-based/manual accrual such as RDO 2. Calculate their pay where the roster-based accrual is included 4. Calculate the employee's leave accruals for the same date (Pay Period End Date) 5. Generate the employee's pay advice 6. Confirm that the roster-based leave accrual has the expected Period Accrual value and balances displayed correctly in the pay advice.

Solution Implemented

The accrual pay summary processing has been updated to ensure that manual/roster-based accruals have the Period Accrual value restored during a leave accrual process (which does not create the accrual that is loaded/accrued via a pay and/or timesheet).

HRPC-706 - Deleted payroll does not delete manually entered Leave taken lines

Functional Issue

On deletion of a Pay, any manually entered leave taken is not deleted from the corresponding Leave Taken table (HRPAY_LVE_TKN_DTL). This results in the accrual balance being incorrect, and a data fix to remove the orphaned manual leave taken records (i.e. not approved via Leave or Timesheet modules).

Functional Verification

1. As a Payroll Officer, navigate to the Adjust Payroll function 2. Create or retrieve a pay for an employee 3. Manually add a pay item for Leave Taken and recalculate. e.g. pcc type 500 for sick leave 4. Delete the pay 5. Confirm that the employees accrual balance has also restored the deleted Leave Taken units.

Solution Implemented

The pay master process has been updated to ensure that manually entered pay items for leave taken are also removed on deletion of a pay. Thereby ensuring that the accrual balance remains correct after the pay deletion.

HRPC-822 - Security issue in Calculate Manual Back Pays by Group Function

Functional Issue

Employee security is not applied to the displayed grid of Employees in the Manual Back Pays by Group function. NOTE Security access is applied within the manual back pay process itself, therefore the user is only able to produce back pays for employees they have access to, regardless of their selection.

Functional Verification

1. As Payroll Officer with limited employee Security Access (i.e. user's assigned Security Category is limited to a group of employees or specific company) 2. Navigate to the function for Calculate Manual Back Pays by Group 3. Complete the criteria for the required manual back pay 4. Retrieve employees into the grid 5. Confirm that only the employees the user has access to are loaded and available for selection 6. Select employees and run the back pay process 7. Confirm the employees selected are processed and have subsequent back pays correctly created.

Solution Implemented

The Manual Back Pay enquiry used to load the grid of employees has had employee Security Category access enabled. Additionally the Employee picklist accessed from the grid has been updated to limit the selections available by security category access.

HRPC-1049 - Pay includes pay items that have no pay calculation date and/or are not included in the pay nett and tax amounts

Functional Issue

1. Importing pay items into a Paid employee's pay allows new pay items to be imported and saved, but not calculated. 2. Adding and saving new pay item(s) to a calculated employee pay does not clear the Pay Calculation Date on all the pay items.

Functional Verification

Attempting pay import to a paid or posted pay: 1. Navigate to Adjust Payroll and calculate an employee's pay 2. Bank download the pay 3. Create a pay import file for that employee's same Pay Period. i.e. including multiple new pay items for the same period 4. Import the file 5. Confirm that an error message is returned due to the pay being paid or posted 6. Navigate to Adjust Payroll and retrieve the employee's same pay 7. Confirm that the pay has not been modified by the import and the pay items reflect the same as in the unchanged Calculation Audit 8. Repeat steps 1-7 to test a Posted but not Paid employee pay. i.e. replace step 2 with Payroll Posting of the employee's pay On saving without calculating a pay: 1. Navigate to Adjust Payroll and calculate an employee's pay 2. Confirm that the Calculation Date is completed 3. Add new pay item to the pay 4. Save but do NOT calculate 5. Confirm that pay Calculation Date is cleared on the pay master and all its pay items. i.e. This can be confirmed via the Adjust Pay pay items grid, Pay Transactions data analyser or attempting to Post the pay (only calculated pay items are posted).

Solution Implemented

1. The pay import process has been corrected to ensure that pay items cannot be added to a paid or posted pay. 2. The saving of a pay has been corrected to clear all pay item Calculation Dates if the pay has been Saved but not calculated (i.e. pay master Calculation Date is cleared). NOTE For the full functionality of this change the following updates are required: - HRP Core Ci package - Payroll Processing Ci package - Payroll App (CiAnywhere) - Posting (Financials) Ci package

HRPC-1302 - Termination Pay Run excluding annual leave pay out

Functional Issue

Termination pay calculation is not paying leave when the termination earnings period control variable (HR_TERM_EARNINGS_PRD) is set to a value of zero.

Functional Verification

1. For scenarios where the Termination Earnings period in Control Variables | Payroll is set to zero 2. For an Australian employee with accruals to be paid on termination 3. Process the termination by creating a Termination Activity for the employee 4. Calculate the Termination Pay 5. Confirm that termination pay contains the termination Leave 6. Confirm the termination leave has been paid out per the current unused accrual entitlement balance and pro-rata value. i.e. Is not based on a percentage of the employee earnings.

Solution Implemented

The calculation for the termination pay has been changed to ensure the termination leave is calculated on a termination earnings basis only when the termination earnings period control variable is set to a value greater than zero.

HRPC-1343 - Super contribution YTD adjustment not showing on the payslip

Functional Issue

When a Correction Pay is used to adjust the amounts of an Employee Super contribution on a pay component which is no longer included in their active Employee Super Details, the amount is not included in the pay advice section for Superannuation Details. E.g. when an optional contribution pay component is removed from the newer Employee Super Details. Instead the adjustment/correction appears in the pay Advice as a Pre Tax Deduction (not under the Super Details summary). This occurs as the manually entered pay item is missing a Super Fund. Therefore the amounts are included in a different record in the Payment Summary table (HRPAY_PAYITEMS_SUMMPMNT).

Functional Verification

1. For an employee that has a new Superannuation Details record that includes the removal of a previous optional contribution pay component 2. Calculate a Correction pay which includes a negative adjustment on the previous optional contribution pay component. NOTE this Correction pay should be dated on or after the new effective superannuation details 3. Produce the pay advice for the correction pay 4. Confirm the pay advice correctly adjusts the amounts in the Super Details section. i.e. the amounts have been adjusted to include the optional contribution correction.

Solution Implemented

The payroll advice summary process has been modified to accommodate the scenario where a superannuation pay item is missing the fund code due to a change in employee effective superannuation details. If the pay component already exists in the employee's pay Summary records, the existing record's details are updated.

HRPC-1539 - NZ 8% Term Pay - History pay not pro-rata'd for mid-period anniversary

Functional Issue

On NZ Termination pay calculation, the full earnings of a History pay are used in the 8% earnings leave calculation if the employee's last anniversary date occurs in that pay period. The History pay earnings should only include amounts after the anniversary date. i.e. prorated earnings within a pay period for after the anniversary date only.

Functional Verification

1. For a New Zealand employee being terminated who has History pays which will be used in the 8% accumulated earnings calculation. N.b. a payroll system transition results in History pays being imported to ensure employees have at least 12 months of pay history in the system to assist leave rate and earnings calculations. 2. For scenarios where the Leave Accrual anniversary date falls in one of these History pay periods 3. Calculate the Termination pay 4. Confirm that the history pay amount included in Gross Earnings total is prorated to only include the earnings after the mid-pay period anniversary date.

Solution Implemented

The NZ Termination calculator has been updated to pro-rata earnings for 8% in a History pay that includes the employee's last anniversary date.

HRPC-1598 - The amount calculator for AWE under the NZ Holidays Act 2003 calculates rates based on average hourly earnings over the year (instead of average weekly earnings).

Functional Issue

Pay component amounts based on average weekly earnings (AWE) are calculated from average hourly earnings rather than average weekly earnings. For example, given an employee paid $1000 per week, 40 hours per week over 26 weeks, and then $1000 per week, 38 hours per week over the subsequent 26 weeks, the pay component amount based on AWE would be calculated as $52,000 over 2,028 hours ($25.641026 per hour). In some cases, clients would prefer that this was calculated based on average weekly earnings, that is, $52,000 over 52 weeks ($1000 AWE) at 38 hours per week would be $26.315789 per hour.

Functional Verification

1. In Pay Component Maintenance, remove the AWE_UNITS NZ regional configuration code from all pay components. 2. For an employee, calculate ordinary pays over 12 months. 3. Submit and approve an annual leave request for this employee (where annual leave is paid based on entitlements reduced, and the reduced entitlement is calculated from the Annual Leave pay component amount calculator. 4. Process the pay containing leave for this employee. 5. Review the calculation audit log and verify that the amount calculated from AWE eligible earnings has been calculated based on average weekly earnings.

Solution Implemented

The pay component amount calculator ($HRPCM_AC_AWE) based on average weekly earnings (AWE) has been extended. Where the system is not configured to derive AWE units from pay items, the calculator will derive the AWE hourly rate using the employee's work pattern for the week prior to the calculation date.

HRPC-1605 - Manual Back Pay - include previous Back Pays in Manual Back Pay process

Functional Issue

Manual back pay is deliberately excluding previous Back Pays from the calculation. i.e. those existing back pays that occur in the specified date range.

Functional Verification

1. Ensure that the Control Variable for Document Types to Include in Retrospective Pays includes the R document type (manual back pays) 2. For a pay rate change that is retrospectively paid to employees over two separate back pay calculations. E.g. The one effective Employment Condition is updated twice for a staged rate increase: a. 1% increase from 1 July 2018 - 1 March 2019 - paid to employees on 31 March 2019 b. 1.5% further increase from 1 July 2018 - 1 March 2019 - paid to employees on 1 June 2019. 3. Navigate to Calculate Manual Back Pays by Group function 4. Calculate and finalise the FIRST Back Pay due to the employees. E.g. PPED 31/3/2019 for Date range 1/7/2018 to 1/3/2019 5. Calculate and finalise the SECOND Back Pay due to the employees. E.g. PPED 1/6/2019 for the same Date range 1/7/2018 to 1/3/2019 6. Confirm that the second back pay has included the rate adjustments to the first Manual Back Pay (PPED 31/3/2019). i.e. Navigate to Adjust Back Pay for Employee and confirm that the employee has had both pay rate increases correctly applied for all finalised pays within the date range. Including the first Back Pay of 31/3/2019.

Solution Implemented

The Manual Back Pay process has been updated to include Back Pay document type (R) in the back pay calculation. This is also reliant on the back pay document type being included in the Control Variable (HR_PAY_RETRO_DT).

HRPC-2043 - STP Termination PAY event - Period Gross amount not equal to Taxable Income pay items

Functional Issue

STP Payer Period Gross amount and Pay Master Taxable Income are not correct for a Termination Pay that includes a Lump Sum B pay item. The variation is due to the Pay Master Taxable Income duplicating the inclusion of the 5% taxable income applicable to Lump Sum B amounts.

Functional Verification

1. For a terminating employee who was has a long service payout including pre 16 August 1978 entitlement. i.e. a Lump Sum B will apply 2. Calculate the termination pay 3. Review and confirm that the termination pay is correct and includes a Lump Sum B pay item 4. Prepare STP Pay event details 5. Run the STP Review Pay details report 6. Confirm that the STP Payer Gross Amount is correct. i.e. This is the pay period total gross amount only and includes all taxable payments made to the terminating employee, including the Lump Sum B pay item amount. NOTE The STP Reconciliation report can also assist compare the pay master details with the STP amounts reported. The ATO does currently support any ability to "Correct/fix" a reported event PAY PERIOD Gross or Tax amount. Additionally it has no impact on employees YTD amounts for EOFY or the EOFY Finalisation process. There are no current impacts to ATO of this taxable income variation on a particular pay period. The employer BAS and subsequent STP employee YTD amounts correct ATO systems.

Solution Implemented

The pay process has been corrected by ensuring the Pay Master Taxable Income amount includes only the taxable 5% of a Lump Sum B pay item amount.

HRPC-2057 - Payroll Transaction Drilldown enquiry doesn't display Payroll Transactions for Balancing Transactions in GL Account

Functional Issue

From financial officer workplace, the Payroll Drilldown enquiry returns an error (Details Do Not Exist) when opened from the Transaction Details for a Balancing/Clearing ledger details. i.e. of a company superannuation contribution.

Functional Verification

1. Calculate an ordinary pay for an employee with company superannuation contributions 2. Post the payroll on-costs for the pay period 3. Review the posting log and audit report for the posting process to ensure the company superannuation is posted correctly 4. Review the company superannuation pay items within the pay and confirm the posting costing and Balancing transaction details have been saved to the pay item(s) correctly 5. Navigate to the financials function for Transaction Details which includes Payroll Drilldown access. e.g. from GL Officer workplace > Enquire on Accounts and their Transactions task 6. Select the company superannuation pay item(s) balancing ledger name and balancing account number 7. Select the transaction for the pay period posted in step 2 above 8. From the Transaction Details function select the Payroll Drilldown enquiry within the Links to other Functions 9. Confirm no errors are displayed 10. Confirm the company superannuation pay item from the pay above is displayed within the Pay items grid.

Solution Implemented

The Payroll Account Number Drilldown enquiry has been updated to load clearing account pay details for company superannuation transactions.

HRPC-2069 - Single Touch Payroll - Duplicated inclusion of employee YTD Tax

Functional Issue

The STP Tax withholding YTD amount can be duplicated if an incorrect configuration of the tax pay component has been defined - both TAX_NORMAL and TAX_EXTRA. Only one of these should be configured per pay component. However, PAYG Payment Summary load process was able to avoid the duplication of amounts due to multiple selection of pay component configuration codes.

Functional Verification

1. For a tax pay component with both TAX_NORMAL & TAX_EXTRA selected NOTE this is incorrect configuration and should be corrected to specify one tax code only. 2. For an Australian employee, finalise a pay which includes that taxation pay component 3. Run Prepare STP Pay Details for ATO 4. Via the STP review report or the STP PAY Employee Data Analyser, confirm that the Tax YTD amount is correct. i.e. the tax amount from the pay has not been duplicated

Solution Implemented

The STP Prepare process has been enhanced to ensure that Taxation YTD total amounts are not including a single pay item amount more than once, regardless of multiple config code selection on the pay component.

HRPC-2085 - SAVE has been removed as an ‘Action to Perform’ from the Adjust Pay screen for paid pays

Functional Issue

The Save action is not available to allow attachments to be saved on finalised pays. i.e. User has Corrective Access however cannot Save on a Paid/Bank Downloaded, Submitted (to Gov) or Posted employee pay.

Functional Verification

1. As a Payroll Officer 2. Load a finalised Pay which requires an attachment to be saved or deleted. i.e. Paid, Submitted or Posted NOTE Corrective Access is required on Paid or Submitted employee pays to recalculate, save or reproduce a pay advice. 3. Confirm that the Save button is only available if the user has Corrective Access turned on 4. Add a new attachment, and/or delete an existing attachment. 5. Save and Retrieve 6. Confirm that the attachment changes have been saved.

Solution Implemented

The Adjust Payroll function has been corrected to enable users with Corrective Access to Save a pay that is Paid, Posted and Submitted (STP ATO or IRD). This permits attachments to be modified, added or deleted to a finalised pay. This includes but is not limited to the attachment for pay advices. NOTE Posted and Submitted pays cannot be modified and recalculated even with Corrective Access. Correction pays should be used to adjust these finalised payments. Pays that have been Bank Downloaded only (i.e. Paid), can be modified and recalculated with Corrective Access. Submitted pays cannot be Deleted. Correction pays should be used to adjust these finalised payments. Deleting Posted pays will require financial journal adjustments.

HRPC-2088 - Com Super EPSC Scales Effective 01/07/2019

Functional Issue

The Commonwealth Superannuation Corporation (CSC) Employer Productivity Superannuation Contribution (EPSC) rates have been published for the 2019 - 2020 financial year.

Functional Verification

1. Log into the Payroll Officer workplace 2. Select the Manage Payroll tab 3. Navigate to the EPSC Productivity Component scales (Payroll Management -> Other Scales -> $AU - Australia -> AU_EPSC - Productivity Component) 4. Confirm the scales effective 01/07/2019 are defined 5. Confirm the scale details are defined per the CSC website.

Solution Implemented

Updated the systems Other Scales to include the latest EPSC scales. NOTE: To ensure that these new tax details are loaded into your database(s): 1. For EAS users, ensure that the latest Core Suite - Common package is installed 2. Ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server 3. For On-Premise installations, a Package Finalise can be executed after applying this update 4. If the scales are still not updated after the above, please run the 'HR & Payroll Load Region Data' function for region $AU and N for Test Mode.

HRPC-2090 - Payslip Format - IRD Number field placement - Privacy Issue Raised.

Functional Issue

In Pay Advice, IRD Number is placed directly below employee address and can be visible through envelope windows.

Functional Verification

1. For a New Zealand employee who has an IRD Number, calculate or load an existing pay 2. Navigate to Pay Advice and select Payment Advice NZ 3. Start Processing and confirm that the IRD Number field is now anchored to the right-hand side. (next to Tax Code) 4. NOTE As required also test the shipped Payment Advices for NZ No Prorata and Multiple Companies.

Solution Implemented

Moved IRD Number field to the right side of the pay advice to avoid display through envelope windows.

HRPC-2107 - Cents per Km reimbursement can't assess threshold from timesheet lines

Functional Issue

The cents per kilometre reimbursement process cannot load entries from employee timesheets as only the Hours unit type is able to be entered in timesheets. i.e. not Kilometers units

Functional Verification

1. Ensure the system has both a tax free and taxable car allowance pay component configured with the pay period unit 'Kilometers' and the system configuration code 'ALLW_CAR' selected. For details refer to release notes on enhancement HRPC-678 2. Define a timesheet format line with the 'Allowance' line type selected and ensure the tax free car allowance PCC configured above is defined with the selected pay components within the payroll section. The PCC can be set as default to simplify user input if desired 3. Load the timesheet entry function for an employee who is assigned to the timesheet system/format with the allowance line defined above 4. Enter allowance lines for kilometres to be claimed. NOTE The unit type will still display as Hours in the Ci timesheet entry function. 5. Calculate the ordinary pay period that includes the timesheet lines defined above, load entitlements and timesheets 6. Confirm the allowance timesheet lines are displayed within the timesheet summary 7. Confirm the pay item(s) generated from the allowance timesheet lines has been created with the pay period unit 'Kilometers', per the PCC configuration 8. Review the calculation audit and confirm the timesheet pay item has been included within the cents per kilometre reimbursement tax free threshold assessment 9. Re-do the test above for the following pay period entering and approving the Ci timesheets via employee self service.

Solution Implemented

The pay process has been changed to generate timesheet pay items per the pay component pay period unit (i.e. Kilometers) when the component is configured as a car allowance per the configuration above in step 1. NOTE: For Ci Anywhere Timesheets enhancement to accept Kilometers entry, refer to release notes on reference HRP-21435.

HRPC-2114 - Payroll Pay Span now totals 100% and total base pay amount match employee entitlements when pay period has multiple Work Patterns

Functional Issue

An employee's total base pay amount and percentage pay span amounts in the pay calculation audit were not correct when mid period position changes occurred and these affected position's were also configured with work patterns . Active days/hours from each work pattern were being combined together resulting in incorrect pay span percentages.

Functional Verification

1. Configure an employee for a monthly pay group being paid on the last day of the month. 2. Configure Entitlements, Tax and Banking. 3. Set up 2 Work Group codes (eg WG1 and WG2). 4. Set up 2 different Work Patterns (WP1 and WP2), WP1 is configured with Monday to Friday as the normal work days, WP2 is configured with Friday to Monday as the normal work days. 5. Create Work Pattern assignments via Work Groups with WG1 linked to WP1 and WG2 linked to WP2. 6. Configure the existing employee's primary position's Work Group with WG1. 7. Add another primary position effective mid period and configure that position's Work Group with WG2. 8. Calculate a pay for the employee in a pay period that contains the mid period position change. 9. Review the calculation details. 10. Confirm that percentage pay span amounts are correct for the amount of active work days that exist in the period for each of the different work patterns divided by the total active days in the period. 11. Confirm that the total base pay hours match the employee's entitlements. 12. Confirm that the base pay hours for each pay span is correct based on the pay span percentage.

Solution Implemented

The Work Patterns Ci package has been updated to correctly identify active days/hours when multiple work patterns exist in a pay period by using an employee position entitlement key filter criteria. The Payroll Processing Ci package has been updated to use the employee's position entitlement key when determining a work pattern's active days/hours. NOTE: Both the Work Patterns and Payroll Processing packages need to be updated to the latest version for this new functionality.

HRPC-2144 - Update Paid Date - ensure that uncalculated pays are not updated by the process

Functional Issue

Although the enquiry for the Update Paid Date function only returns employee pays that have NOT been calculated (i.e. do not have a Calculation Date), the process itself does not ensure that only those pay masters with both a Paid Date and Calculation are updated. This is a preventative change for pay masters that may be missing the pay calculation date, but do have a Paid Date.

Functional Verification

1. For a calculated employee pay (i.e. has a valid Calculation Date) 2. Navigate to Update Paid Date function 3. Complete the criteria to adjust the Paid Date on the recent calculated pay 4. Confirm that the employee is available for selection in the Employees grid for Update Paid Date processing. 5. NOTE Leave this function open and without changing details navigate back to the Adjust Payroll 6. Modify the same employee pay and save (WITHOUT calculation) NOTE Retrieve the pay to confirm that the Calculation Date has been cleared 7. Navigate back to the unchanged Update Paid Date function. Do NOT re-retrieve 8. With the same employee pay selection remaining, start the process to update the Paid Date (again) 9. Confirm that an error message is displayed and the employee pay has not been updated. i.e. confirm by navigating to Adjust Pay and retrieving its details.

Solution Implemented

The Update Paid Date process has additional validation to ensure uncalculated pays are not updated with a Paid Date.

HRPC-2147 - TFN efile v4.0 - warning on payee email addresses due to missing dots

Functional Issue

The new field introduced in eFile TFN v4.0 for payee email has incorrectly replaced the dots with blanks

Functional Verification

1. For an Australian employee with a TFN Declaration to be submitted to ATO 2. Ensure that the employee has a valid Email specified in the first email field in their Street Address 3. Navigate to Electronic TFN Declarations function 4. Complete the report criteria for an E-File report option 5. Start Processing 6. Review the csv file produced, and confirm that the employee's email address is correctly loaded. E.g. JSmith@gmail.com

Solution Implemented

The eFile TFND process has been corrected to ensure the Payee's email address does not replace the dots (.) with a space/blank.

HRPC-2150 - ATO 2019 changes to merge Study and Training Support Loans

Functional Issue

ATO released updates mid 2019 to Study and training support loan debts stating: Study and training support loan debts are paid off in full, one at a time, according to the hierarchy. The repayment hierarchy for study and training support loans will be: 1. HELP 2. VSL 3. SFSS 4. SSL 5. ABSTUDY SSL 6. TSL Currently users are required to ensure that only one loan is selected in Employee Tax Details otherwise the employee will incorrectly have multiple loans deducted for ATO withholdings.

Functional Verification

1. For an Australian employee with more than one loan to repay as stated on their TFN declaration. e.g. HELP, SFSS, and/or TSL 2. From Employee Maintenance, confirm that multiple loans are selected in the employee's currently effective Tax Details 3. Calculate the employee's next pay. NOTE: For pays on or after 1 July 2019 4. Confirm that only ONE deduction pay item (tax) for Study and Training Support Loan has been generated. This will be according to the ATO Hierarchy: a. HELP b. SFSS c. TSL (also selected for VSL, SSL).

Solution Implemented

The Australian Taxation calculation for HELP/TSL/SFSS has been modified to apply the ATO 2019 hierarchy order for payments after 1 July 2019, ensuring only one loan is repaid per pay. The Australian Other Tax Scales have been updated to reflect a combined Study scale: - Existing AU_HELP description updated to Study and Training Loans (HELP, VSL, SFSS, SSL, ABSTUDY SSL and TSL). - Existing AU_SFSS description updated to note now OBSOLETE.

HRPC-2161 - STP - Commencement Date in UPDATE events

Functional Issue

Employee Commencement Date should always be reported in STP Update YTD events to ensure that the ATO MyGov Income Statement has the most accurate Starting Date for employees. NOTE This issue is only evident in the first year that an employer transitions to Single Touch Payroll where the Commencement Date is only reported for new employees hired in the current Financial Year.

Functional Verification

1. Navigate to the STP Update Employee YTD at ATO function 2. Enter the required processing details. E.g. As At Paid Date = Today to update employee YTDs up to the current date 3. Submit process 4. Run the report to Review STP Update Employee YTDs 5. Confirm that the Commencement Date is included for ALL employees who have been paid in the relevant financial year.

Solution Implemented

The STP process for preparing UPDATE YTD event data has been enhanced to include the Commencement Date for all employees as specified by the selection criteria. E.g. such as Company, Pay Group, Id Number. The STP Data Analysers have been updated to identify the STP fields more clearly from job details. i.e. "Payee Commencement Date" and "Payee Cessation Date"

HRPC-2163 - STP - Lump Sum D not reported when only ETP in FY

Functional Issue

In STP, the Lump Sum D YTD amount is not being reported for employees who have only received ETP payments in the financial year. NOTE ATO only require the reporting of Lump Sum D in STP when an employee has had another type of payment in the same financial year.

Functional Verification

1. For a terminated Australian employee who has only received termination payments in financial year reported under STP. i.e. no regular or adhoc pays. 2. Ensure that the termination pay for the employee only contains Lump Sum D and ETP payments 3. Finalise the pay by reconciling and performing bank download 4. Navigate to Prepare STP Update YTD amounts 5. Select the terminated employee for STP reporting 6. Review the details via the STP report 7. Confirm that both the Lump Sum D and ETP payments are included in the STP report.

Solution Implemented

The STP Prepare process has been updated to ensure that Lump Sum D YTD amounts are reported when the employee has received any other payments in the same financial year. This includes only receiving payments for either ETP payments or reportable STP Allowances.

HRPC-2167 - STP EOFY/YTD Update where employee worked for 2 companies in the financial year

Functional Issue

The STP Prepare process for EOFY Finalisation (or Update YTD Amounts), will only find the latest Company that employed the selected employee Id Number - as at the supplied As At Paid Date. This becomes an issue if the payroll officer is attempting to correct or finalise the STP YTD amounts or other data for ALL companies that a single employee in the Financial Year (i.e. rather than an processing by an entire company or pay group). The workaround is to run a company wide STP EOFY Finalisation for the employee's earlier company(ies).

Functional Verification

1. Navigate to Prepare STP Update Employee YTD or EOFY Finalisation 2. Specify the As at Paid Date and the Id Number of one employee to process NOTE The employee selected has worked in more than one company within the financial year being finalised or corrected 3. Confirm that all the relevant companies which the employee has worked for in the (current) financial year are loaded into the Companies grid 4. Select all companies or a single company to process for the employee 5. Perform the processing 6. Prepare the report to Review the STP Update or EOFY details of the employee 7. Confirm that there is a separate STP submission prepared for each company that the employee has worked (and was selected for processing) 8. Navigate to the STP submit function 9. Confirm that the employee's Id Number is loaded and the company grid is visible and loaded with the companies selected (for the prepare STP details) 10. Sign and submit the employee's STP details 11. Confirm that all the STP Update (or EOFY FInalisation) events are submitted to the ATO. i.e. Submission Status is updated accordingly through the process stages. NOTE This can be reviewed in the STP data analysers or by running the Review STP report again.

Solution Implemented

The STP Update YTD Amounts and EOFY Finalisation functions have been updated to allow company selection when a single employee Id Number criteria has been specified. Multiple companies will only be loaded if the employee selected was paid by more than one payroll company within the financial year specified. NOTE The list of companies loaded only includes those that the selected employee was actively paid by during the financial year being processed (as determined by the As At Paid Date).

HRPC-2176 - STP - Lump Sum A type does not match payment when multiple terminations

Functional Issue

An incorrect Lump Sum A Type can be reported in STP for an employee who has had multiple termination pays in the Financial Year and the earlier termination included the Lump Sum A payment. The Lump Sum A Type value reported is based on the details of the latest Termination Activity, rather than the Termination Activity associated with the pay that included the Lump Sum A payment.

Functional Verification

1. Terminate an employee using Genuine Redundancy as the termination type in the termination activity details 2. Calculate the termination pay and confirm that a Lump Sum A payment is included 3. Finalise the pay and run the STP Prepare Pay Details 4. Confirm that the YTD Lump Sum A amount and Lump Sum A Type of 'R' is reported 5. Re-hire the employee in the same financial year 6. Calculate and finalise their first pay 7. Run the STP Prepare Pay Details 8. Confirm that the YTD Lump Sum A amount and Lump Sum A Type of 'R' is still reported for the FY 9. Terminate the employee again. NOTE The termination activity details will no longer be a Genuine Redundancy. E.g. resignation 10. Calculate the second termination pay and confirm that there is no Lump Sum A payment made 11. Finalise the pay and run the STP Prepare Pay Details 12. Confirm that the YTD Lump Sum A amount and Lump Sum A Type of 'R' is still reported. i.e. as per the first termination pay and activity details. NOTE As per ATO specifications: If an employee has multiple Lump Sum A types within the one Financial Year, then the latest Lump Sum Type is reported.

Solution Implemented

The STP Prepare process has been corrected to retrieve the Lump Sum A Type from the termination activity associated to the pay containing the Lump Sum A payment.

HRPC-2182 - Rerunning TFN eFile failing

Functional Issue

Attempting to reproduce the TFND eFile will result in an authorisation error. This occurs even though the user has the correct authorisation to reprocess TFN declarations. This occurs if an employee only has effective Tax records that are all marked as Transmitted to the ATO. i.e. no outstanding TFNDs to transmit.

Functional Verification

1. Navigate to User Authorisation Maintenance > HR&Payroll > Electronic Reporting, and ensure the user has authorisation to reprocess TFN declarations 2. Navigate to the Electronic TFN Declaration function 3. Ensure Production Run is ticked and Report Date loads the employee TFNDs that need to be included 4. Process TFN declaration 5. Confirm that Transmitted to ATO for the employee is ticked and the TFND eFile is generated 6. Attempt to reproduce the TFND file by repeating Steps 2-5 7. Ensure the same employee TFNDs that now have transmitted values are selected for the reproduced TFND file 8. Confirm that there is no authorisation error message and the TFND eFile is generated successfully NOTE A warning message will be returned if an employee's tax record fails to be updated with new ATO Transmitted details.

Solution Implemented

The TFND process has been corrected to allow re-processing of transmitted TFND records when the user has authorisation to do so.

HRPC-2189 - NZ IRD KED (KS1) process errors for employees on Contributions Holiday

Functional Issue

The IRD KED process fails for employees on a Contributions Holiday (i.e. specified in KiwiSaver Enrolment type)

Functional Verification

1. For an NZ employee who is 'Eligible For Kiwisaver' and is going on a 'Contributions Holiday' (set in Enrolment Type) 2. Ensure the employee address details are provided 3. Ensure that the 'Kiwisaver Opt Out' is NOT selected. i.e. employee remains as an active member 4. Navigate to KiwiSaver Employment Detail (KS1) process function 5. Select the criteria to include the employee with updated KiwiSaver details 6. Confirm that the KS1 is successfully produced. i.e. there is no error returned for the employee on contributions holiday (E.g. Employee xxx has Kiwisaver eligibility indicator 'CH' which is invalid).

Solution Implemented

NZ IRD KED (KS1) Process has been corrected to support the enrolment type for Contributions Holiday. Additional error messaging has been included to indicate missing employee address details related to the KiwiSaver options selected.

HRPC-2273 - Manual Back Pay does not correctly apply rate increases to pays that include leave adjustments

Functional Issue

Manual back pay does not apply percentage increase to the first pay span pay components of leave adjustments for pays that include mid period change that involves a position code change in conjunction with leave adjustment scenarios.

Functional Verification

1. Ensure the "Entitlement Reduction" default control variable is set to MODIFY. 2. Configure a monthly employee to be paid on the last day of the month with base pay entitlements of 150 hours. 3. Configure the employee with leave accruals. 4. Create another job effective in the middle of May with a position code that is different from the one used in step 2 above. 5. Generate and approve leave for the entire month. 6. Calculate the pay for the month of May. 7. Review the pay and confirm that negative leave adjustments were made. 8. Generate a Manual Back pay that covers the May pay period from step 6 and applies a percentage increase to Base Pay and Leave Taken pay items. 9. Review the Back Pay and confirm the adjustment base pay items from both pay spans in the pay from step 6 have been reversed and then regenerated correctly with the percentage increase.

Solution Implemented

Manual Back Pay now correctly applies increases to pays that include leave adjustments

HRPC-2331 - No Superannuation when ordinary hours are not worked on primary position

Functional Issue

SGC or other mandatory super contributions are not calculated for an employee who has only worked hours in a Secondary position and the Control Variable for Allow Split Costing = No.

Functional Verification

1. For sites that have the Control Variable for Superannuation > Allow Split Costing set to No 2. For a Timesheet Only employee who occupies a Secondary position and has Superannuation details including SGC contributions 3. Complete a timesheet with only hours worked for the Secondary position. i.e. no Primary position hours worked for the period 4. Calculate the pay period that loads this timesheet (and no other entitlements) 5. Confirm that the pay includes the mandatory superannuation contribution pay item(s). e.g. SGC

Solution Implemented

The pay calculation logic for superannuation has been modified to ensure that when Super Cost Splitting is not required (control variable is set to No), the OTE of all an employee's active positions contributes to the mandatory superannuation contributions.

HRPC-2343 - Australian Termination recalculation removes the leave paid out on termination

Functional Issue

A recalculation of Australian Termination pay removes the paid out Leave from the initial calculation.

Functional Verification

1. As Payroll Officer navigate to Process Termination Pay for Employee 2. For an Australian employee expecting leave to be paid out on termination. E.g. Annual leave owing 3. Calculate the termination pay 4. Confirm leave is paid out on termination as expected 5. Make a manual adjustment to the pay. e.g. additional Base Pay 6. Recalculate the termination pay 7. Confirm termination leave is still paid out correctly.

Solution Implemented

Previous changes made under HRPC-1049 which ensure all pay item Calculation Dates are kept consistent when a pay is saved or recalculated, have been reversed.

RELEASE May 2019

HRPC-608 - Pay by Group - Timesheet only employes with no current timesheet do not have previous timesheets loaded

HRPC-678 - Automate management of ATO cents per kilometre reimbursement threshold

HRPC-855 - SBR PAYG submission failing - Invalid Item Value for UK PostCode

HRPC-905 - New HRP Diagnostics for STP Pay Event transmissions

HRPC-1147 - Security required on find pays in Adjust Payroll

HRPC-1307 - Single Touch Payroll - Company Trading Name length increase to 200 char

HRPC-1332 - Electronic TFN Declaration - eFile only stamps latest Employee Tax record as Transmitted to ATO

HRPC-1363 - Payroll Liability process creating Payroll document types

HRPC-1438 - Australian Working Holiday Makers scale change effective 01/07/2018

HRPC-1650 - Single Touch Payroll - New field RAN for Registered Agent Intermediaries (Taxation Supplier)

HRPC-1734 - Super not calculating when job details fall between PPE & Paid date

HRPC-1747 - NZ Payday - new function for Prepare Payday Upload File for IRD

HRPC-1795 - Single Touch Payroll - packaging changes for Legislative Reporting

HRPC-1808 - PNG - 2019 Tax Rate threshold changes to personal income

HRPC-1824 - ATO STP Validation Response process fails with XML Whitespace Exception

HRPC-1825 - User's Default Queue not flowing through to STP Submit function

HRPC-1832 - New Zealand Legislative Changes effective 01/04/2019 - Tax rate and calculation changes

HRPC-1855 - ATO TFN Declaration electronic reporting version 4.0.0 effective 1 July 2019

HRPC-1861 - STP Allowances - Total STP YTD Submission positive for ALLW_MEAL, but individual PCC's defaulting to zero if Negative

HRPC-1877 - NZ PayDay - new KiwiSaver status 'Contributions holiday' and minor issues in New and Departing Employees Report (Employee Details report)

HRPC-1899 - STP Report Changes for People data analyser usage

HRPC-1915 - Payroll reports will not run in CiA - standard code selection error

HRPC-1917 - NZ PayDay - Prepare function UI minor issues

HRPC-1918 - NZ PayDay - Pay Master auditing 'last_mod' fields not updated

HRPC-1922 - Single Touch Payroll - Updated ATO validation on Allowance Description for 'Other Allowance' types

HRPC-1952 - $AU ATO legislative changes effective 01/07/2019

HRPC-1955 - EDF IR 345 text file no longer supported by myIR

HRPC-1961 - STP - SBR2Utils does not use the correct SQL.Node for updating Last_mod_term field

HRPC-1995 - Back pay fail to bank download due to change of Pay Group

HRPC-1997 - The payroll calculation can overpay monthly employees entitlement due to leave taken for the entire pay period.

HRPC-2021 - STP error on country code 1101

HRPC-608 - Pay by Group - Timesheet only employes with no current timesheet do not have previous timesheets loaded

Functional Issue

'Timesheet Only' employees with only prior outstanding timesheets are not included in the pay calculation when the option 'Exclude Employees With No Timesheets' option is selected. i.e. there is no current timesheet for the pay period.

Functional Verification

1. Navigate to Calculate Payroll by Group 2. Select the pay period to calculate 3. Ensure that this pay period has a Timesheet Only employee who has no timesheet entries for the current pay period, however, does have prior outstanding timesheets that should be paid. E.g. the employee has retrospective leave entries in earlier periods that now require payment 4. Ensure the processing option is checked to 'Exclude Employees with No Timesheets' 5. Calculate Payroll 6. Confirm that the employee with only prior timesheets has the current pay calculated.

Solution Implemented

The payroll calculation process has been corrected to ensure casual employees with only prior timesheets are included in the pay calculation. e.g. Timesheet Only employees with retrospective leave or worked hours to be paid, but have not current timesheet period entries (time worked).

HRPC-678 - Automate management of ATO cents per kilometre reimbursement threshold

Functional Issue

The pay calculation was not able to automatically check and apply the ATO reimbursement kilometres and rate thresholds for allowance items relating to cents per kilometre reimbursements.

Functional Verification

Other Scales: 1. Log into the Payroll Officer workplace 2. Select the Manage Payroll tab and expand the Other Scales section within Payroll Management 3. Expand the $AU - Australia region section of the other scales 4. Confirm the $AU region includes the scale type 'AU_CPKR - Cents per Kilometre Reimbursement' 5. Expand the AU_CPKR scale type and confirm the scale has details effective 01/07/2018 6. Confirm the scale details are column (X) - maximum value, column (A) - 5,000.0000, and column (B) - 0.6800 7. Column (A) represents the annual tax free kilometres threshold and column (B) represents the ATO approved reimbursement rate. NOTE To enable the automatic assessment and processing of the ATO cents per kilometre reimbursement thresholds, the following pay components must be defined: 1. A Tax Free allowance type pay component with the Kilometers pay period unit and the system configuration codes 'ALLW_CAR' and 'TAX_ALLW' selected. 2. A Taxable allowance type pay component with the Kilometers pay period unit and the system configuration codes 'ALLW_CAR' and 'TAX_ALLW' selected. n.b. This applies to amounts over the 5000 km per annum allowance at 68 cents per km OR amounts on rates paid over the 68 cents per km but still under the 5000 km threshold. 3. A Taxable allowance type pay component with the Kilometers pay period unit and the system configuration codes 'ALLW_OTHER' and 'TAX_ALLW' selected. n.b. This only applies to amounts that exceed both the 68 cent per km allowance rate and over the 5000 km threshold. Pay Calculation: 1. Load the current ordinary pay for an employee 2. Manually enter a pay item for the tax free travel allowance pay component created above, use the current approved reimbursement rate 3. Calculate the pay with entitlements and timesheets loaded 4. Review the calculation audit 5. Confirm the calculation audit includes a section for the assessment and applying cents per kilometres reimbursement tax free limits 6. Confirm the process retrieves the current AU_CPKR scale details correctly 7. Confirm the process retrieves the paid tax free car allowances within the current financial year correctly 8. Confirm the process sums the total tax free car allowances correctly, including item(s) within the current pay 9. Confirm when the total tax free kilometres are within the yearly limit and the rate is within the approved ATO rate (68 cents), the allowance pay item entered remains in the pay unchanged. i.e. a Tax free CAR allowance 10. When the total tax free kilometres exceed the yearly limit, the amount for excess kilometres is transferred to the Taxable CAR allowance pay component created. NOTE First found pcc defined for the company is used. 11. When the approved reimbursement rate (68 cents) is exceeded for km UNDER the 5000km threshold, the excess amount of the rate is transferred to the Taxable CAR allowance pay component created. NOTE First found pcc defined for the company is used. 12. When the approved reimbursement rate (68 cents) is exceeded for km OVER the 5000km threshold, the excess amount of the rate is transferred to the Taxable OTHER allowance pay component created. NOTE First found pcc defined for the company is used.

Solution Implemented

Payroll Processing has been enhanced to support automatic management of the ATO cents per kilometre reimbursement thresholds. These thresholds are date-effective and are contained in a new Australian Other Tax Scales - AU_CPKR tax scale type. IMPORTANT NOTE To enable the automatic assessment and processing of the ATO cents per kilometre reimbursement thresholds, the following pay components must be defined: 1. A Tax Free allowance type pay component with the Kilometers pay period unit and the system configuration codes 'ALLW_CAR' and 'TAX_ALLW' selected. 2. A Taxable allowance type pay component with the Kilometers pay period unit and the system configuration codes 'ALLW_CAR' and 'TAX_ALLW' selected. n.b. This applies to amounts over the 5000 km per annum allowance at 68 cents per km OR amounts on rates paid over the 68 cents per km but still under the 5000 km threshold. 3. A Taxable allowance type pay component with the Kilometers pay period unit and the system configuration codes 'ALLW_OTHER' and 'TAX_ALLW' selected. n.b. This only applies to amounts that exceed both the 68 cent per km allowance rate and over the 5000 km threshold.

HRPC-855 - SBR PAYG submission failing - Invalid Item Value for UK PostCode

Functional Issue

PAYG payment summaries and Tax File Number declarations submitted to ATO via SBR are failing for overseas addresses.

Functional Verification

1. For an Australian company employee whose current street address contains an overseas address, produce their PAYG Payment Summary 2. Navigate to the Adjust PAYG Payment Summary function 3. Load the current financial year's PAYG Payment Summary for the employee 4. To transmit the Payment Summary to the ATO, navigate to the PAYG Payment Summaries function 5. Select the SBR Report option 6. Enter the required fields to select the employee above 7. Select Start processing 8. When the process is complete confirm the process has displayed a SBR Message Accepted (CMN.ATO.GEN.OK) message.

Solution Implemented

Updated the SBR Payment Summary process as per ATO overseas address guidelines. i.e. Payee overseas address fields for State and Postcode are concatenated and loaded into the field 'Line 3' of the SBR address. SBR fields for State and Postcode are only loaded for Australian addresses.

HRPC-905 - New HRP Diagnostics for STP Pay Event transmissions

Functional Issue

The system does not have a diagnostic export data stored script procedure for Australian single touch payroll (STP).

Functional Verification

1. Log into the system and select the System Administrator - All workplace. 2. Select the System workplace tab and expand the Stored Script Procedures - Scripts section of the Explore tree. 3. Locate the script name '$HRPAY_DIAG_STP' and retrieve the script. 4. Confirm the script is retrieved without errors and select Check Syntax to ensure the current user has the correct user authorisations. 5. Confirm the check syntax completes without any errors being displayed in the Results section. 6. Select Start Processing and enter the pay period end date to retrieve diagnostic data for and the Id number of the employee if the submission enquiry is for a single employee only. 7. When the script has finished processing review the results and confirm the script completed successfully and the results narrate details of the diagnostic files created. 8. Open My Report and Files and download the diagnostic zip file created. 9. Confirm the diagnostic zip file contains diagnostic files for the STP submission(s) for the pay period entered.

Solution Implemented

Created a diagnostic single touch payroll stored script procedure to assist support to analyse STP related cases.

HRPC-1147 - Security required on find pays in Adjust Payroll

Functional Issue

Pay Master picklist HRPAY412 'Find Pays' accessed from 'Adjust Payroll' to support employee pay searching, does not apply the user's security category access.

Functional Verification

1. As Payroll Officer with limited security access, navigate to the Adjust Payroll. E.g. Payroll Officer can only access employees of one Company Code 2. Leave Id Number blank and click 'Find Pays' 3. In the Pay Master picklist, click Retrieve 4. Confirm that the list of employees and their Pay Masters is limited to the user's security access of one company.

Solution Implemented

Security Category access has been added to the retrieval for the 'Pay Master' picklist HRPAY412 accessed in the 'Adjust Payroll' function - 'Find Pays'.

HRPC-1307 - Single Touch Payroll - Company Trading Name length increase to 200 char

Functional Issue

Single Touch Payroll reporting to ATO supports 200 characters for a company's Organisation Name. Currently all name fields of the Company entity are limited to 50 characters. The Trading Name of companies will be increased to support the ATO's Organisation Name in STP events, as well as for those employers whose company name exceeds 50 characters. NOTE Company Name 1 and 2 will remain at 50 characters maximum.

Functional Verification

1. Navigate to Company Maintenance and load an existing company 2. Update the Trading Name with a string that exceeds 50 characters length 3. Save 4. Navigate to Adjust Pay function and load the pay of an employee who works for the company 5. Generate the Pay Advice for the employee pay NOTE The change for this enhancement is contained in the shipped pay advices. Any custom pay advice will need to be modified accordingly to see the enhancement. 6. Confirm that the Trading Name appears on the employee's Pay Advice NOTE If Trading Name value is left blank for a Company, the the values of Company Name 1 and 2 will be concatenated and displayed in the shipped Pay Advice. The Trading Name is limited to one line in the Pay Advice, so may be truncated if it exceeds this length. E.g. over 110 characters. If this is not desirable, then a custom pay advice can be used to display Trading Name as required. 7. Prepare the STP Pay event for the employee's pay. 8. Confirm that the full Trading Name is loaded for the Company. i.e. via report for Review STP Pay Event or data analyser for STP Pay Event.

Solution Implemented

The length of the Company field for Trading Name has been increased to 200 characters. All shipped Pay Advices now display the Trading Name by default, unless this field is left blank. Company Names 1 and 2 are concatenated and displayed where the Trading Name is blank. i.e. as per existing functionality in PAYG Payment Summary NOTE For the full functionality related to this enhancement ensure the latest packages for both Payroll Processing and HRP Core are installed.

HRPC-1332 - Electronic TFN Declaration - eFile only stamps latest Employee Tax record as Transmitted to ATO

Functional Issue

The TFN Declaration eFile process does not update all Effective Tax records of an employee as transmitted to ATO. This causes the employee to be included in every subsequent eFile TFN declaration submission. NOTE The SBR TFN Declaration submission does not have this issue.

Functional Verification

1. Create or find an Australian employee who has more than one Effective tax record requiring transmission to the ATO 2. Navigate to the Electronic Reporting for TFN Declaration 3. Ensure the eFile option is selected and the employee is included in the outstanding TFN employee declarations grid 4. Prepare the TFND eFile 5. From Employee Maintenance, confirm that all of the employee's Effective Tax records are signed as transmitted to the ATO. i.e. as dated on or before the TFN reporting date selected. 6. Confirm that the employee is excluded from subsequent TFN Declaration submissions.

Solution Implemented

The TFN Declaration eFile process has been corrected to update all Effective Tax records of employees that are dated prior to the processing date.

HRPC-1363 - Payroll Liability process creating Payroll document types

Functional Issue

The Payroll Liability can create negative Payroll master records for casual employees who have not entered timesheets for the period. i.e. on Timesheet Only

Functional Verification

1. For a Casual employee (Employee Type Casual on Timesheet Only pay) 2. Ensure the employee's entitlement has a Deduction or extra Tax pay component (which can result in negative pays if no timesheet entries are loaded for the pay period) 3. For the Payroll Liability period, ensure the employee has no calculated pays or timesheet entries 4. Navigate to Payroll Liability and calculate the employee's payroll liability 5. Navigate to Adjust Payroll and use Find Pays to find for all pay master records created for the employee (i.e. clear the document type criteria) 6. Confirm that a Payroll document pay master has not been created as a result of the payroll liability processing above.

Solution Implemented

The payroll liability process has been corrected to ensure that negative pay masters are not committed for casual employees that do not have timesheet entries for the liability period (i.e. no pay).

HRPC-1438 - Australian Working Holiday Makers scale change effective 01/07/2018

Functional Issue

The ATO has changed one of the scale brackets' earnings range for the working holiday maker scale effective 1 July 2018.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Working Holiday Maker income thresholds (Other Tax Scales -> $AU - Australia -> AU_WHM - Working Holiday Makers): 4. Confirm that the Working Holiday Makers income thresholds are available for the 1 July 2018. 5. Confirm that the Working Holiday Makers income threshold details are correct per the ATO Schedule 15 - Tax table for working holiday makers. i.e. 32.5% threshold set to $90,000 (previously $87,000). On exceeding $90,000 taxable earnings for the financial year, the WHM employee will be taxed at 37%.

Solution Implemented

The system has been updated to the correct values for working holiday makers scale effective 1 July 2018.

HRPC-1650 - Single Touch Payroll - New field RAN for Registered Agent Intermediaries (Taxation Supplier)

Functional Issue

In Single Touch Payroll, if a user declares that they are acting as a 'Registered Agent', then they must provide their RAN (Registered Agent Number) in addition to ABN for STP submissions.

Functional Verification

1. Navigate to Taxation Supplier maintenance 2. Select the Australian Taxation Supplier to be used for the Registered Agent of STP submissions 3. Complete the Registered Agent Number (RAN) as per the registration with the tax authority NOTE The Registered Agent ABN is also required for STP 4. Navigate to 'Calculate Pay by Group' or Adjust Pay 5. For a finalised pay run (i.e. has a Paid Date), select 'Transmit STP Pay Details for ATO' 6. Review the STP Pay Details report, confirming that the 'Intermediary RAN' field value is loaded correctly for the Taxation Supplier of the registered agent selected NOTE An error will be returned if a declared Registered Agent has not specified a RAN on the Taxation Supplier entity. 7. Once prepared successfully, submit the STP event after selecting the Registered Agent option and Taxation Supplier 8. Confirm that the STP Pay event is submitted successfully to the ATO. i.e. proceeds through to the submission status of 'Awaiting Response' and finally 'Success'.

Solution Implemented

Taxation Supplier has a new 'Registered Agent Number" field (RAN) for Australian suppliers acting as Registered Agents submitting STP pay details on behalf of their serviced payroll employers. The STP process and reports have been updated to include the new RAN field when the user specifies they are acting as a Registered Agent. NOTE For the full functionality of this enhancement, both the latest Ci packages for Payroll Processing and HRP Core must be installed.

HRPC-1734 - Super not calculating when job details fall between PPE & Paid date

Functional Issue

When an employee has multiple Jobs which are effective between the Pay Period End Date (PPED) and Expected Paid Date (EPD), there are no Superannuation items in the pay. Also, during the Superannuation calculation process the retrieval of the employee Job details effective for the pay period was being done as at the pay's Expected Paid Date rather than the Pay Period End Date.

Functional Verification

The initial issue of the superannuation not calculating with job details effective mid pay period was resolved via the issue HRPC-807 included in a previous Payroll Processing Ci package release. Verification of the correct processing of the employee superannuation details effective mid pay period: 1. Create a new employee whose job details are for an Australian company. 2. Do not include superannuation within the employee maintenance superannuation section. 3. Calculate an ordinary pay for the current pay period. 4. Assign employee superannuation details to the employee effective as at the following pay period end date. 5. Load the adjust pay function for the pay period the superannuation if effective. 6. Set the expected paid date to a day after the pay period end date. 7. Calculate the pay. 8. Confirm the pay has generated employee/SGC/company superannuation items per the superannuation fund configuration. NOTE: Employee superannuation details that are effective mid pay period are generated for the whole pay period. The pay calculation does not ratio superannuation effective mid pay period.

Solution Implemented

The Australian superannuation and tax calculations have been changed to ensure employee job details are always retrieved as at the pay period end date. i.e. consistent with all other pay processes that require job retrieval.

HRPC-1747 - NZ Payday - new function for Prepare Payday Upload File for IRD

Functional Issue

NZ IRD legislation for Payday reporting of Employment Information (EI) becomes mandatory from 1 April 2019 for employers. A new function is required to produce the csv file that is uploaded to the NZ MyIR website by the employer within 2 working days after each payday. Refer to NZ IRD website for more information on Payday reporting via the Upload EI File.

Functional Verification

The new 'Prepare Payday Upload File for IRD' function loads the specified Payday Pay Period details into the IRD payday filing EI upload file (Employment Information). This file is CSV format and very similar to the current EMS IR348 upload file. 1. As Payroll Officer, navigate to a pay calculation function. i.e. Adjust Pay for employee or Calculate Payroll by Group 2. Once the employee is Paid, confirm that the action link to 'Preparing Payday Upload File for IRD' is visible 3. Select the 'Prepare Payday Upload File for IRD' link 4. Confirm that the main criteria of the calculated pay is loaded. i.e. Pay Period End Date, Company, Document Type, Pay Group, Id Number(s) selected for pay calculation NOTE - Only selected employees will be loaded into 'Prepare Payday Upload File' and available for inclusion in the payday file. - If no employees are selected from the Pay Calculation function, then the default for Payday processing will be to include ALL employees in the pay period that are Paid. 5. Submit processing 6. On completion of the job, review the log for errors and warnings 7. Review the generated csv payday file for correctness. By default this file is saved with the default naming format of 'Payday_<CompanyCode>_<PPED>.csv'. E.g. 'Payday_1_15Apr2019.csv'. 8. Confirm that the employee pay masters are updated to reflect the Submission Status (SUCCESS) and Submission ID (payday file name). The Submission Status is visible in the Pay calculation functions as well as the Pay Transactions data analyser. 9. Confirm that the selected employees are included unless excluded due to errors or warnings. 10. Confirm details and amounts are correct for the Pay Period and criteria specified. NOTE - Do NOT open the csv file in MS Excel and re-save, as this may adjust the file formatting required by the IRD. E.g. date formats, IRD '00000000' - If multiple Paid Dates are detected in the one Pay Period, the Paid Date will be appended to the file name. E.g. Payday_1_15Apr2018_PD19Apr2018.csv' and 'Payday_1_15Apr2018_PD20Apr2018.csv' - Amounts are for the pay period only (not YTD or calendar month as per the EMS). - The IRD do NOT accept negative amounts in Payday reporting. Any employee who has any negative amounts for the pay period will be excluded from the Payday report. A warning message is returned and the employee's Submission Status will be set to FAIL. - Function parameters are available to default Taxation Supplier and Destination Folder values into 'Prepare Payday Upload File for IRD'. - This function includes a function link to the report for 'New and Departing Employees' which is defaulted to the shipped function definition. This can be customised and overridden if required.

Solution Implemented

A new function has been shipped for 'NZ Prepare Payday Upload File for IRD'. A new link has been added to Pay calculation functions to navigate to the new Prepare Payday function. This produces a csv file that is then uploaded manually by the employer via their MyIR logon. NOTE 1. The Payday Upload File (aka Employment Information (EI) return) will: - Replace the employer monthly schedule (IR 348/EMS) for payday filers, - Hold employment income information from employers filing on a payday basis. i.e. it must incorporate all payments made to employees (and/or contractors), and ESCT deducted per employee line - Include new information, such as dates of employer’s payday 2. Multiple Payday files can be generated by a single prepare process if multiple Paid Date are detected in the Pay Period selected. i.e. one file per Company and Paid Date 3. The Prepare Payday Upload File process can be re-run. All selected employee pays as per the selected criteria will be included at each run. 4. A 'NIL Return' for Payday is accepted by the IRD. A NIL return payday file only has a Header row and no Detail employee rows. This is the case if there are no employees paid for the specified Pay Period criteria. This may be an unlikely scenario. 5. PAYE Intermediaries are not currently supported in the product for either EMS or Payday reporting. 6. Corrections for Payday Reporting The amounts reported to the NZ IRD are pay period amounts (not YTD) and cannot be negative. As such the payroll officer can only correct previously reported amounts by: - Producing a Payday upload file for off-cycle pays that have positive amounts paid (e.g. Correction, Bonus, Special). This file is manually uploaded to the IRD via the MyIR website as a separate payday file; or - Including the correction adjustments in the next regular pay period amounts (and manually uploading this payday file to the IRD). The payroll officer does this by selecting the option to “Include Correction Pays” for the relevant Paid Date(s); or - Logging onto their myIR website and performing a manual payday amendment for the previous reporting pay period and employee(s). This adjusts the amounts of the payday file that was previously uploaded/reported to the IRD. Thereby correcting the pay period details directly at the IRD. NOTE: This is particularly important to report correctly for calendar months. i.e. a retrospective correction cannot be included in the next regular pay period if it corrects the amounts that were reported in a previous calendar month.

HRPC-1795 - Single Touch Payroll - packaging changes for Legislative Reporting

Functional Issue

The Payroll Officer workplace requires better navigation options to STP functions and other Legislative based functions.

Functional Verification

1. As System Administrator, ensure that any previous custom changes for STP functions, reports and data analysers are deleted. 2. As Payroll Officer 3. Navigate to the new tab for 'Legislative Reporting' 4. Confirm that menus on this tab include: a. ATO Electronic Reporting b. ATO Single Touch Payroll c. NZ IRD Reporting d. HRP Diagnostics 5. Confirm that each link in the menus navigates successfully to the described function 6. Navigate to the existing 'More' tab 7. Confirm that the menu lists for legislative reporting are no longer listed. NOTE HRP Diagnostics is still available on the More tab. 8. Navigate to the STP Update YTD or STP EOFY function 9. Confirm that a new link is provided to the STP Reconciliation Report. This report can be used to compare Pay Master YTD amounts with those classified for the ATO STP events.

Solution Implemented

Shipped Payroll Officer workplace has been enhanced with a new Legislative Reporting tab, including Single Touch Payroll functions.

HRPC-1808 - PNG - 2019 Tax Rate threshold changes to personal income

Functional Issue

The Papua New Guinea Tax Scales are to be updated effective from 1 January 2019.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Normal Tax Scales (Tax Scales -> $PG - Papua New Guinea). 4. Confirm that Tax Scales R - Resident, NR - Non Resident and ND - No Notification are available for the 1 January 2019.

Solution Implemented

Added new Papua New Guinea Tax Scale co-efficients effective from 1 January 2019.

HRPC-1824 - ATO STP Validation Response process fails with XML Whitespace Exception

Functional Issue

The ATO have changed the format of some STP validation response messages, the change was causing an application error while processing the message. The submission status is set to Full Failure in this instance. The submission response message creating the issue is ATO error code 'SBR.GEN.AUTH.006'.

Functional Verification

For customer sites that have received ATO errors due to incorrectly configured STP product registration on the ATO Access Manager: 1. Review the recent 'STP ATO Validation Respone001.log' files within the $PAYLOG server folder. 2. Locate a submission with an application error relating to XML whitespace while processing the ATO validation response message SBR.GEN.AUTH.006, if applicable to your system. NOTE: This message relates to sites who have not configured their ATO Access Manager correctly. 3. Prepare another STP submission and transmit the submission to the ATO. 4. Once the ATO validation response has been returned review the latest 'STP ATO Validation Respone001.log' file within the $PAYLOG server folder. 5. Confirm the validation response has been processed successfully without the application error being shown within the log. 6. Review the STP messages drag and analyse for the submission and confirm the ATO SBR.GEN.AUTH.006 response message has been stored, which advises the 'The software provider has not been nominated to secure your online (cloud) transmissions.' 7. Review the submission status and confirm the status is set as Full Failure. 8. Correct the STP configuration via the ATO Access Manager. Refer to Knowledge Base Community articles on STP. 9. Prepare, transmit another submission and confirm the transmissions are completing successfully when the ATO validation response has returned.

Solution Implemented

Changed the ATO STP validation response process to correctly handle the current ATO xml messages.

HRPC-1825 - User's Default Queue not flowing through to STP Submit function

Functional Issue

A DP Queue selected or customised for the function 'Calculate Payroll by Group' is not defaulted into the STP linked functions - 'Prepare STP Pay Details for ATO' and 'Submit STP Pay Details to ATO'.

Functional Verification

For users that have specified an overriding DP Queue in the payroll calculation function 'Calculate Payroll by Group'. i.e. to customise the default DP Queue that payroll processes are executed on: 1. Navigate to 'Calculate Payroll by Group' 2. For a finalised pay run (i.e. has a Paid Date), select 'Transmit STP Pay Details for ATO' 3. Confirm that the default DP Queue specified in the function 'Calculate Pay by Group' is also loaded into the DP Queue of 'Prepare STP' 4. Navigate to 'Submit STP Pay Details to ATO' 5. Confirm that the default DP Queue specified in the function 'Calculate Pay by Group' is also loaded into the DP Queue of 'Submit STP' For users that want to specify a custom 'STP Prepare Pay Details for ATO' function. E.g. to include a custom DP Queue for the process: 1. Maintain or create custom function definitions for the payroll calculation functions. E.g. 'Calculate Pay by Group' or 'Adjust Payroll' 2. Specify the new parameter for a custom 'STP Prepare' function name 3. Save the custom function definition. 4. Navigate to 'Calculate Pay by Group' or 'Adjust Payroll' 5. For a finalised pay run (i.e. has a Paid Date), select 'Transmit STP Pay Details for ATO' 6. Confirm that the 'Prepare STP Pay Details for ATO' process has the overriding DP options and Queue as per the custom function linked 7. Navigate to 'Submit STP Pay Details to ATO' 8. Confirm that the same custom DP Queue is also loaded into the DP Queue of 'Submit STP' NOTE Manually overriding the DP Queue name in 'Calculate Payroll by Group' will pass this value to the linked STP functions - 'Prepare STP Pay Details for ATO' and 'Submit STP Pay Details to ATO'.

Solution Implemented

1. The Payroll calculation functions have been updated to ensure that custom or selected DP Queues are passed from the payroll calculation function through to their linked STP functions - Prepare and Submit STP Pay Details. 2. A new function parameter for the 'Default STP Prepare Function' has been added to the payroll calculation functions. i.e. HRPAY710 Adjust Payroll, HRPAY410 Calculate by Group and HRPAY510 Manual Back Pay. This allows users to customise the settings of the function 'Prepare STP Pay Details' and have this function initiated from the function links in custom payroll calculation functions.

HRPC-1832 - New Zealand Legislative Changes effective 01/04/2019 - Tax rate and calculation changes

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2018: 1. The ACC earners levy scales have been updated as at 1 April 2019. 2. The Student Loan repayment threshold has been amended as at 1 April 2019. 3. Inland Revenue have advised that the four weekly gross up earnings for lump sum payments: "Do not include any other amounts of extra pay that may have been made in that 4 week period."

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2019 and are for the correct percentage and maximum levy. The Earners Levy percentage for 1 April 2019 is 1.39% for annual income less than $128,470 and the maximum levy is $1,785.73. 2. Calculate an ordinary pay after the 1st April 2019 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Student Loan Changes: 1. Verify the Student Loan scales (NZ_SL) exist for 1 April 2019 and are for the correct percentage and maximum levy. The Student Loan percentage for 1 April 2019 is 12.0% (A) for annual income greater than $19,760 (X). 2. Calculate an ordinary pay after the 1st April 2019 for an employee with tax code M SL. 3. Review the calculation audit. 4. Confirm the new Student Loan repayment threshold was used for the tax calculation. Lump Sum PAYE four weekly gross up calculation change: 1. Load the current ordinary pay period for an employee. 2. Manually enter a lump sum pay item to the pay period. Note: The lump sum item pay component must have the 'LUMP_SUM' New Zealand region configuration code selected to calculate the PAYE as a lump sum. 3. Calculate the pay period with entitlements and timesheets loaded. 4. Review the pay's calculation audit tax calculation section. 5. Confirm the lump sum PAYE four weekly gross up earnings include the ordinary earnings for the four week period correctly. 6. Load the following pay period for the employee. 7. Manually enter another lump sum pay item for the pay period. 8. Calculate the pay period with entitlements and timesheets loaded. 9. Review the pay's calculation audit tax calculation section. 10. Confirm the lump sum PAYE four weekly gross up earnings include the ordinary earnings for the four week period but does NOT include the lump sum payment included within the previous pay calculated in step 3 above.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2019: 1. The ACC Earners Levy tax scales have been updated and apply to pay on or after 1 April 2019. 2. The Student Loan tax scales have been updated and apply to pay on or after 1 April 2019. 3. The lump sum PAYE four weekly gross up calculation has been changed.

HRPC-1855 - ATO TFN Declaration electronic reporting version 4.0.0 effective 1 July 2019

Functional Issue

ATO TFN Declaration for electronic reporting (Portal file upload) has been updated to version 4.0.0.

Functional Verification

1. Run Electronic TFN Declarations choosing e-File transmission for the current reporting period 2. Review the file's version number reported in the supplier line 3. Confirm the version is 'FTFNDV04.0' 4. Payee email address field has been added to the Payee declaration details This field is at position 300-375, replacing the 'Financial Supplement Scheme Indicator' field. The employee email address loaded follows the same usage as ATO Single Touch Payroll. i.e. the first non-blank employee email address from the employee's Residential / Street address is included in the TFN Declaration.

Solution Implemented

Updated ATO TFN Declaration for eFile submissions to TFND Version 4.0.0 This version includes loading employee email addresses, to be aligned with Single Touch Payroll transmitted fields. NOTE The email address of employees is not mandatory and can be left blank. If employees do not wish to transmit their email address to the ATO then leave the first/primary Email address field in Street Address details blank.

HRPC-1861 - STP Allowances - Total STP YTD Submission positive for ALLW_MEAL, but individual PCC's defaulting to zero if Negative

Functional Issue

For STP, negative allowance amounts on YTD should only be rejected if this occurs on the total of each reported Allowance Type (e.g. 'ALLW_MEAL'). Currently negatives are being excluded due to processing at the Pay Component Code level. This results in incorrect allowance amounts reported in STP (per each allowance classification/type).

Functional Verification

1. For an Australian company employee receiving allowances 2. For the scenario where there are two different Pay Component Codes (PCC) with the same allowance config code (e.g. ALLW_MEAL) 3. For the employee's current pay being calculated 4. Add one allowance pcc from above with a negative amount. e.g. -$10 5. Add the second allowance pcc of the same category (ALLW_MEAL) with a positive amount that exceeds the negative. e.g. $50 6. Finalize the employee pay (i.e. with Paid Date via Bank Download) 7. Run the Prepare STP Pay Details 8. Run the 'Review STP Pay Details' report 9. Confirm that the correct total allowance amount is reported and no warning for the negative amount is received. e.g. Meal Allowance reported as $40 total (50-10).

Solution Implemented

The STP preparation process for the allowances has been corrected to total allowance amounts by Allowance Type. NOTE Allowances classified as 'Other' type are reported under multiple allowance YTD amounts based on the Allowance pay component Description.

HRPC-1877 - NZ PayDay - new KiwiSaver status 'Contributions holiday' and minor issues in New and Departing Employees Report (Employee Details report)

Functional Issue

A new option is required for the KiwiSaver Membership enrolment type for 'Contributions Holiday'. This option is loaded into the New and Departing Employees report which supports NZ Payday filing. New and Departing Employees report has an issue with reporting of KiwiSaver Status for 'Non-Members'. New and Departing Employees report has an issue with IRD Number being invalidated when opening report definition from XLOne designer. Workaround is to change the cell type to 'General'.

Functional Verification

1. Create a new New Zealand employee 2. Confirm the KiwiSaver Membership enrolment drop down includes the 'Contributions holiday' option 3. To ensure the payroll calculation process does not include KiwiSaver contributions for the employee on Contribution Holidays, assign the employee to a KiwiSaver Superannuation Fund that has NO contribution details (i.e. no employee, employer, or Esct contribution items) 4. Complete the KiwiSaver Membership section and select the 'Contributions holiday' Enrolment Type 5. Complete the rest of the new employee's details, and Save 6. Navigate to the NZ IRD New and Departing Employees Report 7. Enter the required fields to process the new employee, including the Report date range which only includes the unreported new and departing employees (i.e. since the last notification to the IRD) 8. Process the report 9. Review the report generated and confirm the KiwiSaver status column has the status 'Contributions holiday' 10. Remove column A from the report per the note on the report 11. Upload the report to the IRD via MyIR website.

Solution Implemented

The New Zealand KiwiSaver Membership section of employee maintenance and the New and Departing Employees report have been updated to allow reporting of an employee on a Contributions Holiday. An issue with reporting of KiwiSaver Status for 'Non-Members' has been corrected. An issue with IRD Number being invalidated from XLOne designer has been corrected. i.e. cell type changed to 'General' from 'Text'. NOTE For full functionality of the 'Contributions holiday' enhancement, ensure that the region data is updated via running the 'HR and Payroll Load Region Data' function for Region '$NZ' and Test Check = 'N'.

HRPC-1899 - STP Report Changes for People data analyser usage

Functional Issue

Single Touch Payroll reports will error for users with only Payroll Officer access due to missing access to the HR People data analyser.

Functional Verification

1. Log in as a user with Payroll Officer workplace access 2. Navigate to 'Drag and Analyse' > Human Resources 3. Confirm that the 'People' data analyser is available 4. When logged on with access only to the Payroll Officer workplace. i.e. no Human Resource Officer shipped access 5. Navigate to 'Prepare STP Pay Details for ATO' i.e. after finalising employee pays for one or more employees 6. After successfully preparing STP Details, review the STP details via the report link provided. i.e. executing the shipped XLOne report HRPAY_STPPayReport 7. Run the STP pay details report 8. Confirm that the report runs successfully. i.e. without failing error messages for "NullReferenceException".

Solution Implemented

The shipped Payroll Officer workplace has been updated to include access to the Employees data analyser used by the STP reports.

HRPC-1915 - Payroll reports will not run in CiA - standard code selection error

Functional Issue

Payroll crystal reports have standard code picklists which are returning the Code Description instead of the Code Id. This causes errors in CiAnywhere apps. NOTE No error occurs in Ci execution of these crystal reports.

Functional Verification

1. From CiAnywhere Payroll app, open the Exception or Variations Report 2. Complete mandatory report criteria 3. Specify a criteria for Pay Group or Document Type 4. Confirm that all combo boxes for report criteria function correctly 5. Generate the report 6. Confirm that the report is generated correctly without error.

Solution Implemented

Payroll crystal reports have been corrected to return the Code Id in all standard code criteria. These include: Variations Payroll Exceptions Pay Calculation Pay Calculation for Multiple Companies Pay Component Detail by Employee Pay Item Detail Pay Item Explanation Summary Pay Summary Pay Summary (incl Historical Data) Pay Summary Report across Multiple Companies Payment Advice for Multiple Companies Payroll Audit Report Overtime Hours Lost Time Report - Detail Lost Time Report - Summary

HRPC-1917 - NZ PayDay - Prepare function UI minor issues

Functional Issue

NZ PayDay - Prepare function UI minor issues

Functional Verification

1. Navigate to NZ Prepare Payday EI Upload File. e.g. from Adjust Pay or Calculate Payroll by Group 2. Confirm that the information text no longer has the word "stamped" included 3. Confirm that the Company field no longer has a calculator function 4. Resize the screen and confirm the info text under 'Pay Document Type Options' wraps with the screen 5. Click the Clear button 6. Re-enter the same Company Code and Pay Period End Date values as previously set 7. Confirm that the filename default is loaded again to reflect the selected criteria.

Solution Implemented

The function 'Prepare Payday EI Upload File' has been corrected to: 1. remove use of the word 'stamped' in the information text 2. remove the unnecessary calculator control on Company Code field 3. reload the default filename correctly after Clearing the function 4. wrap the information text when the screen is resized.

HRPC-1918 - NZ PayDay - Pay Master auditing 'last_mod' fields not updated

Functional Issue

When preparing NZ PayDay, the employee Pay Master records are not correctly updated with auditing values in the 'last_mod' fields. A warning message is not returned if a NIL Payday file is prepared due to an employee(s) being omitted due to negative amounts. E.g. Correction pays.

Functional Verification

1. For a New Zealand employee's pay 2. Ensure the pay is finalised/paid 3. Run the 'Prepare Payday upload file for IRD' 4. Review the employee pay master Audit Details (available via Adjust Pay function) 5. Ensure the Last Modified values have been updated by the 'Prepare Payday' process

Solution Implemented

The NZ Payday process has been corrected to set Last Modified values in the Pay Master records when the Submission ID and Status are updated. The NZ Payday process has been modified to ensure a NIL return warning message appears if the only employee found to process is excluded due to containing negative amounts.

HRPC-1922 - Single Touch Payroll - Updated ATO validation on Allowance Description for 'Other Allowance' types

Functional Issue

Effective from 16 March 2019, the ATO has extended STP event validation on the 'Other Allowance Type' field to stop illegal characters from being used and causing failed STP event submissions.

Functional Verification

1. For an allowance that is reportable as 'Other' to the ATO under Single Touch Payroll. i.e. the allowance pay component has configuration code 'TAX_ALLW' selected with either 'ALLW_OTHER' or no other allowance classification selected. 2. Ensure the pay component description has one or more invalid characters as per ATO guidelines. i.e. where valid allowance description characters include: A to Z a to z 0 to 9 ! @ $ % & * ( ) - = [ ] ; : ' " , . ? / or a space character 3. Prepare the STP Pay event for an employee's pay who has this allowance paid 4. If successful preparation, proceed to Submit STP Pay event to ATO 5. Confirm that submission is successful and a warning message is returned stating that the allowance description was changed by removing invalid characters.

Solution Implemented

The Single Touch Payroll submission process has been enhanced to exclude invalid characters from the 'Other Allowance Type' field.

HRPC-1952 - $AU ATO legislative changes effective 01/07/2019

Functional Issue

1. The Australian HELP/TSL and SFSS Other Scales are to be updated from 1 July 2019 2. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2019 3. The Maximum super contribution base amount will increase from 1 July 2019 4. The indexed ETP cap amount will increase from 1 July 2019.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace 2. Navigate to the Manage Payroll Tab 3. Navigate to the HELP (SSL or TSL) income thresholds (Other Scales -> $AU - Australia -> AU_HELP - HELP): 4. Confirm that new HELP (SSL or TSL) income thresholds are available for the 1 July 2019. 5. Navigate to the SFSS repayment thresholds (Other Scales -> $AU - Australia -> AU_SFSS - SFSS): 6. Confirm that SFSS repayment income thresholds are available for the 1 July 2019. 7. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Scales -> $AU - Australia -> AU_GRTFL): 8. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2019. 9. Navigate to the Maximum Super Contribution Quarterly Base (Other cales -> $AU - Australia -> AU_SUP_BAS): 10. Confirm that the Max Quarterly Base is $55,270.00 - details scale column (B). 11. Navigate to the Employment Termination Payment (ETP) CAP Amount (Other Scales -> $AU - Australia -> AU_ETP_CAP): 12. Confirm that the ETP Cap Amount is $210,000.00 - details scale column (B).

Solution Implemented

1. New Australian HELP/SSL/TSL and SFSS Other Scales have been added for the 2019-2020 financial year (refer to ATO website). NOTE: As of 1 July 2019, the ATO now refers to these tax scales under the combined name of Study and Training Support Loans (STSL). i.e. HELP, VSL, SSL, ABSTUDY, TSL and SFSS scales have the same rates and thresholds. 2. New Australian Genuine Redundancy Tax Free Limit thresholds have been added for the 2019-2020 financial year (refer to ATO website). 3. The Other Scale for the Superannuation Maximum Quarterly Base has been updated effective 1 July 2019 (to 55,270.00). 4. The Other Scale for the ETP Cap Amount has been updated effective 1 July 2019 (to 210,000.00). 5. The Commonwealth Superannuation corporation (CSC) have NOT published the new EPSC rates for 1 July 2019, we will provide an updated release when the new rates are published. IMPORTANT NOTE At time of this publication the ATO had not released updated Tax Scales 2019-20 for the medicare levy threshold changes. These will be released as soon as they become available. As per every EOFY, legislative Tax Scales can be updated or added manually by users. Please refer to the Customer Community for the EOFY Knowledge Base articles for further details. NOTE: To ensure that these new tax details are loaded into your database(s) for releases 2018A onward: 1. Ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server. 2. Alternatively, for On-Premise installations, a Package Finalise can be executed after applying this update. 3. If the scales are still not updated after the above two solutions, please run the 'HR & Payroll Load Region Data' function for region $AU and N for Test Mode. NOTE: If employers have not taken the Legislative release updates for Payroll beyond May 2017 (2017A) then the above tax scales changes must be done manually. Additionally, the DEFAULT control variable values for ETP Cap and Super Quarterly Max must be updated manually after 30 June 2018. i.e. These Control Variable values are obsolete and no longer updated from the 1/7/2017 values: 1. HR_SUP_BASE_MAX 2. HR_ETP_CAP

HRPC-1955 - EDF IR 345 text file no longer supported by myIR

Functional Issue

EDF IR 345 text file extension (.txt) is no longer supported by the IRD's myIR portal.

Functional Verification

1. As a Payroll Officer, navigate to Electronic Deduction Form (IR 345) function (HRUPD410) 2. Complete the period criteria and Start Processing 3. Confirm that the generated file extension is now .csv (instead of .txt) 4. Upload to the IRD MyIR website portal, and confirm the csv EDF file is accepted 5. Repeat steps 1-4 for the KiwiSaver Employment Details (KS1) and Employer Monthly Schedule (IR 348). NOTE Both EMS and EDF are no longer required by the IRD for pay periods after 1 April 2019.

Solution Implemented

The IRD electronic reporting function has been updated to default the filename to the .csv extension (instead of .txt). NOTE Both EMS and EDF are no longer required by the IRD for pay periods after 1 April 2019.

HRPC-1961 - STP - SBR2Utils does not use the correct SQL.Node for updating Last_mod_term field

Functional Issue

STP processing does not update the Pay Master records correctly for the Last Modified Terminal field (Last_mod_term).

Functional Verification

1. Calculate and finalize pay of an Australian employee 2. Prepare the STP Pay Details 3. Submit the STP Pay Details 4. Navigate to Adjust Pay and load the employee pay 5. Once the Submission Status has been updated by the STP submission engine job ($SBR) 6. Use Audit Details to confirm that the Pay Master last modified Node value has been set.

Solution Implemented

STP submission processing has been corrected to set the Last Modified Terminal value (i.e. using SQL.Node variable instead of SQL.Term).

HRPC-1995 - Back pay fail to bank download due to change of Pay Group

Functional Issue

Back Pay master records can be produced with an earlier Pay Group for employees who have had a change of Pay Group during the date range of the Back Pay. This causes Bank Download and/or back pay retrieval to fail.

Functional Verification

1. For an employee who has had a change of Pay Group during the date range for which a back pay is owing 2. Navigate to "Calculate Manual Back Pays by Group" specifying the current Pay Group of the employee(s) due the back pay 3. Specify the back pay criteria with a From and To date range that includes the employee's previous job and Pay Group 4. Retrieve the pay components impacted and employees 5. Calculate 6. View the employee's back pay by navigating to Adjust Back Pay for Employee 7. Perform the Bank Download for the retrieved back pay 8. Confirm that the bank download succeeds without error. NB previously failing with error message = "No Pay Items matching the following criteria are available for Bank Download".

Solution Implemented

The Manual Back Pay process has been updated to only include employees assigned to the selected Pay Group effective as at the Pay Period End Date of the back pay.

HRPC-1997 - The payroll calculation can overpay monthly employees entitlement due to leave taken for the entire pay period.

Functional Issue

Overpayments can happen for monthly employees when: 1. Leave has been taken in a pay period and the leave taken hours is greater than the employee's entitlement hours. 2. Leave without pay has been taken for the entire pay period but the leave taken hours is less than the employee's entitlement hours.

Functional Verification

Environment Setup 1. Navigate to the Default control variable and set the "Entitlement Reduction" to "Balancing Entry" (MODIFY). Leave Overpayment 1. Configure a monthly employee to a pay period that ends on the 15th of the month. 2. Configure the employee with an entitlement of 150 hours for $3000. 3. Configure the employee with leave accruals. 4. Enter leave starting the 16-April-2019 and ending on the 15-May-2019. 5. Calculate the pay for the period ending 15-May-2019 ensuring to load both Entitlements and Timesheets. 6. Confirm that the pay is calculated with no errors. 7. Confirm that the following warning messages is displayed, "Leave taken (<leave_pcc>) for employee Id <employee_id> in the pay period ending 15-May-2019 is greater than the employee's entitlement. A reversal for the amount of -520.00 has been made." 8. Confirm that leave taken pay component is for 176 hours. 9. Confirm that a reversal Base Pay pay component for -26 hours exists and has a pay item explanation of "Leave (<leave_pcc>) Overpayment Reversal". 10. View the Calculation Audit and confirm a section exists for "Checking Leave Overpayments". 11. Confirm that the "Checking Leave Overpayments" section contains information detailing Leave Hours, Entitlement Hours and Adjusted Leave Hours. 12. Confirm that the "Checking Leave Overpayments" section contains information detailing Leave pay component that was overpaid and the amount of the reversal pay item. Entitlement Reduction 1. Configure a monthly employee to a pay period that ends on the 15th of the month. 2. Configure the employee with an entitlement of 170 hours for $3000. 3. Configure the employee with leave accruals. 4. Enter leave without pay starting the 16-February-2019 and ending on the 15-March-2019. 5. Calculate the pay for the period ending 15-March-2019 ensuring to load both Entitlements and Timesheets. 6. Confirm that the pay is calculated with no errors. 7. Confirm that the following warning messages is displayed, "Employee Id <employee_id> has taken leave for the entire pay period ending 15-March-2019 but it is less than the employee's entitlement. A base pay adjustment for leave taken (<leave_pcc>) for the amount of 0.00 has been made." 8. Confirm that leave taken pay component is for 160 hours. 9. Confirm that a Offset Adjustment Base Pay pay item for 10 hours with an amount of 0.00 exists and has a pay item explanation of "Leave (<leave_pcc>) Offset Adjustment". 10. View the Calculation Audit and confirm a section exists for "Checking Leave Overpayments". 11. Confirm that the "Checking Leave Overpayments" section contains information detailing Leave Hours, Entitlement Hours, the leave pay component that needs to be adjusted and the amount for the adjustment base pay pay item.

Solution Implemented

New default control variable introduced to provide 3 modes of operation for the Leave Overpayment processing. 1. None - No change to existing functionality. 2. Warning - Warning message is displayed, logging is written to the calculation audit and balancing pay items are NOT created when overpayment scenarios detected. 3. Balancing Entry- (Modify) Balancing pay items are created when overpayment scenarios detected as well as a Warning message (displayed and written to the calculation audit). When leave has been taken in a pay period and the leave taken hours is greater than the employee's entitlement hours a reversal pay item will be created for the amount of hours that the leave exceeds the employees entitlement and at a rate based on the leave taken pay item rate. When leave has been taken in a pay period and the leave taken hours is for the entire period but is less than the employee's entitlement hours an adjustment pay item will be created for the amount of hours that the entitlement exceeds the leave hours and at a rate based on the leave taken pay item rate. Where different leave types and rates (Eg Annual Leave is at full pay and Sick Leave at half pay) exist the balancing pay item hours will be based on the ratio of that leave hours over the period and the balancing pay item rate will be based on the leave taken pay item rate.

HRPC-2021 - STP error on country code 1101

Functional Issue

Country code 1101 is not accepted by the ATO for STP event details. This is the Australian code used by the Australian Bureau of Statistics and should be translated to 'au' in STP events.

Functional Verification

1. For customers using the Australia country code '1101' in order to integrate with systems aligned with the Australian Bureau of Statistics: 2. In Company Maintenance, select country code 1101 for the Street & Postal country address 3. For an employee working for the Australian company also select the country code 1101 for their Street & Postal country address 4. For a calculated and paid employee pay, Prepare STP Pay event for ATO 5. Open the Data Analyser for STP Event PAY Employees Data Analyser and filter for the recent pay prepared for STP 6. Confirm the Payee Street Country and Payer Postal Country columns are displayed and set to AU 7. Submit the STP Pay event after signing the Declaration 8. Confirm the ATO respond with Success.

Solution Implemented

The STP process has been enhanced to translate an Australia country code of 1101 to the ATO STP valid country code of AU. NOTE In addition to the current translation of code 61 and blank to AU (both interpreted as Australia).

RELEASE November 2018

HRPC-551 - Payroll Calculation - Improve Error messages

HRPC-600 - Payroll liability calculated for casual employees not currently working

HRPC-621 - Pay Advice for Multiple Companies - Pay Group picklist blank

HRPC-807 - Superannuation not calculating when no hours worked on primary position or on rostered position

HRPC-883 - Single Touch Payroll - add Submission Status (STP) to Payroll enquiry views and critieria

HRPC-909 - STP Deductions for Unions - load Deduction Payee name instead of Union on Job

HRPC-1333 - NZ IRD clarification taxing lump sums for ND and NSW Tax Code

HRPC-1427 - Performance Issues/Timing Out Calculate Pay by Group

HRPC-1469 - Imported files dropping off decimals - Pay import

HRPC-1556 - Single Touch Payroll - Adjust Payroll / Calculate by Group Display STP Status

HRPC-1559 - Payroll fails when the employee is a WHM with fixed tax percentage

HRPC-1574 - Pays Not Calculating Through "Calculate Payroll by Group"

HRPC-1634 - Single Touch Payroll - Validation for email addresses

HRPC-1636 - Single Touch Payroll - Submit EOFY job incorrectly labelled

HRPC-1639 - Single Touch Payroll - Intermediary Role setting for SBR2 ebms3 header

HRPC-1659 - Single Touch Payroll - Payer Gross Amount not including Non Taxable allowances

HRPC-1665 - Single Touch Payroll - WHM and Vol Agree Gross Amount YTD does not include Non-taxable Allowances

HRPC-1668 - STP Submission error message is incorrect when SBR2 system data is missing

HRPC-1675 - Single Touch Payroll - ATO change for address field validation

HRPC-1728 - Update Paid Date - YTD Opening Amount incorrect for some pay components when first appearing in a pay of the Financial Year

HRPC-1744 - Single Touch Payroll - Prevent ATO transmission for non-Prod environments

HRPC-2038 - NZ PayDay Filing Files error on filename greater than 40 char

HRPC-551 - Payroll Calculation - Improve Error messages

Functional Issue

Pay Calculation can fail with 'Object Reference not set' errors when the user has incorrect data in payroll configuration. E.g. Company Financial years have the same or overlapping start and end dates. No Pay Periods configured for a company pay group prior to the first pay run. Multiple companies sharing a Pay Group but with varying Pay Period End Dates.

Functional Verification

1. Navigate to Company Maintenance and load an existing company 2. Maintain Financial Years and enter a new year with dates that overlapped with an existing period 3. Confirm that an error message is displayed and the incorrect new Financial Year is not saved. 4. Navigate to Calculation Payroll for Multiple Companies, where the pay group has more than one company and varying Pay Period End Dates. E.g. 10/7/2018, 12/7/2018 for fortnightly pays. 5. Calculate the pay for more than one selected company 6. Confirm that the pays either succeed or provide the user with valid error messages.

Solution Implemented

Additional validation has been added to Company Maintenance / Financial Years to prevent user entering overlapping dates for financial years. Additional error handling has been added to the creation/update of Payroll Summary YTD records (for pay advice use). NOTE For the full resolution of this issue, upgrade the latest versions of both Payroll Processing and HRP Core Ci Packages.

HRPC-600 - Payroll liability calculated for casual employees not currently working

Functional Issue

The payroll liability process can generate liability for casual employees who are not currently working. The employees affected have a primary position Pay Basis of Hourly and the Use Timesheets Only calculation method selected.

Functional Verification

1. Locate an employee whose current active position has the Pay Basis set as hourly and the Use Timesheets Only calculation method. 2. Confirm the final pay period for the current month has not been calculated for the employee. 3. Calculate the pay liability for the employee. 4. Review the pay liability including messages displayed. 5. Confirm the liability is not calculated for the employee. 6. Confirm a message is displayed to advise the liability has calculated due to no normal pay within the preceding pay period. NOTE: If the existing behaviour is preferred, define a system variable 'HR_PAY_LIAB_CASUAL' with the value 'Y' within the '$HR' system variable group. This will generate pay liability or casuals whose have not worked within the preceding ordinary pay period.

Solution Implemented

Changed the pay liability calculation process to not generate a liability for casual employees not paid within the preceding pay period. NOTE: If the existing behaviour is preferred, define a system variable 'HR_PAY_LIAB_CASUAL' with the value 'Y' within the '$HR' system variable group. This will generate pay liability or casuals whose have not worked within the preceding ordinary pay period.

HRPC-621 - Pay Advice for Multiple Companies - Pay Group picklist blank

Functional Issue

The Payment Advice for Multiple Companies report displays a blank list in the Pay Group picklist.

Functional Verification

1. Navigate to the 'Payment Advice for Multiple Companies' report 2. Open the Pay Group picklist 3. Confirm that the picklist displays the list of Pay Groups 4. Select a Pay Group 5. Complete criteria 6. Start Processing 7. Confirm that the pay advice report is generated correctly based on the chosen criteria.

Solution Implemented

Corrected Pay Group picklist in the Payment Advice for Multiple Companies report to display a list of valid Pay Groups.

HRPC-807 - Superannuation not calculating when no hours worked on primary position or on rostered position

Functional Issue

Superannuation was not calculating when there was a mid pay period primary position change and the pay period did not include any superannuation earnings for the new primary position.

Functional Verification

1. For an employee on timesheets who has a mid-pay period position change due 2. Calculate the current pay period to confirm the superannuation is calculated correctly 3. Create new job details with an effective date before the last day of the following pay period 4. Create timesheet entries for the old primary position on work days up to but not including the effective date of the new job details 5. Load the ordinary pay that includes the new effective job details 6. Select Load Timesheets - do not load entitlements for this test 7. Calculate the pay 8. Confirm the pay completes with the superannuation being calculated correctly per the superannuation fund configuration. NOTE: The superannuation contribution pay items will be created with the new primary position code assigned to them. The process creates the superannuation items as at the pay period end date.

Solution Implemented

Changed the pay calculation to ensure the superannuation is calculated correctly when the employee has a mid period primary position change.

HRPC-883 - Single Touch Payroll - add Submission Status (STP) to Payroll enquiry views and critieria

Functional Issue

The Payroll Enquiry function requires enhancement for Single Touch Payroll, by adding the Submission Status to the Pay Master view. This allows the Payroll Officers to see if the pay has been submitted to the ATO and what the resulting status is. NOTE Displaying a Submission Status can apply to all regions where the legislative reporting is pay period based and processed within the application. E.g. New Zealand payday filing

Functional Verification

1. Navigate to 'Payroll Enquiry' 2. Specify the Paid Date criteria, and any other criteria required 3. Select 'Perform Enquiry' 4. From within the Summary Views, select any Pay Component Code. This will display the Detail Views 5. Select the 'Pay Master' tab 6. Confirm that the 'Submission Status' column is displayed in the grid. If the employee's pay has been included in STP processing and submitted to the ATO, this field will contain the resulting status. E.g. one of: - Success - Awaiting Response (from the ATO) - Failure - Missed (was not submitted to the ATO and has been superceded by a later pay that has been submitted to the ATO)

Solution Implemented

Payroll Enquiry function has been updated with a new 'Submission Status' field in the Pay Master grid.

HRPC-909 - STP Deductions for Unions - load Deduction Payee name instead of Union on Job

Functional Issue

Reporting Union fees on the current ATO PAYG Payment Summary loads the description from the Union field on the employee's currently active position (i.e UNION_CODE standard code). If a Deduction Payee has been defined on the union pay component code, then this payee description should be used on the PAYG Payment Summary.

Functional Verification

1. For an employee who has a Union Fees pay component deduction on their active entitlements 2. Ensure that the union fees deduction Pay Component Code is configured with UNION_DUES and also has a Deduction Payee code selected 3. Navigate to Adjust PAYG Payment Summary 4. Load the employee's payment summary 5. Confirm that the Deduction Payee name is included on the payment summary for the employee's paid Union Fees amount.

Solution Implemented

The PAYG Payment Summary process has been updated to include the Deduction Payee description for Union Fees. If a Deduction Payee has not been defined on the pay component for the union fees, then the description of the Union standard code on the employee's active job is used.

HRPC-1333 - NZ IRD clarification taxing lump sums for ND and NSW Tax Code

Functional Issue

NZ IRD payroll specification effective 1/4/2018 included clarifications to PAYE for ND (No Notification) and NSW (Non-resident Seasonal Workers) Tax Codes when withholding for Lump Sum Payments. These should be taxed at the applicable flat rate rather than as part of the annualised grossed up income.

Functional Verification

1. Calculate a pay for New Zealand employee on either ND or NSW Tax Code 2. Add a Lump Sum to the pay 3. Recalculate pay 4. Ensure that the tax calculation taxes the Lump Sum amount as per the tax code flat rate rather than part of the annualised grossed up income.

Solution Implemented

The NZ tax calculation has been changed to apply the associated flat tax rate to lump sums for employees on tax codes ND and NSW.

HRPC-1427 - Performance Issues/Timing Out Calculate Pay by Group

Functional Issue

Timeouts can occur from 'Calculate Pay by Group' function when attempting to load employees for selection into the grid. NOTE This may occur only when employees are entering time worked using CiAnywhere Timesheet apps.

Functional Verification

1. Navigate to Calculate Pays tab or 'Calculate Payroll by Group' 2. Select the Pay Period to calculate 3. In Processing Options choose the option to 'Process Selected Employees' 4. Select Retrieve (employees) 5. Confirm that employees are loaded correctly into the grid according to the selected criteria and displaying the correct status for their pay. 6. Repeat the above testing for the function 'Update Paid Date' to confirm that timeouts do not occur for employee retrieval into the grid. NOTE Immediately repeat the employee grid 'Retrieve' if the first attempt receives a Timeout.

Solution Implemented

The retrieval SQL has been altered to optimise the retrieval of CiAnywhere Timesheets for the queries used by the functions 'Calculate Pay by Group' and 'Update Paid Date'.

HRPC-1469 - Imported files dropping off decimals - Pay import

Functional Issue

Payroll import only saves Number of Units value up to 2 decimal places, whereas it should support to 4 decimal places.

Functional Verification

1. Import a leave accrual adjustment for an employee (Document Type = V) NOTE Ensure the field for Number of Units has a value to 4 decimal places. E.g. 12.3456 2. Open Leave Accrual Adjustment for Employee 3. Load the leave accrual adjustment that was imported 4. Confirm that the imported Number of Units correctly loads to the 4 decimal value.

Solution Implemented

The pay import process has been updated to load 4 decimal values correctly into the Number of Units field.

HRPC-1556 - Single Touch Payroll - Adjust Payroll / Calculate by Group Display STP Status

Functional Issue

Payroll functions 'Adjust Payroll' and "Calculate by Group" should display the STP Submission Status, along with Paid Date.

Functional Verification

1. For Australian employees, do the following 2. Navigate to the 'Adjust Payroll' function 3. Confirm that the 'Submission Status' field is displayed in the Payroll Details summary 4. Once pay is submitted to the ATO, confirm that this field is updated with the appropriate status: - Awaiting Response - Success - Failed 5. Similarly, navigate to the 'Calculate Payroll by Group', and confirm that the 'Submission Status' field is displayed in the grid of employee pays.

Solution Implemented

The new field for 'Submission Status' field has been added to payroll calculation functions to display each employee's STP status for the pay.

HRPC-1559 - Payroll fails when the employee is a WHM with fixed tax percentage

Functional Issue

An exception is thrown when calculating the pay of a Working Holiday Maker employee that has defined a Fixed Tax Percentage override value in their Tax Details. NOTE This is an invalid tax option for WHM. Immediate solution is to remove the Fixed Tax Percentage value from the employee's tax details.

Functional Verification

1. For an employee who is classified as a Working Holiday Maker 2. Navigate to Employee Maintenance and Tax Details for this employee 3. Complete the Fixed Tax Percentage to a value above zero NOTE This is an invalid option for a WHM. WHM are to be taxed as per the ATO specified tax rates. 4. Calculate a pay for this employee 5. Confirm that the pay calculates without error.

Solution Implemented

The Fixed Tax Percentage value is ignored for calculating pays of Working Holiday Maker employees. The tax withholding rates as supplied by the ATO for WHM are applied (defined in shipped Other Scales).

HRPC-1574 - Pays Not Calculating Through "Calculate Payroll by Group"

Functional Issue

Employees on 'Exception Entry' (job timesheet calculation method), are not always included in payroll calculation when using the 'by group' process. This only occurs when 1. the calculation option to 'Exclude Employees With No Timesheets" has been selected AND 2. the employee is on 'Exception Entry' and 'Hourly' pay basis AND 3. the employee has not submitted a timesheet for the pay period.

Functional Verification

1. Navigate to "Calculate Payroll by Group" 2. For a pay group with employees on 'Exception Entry' and a pay basis of Hourly 3. Ensure one or more of those employees have not submitted a timesheet for the pay period 4. Check the calculation option "Exclude Employees With No Timesheets" 5. Process pays 6. Confirm that the employees on Exception Entry have all had pays calculated.

Solution Implemented

The pay calculation process has been updated to ensure that the option to 'Exclude Employees With No Timesheet' is only applied to Timesheet Only employees who have not completed a timesheet for the period.

HRPC-1634 - Single Touch Payroll - Validation for email addresses

Functional Issue

The ATO have provided additional guidance on accepted characters in email addresses for STP events. i.e. in Payee (employee), Payer and Intermediary. Currently ATO systems may fail silently if invalid characters are included in email addresses. Alternatively, an ATO error message will be returned. E.g. "Email Address contains invalid text. A text character must be one of the following: A to Z a to z 0 to 9 ! @ $ % & * ( ) - _ = [ ] ; : ' " , . ? / or a space character"

Functional Verification

1. As Payroll Office, test an employee who has invalid characters included in their email 1 address (Street Address) 2. Proceed to 'Prepare STP Pay Details for ATO' for one of the employee's pays (Paid) 3. Confirm that the details have been prepared and still include the invalid character(s) in the email address (see Review report) 4. Submit the STP pay event. 5. Confirm that the STP pay event is successfully submitted and a warning message is returned. This advises that invalid characters have been removed from the email address field prior to submission. NOTE If an email address field does not have a '@' character followed by at least one period '.' character, then a Warning message is returned from the 'STP Prepare' process. As the email address is optional, it is removed completely from the STP event details, and will not be sent to the ATO.

Solution Implemented

Additional email validation has been added to the 'STP Prepare' and 'STP Submit' processes. Invalid characters are removed from email addresses prior to submission. A warning message informs the user that this has occurred. Email addresses with Invalid formats are removed from the STP event details. A warning message informs the user that this has occurred during the STP preparation process. NOTE Email addresses are optional. These can be left blank by the employee or payroll officer. STP event preparation and submission will not fail due to an invalid email address. The STP process will not correct the source of the email address. i.e. Employee Street Address - Email field 1, Company contact email address, Taxation Supplier email address.

HRPC-1636 - Single Touch Payroll - Submit EOFY job incorrectly labelled

Functional Issue

When running the 'Submit STP EOFY Employee Finalisation to ATO, the title of the job is incorrectly set to 'Submit STP Update to ATO' function. This is due to the two STP processes sharing the same function but not being overridden at runtime.

Functional Verification

1. Navigate to 'Prepare STP EOFY Employee Finalisation for ATO' 2. Select the employees whose Financial year income statements are ready to be finalised with the ATO. NOTE This is an EOFY legislative reporting process for Australian companies only. 3. Process the job 4. Confirm successful generation of the data by using the Review report 5. Proceed to 'Submit STP EOFY Employee Finalisation to ATO' 6. Process the job 7. Confirm that the process title is correctly set for the EOFY process.

Solution Implemented

The STP Submit job title has been corrected to display the associated STP activity.

HRPC-1639 - Single Touch Payroll - Intermediary Role setting for SBR2 ebms3 header

Functional Issue

The STP submission process was not setting the reporting party Role correctly within the report properties set for transmission to the ATO. The STP From Role value varies if an employer is reporting to the ATO via a Group or Intermediary ABN.

Functional Verification

1. Prepare an STP submission with the Taxation Supplier option 'Single Intermediary Taxation ABN submitting STP for multiple payroll companies' selected. 2. Transmit the submission. 3. Confirm the messages and processing log indicates the submission has been successful. 4. After the ATO has returned the validation response confirm the transmission was successful.

Solution Implemented

Changed the STP submission process to set the reporting party role within the transmission report's properties dependent on the user's submission options. i.e. STP Role is 'Business' if 'Not Applicable' is chosen. STP Role is 'Intermediary' if a Taxation Supplier with group or intermediary ABN is selected. NOTE: The report properties are not visible to the user.

HRPC-1659 - Single Touch Payroll - Payer Gross Amount not including Non Taxable allowances

Functional Issue

For Single Touch Payroll Pay events, the Payer Gross Amount has not included all the reported allowances for the period. The 'non-taxable' allowance amounts have been incorrectly excluded from the Payer Gross amount. NOTE Employee YTD allowance and gross amounts are correctly reported.

Functional Verification

1. As Payroll Officer, navigate to a pay period that has been calculated and paid, but not submitted to ATO STP 2. Proceed to Prepare the STP Pay event details 3. Run the report to review the STP Pay event details 4. From the report, confirm that the 'Payer Gross Amount' now includes 'non-taxable' allowances that have been reported in employee Allowance YTD. i.e. 'Payer Gross Amount' will include all taxable income plus the 'non-taxable', reportable allowance total for the employee pays included in the STP pay event.

Solution Implemented

The Single Touch Payroll Payer Gross amount in the Pay event has been corrected to include non-taxable allowance amounts which have been reported in the employee Allowance types. NOTE 1. If an allowance is configured to be both non-reportable ('TAX_NONRPT' config code) and reportable to the ATO ('TAX_ALLW' config code), the allowance will be treated as reportable. i.e. The 'TAX_NONRPT' configuration is ignored. i.e. The allowance amount will be included in the employees STP Allowance YTD amounts, and also the Payer Gross Amount for the pay event period(s). 2. If an allowance needs to be excluded from all reporting to the ATO, then it must be configured with 'TAX_NONRPT' checked and 'TAX_ALLW' NOT checked. i.e. a non-reportable allowance that should not be included in Employee Allowances, Employee Gross, or Payer Gross. E.g. award overtime meal allowance (that does not exceed reasonable allowance amount) Refer to ATO website on Allowances and reimbursements - Withholding for allowances.

HRPC-1665 - Single Touch Payroll - WHM and Vol Agree Gross Amount YTD does not include Non-taxable Allowances

Functional Issue

In Single Touch Payroll, the ATO requires that all reportable allowances paid to Working Holiday Makers and Voluntary Agreement Contractors must be included in their corresponding Gross Amount (YTD). This is unlike INB employees, who have reportable allowances classified separately and only the non-classified, reportable allowances are included in their Gross Amount (taxed or untaxed). Refer to ATO website for more details on allowance classifications. Currently in the preparation of STP details, the Gross Amount for Working Holiday Makers and Voluntary Agreement Contractors incorrectly excludes their reportable Non-taxable Allowances amount. NOTE 1. Allowances that are NOT 'reportable' to the ATO must be configured with the code 'TAX_NONRPT'. This ensures that the amount is excluded from both Gross and Allowance amount. A non-reportable allowance must NOT have the code for reportable allowance also checked - 'TAX_ALLW'. i.e. cannot be both reportable and non-reportable. 2. Any allowance configured with 'TAX_ALLW' code WILL be reported to the ATO as per the ATO allowance classifications. Falling into 'OTHER' if no allowance classification is configured on the allowance pay component. 3. Reportable allowances can be either taxed or untaxed (i.e. have tax exempt components). 4. Allowances configured without either 'TAX_NONRPT' or 'TAX_ALLW' will be included in the Gross amount for employees. i..e reportable but not classified as per ATO requirements.

Functional Verification

1. For a Working Holiday Maker or Voluntary Agreement Contractor employee, ensure they have a reportable Non-Taxable Allowance in their current entitlements. i.e. 'Taxable' flag is disabled on their allowance pay component definition. NOTE Ensure that the config code 'TAX_NONRPT' is NOT checked. These amounts are not reported to the ATO. 2. Process a pay for this employee, including the bank download (for the Paid Date) 3. Prepare the STP details 4. Run the report to 'Review STP Pay Details' 5. Confirm that the Non-Taxable Allowance amount is included in their Gross Amount (YTD). NOTE WHM and Voluntary Agreement Contractors have separate fields for Gross Amount YTD and PAYG Withholding Tax YTD fields in STP events.

Solution Implemented

The STP Preparation process has been corrected to ensure that reportable Non-Taxable allowances are included in the Gross Amount YTD for Working Holiday Maker and Voluntary Agreement Contractor employees.

HRPC-1668 - STP Submission error message is incorrect when SBR2 system data is missing

Functional Issue

An incorrect error message is returned if the STP SBR2 system data has not been updated correctly. i.e. Message incorrectly refers to number of employee allowances.

Functional Verification

Verification is only possible if an incomplete upgrade for STP packages has occurred. i.e. an error has occurred installing packages or upgrading the database(s). 1. As Payroll officer, navigate to a completed employee pay for which fewer than 30 allowance types have been paid (i.e. pay must have a paid date) 2. Prepare STP pay event 3. Review STP pay details 4. Submit STP pay details to the ATO 5. Confirm pay event submission is successful, and no error messages are returned.

Solution Implemented

Corrected error message in the event that a STP SBR2 PAYEVNT process cannot be created.

HRPC-1675 - Single Touch Payroll - ATO change for address field validation

Functional Issue

The ATO have found an issue in production where characters that are outside the UTF-8 character set are causing the record (PAYEVNT or PAYEVNTEMP) to stop processing and not get recorded in ATO back end systems. Investigations revealed missing constraints on the character sets allowed in several address fields. Valid characters include: A to Z a to z 0 to 9 ! @ $ % & * ( ) - = [ ] ; : ’ " , . ? / or a space character

Functional Verification

1. As Payroll Officer, navigate to an employee pay ready for STP. i.e. has a paid date 2. For test purposes, add invalid characters into one or more of the following employee Street Address Fields. E.g. # or | - Address Line 1 - Address Line 2 - City (Suburb/Town) 3. Prepare STP pay details 4. Review STP pay details 5. Submit STP pay details 6. Confirm that the STP pay event is successfully submitted. Warning messages will indicate that invalid characters have been removed from the employee address fields before being sent to the ATO.

Solution Implemented

STP submission process has been enhanced with additional address field validation that strips out invalid characters (i.e. those not accepted by the ATO and which cause issues in their production systems). These fields include the following for both Payee and Payer addresses: - Address Line 1 - Address Line 2 - City (Suburb/Town)

HRPC-1728 - Update Paid Date - YTD Opening Amount incorrect for some pay components when first appearing in a pay of the Financial Year

Functional Issue

The 'Update Paid Date' does not correctly reset a Pay Component YTD Opening Amount to zero when it is first paid in a new financial year. E.g. Some pay components YTD Opening Amount are incorrectly set to the Closing amount of the previous financial year.

Functional Verification

1. For an existing employee who is paid an infrequent allowance 2. Calculate a pay later in the financial year and where the allowance first appears. E.g. first receives the allowance in an October pay 3. Bank Download the pay 4. Produce the Pay Advice 5. Confirm that the allowance YTD Amount is correct. i.e. via Pay Advice or Data analyser for Payroll Summary - with Employee Jobs

Solution Implemented

The Update Paid Date process has been corrected to reset Pay Advice YTD Opening amounts for first occurrences of pay components in the new financial year.

HRPC-1744 - Single Touch Payroll - Prevent ATO transmission for non-Prod environments

Functional Issue

STP submissions can be transmitted from NON production SAAS environments in the event where Production databases are copied to Test databases.

Functional Verification

1. From a cloud/SAAS TEST environment 2. Confirm that the STP system variable 'HR_ATO_STP_ENABLED' exists and is set to 'PROD' 3. Prepare and transmit a STP PAY event submission 4. Review the submission processing log and confirm a test submission only was done 5. Review the submission status and confirm the SUCCESS status has been applied 6. Log into a cloud/SAAS PRODUCTION environment 7. Prepare and transmit a STP PAY event submission 8. Review the submission processing log and confirm the submission was transmitted 9. Review the submission status and confirm the WAITING_RECEIPT status has been applied.

Solution Implemented

1. STP system variable is now shipped and defaulted to PROD. i.e.HR_ATO_STP_ENABLED = 'PROD' NOTE Additional STP config settings still need customer attention before they can successfully transmit to ATO. i.e. registering STP with ATO Access Manager, STP Cloud Server API Key and URL in system config. 2. Changed the STP submission process for SAAS installations to only proceed with submissions to the ATO from Production SAAS environments. NOTE: On-premise installations are not affected by this change. To prevent transmissions of STP events to the ATO from on-premise TEST environments, the TEST system configuration should exclude the STP SBR API and URL values.

HRPC-2038 - NZ PayDay Filing Files error on filename greater than 40 char

Functional Issue

When multiple Paid Dates exist within one pay run, the NZ payday filenames are appended with the Paid Date (i.e. _PDddMMMyyyy). If this filename exceeds a length of 40 chars, an error will occur saving the filename into the Submission Id on the Pay Master record.

Functional Verification

1. For a single pay run (Pay Group and Pay Period End Date) that includes multiple Paid Dates across the employee pays 2. Finalise the pays (calculate and bank download - with groups of varying Paid Dates) 3. Prepare the NZ Payday EI Upload File for IRD 4. Ensure the filename entered reaches the length limit on the field - i.e. of 40 characters 5. Run the Payday process 6. Confirm that the payday files are successfully created with different filenames appended with the Paid Date (_PDddMMMyyyy) 7. Navigate to the Data Analyser/Drag and Analyse for Pay Transactions 8. Enter criteria to view the pays of the pay run (Company, Pay Group, Pay Period End Date) 9. Confirm that the field Submission ID has the truncated filenames as a reference (i.e. limited to first 40 chars).

Solution Implemented

The NZ Payday process has been updated to correctly truncate the Submission Id field to 40 chars prior to saving the employee Pay Master records.

RELEASE May 2018

HRPC-528 - Leave Hours for Casual paid incorrectly in Special Pay

HRPC-888 - Single Touch Payroll - Voluntary Agreement Contractors in payroll

HRPC-930 - Single Touch Payroll - Corrective Access restriction on transmitted pays

HRPC-931 - Single Touch Payroll - ATO Allowance Types

HRPC-945 - Leave Accruals undercalculating DOS units

HRPC-984 - CiAnywhere 11 Pays failed to calculate without a valid error message.

HRPC-1097 - Single Touch Payroll - EOFY Reporting to ATO

HRPC-1098 - Single Touch Payroll - Update STP Employee YTD Amounts

HRPC-1242 - Single Touch Payroll for Australia - Prepare STP Pay Details (HRTAX300)

HRPC-1243 - Single Touch Payroll - Submit STP Pay Details function (HRTAX310)

HRPC-1261 - Payment to a deceased employee - manual calculation only supported

HRPC-1389 - Single Touch Payroll - Submit STP Update Employee YTD to ATO function (HRTAX380)

HRPC-1445 - KS1 KED File includes 'Opt Out' data for ALL companies

HRPC-1522 - PAYG Payment Summary - FBT not strictly based on paid FBT year 1 Apr - 31 Mar

HRPC-1557 - Single Touch Payroll - Submit issue with multiple Paid Dates and non-blank Status

HRPC-1560 - Manual back pays incorrectly reset the Pay Master Pay Period Start Date to the employee's Date Hired

HRPC-1563 - Single Touch Payroll - Validate TFN if not a Contractor with ABN

HRPC-1572 - Single Touch Payroll - direct access to STP Prepare Pay Details

HRPC-1575 - Single Touch Payroll - Manual Back Pay HRPAY510 links to STP and Bank Download

HRPC-1577 - Single Touch Payroll - Incorrect Message when a future 'As At Paid Date' is entered for Update events

HRPC-1580 - Single Touch Payroll - In 'Prepare STP Pay Details' allow Document Type to be modifiable

HRPC-1582 - Single Touch Payroll - Errors on Company ABN longer than 11 char

HRPC-1583 - Single Touch Payroll - Submit message when event is already at SUCCESS

HRPC-1586 - Single Touch Payroll - ReSubmit does not remove the previous STP message records

HRPC-1620 - Paid Date - Expected Paid Date payroll calculation parameter missed from serialisation

HRPC-1625 - Single Touch Payroll - Update event incorrectly finding companies earlier than Financial Year of 'As At Paid Date'

HRPC-1642 - Single Touch Payroll - Shipped system data for functions and reports

HRPC-528 - Leave Hours for Casual paid incorrectly in Special Pay

Functional Issue

Paying leave taken in Special pay can result in leave being over paid for timesheet only employees.

Functional Verification

1. For a Timesheet Only employee (i.e. casual) 2. Approve several leave taken by the employee for dates both retrospectively (i.e. in a past period already paid), and in the current pay period (which has not yet been paid) 3. Create a Special pay for a date that is after this leave but also within the same period as the next regular Payroll period 4. Calculate the Special pay, loading timesheets (which includes the leave taken yet to be paid) 5. Confirm that the pay loads correctly and pays the correct number of leave hours 6. Calculate the next regular Payroll pay and confirm that the leave is not included in this pay. i.e. as it was already paid in the Special pay

Solution Implemented

Additional validation has been added when paying leave to ensure that off-cycle pays do not duplicate paying leave due to overlapping pay period dates. E.g. Special, Bonus, Miscellaneous pays

HRPC-888 - Single Touch Payroll - Voluntary Agreement Contractors in payroll

Functional Issue

Reporting payments and withholding for contractors is an optional inclusion in Single Touch Payroll. Many employers pay contractors via Accounts Payable (Financials Invoicing). Currently any contractors paid via payroll are reported to the ATO as INB PAYG employees.

Functional Verification

1. Navigate to Employee Maintenance 2. Select an employee who is a Contractor with a PAYGW Voluntary Agreement and will be paid via Payroll 3. Create a new Tax Details record for the employee for the Effective Date that their Voluntary Agreement and payments from payroll commence 4. Complete all the tax details for the contractor, including selecting the 'Voluntary Agreement Contractor' indicator 5. Note that the Contractor ABN is mandatory if choosing to report an contractor with a Voluntary Agreement. This is a mandatory field to support STP pay reporting of Voluntary Agreement Gross and PAYG Withholding amounts 6. Save the changes 7. Calculate the next pay for the employee contractor 8. Prepare the STP pay details 9. Using the STP report or Data Analysers, confirm that the details for the employee contractor include: - Contractor ABN - All payments made to the contractor since the new Tax Effective Date are included in the single field for Voluntary Agreement Gross Amounts YTD - PAYG Withholding amounts since the new Tax Effective Date is included in the field for Voluntary Agreement PAYG Withholding YTD - Deductions are reported separately NOTE If the contractor was paid for a period of the Financial Year as an INB employee (non-contractor), these amounts are reported in the INB Payee amount fields in the STP Pay event. E.g. INB Payee Gross Amount and Payee PAYG Withholding YTD amounts, and separately reported amounts for Termination payments, Allowances, CDEP, etc.

Solution Implemented

Employee Tax Details Maintenance has new fields to identify a Voluntary Agreement PAYG Contractor who is paid via Payroll: - 'Voluntary Agreement Contractor' indicator - Contractor ABN STP reporting for Voluntary Agreement Contractors has amounts reported separately from INB Payees for Gross and PAYG Withholding.

HRPC-930 - Single Touch Payroll - Corrective Access restriction on transmitted pays

Functional Issue

As part of Single Touch Payroll enhancement, HRP Ci needs corrective access restriction on transmitted pay. The pay should not be allowed to be modified once it has been transmitted to ATO.

Functional Verification

1. Open Adjust Payroll function. Retrieve an existing pay that has been transmitted to ATO. Note: The submission status is not blank for the pay that has been transmitted to ATO. 2. Confirm that the link to save, recalculate and delete pay are hidden. Pay cannot be modified or deleted. 3. Retrieve another existing pay that has been processed in the Prepare STP function (HRTAX300). Note: The submission status is blank but the Submission Id has value for pay that has been processed in the Prepare STP function. 4. Recalculate the pay. 5. Confirm that a warning is displayed notifying user that payroll has been included in the STP prepare process. A re-run of STP Prepare Pay Details is recommended.

Solution Implemented

Updated the Adjust Payroll and Calculate pay by Group functions to prevent data modification when the pays have been submitted to ATO.

HRPC-931 - Single Touch Payroll - ATO Allowance Types

Functional Issue

The ATO have defined classifications of taxable allowances that are included in STP reporting (i.e. deductible allowances subject to PAYG withholding). These include: - Car - Transport - Laundry - Meals - Travel - Other In the existing PAYG Payment Summary, the details of each allowance is listed separately for up to 5 different allowance descriptions. STP reporting supports up to a maximum of 30 different allowance types to be reported for each employee. NOTE For the 'Other' type of allowances, the description of the allowance Pay Component code will be used to classify the allowance in the STP report.

Functional Verification

1. As Payroll officer, navigate to Pay Component Maintenance 2. Select an existing taxable allowance paid to employees. NOTE Taxable allowances that are being reported to the ATO (i.e. via PAYG Payment Summaries and STP). are configured with the System Config Code 'TAX_ALLW'. 3. Select the System Config Code that correctly classifies the allowance for STP reporting: - ALLW_CAR - ALLW_TRANS - ALLW_LAUND - ALLW_MEAL - ALLW_TRAVEL - ALLW_OTHER - the pay component description will be used as further classification in the STP report 4. The employee's deductible allowances subject to PAYG withholding, will appear separately in the STP pay events transmitted to the ATO. These are YTD amounts per allowance classification type. These allowance amounts are not included in the employee's Gross Amount YTD. .

Solution Implemented

New System Config Codes have been introduced to support the classification of taxable Allowances that deductible and reported to the ATO separately from Gross Amount YTD. Allowances that are non-deductible do not require the classification and these amounts continue to be included in employee Gross Amounts. NOTE For further information on ATO Allowance definitions, refer to their website: https://www.ato.gov.au.

HRPC-945 - Leave Accruals undercalculating DOS units

Functional Issue

The accrual process can miss including service hours from off-cycle pays due to applying a pro-rata of service for any Manual entered hours worked (DOS) based on the Pay Period Start and End Dates of the pay. e.g. Off-cycle pays include Special, Correction, and Bonus. i.e. Any service hours which occur between the Pay Period Start Date and the last accrual date are excluded.

Functional Verification

1. For an employee on Service-based Accruals, ensure the last pay period's accrual has been calculated and is correct 2. Calculate the employee's regular pay for the current period 3. Create a Special pay dated as at the start date of the current pay period (and dated after the Last Accrual calculation date). i.e. increasing service hours to be included in the accrual 4. Calculate the employee's Leave Accrual for the date ending the current pay period 5. Ensure the Leave Accrual calculation has included the correct number of service hours for the whole period, including the entire worked hours on the Special pay.

Solution Implemented

Off-cycle pays have been corrected to set a Pay Period Start Date which is equal to the Pay Period End Date. i.e. Correction, Special, Bonus, Miscellaneous pays.

HRPC-984 - CiAnywhere 11 Pays failed to calculate without a valid error message.

Functional Issue

CiAnywhere payroll requires employee Id Number to be included in the error messages from pay calculation processes. This enables matching and displaying of all errors with the corresponding employee pay in CiAnywhere.

Functional Verification

1. From CiAnywhere payroll app (or Ci Calculate Payroll by Group), calculate one or more employee pays 2. For at least one of the Superannuation pay items, proceed to Financials and change its account number to be Inactive 3. Confirm that the pay calculation fails with the correct error message which now contains the employee Id Number.

Solution Implemented

Enhanced error messages generated from the Pay Component Lookup Process to include the employee Id Number.

HRPC-1097 - Single Touch Payroll - EOFY Reporting to ATO

Functional Issue

Single Touch Payroll for Australia - new function to Prepare STP EOFY Employee Finalisation for ATO

Functional Verification

The 'Prepare STP EOFY Employee Finalisation for ATO' function is an STP update event that allows the employer to notify the ATO that an employee’s payments are complete for a Financial Year. i.e. The equivalent of the current PAYG Payment Summary submission process of sending the PSAR/EMPDUPE to the ATO. Employee YTD amounts are calculated as at a given Paid Date. There are no specific Pay Periods selected and the STP EOFY function does not include Payer total amounts for Gross and Tax Withholding. This function is accessed directly as needed by the Payroll Officer i.e. to finalise the Financial Year YTD amounts for one employee, or all employees of a Pay Group or Company(ies). After preparing the STP EOFY data, the user then submits the details to the ATO via SBR2 transmission supported by the product infrastructure (the Standard Business Reporting framework used by the ATO for STP). Refer to linked function 'Submit STP Update Employee YTD to ATO'. NOTE: Best practice is to transmit all employee EOFY data to the ATO for a given Pay Group and/or Company. This ensures that no employee is inadvertently missed from the ATO finalisation of a financial year. Prerequisites: 1. The customer must be registered with both ATO and TechnologyOne for STP before being able to make submissions to the ATO. I.e. The ATO will return with errors if a relationship between all parties is not detected in their systems. 2. Only YTD amounts for employee pays that have been Paid will be included in STP reporting data. i.e. has both a Paid Date and Calculation Date. 3. Only payable Document Type pays are included in STP reporting data. i.e. Accruals and Liabilities calculated pay items are not included 4. The payroll officer will be limited to the companies and employees that they have security access to. 5. STP is only applicable to Australian payroll companies. i.e. companies assigned to other regions will be excluded from STP processing. 6. To finalise or update the EOFY employee details of previous financial years, the As At Paid Date must be set to 30 June (of that financial year end). 7. The STP EOFY Employee Finalisation (or Update YTD) can only be used for financial years that were reported to the ATO via Single Touch Payroll. 8. Financial Years that are reported to the ATO via STP, can be updated or corrected retrospectively for up to 5 years. E.g. The payroll officer can correct the employee YTD amounts for the Financial Year 2018-19 as late as the year 2023. Key Fields The 'As At Paid Date' is mandatory. Additional Processing Options There are several user options provided to specify what employees will be included in the 'Prepare STP EOFY Employee Finalisation for ATO’: 1. For a single employee – optional. Allows a single employee’s EOFY details to be finalised with the ATO 2. For a single Pay Group - optional. NOTE Leaving Pay Group blank allows the payroll officer to finalise employee EOFY details across one or more companies regardless of Pay Group. 3. For one or more Companies (that the user has security access to) – mandatory, unless a single employee Id Number is specified. Taxation Supplier The user must select a Taxation Supplier if: 1. they wish to submit the STP EOFY Finalisation across multiple Companies under a single Intermediary ABN, or 2. they are providing Payroll services for their registered payroll companies. In this scenario, the payroll agent must have received a written Declaration from each Payroll Company that they service. NOTE If the payroll officer does not select a Taxation Supplier, but does have access to multiple payroll companies that they are authorised to pay and submit STP update events, then each STP EOFY update Event will contain only a Declaration for the payroll ABN/Branch with the user’s details as the authorised representative. i.e. There will be no Intermediary Declaration details included in the STP update event. Each company will be processed as if individually signed and declared by the same individual. Links to other Functions After preparing the STP EOFY Finalisation data, the payroll officer will proceed to the next steps of reviewing the data (optional) prior to submitting the prepared STP EOFY Employee Finalisation to the ATO (via SBR2 infrastructure). • Review STP EOFY Employee Finalisation Report • Submit STP EOFY Employee Finalisation to ATO

Solution Implemented

The new function 'Prepare STP EOFY Employee Finalisation to ATO' updates the specified STP Data into the new STP reporting tables and marked it as completed for the Financial Year. The user can then choose to review the prepared STP EOFY data, or submit the prepared STP EOFY details to the ATO. Users navigate to this function directly from a payroll processing menu list.

HRPC-1098 - Single Touch Payroll - Update STP Employee YTD Amounts

Functional Issue

Single Touch Payroll for Australia - new function to Prepare STP Update Employee YTD for ATO

Functional Verification

This process function 'Prepare STP Update Employee YTD for ATO', loads the STP reporting tables with the STP Update event data which includes YTD Amounts for the employees specified. Employee YTD amounts are calculated as at a given Paid Date. There are no specific Pay Periods selected and the STP Update event does not include Payer total amounts for Gross and Tax Withholding. This function is accessed directly as needed by the Payroll Officer. i.e. to correct YTD amounts for one employee, or all employees of a Pay Group or Company(ies). After preparing the STP data, the user then submits the details to the ATO via SBR2 transmission supported by the product infrastructure (the Standard Business Reporting framework used by the ATO for STP). Refer to linked function 'Submit STP Update Employee YTD to ATO'. NOTE Best practice is to transmit all employee YTD amounts to the ATO for a given Pay Group and/or Company. This ensures that no employee is inadvertently missed from an update or correction of the YTD amounts for a group of employees. It will not adversely impact the ATO systems if the YTD amounts have not altered for any employee. Prerequisites: 1. The customer must be registered with both ATO and TechnologyOne for STP before being able to make submissions to the ATO. I.e. The ATO will return with errors if a relationship between all parties is not detected in their systems. 2. Only YTD amounts for employee pays that have been Paid will be included in STP reporting data. i.e. has both a Paid Date and Calculation Date. 3. Only payable Document Type pays are included in STP reporting data. i.e. Accruals and Liabilities calculated pay items are not included 4. The payroll officer will be limited to the companies and employees that they have security access to. 5. STP is only applicable to Australian payroll companies. i.e. companies assigned to other regions will be excluded from STP processing. Key Fields The 'As At Paid Date' is mandatory. Additional Processing Options There are several user options provided to specify what employees will be included in the 'Prepare STP Update Employee YTD for ATO’. 1. For a single employee – optional. Allows a single employee’s YTD amount details to be corrected with the ATO. 2. For a single Pay Group - optional. NOTE Leaving Pay Group blank allows the payroll officer to update employee YTD amounts across one or more companies regardless of Pay Group. 3. For one or more Companies (that the user has security access to) – mandatory, unless a single employee Id Number is specified. Taxation Supplier The user must select a Taxation Supplier if: 1. they wish to submit the STP Pay Events across multiple Companies under a single Intermediary ABN, or 2. they are providing Payroll services for their registered payroll companies. In this scenario, the payroll agent must have received a written Declaration from each Payroll Company that they service. NOTE If the payroll officer does not select a Taxation Supplier, but does have access to multiple payroll companies that they are authorised to pay and submit STP pay events, then each STP Pay Event will contain only a Declaration for the payroll ABN/Branch with the user’s details as the authorised representative. i.e. There will be no Intermediary Declaration details included in the STP pay event. Each company will be processed as if individually signed and declared by the same individual. Links to other Functions After preparing the STP Pay period data, the payroll officer will proceed to the next steps of reviewing the data (optional) prior to submitting the prepared Update STP to the ATO (via SBR2 infrastructure). • Review STP Update Employee YTD Report • Submit STP Update Employee YTD to ATO

Solution Implemented

The new function 'Update STP Employee YTD Amounts' updates the specified STP Data into the new STP reporting tables. The user can then choose to review the prepared STP update data, or submit the prepared STP update details to the ATO. Users navigate to this function directly from a payroll processing menu list.

HRPC-1242 - Single Touch Payroll for Australia - Prepare STP Pay Details (HRTAX300)

Functional Issue

Single Touch Payroll for Australia - Prepare STP Pay Details (HRTAX300)

Functional Verification

The new function, 'Prepare STP Pay Details', is the first step in transmitting Single Touch Payroll Pay Event details to the ATO. This process function loads the STP reporting tables with the STP data for the employee pays specified. The employee pays are determined by Pay Group and Pay Period End Date currently being finalised. i.e. been calculated and paid. Navigation links to this function are provided in the existing payroll calculation functions. i.e. Calculate Payroll by Group and Adjust Payroll for all payable Document Types, including Special, Back Pay, Bonus and Correction. After preparing the STP data, the user then submits the details to the ATO via SBR2 transmission supported by the product infrastructure (the Standard Business Reporting framework used by the ATO for STP). Refer to linked function 'Submit STP Pay Details to ATO'. Prerequisites: The customer must be registered with both ATO and TechnologyOne for STP before being able to make submissions to the ATO. I.e. The ATO will return with errors if a relationship between all parties is not detected in their systems. The employer is obligated to report pay details to the ATO via STP, on or before the scheduled Paid Date for every payment made to employees. i.e. the date the employees are to receive their pay in their bank accounts. This includes Correction, Special or Bonus pays that do not have a regular pay period or paid date. Only employee pay that has been successfully Paid will be included in STP reporting data. i.e. has both a Paid Date and Calculation Date. Only payable Document Type pays are included in STP reporting data. i.e. Accruals and Liabilities calculated pay items are not included The payroll officer will be limited to the companies and employees that they have security access to. STP is only applicable to Australian payroll companies. i.e. companies assigned to other regions will be excluded from STP processing. Key Fields The Pay Group and Pay Period End Date are mandatory. These fields are pre-loaded by the calling functions that calculate employee pay. For Example: Calculate Payroll by Group, Calculate Manual Back Pays by Group, Special Pay Run by Group, Adjust Payroll (by employee) Additional Processing Options Document Type - The user has the option to restrict the STP transmission by Document Type when navigating directly to this function. i.e. Not navigating via a payroll calculation function. Leaving the document type blank will allow all document types to be included in the STP pay data for the specified Pay Group and Pay Period End Date. Id Number - Will only be visible and pre-loaded if the user has navigated from a single employee pay calculation function. E.g. Adjust Payroll Taxation Supplier The user must select a Taxation Supplier if: • they wish to submit the STP Pay Events across multiple Companies under a single Intermediary ABN, or • they are providing Payroll services for their registered payroll companies. In this scenario, the payroll agent must have received a written Declaration from each Payroll Company that they service. NOTE If the payroll officer does not select a Taxation Supplier, but does have access to multiple payroll companies that they are authorised to pay and submit STP pay events, then each STP Pay Event will contain only a Declaration for the payroll ABN/Branch with the user’s details as the authorised representative. i.e. There will be no Intermediary Declaration details included in the STP pay event. Each company will be processed as if individually signed and declared by the same individual. Companies to Process: The Companies to Process list is loaded and visible if the user has navigated from one of the pay calculation functions. If the user has navigated from a single employee pay, the Companies section is not displayed. i.e. the employee's active job company is applied to the STP reporting details. If the user has navigated directly to this function, the Companies will load according to the Pay Group and Pay Period End Date specified. i.e. based on paid employee pay for that pay cycle. The user will only have selection of the companies that they are authorised to access. i.e. Refer to Security Category and its Organisation Management security access criteria. Links to other Functions After preparing the STP Pay period data, the payroll officer will proceed to the next steps of reviewing the data (optional) prior to submitting the prepared STP Pay details to the ATO (via SBR2 infrastructure). • Review STP Pay Details Report (XLOne report) • Submit STP Pay Details to ATO (HRTAX310)

Solution Implemented

The new function 'Prepare STP Pay Details' loads the specified STP Pay Period details into the new STP reporting tables. The user can then choose to review the prepared STP data, or submit the prepared STP pay details to the ATO. Refer to the new function link to 'Submit Pay Details to the ATO'. Users navigate to this function from links provided in the existing payroll calculation functions.

HRPC-1243 - Single Touch Payroll - Submit STP Pay Details function (HRTAX310)

Functional Issue

A new function for 'Submit STP Pay Details to ATO' enables the user to 'sign' and submit the pay details that were prepared in the prerequisite function, 'Prepare STP Pay Details for ATO'. Included in this function is the Declaration that the user must provide the ATO in submitted Pay events. i.e. an acknowledgement statement that the pay details are true and correct.

Functional Verification

1. Open the Adjust Payroll function and retrieve a paid employee pay where the employee works for an Australian company 2. Prepare the STP pay details by choosing the link to 'Prepare STP Pay Details for ATO' 3. Start processing, and confirm that the process succeeded in preparing the STP pay event. i.e. via 'Review STP Pay Details Report' or associated online Drag and Analyse queries for STP. 4. Choose the link to navigate to 'Submit STP Pay Details to ATO' 5. Confirm that the key fields are loaded for the submission. i.e. Id Number, Pay Period End Date 7. Complete the Declaration statement by choosing the applicable Taxation Supplier option and ticking the acknowledgement statement 7. Start processing 8. Confirm that the submission to the ATO succeeds with a Receipt Number from the ATO. 9. The 'Submit STP Pay Details' function is also accessible from 'Prepare STP Pay Details' when processed from: - Calculate Payroll by Group - Calculate Payroll by Group for Multiple Companies - Pay Calculation functions for all payable Document Types. e.g. Special Pay, Bonus Pay, Back Pay, Termination Pay NOTE 1. Response times for the ATO to complete the loading into their systems can vary up to several hours. 2. A polling process will continue to monitor submitted STP events and update the corresponding STP reporting records on the final response from the ATO. These include the STP reporting details as well as the STP Submission Status on each employee pay master record. 3. Final responses from the ATO will result in one of the Submission Statuses: - Success - Full Failure - entire pay event is rejected by the ATO - Partial Failure - one or more employee records failed to update at the ATO. However, Payer Gross and Tax Withholding for the pay periods have been updated at the ATO. 4. STP Events that have received a Full Failure can be (a) resubmitted to try again, or (b) re-prepared and submitted after fixing any data errors (as noted in messages from the ATO). 5. STP Events that have received a Partial Failure contain one or more employees whose YTD amounts have not been updated at the ATO. After fixing any data errors for the employee, these can be corrected (a) in the next Pay Period for the employee, or (b) via an 'Update Employee YTD Amounts'.

Solution Implemented

A new function for 'Submit STP Pay Details to ATO' (HRTAX310) enables the user to 'sign' and submit the pay details that were prepared in the 'Prepare STP Pay Details for ATO' (HRTAX300). NOTE The 'Submit STP' functions are only accessible when navigating from its corresponding 'STP Prepare' function.

HRPC-1261 - Payment to a deceased employee - manual calculation only supported

Functional Issue

The termination pay for a deceased employee should not be taxed or included in the Payment Summary.

Functional Verification

For processing the Termination payments due to a deceased employee: 1. Create the Termination record with a Termination Type that maps to the system standard code value for 'Death' 2. Navigate to Termination pay calculation 3. Run Calculate with the process tax option not selected. 4. Confirm that the pay is saved but has failed to calculate (i.e. no Calculation Date). 5. Confirm an error message explains that Termination payments cannot be made to a deceased employee. To proceed, follow the recommended pay process steps when making payments to the beneficiaries of deceased employees: 1. Prepare the deceased employee's Payment summary. NOTE Perform this prior to the calculation of Death payments that are unpaid and therefore to be paid to a beneficiary. i.e. dependent or trustee. 2. To calculate the outstanding entitlements due to the deceased employee, navigate to Special Pay. 3. For ETP payments, manually calculate the appropriate Lump Sum based on recipient. - ETP_DTH_D - Death Benefit Dependent (Code D) - ETP_DTH_N - Death Benefit Non Dependent (Code N) - ETP_DTH_T - Death Benefit Trustee (Code T) NOTE to receive tax free components, ensure that a tax free pay component code (type 600) exists for the Death Benefit ETP Lump Sum Payment codes D and T. (Dependent and Trustee). - ETP_DTH_D - Death Benefit Dependent (Code D), ETP_DTH_T - Death Benefit Trustee (Code T) both with Taxable checkbox not selected. 4. Based on this Special Pay, arrange for payment of the amount owing to be made to the dependent (or other recipient.) E.g. From Financials accounts payable. 5. As death termination payments are not applicable to the deceased employee, delete the Special Pay which has been created under their details. 6. Manually adjust the deceased employee's accrual balances to be shown as paid out (to the beneficiary). NOTE It is optional to prepare a manual Payment Summary for the dependent with their details (TFN, names, address etc) Under Single Touch Payroll, Death termination payments are an optional inclusion. As the STP details must be relating to the beneficiary, Death Termination Payments will currently be excluded from STP reporting.

Solution Implemented

Termination Pay calculation has been modified to check for the Termination Type of the employee. If that Termination Type is mapped to a cause of 'Death', the termination pay will save without a Calculation Date. This prevents death termination payments from (a) being paid to the deceased employee and (b) being included in Payment Summaries and Single Touch Payroll reporting.

HRPC-1389 - Single Touch Payroll - Submit STP Update Employee YTD to ATO function (HRTAX380)

Functional Issue

A new function for 'Submit STP Update Employee YTD to ATO' enables the user to 'sign' and submit the pay details that were prepared in the prerequisite function, 'Prepare STP Update Employee YTD for ATO'. Included in this function is the Declaration that the user must provide the ATO in submitted Pay events. i.e. an acknowledgement statement that the employee YTD details are true and correct. A new function for 'Submit STP EOFY Employee Finalisation to ATO' enables the user to 'sign' and submit the pay details that were prepared in the prerequisite function, 'Prepare STP EOFY Employee Finalisation for ATO'

Functional Verification

For payroll officers of Australian companies who wish to update Single Touch Payroll employee YTD amounts with the ATO: 1. Navigate to the new function for 'Prepare STP Update Employee YTD for ATO' (or 'Prepare STP EOFY Employee Finalisation for ATO') 2. Select the Pay Group, Company(ies) or single employee who will have YTD amounts recalculated 3. Specify the 'As At Paid Date' that will determine the employee pays included in the YTD calculations. i.e. all paid employee pay for the Financial year up to and including the As At Paid Date. E.g. Today's date would commonly be the date for which you wish to update employee YTD amounts. NOTE - 'As At Paid Date' cannot be prior to 1 July 2017 - 'As At Paid Date' cannot be later than today's date - Submit all outstanding STP reporting for employee pays that have been paid prior to attempting to Update YTD amounts - YTD amounts will be recalculated in the next STP Pay event for employee pays, and will replace the YTD amounts submitted for an earlier date. 4. Start processing, and confirm that the process succeeds in preparing the STP details i.e. via 'Review STP Update Employee YTD Report' or associated online Drag and Analyse queries for STP 5. Using the links, navigate to the 'Submit STP Update Employee YTD to ATO' function 6. Confirm that the key fields are loaded for the submission. i.e. Id Number, As At Paid Date 7. Complete the Declaration statement by choosing the applicable Taxation Supplier option and ticking the acknowledgement statement 8. Start processing 9. Confirm that the submission to the ATO succeeds with a Receipt Number from the ATO. NOTE 1. Response times for the ATO to complete the loading into their systems can vary up to several hours. 2. A polling process will continue to monitor submitted STP events and update the corresponding STP reporting records on the final response from the ATO. These include the STP reporting details as well as the STP Submission Status on each employee pay master record. 3. Final responses from the ATO will result in one of the Submission Statuses: - Success - Full Failure - entire STP Update event is rejected by the ATO - Partial Failure - one or more employee records failed to update at the ATO. 4. STP Events that have received a Full Failure can be (a) resubmitted to try again, or (b) re-prepared and submitted after fixing any data errors (as noted in messages from the ATO). 5. STP Events that have received a Partial Failure contain one or more employees whose YTD amounts have not been updated at the ATO. After fixing any data errors for the employee, these can be corrected (a) in the next Pay Period for the employee, or (b) via an 'STP Update Employee YTD'.

Solution Implemented

A new function for 'Submit STP Update Employee YTD to ATO' (HRTAX380) enables the user to 'sign' and submit the employee YTD details that were prepared in the 'Prepare STP Update Employee YTD for ATO' function (HRTAX350). A new function for 'Submit STP EOFY Employee Finalisation to ATO' (HRTAX380) enables the user to 'sign' and submit the employee YTD details that were prepared in the 'Prepare STP EOFY Employee Finalisation for ATO' function (HRTAX350). NOTE The 'Submit STP' functions are only accessible when navigating from its corresponding 'STP Prepare' function.

HRPC-1445 - KS1 KED File includes 'Opt Out' data for ALL companies

Functional Issue

The IRD electronic reporting for KiwiSaver KED can incorrectly include other company details for Opt Out.

Functional Verification

1. For NZ employees across several companies, ensure that there are employees with both Opt In and Opt Out updated details for KiwiSaver that require transmitting. 2. Process the IRD electronic reporting 'Kiwisaver Employment Details' for the current month for only one of the companies 3. Confirm that the KED file and log does not include the employees from other companies (not selected). i.e. those who had 'Opt Out'

Solution Implemented

The IRD KED process has been updated to ensure all details loaded into the file are restricted to the company specified.

HRPC-1522 - PAYG Payment Summary - FBT not strictly based on paid FBT year 1 Apr - 31 Mar

Functional Issue

The FBT calculation in PAYG payment summary preparation does not apply the FBT financial year End Date of 31 March correctly. Currently FBT amounts dated 1 April - 30 June can be included in the current financial year's PAYG Payment Summary.

Functional Verification

1. For an employee who has FBT amounts paid between 1 April and 30 June of the current financial year 2. Produce the PAYG Payment Summary for the employee for the current financial year 3. Confirm that only FBT payments from 1 April - 31 March are included in the PAYG Payment Summary.

Solution Implemented

The PAYG Payment Summary process for Fringe Benefit amounts has been corrected to only include the FBT amounts paid between 1 April and 31 March of the financial year.

HRPC-1557 - Single Touch Payroll - Submit issue with multiple Paid Dates and non-blank Status

Functional Issue

All failed submissions may not be re-submitted when a single Company has multiple Paid Dates within a single Pay Period End Date.

Functional Verification

1. Run Prepare STP Pay detail for a company with several paid dates in a single Pay Period End Date. E.g. one or more employees are paid on an earlier Paid Date than the Pay Group 2. Ensure there are multiple Submission Ids generated - one per Paid Date 3. Submit the STP details to ATO 4. In the event that the submission process results in a status of 'Full Failure' (or 'Awaiting Receipt' for an extended period) 5. Re-submit the STP submissions (for the Pay Period End Date and Company as per step 1) 6. Confirm that ALL Submission Ids are re-processed. NOTE There are information messages indicating that the previous Full Failure submissions will be re-submitted. Also there will be any messages returned from ATO explaining the Full Failure.

Solution Implemented

Updated the Single Touch Payroll submission process to ensure all Submission Ids are re-submitted if they have previously resulted in a Full Failure. i.e. for a single company which has multiple Paid Dates within the one Pay Period End Date

HRPC-1560 - Manual back pays incorrectly reset the Pay Master Pay Period Start Date to the employee's Date Hired

Functional Issue

When calculating Manual Back Pay by Group, the Pay Master value of Pay Period Start Date is defaulted to the employee's Hired Date instead of the specified back pay period start date.

Functional Verification

1. Run Calculate Manual Back Pay for an employee 2. Confirm that the manual back pay is calculated correctly 3. Use the Pay Transactions data analyser to confirm that the Pay Period Start Date is correct for the back pay's Pay Period End Date. NOTE as back pays are not regular pay periods, the Pay Period Start Date will be based on the employee's Pay Group and the entered back pay Pay Period End Date.

Solution Implemented

Updated the Calculate Manual Back Pay processing to ensure that the back pay value for Pay Period Start Date is maintained and not defaulted to the employee's Date Hired.

HRPC-1563 - Single Touch Payroll - Validate TFN if not a Contractor with ABN

Functional Issue

Payroll employees (INB) with negative or zero YTDs are included in STP events and therefore should have their TFN validated and defaulted as required. Voluntary Agreement contractor employees only require an ABN. TFN is optional for these employees.

Functional Verification

For an INB payroll employee: 1. Who has not provided a Tax File Number 2. Process and bank download the next pay for the employee 3. Run the Prepare STP pay detail for the employee 4. Confirm that a warning message is returned indicating that the employee is using a defaulted generic Tax File Number (000 000 000) for the purpose of STP. For a Voluntary Agreement Contractor 1. Who has not provided a Tax File Number, but has provided a contractor ABN 2. Process and bank download the next pay for the contractor 3. Run the Prepare STP pay detail for the contractor 4. Confirm that no warning is returned indicating the contractor is using generic Tax File Number. i.e. No TFN is defaulted for a Voluntary Agreement Contractor

Solution Implemented

The STP Prepare process has been updated to ensure that an employee's Tax File Number is defaulted when not provided by the employee, regardless of their YTD amount values in the STP event.

HRPC-1572 - Single Touch Payroll - direct access to STP Prepare Pay Details

Functional Issue

The key values from from the 'Prepare STP Pay Details for ATO' function are not synced to 'Submit STP Pay Detail to ATO'. This only occurs when the 'Prepare STP' for ATO' function is accessed directly.

Functional Verification

1. Open the 'Prepare STP Pay Detail for ATO' function directly 2. Fill all of the key fields 3. Navigate to the 'Submit STP Pay Details to ATO' by clicking the link in the 'Links to other Functions' panel 4. Confirm that the key fields values are synced to the 'Submit STP Pay Details to ATO' function.

Solution Implemented

The 'Prepare STP Pay Details for ATO' function has been modified to work correctly when access directly (i.e. not via links from Payroll calculation functions). This ensures the correct syncing of the processing criteria values to 'Submit STP Pay Details to ATO' function.

HRPC-1575 - Single Touch Payroll - Manual Back Pay HRPAY510 links to STP and Bank Download

Functional Issue

Manual Back Pay by Group (HRPAY510) does not have links to Bank Download and Transmit STP functions

Functional Verification

1. Navigate to Manual Back Pay by Group 2. Complete the back pay criteria for an Australian company 3. Ensure both "Bank Download" and "Transmit STP Pay Details to ATO" links are visible in 'Links to Other Function' section 4. Calculate the back pay for one or more employees meeting the criteria 5. Navigate to Bank Download function by clicking the link Confirm that the Paid Date is synced to the Bank Download. As per 'Calculate Pay by Group' the bank download will only apply to the selected employees. Confirm the 'Update All Calculated as Paid' option is checked on by default. This ensures that zero and negative pays are completed with a Paid Date (although not included in the bank file). 6. Process Bank Download. Confirm that the selected employees back pays are showing as paid with a Paid Date. 7. Navigate to Transmit STP Pay Details to ATO by clicking the link Confirm that the back pay criteria is synced to the STP 8. Process the STP preparation Confirm that the prepared STP submission details are generated for the employee back pays.

Solution Implemented

Added "Bank Download" and "Transmit STP Pay Details to ATO" links in the Calculate Manual back pays by Group function.

HRPC-1577 - Single Touch Payroll - Incorrect Message when a future 'As At Paid Date' is entered for Update events

Functional Issue

'Prepare STP EOFY Employee Finalisation for ATO' function returns an incorrect error message when a future date is entered the 'As At Paid Date' field and there are no employee pays at that future date.

Functional Verification

1. Navigate to function 'Prepare STP EOFY Employee Finalisation for ATO' (or 'Prepare STP Update Employee YTD for ATO') 2. Enter a future date in 'As At Paid Date' field. Ensure that the future date is set to a date where there are no employee pays as yet. E.g. 30 June 2020 3. Confirm that an error message is returned stating "As At Paid Date for a STP Update cannot be later than today's date". Additionally, there are no Companies to process in the grid.

Solution Implemented

Corrected the STP update event validation to ensure the correct error message appears when a future date is specified in 'As At Paid Date'.

HRPC-1580 - Single Touch Payroll - In 'Prepare STP Pay Details' allow Document Type to be modifiable

Functional Issue

The Document Type field in function 'Prepare STP Pay Details' is defaulted and disabled when opened from a Pay Calculation function. This field should be modifiable to allow the user to include other document types in the STP Pay (period) event. E.g. Clear the Document Type fields to include any Terminations, or Corrections that are dated for the same Pay Period End Date.

Functional Verification

1. Navigate to the Adjust Payroll function 2. Load an employee pay ready for STP submission. i.e. is Paid 3. Navigate to 'Transmit STP Pay Details to ATO' 4. Confirm that Document Type field is loaded with the document type from previous function and is modifiable 5. Clear the Document Type field to enable all other pay types on the same Pay Period End Date to be included for the employee. E.g. To include Termination or Correction Pays of the same PPED 6. Confirm that the amounts relating to all document types for the employee are included in the STP values - for Pay Period Gross and Tax Withholding amounts.

Solution Implemented

The STP Prepare Pay Details function has been updated to allow the Document Type field to be modifiable when navigated to from payroll functions.

HRPC-1582 - Single Touch Payroll - Errors on Company ABN longer than 11 char

Functional Issue

The 'Prepare STP' function returns an error when the company is using an ABN longer than 11 characters

Functional Verification

1. In the Company Maintenance, set the ABN value to be more than 11 characters. e.g. insert spaces 2. Run the 'Prepare STP Pay' function for an employee who has been paid by the company 3. Confirm that the Company ABN is truncated to 11 chars with spaces removed. A warning is returned informing the user that the ABN value has been truncated.

Solution Implemented

The STP preparation process has been modified to remove spaces and truncate the Company ABN to 11 characters.

HRPC-1583 - Single Touch Payroll - Submit message when event is already at SUCCESS

Functional Issue

Functions for 'Submit STP' do not display any message indicating the previous submission was already successful.

Functional Verification

1. Navigate to Submit STP function from a pay that was previously submitted and finalised with a 'SUCCESS' status 2. Run the Submit process 3. Ensure that an information message appears indicating the submission process is successful.

Solution Implemented

Updated the Submit Single Touch Payroll function to display an information message when the previous submission received a response of 'Success'

HRPC-1586 - Single Touch Payroll - ReSubmit does not remove the previous STP message records

Functional Issue

When a STP event is re-submitted, the messages from its previously failed submission are not deleted. This causes multiple and obsolete ATO messages to exist for the same Submission Id.

Functional Verification

1. In the case of a STP event that received a 'FULL FAILURE' status. 2. Confirm the messages returned from the ATO for the Submission Id have been saved. i.e via the Data Analyser for 'STP Event Message Response'. 3. Re-submit the STP Submission 4. Confirm only messages for the last re-submission attempt exist for the Submission Id. i.e via the Data Analyser for 'STP Event Message Response'.

Solution Implemented

The STP submit and prepare processes have been corrected to remove previous submission messages when the user re-submits or re-prepares STP events that have failed.

HRPC-1620 - Paid Date - Expected Paid Date payroll calculation parameter missed from serialisation

Functional Issue

The Expected Paid Date field is missing from the process that is responsible for serialising the payroll calculation parameters. In the event of a failed DP payroll job which restarts automatically, this can result in a default Expected Paid Date being used by the payroll calculation and noted in the payroll calculation log. E.g. "Expected Paid Date not provided. Defaulting to Pay Period End Date: 24-Aug-2018."

Functional Verification

1. Navigate to function 'Calculate Payroll by Group' 2. Complete the calculation parameters for the pay run. Taking note of the entered value for Expected Paid Date, which in this test case is different to the Pay Period End Date 3. Submit the process to the DP 4. On completion of the payroll calculation, review the payroll calculation log 5. Confirm that the 'Expected Paid Date' is the same value as entered for the requested payroll process. i.e. A message does not appear in the log which states that "Expected Paid Date not provided. Default to Pay Period End Date".

Solution Implemented

The calculation parameter 'ExpectedPaidDate' has been added to the serialisation of the payroll calculation parameters.

HRPC-1625 - Single Touch Payroll - Update event incorrectly finding companies earlier than Financial Year of 'As At Paid Date'

Functional Issue

STP Update events (YTD and EOFY) are incorrectly loading the company Paid Date details to process with all those that have pays prior to the Financial Year of the entered 'As At Paid Date'. i.e. the Companies to process should only include those with paid employees within the financial year being reported. 1 July up to and including 'As At Paid Date'.

Functional Verification

Applicable only if there are more than one Australian payroll companies to report STP. 1. Navigate to the 'Prepare STP Update Employee YTD for ATO' function 2. Enter a value for 'As At Paid Date'. E.g. a paid date early in the current financial year - 4/07/2018. 3. Confirm that the Companies to Process list only includes those that have paid employees within the Financial Year up to and including the 'As At Paid Date'. i.e. Paid employees with Paid Date between 1/07/2018 and 4/07/2018. 4. Leave the Companies to Process as the selection for All - 'Process All Companies' 4. Start Processing 5. Confirm that only the companies loaded to the grid are processed (check in the log), and that no errors occur attempting to retrieve the list of companies.

Solution Implemented

The STP update YTD and EOFY process has been corrected to restrict the list of companies based on the Financial Year of the selected 'As At Paid Date'.

HRPC-1642 - Single Touch Payroll - Shipped system data for functions and reports

Functional Issue

Single Touch Payroll system data for functions and reports is not shipped in the early release.

Functional Verification

1. As System Administrator, ensure that any previous custom changes for STP functions, reports and data analysers are deleted. 2. As Payroll Officer 3. Navigate to Drag and Analyse 4. Confirm that all the STP data analysers appear (under Payroll) 5. Navigate to Correction Pay for an employee 6. For a Paid correction pay, confirm that the STP link appears - 'Transmit STP Pay Details to ATO' 7. Select the STP link and run the Report 8. Confirm that the STP Pay Details report is found and generated 9. Navigate to 'STP Update Employee YTD' by using Search 10. Enter today's date 11. Click on the report link and confirm the report is found and criteria presented.

Solution Implemented

Single Touch Payroll shipped data for Payroll Officers has been updated for: 1. STP report functions and default access 2. Payroll calculation functions - have the STP Pay Details report function specified. E.g. Includes Adjust Payroll, Calculate by Groups and all payable Document Type functions (Termination, Special, Bonus, Correction, Miscellaneous) 3. Payroll Data Analysers - all STP data analyser selections are turned on by default.

RELEASE November 2017

HRPC-109 - Issues running Pay Calculation Report - Invalid Printer

HRPC-182 - Australia Termination - Update Long Service Leave payout process by the ATO

HRPC-529 - New Zealand leave calculators error after transfer to new company.

HRPC-610 - Leave booked and approved before secondment would not be paid at the higher-duties payroll rate.

HRPC-625 - 'Transmitted' spelling error in Kiwisaver Membership Details

HRPC-660 - NZ IRD processes not including pay when employee transfers to non-NZ company

HRPC-674 - System paying public holidays outside of pay period when employee moved from casual to part time

HRPC-690 - Termination Pay is not displayed when an employee rehired date is prior to the Termination Pay PPED.

HRPC-708 - Bank Download - Paid Date enhancements

HRPC-710 - Payroll Reports - Paid Date enhancement

HRPC-711 - Payroll Enquiry - add Paid Date to search criteria

HRPC-712 - Payroll Calculations based on Paid Date

HRPC-713 - Pay Calculation options - new Expected Paid Date field for YTD and calculation thresholds

HRPC-714 - New function 'Update Paid Date'

HRPC-722 - ATO TFN Declaration electronic reporting changes effective 1/10/2017

HRPC-737 - Period Leave taken on Payslip differs from actual leave taken in that pay period

HRPC-773 - EFT report not always showing Paid Date from the Correction pay master

HRPC-802 - Paid Date - Corrective access and Pay Calculation improved validation

HRPC-805 - Data Analyser only includes the latest PAYG Payment summary for employees who have worked for more than one company in a single financial year.

HRPC-810 - Payroll Calculation Log does not identify employee when an Application Error occurs

HRPC-814 - Default Control Var for ATO thresholds to be moved to Effective Dated Other Tax Scales

HRPC-819 - The Payment Summary Listing Report ($HR.TAX.PAYGLST.RPT) is missing the Exempt Fringe Benefits field

HRPC-847 - SBR Payment Summary error - max DB connections exceeded with 725 employees

HRPC-849 - Pay as you go withholding (PAYGW) payment summary annual report (PSAR) specification v13.0.0

HRPC-859 - Paid Date - Payroll Import update

HRPC-863 - [Bank Download Format] Format TDB Bank File

HRPC-869 - Australian ABA bank download file requires BSB and account in the header when the employer has multiple accounts.

HRPC-879 - Error on Leave Cancel when reducing accruals only (not paying leave taken)

HRPC-886 - Timesheet Only employee's leave taken hours recalculate to standard work day units on recalculation of a manually adjusted pay

HRPC-914 - Employee transfer to another company - Payroll Enquiry not resolving amounts correctly

HRPC-921 - EMS File(s) are created with the same filename when processing multiple companies

HRPC-950 - TSL is not included in the Payment Summary's Total Tax Amount

HRPC-966 - Data Management task for Paid Date enhancements

HRPC-974 - SBR TFN transmission failed but the TFN transmission marked as successful

HRPC-977 - Error message on Deduction Payee ledger/account validation needs to be improved when an application error occurs.

HRPC-983 - Base pay reversals were not being processed for retrospective leave booked in Ci Anywhere.

HRPC-989 - Payroll Enquiry - Employee Name Reversed

HRPC-1007 - PAYG Payment Summary - Paid Date by default

HRPC-1037 - SBR Payment Summary Taxonomy load error for on-premise installations

HRPC-1051 - TFN Dec SBR transmission errors - only 1 payee can be transmitted at a time

HRPC-1053 - Australian Tax Scale Codes are not descriptive

HRPC-1056 - Manual Back Pay incorrectly shows a pay as 'Posted' when it is not

HRPC-1083 - Manual Back Pay - Load Search for employees results in exception RTE

HRPC-1111 - ETP maximum witholding rate should be at 47% effective 1 July 2017

HRPC-1195 - Payroll Enquiry Poor performance in 2018A

HRPC-1196 - New Zealand IRD Payroll Legislation changes 1 Apr 2018

HRPC-1220 - Timesheet Adjustments from previous periods not resolving pay rate in pay calc

HRPC-1278 - NZ Electronic deduction Form (IR345) File name default

HRPC-1284 - Error when downloading Bank Download file

HRPC-1309 - New Report required for Pay Components by Pay Location with the criteria using Paid date

HRPC-1340 - New Zealand pay calculation completes with $0.01 out of balance error

HRPC-1370 - TFN Declaration SBR TFND.0003 2016 required for 30 June 2018 ATO Legislative Changes

HRPC-1409 - Aust ATO Payroll Legislative changes effective 01/07/2018

HRPC-1477 - EPSC Rates effective 1 July 2018 are incorrect

HRPC-109 - Issues running Pay Calculation Report - Invalid Printer

Functional Issue

The Pay Calculation report, Pay Summary report and new Pay Advice reports have been designed using Microsoft XPS Document Writer as the default printer. Printing this report gives following error for customers who do not have Microsoft XPS Document Writer installed OR not setup as their default printer. "Unable to generate the report: Invalid printer specified."

Functional Verification

1. Create an employee's Pay Advice for Australia 2. Choose the Print option (where a local or default printer has been defined) 3. Confirm that the Pay Advice prints without error (i.e. XPS Document Writer not installed). Where applicable, run the above tests for the following crystal reports: 1. Pay Advice AU 2. Pay Advice AU Multi Company 3. Pay Advice AU No Pro-rata 4. Pay Advice AU Multi Company No Pro-rata 5. Pay Advice NZ 6. Pay Advice NZ Multi Company 7. Pay Advice NZ No Pro-rata 8. Pay Advice NZ Multi Company No Pro-rata 9. EFT Payment report.

Solution Implemented

Changed the default printer for the following reports to be 'Print to PDF' instead of 'Microsoft XPS Writer': 1. Pay Advice AU 2. Pay Advice AU Multi Company 3. Pay Advice AU No Pro-rata 4. Pay Advice AU Multi Company No Pro-rata 5. Pay Advice NZ 6. Pay Advice NZ Multi Company 7. Pay Advice NZ No Pro-rata 8. Pay Advice NZ Multi Company No Pro-rata 9. EFT Payment report.

HRPC-182 - Australia Termination - Update Long Service Leave payout process by the ATO

Functional Issue

The process for calculating Australian termination long service leave has been updated by the ATO. The leave accrued and taken is separated into the three applicable components based on the different withholding rates which have changed over time. NOTE For details of the ATO termination Long Service leave calculation steps see the ATO website on 'Withholding from unused leave payments on termination of employment'

Functional Verification

1. For an Australian employee hired before the 16 August 1978 2. Ensure long service leave is assigned to the employee 3. Ensure some long service leave is taken during the employment period 4. Termination the employee, by first creating a termination activity for the employee 5. Calculate the termination pay 6. Review the calculation audit and confirm the post-17 August 1993 component is calculated correctly, including reducing the accrued leave for leave taken if applicable 7. Confirm the pre-18 August 1993 component is calculated correctly, including reducing the accrued leave for leave taken if applicable 8. Confirm the pre-16 August 1978 component is calculated correctly, including reducing the accrued leave for leave taken if applicable. 9. Review the long service leave items generated and confirm their generated for the correct amount per the calculation audit 10. Review the calculation audit tax calculation section after the termination leave and confirm the marginal tax is calculated correctly 11. Review the termination lump sum A taxation item and confirm it is for the correct amount per the calculation audit 12. Review the termination taxation item and confirm it is for the correct amount per the termination tax calculation audit. NOTE For details of the ATO termination Long Service leave calculation steps see the ATO website on 'Withholding from unused leave payments on termination of employment'

Solution Implemented

Changed the Australian termination process for long service leave to comply with the latest ATO instructions.

HRPC-529 - New Zealand leave calculators error after transfer to new company.

Functional Issue

New Zealand leave calculators can error when an employee is transferred to a new company or an employee is hired in a new company. The error indicates that a pay period could not be retrieved for a date that is before the employee's hire/re-hire date.

Functional Verification

1. For a new pay group for a New Zealand company 2. Define the first pay period for the pay group as at the beginning of the current month 3. Terminate an existing employee as at the end of the previous month 4. Rehire the employee as at the beginning of the current month, assign the new pay group to the employee's job details 5. Calculate the first ordinary pay period for the employee 6. Load the second pay period of the month 7. Create an leave day during the second pay period, the leave pay component rate should be calculated by the $HRPCM_AC_AL amount calculation script 8. Calculate the pay period 9. Confirm the pay calculation completes without any errors displayed 10. Confirm the leave pay item rate is calculated as expected 11. Review the pays' calculation audit where the leave rate calculation details are provided 12. Confirm the average weekly earnings (AWE) calculation dates has a period start date of the employee's rehire date 13. Confirm the ordinary weekly pay (OWP) calculation dates has a period start date of the employee's rehire date 14. Calculate the pay periods for the remainder of the month 15. Create and calculate another leave day in the following month 16. Confirm the AWE calculation dates have a period start date of the employee's rehire date 17. Confirm the OWP calculation dates have a period start date that is four weeks before the end of the previous pay period.

Solution Implemented

Amended the New Zealand leave amount calculators that lookup pay period dates to ensure the lookup does not occur before an employee's current hire date. The following amount calculator scripts were updated: $HRPCM_AC_AWE $HRPCM_AC_OWP $HRPCM_AC_ADP $HRPCM_AC_RDP $HRPCM_AC_T15

HRPC-610 - Leave booked and approved before secondment would not be paid at the higher-duties payroll rate.

Functional Issue

Leave booked and approved before secondment would not be paid at the higher-duties payroll rate. This occurred when the position from which leave was taken was still "effective" (i.e., in the employee's active job details) but not "active" (i.e., it had been superseded by an acting position).

Functional Verification

1. As an employee, logon to self service and submit a request for future dated leave in the primary position 2. As the employee's manager, approve the request for future dated leave 3. Verify the leave is being taken from the employee's (currently active) primary position 4. As a payroll officer, change the employee's job details such that they commence work in an acting position as at the leave start date 5. Navigate to the Adjust Payroll function and process the pay containing the booked and approved leave 6. Verify leave is paid out using the employee's new active position which is the acting position (i.e. paying higher duty rates).

Solution Implemented

Payroll processing has been corrected to check positions referenced by leave timesheet lines/entries, and where the position is not active, the leave pay item will be generated using the employee's active position details. i.e. Acting or Primary position.

HRPC-625 - 'Transmitted' spelling error in Kiwisaver Membership Details

Functional Issue

The employee maintenance Kiwisaver Membership section has a spelling error within the label for the Transmitted to IRD indicator.

Functional Verification

1. Log into the Payroll Officer workplace. 2. Select the Maintain Employee tab. 3. Load the details for a New Zealand employee. 4. Review the Transmitted to IRD indicator within the Kiwisaver Membership section. 5. Confirm the spelling is correct.

Solution Implemented

Corrected the spelling error on the New Zealand employee maintenance field Transmitted to IRD.

HRPC-660 - NZ IRD processes not including pay when employee transfers to non-NZ company

Functional Issue

The New Zealand IRD Electronic Deduction Form (IR 345) and Employer Monthly Schedule (IR 348) processes were not reporting the total earnings and PAYE components correctly when an employee transferred from an $NZ region company to a non $NZ region company during the month. Additionally, if the termination pay was paid in the month after the transfer from the $NZ region company, the pay was not included within the IR 345 or IR 348.

Functional Verification

1. Create a termination activity mid way through a month for a New Zealand employee 2. Calculate the termination pay for the employee 3. Confirm the termination pay has generated pay items as expected and bank download the pay 4. Rehire the employee within the same month with a company that is not based in the $NZ region 5. Calculate ordinary pay period(s) to the end of the month and bank download each pay with a Paid Date within the month 6. Process the Employer Monthly Schedule (IR 348) for the month 7. Review the detail record for the terminated and re-hired employee 8. Confirm the Gross earnings and PAYE field totals include the New Zealand pays for the month only, including the termination pay 9. Confirm the IR 348 header totals are correct and do not include the paid pay periods after the employee has transferred from the New Zealand 10. Confirm the Electronic Deduction Form (IR 345) totals are correct and do not include the paid pay periods after the employee has transferred from New Zealand.

Solution Implemented

Amended the New Zealand IRD IR 348 and IR 345 processes to ensure the paid gross earnings and PAYE components are reported for the New Zealand company being reported only.

HRPC-674 - System paying public holidays outside of pay period when employee moved from casual to part time

Functional Issue

When an employee has a mid-pay period job change of Holiday Category from/to one which does not support Public Holidays, an error can occur in pay calculation. This occurs as the generation of Public Holiday leave records for the entire pay period is based on the Job record (and Holiday Category) that is effective as at the Pay Period End Date. i.e. Rather than applying the Holiday Category to the 'pay spans' caused by a change in job details.

Functional Verification

1. For an existing or test employee, create a mid-pay period job change of Holiday Category such that one does not pay Public Holidays. E.g. changing to a casual or part time employee 2. Ensure there a public holiday occurs within the pay period but which falls under the job Holiday Category that does not pay public holidays 3. Calculate the pay 4. Confirm that no public holiday is generated and the pay calculates correctly.

Solution Implemented

The public holiday generation in the pay calculation has been changed to handle mid-period job changes. Therefore the Holiday Category of each job occurring in a pay period is applied based for the dates the job is effective within the pay period (i.e. individual 'pay spans').

HRPC-690 - Termination Pay is not displayed when an employee rehired date is prior to the Termination Pay PPED.

Functional Issue

The Process Termination Pay for Employee function does not display a calculated termination pay when the pay's period end date is after the termination date and the employee is rehired in a different company effective from a date that is before the termination pay's period end date. i.e. The payment of the Termination (i.e. Pay Period End Date) occurs after the actual Termination Date (which occurs prior to the rehire).

Functional Verification

1. Terminate a New Zealand employee by creating a termination activity 2. Calculate the termination pay with a period end date of 1 week after the termination date 3. Review the termination pay and confirm it has calculated as expected. NOTE: If the ordinary pay period cycle has completed between the termination date and the termination pay period end date the termination pay will not generate the ordinary pays' entitlements when Load Entitlements is selected. 4. Bank Download the pay and generate a pay advice 5. Rehire the employee as an Australian employee with an effective date that is the first work day after the termination date and before the termination pay period end date 6. Reload the termination pay 7. Confirm the pay is displayed 8. Confirm the messages include a warning that "The termination pay relates to a previous work period and the pay can not be re-calculated." 9. Confirm no Actions to Perform are displayed if corrective access is not enabled, as the pay has been paid 10. Enable corrective access for Payroll Processing 11. Reload the termination and confirm the Actions to Perform include the Delete action 12. Complete the New Zealand payroll posting for the termination pay period end date 13. Confirm the termination pay is posted. NOTE: In this scenario, the pay can not be bank downloaded and a pay advice can not be generated once the new employment period is created.

Solution Implemented

Amended the pay retrieval process to allow a termination pay to be displayed when the employee is rehired with an effective date that is before the termination pay period end date.

HRPC-708 - Bank Download - Paid Date enhancements

Functional Issue

The Bank Download functionality has been enhanced for Paid Date processing by: 1. Clarify the 'Process Date' field which is used as 'Paid Date'. 2. Ensure that payroll officers consciously set an accurate 'Paid Date' by not defaulting this field. 3. Enable zero and negative pays to be marked as 'Paid' (with Paid Date) if they have been successfully Calculated (i.e. have Calculated Date and balanced). i.e. This includes pays of the same selected pay period and document type that are fully salary sacrificed pay (zero nett amounts) or negative nett pays (i.e. usually a Correction pay).

Functional Verification

1. As Payroll Officer, Open the 'Bank Download' Function 2. Confirm that the new option to 'Update All Calculated as Paid' is available. Check this option 3. Select the pay period(s) and pay document types to be downloaded for payment. E.g. Payroll, Correction for a specific pay period end date. 4. Confirm that the 'Paid Date' field is blank and a value is mandatory for processing NOTE a. When navigating to 'Bank Download' from Adjust Pay or Calculate Payroll by Group, the Paid Date will be defaulted to the 'Expected Paid Date' used in the pay calculation that has just been processed. b. Varying the 'Paid Date' from the 'Expected Paid Date' will result in a warning message advising that a re-calculation may be needed. 5. Enter a valid 'Paid Date' value. E.g. in 2 days time when the employee funds are expected to clear in their accounts 6. Ensure that there are also zero or negative nett employee pay included in the pay period being downloaded. i.e. fully salary sacrificed or a correction pay NOTE a. Only employee pays with a 'Calculated Date' can be marked as Paid. i.e. pays are calculated and balanced with a zero or negative nett amount. b. These pays will not be included in the download period grid - employee count nor total $ amount. Only the employees that will actually be paid and included in the bank download file are included in the summary details shown in the grid. 7. Start processing 8. Confirm that only employees with a positive Nett Amount in the selected pays are included in the bank download file 9. Confirm that the zero or negative nett pays have been updated with the specified 'Paid Date'. E.g. from Adjust Payroll function or Pay Transactions data analyser. 10. If applicable, open 'Bank Download for Multiple Companies, and repeat steps 2-9. Function Parameter: 1. Open the Function Maintenance for Bank Download function 2. Confirm that 'Update All Calculated As Paid Default As Checked' option is available 3. Save this option into a customised version of the function if you require it on by default. i.e. mark calculated pays as 'Paid' regardless of nett amount.

Solution Implemented

The Bank Download functionality has been enhanced for Paid Date processing by: 1. The existing 'Process Date' field has been changed to reflect is usage as 'Paid Date'. This mandatory field is no longer defaulted to the current date, therefore the payroll officer must specify the actual paid date to the employees (i.e. when funds are expected to be received by employees). 2. A new processing option has been added labelled 'Update All Calculated as Paid'. This ensures that all Calculated employee pay within the specified pay period is marked as 'Paid' with a 'Paid Date'. This includes fully salary sacrificed pay (zero nett amounts) and negative calculated corrections (negative nett amounts) 3. A new function parameter allows the default setting of the new field 'Update All Calculated as Paid' for the Bank Download function. 4. All Bank Download scripts have been corrected to include last_mod auditing fields in the update of paid_date on HRPAY_MASTER_CTL. NOTE Zero or negative pays that have not been included in the regular employee pay cycle (and include pays which have positive nett pay), will not be visible for selection in the bank download grid. i.e. no bank download file is outstanding for those pays as there is no payment due. These pays can be marked as 'Paid' from either the Adjust Payroll function link to Bank Download (per employee pay) or the new 'Update Paid Date' function.

HRPC-710 - Payroll Reports - Paid Date enhancement

Functional Issue

Pay Calculation and Summary reports that specify criteria for 'Report Start Date' and 'Report End Date' should clarify that these dates refer to the 'Pay Period Start Date' and 'Pay Period End Date'.

Functional Verification

1. Open the Pay Calculation or the Pay Summary report 2. Confirm the main criteria fields for the date range are labelled 'Pay Period Start Date' and 'Pay Period End Date' 3. Fill mandatory criteria and start processing the report 4. Confirm that the results of the report are correct for the criteria selected.

Solution Implemented

The 'Report Start Date' and 'Report End Date' labels in the payroll reports have been changed to 'Pay Period Start Date' and 'Pay Period End Date'. This impacts the following reports: - Account Amounts - Deduction Summary - Overtime Hours - Pay Calculation Report - Pay Calculation Report (Inc. Historical Data) - Pay Calculation Report across Multiple Companies - Pay Summary Report - Pay Summary Report (Inc. Historical Data) - Pay Summary Report across Multiple Companies - Payroll Audit Report - Pay Component Detail by Employee - Pay Component Summary - Pay Component Summary by Department - Pay Component Summary by Pay Location - Pay Component Summary by Pay Loct/Dept - Pay Item Detail - Pay Item Explanation Summary - Pay Item Explanation Summary by Department - Pay Transaction Report - Absences Report

HRPC-711 - Payroll Enquiry - add Paid Date to search criteria

Functional Issue

Payroll Enquiry does not have Paid Date in the search criteria. This makes financial year reporting reconciliation difficult.

Functional Verification

1. Login as payroll officer 2. Open the Payroll Enquiry function 3. Confirm that the main Search criteria dates now refer to 'Paid Date' 4. Complete the paid date range to be queried 5. Run Perform Enquiry 6. Confirm that the results returned only includes the employee pays that were paid during the date range specified. 7. Open the extended criteria 8. To restrict the employee pay results to pay periods, enter the Pay Period End Date range as an extended criteria NOTE 'Paid Date' also appears as extended criteria. 9. Run Perform Enquiry 10. Confirm that the results returned only includes the employee pays that were paid during the date range specified AND have a Pay Period End Date in the specified pay period date range. 11. With the preference on for 'Power User' or from Employee tab, navigate to the 'Pay Master' view grid 12. Confirm that the 'Paid Date' now appears in the grid.

Solution Implemented

Paid date has replaced the Pay Period End Date as the main criteria in the Payroll Enquiry function. Both Pay Period End Date and Paid Date can be found and used in the Extended crtieria. Paid Date now appears in the Pay Master grid with the existing column for Pay Period End Date.

HRPC-712 - Payroll Calculations based on Paid Date

Functional Issue

Currently tax and superannuation processing within payroll calculation is based on Pay Period End Date. For Australian employers, tax and superannuation payments should be determined by the Paid Date. E.g. Tax scales effective from 1 July should be applied to employee pays that are received on or after 1 July, regardless of the Pay Period End Date.

Functional Verification

1. From Payroll Officer, navigate to 'Adjust Payroll' or 'Calculate Payroll by Group' function 2. Select pay period and employee criteria to calculate the current pay 3. Specify an Expected Paid Date which varies from the Pay Period End Date. NOTE Primarily the change in processing will be verified more clearly when these two dates cross the ATO financial year boundary of 30 June. 4. Calculate the employee pay(s) 5. Confirm the details of calculations from the Calculation Audit log which is available in 'Adjust Payroll' function 6. Confirm that the calculation has used effective records for tax and superannuation based on the specified 'Expected Paid Date'

Solution Implemented

Payroll calculation of tax and superannuation for the Australian region has been updated to use effective records based on the Expected Paid Date of the pay being calculated. This includes retrieval of: 1. Australian Tax scales effective records 2. Australian Superannuation thresholds 3. Employee effective tax records 4. Employee effective superannuation details

HRPC-713 - Pay Calculation options - new Expected Paid Date field for YTD and calculation thresholds

Functional Issue

A new field 'Expected Paid Date' is required for Pay Calculations to ensure that the tax, superannuation and Year To Date pay advice figures are based on a 'Paid Date' rather than the 'Pay Period End Date'. NOTE The 'Expected Paid Date' represents the date that the employee is expected to 'receive' their pay. i.e. funds are cleared into their account via bank transfer. This date is not expected to vary from the actual 'Paid Date' used for the corresponding bank download file and transfer. Variations in a 'Paid Date' from its corresponding 'Expected Paid Date' may result in incorrect tax, superannuation or YTD pay advice values. e.g. if crossing new effective tax scale date boundaries such as 1 July.

Functional Verification

Adjust Payroll. 1. Open the Adjust Payroll function 2. Confirm that the 'Expected Paid Date' field is accessible under the 'Pay Period End Date' field and is blank 3. For a selected employee, calculate their next pay. Noting that the 'Expected Paid Date' is mandatory for the calculation. 4. After a successful pay is calculated, confirm that the 'Pay Calculated' date is now populated. 'Paid Date' remains blank as the pay is not yet bank downloaded. 5. Clear the Adjust Payroll screen 6. Re-retrieve the previous employee's pay 7. Confirm that the 'Expected Paid Date' contains the previously entered date, and is still modifiable. i.e. the user can choose to change the expected paid date while the pay is only in a Calculated status 8. Modify the employee's pay by making a manual adjustment and re-calculate 9. Confirm that the 'Expected Paid Date' remains at the entered date; the 'Pay Calculated' date is still set to today's date and the 'Paid Date' is blank 10. Confirm that the YTD amounts displayed in the summary panel are based on Paid Dates (or Expected Paid Date) within the Financial Year of the employee's company. 11. Proceed to 'Bank Download' this employee's pay 12. Confirm that the 'Expected Paid Date' is loaded into the 'Paid Date', and the field is modifiable. i.e. the user can choose to change the actual 'Paid Date' from the originally entered 'Expected Paid Date' NOTE The calculations of the pay will be based on the 'Expected Paid Date' for tax and superannuation rate and threshold purposes (effective dated), therefore if a change to the 'Paid Date' varies from the 'Expected Paid Date' and crosses these date boundaries, the calculation may vary from what is expected. i.e. incorrect tax scales applied. The pay should be re-calculated in these scenarios before being processed further (i.e. paid and posted). 13. After a successful bank download, return to the Adjust Payroll view of this employee's pay 14. Confirm that the 'Expected Paid Date' field is now disabled, and the 'Paid Date' field has been completed 15. Proceed to produce the employee's Pay Advice 16. Confirm that the YTD amounts on the Pay Advice are based on Paid Dates (or Expected Paid Date) within the Financial Year of the employee's company. Calculate Payroll by Group and Calculate Payroll for Multiple Companies 1. Open the Calculate Payroll by Group (or for Multiple Companies) 2. Confirm that the 'Expected Paid Date' field is accessible under the 'Pay Period End Date' field and is blank 3. For all or selected employees, calculate their next pay. Noting that the 'Expected Paid Date' is mandatory for the calculation. NOTE Only employee pays that can be calculated or re-calculated will have the 'Expected Paid Date saved or modified to the value entered on the screen. E.g. Pays that can be re-calculated have a status of 'Not Processed', 'Calculated', or 'Saved not Calculated'. Additionally, under 'Corrective Access' the user may re-calculate pays that have been paid only - status of 'Paid not Posted' . 4. Confirm that the 'Expected Paid Date' and 'Paid Date' are now loaded into the Employees grid (next to Status field) 5. After successful pays are calculated, navigate to 'Adjust Payroll' function 6. Open one of the calculated employee pays, and confirm that: (a) 'Pay Calculated' date is now populated (b) 'Paid Date' remains blank as the pay is not yet bank downloaded (c) 'Expected Paid Date' contains the previously entered date for the calculation, and is still modifiable. i.e. the user can choose to change the expected paid date while the pay is only in a Calculated status NOTE The calculations of the pay will be based on the 'Expected Paid Date' for tax and superannuation rate and threshold purposes (effective dated). Therefore a change to the 'Expected Paid Date' requires a re-calculation of the pay. Saving without calculation will result in a 'Saved not Calculated' pay. Such pays are unable to be finalised (i.e. paid and posted). Calculate Manual Back Pays by Group. 1. Open the Calculate Manual Back Pays by Group 2. Confirm that the 'Expected Paid Date' field is accessible under the 'Pay Period End Date' field and is blank 3. Complete other back pay criteria and select the employees to be back paid 4. Process back pays with the 'Expected Paid Date'. Noting that the 'Expected Paid Date' is mandatory for the calculation 5. Confirm that the 'Expected Paid Date' is now loaded into the Employees grid (next to Status field) 6. After successful back pays are calculated, navigate to 'Adjust Back Pay' function 7. Open one of the calculated employee back pays, and confirm that: (a) 'Pay Calculated' date is now populated (b) 'Paid Date' remains blank as the pay is not yet bank downloaded (c) 'Expected Paid Date' contains the previously entered date for the calculation, and is still modifiable. i.e. the user can choose to change the expected paid date while the pay is only in a Calculated status NOTE The calculations of the pay will be based on the 'Expected Paid Date' for tax and superannuation rate and threshold purposes (effective dated). Therefore a change to the 'Expected Paid Date' requires a re-calculation of the pay. Saving without calculation will result in a 'Saved not Calculated' pay. Such pays are unable to be finalised (i.e. paid and posted).

Solution Implemented

A new mandatory field 'Expected Paid Date' has been added to the payroll calculation functions where a 'Paid Date' is relevant. This enables calculations to be based more correctly on a 'Paid Date' with regards to: (a) tax scales (b) superannuation thresholds (c) YTD figures displayed in the Adjust Payroll function and used in the employee's pay advice. This includes the following functions: 1. Adjust Payroll (by employee) 2. Calculate Payroll by Group 3. Process or Adjust an employee pay for Correction, Bonus or Special Pays 4. Correction, Bonus and Special Pay Run by Group 5. Calculate Manual Back Pays by Group 6. Adjust Back Pay for Employee 7. Calculate for Multiple Companies - for Payroll, Correction, Bonus and Special Pay 8. NOTE All other document types that are actually 'paid' require an 'Expected Paid Date'. Including Non-Payroll Reportable, History and Imported Pays. NOTE The following payroll document types do not require an 'Expected Paid Date': 1. Accrual 2. Accrual Adjustment 3. Leave Liability 4. Payroll Liability 5. Accrual and Long Service Leave

HRPC-714 - New function 'Update Paid Date'

Functional Issue

The 'Paid Date' on employee pay is unable to be corrected by Payroll Officers if it was incorrectly set during Bank Download. This can impact legislative payroll reporting to government agencies which determine tax withholding by 'Paid Date'. Additionally, pays that have a zero (fully salary sacrificed) or negative Nett Pay (Correction Pay) are not eligible for Bank Download (i.e. no actual payment), and therefore unable to be finalised without running data fix scripts to set the 'Paid Date'.

Functional Verification

1. As Payroll Officer, navigate to the new function 'Update Paid Date' 2. Enter the Pay Group and Pay Period End Date for which pays require a new or updated Paid Date NOTE Only successfully Calculated pays are eligible for a Paid Date. Additional criteria can be specified prior to 'Retrieve' to reduce the list of employee pays available for selection. 3. Specify the 'New Paid Date' 4. To review and select individual employee pays for update, complete the Criteria and click 'Retrieve'. Review the existing 'Expected Paid Date' and 'Paid Date' values displayed in the Employees grid Alternatively, choose 'Process All Employees' to update the Paid Date on all pays included in a pay period (by group and date). 5. Submit the process to update the selected pays 6. After successful completion of the update, Retrieve to confirm the new Paid Date on each employee pay. Alternatively, navigate to 'Adjust Pay' to open one of the updated employee pays, and confirm that: (a) 'Pay Calculated' and 'Expected Paid Date' values are still populated with previous values (b) 'Paid Date' has been updated as specified (c) The displayed YTD pay amounts are correct for the current financial year (d) Reproducing the Pay Advice shows the updated and correct YTD amounts NOTE If the change of Paid Date crosses the company's financial year period then YTD amounts are impacted. As such, the update process will include the recalculation of YTD amounts stored for each updated employee pay period, as well as in all the latest pays of the employee(s) for all document types. If required, re-produce these impacted employee Pay Advices to provide the updated YTD amounts to the employee. i.e. for the pay period updated and the most recently dated pay. NOTE 1. Only employee pay that has been successfully Calculated is eligible to be marked as paid with a 'Paid Date'. This includes balanced negative or zero Nett Pays, such as Correction Pay. 2. Only the companies and employees that the user has Security Access to will be available for updating the Paid Date. This is determined by their assigned User Security Category and Employee-specific section criteria. 3. The calculations of each pay are based on the 'Expected Paid Date' for tax and superannuation rate and threshold purposes (effective dated). Therefore a change to the 'Paid Date' may require a re-calculation of the pay with a new 'Expected Paid Date' (i.e. which now reflects the actual 'Paid Date'). 4. Saving without a successful calculation will result in a 'Saved not Calculated' pay. Such pays are unable to be finalised (i.e. paid and posted). 5. Pays that can be re-calculated have a status of 'Not Processed', 'Calculated', or 'Saved not Calculated'. Additionally, under 'Corrective Access' the user may re-calculate pays that have been paid but not yet posted. i.e. a status of 'Paid not Posted' .

Solution Implemented

1. The new function 'Update Paid Date' has been provided to enable payroll officers to correct 'Paid Date' values on calculated pays. This includes zero and negative nett pays. However, only employee pay that has been successfully calculated (i.e. has a Calculated Date) are eligible for a Paid Date. 2. YTD amounts used for Pay Advices are updated when the Paid Date is changed. This only includes the YTD amounts of the updated pay period and the most recent pays for the employee(s) selected (i.e. by Pay Period End Date and Document Type). Any intervening pay records for the pay advice YTD amounts (HRPAY_PAYITEMS_SUMMPMNT) will NOT be updated with recalculated YTD amounts. These can be updated if required by specifying those pay period end dates in another 'Update Paid Date' process.

HRPC-722 - ATO TFN Declaration electronic reporting changes effective 1/10/2017

Functional Issue

ATO TFN Declaration for electronic reporting (Portal file upload) has been updated to support Working Holiday Makers.

Functional Verification

1. Run Electronic TFN Declarations choosing e-File transmission for the current reporting period 2. Review the file's version number reported in the supplier line 3. Confirm the version is 'FTFNDV03.0' 4. For new employee TFN Declarations who have checked the Working Holiday Makers indicator, the new 'Payee Tax Status' field will contain a value of 'H'. While Residents = 'A' and Foreign Residents = 'F' 5. Additionally, a new field for 'Payer email address' is now completed (from the Company details - Street Email 1 field). The former 'Contact facsimile number' has been removed.

Solution Implemented

Updated ATO TFN Declaration for eFile submissions to TFND Version 3.0.0 NOTE This version is only supported post 1 October 2017 due to ATO system dependencies.

HRPC-737 - Period Leave taken on Payslip differs from actual leave taken in that pay period

Functional Issue

When an employee has transferred between companies that share the same leave accrual pay component code(s), their Pay Advice shows the incorrect units for the current period's leave taken (in the 'Period Leave Taken'), NOTE This issue occurs when employees are transferred to another company without creating a termination record and new date of hire. i.e. not maintaining separate employment periods based on company.

Functional Verification

1. For an employee who has transferred between companies (changed job details) but maintained the same leave accrual codes, perform the following testing. NOTE Accrual rules exist for both companies with the same accrual pay component code(s). AND a termination record and new re-hire date has not been created to identify the company transfer. 2. Ensure they have taken leave during both periods of employment. 3. From Leave Maintenance, create new leave taken for that employee (for their latest job and company position) 4. Calculate the pay period to pay this leave taken (i.e. after the company transfer) 5. Generate Pay Advice 6. Confirm that the current leave taken units are displayed correctly in the 'Period Leave Taken' on the pay advice. i.e. no additional leave taken units are included

Solution Implemented

The accrual summary process has been corrected to ensure that leave accrual amounts are restricted by the company that the employee works for in each accrual period. NOTE Best practice when transferring employees to other payroll companies, is to terminate and rehire the employee into the new company.

HRPC-773 - EFT report not always showing Paid Date from the Correction pay master

Functional Issue

The EFT Payment report incorrectly groups off-cycle pays (e.g. Correction) under the Paid Date of other pay periods that occur in the same week.

Functional Verification

1. To test EFT payments for a specified company and Pay Period End Date of a regular pay run 2. Ensure that the bank download file(s) have been produced, thereby providing a Paid Date on the employee pays 3. Ensure that a Correction or Special Pay has been processed and paid in the same week as the Pay Period End Date 4. Run the EFT Payment report 5. Confirm the report displays each employee pay correctly grouped by Paid Date and Document Type.

Solution Implemented

EFT Payment and EFT Payments for Multiple Companies reports have been corrected by grouping the Paid Date on a daily basis.

HRPC-802 - Paid Date - Corrective access and Pay Calculation improved validation

Functional Issue

Under payroll 'Corrective Access', a posted pay can be modified and re-calculated. However this results in a failure to re-calculate and also clears the Calculation and Paid dates. At this point either the entire pay must be deleted and re-processed; or a data fix is requested to restore the dates.

Functional Verification

Posted Pay under Corrective Access 1. Ensure the payroll user has 'Corrective Access' to 'Allow reprocessing of Finalised Pays' authorisation 2. Navigate to Adjust Payroll function 3. Open an employee pay that has been posted 4. Confirm that the action links for 'Save' and 'Calculate' are no longer available and the pay items grid is not modifiable 5. The only action available to the user is to 'Delete'. This allows the user to reenter and recalculate the entire pay 6. Delete the posted pay 7. Confirm that a warning message box appears with 'Pay has been posted. Deletion of a posted pay will require financial journal adjustments. Do you wish to Continue and Delete this pay?' 8. Select 'Yes' to the prompt 9. Confirm that the pay has been deleted. Paid but not Posted Pay under Corrective Access 1. Ensure the payroll user has 'Corrective Access' to 'Allow reprocessing of Finalised Pays' authorisation 2. Navigate to Adjust Payroll function 3. Open an employee pay that has been Paid but NOT Posted (i.e. bank download file produced but Payroll Posting not run) 4. Confirm that the action links for 'Save' and 'Calculate' are still available and the pay items grid is modifiable 5. Modify the pay and recalculate 6. Confirm that a warning message appears stating 'Changing the pay has cleared the Paid Date. Restore the Paid Date via a bank download or the Update Paid Date function.' 7. Confirm that the pay has a new Calculation Date. 8. Proceed to Bank Download the pay NOTE If this is a bank file reproduction of a Pay Group of employees, additional 'Corrective Access' is required for 'Allow Reprocessing of Bank Download Files' 9. Confirm that the Paid Date has been restored to the recalculated employee pay.

Solution Implemented

1. Additional validation for Posted pays has removed the ability to modify or recalculate under 'Corrective Access'. 2. The only corrective access action available for a Posted pay is to delete and re-enter the entire pay. However, this will result in financial journal adjustments. 3. An additional warning message prompts the user to confirm that they understand the implications and wish to proceed with the deletion. 4. Paid but unposted employee pay may still be modified and recalculated under 'Corrective Access', however a new warning message appears reminding that the Paid Date must be restored.

HRPC-805 - Data Analyser only includes the latest PAYG Payment summary for employees who have worked for more than one company in a single financial year.

Functional Issue

The data analyser for 'Payment Summaries inc ETP' only includes the latest PAYG Payment summary for employees who have worked for more than one company in a single financial year. Additionally, the employee job details included are for those effective 'Today' when running the query, rather than effective at Financial Year End.

Functional Verification

1. Test for employees who have transferred between companies in one financial year, and received termination pays for both companies 2. Ensure that the employee's PAYG payment summaries are loaded for both company employment periods 3. Open 'Drag and Analyse' and the 'Payment Summaries inc ETP' data analyser 4. Enter the criteria to query the employees who have transferred companies 5. Confirm that both payment summaries in the one financial year are retrieved for the employee(s) 6. Confirm that the job details available are from the employee's job that effective on or before the Financial Year End Date. E.g. last job effective on or before 30/6/2017

Solution Implemented

The retrieval of Payment Summaries details for data analysers has been corrected to match on company code for each employee job relevant to each payment summary within a single financial year.

HRPC-810 - Payroll Calculation Log does not identify employee when an Application Error occurs

Functional Issue

Employee Id Number is not always reported in the Log file when an unexpected exception occurs during processing Payroll.

Functional Verification

NOTE Verification can only occur when an unexpected system exception occurs. E.g. server or database connection error 1. Run Pay Calculation by Group function. 2. Confirm that when any unexpected exception occurs, the Id Number of the affected employee is included in the error message in the log file. NOTE This enables Payroll calculation in CiAnywhere to display the error message matching by Id Number.

Solution Implemented

The Payroll calculation process function has been updated to include employee Id Numbers when reporting unexpected exceptions in error messages.

HRPC-814 - Default Control Var for ATO thresholds to be moved to Effective Dated Other Tax Scales

Functional Issue

The Superannuation Base Maximum quarterly, Employment Termination Payment (ETP) Cap amount and ETP withholding rates are not currently delivered via the effective dated scales for the Australian region.

Functional Verification

Superannuation maximum quarterly base: 1. From the Payroll Officer workplace, Manage Payroll tab, Payroll Management section of the System Administration explorer. 2. Confirm the Other Scale $AU region includes the AU_SUP_BAS - Maximum Quarterly Base for Super Guarantee tax scale type. 3. Confirm the Maximum Quarterly Base includes the following effective dated details: 01/07/2016 - Earnings (X) less than $9,999,999,999.00, value of column (B) $51,620.00. 01/07/2017 - Earnings (X) less than $9,999,999,999.00, value of column (B) $52,760.00. 01/07/2018 - Earnings (X) less than $9,999,999,999.00, value of column (B) $54,030.00. 4. Calculate SGC superannuation for an employee whose current quarter earnings exceeds the applicable limit above. 5. Confirm the SGC calculation earnings are limited due to the quarterly base earnings limit being exceeded. ETP Cap Amount: 1. From the Payroll Officer workplace, Manage Payroll tab, Payroll Management section of the System Administration explorer. 2. Confirm the Other Scale $AU region includes the AU_ETP_CAP - Employment Termination Payment (ETP) CAP Amount tax scale type. 3. Confirm the ETP Cap Amount includes the following effective dated details: 01/07/2016 - Earnings (X) less than $9,999,999,999.00, value of column (B) $195,000.00. 01/07/2017 - Earnings (X) less than $9,999,999,999.00, value of column (B) $200,000.00. 01/07/2018 - Earnings (X) less than $9,999,999,999.00, value of column (B) $205,000.00. 4. Terminate an $AU region employee. 5. Manually add an taxable ETP code 'O' pay item with the item type set to Termination. 6. Calculate the termination pay. 7. Review the calculation audit and confirm the termination tax calculation has retrieved the correct ETP cap amount from the other tax scales. NOTE: The ETP tax calculation process includes the whole-of-income cap within the calculation of the minimum cap to apply. The whole-of-income cap is a separate non-indexed ETP cap that is not defined within the other scales. ETP Withholding rates: 1. From the Payroll Officer workplace, Manage Payroll tab, Payroll Management section of the System Administration explorer. 2. Confirm the Other Scale $AU region includes the AU_ETP - Employment Termination Payment (ETP) tax scale type. 3. Confirm the ETP rates include the following effective dated details as at 1/07/2017 per the ATO Schedule 11: https://www.ato.gov.au/Rates/Schedule-11---Tax-table-for-employment-termination-payments/?page=5#Table_A__Withholding_rates_for_ETPs

Solution Implemented

Enhanced the Payroll package and app to define and use effective dated records for the Superannuation Maximum Quarterly Base earnings, ETP Cap amount and ETP withholding rates. These are defined in the effective dated Other Tax Scales for Australia. NOTE If employers do not take the Legislative release updates for Payroll then the DEFAULT control variable values for ETP Cap and Super Quarterly Max must be updated manually after 30 June 2018. i.e. These Control Variable values will no longer be updated from the 1/7/2017 values: 1. HR_SUP_BASE_MAX 2. HR_ETP_CAP

HRPC-819 - The Payment Summary Listing Report ($HR.TAX.PAYGLST.RPT) is missing the Exempt Fringe Benefits field

Functional Issue

The PAYG Payment Summary Listing report is missing the Jan 2017 ATO Exempt Fringe Benefits field

Functional Verification

1. Open PAYG Payment Summary Listing report 2. Fill in the criteria and run the report 3. Confirm that the Exempt Fringe Benefits field and summary are available in the report.

Solution Implemented

Added Exempt Fringe Benefits field and summary in the PAYG Payment Summary Listing report.

HRPC-847 - SBR Payment Summary error - max DB connections exceeded with 725 employees

Functional Issue

An application exception is raised when processing SBR PAYG Payment summary report for a large number of employees.

Functional Verification

1. Navigate to the Electronic PAYG Summaries function 2. Select the option for SBR (if you have been using SBR and have created the required credentials with your AusKey) 3. Specify the Financial Year to transmit to the ATO. E.g. 2018 4. Ensure that more than 100 employees are selected for processing 5. Start Processing 6. Confirm that the transmission is successful. i.e. without SBR Validation Error ERROR_TAXONOMY_SERIALISE that states "The maximum number of allowed connections (10) has been reached".

Solution Implemented

The SBR PAYG Payment Summary process has been modified to ensure that processing large numbers of employees will not cause a SQL connection error.

HRPC-849 - Pay as you go withholding (PAYGW) payment summary annual report (PSAR) specification v13.0.0

Functional Issue

ATO update of the Pay as you go withholding (PAYGW) payment summary to version 13.0.0.

Functional Verification

1. Navigate to Electronic PAYG Summaries function 2. Complete the mandatory criteria for e-File transmission (EMPDUPE) 3. Run the PAYG Payment Summaries 4. Confirm the e-file version is 'FEMPA013.0' in row 1 5. Additionally a field has been removed for "ECI tested" ('Y') from column 92 row 4 of the e-File.

Solution Implemented

Updated the function for the Electronic PAYG Withholding Summary to comply with the new specification v13.0.0. Update the e-File version to 'FEMPA013.0' and removed the ECI tested field.

HRPC-859 - Paid Date - Payroll Import update

Functional Issue

New field for 'Expected Paid Date' is required in the Pay Import function.

Functional Verification

1. Open Pay Import template file. 2. Confirm that the 'expected_paid_date' field is available in the template. 3. Import a payroll with 'expected_paid_date' set. Do not set the pay calculate options. 4. Confirm that the payroll is imported and not calculated. 5. Import a payroll with 'expected_paid_date' set. Set the pay calculate options. 6. Confirm that the payroll is imported and calculated. 7. Navigate to 'Adjust Payroll' function to confirm that the Expected Paid Date and Pay Calculation Date are set and reflect the imported pay details. NOTE A warning will be logged if the Expected Paid Date is not provided in a pay import. This value will be defaulted to the Pay Period End Date, thereby processing as in previous releases.

Solution Implemented

Added 'Expected Paid Date' field to the Pay Import template and function. NOTE: For the full functionality of this enhancement both the latest HRP Core and Payroll Processing packages are required. Updated pay import template is included in Payroll Processing package, along with Expected Paid Date changes. Updated pay import processing is included in HRP Core package.

HRPC-863 - [Bank Download Format] Format TDB Bank File

Functional Issue

Tonga Development Bank implements the DiskPay system now. Hence, a download script needs to be created.

Functional Verification

1. Ensure the stored script procedure '$HRPAY_TOTDB' exists. 2. Open Bank Download function. 3. Retrieve the bank account format and bank and branch number that use the '$HRPAY_TOTDB' script. 4. Choose one or more pay periods to process. 5. Start Processing. 6. Confirm that the bank download succeeds. 7. Open the bank download file generated. 8. Confirm that the file format is correct based on the 'TDB EFT File Format Definitions for TPL' document.

Solution Implemented

Created a bank download script for Tonga Development Bank ($HRPAY_TOTDB).

HRPC-869 - Australian ABA bank download file requires BSB and account in the header when the employer has multiple accounts.

Functional Issue

ANZ Bank requires BSB and account in the header section of the bank download file when the employer has multiple accounts.

Functional Verification

1. Open the Stored Scripts function 2. Confirm the new $HR_PAY_AU_ANZ script is available 3. Create or update the bank download format to use the script above 4. Perform a bank download that uses the format above 5. Confirm the BSB & Account number are available in the header section of the bank download file per the ANZ ABA File Specifications document.

Solution Implemented

Created the $HR_PAY_AU_ANZ bank download script to accommodate BSB and Account Number in the header section of ANZ bank download file.

HRPC-879 - Error on Leave Cancel when reducing accruals only (not paying leave taken)

Functional Issue

When an employee has the Timesheet Leave Rule option on their position set to 'Reduce Accruals Only', an error is displayed when doing cancellation of leave that has been paid (or posted).

Functional Verification

1. For an existing employee that has their job 'Timesheet Leave Rule' option set to 'Reduce Accruals Only' 2. From Leave Maintenance, generate leave taken for that employee NOTE ensure that leave line type in the employee's Timesheet Format does not have a Base Pay pay component code listed. i.e. the leave is only to reduce an accrual. 3. From Adjust Payroll, process the pay period containing this employee's leave, ensuring to load timesheets 4. Bank download and post the pay 5. From Leave Maintenance, cancel the paid and posted employee leave (as created in step 2) 6. Confirm that the leave is cancelled without error 7. From Adjust Payroll, process the pay period for the next period, ensuring to load timesheets 8. Confirm that the pay calculates, and that the cancelled leave is reversed. However, base pay is not generated to replace the leave, due to the 'Reduce Accruals Only' being specified.

Solution Implemented

Leave and payroll processing has been corrected to handle cancelling leave when 'Reduce Accruals Only' is applied to an employee. i.e. Base pay is not repaid when cancelling leave which has already been paid (or posted) and the leave only applies to reduce an accrual.

HRPC-886 - Timesheet Only employee's leave taken hours recalculate to standard work day units on recalculation of a manually adjusted pay

Functional Issue

When manually adjusting a pay of a Timesheet Only employee who is not on a work pattern, the recalculation results in the leave units being modified to the expected daily work hours. This only occurs if Leave entry has not been used and the leave hours entered directly into the timesheet are above their standard work day hours.

Functional Verification

1. Enter leave directly into a timesheet of a 'Timesheet Only' employee, ensuring that the units entered are above the standard work day hours. NOTE Ensure this employee has no work pattern assigned, nor is there an accrual leave conversion matrix configured for the leave. 2. Calculate the pay period and load this timesheet to be paid 3. Manually adjust the pay 4. Calculate the pay again without loading timesheets (as they are already included in the pay) 5. Confirm the leave units remain paid as entered in the timesheet.

Solution Implemented

Payroll calculation process has been modified to avoid an unnecessary unit type conversion when the unit type in an accrual rule is blank.

HRPC-914 - Employee transfer to another company - Payroll Enquiry not resolving amounts correctly

Functional Issue

The payroll enquiry does not include the paid pays for employees that have terminated and re-hired within different companies.

Functional Verification

1. For a terminated New Zealand employee who is re-hired into an Australian company immediately and where the termination pay date crosses into the new transfer employment period, confirm the following: 2. Ensure the termination pay for the employee is paid after the termination activity date 3. Confirm the termination pay has calculated correctly and bank download the pay to mark it as Paid 4. Re-hire the employee as at the first work day after the termination activity BUT before the previous termination pay period end date 5. Calculate ordinary pay periods for the remainder of the month. i.e. for the new Australian employment period that occurs after the termination pay 6. Bank download the ordinary pay periods 7. Perform a payroll enquiry for the month that the employee has been terminated within, include the first work period Company Code (NZ) and Pay Group within the quick criteria 8. Review the summary views and confirm all views include the total pays paid for the employee that have been paid per the first work period. In particular the Employee view lists the terminated employee 9. Review the Detail Views for each of the summary views and confirm the details are correct 10. Perform a payroll enquiry for the month after the employee has been terminated within, include the first work period Company Code (NZ) and Pay Group within the quick criteria 11. Review the summary views and confirm all views include the termination pay paid to the employee. In particular the Employee view lists the terminated employee 12. Review the Detail Views for each of the summary views and confirm the details are correct 13. Perform a payroll enquiry for the same month as step 10, except the quick criteria should be for the second work period Company Code (Australia) and Pay Group 14. Review the summary and detail views and confirm the values displayed include the pays paid for the employees second work period only

Solution Implemented

Amended the payroll enquiry to ensure employees re-hired in a different company are included in the enquiry if paid after the termination date.

HRPC-921 - EMS File(s) are created with the same filename when processing multiple companies

Functional Issue

The Employer Monthly Schedule (IR 348) job fails if a file with the same name already exists in the target server folder. The user is then required to change the filename to another prior to processing each company.

Functional Verification

1. Navigate to the NZ IRD Employer Monthly Schedule (IR 348) function 2. Specify the Company Code and reporting period. Tab out 3. Confirm that the filename is defaulted to 'EMS_{CompanyCode}_{PayeePeriod} format. E.g. 'EMS_1_Dec2017.txt' 4. Change the company code and/or PAYE Period to another month 5. Confirm that the filename is updated with the changed company and reporting period in the format 'EMS_{CompanyCode}_{PayeePeriod} format. E.g. 'EMS_2_Jan2018.txt' 6. Start Processing 7. Confirm that the process produces the file as named 8. Repeat the above steps and override the default filename 9. Start Processing 10. Confirm that the overridden filename modified by the user is correctly generated 11. Repeat the above steps for the Electronic Deduction Form (IR 345) and KiwiSaver Employment Details (KS1) functions to confirm new default file naming.

Solution Implemented

The NZ IRD eFile process has been enhanced with a new filename format default that includes the selected company code and reporting pay period. i.e. "{Job Type}_{CompanyCode}_{PayeePeriod}.txt". This applies to the following NZ IRD electronic forms: 1. Electronic Deduction Form (IR 345) 2. Employer Monthly Schedule (IR 348) 3. KiwiSaver Employment Details (KS1)

HRPC-950 - TSL is not included in the Payment Summary's Total Tax Amount

Functional Issue

Trade Support Loans (TSL) amount is not included in the Total Tax Amount when loading PAYG Payment Summaries.

Functional Verification

1. Calculate and pay an employee who has TSL specified in their tax details 2. Load the employee's payment summary using Adjust PAYG Payment Summary 3. Confirm that the Total Tax Amount in payment summary matches the total Taxation withholding amount including the TSL withheld for the employee within the financial year.

Solution Implemented

Changed the load Payment Summary process to include TSL amounts in the Total Tax Amount loaded into the PAYG Payment Summary.

HRPC-966 - Data Management task for Paid Date enhancements

Functional Issue

A new Data Management task is required for Paid Date enhancements

Functional Verification

1. Login as Payroll Officer 2. Open the 'Pay Transactions' data analyser 3. Set the criteria to Pay Period End Date >= 1-Jan-2017 4. Confirm that the new field 'Expected Paid Date' is defaulted to the Pay Period End Date on all payable Document Types. i.e. this does not include Accruals, Accrual Adjustments, Payroll Liability and Leave Liability 5. As System Administrator, access the System Variables 6. Confirm that either: a. 'HR_PAIDDATE_IND' does not exist b. 'HR_PAIDDATE_IND' is set to 'Y'

Solution Implemented

A new Data Management task has been added for the Paid Date enhancements, in order to: 1. Default the Pay Master field 'Expected Paid Date' to the value of 'Pay Period End Date' for all pays on or after 1-Jan-2017. This assists reporting and viewing of pays after the introduction of the mandatory 'Expected Paid Date' field. 2. Reset the system variable 'HR_PAIDDATE_IND' to ensure PAYG payment summaries are loaded by Paid Date. This system variable will NOT exist by default. It will only exist if it was previously created by the system administrator to override PAYG Payment Summary date processing. i.e. to load by Paid Date rather than Pay Period End Date For the Paid Date enhancements, this system variable should either be set to 'Y'es or deleted completely. If this variable exists and is set to 'N'o, then employee PAYG Payment Summaries will be loaded for the financial year based on Pay Period End Date rather than Paid Date.

HRPC-974 - SBR TFN transmission failed but the TFN transmission marked as successful

Functional Issue

The SBR transmission of TFN declarations will show all declarations as successful when at least one succeeds. The system should only update the successful employee TFN declaration with the ATO transmission details.

Functional Verification

1. Navigate to the Electronic TFN Declarations function 2. Change Report Options to SBR 3. To test failure, ensure that one employee's declaration is missing a required field for the ATO (e.g. missing payment basis, missing date signed, or missing payee signature) 4. Process multiple employee TFN declarations to be submitted 5. Confirm only employees with completed declarations are marked as successfully transmitted. The employee with the incomplete declaration remains outstanding. i.e. ATO transmission details are not present on their Tax record

Solution Implemented

The method to transmit the SBR Report has been updated to transmit 1 payee/employee per transmission. Each single process will be marked as successful or fail separately.

HRPC-977 - Error message on Deduction Payee ledger/account validation needs to be improved when an application error occurs.

Functional Issue

The error message is not informative when the deduction payee ledger/account validation raises an error or exception during pay calculation.

Functional Verification

NOTE This is an exceptional error scenario where the validity of a cost ledger on a pay component has been compromised after being configured and selected for payroll usage. 1. As a Payroll Officer, navigate to the Adjust Payroll function 2. Select an employee who will be receiving a Deduction pay item with deduction payee configured 3. Calculate the employee's next outstanding pay 4. Confirm that an application error does not occur and that the error message returned contains detail that is informative to user. E.g. 'Failed to get valid Financial Ledger details for Deduction Payee 'ATODED' in Pay Component code '813.0' for Company '1', Ledger 'GL' as at Date '1 Jan 2018'. Check configuration details.'

Solution Implemented

Added error messages that contain informative details to user in the deduction payee ledger/account validation.

HRPC-983 - Base pay reversals were not being processed for retrospective leave booked in Ci Anywhere.

Functional Issue

For employees configured with a Timesheet Calculation method of 'No Timesheets Required', base pay reversals were not being processed for retrospective leave booked in Ci Anywhere. This would result in the employee receiving more than their expected payroll entitlement.

Functional Verification

1. As an employee configured as 'No Timesheets Required', log on to Ci Anywhere and navigate to the My Leave function 2. Submit a request for leave as at a date that falls within a pay period that has already been paid and processed for banking 3. As the employee's manager, log on to Ci Anywhere and navigate to the My Tasks function 4. Approve the employee's leave request 5. Log on as the Payroll Officer and navigate to the Adjust Pay function 6. Specify the employee and current pay period 7. Verify that the retrospective leave timesheet entries are available to be loaded into the pay 8. Process the pay, ensuring to load entitlements and timesheets 9. Verify that the pay contains pay items for the employee's retrospective leave 10. Verify that the pay contains reversal pay items for Base Pay and which matches the days that are now being paid as leave.

Solution Implemented

Payroll processing has been modified to ensure base pay reversals for CiAnywhere leave are correct when the employee being paid is configured as 'No Timesheets Required'. NOTE The Timesheet Calculation method of 'Exception Entry' should be used in preference to 'No Timesheets Required' which is obsolete.

HRPC-989 - Payroll Enquiry - Employee Name Reversed

Functional Issue

Employee Names in the employee tab in the Payroll Enquiry are in the wrong order (i.e. are 'Given, Family'). The order should be displayed as 'Family, Given' order.

Functional Verification

1. Navigate to the Payroll Enquiry function 2. Complete the mandatory criteria 3. Start the payroll enquiry 4. Open the employee tab 5. Confirm that the employee names are in the correct order (i.e. Family, Given).

Solution Implemented

Corrected the display of employee names in the Payroll Enquiry.

HRPC-1007 - PAYG Payment Summary - Paid Date by default

Functional Issue

Currently the ATO PAYG Payment Summary uses the Pay Period End Date to determine what employee pays to include in the payment summary reporting. i.e. comparing Pay Period End Date to the company's Financial Year start and end dates. The Pay Period End Date does not reflect the actual date employees receive the money (as per the ATO paid date definition), therefore payroll users are forced to adjust the Financial Year dates to include the correct financial year pays.

Functional Verification

1. Login as Payroll Officer and navigate to Company Maintenance 2. Ensure that the Financial Year Start and End dates will correctly include employee pays based on the Paid Date. E.g. The Financial Year dates for Australian companies can be set to the ATO financial year dates of 1 July 2017 to 30 June 2018 3. Navigate to the Load PAYG Payment Summaries function 4. Specify the company and current financial year criteria for loading employee PAYG Payment Summaries. E.g. 2017/18 5. Run the load PAYG process 6. Confirm success from the log and messages returned 7. Navigate to Adjust PAYG Payment Summary function 8. Confirm that Payment Summaries for the loaded employees only include Paid pays that have Paid Dates within the Financial Year selected. NOTE Pays will be excluded if the Pay Period End Date falls within the Financial Year dates BUT the Paid Date falls outside of that financial year. Similarly, pays will not be included if they have not been bank downloaded or updated with a Paid Date. This can be confirmed by using the data analysers for Payment Summaries and Pay Transactions (using the Paid Date range criteria).

Solution Implemented

The Australian PAYG Payment Summary has been modified to use the Paid Dates within the defined Company Financial Year dates to accumulate the payment summary amounts.

HRPC-1037 - SBR Payment Summary Taxonomy load error for on-premise installations

Functional Issue

SBR Payment Summary can result in an error for on-premise installations. i.e. With error message: ERROR_TAXONOMY_LOAD : An error occurred while loading taxonomy

Functional Verification

1. From Payroll Officer 2. Open Electronic PAYG Summaries (Payment Summaries) 3. Select SBR transmission option 4. Complete the criteria for the PAYG financial year. Ensure valid credentials are selected and working prior to transmission (i.e. refer to SBR Credential Maintenance and Taxonomy Diagnostics). 5. Start Processing 6. Transmission returns successful. No error is received - i.e. "ERROR_TAXONOMY_LOAD". NOTE If validation errors are received for specific employee details, correct these prior to further transmission attempts.

Solution Implemented

SBR taxonomy files are copied into Data server folders to allow write access during the SBR transmission process (i.e. updated or additional files returned by the ATO SBR process). NOTE To receive this resolution the latest package for Framework - External Integration must be installed. Reference ADFC-1968.

HRPC-1051 - TFN Dec SBR transmission errors - only 1 payee can be transmitted at a time

Functional Issue

On 22 Sep 2017 the ATO changed the validation of TFN declarations to reject multiple employee declarations in a single transmission. To avoid the need for user to manually select and submit one employee at a time, the TFN SBR process should be enhanced to separate each employee declaration selected by the user and submit to the ATO singularly.

Functional Verification

1. Navigate to the Electronic TFN Declarations function 2. Change Report Options to SBR 3. Select multiple employee TFN declarations to be submitted. Submit 4. Confirm that all valid TFN declarations are successfully transmitted, and that no ATO SBR error is received. E.g. 'Maximum payee limit exceeded, only 1 payee per transmission is allowed'

Solution Implemented

The method to transmit the SBR Report have been changed to transmit 1 payee/employee per transmission to the ATO. NOTE Additionally the ATO has ceased support of the SBR Test portal for versions 1 and 2 of the TFN Declaration. However, Production submission is still supported for these versions.

HRPC-1053 - Australian Tax Scale Codes are not descriptive

Functional Issue

Australian Tax Scale Codes 1-6 do not provide the functional description in order to be more helpful to the user. E.g. Tax Scale 1 - Not Claiming Tax-free Threshold

Functional Verification

1. For new installations only, navigate to Employee Maintenance 2. Select an employee who requires new tax details 3. Add Tax Details 4. Select the Tax Scale Code required 5. Confirm the list of tax scale codes include the ATO functional descriptions.

Solution Implemented

Australian Tax Scale Code descriptions have been updated to include the ATO purpose. NOTE As these standard codes are configured to allow the user to modify the descriptions, these codes will NOT be refreshed on upgrade. Only new installations will receive these enhanced Australian tax scale code descriptions. If you require the enhanced descriptions, update the TAX_SCALE_CODE standard codes via Standard Codes Maintenance: Tax Scale 1 - Not Claiming Tax-free Threshold Tax Scale 2 - Claiming Tax-free Threshold Tax Scale 3 - Foreign Resident Tax Scale 4a - No TFN Provided (Resident) Tax Scale 4b - No TFN Provided (Foreign Resident) Tax Scale 5 - Full Medicare Exemption Tax Scale 6 - Half Medicare Exemption

HRPC-1056 - Manual Back Pay incorrectly shows a pay as 'Posted' when it is not

Functional Issue

The 'Delete Pays by Group' and 'Manual Back Pay' functions display the pay status incorrectly as 'Posted' or 'Paid and Posted' when a pay is not posted but does contain an Accrual pay component code (e.g. RDO, banked time).

Functional Verification

1. As Payroll Officer, navigate to Adjust Payroll 2. Select an employee and pay period where the employee will be receiving an accrual adjustment in the pay. e.g. via RDO or banked time i.e. Ensure the pay has an accrual pay component, which may be entered manually 3. Calculate the pay 4. Bank download the pay, thereby stamping it as Paid 5. Open the Delete Pay by Group function (or Manual Back Pay) and retrieve the employee pay from above 6. Ensure that the status of the employee pay is displayed as 'Paid and not Posted'.

Solution Implemented

Corrected the enquiry sets used to display the pay status to exclude the accrual pay components from the posted pay retrieval.

HRPC-1083 - Manual Back Pay - Load Search for employees results in exception RTE

Functional Issue

In the Manual Back Pay function, using the Load Search for employees results in a system exception.

Functional Verification

1. As Payroll Officer, navigate to Calculate Manual Back Pays by Group 2. Specify the mandatory criteria for the Back Pay period and pay components required 3. Specify Employee search criteria in the Criteria section and Retrieve 4. Save the specified criteria 5. Clear the function and repeat steps 1-3 and click the link 'Load Search' 6. Confirm that the saved search criteria can be retrieved and used without error.

Solution Implemented

The Manual Back Pay function has been corrected to handle loading and saving search criteria.

HRPC-1111 - ETP maximum witholding rate should be at 47% effective 1 July 2017

Functional Issue

The ETP maximum withholding rate is still set to 49%. It needs to be lowered to 47% based on ATO Witholding rates table effective on 1 July 2017.

Functional Verification

1. For an employee receiving a large Termination pay out which exceeds the ETP cap for 2017-18 of $200,000 2. Calculate termination pay with the required ETP pay item 3. Confirm that the ETP amount is taxed at 47%.

Solution Implemented

Updated the maximum withholding rate for ETP tax to 47%.

HRPC-1195 - Payroll Enquiry Poor performance in 2018A

Functional Issue

Payroll Enquiry can timeout on some enquiries due to excessive database times. This occurs in some SQL queries due to additional table joins which are not included in the where clause.

Functional Verification

1. Login as payroll officer 2. Open the Payroll Enquiry function 3. Confirm that the main Search criteria dates now refer to 'Paid Date' 4. Complete the paid date range to be queried 5. Run Perform Enquiry 6. Confirm that the results returned only includes the employee pays that were paid during the date range specified. 7. Restrict the range of pays by specifying a Pay Group to the criteria 8. Set the Preference to display the results as a Power User. i.e. interactive grids by row selection 9. Run Perform Enquiry 10. Confirm that the results returned only includes the employee pays that were paid during the date range specified AND have a Pay Group as selected 11. For a row selected in each of the Summary Views, view each of the corresponding Detail Views tab results retrieved by: a. Pay Component b. Ledger and Account c. Pay Master 12. Confirm that all results return within seconds and do not timeout.

Solution Implemented

Payroll Enquiry has been corrected by adding explicit table joins to the Pay Master which is now required for the Paid Date primary critieria change introduced in 2018A (Nov 2017 packages).

HRPC-1196 - New Zealand IRD Payroll Legislation changes 1 Apr 2018

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2018: 1. The ACC earners levy scales have been updated as at 1 April 2018. 2. The Student Loan repayment threshold has been amended as at 1 April 2018. 3. From 1 April 2017 employers have been able to tax benefits of an Employee Share Scheme as an extra pay. To date the PAYE, Student Loan & Benefit has been included within the employee's detail record in the Employer Monthly Schedule (IR348). Effective from 1 April 2018 the IRD require the Employee Share Scheme benefit, related PAYE and Student Loan to be reported within the IR348 as a separate 'ESS' detail record. 4. Inland Revenue have advised that protected earnings for Attachment Orders, other than Child Support Deduction notices, are the greater of: a. the protected earnings stated on the attachment order b. 60% of the post-tax earnings for the period, per the calculation of child support protected earnings.

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2018 and are for the correct percentage and maximum levy. The Earners Levy percentage for 1 April 2018 is 1.39% for annual income less than $126,286 and the maximum levy is $1,755.37. 2. Calculate an ordinary pay after the 1st April 2018 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Student Loan Changes: 1. Verify the Student Loan scales (NZ_SL) exist for 1 April 2018 and are for the correct percentage and maximum levy. The Student Loan percentage for 1 April 2018 is 12.0% (A) for annual income greater than $19,448 (X). 2. Calculate an ordinary pay after the 1st April 2018 for an employee with tax code M SL. 3. Review the calculation audit. 4. Confirm the new Student Loan repayment threshold was used for the tax calculation. Employee Share Scheme (ESS) benefits Employer Monthly Schedule (IR348) reporting changes: 1. Create a pay component type 990 - Taxation for Employee Share Scheme benefits PAYE withholding. 2. Confirm the New Zealand region configuration codes include the code 'Tax Lump Sum Payment - Employee Share Scheme' (TAX_LSPESS) and select the configuration code. 3. Create a pay component type 990 - Employee Share Scheme benefits Student Loan. 4. Confirm the New Zealand region configuration codes include the code 'Student Loan - Employee Share Scheme' (TAX_SLESS) and select the configuration code. 5. Select the Taxable indicator in the General section. 6. Save the changes. 7. Load the next ordinary pay period for an employee. 8. Manually enter a pay item for the employee share benefits pay component for $2,500.00. 9. Calculate the pay with entitlements loaded. 10. Review the taxation section of the calculation audit. 11.Confirm the employee share benefits has been included in the tax calculation as a lump sum payment. 12. Confirm the lump sum tax rate is calculated per the IRD lump sum calculation steps. 13. Confirm the lump sum tax calculation does not include earners levy within the withholding amount. 14. Review the pay items to confirm a lump sum tax item is generated for the correct amount per the calculation audit. 15. Confirm the ESS benefit PAYE item has been generated with the pay component configured in step 1 - 2 above. 16. Confirm the calculation audit has calculated the student loan applicable to the ESS benefit and it has reduced from the total student loan payable. 17. Confirm the ESS benefit student loan has been generated with the pay component configured in step 3 -4 above. 18. Bank download the pay. 19. Process the EMS (IR 348) for the month that includes the ordinary pay. 20. Confirm employee has an additional detail line for the ESS benefit: The line should include the Employee IRD Number, Employee Name, the Tax Code 'ESS'. The benefit amount is included in the gross earnings and earnings not liable for ACC Earner's Levy fields. The ESS PAYE withholding and student loan are included within the PAYE / Tax and Student Loan deduction fields. 21. Confirm the EMS header totals are correct, the ESS detail line should be included within the respective header totals fields. 22. Process the Employer Deduction Form (IR345) for the month reported within the EMS. 23. Confirm the deduction fields are correct per the respective EMS header fields. Protected Earnings for Attachment Orders other than Child Support Deduction Notices: 1. Confirm the system includes a PCC type 120 - Protected Earnings Amount pay component configured for the Child Support protected earnings percentage of 60%, the percentage is specified within the amount field of the pay component. Also confirm the New Zealand region configuration code 'CHILD_SUPP' is selected for this component. 2. Configure a PCC type 810 - Deduction pay component for Attachment Orders stated deduction amount. Do NOT select the New Zealand region configuration code 'CHILD_SUPP' while configuring the pay component. 3. Configure a PCC type 120 - Protected Earnings Amount pay component for Attachment Order protected earnings amount. Do NOT select the New Zealand region configuration code 'CHILD_SUPP' while configuring the pay component. 4. Load the employee maintenance function for an New Zealand employee. 5. Generate a new entitlement set effective from the start of the current pay period. 6. Add the PCC type 810 - Deduction pay component configured for Attachment Orders to the entitlement set for the stated deduction amount of an order. 7. Add the PCC type 120 - Protected Earnings Amount pay component to the entitlement set for the stated Attachment Order protected earnings amount of an order. 8. Calculate the current ordinary pay period for the employee. 9. Review the calculation audit to confirm the 60% post tax protected earnings is calculated per the child support rules and confirm the greater of the calculated protected earnings and the stated protected earnings per the employee entitlements is used while assessing the attachment order protected earnings.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2018: 1. The ACC Earners Levy tax scales have been updated and apply to pay on or after 1 April 2018. 2. The Student Loan tax scales have been updated and apply to pay on or after 1 April 2018. 3. The pay calculation and IRD Electronic Reporting have been changed to allow Employee Share Scheme Benefits, their related PAYE withholding and student loan deduction to be reported as a separate detail record within the Employer Monthly Schedule (IR348). 4. The Post Tax deduction section of the pay calculation has changed to calculate the 60% post-tax protected earnings for attachment orders and use the greater of the calculated post-tax protected earnings OR the attachment order stated protected earnings.

HRPC-1220 - Timesheet Adjustments from previous periods not resolving pay rate in pay calc

Functional Issue

Timesheet lines retrospectively added to a timesheet that has already been paid are not being paid in the next pay period calculated for the employee IF there has been a new Effective Job added since the original pay period.

Functional Verification

1. For an employee who will have a timesheet modified since it was paid in the previous pay period 2. Navigate to Employee Maintenance and ensure that this employee also has a new Effective Job defined that is dated after the last paid period. E.g. for change of FTE 3. Navigate to Timesheet Entry 4. Perform retrospective timesheet adjustments to the previously paid timesheet by adding new line entries. E.g. for additional ordinary or overtime hours worked 5. Save to approve 6. Select the current Timesheet period and ensure that times worked are entered and approved 7. Navigate to Adjust Payroll and select the next pay period for the employee 8. Ensure to select Load Timesheets and calculate the pay. 9. Confirm that both the currently unpaid timesheet and the previous timesheet period adjustments are loaded and paid.

Solution Implemented

Corrected the pay calculation to ensure all position data and associated pay rates are retrieved for the unpaid timesheets that have been loaded from previous periods.

HRPC-1278 - NZ Electronic deduction Form (IR345) File name default

Functional Issue

NZ IRD EDF reporting - If the user changes the file name from the default file name created based on the selection, the file name reverts to the default file name when Start Processing is selected.

Functional Verification

1. Open the Payroll Officer workplace. 2. Select the More tab and open the IRD Electronic Reporting --> Electronic Deduction Form (IR 345) ($HR.IRD.ELECEDF.PRC) function. 3. Enter the function's key fields for the period to be reported. 4. Confirm the File Name field has defaulted per the key fields values entered. 5. Change the File Name field value. 6. Select Start Processing. 7. Confirm the processing has been completed with the File Name value entered in step 5 above. 8. Confirm the EDF file has been saved within the Destination Folder per the File Name entered.

Solution Implemented

Changed the New Zealand IRD reporting Electronic Deduction Form process to ensure the entered File Name is retained for the processing. Rather than reverting to the default File Name per the key field values entered.

HRPC-1284 - Error when downloading Bank Download file

Functional Issue

Cloud environments only are impacted by a Bank Download run time error when upgrading to 2018A. This occurs due to the schema and system data being upgraded for several days prior to the 2018A Packages and Apps being upgraded. If the bank download is processed during this time, a run time error will result due to the missing Payroll Processing Compatibility Helper (Common CS package).

Functional Verification

1. Calculate employee pay(s) for a Pay Period 2. Bank Download the pays 3. Open the generated Bank Download file 4. Confirm that no errors occurred and that the bank download file is generated correctly.

Solution Implemented

The Bank Download Common script has been updated to replace the usage of Compatibility helpers with basic exception handling. If the software has not yet been upgraded then the attempt to use new functionality is ignored. In this case, the use of Expected Paid Date when processing Bank Downloads.

HRPC-1309 - New Report required for Pay Components by Pay Location with the criteria using Paid date

Functional Issue

A new report is required to retrieve Pay Components by Pay Location with the Paid Date as the main date criteria. NOTE The existing shipped report, 'Pay Component Summary by Pay Location' is based on Pay Period End Date only.

Functional Verification

1. As System Administrator, define a new custom Crystal Report function that provides access to the new report, 'pcsloc01_PaidDate.rpt'. This can be titled 'Pay Component Summary by Pay Location and Paid Date'. Assign access for the Payroll Officer. 2. As Payroll Officer, open the new report 'Pay Component Summary by Pay Location and Paid Date' 3. Confirm that the Paid Date is used in the main criteria 4. Run the report 5. Confirm the report is generated and displays the results for the selected criteria.

Solution Implemented

A new Payroll report has been shipped 'pcsloc01_PaidDate.rpt'.for "Pay Component Summary by Pay Location and Paid Date". This is a copy of the existing report, 'Pay Component Summary by Pay Location' enhanced with the main criteria of Paid Date. NOTE A custom function is required to provide the Payroll Officer with the authorised access to this new Crystal report if it is required for payroll use. A shipped report function for this report will be available in a future release.

HRPC-1340 - New Zealand pay calculation completes with $0.01 out of balance error

Functional Issue

New Zealand employee pay calculation can result in an out of balance error of $0.01 in the following scenario: 1. Employee has a child support deduction, and 2. The deduction is reduced due to the 60% protected earnings calculation (i.e. employee receives insufficient nett pay earnings to meet their child support obligation).

Functional Verification

1. Locate an New Zealand employee with child support deduction 2. Load the next available ordinary pay period 3. Calculate the pay period with reduced ordinary earnings that will cause the 60% protected earnings to reduce the child support deduction. E.g. Employee receives a pay of 9 hours worked only. 4. Confirm the pay has calculated and saved without error 5. Review the calculation audit to confirm the child support protected earnings has been calculated, and the deduction is reduced 6. Confirm the child support deduction has been reduced per the calculation audit.

Solution Implemented

The NZ pay calculation has been modified to ensure that child support deductions which are reduced do not result in an out of balanced pay error,

HRPC-1370 - TFN Declaration SBR TFND.0003 2016 required for 30 June 2018 ATO Legislative Changes

Functional Issue

The current SBR TFND version 0001 will be unsupported by the ATO from 30 June 2018. This will be replaced by SBR TFND.0003 2016. NOTE This SBR TFND.0003 2016 does not support Working Holiday Maker indicator. If the employer has WHM TFND to submit, the eFile TFND must be used instead of SBR.

Functional Verification

1. For an employee who requires tax details to be submitted to the ATO. i.e. employee Tax and Electronic TFN Declaration sections are completed 2. Navigate to the Electronic TFN Declarations process function 3. Select the SBR report option 4. Enter the required fields to select the employee tax details created in step 1 5. Start Processing 6. When the process is complete confirm that the process has displayed a SBR Message Accepted (CMN.ATO.GEN.OK) message 7. Open the SBR Submission Enquiry function 8. Locate the TFND submission and confirm the Report Version transmitted is 03.00

Solution Implemented

SBR TFND processing has been updated to transmit the ATO TFND version 0003 2016 taxonomy. NOTE: This SBR TFND.0003 2016 does not support Working Holiday Maker indicator. If the employer has WHM TFND to submit, the eFile TFND must be used instead of SBR.

HRPC-1409 - Aust ATO Payroll Legislative changes effective 01/07/2018

Functional Issue

Australian Legislative changes effective 1 July 2018, including: 1. The Australian ordinary tax scales are to be updated from 1 July 2018. 2. The Australian HELP/TSL and SFSS Other Scales are to be updated from 1 July 2018. 3. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2018. 4. The Maximum super contribution base amount will increase from 1 July 2018. 5. The indexed ETP cap amount will increase from 1 July 2018. 6. The 'Document Types to Exclude from YTD figures' control variable (HR_YTD_EXCLUDE) is not shipped with a default value. 7. The indexed Employer Productivity Superannuation Contribution (EPSC) will increase from 1 July 2018.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Australian ordinary income thresholds (Tax Scales -> $AU - Australia): 4. Confirm that new Australian ordinary income thresholds are available for the 1 July 2018. 5. Navigate to the HELP (SSL or TSL) income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP): 6. Confirm that new HELP (SSL or TSL) income thresholds are available for the 1 July 2018. 7. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS): 8. Confirm that SFSS repayment income thresholds are available for the 1 July 2018. 9. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Tax Scales -> $AU - Australia -> AU_GRTFL): 10. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2018. 12. Navigate to the Maximum Super Contribution Quarterly Base (Other Tax Scales -> $AU - Australia -> AU_SUP_BAS). 13. Confirm that the Max Quarterly Base is $54,030.00 - details scale column (B). 14. Navigate to the Employment Termination Payment (ETP) CAP Amount (Other Tax Scales -> $AU - Australia -> AU_ETP_CAP). 15. Confirm that the ETP Cap Amount is $205,000.00 - details scale column (B). 16. Navigate to the Default Control Variable Maintenance > Payroll section. 17. Confirm that the Document Types to Exclude from YTD figures $DEFAULT value is 'F, G' (i.e. liabilities). 18. Navigate to the EPSC Productivity Component scales (Other Tax Scales -> $AU - Australia -> AU_EPSC). 19. Confirm that the 1 July 2018 EPSC scales are available.

Solution Implemented

1. New Australian Ordinary Tax Scales have been added for the 2018-2019 financial year (refer to ATO website). Note: The tax scale changes announced within the 2018 Federal budget have not been passed within both houses of parliament. The ATO have published these scales on the basis of the legislation passes both houses unchanged. If the scales are withdrawn by the ATO due to the legislation changing we will publish details for manual entry of the new scales within the employee community. 2. New Australian HELP/SSL/TSL and SFSS Other Tax Scales have been added for the 2018-2019 financial year (refer to ATO website). Note: The HELP/SFSS scales are per the scales provided by the ATO for the currently legislated Omnibus Bill. There is an alternate bill before parliament that may become law by 1st July 2018, and these scales may change. If the scales are withdrawn by the ATO due to the legislation changing we will publish details for manual entry of the new scales within the employee community. 3. New Australian Genuine Redundancy Tax Free Limit thresholds have been added for the 2018-2019 financial year (refer to ATO website). 4. The new Other Tax Scale for the Superannuation Maximum Quarterly Base has been updated (to 54,030.00). 5. The new Other Tax Scale for the ETP Cap Amount has been updated (to 205,000.00). 6. The Document Type to exclude YTD figures has been updated in the $DEFAULT Control Variables - with the values for leave and payroll liability document types (F, G). 7. The Commonwealth Superannuation corporation (CSC) have published the new EPSC rates for 1 July 2018. NOTE The ATO have not formalised a change to the thresholds in Working Holiday Maker tax scales for 1 July 2018. We will advise on the Customer Community once this has been confirmed and the Schedule 15 has also been updated. Currently the change discussed is an increase of the 32.5% threshold from earnings less than $87,000 to $90,000. NOTE: To ensure that these new tax details are loaded into your database(s): 1. For release 2017A onward (either cloud installations or on-premise), ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server. 2. Alternatively, for On-Premise installations, a Package Finalise can be executed after applying this update. NOTE If employers do not take the Legislative release updates for Payroll then the DEFAULT control variable values for ETP Cap and Super Quarterly Max must be updated manually after 30 June 2018. i.e. These Control Variable values will no longer be updated from the 1/7/2017 values: 1. HR_SUP_BASE_MAX 2. HR_ETP_CAP

HRPC-1477 - EPSC Rates effective 1 July 2018 are incorrect

Functional Issue

The AU_EPSC Other Scales effective from 1 July 2018 are incorrect for Less than $3790 (should be 0.03 but is incorrectly set to 0.003).

Functional Verification

1. Login into the system and load the Payroll Officer workplace. 2. Navigate to the EPSC Productivity Component scales (Other Tax Scales -> $AU - Australia -> AU_EPSC). 3. Confirm that the 1 July 2018 EPSC scales are available and correct as per the CSC web site. NOTE: If the scales have failed to update, navigate to function 'HR and Payroll Load Region Data' and execute for the '$AU' region. Ensure to select 'N' for test mode.

Solution Implemented

The EPSC scales were corrected per the CSC web page: https://eac.csc.gov.au/your-toolkit/epsc-rates/

RELEASE May 2017

HRPC-372 - WHOLE_PRD percent of total components incorrect on condition change

HRPC-457 - Termination Pay - Superannuation doubling up if multiple positions are paid

HRPC-532 - Pay Recalculation causes incorrect conversion from leave taken Hours to accrual Days

HRPC-537 - Security needs to be applied to PAYG Processing (and IRD)

HRPC-580 - Payment Summary Employment End and Start Dates outside ATO Financial year

HRPC-589 - EOFY - Printing PAYG Summaries (since CLOUD)

HRPC-598 - Manual accrual unit type does not reflect Accrual Rule on Pay Advice when only Initial Load exists

HRPC-603 - Bank Download required for Tonga ANZ and BSP banks

HRPC-620 - Pay Summary Report does not display large Id Numbers

HRPC-622 - Print PAYG Payment Summary for terminated employees only print the first PAYG

HRPC-628 - Australian PAYG Withholding - Seniors and Pensioners Tax Offset

HRPC-642 - Manual Retro Process does not work for ordinary doc type

HRPC-643 - New Manual Back Pay not correct when paying leave impacted by a mid-period retrospective rate change

HRPC-652 - Aust ATO Payroll Legislative Scale changes effective 01/07/2017

HRPC-655 - New Zealand IRD Payroll Legislative changes effective 01/04/2017

HRPC-668 - Security needs to be applied to Bank Download processing

HRPC-669 - Adjust Pay - Cloud Timeout entering Leave pay components

HRPC-680 - BackPay not calculating on Imported Pay Transactions

HRPC-681 - Employee pay status incorrectly displayed for 'Saved and not Calculated' pays in the function Calculate Pay by Group

HRPC-686 - Payroll Calculation new saved negative pay did not include amount in warning

HRPC-689 - Ship EPSC scales for 2016/2017

HRPC-701 - Compulsory extra Student Loan (SLCIR) no longer being deducted

HRPC-707 - Calendar based increments are not as expected for some mid-month dates

HRPC-715 - Negative Manual Back Pay saves calculation date

HRPC-720 - Australian PAYG Withholding - Working Holiday Makers

HRPC-724 - Reportable FBT Exemption changes in 2017 PAYG payment summary

HRPC-726 - ATO SBR - Payment Summary Electronic Reporting changes effective 01/07/2017

HRPC-738 - Deduction Summary Report not applying Pay Group criteria

HRPC-851 - SBR PAYG submission failing with Period Type must be 'Payment'

HRPC-866 - Leave Liability calculation ignoring balances in old Long Service Leave Code

HRPC-372 - WHOLE_PRD percent of total components incorrect on condition change

Functional Issue

Percent of total pay components with the WHOLE_PRD system configuration code selected are not paid correctly when there is a mid period pay condition change.

Functional Verification

1. Create an employee with a percent of total deduction with WHOLE_PRD selected in their employment condition. The deduction percentage is dependant on BASE_PAY. 2. Calculate an ordinary pay period and confirm the deduction is generated correctly. 3. Create a new effective dated employment condition for the employee which is mid way through the following pay period. 4. Increase the BASE_PAY component within the employment condition. 5. Calculate the ordinary pay period. 6. Confirm the deduction pay item is generated for the correct total from the pay period start to the day before the effective date of the employment condition change. 7. Confirm a second deduction pay item is generated for the correct total from the effective date of the employment condition change to the pay period end.

Solution Implemented

Changed the pay calculation to ensure percent of total pay components with WHOLE_PRD selected are paid for the whole pay period correctly when the pay includes a mid period pay condition change.

HRPC-457 - Termination Pay - Superannuation doubling up if multiple positions are paid

Functional Issue

An Australian termination pay with superannuation base earnings for multiples positions would generate duplicate superannuation contribution items.

Functional Verification

1. Locate an Australian region employee with primary and secondary positions. 2. Terminate the employee from Employee Maintenance. 3. Ensure the employee has ordinary base earnings for both positions within the pay period for the termination. 4. Calculate the employee's termination pay. 5. Confirm the SGC/Company/Employee superannuation contribution pay items are generated correctly per the superannuation fund definition.

Solution Implemented

Changed the pay calculation to ensure termination pay superannuation contributions are generated correctly for employees with multiple positions.

HRPC-532 - Pay Recalculation causes incorrect conversion from leave taken Hours to accrual Days

Functional Issue

Recalculating a pay without re-loading timesheets does not convert leave units to accrual units when the unit types require conversion.

Functional Verification

1. Locate an employee whose annual leave is taken hourly and accrue on a daily basis. 2. Create and approve a leave request for annual leave. 3. Calculate the pay period that the leave falls within, select load timesheets. 4. Confirm the leave pay item is paid correctly. 5. Confirm the employee maintenance leave taken details display the units taken as days per the accrual unit type. 6. Confirm the leave taken units are converted to the correct number of days. 7. Recalculate the pay, do not select load timesheets. 8. Confirm the leave pay item is still correct. 9. Confirm the employee maintenance leave taken details are still displayed as per the previous confirmation steps 5 and 6.

Solution Implemented

The pay calculation was amended to ensure leave taken that requires unit conversion is processed correctly when recalculating a pay period and timesheets have not been selected for loading (i.e. calculation option).

HRPC-537 - Security needs to be applied to PAYG Processing (and IRD)

Functional Issue

Security category access needs to be applied to users who have functional capabilities to run ATO PAYG and NZ IRD reporting processes. NOTE: As this security must be defined at Company level, user access is determined by the Organisation Management security criteria.

Functional Verification

1. Create a Security Category that has the Organisation Management access defined and which allows one or several companies to be accessed. Assign this security category to the Payroll user. 2. Login as the user above and navigate to one of the ATO or NZ IRD report processing functions E.g Load PAYG Payment Summary, or Employer Monthly Schedule (IR 348) 3. Select a company that the user is not authorized to access 4. Confirm that the process is not executed and an error message is returned noting that the user does not have security access to the selected company 5. Select a company that the user is authorized to access 6. Confirm that the process is executed without a security access error message.

Solution Implemented

Security category validation has been added to the ATO and NZ IRD Electronic Reporting functions. i.e. When user does not have authorisation to a company as define by their Security Category Organisation Management access setting, an error message is displayed and the process is not run. The Financial Year picklist used by these functions has been updated to display records for the specified company only. When user does not have authorisation to the company, the picklist is empty. NOTE To receive the full functionality of this change both the HRP Core and Payroll Processing May 2017 packages must be installed.

HRPC-580 - Payment Summary Employment End and Start Dates outside ATO Financial year

Functional Issue

In the scenario where the employee's termination is within their company's Financial Year however occurs before the ATO financial start date of 1 July, the loaded PAYG report will include an incorrect period payment date which is outside of the ATO financial year dates. For example: the company's financial year is set to 25/6/2015 - 26/6/2016 (while the ATO financial year date is strictly 1/7/2015 - 30/6/2016). Employee has their Termination record created for the 28/6/2016. As the employee's termination is paid post 30/6/2016 (as per the Company's Financial Year), their termination details appear on the 2016/2017 Payment Summary but with the incorrect end date of 28/6/2016.

Functional Verification

1. Terminate an employee with a Termination Date between the company financial year end date and ATO financial year end date (30 June). E.g. The company financial year is set to 25/6/2015 - 26/6/2016. The ATO financial year date is 1/7/2015 - 30/6/2016. Employee is terminated on 28/6/2016. i.e. the employee receives their termination pay post 1/7/2016 so this amount needs to be included on the 2016/17 Payment Summary. 2. Process the termination pay and do a bank download for the termination pay. 3. Load the PAYG payment summary. 4. Print the PAYG payment summary. 5. Confirm that the loaded PAYG report produces the correct period payment dates. E.g. In this case, the end date on the employee's Payment Summary 2016/17 is set to 1/7/2016. i.e. for their termination 28/6/2016 but which was actually paid to the employee post-30/6/2016, and therefore included in the Payment Summary FYE 2016/17. Additionally, the start date for the 2015/16 Payment Summary is set the ATO financial year start date 1/7/2015, rather than the payroll company financial year start of 25/6/2015.

Solution Implemented

Additional validation has been added in the PAYG process to ensure the Employment End Date and Start Date is valid when the payroll company financial year dates are different to the ATO financial year dates (30 June - 1 July).

HRPC-589 - EOFY - Printing PAYG Summaries (since CLOUD)

Functional Issue

The function to 'Print PAYG Payment Summaries' generates separate documents for each employee when their default transmission type is 'Print'. In cloud installations where the printer is mapped to a specified email address, this results in a separate email for each employee PAYG Payment Summary. NOTE This is not an issue when the default transmission is to email payment summaries directly to each employee. Additionally, some printers are capable of printing emailed documents directly so that separate Payment Summary documents do not prove to be a concern. The alternative report function 'Print PAYG Payment Summary' prints all specified employee payment summaries in one document. This is a print for all employees, where the transmission method on employee jobs is not used.

Functional Verification

1. From Payroll Officer workplace, navigate to the function 'Print PAYG Payment Summaries' which specifies a Document Definition (default $P1PAYGSUM) to transmit the payment summaries as per each employee's chosen method. i.e. Print, email, fax, export 2. Select the financial year criteria. NOTE Do not select 'Overwrite Default Printing Option' 3. Ensure there is a mixture of transmission methods across employees. i.e. their job details will specify Print, Email, Fax or Export 4. Process the payment summaries selected 5. Confirm that the employee payment summaries are issued based on the employee transmission type specified in their job details 6. Confirm that the printed payment summaries are contained in one document. i.e. where the employee specified 'Print' option

Solution Implemented

Updated the Print PAYG Payment Summaries transmission process to generate a single document for all employees who chose the 'Print' option.

HRPC-598 - Manual accrual unit type does not reflect Accrual Rule on Pay Advice when only Initial Load exists

Functional Issue

The employee's pay advice will not display the unit type of a Manual accrual that is not set to Hours, and where the employee's balance is only represented in an initial load. i.e. no accrual adjustments have been made nor included in pay calculations.

Functional Verification

1. Log on as a Payroll Officer 2. From Adjust Payroll, select an employee who: a. has a Manual Accrual in their active entitlements that has an Accrual Rule defining a Unit Type that is NOT a unit type of Hours E.g. Weeks b. has an Initial Load for this active Manual Accrual that defines the current balance c. there are no accrual adjustments for the Manual Accrual (yet) 4. Calculate the employee's current pay 5. Calculate the leave accruals for this employee. NOTE the manual accrual is not included in a calculation however does have an Accrual Summary record created that specifies the correct accrual rule Unit Type 6. Produce the employee's Pay Advice 7. Confirm that the Manual Accrual on the pay advice, displays the correct unit type with the current initial load balance. E.g. Weeks

Solution Implemented

Updated the accrual summary process to ensure that the accrual rule is always applied when getting the Unit Type, regardless of the type of Accrual Rule. E.g. Manual or RDO accrual rule

HRPC-603 - Bank Download required for Tonga ANZ and BSP banks

Functional Issue

A bank download processing script is required for the ANZ and BSP banks in Tonga.

Functional Verification

1. Log into the system with administrator access. 2. Open the System Administrator - All workplace. 3. Navigate to the System Stored Script Procedures. 4. Confirm the stored scripts $HRPAY_TOBSP and $HRPAY_TOANZ are included and they are defined correctly. 5. Define bank download formats for each of the banks. 6. Bank download a pay period for each of the bank download formats. 7. confirm the format files produced are correct per the respective bank's format requirements.

Solution Implemented

Changed the system to include stored script procedures to process ANZ and BSP Tonga bank download formats.

HRPC-620 - Pay Summary Report does not display large Id Numbers

Functional Issue

The Pay Summary reports display long employee id as "#########".

Functional Verification

1. Run Pay Summary report with criteria that include long Id Number, e.g. 10 characters. Ensure it contains the long employee name also, e.g. 50 chars 2. Confirm that the report is generated correctly. The Id Number and Employee Name is displayed without truncated. 3. Confirm the same steps are working in Pay Summary (incl. historical data) and Pay Summary Across Multiple Companies reports.

Solution Implemented

Enlarged the employee Id Number field space in the reports for Pay Summary including Pay Summary (incl. historical data) and Pay Summary Across Multiple Companies.

HRPC-622 - Print PAYG Payment Summary for terminated employees only print the first PAYG

Functional Issue

When an employee has multiple terminations within the same Financial Year, the report to 'Print PAYG Payment Summary for terminated employees only', prints a duplicate PAYG summary for the first employment period.

Functional Verification

1. Find or create an employee who has been hired then terminated twice in the same year (i.e. multiple terminations in the same financial year) 2. Run the report for 'Print PAYG Payment Summary for Terminated Employees Only' 3. Confirm that correct PAYG summaries are printed for the employee. i.e. one per employment period within the financial year.

Solution Implemented

A correction has been made to the report 'Print PAYG Payment Summary for Terminated Employees Only' to handle multiple terminations.

HRPC-628 - Australian PAYG Withholding - Seniors and Pensioners Tax Offset

Functional Issue

The system currently does not allow people who are eligible for the Seniors and Pensioners Tax Offset (SAPTO) to specify their applicable status and apply the correct scales to their PAYG withholding calculation.

Functional Verification

Employee Maintenance: 1. Locate an Australian company employee who is eligible for the seniors and pensioners tax offset (SAPTO) 2. Load the current employee tax details 3. Confirm the Seniors and Pensioners Tax Offset checkbox is visible 4. Confirm the SAPTO Marital Status combo box is visible 5. Confirm the SAPTO Marital Status combo box contains the items 'Single', 'Couple' and 'Illness-separated Couple' 6. Select the SAPTO checkbox and status applicable for the employee 7. Select Ok and confirm the information message advising the SAPTO scale will be applied to the withholding calculation during calculation is displayed 8. Save the employee details and confirm the save completes without errors being displayed 9. Re-load the employee details and confirm the SAPTO checkbox and status combo are displayed as selected. NOTE If the employee's Tax Scale Code value is overridden to a value other than 2 or blank, then this overriding Tax Scale Code will be used for the withholding amounts in the employee's pay rather than the SAPTO withholding Schedule 9. This is reflected in messages and the pay calculation audit. Seniors and Pensioners Tax Offset Tax Scales: 1. Navigate to the Manage Payroll tab 2. Navigate to the Seniors and Pensioners Tax Offset income thresholds (Tax Scales -> $AU - Australia): 3. Confirm that new 'CPL - Couple', 'ILL - Illness-separated Couple', and 'SGL - Single' income thresholds are available for the 1 October 2016. 4. Confirm that new 'CPL - Couple', 'ILL - Illness-separated Couple', and 'SGL - Single' income thresholds are available for the 1 July 2017. PAYG Withholding Calculation: 1. Load an ordinary pay period for the SAPTO employee 2. Calculate the pay period with entitlements and timesheets loaded 3. Review the tax calculation section of the pay calculation audit 4. Confirm the withholding is calculated based on the SAPTO marital status per the ATO PAYG withholding Schedule 9 tax table. NOTE If the employee's currently specified Tax Scale Code has been overridden (from 2 or blank), then the withholding for SAPTO will not apply. Instead the withholding as per the employee's overriding tax scale code will be applied. This is reflected in messages and the pay calculation audit.

Solution Implemented

Employee tax maintenance and payroll tax calculation has been updated to support and withhold tax as per the ATO Seniors and Pensioners Tax Offset (SAPTO).

HRPC-642 - Manual Retro Process does not work for ordinary doc type

Functional Issue

The Auto Retro Document Type control variable 'HR_PAY_RETRO_DT' was misleading due to it being used by both auto and manual retro processing to determine which document type to include during retro processing. Also the control variable determined if the Retrospective changes processing option was selected on by default in the Adjust Payroll and Calculate Payroll by Group functions (i.e. for those document types that can process retrospective changes as per this control variable).

Functional Verification

Control Variable name change: 1. Open the Default Control Variable maintenance function. 2. Locate the HR_PAY_RETRO_DT control variable within the payroll section. 3. Confirm the variable name is Retro Pay Document Types. 4. Confirm the variable description is Document Types to Include in Retrospective Pays. 5. Confirm the variable is set per the shipped default document type (P,R,Z). Customising the Adjust Payroll and Calculate Payroll by Group function definitions to turn off Auto Retro Pay: 1. Open the definition for the Adjust Payroll for Employee function. 2. Confirm the Window Settings section contains a checkbox Do Not Generate Auto Retrospective Pay. 3. Select the checkbox. 4. Save the function definition as a non $ override. 5. Repeat steps 1 to 4 for the Calculate Payroll by Group function definition. Adjust Payroll and Calculate Payroll by Group function display of Auto Retro Pay options: 1. Open the Adjust Payroll for Employee function. 2. Confirm the Calculation Options section has the Retrospective Changes checkbox not visible. 3. Calculate a pay period for an employee who has retrospective changes impacting calculated pay periods. 4. Confirm an auto retrospective pay has not been generated. 5. Repeat steps 1 to 5 for the Calculate Payroll by Group function. Manual Back Pay process: 1. Open the Calculate Manual Back Pays by Group function. 2. Entered the required fields for the employee who has retrospective changes impacting calculated pay periods. 3. Calculate the manual back pay. 4. Confirm the back pay is generated correctly for the employee and includes the Doc Types listed in the control variable, 'Retro Pay Document Types'. Correction Pay processing - confirm Auto Retrospective pay options are not included by default (based on Control Variable, 'Retro Pay Document Types') 1. Open the Correction Pay for Employee function. 2. Confirm the Calculation Options section include the Retrospective Changes checkbox but it is unchecked (i.e. not selected). 3. Calculate correction pay for an employee who has retrospective changes impacting calculated pay periods. 4. Confirm an auto retrospective pay has not been generated. NOTE Follow customising steps as described for Adjust Pay function above in order to hide the 'Auto Retro Pay' processing option for Correction Pay function(s) as well. i.e. not visible at all and therefore not able to be selected by the user.

Solution Implemented

The HR_PAY_RETRO_DT control variable was renamed to reflect its main functionality of determining which Document Types are included for both Auto and Manual back pays. i.e. Now reads "Retro Pay Document Types" - "Document Types to Include in Retrospective Pays". A new window setting, "Do NOT process Auto Retrospective Pay" has been added to all pay processing functions (i.e. Adjust Payroll and Calculate Payroll by Group functions). This setting checkbox determines if the Auto Retrospective Changes calculation option is to be hidden (i.e. and therefore not selected so that Auto Retro Pays will not be generated). NOTE: The default behaviour on shipped functions is to display the Retrospective Changes calculation option selected for the document types listed in the HR_PAY_RETRO_DT control variable.

HRPC-643 - New Manual Back Pay not correct when paying leave impacted by a mid-period retrospective rate change

Functional Issue

Leave is not correctly back paid when that leave occurs in a single pay period which contains a mid-period rate change. The process uses the employee's work pattern to proportion the leave in that the pay period for back pay purposes rather than checking against the exact leave dates from the timesheet (or leave record). i.e. to proportion leave hours prior to the entitlement change date and then after.

Functional Verification

1. Locate a calculated pay period for an employee that contains leave taken. 2. Create a retrospective change to the employee's entitlements with an effective date that is midway through that pay period and leave period. 3. Calculate a Manual Back Pay for the employee via the Calculate Manual Back Pays by Group function, selecting this employee. 4. Review the leave pay items generated for the back pay. 5. Confirm the number of leave units paid for before the new entitlement effective date are correct and they are paid as per the original entitlements. (i.e. prior to the employee's entitlement change) 6. Confirm the number of leave units paid for on or after the new entitlement effective date are correct and they are paid as per the new entitlements.

Solution Implemented

The manual back pay process has been updated to ensure leave items affected by a mid-period entitlement change are paid correctly as per the actual leave dates (which can be confirmed in the timesheet details).

HRPC-652 - Aust ATO Payroll Legislative Scale changes effective 01/07/2017

Functional Issue

Australian Legislative changes effective 1 July 2017, including: 1. The Australian ordinary tax scales are to be updated from 1 July 2017. 2. The Australian HELP/TSL and SFSS Other Scales are to be updated from 1 July 2017. 3. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2017. 4. The Maximum super contribution base amount will increase from 1 July 2017. 5. The indexed whole of income ETP cap amount (HR_ETP_CAP) will increase from 1 July 2017.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Australian ordinary income thresholds (Tax Scales -> $AU - Australia): 4. Confirm that new Australian ordinary income thresholds are available for the 1 July 2017. 5. Navigate to the HELP (SSL or TSL) income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP): 6. Confirm that new HELP (SSL or TSL) income thresholds are available for the 1 July 2017. 7. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS): 8. Confirm that SFSS repayment income thresholds are available for the 1 July 2017. 9. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Tax Scales -> $AU - Australia -> AU_GRTFL): 10. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2017. 12. Navigate to the Default Control Variable Maintenance > Superannuation section. 13. Confirm that the Max Quarterly Base is $52,760.00. 14. NOTE: Check and update the Max Quarterly Base value if required in any customised Control Variable groups. 15. Navigate to the Default Control Variable Maintenance > Taxation section. 13. Confirm that the ETP Cap Amount is $200,000.00. 14. NOTE: Check and update the ETP Cap Amount value if required in any customised Control Variable groups.

Solution Implemented

1. New Australian Ordinary Tax Scales have been added for the 2017-2018 financial year (refer to ATO website). 2. New Australian HELP/SSL/TSL and SFSS Other Tax Scales have been added for the 2017-2018 financial year (refer to ATO website). 3. New Australian Genuine Redundancy Tax Free Limit thresholds have been added for the 2017-2018 financial year (refer to ATO website). 4. The Control Variable for the Superannuation Maximum Quarterly Base has been updated (to 52,760.00). 5. The Control Variable for the ETP Cap Amount has been updated (to 200,000.00). NOTE: To ensure that these new tax details are loaded into your database(s): 1. For On-Premise installations, ensure that a Package Finalise is executed after applying this update. 2. For Cloud installations pre-2016B (i.e. 2016Ax), ensure that the payroll function 'HR and Payroll Load Region Data' is run with Region '$AU' specified. 3. For Cloud installations 2016B onwards, ensure that the Data Management engine job and associated DP Queue $DATAMGMT has been configured to run updates automatically on your active DP Server.

HRPC-655 - New Zealand IRD Payroll Legislative changes effective 01/04/2017

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2017: 1. The ACC earners levy scales have been updated as at 1 April 2017. 2. The Student Loan repayment threshold has been amended as at 1 April 2017. 3. The Schedular payments withholding rules have been changed to allow the contractor to elect a withholding rate. 4. The Schedular payment types have been updated with two new types (WT26 Voluntary and WT27 Labour-hire). 5. The Schedular payment no-notification rate has been standardised at 45 cents per dollar. 6. Effective 1 April 2017 employers are able to tax benefits of an employee share scheme as an extra pay. NOTE This is not mandatory for employers.

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2017 and are for the correct percentage and maximum levy. The Earners Levy percentage for 1 April 2017 is 1.39% for annual income less than $124,053 and the maximum levy is $1,724.33. 2. Calculate an ordinary pay after the 1st April 2017 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Student Loan Changes: 1. Verify the Student Loan scales (NZ_SL) exist for 1 April 2017 and are for the correct percentage and maximum levy. The Student Loan percentage for 1 April 2017 is 12.0% (A) for annual income greater than $19,136 (X). 2. Calculate an ordinary pay after the 1st April 2017 for an employee with tax code M SL. 3. Review the calculation audit. 4. Confirm the new Student Loan repayment threshold was used for the tax calculation. Schedular Payments elected withholding rate: 1. Create employee tax details for a New Zealand employee. 2. Confirm the field Schedular Payment Tax Code is labelled correctly. 3. Confirm the new field Schedular Payment Elected Tax Rate is displayed and labelled correctly. 4. Select the Tax Code WT - Withholding Tax (Schedular Payment). 5. Select the Schedular Payment Tax Code applicable for the contractor. 6. Enter the Schedular Payment Elected Tax Rate the contractor has elected on the new Schedular Payments tax rate notification form (IR number unknown as at Feb 2017). NOTE: The default minimum withholding rate is 10%, except for Non-resident contractors who cannot elect below 15%. 7. Save the employee maintenance changes. 8. Confirm the elected rate has saved without errors being displayed. 9. Calculate the next ordinary pay period. 10. Review the calculation audit to confirm the schedular payment elected rate is used in the calculation of the taxation to withhold. Schedular Payments additional payment types: 1. Verify the Withholding Tax scales (NZ_WT) exist for 1 April 2017. 2. Confirm the scales include the Tax Scale Code WT26 - Voluntary schedular payment. 3. Confirm the Voluntary schedular payment scale is displayed with the correct rates - 20% standard rate (A) and 45% no notification (B). 4. Create employee tax details for a New Zealand employee. 5. Select the Tax Code WT - Withholding Tax (Schedular Payment). 6. Select the Schedular Payment Tax Code for WT26 Voluntary schedular payment. 7. Save the employee maintenance changes. 8. Calculate the next ordinary pay period. 9. Review the calculation audit to confirm WT26 - Voluntary schedular payment is used in the calculation. 10. Confirm the correct percentage is used to calculate the amount to withhold. 11. Repeat the test for the Tax Scale Code WT27 - Contractor payments under a labour-hire agreement. Schedular Payments tax rates updated: 1. Verify the Withholding Tax scales (NZ_WT) exist for 1 April 2017. 2. Confirm the scales for Tax Scale Codes WT1 to WT27 exist. 3. Confirm the standard rate (A) is defined correctly for all scales. 4. Confirm the no-notification rate (B) is displayed as 45% for all scales except the non resident scales below. 5. Confirm the no-notification rate (B) is displayed as 20% for Non-resident contractors who are a company. 6. Confirm the no-notification rate (B) is displayed as 0% for Non-resident entertainers. Employee share scheme (ESS) benefits PAYE: 1. Create a pay component type 4000 - Additional benefits for employee share benefits. 2. Confirm the New Zealand region configuration codes include the codes Lump Sum Payments (LUMP_SUM) and Exempt From Earners Levy (NO_EARN_LV). NOTE Select the config code (ESS) Reportable ESS unless the additional benefit is not reportable for the employees receiving this type of benefit. E.g. "Commissioner approved" share schemes do not need to be reported on EMS. Multiple ESS additional benefit pay component codes will be required if there are both reportable and non-reportable schemes being used by employees. NOTE ESS benefits are not liable for KiwiSaver. Pay Component Type 4000 is not eligible for the config code SUP_ORDHRS. However, if a user-defined config code for KiwiSaver has been defined on the KiwiSaver Funds, ensure this is not selected for ESS benefit pay components. 3. Select the Taxable indicator in the General section. 4. Select region configuration codes above. 5. Save the changes. 6. Load the next ordinary pay period for an employee. 7. Manually enter a pay item for the employee share benefits pay component for $2,500.00. 8. Calculate the pay with entitlements loaded. 9. Review the taxation section of the calculation audit. 10.Confirm the employee share benefits has been included in the tax calculation as a lump sum payment. 11. Confirm the lump sum tax rate is calculated per the IRD lump sum calculation steps. 12. Confirm the lump sum tax calculation does not include earners levy within the withholding amount. 13. Review the pay items to confirm a lump sum tax item is generated for the correct amount per the calculation audit. 14. Confirm the ESS benefit has not been added to the net pay, but the lump sum tax for the benefit is deducted from the net pay. 15. Bank download the pay. 16. Process the EMS (IR 348) for the month that includes the ordinary pay. 17. Confirm the ESS benefit is included in the employee's gross earnings and earnings not liable for ACC Earner's Levy fields. 18. Confirm the lump sum taxation is included in the PAYE/Tax field. 19. Confirm the ESS benefit and lump sum taxation are included in the respective totals within the header record.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2017: 1. The ACC Earners Levy tax scales have been updated and apply to pay on or after 1 April 2017. 2. The Student Loan tax scales have been updated and apply to pay on or after 1 April 2017. 3. The Withholding (Schedular payments) tax scales have been updated and apply to pay on or after 1 April 2017. 4. The employee tax maintenance function and pay calculation have been amended to allow the employee to elect a schedular payment withholding rate. 5. The Additional Benefits pay component type 4000 and pay calculation have been amended to allow employers to tax the benefits of an employee share scheme as an "extra pay". A new NZ Region config code for Reportable ESS (ESS) must be checked for these pay components if the benefit is not explicitly excluded from being reportable by the IRD. E.g. "Commissioner approved" schemes are not reportable.

HRPC-668 - Security needs to be applied to Bank Download processing

Functional Issue

Security category access needs to be applied to users who have functional capabilities to run the Bank Download function. NOTE: As this security must be defined at Company level, user access is determined by the Organisation Management security criteria.

Functional Verification

1. Create a Security Category that has the Organisation Management access defined and which allows one or several companies to be accessed. Assign this security category to the Payroll user 2. Login as the user above and navigate to the Bank Download function 3. Select the required Bank Account Format, with associated Bank and Branch Number 4. Retrieve 5. Confirm that the results in the grid only displays the company(ies) that the user is authorized to access 6. Select row(s) in the grid and start processing 7. Confirm that the bank download process completes successfully and only contains the selected pay periods. 1. For the same user, navigate to the Bank Download for Multiple Companies function 2. Select the Pay Group and Pay Period End Date 3. Retrieve 4. Confirm that the results in the grid only displays the company(ies) that the user is authorized to access 5. Select row(s) in the grid and start processing 6. Confirm that the bank download process completes successfully and only contains the selected pay periods.

Solution Implemented

Security category validation has been added to Bank Download functions. i.e. When user does not have authorisation to a company as defined by their Security Category Organisation Management access setting, these companies are not made available for bank download.

HRPC-669 - Adjust Pay - Cloud Timeout entering Leave pay components

Functional Issue

An accrual forecast is initiated when entering Leave taken pay components manually into the Adjust Pay function. This can result in a timeout error if calculating the employee's associated available accrual balance as of the pay period end date is complex.

Functional Verification

1. As Payroll Officer, navigate to the Adjust Payroll function 2. For an existing employee with available accrual balances, select a pay period to calculate 3. Manually enter a leave taken pay component code applicable to that employee's leave accruals. i.e. to take and pay additional leave 4. Confirm that the 'Number of Units' field is blank and there is no delay when tabbing from the pay component code entered 5. Enter the number of leave units to take. e.g. 8 hours 6. Confirm that the 'Pay Item Amount' value is updated correctly 7. Calculate payroll 8. Confirm that payroll is calculated successfully 9. From Employee Maintenance, confirm that the leave accrual balance has been reduced by the entered leave taken.

Solution Implemented

Removed the accrual forecast calculation when entering a Leave taken pay component into the Adjust Pay function.

HRPC-680 - BackPay not calculating on Imported Pay Transactions

Functional Issue

Manual back pay processing does not include imported and manually entered pay items. This was a deliberate design decision based on the inability to determine that a different rate was intentionally overridden by the payroll officer on these 'manual' pay items.

Functional Verification

1. Import one or more pay items into a pay period for an employee 2. Calculate and bank download this pay 3. Make a retrospective entitlement change that impacts the imported pay by adding a new employee entitlement at a date prior to the imported pay period. E.g. Ensure the base pay rate has changed. 4. Navigate to the Calculate Manual Back Pay by Group function 5. Complete back pay criteria to include the imported employee pay impacted by the entitlement change 6. Process the back pay 7. Navigate to the Adjust Back Pay function and retrieve the employee's generated back pay 8. Confirm that the imported pay item has been included and paid at the new entitlement rate.

Solution Implemented

The Manual Back Pay function has been updated to include the imported and manually entered pay items into the calculation. NOTE This processing change does not apply to the Auto Retrospective pay processing.

HRPC-681 - Employee pay status incorrectly displayed for 'Saved and not Calculated' pays in the function Calculate Pay by Group

Functional Issue

The Status of employee pays displayed in the function 'Calculate Pay by Group', will incorrectly show 'Timesheet Modified' instead of a status of 'Saved and Not Calculated'. This occurs if a pay has included loaded timesheets, however failed to calculate successfully, most commonly due to a zero or negative nett pay result.

Functional Verification

1. Ensure an employee has a Deduction in their active entitlements 2. Approve leave without pay (LWOP) for a full pay period 3. Calculate the employee's pay for this period 4. Confirm that the pay has saved with a negative or zero Nett Amount, and therefore does not have a Calculated Date 5. Navigate to the function 'Calculate Pay by Group' and retrieve the same employee pay period 6. Confirm that the payroll status of this employee's pay is displayed as 'Saved and Not Calculated'.

Solution Implemented

Updated the 'Calculate Payroll by Group' function to correctly display the payroll status as 'Saved and Not Calculated' when the employee pay has been saved without a Calculated Date and has associated timesheets.

HRPC-686 - Payroll Calculation new saved negative pay did not include amount in warning

Functional Issue

When calculating payroll that results in a negative pay, the negative pay amount is not included in the warning message.

Functional Verification

1. Calculate payroll for an employee in Adjust Payroll function. Manually enter a deduction pay item that has an amount greater than the income (base pay + any allowance). 2. Confirm that pay is saved but not calculated. The 'Pay Calculation Date' column is blank. 3. Confirm that the warning message is displayed includes the negative amount. i.e. "A negative pay has been generated for Employee Id: [Id] and Pay Period End Date: [date]. Normal nett pay amount is [negative pay amount]."

Solution Implemented

Added the normal nett pay amount in the warning message when a negative pay is calculated. The warning message is displayed as "A negative pay has been generated for Employee Id: [Id] and Pay Period End Date: [date]. Normal nett pay amount is [negative pay amount]."

HRPC-689 - Ship EPSC scales for 2016/2017

Functional Issue

The Employer Productivity Superannuation Contribution (EPSC) rates have not been updated.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the EPSC income thresholds (Other Tax Scales -> $AU - Australia -> AU_EPSC - EPSC): 4. Confirm that new EPSC income thresholds are available for the 1 July 2016. 5. Confirm that new EPSC income thresholds are available for the 1 July 2015.

Solution Implemented

Updated the EPSC other scales for the financial year 2017 and 2016. NOTE: For the latest rates go to http://www.eac.csc.gov.au/your-toolkit/epsc-rates/

HRPC-701 - Compulsory extra Student Loan (SLCIR) no longer being deducted

Functional Issue

NZ SLCIR Student Loan additional payment is not included in the payroll as expected. This occurs due to the associated SLCIR pay component being configured with a 'Derived Percentage From' using Total (while a value of Rate continues to generate into pay correctly).

Functional Verification

1. For a NZ Employee on a tax code of M SL (student load payments owing) 2. Ensure that a SLCIR Student Loan pay component is included in the employee's debtors & entitlements. Refer to recommended practice for SLCIR configuration and usage 3. Calculate the payroll for the next period 4. Confirm SLCIR payment is included in the pay

Solution Implemented

Additional validation has been added to ensure payments for SLCIR configured to be based on Total are generated into employee pay.

HRPC-707 - Calendar based increments are not as expected for some mid-month dates

Functional Issue

The Calendar based increments are incorrectly rounding up increment dates to the following month when running by 'Month' period type and the last increment date is mid-month. E.g. incorrect increment calculated for 1 May instead of 16 April.

Functional Verification

1. Open the function to 'Calculate due Increments - Calendar based' 2. Select one or more employees who are due an increment. E.g. 15 April 3. Set the increment period type to 'Months'. E.g. 12 months 4. Start the increment processing 5. Confirm that pending increments are generated with the correct due increment dates for the period specified. e.g. 12 months from the employee's last increment dated job/position record. NOTE increment dates may round to the next day of the month. e.g. last increment 15 April 2016 > due increment 16 April 2017.

Solution Implemented

Increment date rounding has been corrected for Calendar based increments when using the 'Months' increment period type.

HRPC-715 - Negative Manual Back Pay saves calculation date

Functional Issue

A manual back pay calculation that results in a negative pay was being generated with a saved Calculated Date.

Functional Verification

1. Generate a new entitlement set for an employee. Use an effective date that will impact ordinary pay periods that have been calculated. Reduce the base pay earnings within the new entitlement set. 2. Open the Calculate Manual Back Pays by Group ($HR.PAY.PAYRUN.R.PRC) function. 3. Enter the key fields for the function to calculate a manual back pay for the employee and pay period(s) impacted in step 1. 4. Calculate the manual back pay. 5. Load the back pay generated. 6. Confirm the pay has been saved but does not display a Pay Calculated date.

Solution Implemented

Changed the manual back pay process to ensure a negative back pay is saved without the calculation date.

HRPC-720 - Australian PAYG Withholding - Working Holiday Makers

Functional Issue

Australian ATO legislative changes for Working Holiday Makers made effective 1 Jan 2017. NOTE associated PAYG Payment Summary changes effective 1 July 2017

Functional Verification

Employee Maintenance: 1. Locate an Australian company employee who is an eligible Working Holiday Maker (WHM) 2. Load the current employee tax details 3. Confirm the Working Holiday Make checkbox is visible 4. Select the Working Holiday maker checkbox, select Ok and save the employee tax details change 5. Re-load the employee details and confirm the Working Holiday Maker checkbox is displayed as selected. NOTE a. WHM income type is only applicable to non-residents. b. A change in the tax income type for an employee must be indicated by a new employment period. E.g. Change to or from WHM income type must also be noted with a Termination and re-hire with new Job Details and hire date. Working Holiday Makers Tax Scales: 1. Navigate to the Manage Payroll tab 2. Navigate to the Working Holiday Maker income thresholds (Other Tax Scales -> $AU - Australia -> AU_WHM - Working Holiday Makers) 3. Confirm that new WHM income thresholds are available for the 1 January 2017. PAYG Withholding Calculation: 1. Load an ordinary pay period for the employee 2. Calculate the pay period with entitlements and timesheets loaded 3. Review the tax calculation section of the pay calculation audit 4. Confirm the withholding is calculated as a working holiday maker per the ATO PAYG withholding Schedule 15 tax table. NOTE Specifying the Working Holiday Maker income type in the employee's tax details will override the selected Tax Scale Code and other residential tax options. This is reflected in the Calculation Audit logging. PAYG Payment Summary: 1. Navigate to 'Adjust PAYG Payment Summary' function 2. Enter the key fields for an eligible working holiday maker employee, load the current financial year end date 3. Load the payment summary 4. Confirm the income type field has the code for a working holiday maker - 'H' 5. Confirm the details and values fields are loaded correctly for the employee 6. Print the PAYG payment summary 7. Confirm the PAYG payment summary is printed correctly, including the correct Income Type value. i.e. 'H' for Working Holiday Maker and 'S' for all other employees.

Solution Implemented

Enhanced the employee tax details to enable identification of an employee who is an eligible Working Holiday Maker (WHM). Updated the payroll tax process to apply the PAYG withholding as per the ATO rules for Working Holiday Makers (WHM). Updated the PAYG Payment Summary to include the new Income Type for Working Holiday Maker (WHM) - 'H'. For more information on the Working Holiday Makers legislation changes and withholding refer to the ATO site on Schedule 15: https://www.ato.gov.au/Rates/Schedule-15--Tax-table-for-working-holiday-makers/ NOTE: If an employee either becomes eligible as a Working Holiday Maker or progresses to a different income type (e.g. Resident), the ATO requires two separate payment summaries for their earnings on the different income types that occur within one financial year. To ensure the system generates these separate payment summaries correctly, create a Termination record as at the last day on the old income type and re-hire the employee as at the following day on the new income type (i.e. new Job details with new Date of Hire and new Effective Tax details with relevant tax withholding options).

HRPC-724 - Reportable FBT Exemption changes in 2017 PAYG payment summary

Functional Issue

Australian legislative changes 2017-18 include PAYG Payment Summary changes for Reportable FBT that is Exempt

Functional Verification

1. Logon as Payroll Officer and navigate to the Pay Component Maintenance 2. Confirm that the new 'FBT_Exempt' system config code type is available for selection on Pay Component Types : 100, 400, 410, 3000 and 4000 NOTE For confirmation of Reportable FBT duties that qualify as Exempt under section 57A of the FBTAA 1986 act, contact the ATO or search their website. 3. If your organisation qualifies for these exempt FBT duties, configure new pay component codes that capture this benefit amount. E.g. Under type 3000 for Non-Payroll reportable benefits, create a non-payment (Neither) pay component and check the 'FBT_EXEMPT' system config code. 4. Add this pay component to the entitlements of employees who perform these duties and receive the reportable exempt FBT. Alternatively include FBT amounts as manual items in relevant pay periods. 5. Process the pay periods where the employees receive FBT (i.e. including both non-exempt and exempt reportable FBT) 6. Process the EOFY Payment Summary load and transmissions that include reportable FBT 7. Navigate to the 'Load PAYG Payment Summary' function and specify the current financial year criteria 8. Process employee payment summaries including those employees receiving FBT 9. Navigate to the 'Adjust PAYG Payment Summary' function to review the loaded employee payment summary details 10. Confirm that the additional fields for FBT exemption appear on each payment summary i.e. 'Is the employer exempt from FBT under section 57A of the FBTAA 1986?' with No and Yes check boxes. 11. Navigate to the 'Print PAYG Payment Summaries' function and produce the printable version of employee payment summaries for the current financial year 12. Confirm that the payment summary includes Reportable FBT amounts which appear as: a. Non-exempt FBT total amount appears in the Reportable Fringe Benefits field and the check box for 'No' = not exempt is checked (i.e. for existing Reportable FBT amounts already configured and now considered 'non-exempt') b. Exempt FBT total amount appears in the Reportable Fringe Benefits field and the check box for 'Yes' = exempt is checked (i.e. newly configured 'exempt' Reportable FBT) c. If both exempt and non-exempt FBT amounts are included in the financial year, a second page for the PAYG Payment Summary is produced which only includes amounts for the additional FBT details d.. If an employee does not have any Reportable FBT then the Reportable Fringe Benefits field is empty and both 'No' and 'Yes' exempt check boxes are left blank 13. Navigate to 'Electronic PAYG Summaries' function and process the E-File EMPDUPE for the current financial year. 14. Confirm that the Reportable FBT amounts for both non-exempt and exempt are included. NOTE Other PAYG Payment summary reports that will include the FBT exempt field changes include: - Print PAYG Payment Summary across Multiple Companies - Print PAYG Payment Summary for terminated employees only

Solution Implemented

Added processing for the new 'Fringe Benefits Exempt' field in the PAYG Payment Summary process and reports. New System Config Code, 'FBT_EXEMPT', has been added to pay component maintenance to enable FBT exempt benefits to be identified. i.e. on Pay Component Types for Base Pay, Allowances, and non-payroll Benefits (100, 400, 410, 3000, 4000)

HRPC-726 - ATO SBR - Payment Summary Electronic Reporting changes effective 01/07/2017

Functional Issue

The ATO has updated the SBR electronic reporting format for the payment summary report. Updates relate to: 1. Working holiday maker income type. 2. Reportable exempt fringe benefits.

Functional Verification

Ordinary Employee: 1. Load an payment summary for the financial year ending 2017. 2. Process a test SBR submission via the test SBR payment summary report '$HR.PS.AU.TEST'. 3. Confirm the SBR system returns a Message accepted report outcome. 4. Review the SBR report submission via the SBR Submission Enquiry function. 5. Confirm the Report Version submitted was '04.00'. Working Holiday Maker: 1. Load a 2017 payment summary for an working holiday maker employee. 2. Confirm the adjust payment summary function displays the Income Type 'H'. 3. Process a test SBR submission for the employee. 4. Confirm the SBR system returns a Message accepted report outcome. Exempt Fringe Benefits: 1. Load a 2017 payment summary for an employee who has received reportable exempt fringe benefits. 2. Confirm the adjust payment summary displays the correct amount in the Fringe Benefits Exempt field. 3. Process a test SBR submission for the employee. 4. Confirm the SBR system returns a Message accepted report outcome.

Solution Implemented

Updated the SBR Payment summary reporting process per the latest ATO reporting format. NOTE: The ATO SBR service registry indicates the new report format is effective from 1 July 2017 in the production environment. For the full functionality of this enhancement the Framework External Integration May 2017 or Sep 2016 re-release package is required.

HRPC-738 - Deduction Summary Report not applying Pay Group criteria

Functional Issue

The Pay Group selection in the criteria for the Deduction Summary Report is not working. The report is generated regardless of the Pay Group criteria given.

Functional Verification

1. Open Deduction Summary report 2. Complete the required criteria including Pay Group 3. Run the report 4. Confirm that the report results are correct for the selected Pay Group.

Solution Implemented

Updated the record selection in the Deduction Summary report to include the Pay Group criteria value.

HRPC-851 - SBR PAYG submission failing with Period Type must be 'Payment'

Functional Issue

The new PAYG SBR report has been configured with the ATO activation dates which do not align with the Framework SBR reporting active dates.

Functional Verification

1. From Payroll Officer, select Electronic PAYG Payment Summary process 2. Select 'SBR' option 3. Enter the critieria to submit 2016/2017 FY employee pay to the ATO 4. Process All or selected employees for the submission 5. Ensure the 'Production Run' option is selected 6. Submit the process 7. Confirm that a successful message was received from the ATO SBR service. Confirm that the employees that were selected for transmission are now showing ATO transmission details which prevents SBR PAYG re-transmission.

Solution Implemented

Corrected the SBR PAYG Payment Summary Version end and start dates for production versions 2.00 and 4.00.

HRPC-866 - Leave Liability calculation ignoring balances in old Long Service Leave Code

Functional Issue

Leave liability is not including inactive leave accruals that have a non-zero pro-rata balance.

Functional Verification

1. Select an employee who will have an accrual replaced in their active entitlement set 2. Ensure that the leave accrual to be removed has a positive pro-rata balance only (i.e. actual entitlement balance = 0) 3. Create new entitlements for the employee, adding a new leave accrual and removing the accrual with only a pro-rata balance 4. Generate leave accruals for the current period, ensuring the new accrual is working correctly (i.e. pro-rata and/or entitlement balance) 5. Calculate the next month's leave liability for this employee 6. Confirm that the inactive leave accrual is still included in the calculation. i.e. pro-rata included in liability

Solution Implemented

Conditions have been corrected to only exclude inactive accruals from leave liability processing when both the entitlement balance and pro-rata are zero (includes recognising 0.01 and 0.0001 as zero for balances that have been transferred). NOTE negative balances and pro-rata on inactive accruals are still included in the leave liability. If negative accrual balances are not to be included in liability then adjust the balance with initial loads or accrual adjustments to zero out or transfer the negative values to active accruals.

RELEASE August 2016

HRPC-41 - Pay calculation report does not pick up all pays calculated for whole pay period

HRPC-43 - System Security not being applied to Payroll Enquiry

HRPC-76 - NZ termination pay - 8% of earnings not from anniversary date exactly but whole pay period

HRPC-432 - Retro Pays not calculating due to missing SGC fund (but no SGC default)

HRPC-435 - Extra super contributions at mid period acting position start

HRPC-438 - NZ Fixed salary contributions incorrect for multiple positions

HRPC-443 - NZ Pay not calculating due to Out of balance error related to child support

HRPC-464 - Group Pay Calculation failing

HRPC-465 - Negative net pays are not saved.

HRPC-474 - NZ Termination Public holiday not paid correctly for multiple regions

HRPC-481 - NZ EMS IRD report failing on DP

HRPC-488 - Providing a manual back pay solution for retro pay requirements

HRPC-489 - Termination Pay Run by Group does not pay out accrued annual leave

HRPC-506 - Retrospective Entitlement changes - cause Deduction Payee bank file issues

HRPC-522 - Base pay entitlements are reduced when the pay includes leave approved in Ci but cancelled in Ci Anywhere.

HRPC-523 - NZ IRD reporting processes run on DP do not return logged messages

HRPC-524 - Error running KiwiSaver Employment Details (KS1) - phone numbers including +

HRPC-530 - Pay Period Type not working in Pay Component Summary Report

HRPC-531 - Base pay reversals for retrospective leave are not posting to the same account as the base pay being reversed.

HRPC-534 - SBR Payment Summary errors on transmission

HRPC-546 - Pay can incorrectly error on accrual balance exceeded when retrospective leave is processed from Ci Anywhere.

HRPC-548 - Retro paid leave (unpaid) doesn't reduce Ord Hours

HRPC-550 - Payroll calculation Status does not change if a CiAnywhere Timesheet has been modified.

HRPC-553 - Timesheets that were unpaid in previous pay are not being included in current pay

HRPC-559 - Additional Banking calculation incorrect for prepaid Ci Anywhere leave

HRPC-560 - Infrastructure changes for the cloud 5 environment

HRPC-562 - ATO Updates Pay as you go withholding (PAYGW) electronic report update PSAR v11.0.2

HRPC-563 - Pay Advice reports - not using Accrual Config Code description for User Defined codes (e.g. U_AG_Annual)

HRPC-565 - EOFY - Payment Summary not picking up Branch Number

HRPC-566 - Need to be able to Print PAYG Payment Summaries for Terminated Employees ONLY

HRPC-570 - Pay by Group errors due to one employee's invalid Pay Group

HRPC-579 - Westpac NZ Bank Download file has incorrect format

HRPC-581 - SBR TFN & Payment Summary - translate State field to ATO values (QLD, TAS, NSW, VIC, ACT, WA, SA, NT, AAT)

HRPC-587 - Termination Pay Process Errors with "Value to add was out of range" error.

HRPC-595 - Increment Processing to ignore FTE when calculating

HRPC-601 - Australian Tax Scale changes Effective 01/10/2016 (Region $AU)

HRPC-604 - New Data Management for Region System Data

HRPC-606 - KED schedule error - blank Salutation field is attempting to use code '_' in report

HRPC-627 - Increment processing for Calendar with minimum service can time out for the first increment period

HRPC-41 - Pay calculation report does not pick up all pays calculated for whole pay period

Functional Issue

The Pay Calculation report only contains pay generated for the Pay Period End Date specified in the criteria. Subsequently mid pay period employee pays are not included for what is considered the last pay period. Such as Correction, Special and Bonus pay.

Functional Verification

1. Open one of the Pay Calculation Reports: * Pay Calculation Report * Pay Calculation Report across Multiple Companies * Pay Calculation Report (inc Historical Data) 2. Ensure the Report Start Date and Report End Date criteria are displayed. 3. Fill all the mandatory fields and leave the Document Type blank. 4. Confirm that all pays calculated between the given Start and End Date are displayed in the report, including mid-period Special, Correction and Bonus Pay.

Solution Implemented

The Pay Period End Date criteria in the Pay Calculation reports has been replaced with a Report Start and End Date to enable all pays calculated within a specified period to be included in the report.

HRPC-43 - System Security not being applied to Payroll Enquiry

Functional Issue

Security access as determined by a user's Security Category is not applied to the Payroll Enquiry function. i.e. User is able to run payroll/financial queries on employees they do not have access to.

Functional Verification

1. Create a new Security Category which limits access to a specific group of employees. i.e. In the Employee Access section, specify criteria that represents a subset of employees. E.g. all employees employed in Company 1 2. For a selected User, add this new Security Category to their access details in User Maintenance. 3. Login as the new User. 4. Open the Payroll Enquiry and run an enquiry for the required criteria. E.g. for a date range 5. Confirm that the returned records only include the employees that user has been given access to in their Security Category.

Solution Implemented

The Payroll Enquiry function has been updated to respect the user's Employee access as defined by Security Category and its Employee Security access criteria. NOTE Additional security on Financial access (Ledger/Account) is only applied to Payroll Enquiry when the user drills into the Account Details enquiry function.

HRPC-76 - NZ termination pay - 8% of earnings not from anniversary date exactly but whole pay period

Functional Issue

For the New Zealand termination calculation that pays 8% of earnings, all income is included for the pay period that the anniversary date falls within. This results in the employee being overpaid for 8% of the proportion of a pay that occurs prior to their anniversary date.

Functional Verification

1. Create or test an employee who has a hire date on the first of the month. 2. Assign the employee to a pay group that is paid monthly on the 15th of every month. i.e. So the employee's anniversary date falls at the midpoint of a pay period. 3. Calculate ordinary pays for the first 13 months of employment. 4. Create a termination activity for the 15th of the following month. 5. Calculate the termination pay. 6. Review the calculation audit. 7. Confirm that the termination earnings has been calculated from the anniversary date to the termination date. i.e. Only part of the pay containing the anniversary date is included in the total earnings used for the 8% calculation. In this example, approximately half of the first pay period is included in the 8% earnings. i.e. The value of the termination earnings does not include earnings before the anniversary date that occur in the anniversary pay period. NOTE: The earnings to exclude from the pay period containing the employee's anniversary date, is calculated using a proportion of the employee's work pattern. i.e. (work pattern units before anniversary / total work pattern units) * anniversary period earnings

Solution Implemented

Amended the New Zealand termination calculation to calculate termination earnings from the actual anniversary date exactly. This is achieved by excluding earnings for work occurring prior to the anniversary date in the pay that the anniversary occurs in (using proportioned values based on work pattern).

HRPC-432 - Retro Pays not calculating due to missing SGC fund (but no SGC default)

Functional Issue

Imported superannuation pay items would error during retrospective pay process due to missing superannuation fund code.

Functional Verification

1. Import superannuation pay items into an ordinary pay. 2. Calculate the pay. 3. Create a retrospective impact to the pay by creating a new entitlement set as at the start of the calculated pay period. 4. Increase the base pay entitlement amount within the new entitlement set. 5. Calculate the following pay period with the Retrospective Changes option selected. 6. Confirm the calculation has completed without an error relating to the imported superannuation item. 7. Review the back pay and confirm the retrospective pay has not processed the imported superannuation item - superannuation items from impacted pay periods are not processed.

Solution Implemented

Amended the retrospective pay process to ensure imported or manually entered superannuation pay items are not processed per the generated superannuation items.

HRPC-435 - Extra super contributions at mid period acting position start

Functional Issue

Extra superannuation contributions are generated when processing annual leave with loading during a pay period that an acting position starts.

Functional Verification

1. Create an acting position that becomes effective mid pay period. 2. Create approved annual leave for a day in the same pay period before the acting position is effective. The annual leave loading should be part of the annual leave entitlement. 3. Calculate the pay period. 4. Review the leave items generated. 5. Confirm the annual leave and loading are generated correctly. 6. Review the superannuation items generated. 7. Confirm the employee and SGC contributions are generated correctly for the primary position's superannuation ordinary time earnings. 8. Confirm the employee and SGC contributions are generated correctly for the acting positions superannuation ordinary time earnings.

Solution Implemented

Changed the pay process to ensure the superannuation contributions are generated correctly within a pay period that an acting position starts and the pay includes annual leave with loading.

HRPC-438 - NZ Fixed salary contributions incorrect for multiple positions

Functional Issue

The New Zealand pay calculation incorrectly calculates superannuation contributions for employees with a secondary position who are on a fixed salary superannuation contribution. i.e. the current salary is used instead when secondary position hours are worked.

Functional Verification

1. Locate an employee with an secondary position with base pay earnings. 2. Assign employee superannuation with the Salary Calculation Method 'Use Fixed Salary'. 3. Confirm the Superannuation control variable Allow Split Costing (HR_SUP_COST_SPLT) is set to the shipped value 'Yes'. 4. Calculate an ordinary pay period. 5. Review the calculation audit. 6. Confirm the total employee contribution is calculated correctly per the fixed salary. 7. Confirm the employee contribution for each position is calculated correctly based on the total employee contribution multiplied by the ratio of position pay earnings / total pay earnings. 8. Confirm the total company contribution is calculated correctly per the fixed super salary. 9. Confirm the company contribution for each position is calculated correctly based on the total company contribution multiplied by the ration of position pay earnings / total pay earnings. 10. Confirm the pay items are generated correctly per the calculation audit calculations. Note: The ESCT calculation will have split the company contribution item into an net contribution and ESCT items.

Solution Implemented

Amended the New Zealand pay calculation to calculate contributions correctly for fixed salary superannuation employees with a secondary position.

HRPC-443 - NZ Pay not calculating due to Out of balance error related to child support

Functional Issue

1. Recalculating NZ termination pay results in an out of balance error when the employees' entitlements includes child support deductions. Manually entered child support items also results in an out of balance error during pay calculation. 2. Processing child support without the protected earnings pay component defined that includes the NZ region 'CHILD_SUPP' configuration code, results in an out of balance error.

Functional Verification

NZ Termination pay recalculation: 1. Create a termination activity for an employee with child support assigned to their entitlements. 2. Calculate the termination pay. 3. Remove the 8% termination earnings pay item. 4. Add a new 8% termination earnings pay item for a different amount. 5. Clear the load Termination, Entitlements and Timesheets check boxes. 6. Recalculate the pay. 7. Confirm the pay has completed without error. 8. Confirm the 8% termination earnings is paid per the amount entered. 9. Confirm the child support is deducted from the ordinary pay and termination leave correctly. NZ Ordinary Pay manual child support entry: 1. Load an ordinary pay period for an employee with child support assigned to their entitlements. 2. Manually enter pay items for base pay and the child support deduction. 3. Clear the load Entitlements option. 4. Calculate the pay. 5. Confirm the pay calculates without error. 6. Confirm the ordinary and child support is paid per the entered amounts. Child support protected earnings not configured: 1. Navigate to the Pay Component Types section of the System Admin Console. 2. Maintain the New Zealand child support protected earnings pay component, if already defined. 3. Clear the NZ region configuration code 'CHILD_SUPP' and save the change. 4. Load an ordinary pay for an employee with child support assigned to their entitlements. 5. Calculate the pay with entitlements loaded. 6. Confirm the pay completes with a warning (i.e. stating that a pay component is not configured for protected earnings) 7. Confirm the child support is deducted per the entitlements. 8. Review the calculation audit and confirm the audit log advises that there is child support configured but the protected earnings is not configured. 9. Return the protected earnings pay component configuration to have the 'CHILD_SUPP' configuration code selected, or define the component. Note: If the component has to be defined, the child support protected earnings is defined in the amount field as '60.0' for 60%. 10. Recalculate the pay with entitlements loaded. Confirm that the warning no longer occurs. 11. Review the calculation audit and confirm the child support protected earnings is calculated correctly.

Solution Implemented

Changed the pay calculation to ensure New Zealand child support is calculated correctly and does not fail with errors when: 1. manually entered child support deductions are included in an employee's pay 2. recalculating a termination pay containing a child support deduction 3. the child support protected earnings pay component is not configured.

HRPC-464 - Group Pay Calculation failing

Functional Issue

If an employee is setup with an incorrect Pay Group, the pay calculation for all other employees correctly listed for the Pay Group is failing from the Calculate Payroll by Group function.

Functional Verification

1. Assign an employee to a Pay Group where the pay period does not exist for the pay basis that the employee is on. E.g. Pay Group A is for Salaried employees only, but an Hourly paid employee is assigned to this pay group. 2. Run the Calculate Payroll for the Pay Group created for Salaried employees only. 3. An error is displayed for the employee with incorrect an pay period, saying the Pay Periods do not exist (i.e. due to missing Hourly pay basis). All other employees who are to be paid by Salary are processed normally.

Solution Implemented

The Calculate Payroll by Group validation has been corrected to ensure that a valid Pay Period End Date is used for each employee.

HRPC-465 - Negative net pays are not saved.

Functional Issue

When the pay calculation is processing retrospective unpaid leave and the net pay results in a negative value, the pay is not saved. This prevents the user from analysing and easily correcting the pay as required.

Functional Verification

1. Calculate an ordinary pay period for an employee who inputs timesheets and leave via Ci Anywhere. 2. Bank download the pay. i.e. Pay is marked as 'Paid' 3. Enter and approve LWOP (leave without pay) retrospectively. i.e. Leave dates occur in the finalised pay period. 4. Calculate the following pay period, ensuring to load timesheets. NOTE: The timesheets loaded into the pay will include reversal base pay lines for the previously paid period. Leave is without pay, therefore resulting in a negative pay. 5. Confirm the pay calculation completes without an out of balance error. 6. Confirm the calculated pay displays a negative pay warning message. 7. Confirm the pay has saved generated entitlement and timesheet pay items. 8. Confirm the pay does not have a net pay or additional banking pay items. 9. Confirm the pay or the saved pay items do not have a calculation date displayed. 10. Enter corrections to the pay items in order to proceed with a valid non-negative pay. i.e. in order to achieve a zero net pay. 11. Re-calculate the pay with the load timesheets option selected. NOTE: The loading timesheet option is required on a recalculation of the pay to ensure the loaded timesheet lines are stamped as paid and therefore not included in a future pay. 12. Confirm the pay is saved without error or warning messages displayed. 13. Confirm the pay is saved with calculation dates displayed on the pay and the pay items included. 14. Confirm the timesheet lines are locked and the pay details are saved to them.

Solution Implemented

Amended the pay calculation process to enable the generated items to save for a negative pay. NOTE Net Pay and banking items are not generated when a negative occurs. Pays without a Net Pay item are not included in bank downloads nor posted (i.e. do not have calculated dates). These pays are marked as saved only (i.e. un-calculated) until corrected by the user (or deleted).

HRPC-474 - NZ Termination Public holiday not paid correctly for multiple regions

Functional Issue

The NZ Termination process uses the first defined public holiday pay component when paying out post-termination public holidays. For an implementation using two payroll regions (e.g. $AU and $NZ), the system will have two separate pay components defined which are used to pay public holidays that occur in a normal pay period. However, the NZ termination process can use the incorrect public holiday leave Pay Component Code due to the assumption to use the first pay component code returned that has the public holiday config code selected.

Functional Verification

For Payroll implementations that pay employees in multiple regions (e.g. have both Australian and New Zealand payroll companies): 1. Ensure that there are separate public holiday pay components configured to be used for each region 2. Ensure that a holiday category is configured for each region and each holiday date has the region-specific pay component selected. 3. Run a termination pay for a New Zealand employee that is entitled to a pay out of leave accruals, and where a public holiday occurs after the termination date but within the period for the employee's remaining, unused accrual balance. E.g. 4 weeks of annual leave remaining and a public holiday occurs in the 4 weeks after the Termination Date 4. Confirm that the termination pay has paid out the employee's leave accrual and has included the pay out of public holiday(s). 5. Confirm that the public holiday appears as a pay item with the correct leave pay component code defined in the employee's Holiday Category.

Solution Implemented

The NZ termination pay process has been modified to ensure that the correct public holiday leave pay component code is used for an employee based on the Holiday Category that they are assigned to (via their job).

HRPC-481 - NZ EMS IRD report failing on DP

Functional Issue

The EMS (Employer Monthly Schedule) process fails with OutOfMemory error when run on the DP. Running the process locally (2tier) succeeds without error.

Functional Verification

1. Login as Payroll Officer 2. Open the Employer Monthly Schedule (IR 348) process function 3. Complete the monthly report criteria 4. Submit the process to the DP 5. Confirm that the process succeeds without error. NOTE: The process log file containing errors and messages is saved to the Destination Folder specified by the user.

Solution Implemented

The EMS process has been optimised when searching for employee leave taken in the reporting period that has been pre-paid in an earlier period. NOTE: A log file containing messages generated by the process is saved to the Destination Folder specified by the user.

HRPC-488 - Providing a manual back pay solution for retro pay requirements

Functional Issue

The 'Calculate Manual Back Pays by Group' function required changes to: 1. Avoid issues resulting from attempts to generate retrospective timesheet lines for the impacted pays. i.e. Only pay items are generated by the manual back pay process. E.g. Including issues resulting from retrospective changes to position or timesheet format on employees who submit timesheets to be paid. 2. Provide the user with more control over the back pay changes required. E.g. Improved employee and pay component selection. 3. Provide the user with a viable replacement to automatic retrospective pay functionality which is based on impacted pays as determined by the system when a retrospective change to an employee is detected.

Functional Verification

1. From Payroll Officer, open the "Calculate Manual Back Pays by Group" function 2. Complete the criteria for the required back pay. i.e. Company, Pay Group, Pay Period End Date (date of the back pay which is not driven by pay group dates), 3. Enter the From and To Date to specify employee pays to be included. i.e. the impacted pay range 4. Confirm the Pay Components to Process grid loads only pay components included in the impacted pays. 5. Review and if required, deselect unwanted pay components to exclude from the back pay process. 6. Use the Employees criteria options to retrieve and select the employees who will receive a back pay. 7. Confirm only the employees with pays in the period selected are loaded into the employee grid. 8. Start Processing 9. On completion of the process, review the processing log generated to view errors and warnings. 10. Click the Retrieve button to view the status of each employee back pay. NOTE: A successful employee back pay will have a "Processed" status, while a back pay that did not calculate successfully will have either a "Saved and not Calculated" or "Not Processed" status. Refer to the log to view the error or warning messages associated with these uncalculated pays. 11.To view an employee's generated back pay, click the "Adjust Back Pay for Employee" function link. 12. If modifications are required to correct an employee's back pay, note that: a. additional pay items can be added to the Back Pay to negate or adjust the generated back pay items b. when modifying a back pay by adding new pay items, set the "Item End Date" field for the item in order to specify which pay period the adjustment relates to and calculates the appropriate tax amount. New pay items will default to the Pay Period End Date of the generated Back Pay, and calculate the tax accordingly as at that date. c. generated back pay items included from the employee's entitlements can be deleted. E.g. unwanted allowance or deduction d. leave generated by the back pay process cannot be deleted. E.g. Negative and positive leave or public holiday items e. a back pay that results in a negative Net Pay will be saved. This allows the user to delete or modify the generated back pay as required. E.g. if LWOP was entered retrospectively. The status of a negative pay will be "Saved and not Calculated". f. when an employee back pay includes leave items, ensure the "Load Timesheets" option is selected when re-calculating after modifying the generated back pay. This ensures the leave and associated timesheet lines are marked as paid and not loaded into the next calculated pay for the employee. g. superannuation is calculated based on the final gross amount due the employee. i.e. company super, compulsory member contributions. h. superannuation pay items of impacted pays do not have back pay adjustments generated. i.e. no negative and positive back pay superannuation items. i. deduction payee pay items in impacted pays do not have back pay adjustment items generated. i.e. no negative and positive back pay deduction payee items. NOTE Re-submitting the same Back Pay process for employees showing a successfully "Calculated" back pay, will delete and re-calculate each specified back pay. i.e. A bulk pay deletion is not necessary in this scenario.

Solution Implemented

Enhancements to the 'Calculate Manual Back Pays by Group' function include: 1. Pay Components are loaded based on the impacted employee pays included in the date range specified. i.e. Obsolete pay components and non-applicable Pay Component Types are excluded from the list provided. 2. Employee selection has been improved to use the same advanced criteria as the Pay By Group functions. 3. Function links have been added to provide quick access to related functions, "Adjust Back Pay for Employee" and "Delete Pays by Group" 4. All pays marked as "Impacted" due to a retrospective change to employee payroll details, will be cleared of this impact after the running of a Manual Back Pay on those employees selected. i.e. the impacted pays dated on or before the Back Pay Pay Period End Date. This will prevent future pays from including the auto-generated retro pay changes (if that option is selected in pay calculation). 5. Retrospective timesheet lines are not generated by the Manual Back Pay process. Only pay items are generated to achieve the back pay adjustment. i.e. negating impacted paid items and generating the new paid items based on the updated employee pay details (i.e. changed entitlement rates, cost accounts) 6. A new function parameter has been added to hide the Auto Retro Pay option ('I want to perform an automatic retrospective pay'). i.e. The Manual Back Pay function by default will not rely on auto-retro impacted pay items, but rather provide the user with complete control of generating the back pays required. Enhancements to the "Adjust Back Pay for Employee" function include: 1. Pays resulting in a negative net pay are saved but not marked as calculated. i.e. will not be posted nor bank downloaded. This allows the payroll officer to correct or delete the pay as required. 2. The fields "Item End Date" and "Item Start Date" are modifiable for added pay items. This ensures the correct tax calculation for the associated pay period as determined by the payroll officer. NOTE: Entering the "Item End Date" is sufficient and will default the same date to "Item Start Date" field. 3. Position Code field is always shown in Back Pays. i.e. to enable a change in position code to be displayed

HRPC-489 - Termination Pay Run by Group does not pay out accrued annual leave

Functional Issue

The Termination Pay Run by Group does not pay out accrued annual leave.

Functional Verification

1. Open the function for Termination Pay Run by Group. NOTE this function does not appear on a shipped menu so will require packaging changes to appear permanently for your payroll officer who requires the ability to run termination pay for multiple employees. E.g. bulk redundancies. 2. Ensure the 'Termination' and 'Leave Accrual Payout' options are selected. 3. Select employees who require termination pay on the same date. E.g. multiple redundancies 4. Confirm that the termination pay is generated for all selected employees. 5. Confirm that the annual leave is paid out in the termination pay.

Solution Implemented

The Termination Pay Run by Group function has been corrected to pass the Termination and Leave Accrual Payout options selected to the termination pay process, thereby ensuring the leave accruals are paid out on termination if requested.

HRPC-506 - Retrospective Entitlement changes - cause Deduction Payee bank file issues

Functional Issue

Retrospective back pay can result in errors due to negative deduction payee amounts in the bank download files. i.e. For employees with deductions to a payee defined in their entitlements and impacted by retrospective entitlement changes that result in a back pay (either via automatic retro pay or manual back pay).

Functional Verification

1. Locate an employee with a deduction payee pay component within their entitlements. 2. Calculate an ordinary pay period. 3. Create an impact to the base pay entitlements effective at the start of the ordinary pay period calculated. E.g. add new entitlements dated prior to the Pay Period End Date 4. Calculate the following ordinary pay period and ensure the Retrospective Changes process option is selected. 5. Confirm the ordinary pay is calculated correctly without error. 6. Confirm a back pay has been calculated for the impacted previous pay period. 7. Review the back pay items generated and confirm the process did not generate items for the deduction payee component. 8. Bank download both the ordinary and back pay. 9. Confirm the bank download does not contain a banking entry per the deduction payee configuration.

Solution Implemented

Amended the back pay calculation to exclude generating adjustment pay items for payee deductions.

HRPC-522 - Base pay entitlements are reduced when the pay includes leave approved in Ci but cancelled in Ci Anywhere.

Functional Issue

Base pay entitlements are reduced by leave that has been approved in Ci but cancelled in Ci Anywhere. Where the cancelled leave was for the entire pay period, the base pay is reduced to zero and the employee is not paid his base pay entitlement.

Functional Verification

1. Create an employee for testing purposes. 2. Give the employee job details effective as at 01-Jan-2015: the employee uses timesheets for exception entry. 3. Give the employee an entitlement effective as at 01-Jan-2015: the entitlements includes an accrual of annual leave. 4. In Ci Leave Maintenance, create an approved leave request commencing 04-Jan-2016 and ending 08-Jan-2016. 5. Log on to Ci Anywhere as a user with access to the payroll administration functions. 6. Navigate to the Leave Upgrade function. 7. In the Upgrade From field, enter 01-Jan-2016. 8. In the Employee(s) to Process field, enter the ID of the employee created in Step 1. 9. Run the upgrade. 10. Navigate to the Leave function. 11. In the Search field, enter the ID of the employee created in Step 1. 12. Search for leave upgraded for this employee. 13. Select the approved leave request upgraded in Step 9. 14. Select View leave details from the available actions. 15. Select Cancel leave from the available actions; confirm the action. 16. Select Approve from the available actions. 17. Log on to Ci as a user with access to the payroll officer functions. 18. Navigate to Adjust Payroll. 19. Calculate the pay period including the cancelled leave request. 20. Verify that base pay entitlements are paid for the pay period. 21. Verify that the cancelled leave is processed but does not affect the pay.

Solution Implemented

The process by which timesheet entries are loaded into payroll and turned into pay items has been modified to ensure that cost accounts and pay rates are resolved and set before the entries are aggregated for payment. This ensures that timesheet lines from Ci can be properly aggregated with timesheet entries from Ci Anywhere. Where a Ci leave request is cancelled in Ci Anywhere, this ensures that timesheet lines and timesheet entries can properly cancel each other.

HRPC-523 - NZ IRD reporting processes run on DP do not return logged messages

Functional Issue

The NZ IRD reporting processes do not receive logged messages when submitted to the DP. i.e. EMS (Employer Monthly Schedule IR 348) KED (KiwiSaver Employment Details KS1) EDF (Electronic Deduction Form IR 345)

Functional Verification

1. Login as Payroll Officer 2. Open the KiwiSaver Employment Details KS1 process function 3. Complete the report criteria 4. Submit the process to the DP 5. Confirm that a message appears informing that a process log is saved to the Destination Folder 6. Confirm that a process log file containing errors and messages is saved to the Destination Folder specified by the user. The file is named as per the date, time and process name. E.g. 201610081158-KEDFile001.log

Solution Implemented

The NZ IRD reporting and ATO Load Payment Summaries processes have been updated to include the saving of a log file to the specified Destination Folder or the user's Reports and Files area.

HRPC-524 - Error running KiwiSaver Employment Details (KS1) - phone numbers including +

Functional Issue

The KiwiSaver Employment Details (KS1) function returns an error of invalid character when the employee's phone number contains '+' character.

Functional Verification

1. Run the KiwiSaver Employment Details (KS1) for a company. Ensure there are active Kiwisaver employees included with phone numbers containing invalid characters. E.g. '+', '(', ')' or '/' Ensure there are active employees included with address lines containing punctuation characters. E.g. '/' ',' or '.' 2. Confirm that the process completes without invalid characters error.

Solution Implemented

Updated the KiwiSaver Employment Details (KS1) processing by removing invalid phone and address characters not accepted by the IRD. E.g. + / ( ) - \ [ ] and punctuation . ,

HRPC-530 - Pay Period Type not working in Pay Component Summary Report

Functional Issue

The 'Pay Period Type' extended criteria displays an empty list in the Pay Component Summary reports. Users are not able to use the criteria for the report.

Functional Verification

1. Open the Pay Component Summary report. 2. Fill in the mandatory key fields. 3. Add an Extended Criteria of Pay Period Type. Open the picklist. 4. Confirm that the list of Pay Period Type values is displayed in the picklist. 5. Select one of the valid values. Run the report. 6. Confirm that the report is generated. If required, confirm the use of Pay Period Type criteria for the associated reports: 1. Pay Component Summary by Department 2. Pay Component Summary by Pay Location 3. Pay Component Summary by Pay Locn/Dept

Solution Implemented

Added 'Pay Period Type' to the related view to enable the extended criteria to support this field and provide a populated list for the Pay Component Summary reports.

HRPC-531 - Base pay reversals for retrospective leave are not posting to the same account as the base pay being reversed.

Functional Issue

When base pay reversals are generated for leave retrospectively entered in to Ci Anywhere, the reversal is costed to the same account as the leave pay item. This results in a journal imbalance when the cost account for leave is not the same as the cost account for base pay.

Functional Verification

1. Create an employee for testing purposes. 2. Give the employee job details effective as at 01-Jan-2015: the employee uses timesheets for exception entry; the timesheet system is configured to post to payroll and to cost ledgers; the timesheet format includes a leave format line that is enabled for costing; the leave pay component is configured to use a recovery account in timesheets. 3. Give the employee entitlements effective as at 01-Jan-2015: the entitlement includes an accrual reduced by the leave pay component configured in Step 2. 4. Give the employee a user account with access to the Ci Anywhere employee self-service functions. 5. Log on to Ci as a user with access to the payroll officer functions. 6. Navigate to Adjust Payroll. 7. Process and generate bank downloads for each pay period in January, 2016, up to and including 08-Jan-2016. 8. Log on to Ci Anywhere as the user configured in Step 4. 9. Navigate to the My Leave function. 10. Submit a leave request for one week of leave commencing 04-Jan-2016 and ending 08-Jan-2016. 11. Log on to Ci Anywhere as the user's supervisor. 12. Navigate to My Tasks. 13. Approve the leave submitted in Step 7. 14. Log on to Ci as a user with access to the payroll officer functions. 12. Navigate to Adjust Payroll. 13. Calculate the next unprocessed pay in January, 2016, loading timesheets and entitlements. 14. Verify that pay items for the period being calculated have been generated from the employee's entitlements. 15. Verify that pay items have been generated for the retrospectively entered leave being paid. 16. Verify that base pay reversal pay items have been generated from the leave being paid. 17. Verify that the base pay reversals are costed to the same account as the base pay entitlement pay items.

Solution Implemented

The process by which timesheet entries are loaded into payroll and turned into pay items has been modified to ensure cost accounts for base pay reversals are set to the cost account derived for the base pay entitlement.

HRPC-534 - SBR Payment Summary errors on transmission

Functional Issue

The following taxonomy error occurs while processing the Payroll Payment Summary PAYG report to the ATO: SBR Validation Error: ERROR_INVALID_DIMENSION : The dimension "{http://sbr.gov.au/dims/RprtPyType.02.03.dims} ReportPartyTypeDimension" does not exist (domain ={http://sbr.gov.au/dims/RprtPyType.02.03.dims} ReportingParty).

Functional Verification

1. From Payroll Officer 2. Open Electronic PAYG Summaries (Payment Summaries) 3. Select SBR transmission option 4. Complete the criteria for the PAYG financial year. Ensure valid credentials are selected and working prior to transmission (i.e. refer to SBR Credential Maintenance and Taxonomy Diagnostics). 5. Start Processing 6. No transmission error "ERROR_INVALID_DIMENSION" is received. NOTE If validation errors are received for specific employee details, correct these prior to further transmission attempts.

Solution Implemented

Required SBR system data for the payment summary version 002 has been released.

HRPC-546 - Pay can incorrectly error on accrual balance exceeded when retrospective leave is processed from Ci Anywhere.

Functional Issue

"Available accrual exceeded" errors would prevent a pay from calculating. This occurred because the leave taken processor was generating duplicate reductions for retrospective leave from Ci Anywhere, and when the employee was close to his minimum permitted accrual, the duplication would cause leave taken to appear to exceed the available accrual.

Functional Verification

1. Create an employee with job details and an entitlement to a roster-based/manual accrual. 2. Create an initial load for the accrual to set the initial balance to 40 units. 3. Calculate and generate a bank download file for a pay period. 4. For the same pay period, using a leave type that reduces the manual accrual from Step 1, submit and approve 40 hours of leave. 5. Verify that the forecast available leave in Ci Anywhere My Leave is zero hours. 6. Calculate the next pay period, loading the retrospective leave from Ci Anywhere timesheets. 7. Verify that the pay calculates without error. 8. Verify that the employee's roster-based accrual has been reduced to zero hours.

Solution Implemented

The process for loading timesheets into payroll now ensures that loaded timesheet entries can be identified as such by completing the pay period date on Ci Anywhere leave timesheet records prior to processing the accrual reduction. This allows the accrual reduction process to properly determine whether a timesheet entry has already been processed in a pay.

HRPC-548 - Retro paid leave (unpaid) doesn't reduce Ord Hours

Functional Issue

Ci Anywhere Leave - A pay's ordinary hours are not being being reduced when a retrospective leave request for unpaid leave is submitted for an employee's secondary position from the Ci Anywhere Leave app.

Functional Verification

1. In Ci Anywhere create an employee with primary and secondary positions. 2. Configure the "Timesheet Usage" to "Use Timesheet Only" on the primary position. 3. Configure the "Timesheet Usage" to "Exception Entry" on the secondary position. 4. Calculate pay for a pay period and bank download the pay. 5. Using the secondary position retrospectively add a leave without pay request via Ci Anywhere for the pay period in step 4. 6. Approve the leave submitted in step 5. 7. Calculate the pay for the next period after the period in step 4. 8. Confirm a negative "Retro Paid Leave Reversal" pay item has been generated. 9. Confirm a "Retro Paid Leave" pay item has been generated for the leave request. 10. Confirm the base pay ordinary hours has been reduced by the leave without pay request.

Solution Implemented

Retrospective leave submitted against an employee's secondary position in Ci Anywhere is now being correctly processed in the pay calculation and reduces ordinary hours.

HRPC-550 - Payroll calculation Status does not change if a CiAnywhere Timesheet has been modified.

Functional Issue

Ci Anywhere Timesheet - When using the Calculate Payroll by Group function to calculate pays for selected employees, the Status field in the Employees grid would not change from "Calculated" to "Timesheet Modified" for pays with CiAnywhere timesheets that had been modified after the pay was calculated.

Functional Verification

1. In Ci Anywhere create an employee with a primary position and configure it with a "Hourly" Pay Basis and Timesheet Usage set to "Use Timesheet Only". 2. Using Ci Anywhere enter timesheets for a pay period. 3. Calculate the pay for the pay period in step 2. 4. Using the Calculate Payroll by Group function, choose to process selected employees and filter on the employee from step 1. 5. Confirm that the Status for this employee pay is "Calculated". 6. Using Ci Anywhere add another timesheet entry for the same pay period in step 2. 7. Repeat Step 4. 8. Confirm that the Status for this employee pay is "Timesheet Modified". 9. Confirm a warning message is displayed indicating that timesheets have been added or modified since the pay was calculated and should be recalculated. 10. Using the Calculate Payroll by Group function re-calculate the pay for the employee. 11. Pay calculates without error and includes the timesheet entry from Step 6. Confirm that the Status for this employee pay is now "Calculated"

Solution Implemented

The Status in the Employees grid on the Calculate Payroll by Group function will now correctly show "Timesheet Modified" whenever Ci Anywhere timesheets have been added or modified since a processed pay was last calculated.

HRPC-553 - Timesheets that were unpaid in previous pay are not being included in current pay

Functional Issue

Ci Anywhere Timesheets - Timesheets that have been entered retrospectively via the Ci Anywhere Timesheets app for Hourly employees into a previous calculated pay period do not get included in the pay calculation in the next pay period when the "Exclude Employees With No Timesheets" calculation option is ticked.

Functional Verification

1. In Ci Anywhere create an employee with primary positions. 2. Configure the "Pay Basis" to "Hourly". 3. Configure the "Timesheet Usage" to "Use Timesheet Only". 4. Enter and approve some timesheet entries for a single period via Ci Anywhere for the employee. 5. Calculate a pay for the pay period with the timesheet details entered in step 4. 6. Bank download the pay. 7. Enter and approve another timesheet entry via Ci Anywhere for the employee using the same period from steps 4 and 5. 8. Using the Adjust Payroll function calculate a pay for the period after the one used in step 5 ensuring the "Load Timesheets" and "Exclude employees with no timesheets" calculation options have been ticked. 9. Confirm the timesheet entry from step 7 appears in the "Timesheets For This Period" section. 10. Confirm the pay is calculated with pay items generated from the timesheet entry from step 7. 11. Repeat steps 4 to 8 using the Calculate Payroll by Group function instead of the Adjust Payroll function to calculate multiple employee pays. 12. Confirm that the timesheet entry for the previous period is included in the current pay period calculation.

Solution Implemented

The payroll process now correctly identifies unpaid timesheets entered retrospectively via Ci Anywhere into a previous pay and now includes them in the current pay calculation.

HRPC-559 - Additional Banking calculation incorrect for prepaid Ci Anywhere leave

Functional Issue

Ci Anywhere Leave - When a pay is calculated with multiple periods of prepaid leave entered via Ci Anywhere for an employee configured with additional banking, only 1 period of additional banking is calculated.

Functional Verification

1. Create an employee configured with additional banking. 2. Using Ci Anywhere request and approve 2 full periods of leave in the one leave request and ensure it is marked as "Pay in Advance". 3. Using the Ci Adjust Payroll function, calculate a pay in the period immediately prior to the pay periods containing the prepaid leave. 4. Confirm that a pay item for the base pay for the calculated pay period has been generated. 5. Confirm that two pay items for the two whole periods of leave have been generated. 6. Confirm that a pay item for additional banking has been generated and its total is three times the amount configured for the employee.

Solution Implemented

Any additional banking will be correctly calculated for employees that have submitted prepaid leave via Ci Anywhere.

HRPC-560 - Infrastructure changes for the cloud 5 environment

Functional Issue

Infrastructure changes for the cloud 5 environment.

Functional Verification

Functional Verification is not applicable for this change.

Solution Implemented

Modified the system to support some minor infrastructure changes in the cloud 5 environment.

HRPC-562 - ATO Updates Pay as you go withholding (PAYGW) electronic report update PSAR v11.0.2

Functional Issue

The following updates were made by the ATO to the Pay as You Go Withholding (PAYGW) payment summary annual report v11.0.2 (released June 2016): • Removal of any reference to ECI being a lodgment channel from October 2016. • The requirement to call the file name EMPDUPE has been removed. If preferred the file name can remain as EMPDUPE or a name that is easily identified by the end user eg PSAR2016.

Functional Verification

1. Open the PAYG Payment Summaries form. Set the Report options to E-File. 2. Confirm that the File Name field is defaulted to 'EMPDUPE'. 3. Fill in the key fields. 4. Change the File Name to a value that contains characters other than those in the range A-Z, 0-9, space, apostrophe, hyphen and full stop. 5. Confirm that an error is returned due to the file name containing invalid characters. 6. NOTE The File Name is limited to a maximum of 254 characters in length. 7. Change the File Name to a valid value then start processing. E.g. PSAR2016 8. Confirm that the process succeeds and the file is generated as per the file name specified.

Solution Implemented

The PAYG Payment Summary function for E-File generation has been modified to allow the File Name to be named other than 'EMPDUPE'. The file name must only contains characters from the range: A-Z, 0-9, space, apostrophe, hyphen and full stop. The length of the file name must be less than 255 characters. NOTE By default the file name will appear as 'EMPDUPE', however the user can now change this to a preferred name and not receive previous error messages. E.g. 'PSAR2016'.

HRPC-563 - Pay Advice reports - not using Accrual Config Code description for User Defined codes (e.g. U_AG_Annual)

Functional Issue

Pay Advice reports are not using the Accrual Group Description when displaying the leave accruals that specify user-defined Accrual Group codes (e.g. U_AG_Annual).

Functional Verification

1. For those implementations that specify user-defined Accrual Groups on their leave accrual pay components code. i.e. Report Groupings that start with "U_AG_". 2. From Adjust Pay, select an employee who has an accrual balance on such an accrual pay component. E.g. Annual Leave grouped by "U_AG_Annual" 3. Calculate the current pay for the employee. 4. Generate the pay advice. 5. Confirm that the description of the user-defined Accrual Group is displayed for the leave accrual in the Leave section.

Solution Implemented

The Accrual Summary Table (HRPAY_PAYITEMS_SUMMACCR) used for reporting which includes the pay advices, has been corrected to load either the first user-defined Accrual Group code (U_AG) or the shipped accrual group code (AG) defined against the leave accrual pay component. i.e. The description of this Accrual Group field is then displayed on the pay advice.

HRPC-565 - EOFY - Payment Summary not picking up Branch Number

Functional Issue

The PAYG Payment Summary report is not including the correct branch number of the employee's company when the branch number is a value greater than 1 but less than 10. E.g. '001' is shown on the Payment Summary when the actual value is '4'

Functional Verification

1. In Company Maintenance, enter a Branch Number to a value larger than 1 but less than 10. E.g. 4 2. Run the Print PAYG Payment Summary report for the company. 3. Confirm that the branch number is displayed with 3 digits correctly, E.g. '004'.

Solution Implemented

The PAYG Payment Summary report has been updated to display the company's branch number correctly in the 'Payer details' section.

HRPC-566 - Need to be able to Print PAYG Payment Summaries for Terminated Employees ONLY

Functional Issue

New requirement to print PAYG Payment Summaries for only those employees who were terminated during the financial year. i.e. Where email or other distribution option is not applicable.

Functional Verification

1. Log into the system and select the Payroll Officer workplace. 2. Select the Reports tab. 3. Confirm the Tax Reports menu list has the function link Print PAYG Payment Summary for terminated employees only ($HR.TAX.PAYGSMTM.RPT). 4. Select the report's link. 5. Confirm the report loads without errors. 6. Enter the required fields and start processing the report. 7. Confirm the report completes without errors. 8. Review the payment summaries generated. 9. Confirm the payment summaries generated are for employees terminated during the financial year entered. Note: Employees terminated after the financial year end date are included in this reports processing.

Solution Implemented

Added a new report to print only Terminated employee PAYG payment summaries - "Print PAYG Payment Summaries report for terminated employees only" ($HR.TAX.PAYGSMTM.RPT). Available on shipped payroll officer Tax Reports menu list.

HRPC-570 - Pay by Group errors due to one employee's invalid Pay Group

Functional Issue

When running a pay calculation by group, an error in the Pay Period data for an employee prevents the remaining employees to be calculated. NOTE: The solution for this issue is included in resolution of HRPC-464. This additional solution includes validation to prevent saving an employee's job details with a Pay Group that does not have valid pay periods.

Functional Verification

1. Retrieve an employee in the Employee Maintenance. 2. Add a job detail to the employee. Ensure the Pay Group does not have a valid pay period defined in Pay Period Maintenance for the employee's Company and Pay Basis. E.g. Employee pay basis is 'Salary' however only 'Hourly' pay basis has been defined for payroll pay period generation. 3. Save the employee. 4. Confirm that an error is displayed saying 'Invalid Pay Group '[Pay Group]' for Employee '[Id Number]' Job Effective Date '[Effective Date]' Company '[Company Code]' Pay Basis '[Pay Basis]'. Pay Periods do not exist.' Record is not saved.

Solution Implemented

Added validation to prevent saving an invalid Pay Group on an employee's job details. This is to avoid pay processing errors due to missing pay periods. NOTE A Pay Group is considered invalid if there is no corresponding pay period defined on that Pay Group definition for the employee's selected Pay Group, Pay Basis and Company.

HRPC-579 - Westpac NZ Bank Download file has incorrect format

Functional Issue

The Westpac (NZ) bank download format was failing Westpac validation due to a comma in the pay name field.

Functional Verification

1. Log into the system as an administrator. 2. Open the System Administrator - All workplace. 3. Load the $HRPAY_NZWBC stored script. 4. Confirm the script's version information includes '005 / 19-Jul-2016 / RGC / HRPC-579'. 5. Open the Payroll Officer workplace. 6. Open the Bank Download function in payroll processing. 7. Load the bank download format configured for the Westpac (NZ). 8. Process the latest pay period. 9. Review the bank download file. 10. Confirm the payee name does not contain a comma between the family name and given name.

Solution Implemented

Changed the Westpac (NZ) stored script ($HRPAY_NZWBC) to remove the comma from the payee name field.

HRPC-581 - SBR TFN & Payment Summary - translate State field to ATO values (QLD, TAS, NSW, VIC, ACT, WA, SA, NT, AAT)

Functional Issue

The Electronic PAYG Payment Summaries and Electronic TFN Declaration functions can be enhanced by translating the State field of addresses to the valid state code accepted by the ATO. i.e. QLD, TAS, NSW, VIC, ACT, WA, SA, NT, AAT.

Functional Verification

Electronic PAYG Payment Summaries. 1. In the Adjust PAYG Payment Summary screen, load an employee. 2. Set the address state of an employee to the full name, e.g. 'Victoria'. 3. Open the Electronic PAYG Payment Summaries. Fill in the key fields. Select the employee above to be processed. Choose report option as "SBR". Do not check the Production Run. Run processing. 4. Confirm that the request is received successfully. No errors or warnings occurs. Electronic TFN Declarations. 1. In the Employee Maintenance screen, set the employee's state address to a full name, e.g. "TASMANIA". 2. Open the Electronic TFN Declarations function. Fill in the key fields. Select the employee above to be processed. Choose report option as "SBR". Do not check the Production Run. Run processing. 3. Confirm that the request is received successfully. No errors or warnings occurs.

Solution Implemented

Added the state converter function to the Electronic PAYG Payment Summary and Electronic TFN Declarations functions. This is a best effort translation to the 3 character State fields accepted by the ATO - (QLD, TAS, NSW, VIC, ACT, WA, SA, NT, AAT)

HRPC-587 - Termination Pay Process Errors with "Value to add was out of range" error.

Functional Issue

Setting the configuration control variable for 'Default Leave Base Hours' to 0, can cause an error to occur when calculating NZ termination pay that requires a non-zero daily work hours figure for post-termination public holiday leave processing.

Functional Verification

1. From Payroll Officer, open Control Variable Maintenance 2. On the DEFAULT control group, set the 'Default Leave Base Hours' to zero. 3. Process the termination pay for an existing NZ employee who has an annual leave balance to be paid out. Also ensure there is a public holiday occurring after the termination date and would be included in the employee's paid annual leave period. 4. Confirm that the pay calculation is completed without error.

Solution Implemented

The public holiday pay out in the NZ termination process has been updated to default a value of 8 hours if the 'Default Leave Base Hours' control variable has been overridden to zero.

HRPC-595 - Increment Processing to ignore FTE when calculating

Functional Issue

Calendar based increments apply the FTE (Full-Time Equivalent) of employees, which results in part-time employees requiring longer increment periods to receive their next position increment. E.g. an employee with a 0.5 FTE, will receive their next increment after 24 months rather than the expected 12 months increment period (as applied to full time employees).

Functional Verification

1. From Payroll Officer, navigate to the "Calculate due Increments - Calendar based" function 2. Specify the criteria to calculate the next increment for an employee who is on a part time FTE. E.g. Employee on 0.5 FTE is expected to receive an increment to their next Grade/Level every 12 months, regardless of their FTE. 3. Confirm that the process completes with a pending increment for the selected the employee.

Solution Implemented

The application of the employee FTE value has been removed from the processing for Calendar based increments. i.e. "Calculate due Increments - Calendar based" and "Calculate due Increments - Calendar based with min-service".

HRPC-601 - Australian Tax Scale changes Effective 01/10/2016 (Region $AU)

Functional Issue

The Australian Normal Tax Scales are to be updated from 1 October 2016.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the normal tax scales (Tax Scales -> $AU - Australia): 4. Confirm that new normal tax income thresholds are available for the 1 October 2016 for all tax scale codes.

Solution Implemented

New Australian Normal Tax Scales have been added for the 2016-2017 financial year effective from 1 October 2016 (refer to ATO website).

HRPC-604 - New Data Management for Region System Data

Functional Issue

Cloud customers are required to run the "HR and Payroll Load Region Data" manually when new legislative fields are added to each region. E.g. Australia - new ATO tax fields for employees.

Functional Verification

1. Login as Payroll Officer 2. From Adjust Pay, calculate the pay of an employee from each region implemented by the organisation. E.g. Australia, New Zealand. 3. Confirm that no errors occur referring to missing fields in database tables that support region-specific data. E.g. table DETAX_EMP_AU_EMPTAX

Solution Implemented

New Data Management tasks have been added to the Payroll Processing package that automatically refreshes the system data and fields of each Payroll region. i.e. $AU, $NZ, $GB, $PG, $WS. These tasks are scheduled to run automatically after an upgrade in which changes to region system data for payroll have been made. This is achieved by the new shipped Data Management engine job ($DATAMGMT) which submits uncompleted product data management tasks to the DP Queue ($DATAMGMT). NOTE System Administrators must ensure this new queue is serviced by a processor of your active DP Server.

HRPC-606 - KED schedule error - blank Salutation field is attempting to use code '_' in report

Functional Issue

An invalid value error is raised when running Kiwisaver Employment Details (KS1) for an employee who has a blank Title field (and has a standard code value of '_' which is assigned by selecting blank row from drop down list of Title codes).

Functional Verification

1. Run the KiwiSaver Employment Details (KS1) for a company. Ensure the employee included has a blank Title selected from the drop-down list of codes (i.e. code '_' has been saved to the employee's record). 2. Confirm that the process succeeds without error. 3. Open the KED file. Confirm that the employee's title is blank instead of '_'. Test error message. 1. Run the KiwiSaver Employment Details (KS1) for a company. Ensure the employee's address line is set to have an invalid character, e.g. 'Line ???'. 2. Confirm that the an error is raised and the error message is informative with the employee Id and field name. E.g. "Invalid character '?' contained in field 'Employee's address line one' for employee Id Number 999. Field value: 'value???' "

Solution Implemented

Updated the KiwiSaver Employment Details (KS1) to use employee's Title Description instead of Title Code in the generated file. Updated the error and warning messages in the KiwiSaver Employment Details (KS1), Electronic Deduction Form (IR 345) and Employer Monthly Schedule (IR 348) to include the employee Id Number and field name.

HRPC-627 - Increment processing for Calendar with minimum service can time out for the first increment period

Functional Issue

Running the due increment process for Calendar-based with minimum service, can result in a timeout for the first increment period of an employee who is on Exception Entry (timesheets for payroll calculation).

Functional Verification

1. From Payroll Officer, navigate to the "Calculate due Increments - Calendar based with min service" function 2. Specify the criteria to calculate the first increment for an employee who is on Exception Entry for timesheets. i.e. first increment since their hire date. 3. Confirm that the process completes with a pending increment for the selected the employee, if the employee has achieved the minimum service specified in the increment period.

Solution Implemented

The increment processing has been corrected to remove the attempt to prorata/reduce service from the very first pay period of the employee which falls in their first increment period. i.e. there is no service reduction required in this period.

RELEASE May 2016

HRPC-458 - 49% Withholding Limit not being applied to additional payments

HRPC-466 - Australian Legislative changes Effective 01/07/2016 (Region $AU)

HRPC-486 - Payroll Calculation is changing Leave Units manually entered to pay out leave

HRPC-491 - Incorrect tax rate on leave lump sum taxation in NZ termination pays

HRPC-520 - HRP Diagnostics Stored Script updated

HRPC-458 - 49% Withholding Limit not being applied to additional payments

Functional Issue

The Australian tax office 49% withholding limit was not being applied to additional payments that are being taxed on an annualised basis.

Functional Verification

$AU region Other Scales: 1. Confirm the scales include the Scale Type AU_WL - Additional Payment Withholding Limit 2. Confirm a scale is defined for the withholding limit as at the 01/07/2015. 3. Confirm the scale details Earnings (X) Less Than is defined as $9,999,999,999.00 and the rate column (A) has a rate of 49.0000%. Bonus pay calculation: 1. Create an employee whose normal gross earnings are at the highest tax rate's margin(greater than $3,461.00 per week). 2. Assign the employee tax to tax scale 2 and select the HELP indicator. 3. Calculate an ordinary pay period and confirm the PAYE and HELP withheld are correct. 4. Open the Process or Adjust Bonus Pay for Employee function. 5. Add a taxable pay item to the pay and calculate. 6. Review the tax calculation section of the Calculation Audit. 7. Confirm the tax has been calculated on an annualised basis. 8. Confirm the additional payment withholding limit has been calculated correctly. 9. Confirm the total withholding, including HELP, has exceeded the withholding limit. 10. Confirm the HELP payment has been reduced or cancelled to ensure the total withheld equals the withholding limit. 11. Confirm the PAYE has been reduced to the withholding limit, if necessary. 12. Confirm the PAYE and HELP pay items are generated per the calculation audit.

Solution Implemented

Changed the $AU region other scales to include the aditional payment withholding limit, currently 49%. Changed the Australian tax calculation to ensure the withholding limit is applied to additional payments that are taxed on an annualised basis. NOTE: Customers on Cloud 5 will need to run the regional data update to have the new Australian tax scales updated. Run HR and Payroll Load Region Data function (Payroll Officer > More tab > System Update menu list) - specifying the $AU region

HRPC-466 - Australian Legislative changes Effective 01/07/2016 (Region $AU)

Functional Issue

Australian Legislative changes effective 1 July 2016, including: 1. The Australian HELP/TSL and SFSS Other Scales are to be updated from 1 July 2016. 2. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2016. 3. The Maximum super contribution base amount will increase from 1 July 2016. NOTE: The PAYE income tax threshold change announced in the 2016 Budget were not enacted before the election was called, the normal tax scales are not being updated from 1 July 2016 at this point in time. The indexed ETP Cap Amount (HR_ETP_CAP) is not being increased from 1 July 2016.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 6. Navigate to the HELP (SSL or TSL) income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP): 7. Confirm that new HELP (SSL or TSL) income thresholds are available for the 1 July 2016. 8. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS): 9. Confirm that SFSS repayment income thresholds are available for the 1 July 2016. 10. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Tax Scales -> $AU - Australia -> AU_GRTFL): 11. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2016. 12. Navigate to the Default Control Variable Maintenance > Superannuation section. 13. Confirm that the Max Quarterly Base is 51,260.00. 14. NOTE: Check and update the Max Quarterly Base value if required in any customised Control Variable groups.

Solution Implemented

1. New Australian HELP/SSL/TSL and SFSS Other Tax Scales have been added for the 2016-2017 financial year (refer to ATO website). 2. New Australian Genuine Redundancy Tax Free Limit thresholds have been added for the 2016-2017 financial year (refer to ATO website). 3. The Control Variable for the Superannuation Maximum Quarterly Base has been updated (to 51,260.00). 4. TFN specification for electronic reporting has been updated to support the TSL indicator, which is included in the HELP indicator of the ATO report structure. 5. Updated the Employee Tax details indicator field "HELP" to "HELP/SSL" for repayments to both loan types. See notes below. NOTE: 1. The ATO have added a third loan type, Student Start-up Loan scheme (SSL) to the HELP scales and updated the description to 'HELP/SSL or TSL'. The Student Start-up Loan (SSL) scheme started on 01/01/2016. Be aware that employees with both a HELP and SSL debt are required to pay off the HELP debt prior to making repayments for their SSL debt. Read more about repayment thresholds on the ATO website. Although changed within our shipped standard codes, the description of this code will not be updated on existing installations. If you wish to update the HELP scales description accordingly, maintain the Standard Code Type 'TAX_SCALE_TYPE' Code Id 'AU_HELP'. 2. For on-premise installations, ensure that a Package Finalise is executed after applying this update which will load the new tax details into your database(s). Please note, the Package Finalise process may take a long time to run. 3. Customers on Cloud 5 will need to run the regional data update function to have the new Australian tax scales added. i.e. From Payroll Officer > Run "HR and Payroll Load Region Data" function (Payroll Officer > More tab > System Update menu list) - specifying the $AU region.

HRPC-486 - Payroll Calculation is changing Leave Units manually entered to pay out leave

Functional Issue

Manually entered leave items added to a pay are reduced to the work pattern total units for the pay period.

Functional Verification

Ordinary/Correction pay: 1. Load an ordinary pay period for an employee. 2. Enter an annual leave item for more hours than the work pattern total for the pay period. 3. Calculate the pay. 4. Confirm the annual leave pay item units entered have not been reduced. Termination pay: 1. Create a termination activity for an employee. 2. Load the adjust Termination function. 3. Enter a termination leave pay item for 4 weeks of accrued leave. 4. Calculate the termination pay. 5. Confirm the entered termination annual leave units remain unchanged. NOTE: If different unit types are being used for the Accrual and Leave Taken (e.g. accrued in Days and Leave Taken in Hours), confirm that the correct accrual units have been converted as part of the pay calculation. E.g. Leave Taken is paid in Hours, however the Leave Accruals Units Taken has been converted to equivalent Days and the Accrual Balance has been reduced by Days. This can be confirmed in Employee Maintenance > Leave Accrual details. Also refer to Feb 2016 package release for verification of Jira HRPC-48 (Incorrect sick leave calculation for NZ terminations).

Solution Implemented

Changed the pay process to ensure manually entered leave pay items are not reduced to the current work pattern total.

HRPC-491 - Incorrect tax rate on leave lump sum taxation in NZ termination pays

Functional Issue

NZ Termination pays are calculating inflated four-weekly gross-up for the termination leave lump sum tax calculation.

Functional Verification

1. Create a termination activity for an New Zealand employee on or after the 1st April 2016. 2. Calculate the termination pay. 3. Review the termination tax calculation section of the calculation audit. 4. Confirm the termination leave is being taxed on a lump sum basis. i.e. as per legislation change effective 1 April 2016 5. Confirm that a four-weekly gross-up is used to annualise the employee's earnings to obtain the correct lump sum tax rate. i.e. If the termination occurs on a normal pay End Date then the current pay included in the termination is included in that 4 weeks. Alternatively if the termination is out of cycle (i.e. not on a normal pay End Date), then the 4 weeks of the previous pay periods are used for the four-weekly gross-up amount. 6. Confirm the four-weekly gross-up value is correct. 7. Confirm the four-weekly gross-up plus lump sum payment value is correct. 8. Confirm the lump sum tax rate is correct for the total gross-up amount (e.g. last 4 weeks of salary or wage payments * 13 plus the current lump sum).

Solution Implemented

Amended the New Zealand tax calculation to ensure a four-weekly gross-up is used when paying lump sums in all pay types (termination, normal payroll, correction, special or bonus pay). With special note on terminations occurring on or after 1 April 2016, which will have the annual leave paid out and taxed as extra pay (lump sum). NOTE 1. The four-weekly gross-up will not proportion pay periods (e.g. fortnightly to weeks and days), so must be based on whole pay periods on or before the lump sum payment date to gain an accurate four-weekly taxable earnings amount which is then annualised. 2. The types of pay included in the four-weekly taxable earnings are determined by the Control Variable - Taxable Document Types (TAXABLE_DOC_TYPES). By default this includes all Payroll types plus Special and Correction Pay. This list can be customised in the DEFAULT group or custom groups (e.g. if defined by Company). For example, the payroll officer may determine that Special Pay should be excluded from the four-weekly gross annualised for Extra Pay / Lump Sums tax, due to an over-inflated annualised amount and therefore higher tax rate. Similarly, if Regular Bonuses are paid and made through the Bonus Pay document type then it may be determined that these should be included in the 4-weekly gross up annualisation.

HRPC-520 - HRP Diagnostics Stored Script updated

Functional Issue

The HRP Diagnostic - Export HRP Diagnostic Data stored script procedure requires more employee data to assist analysis. i.e. CiAnywhere timesheets, Timesheet Periods, Work Pattern assignment, All pay items (not limited to accrual leave).

Functional Verification

1. Log onto the system as an administrator, open the System Administrator - ALL Workplace. 2. Navigate to the System Administration Console and open the $HRPAY_DIAG_ACC Stored Script Procedure. 3. Confirm version 008 details are included in the script header. 4. Open the Payroll Officer workplace. 5. Select the More tab and open the HRP Diagnostic - Export HRP Diagnostic Data function. 6. Enter a valid employee Id number and process the diagnostic data. 7. Confirm the process completes without errors within the Status Log. 8. Confirm the zip archive is saved in My Reports and Files per the Status Log. 9. Confirm the zip archive contains: a: All pay items for the employee (HRPAY_PAYITEMS_DTL) b: Ci timesheet period details (F1TIM_SYS_PRD) c: Work Pattern assignment for the employee (HRRST_RSTR_GRP_DTL) d: Employee timesheet periods - Ci (F1TIM_TSHEET_CTL) e: Employee timesheet periods - CiAnywhere (HRTIM_TSHEET_PERIOD) f: Employee timesheet costing - CiAnywhere (HRTIM_TSHEET_COSTING)

Solution Implemented

Updated the HRP Diagnostic - Export HRP Diagnostic Data stored script to include additional information.

RELEASE February 2016

HRPC-48 - Ad hoc leave entry in pay is reducing daily accrual incorrectly when leave is taken in hours

HRPC-53 - NZ Special Tax Code does not deduct Student Loan on lump sum payment included in ordinary pay

HRPC-100 - NZ ESCT PAYE not correct in termination part of super and tax calculation

HRPC-330 - ATO new employee tax option and deduction for TSL (Trade Support Loan)

HRPC-333 - Payroll Exception Report Incorrectly Raises No Tax File Number Message

HRPC-349 - Leave Liabilities not calculating for some employees

HRPC-392 - NZ ESCT Calculation $0.01 difference

HRPC-412 - Do not allow Pay Component Type 50 to be calculated in a pay

HRPC-422 - NZ IRD 2016/17 Payroll Legislative Updates

HRPC-429 - SQL Error When Trying to Set Disbursement Code Criteria

HRPC-433 - Student Loan Special Deduction rate

HRPC-440 - Pay Advice print issue - Company Code '0' in errors running for Multiple Companies

HRPC-442 - Cloud 5 Timezone - Payroll Stored Scripts

HRPC-450 - ANZ PNG Bank Download needs refining - ANZ validation error on Details of Payment

HRPC-455 - HR & Payroll Cloud Clients experience region issues after package update

HRPC-460 - New Pay Advice - No Pro-rata included in Accrual summary

HRPC-496 - Payroll processing package release February 2016.2 errors during install from SupportOne

HRPC-48 - Ad hoc leave entry in pay is reducing daily accrual incorrectly when leave is taken in hours

Functional Issue

Entering leave taken manually into normal or termination pay is not reducing Daily accruals correctly. This issue is prevalent in New Zealand region companies due to the common practice of taking leave in Hours while accruing in Days.

Functional Verification

Ordinary Pay - Adjust with manual leave item: 1. From Adjust Pay, calculate the next pay for an employee on a Daily leave accrual (i.e. in their active entitlements) 2. Manually enter a leave item for the normal hours in a single day. E.g. 8 hours 3. Calculate the pay period with entitlements and timesheets loaded. 4. Confirm the leave was paid correctly based on the hours entered. 5. From Employee Maintenance, load the details of the employee. 6. Confirm that the manually entered leave accrual has had the units taken converted correctly (i.e. to Days). E.g. the Leave Accruals Units Taken has been increased by 1 unit (Day) and the Accrual Balance has been reduced by 1 unit (Day). 7. Select Show Accrual Details and retrieve the Leave Taken Transactions. 8. Confirm the manually entered transaction is listed, the units and type should be displayed as 1 Day. Termination Pay: 1. Terminate an existing employee. 2. Calculate the termination pay. 3. Confirm the annual leave is paid correctly including the 8% termination earnings (paid since the last accrual anniversary). 4. Reload the employee details and confirm the annual leave accruals have been reduced correctly. Note: The Balance + Pro-rata column should total zero.

Solution Implemented

Amended the pay calculation process for ad hoc ordinary pay and termination pay, by converting manually entered leave units if required. i.e. A leave unit conversion matrix has been defined (i.e. Hours to Days) and the leave taken has not been processed via Leave Maintenance, MyLeave or timesheets. NOTE For the full functionality of this resolution the following Ci packages are required: 1. Payroll Processing Feb 2016 2. Accruals Feb 2016

HRPC-53 - NZ Special Tax Code does not deduct Student Loan on lump sum payment included in ordinary pay

Functional Issue

Lump sum payments were not included in student loan repayment income for employees with a student loan specified deduction rate certificate.

Functional Verification

1. Locate an employee with a specified tax code of M SL and a student loan specified deduction rate of 6%. 2. Load the next ordinary pay period. 3. Manually add a pay item for a lump sum payment - New Zealand configuration code 'LUMP_SUM'. 4. Calculate the pay with entitlements loaded. 5. Review the tax section of the calculation audit. 6. Confirm the student loan calculation is performed on the total of normal taxable income and the lump sum payment. 7. Confirm the student loan repayment threshold is applied to the student loan calculation. 8. Confirm the student loan is deducted at rate of 6% on the total income in excess of the threshold.

Solution Implemented

Amended the New Zealand tax calculation to include lump sum pay items in the student loan calculation.

HRPC-100 - NZ ESCT PAYE not correct in termination part of super and tax calculation

Functional Issue

The system was calculating ESCT which is included in the PAYE tax calculation incorrectly, especially for company superannuation contributions relating to termination leave.

Functional Verification

1.Create a termination activity for an New Zealand employee with annual leave accruals. 2. Ensure the employee's Superannuation Tax ESCT Rate is set to 'ESCT Calculate with PAYE' 3. Calculate the termination pay. 4. Review the ordinary pay's superannuation ESCT section. 5. Confirm the calculation of ESCT for the company contribution is to be included in the PAYE tax calculation. 6. Confirm the ordinary pay's tax calculation section has included the company contribution as ESCT PAYE. 7. Confirm the ordinary PAYE ESCT is calculated correctly based on the normal PAYE tax scales and is deducted from the gross company contribution. 8. Review the termination leave's superannuation ESCT section. 9. Confirm the calculation of ESCT for company contribution is to be included in the termination PAYE tax calculation. 10. Confirm the termination leave's tax calculation section has included the company contribution as ESCT PAYE. 11. Confirm the termination PAYE ESCT is calculated correctly based on lump sum extra pay tax rate per the termination leave and is deducted from the termination gross company contribution. (i.e. refer to IRD 2016/17 change to pay out leave on termination as a lump sum)

Solution Implemented

Amended the system to calculate company contribution ESCT PAYE correctly for termination pays.

HRPC-330 - ATO new employee tax option and deduction for TSL (Trade Support Loan)

Functional Issue

New employee tax and pay items are required to support the 2015/16 ATO additional payroll repayment option for TSL (Trade Support Loan). TSLs share the same PAYW tax scales as HELP.

Functional Verification

1. Login as Payroll Officer 2. Ensure that a new TSL tax pay component code (type 990) is configured - with "TAX_TSL" config code selected. 3. Maintain an existing Australian employee, and create new tax details with the TSL option selected for deductions in their pay. 4. From Adjust Payroll, calculate the employee's next pay. 5. Confirm that a TSL tax pay item is included in the pay. The rate should reflect the tax scales of HELP/TSL in the current financial year.

Solution Implemented

1. Employee Maintenance > Tax Details - A new check box has been added for TSL (Trade Support Loan). 2. The Australian Payroll Processing Tax Calculation has been updated to generate an additional tax pay item if an employee has a TSL noted in their effective tax details. NOTE This is similar processing to HELP and applies the same Tax Scales (i.e. not applicable to no TFN 4a and 4b). 3. A new Region Config Code ($AU), "TAX_TSL" has been added for use on Taxation (990) pay components. NOTE Employee Tax details import and data analyser for Australia will be updated in the next Ci package releases of HRP Core and Employee Administration.

HRPC-333 - Payroll Exception Report Incorrectly Raises No Tax File Number Message

Functional Issue

The Payroll Exception report generates a "No Tax File Number" message for employees who have a valid Tax File Number in their current tax details.

Functional Verification

1. Create or search for an employee who has multiple tax effective dated records. Ensure that at least one dated previous to the most current does not include a TFN. 2. Open the Payroll Exception report. 3. Specify the required criteria (e.g. company, pay group) Ensure the Pay Period End Date has a date selected for which the employee has a tax record with Tax File Number specified. e.g. the most current tax record. 4. Confirm that the report is generated successfully and the employee does not appear for a missing Tax File Number. Additional corrections have been made to ensure the report includes any employee Ci or CiAnywhere timesheets that have not been calculated in the associated pay. 5. Confirm that employees who are paid Hourly are included on the report if their timesheets have not been included in the associated pay. E.g. either timesheet is unapproved by supervisor or approved but not calculated in the pay (and therefore not paid).

Solution Implemented

The Payroll Exception report has been modified to validate the employee's Tax File Number only in the relevant effective dated tax details relevant to the report date provided. The Payroll Exception report has been corrected to check for unpaid Timesheet entries against time worked for Hourly paid employees. The Payroll Exception and Variation reports have been corrected, changing the 'Pay Period Type' criteria field to 'Pay Group'; and to ensure large employee Id Numbers (10 digits) fit on the report. NOTE For the full functionality of this change the following Ci packages are required: 1. HRP Core Jan 2016 2. Payroll Processing Feb 2016

HRPC-349 - Leave Liabilities not calculating for some employees

Functional Issue

When an employee has a previous entitlement accrual code which is now associated with an inactive account number, the leave liability calculation will fail with an 'invalid account number' error.

Functional Verification

1. Identify an employee whose accruals balances are to be transferred to new accrual codes. 2. Calculate accruals for the current month. 3. Calculate leave liability as at the end of the current month. 4. Generate new entitlements as at the start of the first pay period in the following month, ensuring new accrual codes are generated or selected for the employee. 5. Transfer the old accrual balances to the new accrual codes via initial balances. (ensuring pro-rata is set to 0.0001 on old balances) 6. From Financials, deactivate the account numbers associated with the old accrual code(s) via General Ledger Account maintenance. 7. Calculate leave accruals for the pay periods within the next month. 8. Confirm no errors are displayed after accrual calculation and new accruals are calculated correctly. 9. Calculate the leave liability calculation at the end of the next month. 6. Confirm no 'invalid account number' errors are displayed and the calculation has generated leave liability items correctly.

Solution Implemented

The Leave Liability process has been modified to ensure that previous entitlement accruals with zero balance are not included in the calculation and any subsequent pay component validation. The Accrual process has been modified to exclude pay component account errors when calculating the pro-rata amount for the new accrual balances after processing taken leave. NOTE For the full functionality of this change the following Ci packages are required: 1. Accruals Feb 2016 2. Payroll Processing Feb 2016

HRPC-392 - NZ ESCT Calculation $0.01 difference

Functional Issue

The ESCT calculation for New Zealand employee is incorrect by $0.01 in a certain base pay amount and allocated fund type.

Functional Verification

1. Run a payroll calculation for a NZ employee with a superannuation. Ensure the employee base pay amount and super contribution percentage will result in incorrect rounding due to high decimal precision. For example: 12.0 * 0.175 results in internal value of 2.0999999999999996, which is truncated to 2.09 instead of resulting in 2.10. The employee base pay is $400, employee's contribution is 3% and the ESCT rate allocated fund type is 17.5%. 2. Run the payroll calculation for the employee. 3. Confirm that the ESCT amount is calculated correctly. E.g. based on above example, the amount is 2.10 instead of 2.09.

Solution Implemented

The ESCT calculation process has been modified to change the result to decimal type so the data precision loss does not happen.

HRPC-412 - Do not allow Pay Component Type 50 to be calculated in a pay

Functional Issue

The part-time hours Pay Component 50 can be manually added to an employee pay incorrectly and cause a posting failure for oncosts.

Functional Verification

1. Open the Adjust Payroll. 2. Select a part-time employee's existing pay that has not yet been paid or posted (i.e. calculated only). i.e. who has the pay component 50 included in their entitlements in order for the part time hours to be calculated. 3. Manually add a new pay item choosing the part-time hours pay component 50. 4. Calculate the pay. 5. An error message appears on save or calculate, informing the user that pay component 50 is reserved and cannot be included in the pay.

Solution Implemented

Adjust Pay validation has been added to prevent the pay component type 50 from being manually added to a pay.

HRPC-422 - NZ IRD 2016/17 Payroll Legislative Updates

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2016. The ACC earners levy scales have been updated as at 1 April 2016. The IRD have indicated that for leave paid on termination tax is to be withheld at the lump sum rate.

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2016 and are for the correct percentage and maximum levy. The Earners Levy percentage for 1 April 2016 is 1.39% for annual income less than $122,063 and the maximum levy is $1,696.67. 2. Calculate an ordinary pay after the 1st April 2016 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Termination leave withholding tax: 1. Create a termination activity for a New Zealand employee with annual leave accruals. 2. Calculate a termination pay for the employee. 3. Review the calculation audit. 4. Confirm the ordinary pay tax calculation section has withheld PAYE as a normal pay. 5. Confirm the termination leave section has not done the PAYE calculation based on an ordinary week and the remainder for unused accrual and 8% termination earnings. 6. Confirm the termination leave tax calculation section has a taxable income for the total of the termination leave including unused accrual, 8% termination earnings and public holidays paid that fall within the unused accrual period. 7. Confirm the termination leave tax calculation section has withheld PAYE on termination leave earnings as a lump sum using the extra pay rates. 8. Confirm any student loan deductions appear for both normal pay and termination pay. Noting that both amounts are included for the single Student Loan threshold determination.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2016: - The ACC Earners Levy tax scales have been updated and apply to pay on or after 1 April 2016. - The termination pay leave tax calculation process was updated to tax termination leave as a lump sum using the extra pay calculation steps. NOTE: The IRD have received numerous queries about the treatment of the termination leave, which have been escalated for a legal opinion. The rules around these payments are subject to change. The system can be reverted to the previous termination leave calculation based on the normal weekly pay by defining the system variable below. Variable name: 'HR_NZ_LUMPSUM_TERMTX' Group name: '$HR' Value: 'N'

HRPC-429 - SQL Error When Trying to Set Disbursement Code Criteria

Functional Issue

An error is thrown when the 'Disbursement Code' is used as extended criteria in the Payroll Enquiry function.

Functional Verification

1. Login as payroll officer. 2. Open the Payroll Enquiry tab. 3. Fill the start date and end date field. 4. Use the extended criteria and select a disbursement code to filter the results. 5. Perform the enquiry. 6. The enquiry displays the data without error.

Solution Implemented

The disbursement code criteria column has been changed to the correct field. Additionally, the reference to open the supervisor position criteria picklist has been corrected.

HRPC-433 - Student Loan Special Deduction rate

Functional Issue

Student loan special deduction rate calculation does not apply the repayment threshold when required by the student loan special deduction rate certificate. The monthly EMS (IR348) reports the 'STC' tax code when the employee has a specified standard tax code within the special tax section.

Functional Verification

Employee Tax maintenance: 1. Load employee maintenance function with a New Zealand employee. 2. Select the employee tax code STC - Special Tax Code. 3. The Special Tax (New Zealand) will become editable. 4. Select the Specified Tax code M SL - Main Income with Student Loan. 5. Select the Student Loan drop down. 6. Confirm the existing fixed percentage calculation option has been renamed to "Fixed Percentage - no threshold". 7. Confirm the drop down has a new calculation option "Fixed Percentage - apply threshold". 8. Select the Fixed Percentage - apply threshold option and confirm the Fixed Student Loan Percentage field becomes editable. 9. Enter the value of 6.00 into the Fixed Student Loan Percentage field to change the rate to 6%. 10. Select Ok and then Save in the Actions To Perform. 11. Confirm the special tax values are successfully saved. Pay Calculation: 1. Load the next ordinary pay period for the employee above. 2. Calculate the pay. 3. Review the tax calculation section of the calculation audit. 4. Confirm the audit states that the student loan was calculated on the earnings in excess of the student loan repayment threshold. 5. Confirm the audit state that the student was calculated at the specified rate of 6% (narrated as 0.06). 6. Confirm the student loan deduction payable is for the correct amount and the pay item is generated for the same amount. 7. Bank download the pay. Employer Monthly Schedule (IR348): 1. Generate the EMS for the current month. 2. Review the EMS file generated. 3. Confirm the tax code for the employee above is reported as M SL.

Solution Implemented

Amended the Student Loan calculation options within employee maintenance special tax to include the calculation option "Fixed Percentage - apply threshold"; and renamed existing "Fixed Percentage" option to "Fixed Percentage - no threshold" (i.e. reflecting existing behaviour for this option). Amended the tax calculation process to apply the student loan repayment threshold when the new calculation option is selected. Amended the EMS (IR348) process to report the specified tax code correctly when the special tax code has been selected. NOTE: Employees currently with the special student loan option Fixed Percentage selected and whose current SDR certificate states the repayment threshold is to apply will need to be changed to "Fixed Percentage - apply threshold" after the package install.

HRPC-440 - Pay Advice print issue - Company Code '0' in errors running for Multiple Companies

Functional Issue

The Company code is displayed as '0' in the error message if pay advice generation fails for Multiple Companies

Functional Verification

1. Calculate payroll using the Calculate Payroll for Multiple Companies. 2. Run the pay advice for the payroll calculation. 3. Set the test print email or fax. 4. Run the process for several employees who have email or fax method for their pay advice transmit. 5. Check the displayed error message or open the log file. 6. Confirm that company code is displayed correctly. Note : To force these exception conditions for the testing of printing/emailing or saving pay advices, revoke user authorization or write access from the server folders specified for saving attachments for pay advices or exporting Crystal report files.

Solution Implemented

The Pay Advice print process has been modified to retrieve the company information per employee when no specific company(ies) is selected in the multiple company payroll calculation function.

HRPC-442 - Cloud 5 Timezone - Payroll Stored Scripts

Functional Issue

The introduction of Cloud 5 implementations has identified Date and Time issues in Ci where the application uses the local server/client dates and times (i.e. for Today and Now). The dates and times should be replaced with the date and times from the customer's timezone as dictated by the EAS App Store (cloud 5 only) or database server (pre-cloud 5). In Payroll, this issue affects below functions : 1. Bank Download stored scripts 2. Accrual Diagnostic stored script

Functional Verification

Bank Download 1. Open Maintain Employee. 2. Create a new employee who is on a Pay Group that can be paid on the Date of Hire (i.e. same day). 3. Process pay for the employee (and other employees on the Pay Group). 4. Run the Bank Download. 5. Verify that the newly hired employee's first pay is included in the bank download file. Accrual Diagnostics 1. For a newly hired employee (i.e. as above). 2. From Payroll Office > More tab. 3. Open the diagnostics function, $HRPAY_DIAG_ACC - HRP Diagnostic - Export HRP Diagnostic Data 4. Specify the Id Number of the newly hired employee. 5. Ensure all the related details for that employee are reported in the exported files.

Solution Implemented

Ensured that all calls to retrieve the current date or time in the HRP stored scripts for bank downloads and employee diagnostics are using the standard infrastructure calls (via DBConnection which applies the customer's timezone offset (cloud 5) or the database server's date/time). The following stored scripts have been updated: $HR_PAY_CASH $HR_PAY_WS_ANZ $HR_PAY_WS_CSV $HR_PAY_WS_SCB $HR_PAY_WS_WBC $HRPAY_NZANZ $HRPAY_NZASB1 $HRPAY_NZASB2 $HRPAY_NZBNZ $HRPAY_NZBULK $HRPAY_NZHSBC $HRPAY_NZTSB $HRPAY_NZWBC $HRPAY_PGBSP $HRPAY_DIAG_ACC (diagnostic)

HRPC-450 - ANZ PNG Bank Download needs refining - ANZ validation error on Details of Payment

Functional Issue

The ANZ PNG bank download file was not passing ANZ bank's validation due to invalid characters within the details of payment field.

Functional Verification

1. From Payroll Officer, calculate an ordinary pay period for a PNG company 2. Pay the period calculated using a bank download format linked to the ANZ PNG format '$HRPAY_PGANZ' 3. Confirm the process has generated a 'BKT' file for all employees with ANZ bank accounts 4. Confirm the process has generated a 'ACH' file for all other bank accounts 5. Confirm the Details of Payment field does not contain the '|' character.

Solution Implemented

Amended the ANZ PNG bank download format to remove an invalid separation character ('|') from the Details of Payment field.

HRPC-455 - HR & Payroll Cloud Clients experience region issues after package update

Functional Issue

Human Resource & Payroll clients on the cloud environment do not receive region updates documented in the package notes after a package update. This results in a database error. For example: "Invalid column name 'esct_gross_up_kiwi'."

Functional Verification

1. Review the package notes and confirm that new regional features are expected. E.g. New ATO TSL field or NZ ESCT Gross Up for KiwiSaver field 2. Open the Payroll Officer workplace > More tab > System Update menu 3. Open or Navigate to the new Stored Script function, $HRPAY_LOAD_REG - HR and Payroll Load Region Data 4. Enter the affected region's code. For example: '$AU', and input 'N' in the Test Check Only field 5. Start processing of the stored script 6. Confirm the script completes successfully 7. Confirm the region feature described in the package notes is available (i.e. in the associated maintenance function and data analyser) 8. Confirm the enhanced regional functionality completes without database error 9. Repeat steps 4-8 for each additional region that has received new fields as listed in the package notes of enhanced functionality. E.g. $NZ

Solution Implemented

Delivered a new HR & Payroll update Stored Script for regional data update, $HRPAY_LOAD_REF - HR and Payroll Load Region Data. This has been packaged in Payroll Officer > More > System Update menu list. NOTE: Running this update process is only required for Cloud customers when a Payroll product upgrade is applied that delivers new regional data field(s); and those database changes have not been updated accordingly (i.e. Package Finalise has not been executed). If applicable to the Cloud customer, this process must be run for each region that includes a new payroll feature documenting a new regional database field. i.e. $AU, $NZ, $PG, $GB or $WS. A future release will include product enhancements that will make this manual update of regional data obsolete.

HRPC-460 - New Pay Advice - No Pro-rata included in Accrual summary

Functional Issue

The Long Service Leave pro-rata is displayed in the Australian Pay Advice regardless of the accrual's pro-rata eligibility period, which gives an impression that the employee is entitled to the leave. One solution is to provide new versions of the Pay Advice that excludes all accrual pro-rata (i.e. balances only include actual entitlements on all accruals).

Functional Verification

1. Find or create an employee that has a Long Service Leave accrual with a defined First Eligible Period (e.g. 7 years). 2. Ensure the employee has not yet reached that eligible pro-rata period (i.e. working for less than 7 years). 3. Run the leave accrual process for the employee. 4. For the latest pay, produce the employee's pay advice. NOTE choose one of the new pay advices as outlined in the solution. E.g. Australian Pay Advice without Prorata (PayAdviceAUNoProrata.rpt). 5. Confirm that all accruals including the LSL, do not have pro-rata included in opening, closing balances nor Period Accrual.

Solution Implemented

New Pay Advices have been shipped that do NOT include accrual pro-rata at all in the Accrual section. i.e. For those businesses who only wish to display the actual accrual entitlement on the employee pay advice. The new pay advice reports and Document Definitions are: - Australian Pay Advice without Prorata (PayAdviceAUNoProrata.rpt) in Document Definition $P1PAYAUNP - Australian Multi Company Pay Advice without Prorata (PayAdviceAUMCNoProrata.rpt) in Document Definition $P1PAYAUMN - New Zealand Pay Advice without Prorata (PayAdviceNZNoProrata.rpt) in Document Definition $P1PAYNZNP - New Zealand Multi Company without Prorata (PayAdviceNZMCNoProrata.rpt) in Document Definition $P1PAYNZMN

HRPC-496 - Payroll processing package release February 2016.2 errors during install from SupportOne

Functional Issue

Payroll processing package release February 2016.2 errors during install from SupportOne

Functional Verification

1. Install package version February 2016.3 from SupportOne. 2. Confirm the package has installed without error. Note: The release notes from the February 2016.2 release are applicable for this release.

Solution Implemented

Amended the package release to correct the error occurring in February 2016.2 release

RELEASE November 2015

HRPC-302 - Changes to additional bank account amount for one pay only.

HRPC-378 - Error with Payment Summary

HRPC-395 - Company super contributions incorrect for auto retro pays

HRPC-415 - Payroll Bank Script Required for ANZ PNG

HRPC-302 - Changes to additional bank account amount for one pay only.

Functional Issue

The Pay Advice & EFT Payments Report display blank banking details when there are additional banking pay items added manually.

Functional Verification

1. From Payroll Officer workplace, open the Adjust Payroll function. 2. Calculate the pay for an employee who has an additional banking item in their bank details. 3. Add another banking pay item manually to adjust the total banked amount to that pay component. 4. Confirm that the pay item explanation includes the details of the selected banking item. 5. Re-calculate the payroll. 6. Produce the Pay Advice for this employee pay. 7. Confirm that the Pay Advice includes the correct banking details for the manually entered banking change. 8. Run the EFT Payment report including the employee pay above. 9. Confirm the EFT Payment report displays the correct description for all banking pay items.

Solution Implemented

The payroll calculation process has been changed to retrieve and save the banking details for each manually added banking pay items.

HRPC-378 - Error with Payment Summary

Functional Issue

The PAYG Payment Summaries generates an incorrect result for Gross Amount value when non-reportable liabilities exist and are incorrectly deducted from the Gross Amount (i.e. along with payroll non-reportable amounts).

Functional Verification

1. Setup an allowance pay component and mark as a non-reportable tax item and liability (i.e. TAX_NONRPT and PLIAB_INCL system config codes checked) 2. Setup a payment pay component that is a non-reportable tax item only (e.g. FBT), and therefore must be excluded from the employee's Gross Amount on payment summary. 3. Calculate a pay for an employee whose entitlements include both these non-reportable items. 4. Run the Payroll Liability for the employee 5. Run the Load PAYG Payment Summary for the employee. 6. Confirm that the Gross Amount has not deducted the non-reportable amounts included in the liabilities, but that the payroll non-reportable amounts are correctly deducted (e.g. FBT, non-reportable allowance paid amounts).

Solution Implemented

The Gross Amount calculation in the PAYG Payment Summary loading process has been modified to ensure that non-reportable liability amounts are not deducted from the Gross Amount when deducting the non-reportable pay items (i.e. FBT).

HRPC-395 - Company super contributions incorrect for auto retro pays

Functional Issue

Company superannuation contributions were being generated for a negative amount when the Pay Superannuation on Retro calculation option is selected and there had been a retrospective change to the employee's entitlements. E.g. increase of base pay

Functional Verification

1. Calculate an ordinary pay period for an employee with SGC company superannuation contribution. 2. Create an positive base pay entitlement impact to the pay period. i.e. increase the base pay rate entitlement for one or more employees. 3. Calculate the following ordinary pay period with the Retrospective Changes and Pay Superannuation on Retro calculation options selected. 4. Confirm the calculation has created back paid items for the base pay rate change. 5. Review the back pay and confirm the SGC company superannuation item has been generated for the correct amount. i.e. Not negative and the standard 9.5% (or other if configured).

Solution Implemented

The pay calculation process was amended to ensure the company superannuation is created for the correct amount when processing an auto retro pay. NOTE: Additional correction has been made to calculation of Quarterly based earnings when paying SGC and company super. In the event of an irregular payroll payment made to an employee on the same date as their regular pay (e.g. Correction), the earnings of the normal pay were not included in the Quarterly based earnings, therefore possibly allowing an over payment of SGC and company super for the quarter if the maximum was exceeded.

HRPC-415 - Payroll Bank Script Required for ANZ PNG

Functional Issue

The PNG Office needs a new bank download file with ANZ specified format for PNG region. There must be 2 separate files, of which the Employees Accounts at other Banks will be produced in the one 'ACH' file and Employees Accounts at ANZ will be produced in the 'BKT' file.

Functional Verification

1. Ensure stored script procedure '$HRPAY_PGANZ' exists and used in the specified Bank Download Format. 2. Assign the bank download stored script procedure to the PNG banks - ensure both ANZ and other banks have the script assigned to them. 3. Create multiple employees and assign both ANZ and other banks to the employee's banking. 4. Calculate the current ordinary pay for the employees. 5. Open the Bank Download screen. 6. Retrieve the Bank Account Format and Bank and Branch Number that use the stored script above. 7. Run the bank download process. 8. Confirm that there are 2 files and 2 archive files generated for ACH and BKT methods. 9. Confirm that the details in the result files are correct according to the ANZ specified format for PNG region.

Solution Implemented

The stored script '$HRPAY_PGANZ' has been created based on the ANZ specified format for PNG region.

RELEASE September 2015

HRPC-9 - Overpaid New Zealand 8% termination earnings

HRPC-22 - Reference field on Payroll Deductions

HRPC-44 - Pay out of balance error when processing additional bank accounts

HRPC-54 - Incorrect super calculation for under 18 years of age

HRPC-74 - Unable to select fund code for manual NZ ESCT items

HRPC-86 - Deduction Summary $HR.PAY.DEDNSUM.RPT - criteria and sorting changes

HRPC-95 - HRP SBR Submission of TFN Declarations and PAYG Payment Summaries

HRPC-171 - NZ Pay - New ESCT formula for Grossed Up KiwiSaver contributions

HRPC-173 - Payslips is not showing the correct numbers

HRPC-355 - Payment Summary Issues - Employees who became Contractors mid year are not loaded

HRPC-387 - Cloud 5 Timezone - Payroll Processing changes

HRPC-9 - Overpaid New Zealand 8% termination earnings

Functional Issue

Employees with changed annual leave accrual within current job period would be paid the 8% termination earnings based on the incorrect last accrual date. i.e. Not sourced from the accruals in the current entitlements.

Functional Verification

1. Create a full time employee with annual leave. 2. Assign the employee to an acting position for 6 months which accrues annual leave under a different accrual rule. 3. Create a termination activity after the completion of the acting position period and the next accrual anniversary for the primary position annual leave. 4. Calculate the termination pay. 5. Review the calculation audit. 6. Confirm the 8% termination earnings has been calculated based on the last accrual date for the primary position annual leave. 7. Confirm the unused accrual for the acting position is paid and does not include any 8% termination earnings.

Solution Implemented

Amended the New Zealand termination leave process to ensure the 8% termination earnings is paid based on the active annual leave accrual at the termination date.

HRPC-22 - Reference field on Payroll Deductions

Functional Issue

The Reference Number is not displayed in the Deduction Summary report.

Functional Verification

1. Create or retrieve an existing employee. 2. Ensure the deduction pay component code has a Reference Number in the entitlement. 3. Calculate one or more pay for the employee above. 4. Open the Deduction Summary report. 5. Fill all the mandatory fields. Ensure the employee above is included in the report. 6. Process the report. 7. Confirm that the Reference Number is displayed beside the employee's name.

Solution Implemented

Added the Reference Number from the pay item to the Deduction Summary report.

HRPC-44 - Pay out of balance error when processing additional bank accounts

Functional Issue

The payroll processing raises an out of balance error of -0.01 when additional bank amounts are percentage based and result in an amount to 3 decimals. These are rounded up resulting in an out of balance error with the calculated nett pay amount (also rounded). E.g. The total nett pay for the employee is 635.5. The additional bank account is set to 5% of nett pay which is 31.775. The final nett pay is now 603.725. The amount of each banked amount is rounded up to 2 decimal digits. E.g. 31.78 and 603.73. The total of bank account is now 635.51 which is greater by 0.01.

Functional Verification

1. Find or create an employee that has percentage based additional banking. 2. Set the additional banking to be 5% of nett pay. 3. Calculate the pay for the employee that will result in a total nett pay of $635.50. 4. Confirm that the pay is successful, and there is no out of balance error due to conflicting banking amounts. 5. Confirm the Pay Item Rate and Amount are rounded correctly. E.g. as in the example above, the additional bank account is rounded to $31.78 and the nett pay is $603.72.

Solution Implemented

Updated the payroll calculation process to round additional banking items that have calculated to 3 decimal places due to percentages. Nett pay calculates to the remaining take home amount after all additional banking items are correctly rounded to 2 decimal places.

HRPC-54 - Incorrect super calculation for under 18 years of age

Functional Issue

Company superannuation contributions were being paid for employees under 18 years who have worked less than 30 hours per week in the current pay period and their base superannuation earnings is over $450 for the month.

Functional Verification

1. Assign a SGC superannuation fund to an employee who is less than 18 years old. 2. Ensure the Superannuation control variable 'Minimum Age' (HR_SUP_AGE_MIN) is assigned the value of 18. 3. Ensure the Superannuation control variable 'Min Hours per Week if Under' (HR_SUP_AGE_MIN_HRS) is assigned the value of 30. 4. Ensure the Superannuation control variable 'Minimum Amount' (HR_SUPER_MIN_AMT) is assigned the value 450.00 5. Add base pay to the first pay period in the current month. The payment should be for 29.75 hours and the pay item rate is $15.25 per hour. 6. Calculate the pay with process superannuation selected. 7. Review the pay items generated. 8. Confirm the SGC superannuation has not been generated. 9. Review the calculation audit. 10. Confirm the superannuation section has a message indicating the SGC is not being paid to the employee being less than 18 years and the hours worked are less than 30 for the week. NOTE: If the employee under 18 years works more than the minimum hours per week (30) and has reached the minimum monthly base (450), they will receive SGC and company super for each week of the calendar month they worked excess of 30 hours.

Solution Implemented

Amended the Australian region superannuation process to exclude company and SGC contributions when the employee is less than 18 years of age and the employee has worked less than 30 hours per week (regardless of whether the base superannuation earnings for the current month are $450.00 or more). NOTE: The relevant superannuation control variables as above must be set to these limits.

HRPC-74 - Unable to select fund code for manual NZ ESCT items

Functional Issue

While manually entering pay items for a manual correction pay the pay item grid did not resolve or allow selection of the fund code for New Zealand superannuation ESCT items.

Functional Verification

1. Open the Adjust Correction pay function for an New Zealand employee. 2. Manually enter pay items for the correction including the ESCT superannuation item assigned to the employee's fund. 3. Review the Superannuation Fund / Payee column of the pay item. 4. Confirm the fund code has been resolved for the ESCT item and all other superannuation items entered. 5. Ensure all item are entered for the correction. 6. Calculate the correction with the process Superannuation option not selected. 7. Confirm the pay calculation completes without error. 8. Retrieve the pay and review the ESCT item Superannuation Fund / Payee column. 9. Confirm the superannuation fund has been saved for the ESCT item.

Solution Implemented

Amended the system to ensure manually enter NZ ESCT pay items resolve the applicable superannuation fund.

HRPC-86 - Deduction Summary $HR.PAY.DEDNSUM.RPT - criteria and sorting changes

Functional Issue

The Deduction Summary report needs some changes as below: 1. Report requires new main selection criteria for Company Code and Pay Group. 2. Report requires allowing sorting by employee Family Name or Given Name. 3. Report requires renaming criteria for dates to be: "First Pay Period End Date" and "Last Pay Period End Date"

Functional Verification

1. Open the Deduction Summary report. 2. Confirm that the Company Code, Pay Group, First Pay Period End Date and Last Pay Period End Date are displayed as the criteria in General section. 3. Fill in the company code and/or pay group fields. 4. Change the sort order to family name - ascending. 5. Start Processing. 6. The report should be shown with the correct record order. 7. Run the report with the other sorting criteria. The report should be displayed with the correct order.

Solution Implemented

The Deduction Summary report has been changed as below: 1. Added main criteria for Company Code and Pay Group. 2. Removed Id number as group sorting so user can change the sort order. 3. Added sorting criteria for Family Name and Given Name. 4. Changed the dates criteria label to be "First Pay Period End Date" and "Last Pay Period End Date".

HRPC-95 - HRP SBR Submission of TFN Declarations and PAYG Payment Summaries

Functional Issue

Submission of TFN Declarations and PAYG Payment Summaries are not working as expected

Functional Verification

1. Submit a TFN Declaration via SBR and verify the submission is successful 2. Submit a PAYG Payment Summary via SBR and verify the submission is successful

Solution Implemented

Updated the TFN Declaration and PAYG Payment summary processes to reference latest shipped taxonomy. i.e. ps_0002 and tfnd_0001

HRPC-171 - NZ Pay - New ESCT formula for Grossed Up KiwiSaver contributions

Functional Issue

In some cases New Zealand employers may be "locked in" to an employment agreement where they contribute a set percentage of their employee's salary. In these cases it may be necessary to gross up the employer contribution so the employee receives their full entitlement and requires the ESCT tax to be calculated using the formula provided by the IRD.

Functional Verification

1. Load employee maintenance for a New Zealand employee. 2. Confirm the Superannuation Tax - Kiwisaver or Complying fund type section contains the "Gross Up Employer Contribution (increase ESCT)" checkbox. 3. Confirm the Superannuation Tax - Registered fund type contains the "Gross Up Employer Contribution (increase ESCT)" checkbox. 4. Select the applicable ESCT Gross Up checkbox for the employee's fund type. 5. Calculate the next ordinary pay period. 6. Review the ESCT section of the calculation audit. 7. Confirm the gross company contribution has not been reduced by ESCT. 8. Confirm the ESCT calculation has been completed correctly per the IRD algorithm. i.e. ESCT = a divided by (1 minus a) multiplied by b where: a is the rate of ESCT, and b is the actual amount paid to the fund. 9. Confirm the pay items have been generated per the calculation audit amounts.

Solution Implemented

Amended the Employee maintenance function to include new fields in the New Zealand superannuation tax section for "Gross Up Employer Contribution (increase ESCT)". Amended the pay calculation to process grossed up ESCT per the IRD algorithm. i.e. above the company contribution.

HRPC-173 - Payslips is not showing the correct numbers

Functional Issue

The Payment Advice report is showing incorrect Total and YTD amount when there is any manual entry for superannuation.

Functional Verification

1. Calculate an ordinary pay for an employee. 2. Manually add another superannuation contribution pay item. Set the pay item rate. 3. Ensure the newly added superannuation item has the Super Fund Code in the Superannuation Fund/Deduction Payee column. 4. Re-calculate the payroll for the employee with process superannuation not selected. 5. Run Pay Advice with the new Payment Advice Code ($P1PAYADAU). 6. Confirm that the pay advice superannuation section is showing the correct amounts, Super Fund Code and Super Member Number.

Solution Implemented

The pay process has been modified to ensure that manually added Superannuation items are completed with the correct Super Fund Code and Super Member Number details, thus ensuring all super figures are correct in the pay advice.

HRPC-355 - Payment Summary Issues - Employees who became Contractors mid year are not loaded

Functional Issue

The PAYG Payment Summary details cannot be loaded when an employee has been transferred to the timesheet employee Id class mid year.

Functional Verification

1. Create or find a person with the Employee Id class at the beginning of a financial year. 2. Calculate pays for the employee. 3. Transfer the employee to become a timesheet employee via the Transfer Employee Maintenance - Payroll function. 4. Load the PAYG Payment Summary for the employee in the financial year. 5. Confirm that the PAYG Payment Summary details is loaded.

Solution Implemented

The Load PAYG Payment Summary function has been modified to include the payment summary details of employee who has been transferred to the Timesheet Employee Id class.

HRPC-387 - Cloud 5 Timezone - Payroll Processing changes

Functional Issue

The introduction of Cloud 5 implementations has identified Date and Time issues in Ci where the application uses the local server/client dates and times (i.e. for Today and Now). The dates and times should be replaced with the date and times from the customer's timezone as dictated by the EAS App Store (cloud 5 only) or database server (pre-cloud 5). In Payroll Processing, this issue affects below functions : 1. Adjust Payroll 2. Employee Tax Maintenance 3. Pay Calculation 4. Delete Payroll by Group 5. Multi Company Payroll Calculation

Functional Verification

Adjust Payroll 1. Open Adjust Payroll. 2. Fill in the Id Number with an existing employee. 3. Leave the pay period end date blank then click on the arrow up / down. 4. Pay period end date will be filled with the correct date based on the employee pay period (will default to tomorrow or today when the employee has no job details). Employee Maintenance - Tax 1. Open the Maintain Employee. 2. Create or retrieve existing employee. 3. Create a new employee tax record. 4. The effective date will be filled with today's date - as per the customer's timezone. 5. Complete the tax file number for under 18 - "333 333 333" 6. A warning will be displayed if the employee is no longer under 18 years old. Pay Calculation 1. Open the Calculate Pays. 2. Fill in all mandatory fields. 3. Go to the workset section. 4. Save a new workset. 5. The workset is saved successfully. Delete Payroll 1. Open the Delete Payroll by Group. 2. Delete a payroll calculation. 3. After the payroll deletion is completed, check the log time. 4. The log date and time should refer to the current date and time - as per the customer's timezone. Process Multi Company Payroll Calculation 1. Open the Calculate Payroll for Multiple Company 2. Fill in the mandatory criteria. 3. Start the calculation. 4. After the payroll is completed, check the log time. 5. The log date and time should refer to the current date and time - as per the customer's timezone.

Solution Implemented

Ensured that all calls in this package retrieve the current date or time using the standard infrastructure calls via DBConnection, which applies the customer's timezone offset (cloud 5) or the database server's date/time.

RELEASE July 2015

HRPC-21 - Issue with Read Only Access to the Adjust Payroll Function

HRPC-23 - Bug in Adjust Payroll - pay item account update

HRPC-56 - Unable to retrieve or select employees to calculate Correction Pay by Group

HRPC-61 - EFT Payments Report does not include Deductions paid in Advance

HRPC-98 - Pay Calculation Report not showing all information needed

HRPC-192 - ESCT rate inflated on termination

HRPC-304 - New Zealand ESCT calcuation estimates incorrect.

HRPC-305 - The PNG termination process does not complete when processing the pay.

HRPC-328 - NZ Termination Pay Child Support Error

HRPC-331 - Lump sum tax calculation gross-up income changed.

HRPC-334 - SLCIR is causing an application error in when Gross Taxable is < Student Loan Threshold

HRPC-341 - Student Loan calculating incorrectly in a lump sum tax situation

HRPC-353 - ETP Payment Summary cannot be updated because of validation of legacy data

HRPC-357 - ETP payment missing from PAYG Payment Summary on Rehire

HRPC-359 - No Warning when Loading PAYG Payment Summary with Incorrect ETP Paid Date

HRPC-362 - Human Resource and Payroll Diagnostic Stored Script

HRPC-364 - HELP incorrectly calculating on Termination pays

HRPC-21 - Issue with Read Only Access to the Adjust Payroll Function

Functional Issue

When the Adjust Payroll function is set to read-only, the user is still allowed to update and delete the employee's pay record.

Functional Verification

1. Customise the Adjust Payroll function and set the maintenance restriction to only allow reading 2. Open this read-only Adjust Payroll function 3. Confirm that there is no links in the "Actions to Perform" section 4. Fill in the key fields for an employee's pay and retrieve 5. Confirm that there are only "Bank Download" and "Pay Advice" links in the "Actions to Perform" section. User is unable to update or delete the record.

Solution Implemented

The Adjust Payroll function has been modified to apply the function maintenance restrictions for updating and deleting, thereby supporting a read-only version of Adjust Payroll.

HRPC-23 - Bug in Adjust Payroll - pay item account update

Functional Issue

When the 'Pay Component Code' is changed in the Adjust Payroll function, the 'Ledger Code' and 'Account Number' values are not changed according to the changed pay component code.

Functional Verification

1. Open the Adjust Payroll screen. 2. Retrieve an existing employee pay. 3. Add a new row for another pay item. The payment item details are populated. 4. Change the 'Pay Component Code' to another value. 5. Confirm that the 'Ledger Code' and 'Account Number' values are changed according to the new 'Pay Component Code'.

Solution Implemented

The Adjust Payroll function has been modified to update the 'Ledger Code' and 'Account Number' accordingly when the 'Pay Component Code' is changed to another value.

HRPC-56 - Unable to retrieve or select employees to calculate Correction Pay by Group

Functional Issue

User is unable to retrieve and select employees from the employees grid when calculating Correction Pay Run by Group.

Functional Verification

1. Open the Correction Pay Run by Group. 2. Fill in the key fields. 3. In the processing option, select the 'Process Selected Employees that match the Criteria or Workset below'. Retrieve. 4. Confirm that the Employees grid is filled with the employees that match the criteria. The status is 'Calculated' for the employees that have correction pay. 5. Select employees to be processed from the grid. Start Processing. 6. Confirm that the correction pay is calculated for the selected employees.

Solution Implemented

The Correction Pay Run by Group function has been modified to enable user to retrieve and select employees to be processed based on the key fields input.

HRPC-61 - EFT Payments Report does not include Deductions paid in Advance

Functional Issue

The EFT Payments Report only displays one deduction pay item when there are multiple occurrences of the same deduction in the one pay. i.e. same pay component code and deducted amount.

Functional Verification

1. Open Adjust Payroll. 2. Calculate the pay of an employee with deductions. 3. Add a new pay item that duplicates one of the deductions. i.e. same pay component code and pay item amount. 4. Calculate the payroll. 5. Run the EFT Payments Report ensuring the employee is included 6. The report displays all deduction pay items correctly, including duplicates.

Solution Implemented

The 'view' used in the EFT Payments report has been changed to display all deduction pay items including exact duplicate deductions.

HRPC-98 - Pay Calculation Report not showing all information needed

Functional Issue

Pay Calculation Report displays none of the disbursed pay items with 'Unit Balancing'

Functional Verification

1. Locate a pay that contains disbursed pay items that required a unit balancing item. 2. Open Report | Pay Calculation Report. 3. Complete all mandatory criteria. 4. Select the id Number of the employee whose pay has a 'Unit Balancing' pay item. 5. Process the report. 6. The report displays correctly with all 'Unit Balancing' pay items.

Solution Implemented

The Pay Calculation Report has been changed to display all disbursed 'Unit Balancing' pay items.

HRPC-192 - ESCT rate inflated on termination

Functional Issue

Termination pay for employees who have not worked the full previous tax year were calculating the ESCT based on the current pay amount.

Functional Verification

1. Calculate a termination pay for an employee who has not been employed for all of the previous tax year. 2. Review the superannuation ESCT calculation sections of the calculation audit. 3. Confirm the ESCT withholding rate is based on the employee's saved superannuation tax income estimate.

Solution Implemented

Amended the superannuation ESCT calculation process to derive the withholding rate from the employee's saved superannuation tax estimate. Refer to related details of HRPC-304 New Zealand ESCT calcuation estimates incorrect (for employees starting in the current or previous tax year where less than 12 months has been worked)

HRPC-304 - New Zealand ESCT calcuation estimates incorrect.

Functional Issue

Employee's who have commenced in the current tax year or the previous tax year were calculating an ESCT income estimate based on the current pay period rather than an estimated income for the current period. Employee maintenance did not provide the ability to specify and save a new employee's estimated ESCT income for the first tax year.

Functional Verification

New Starter with hire date in the current financial year: 1. Open Employee Maintenance for a new NZ employee. 2. Confirm the Superannuation Tax - Estimated tax year income section is visible. 3. Confirm the Estimated tax year income section includes the fields Salary or Wages, Company Superannuation, and Last Updated on. 4. Calculate the first ordinary pay period for the employee. 5. Review the Superannuation section of the calculation audit. 6. Confirm the ESCT estimated income has been calculated from the current pay correctly and the audit indicates the estimate was saved to the employee. 7. From Employee Maintenance, review the employee's superannuation tax estimated income section. 8. Confirm the estimated income calculated within the pay process has been saved successfully to the new ESCT fields. 9. Update the estimated income field values and save the change. 10. Confirm the amended values are saved and the last updated date on field has saved today's date. Note: The Employee Administration package is required to enable correct maintenance of the estimated income fields. 11. Calculate the next pay period and review the Superannuation ESCT section of calculation audit. 12. Confirm the ESCT calculation has used the revised estimated income updated via Employee Maintenance. Employee with hire date in previous financial year - but not employed for the full year: 1. Calculate the first pay period after the current financial year start for the employee and review the superannuation ESCT section of the calculation audit. 2. Confirm the ESCT estimated income has been calculated based on the earnings for the previous financial year and the estimate has been calculated correctly. 3. From Employee Maintenance, confirm the estimate for the new financial year has been saved to the employee's superannuation tax estimated income, including the last updated field. 4. Calculate the following pay period and review the superannuation ESCT section of the calculation audit. 5. Confirm the ESCT calculation audit has retrieved the saved estimated income for the current year correctly.

Solution Implemented

Amended the New Zealand pay calculation process to calculate the ESCT estimated income correctly for new starters and enable saving of the employee's estimated income. If the estimated income calculated is deemed to be incorrect the payroll officer can maintain the estimates via the employee maintenance function. New fields have been added to Employee Maintenance, for New Zealand employees under section Superannuation Tax - Estimated tax year income: 1. Salary or Wages 2. Company Superannuation 3. Last Updated on Note: To obtain full functionality of the NZ employee superannuation tax estimate for new employees, both the July 2015 Payroll Processing and August 2015 Employee Administration packages need to be installed. NOTE: Ensure that a Package Finalise is executed after applying this update which will load the new employee superannuation tax estimate fields into your database(s). Please note, the Package Finalise process may take a long time to run.

HRPC-305 - The PNG termination process does not complete when processing the pay.

Functional Issue

The Termination pay calculation for PNG employees does not complete when it cannot find the related pay periods for 12 months before the termination date.

Functional Verification

1. Create an employee working for a PNG company with a hire date more than 12 months before the current date. 2. Ensure pay periods for the employee's pay group are defined for 3 months only before the current date. 3. Create a termination activity for the employee at the current date. 4. Calculate the termination pay. 5. Confirm the termination pay completes. 6. Review the calculation audit. 4. Confirm that a message is displayed in the calculation audit, advising that the System is unable to count the pay periods. E.g. 'Unable to count pay periods for the tax period starting 10-Dec-2013. Pay periods are only defined to 21-Nov-2014 for company 888, pay group F, document type P and pay basis S'.

Solution Implemented

The PNG termination pay calculation process has been changed to ensure it completes when the system cannot find all pay periods for the 12 months before the termination date.

HRPC-328 - NZ Termination Pay Child Support Error

Functional Issue

The New Zealand termination pay calculation would error when the employee has an oncost or additional benefit within their entitlements.

Functional Verification

1. Locate an New Zealand employee who has an additional benefit or oncost within their entitlements and is not paying child support. 2. Create a termination activity. 3. Calculate the termination pay. 4. Review the messages displayed and confirm no error message occurs relating the child support deductions. 5. Review the pay items generated and confirm the pay is correct.

Solution Implemented

Amended the New Zealand child support process to ensure termination pays for employees with oncosts or additional benefits do not error.

HRPC-331 - Lump sum tax calculation gross-up income changed.

Functional Issue

The New Zealand IRD has changed the lump sum PAYE specification to calculate the four-weekly / monthly gross-up income including the current pay period.

Functional Verification

1. Add a lump sum item to the ordinary pay for a fortnightly employee. 2. Calculate the pay with entitlements loaded. 3. Review the calculation audit tax calculation details. 4. Confirm the the last four weeks income including this pay are used in the calculation of the annual grossed up income.

Solution Implemented

Amended the lump sum tax calculation for New Zealand to sum the last four weeks/month income including the current ordinary pay period for the annual grossed up income calculation. For an out of cycle special, correction or bonus pay, the previous four weeks normal pay prior to the date of the out of cycle pay will be used.

HRPC-334 - SLCIR is causing an application error in when Gross Taxable is < Student Loan Threshold

Functional Issue

New Zealand employees with compulsory additional student loan (SLCIR) and taxable income less than the student loan repayment threshold would display an application error.

Functional Verification

1. Locate an employee with an SLCIR deduction assigned to their entitlements. 2. Create unpaid leave to ensure the gross taxable income is less than the student loan repayment threshold of $734.00 per fortnight. 3. Calculate the pay period with entitlements and timesheets loaded. 4. Confirm the SLCIR employee has calculated without error. 5. Confirm the student loan is not deducted. 6. Confirm the SLCIR is not deducted.

Solution Implemented

Amended the New Zealand tax calculation process to correct the message causing the application error when the gross taxable income is less than the student loan repayment threshold.

HRPC-341 - Student Loan calculating incorrectly in a lump sum tax situation

Functional Issue

The student loan repayment threshold was not being assessed while calculating tax on lump sum payments.

Functional Verification

1. Locate an employee with the M SL tax code. 2. Load the next ordinary pay period to be processed for the employee. 3. Add a pay item with the 'LUMP_SUM' configuration code selected and a base pay item that total less than the student loan threshold $19,084.00 per annum. 4. Calculate the pay without entitlements loaded. 5. Review the tax items generated and calculation audit. 6. Confirm the ordinary pay item is taxed correctly. 7. Confirm the lump sum item is taxed correctly. 8. Confirm the student loan is not deducted due to the repayment threshold not being reached.

Solution Implemented

Amended the tax calculation process to ensure lump sum pay items include the student loan repayment threshold while processing the pay. This results in a single Student Loan deduction for all payments - ordinary pay, regular bonus and lump sum.

HRPC-353 - ETP Payment Summary cannot be updated because of validation of legacy data

Functional Issue

When the legacy data of ETP Payment Summary does not have an ETP code, user cannot update the record because the function still validates this payment and displays an error.

Functional Verification

1. Find a legacy ETP payment summary record that has a 'Payment Date' but blank 'ETP Code'. 2. Retrieve the record in the Adjust PAYG payment summary. Without changing any data, Save the record. 3. Confirm that the record is saved correctly.

Solution Implemented

Removed the validation for missing 'ETP Code' and 'Payment Date' of legacy data from the Adjust PAYG Payment Summary function.

HRPC-357 - ETP payment missing from PAYG Payment Summary on Rehire

Functional Issue

The PAYG payment summary does not include the Termination payment details (ETP) when an employee is terminated and rehired in the same financial year.

Functional Verification

1. Terminate an existing or test employee. 2. Process the termination pay, specifying the required ETP pay component code 3. Bank download the termination pay. 4. Rehire the employee within the same financial year. 5. Calculate the employee's first pay in the new employment period. 6. Finalise the pay with a bank download. 7. Open the Adjust PAYG Payment Summaries. 8. Load the PAYG payment summary for the employee twice (for each date of hire within the financial year to load both employment period details into the PAYG). 9. Print the PAYG payment summary 10. Confirm that the Termination payment (ETP) details of the first employment period are included in the payment summary.

Solution Implemented

The PAYG Payment Summaries report has been corrected to load the Termination payment details when the employee's termination and rehire occurs in the same financial year.

HRPC-359 - No Warning when Loading PAYG Payment Summary with Incorrect ETP Paid Date

Functional Issue

There is no warning when loading a payment summary with the ETP Payment Date out of the financial year range. This fails the EMPDUPE loading to the ATO.

Functional Verification

1. Load an employee payment summaries via Adjust PAYG Payment Summary or Load PAYG Payment Summary, where: a. an employee has a termination pay with one or more ETP record(s) b. an ETP payment date has been incorrectly stated out of the financial year of the termination pay. E.g. termination date is 1/12/2014 but the ETP payment date is stated as 15//7/2015 (via the Bank Download). 2. Confirm that a warning is displayed saying 'Invalid ETP Paid Date for employee 'xxxxx' for financial year 'yyyy'. 3. Payment summary is loaded. This allows the user to correct the Paid Date and continue with all payment summaries.

Solution Implemented

Added a warning in the process of loading and saving PAYG Payment Summary when the ETP payment date is out of the financial year range.

HRPC-362 - Human Resource and Payroll Diagnostic Stored Script

Functional Issue

The HRP diagnostic script for accruals and other processes used by support was not shipped with the application.

Functional Verification

1. Open the Payroll Officer workplace. 2. Select the More tab and confirm the HRP Diagnostics menu list is displayed on the tab. 3. Confirm the HRP Diagnostic - Export HRP Diagnostic Data function is listed within the menu list. 4. Select the HRP Diagnostic function and confirm the function opens without errors. 5. Log into the System Administrator - HR/Payroll workplace and select the More tab. 6. Confirm the HRP Diagnostics menu list and function are displayed on the tab. 7. Select the HRP diagnostics function and confirm it opens without errors. 8. Run the diagnostics function for a selected employee Id Number. 9. Confirm the diagnostics zip file is produced and saved to "My Reports and Files"

Solution Implemented

Amended the application to include the HRP Diagnostics stored script within the Payroll Officer and System Administrator - HR/Payroll workplaces.

HRPC-364 - HELP incorrectly calculating on Termination pays

Functional Issue

Termination pay is incorrectly including withholding HELP, TSL or SFSS on unused leave paid out. HELP, TSL and SFSS should not be withheld on termination for any lump sum payments.

Functional Verification

1. Locate an full time employee with HELP selected. 2. Create a termination activity. 3. Calculate the termination pay. 4. Review the calculation audit. 5. Confirm HELP is calculated for the ordinary portion of the termination pay. 6. Review the pay items. 7. Confirm an ordinary HELP item is generated only.

Solution Implemented

Amended the termination tax calculation process to exclude HELP or SFSS for termination leave pay outs and all other termination lump sum payments.

RELEASE June 2015

HRPC-8 - Variances in Calculating Tax Scale 4a

HRPC-19 - Payroll Audit report does not show some YTD totals

HRPC-51 - Calculate payroll by group function does not maintain validation between pay group and pay cycle.

HRPC-60 - Termination leave marginal tax calculation is incorrect

HRPC-65 - Bonus Pay does not withhold HELP

HRPC-78 - Unable to Select Round-down option in Common Rounding Parameters

HRPC-142 - Final Tax file number (TFN) declaration reporting version 2.3.0 published

HRPC-177 - ETP payments incl cap processed incorrectly

HRPC-186 - PAYG withholding – update to specification for self-printing payment summaries

HRPC-306 - Superceded PayAdvice Detailed Rpt - $P1PAYADVC -Payment Advice v2

HRPC-316 - Multiple ETP payments are not loading into the PAYG payment summary

HRPC-321 - The PAYG Payment Summary is missing the ETP pages in the March 2015 package

HRPC-325 - Australian EOFY Legislative changes 2015-2016

HRPC-329 - Package Finalise - ETP duplicate record error

HRPC-340 - ATO 2015 - 2016 Tax Scales Withdrawn

HRPC-8 - Variances in Calculating Tax Scale 4a

Functional Issue

The tax calculation process for tax scales 4a and 4b was not calculating the correct withholding amount. Similarly, employees on a fixed tax rate variation, should apply the same rounding logic for withholding calculation. i.e. As per the ATO specifications on rounding, the correct handling of Tax scale 4a and 4b should be: For scale 4 no coefficients are necessary. To calculate withholding, apply the tax rate to earnings, ignoring any cents in earnings and in the withholding result. For scale 4, cents are ignored when applying the tax rate to earnings and when withholding amounts are calculated.

Functional Verification

1. Load the Tax common Rounding Parameters form for Code Type 'TAX_SCALE_CODE'. 2. Confirm the Code Id 4A and 4B have the Round Down checkbox selected. 3. Calculate an ordinary pay for an employee with tax scale 4a selected. 4. Review the PAYE withholding pay item generated. 5. Confirm the withholding amount generated is correct. i.e. cents ignored 6. Calculate an ordinary pay for an employee with a fixed tax rate specified. 7. Review the PAYE withholding pay item generated. 8. Confirm the withholding amount generated is correct. i.e. cents ignored

Solution Implemented

Updated the tax calculation process to ensure tax scale 4a and 4b withholding is calculated correctly. i.e. Apply the tax rate to the earnings, ignoring any cents in earnings and withholding. Amended the Tax Common Rounding Parameter settings for the shipped Australian Tax Scale Codes 4A and 4B to round down. NOTE: Employees without TFNs do not have ATO loan payments deducted for HELP, SFSS or TSL.

HRPC-19 - Payroll Audit report does not show some YTD totals

Functional Issue

The Ordinary and Overtime hours and amounts are not displayed on the Payroll Audit report.

Functional Verification

1. Open the Payroll Audit report. 2. Input the report criteria. 3. Start Processing. 4. Confirm that the total hours and amounts are displayed for Ordinary YTD and Overtime YTD columns.

Solution Implemented

The Payroll Audit report has been modified to display the total hours and amounts for Ordinary YTD and Overtime YTD columns. NOTE: Other minor field length fixes for the Payroll Audit report can be obtained in the Payroll Processing (May) package.

HRPC-51 - Calculate payroll by group function does not maintain validation between pay group and pay cycle.

Functional Issue

Using the Calculate Payroll by Group function, it is possible to calculate a pay for an employee that does not belong to the pay group being calculated.

Functional Verification

1. Using the Payroll Officer workplace, open the Calculate Payroll by Group function. 2. Fill in the Company Code, Pay Group and Pay Period End Date. 3. Select the Processing Option of "Process Selected Employees that match the Criteria or Workset below". 4. Enter an employee Id that does not belong to the Pay Group manually. 5. Confirm that an error is displayed saying that the employee latest Job Details do not match the Pay Group. E.g. "Employee '9913's latest Job Details do not match Pay Group 'A'. Pay will not be calculated." 6. Click "Start Processing". 7. Confirm that payroll is calculated for the valid employee only. The error is displayed in the log file for the invalid employee saying that the employee latest Job Details do not match the Pay Group. E.g. "Employee '9913's latest Job Details do not match Pay Group 'A'. Pay will not be calculated."

Solution Implemented

The Calculate Payroll by Group function has been modified to exclude the record and raise an error when the processed employee does not belong to the pay group being calculated. E.g. "Employee '9913's latest Job Details do not match Pay Group 'A'. Pay will not be calculated."

HRPC-60 - Termination leave marginal tax calculation is incorrect

Functional Issue

The calculation of the $AU region termination leave taxed at the marginal rate did not disregard cents when converting the taxable income to the pay period equivalent.

Functional Verification

1. Calculate a resignation termination pay that includes leave paid at termination. 2. Review the termination tax calculation section of the calculation audit. 3. Confirm whole dollars only are added to the normal gross income.

Solution Implemented

Amended the $AU region tax calculation to ensure cents are disregarded when adding the pay period equivalent taxable income to the ordinary gross earnings.

HRPC-65 - Bonus Pay does not withhold HELP

Functional Issue

The tax calculation did not withhold HELP from bonus pays

Functional Verification

1. Calculate a bonus pay for an employee with HELP. 2. Review the HELP pay item generated and the calculation audit. 3. Confirm the HELP is for the correct amount. Note: Ensure the employee's base pay is above the HELP repayment threshold.

Solution Implemented

Amended the tax calculation to ensure HELP is withheld for bonus pays.

HRPC-78 - Unable to Select Round-down option in Common Rounding Parameters

Functional Issue

The Tax Common Rounding Parameters form did not display or save changes for the Code Type 'TAX_SCALE_CODE' Round Down, Round Up and Mid Point Round Up checkboxes.

Functional Verification

1. Open the Tax common Rounding Parameters form and retrieve the Code Type 'TAX_SCALE_CODE'. 2. Select the Round Down checkbox for one of the existing Code Id's. 3. Save the change and retrieve. 4. Confirm the selected checkbox has been saved.

Solution Implemented

Amended the Tax Common Rounding Parameters form to ensure the Round Down, Round Up and Mid point Round Up checkboxes are displayed and saved correctly.

HRPC-142 - Final Tax file number (TFN) declaration reporting version 2.3.0 published

Functional Issue

The ATO has published an updated Tax file number (TFN) declaration reporting version 2.3.0. Changes include: 1. ATO report specification version number has changed from FTFNDV02.0 to FTFNDV02.3 2. Field name - 7.68 HELP indicator has been changed to 7.68 Higher Education Loan Programme (HELP) or Trade support loan (TSL). 3. Field name - 7.69 - Student loan indicator in the data record file has been corrected to match definition name 7.69 - Student Financial Supplement Scheme indicator.

Functional Verification

1. Run Electronic TFN Declarations choosing e-file transmission for the current reporting period. 2. Review the file's version number reported in the supplier line. 3. Confirm the version is 'FTFNDV02.3'

Solution Implemented

Updated the ATO electronic TFN declaration process version to the current value. No other changes impact this file.

HRPC-177 - ETP payments incl cap processed incorrectly

Functional Issue

ETP payments added to a termination pay did not process correctly when the termination pay item type was not selected. i.e. Manual pay item entry The ETP cap was not reduced correctly when a pay included both excluded and non-excluded ETP payments. i.e. Was not being reduced prior to comparison to Whole of income cap.

Functional Verification

1. Add an ETP payment to a termination pay, do not select the Termination pay item type. 2. Calculate the pay. 3. Review the calculation audit for the normal pay process tax calculation and the termination pay process tax calculation. 4. Confirm the ETP payment's tax was calculated during the termination pay process only. 1. Add an excluded ETP payment (code R) to a termination pay. 2. Add an non-excluded ETP payment (code O) to the same termination pay. 3. Calculate the termination pay. 4. Review the calculation audit tax calculation for the termination pay process. 5. For the withholding calculation of the code O payment confirm the ETP cap is reduced by the amount of the code R payment. Note: The ETP cap is reduced before the comparison with the whole of income cap to ascertain the lesser of the two caps.

Solution Implemented

Amended the ETP tax calculation process to ensure the withholding amount is calculated during the termination pay process only. Amended the ETP tax calculation process to ensure the ETP cap is reduced by excluded ETP payments before the comparison with the whole of income cap.

HRPC-186 - PAYG withholding – update to specification for self-printing payment summaries

Functional Issue

The PAYG payment summary has been updated by the ATO with a new Privacy statement. Additionally, minor changes are required to be in adherence with the ATO specification for self-printing withholding payment summaries. i.e. Order of additional details and restoration of the "Total Allowances" box.

Functional Verification

1. Confirm the following details are displayed. - There is a new line stating "Privacy - For information about your privacy, go to ato.gov.au/privacy" in the Payer details section, under the Payer's name. - The "Total Allowances" text and amount are displayed under the "Reportable employer superannuation contributions". - In the Allowances details, there is no "Total Allowances" line displayed. - In the Allowances details, the allowances are displayed in 2 items per line. - The "Deductible amount of the undeducted purchase price of an annuity" section is displayed under the "Exempt foreign employment income". - The sections details are displayed in the following order: * Allowances * Deductions * Workspace giving * Exempt foreign employment income * Deductible amount of the undeducted purchase price of the annuity. - There is no header detail for the following sections: * Workplace Giving * Exempt foreign employment income * Deductible amount of the undeducted purchase price of the annuity. - The employee payment summary is printed in one page only, excluding any additional ETP pages. 2. If using Multiple Company Payroll Processing functionality, run the Print PAYG Payment Summary across Multiple Companies report process. - Specify Financial Year - Specify Id Number range - NOTE: No Company Code is required and can be included in the additional criteria. - Confirm that the above changes are applied in each PAYG payment summary included.

Solution Implemented

The Print PAYG Payment Summary and Print PAYG Payment Summary across Multiple Companies reports have been updated to conform to the latest ATO specification (v5.2.2) self-printing withholding payment summaries specification.

HRPC-306 - Superceded PayAdvice Detailed Rpt - $P1PAYADVC -Payment Advice v2

Functional Issue

$P1PAYADVC -Payment Advice v2 (crystal report named PayAdviceDetailed.rpt) has been superceded due to corrections and enhancements. Refer to remaining shipped document definitions for Pay Advices for alternative solutions.

Functional Verification

Document Definition for $P1PAYADVC -Payment Advice v2 is no longer available for selection when producing Pay Advices.

Solution Implemented

Document Definition $P1PAYADVC -Payment Advice v2 has been removed from the shipped product.

HRPC-316 - Multiple ETP payments are not loading into the PAYG payment summary

Functional Issue

The PAYG payment summary process did not load all payment summaries for the financial year end date.

Functional Verification

1. Locate an employee with multiple ETP payments within the current financial year. 2. Open the Adjust PAYG Payment Summary form for the employee. 3. Select Load. 4. Confirm the Employment Termination Payment grid displays all payment summaries for the employee.

Solution Implemented

Amended the payment summary load process to ensure multiple ETP payments within the financial year are loaded.

HRPC-321 - The PAYG Payment Summary is missing the ETP pages in the March 2015 package

Functional Issue

The Payroll Processing package from March 2015 included the PAYG Payment Summary reports with a missing ETP subreport section.

Functional Verification

1. Run the Print PAYG Payment Summary report for an employee who has one or more Termination Payments in the financial year being processed. 2. Confirm that the ETP pages are included in the PAYG Payment Summary with the correct ETP details. 3. Run the Print PAYG Payment Summary across Multiple Companies report for a Pay Group which includes employees who have Termination Payments in the financial year being processed. 4. Confirm that the ETP pages are included in the PAYG Payment Summary, with the correct ETP details.

Solution Implemented

The ETP pages (subreport) has been restored to the PAYG Payment Summary, including the Multiple Company pay processing version.

HRPC-325 - Australian EOFY Legislative changes 2015-2016

Functional Issue

The Australian Tax Scales including HELP income thresholds and SFSS repayment thresholds are to be updated for the 2015 - 2016 financial year. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2015. The indexed ETP Cap will increase from 1 July 2015. The Maximum super contribution base amount will increase from 1 July 2015.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Normal Tax Scales (Tax Scales -> $AU - Australia): 4. Confirm that Tax Scales 1, 2, 3, 4a, 4b, 5, 6 are available for the 1 July 2015. 5. Confirm that Tax Constants for tax scales 2 and 6 are available for the 1 July 2015. Noting the change to Medicare Levy low income thresholds. 6. Navigate to the HELP and TSL income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP and TSL): 7. Confirm that HELP income thresholds are available for the 1 July 2015. 8. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS): 9. Confirm that SFSS repayment income thresholds are available for the 1 July 2015. 10. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Tax Scales -> $AU - Australia -> AU_GRTFL): 11. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2015. 12. Navigate to the Taxation section of the default control variables: 13. Confirm that the ETP Cap Amount is 195,000 (NOTE: Override with 185,000 until 1 July 2015). 14. Navigate to the Superannuation section of the default control variables: 15. Confirm that the Max Quarterly Base is 50,810. 16. NOTE: Check if ETP Cap Amount or Max Quarterly Base need to be updated for other customised Control Variable groups.

Solution Implemented

Added new Australian Tax Scale co-efficients, HELP income thresholds and SFSS repayment thresholds for the 2015 - 2016 financial year (refer to ATO website). Updated the Genuine redundancy payments and early retirement scheme thresholds (refer to ATO website). Updated the Control Variable for ETP Cap Amount (from 185,000 to 195,000). Updated the Control Variable for the Superannuation Maximum Quarterly Base (to 50,810). The ATO have added the Trade Support Loan (TSL) to the HELP scales and updated the description to 'HELP and TSL'. Although changed within our shipped standard codes, the description of this code will not be updated on existing installations. If you wish to update the HELP scales description, maintain the Standard Code Type 'TAX_SCALE_TYPE' Code Id 'AU_HELP' description to 'HELP and TSL'. NOTE: Future enhancements to Employee Taxation within the HR & Payroll product will support the new additional TSL (Trade Support Loan) on top of the current HELP and SFSS. i.e. In the event an employee has both a HELP and TSL to repay. In the meantime, a TSL can be configured with a new pay component code marked with HELP configuration, including checking the HELP option marked in the employee's taxation details. NOTE: Ensure that a Package Finalise is executed after applying this update which will load the new tax details into your database(s). Please note, the Package Finalise process may take a long time to run.

HRPC-329 - Package Finalise - ETP duplicate record error

Functional Issue

Running Payroll Processing package finalise after ETP config codes have been updated results in a duplicate key database update error. E.g. Violation of PRIMARY KEY constraint 'HRFSPC_IDX1'. Cannot insert duplicate key in object 'dbo.HRSYS_PAYCOMP_CFG'. The statement has been terminated. :- UPDATE hrsys_paycomp_cfg SET config_code = @NewEtpCode__1, last_mod_user = @SQL_User__2, last_mod_datei = @SQL_Today__3, last_mod_term = @SQL_Node__4, last_mod_window = @Window__5, vers = vers +1 WHERE config_code = @SupercededEtpCode__6 AND pay_component_ref IN (600.0,601.0,602.0,603.0,604.0,605.0,606.0,607.0,608.0,609.0) Completed processing Online Upgrade - Failed

Functional Verification

1. Download and install the latest Payroll Processing package, running the Package Finalise 2. No duplicate key errors are reported and the package finalise completes successfully. 3. Maintain Pay Components for ETP lump sums (pay component type 600) 4. For ETP Death payments still marked with $AU Regional config code ETP_DTH_O (superseded 2012/13), ensure that the replacement ETP_DTH_N config code (correct) is checked. 5. Uncheck the superseded config code ETP_DTH_O. No longer required. NOTE The package finalise log will include information messaging to advise that ETP pay components configuration may need maintenance. The ETP pay component codes should be corrected by unchecking all superseded ETP config codes. This avoids rerunning this step unnecessarily in the Payroll Processing Package Finalise.

Solution Implemented

Updated the ETP online upgrade process in Payroll Processing to log messages only. i.e. Not to error on failed attempts to update existing ETP_DTH_O pay components as ETP_DTH_N config code.

HRPC-340 - ATO 2015 - 2016 Tax Scales Withdrawn

Functional Issue

The Australian Tax Scale changes released by the ATO on 28 May 2015 for the 2015 - 2016 financial year were withdrawn by the ATO on 9 June 2015. Updated 2015 Pay as you go withholding (PAYGW) tax tables were subsequently issued including changes to the HELP income thresholds and SFSS repayment thresholds as per the May 2015 budget announcements.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Normal Tax Scales (Tax Scales -> $AU - Australia): 4. Confirm that Tax Scales 1, 2, 3, 4a, 4b, 5, 6 are available for the 1 July 2015. 5. Confirm that Tax Constants for tax scales 2 and 6 are available for the 1 July 2015. 6. Navigate to the HELP and TSL income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP and TSL): 7. Confirm that HELP income thresholds are available for the 1 July 2015. 8. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS): 9. Confirm that SFSS repayment income thresholds are available for the 1 July 2015.

Solution Implemented

Amended the Australian Tax Scale co-efficients, HELP income thresholds and SFSS repayment thresholds for the 2015 - 2016 financial year (refer to ATO website). NOTE: Ensure that a Package Finalise is executed after applying this update which will load the new tax details into your database(s). Please note, the Package Finalise process may take a long time to run.

RELEASE March 2015

HRPC-62 - Pay Advice generation failed.

HRPC-87 - Incorrect YTD figures are displayed in the Payroll Pay Advice Summary section.

HRPC-126 - Allowances and Deductions Summary Report has incorrect format.

HRPC-138 - Superannuation Costing is Split and I don't want it to be

HRPC-155 - Multi Company Payroll Processing

HRPC-160 - Not a Valid Pay Group on Bank Download processing

HRPC-62 - Pay Advice generation failed.

Functional Issue

When the Pay Advice process fails, the error message and log do not identify which employee failed the process.

Functional Verification

1. From Payroll Officer workplace 2. Open the function to process Pay Advices (to print or email) 3. Select option to 'Save Pay Advice'. 4. Set the Test Print Emails or Fax. 5. Run the process for several employees who have their 'Pay Advice Transmit Method' option set to 'Email' or 'Fax'. 6. Check the error messages displayed or open the log file. 7. Confirm that additional error messages now specify which employees failed the process. E.g. 'Failed to generate pay advice successfully for employee '323858' of Company '12345', Pay Period '8/01/2016' and Pay Group 'MC6'. Attempted email Address: test@email.com'. NOTE: To force these exception conditions for the testing of printing/emailing or saving pay advices, revoke user authorization or write access from the server folders specified for saving attachments for pay advices or exporting Crystal report files.

Solution Implemented

The Pay Advice print process has been modified to raise more informative error messages that identify the employees who have failed to have a pay advice successfully printed, emailed or saved due to system or access errors.

HRPC-87 - Incorrect YTD figures are displayed in the Payroll Pay Advice Summary section.

Functional Issue

The document types to be excluded from YTD figures as defined in the Control Variable "Exclude from YTD" (HR_YTD_EXCLUDE), are not used in the Adjust Pay function's Payroll Pay Advice Summary section.

Functional Verification

1. From Control Variable Maintenance (e.g. for DEFAULT group), confirm or add the document type G (Payroll Liability) to the "Exclude from YTD" variable (HR_YTD_EXCLUDE). 2. Calculate Payroll liability prior to the next pay period end date. 3. Calculate Payroll for the next pay period. 4. From Adjust Payroll, confirm that in the YTD figures in Payroll Pay Advice Summary section are calculated correctly without including the payroll liability amounts generated in step 2.

Solution Implemented

The Payroll Pay Advice Summary of the Adjust Payroll function has been modified to exclude the document types listed in the "Exclude from YTD" Control Variable from the displayed YTD figures.

HRPC-126 - Allowances and Deductions Summary Report has incorrect format.

Functional Issue

The Allowances and Deductions Summary report has the Id Numbers displayed with commas. The same issue appears in several other payroll reports. The Pay Component Summary report truncates the pay period date fields in the header section.

Functional Verification

1. Confirm that the employee Id Numbers in the following reports are not displayed with commas. - The Allowances and Deductions Summary report. - The Deduction Summary report. - The EFT Payment report. - The Account Amount report. 2. Run the reports below with maximum length Pay Period criteria (E.g. 31/07/2014). Confirm that the Pay Period fields are not truncated in the header section. - Pay Component Summary report. - Pay Component Summary by Department report. - Pay Component Summary by Pay Calculation report. - Pay Component Summary by Pay Locn/Dept report. 3. Confirm that the ACN or ABN field is removed from the header of the Allowances and Deductions Summary report. 4. Open the Deduction Summary report. Add the Extended Criteria of Pay Component Code. Confirm that it allows a decimal value. E.g. 810.1

Solution Implemented

The Id Number in the following reports have been updated to be displayed with no commas. - The Allowances and Deductions Summary report. - The Deduction Summary report. - The EFT Payment report. - The Account Amount report. The Period fields in reports below have been modified to be displayed in full length (dd/mm/yyyy). - Pay Component Summary report. - Pay Component Summary by Department report. - Pay Component Summary by Pay Calculation report. - Pay Component Summary by Pay Locn/Dept report. The ACN or ABN field has been removed from the header of the Allowances and Deductions Summary report. Allow the decimal value for the Pay Component Code in the Extended Criteria section of Deduction Summary report.

HRPC-138 - Superannuation Costing is Split and I don't want it to be

Functional Issue

Superannuation Costing was enhanced to automatically split across all positions held be the employee in the calculated pay period. Some customers do not want this functionality however there is no way to turn this option off.

Functional Verification

1. Verify the Control Variable "Allow Split Costing" is set to "No". This may require System Administrator access 2. Set up an employee with a primary and secondary position and superannuation that calculates for both positions. 3. Calculate a pay 4. Verify Superannuation is calculated against the full amount of both positions, but the costing details are only allocated against the primary position. 5. Alternatively, for having Superannuation costs split across multiple positions, set the Control Variable "Allow Split Costing" is set to "Yes". This may require System Administrator access 6. Set up an employee with a primary and secondary position and superannuation that calculates for both positions. 7. Calculate a pay 8. Verify Superannuation is calculated against both positions separately, and the costing details are allocated against both primary and secondary positions.

Solution Implemented

A new Control Variable is available which allows customers to select if Superannuation Costing should be split by position - "Allow Split Costing" (HR_SUP_COST_SPLT) under the Superannuation section. By default, this control variable will be set to Yes.

HRPC-155 - Multi Company Payroll Processing

Functional Issue

The main objective of the Multi Company Payroll Processing enhancement is to improve productivity and usability for payroll users by providing a single interface to process pays across multiple companies that share the same pay cycle. For example, calculate all fortnightly employee pays due 2/10/2014. In addition to calculating pays, other bulk payroll processes that can be enhanced by processing across multiple companies include: 1. Leave accruals 2. Payroll liabilities 3. Leave liabilities 4. Special pays 5. Bonus pays 6. Correction pays 7. Bank download 8. Payroll posting to financial ledgers The summary and statutory reports associated with these payroll processes will also support multiple company selection. For example, pay advice, payment summaries, EFT (bank download).

Functional Verification

1. Log on as Payroll Officer 2. From the Reports tab, choose from the following Multiple Company reporting functions available: a. EFT Payments Report across Multiple Companies ($HR.PAY.EFTPAYMC.RPT) b. Employee Leave Accrued this Period across Multiple Companies ($HR.EACCPRDMC.RPT) c. Print PAYG Payment Summary across Multiple Companies ($HR.TAX.PAYGSMMC.RPT) - grouping by Company in addition to new sorting for Id Number, Family Name and Given Name d. PAYG Payment Summary Listing across Multiple Companies ($HR.TAX.PAYGLMC.RPT) - original report updated to page break by Company e. ETP Listing Report across Multiple Companies ($HR.TAX.ETPLSTMC.RPT) - original report updated to page break by Company 3. From the Processing tab, choose from the following Multiple Company payroll processing functions available: a. Bonus Pay Run for Multiple Companies ($HR.PAY.PAYR.BMC.PRC)

Solution Implemented

Phase 3 Delivery: 1. Additional Multiple Company payroll processing functions have been delivered, including: a. Bonus Pay Run for Multiple Companies ($HR.PAY.PAYR.BMC.PRC) 2. New payroll reports have been provided to support pay and End of Year functions for Multiple Companies: a. EFT Payments Report across Multiple Companies ($HR.PAY.EFTPAYMC.RPT) b. Employee Leave Accrued this Period across Multiple Companies ($HR.EACCPDMC.RPT) c. Print PAYG Payment Summary across Multiple Companies ($HR.TAX.PAYGSMMC.RPT) d. PAYG Payment Summary Listing across Multiple Companies ($HR.TAX.PAYGLMC.RPT) e. ETP Listing across Multiple Companies ($HR.TAX.ETPLSTMC.RPT) NOTE: Pay Group criteria selection is not available in Print PAYG Payment Summary A new Report menu, called "Multiple Company Processing Reports" is shipped to allow easy customisation on the Reports tab of the Pay Officer workplace. The three Multiple Company reports that were previous shipped in the Processing menu ""Payroll Processing across Multiple Companies" have been moved to this new menu. 3. The existing Print PAYG Payment Summary report has also been updated to allow sorting by a number of fields, including Surname and First Name. NOTE: To obtain the full functionality as outlined for this enhancement, the following packages must also be installed: 1. Payroll Processing 2. Accruals

HRPC-160 - Not a Valid Pay Group on Bank Download processing

Functional Issue

After selecting a Bank and Branch (BSB) Number on the Bank Download screen, a message is returned stating "Not a valid Pay Group" along with the bank code relating to the selected BSB

Functional Verification

1. From the Payroll Officer workplace, navigate to the Bank Download function on the Processing Tab 2. Verify the first data entry field is labelled "Bank Account Format" and its associated picklist contains details of existing Bank Download Formats 3. Verify Bank and Branch Number is now the second data entry field 4. Open the pick list associated with the Bank and Branch Number data entry field and make a selection, ensuring the Bank Account Format field remains blank 5. Verify the correct BSB is returned to the field and no errors occur

Solution Implemented

The Bank Download function has been modified to improve usability by making Account Number the first data entry field and renaming it to "Bank Account Format" to re-enforce that existing formats are required for selection. The Bank and Branch Number pick list has been corrected so as not to display an erroneous error notification .

RELEASE January 2015

HRPC-12 - New Zealand SLCIR Deductions

HRPC-17 - Cannot run pays concurrently - Payroll Processing

HRPC-110 - New Zealand ANZ & HSBC bank downloads

HRPC-112 - Multi Company Payroll Processing

HRPC-140 - New Zealand Legislative changes effective 1 April 2015

HRPC-12 - New Zealand SLCIR Deductions

Functional Issue

1. The new Zealand additional compulsory student loan (SLCIR) deduction is not generated for pay calculations when entitlements are not loaded. E.g. When processing a Correction Pay for the employee after a normal pay has been processed and paid. 2. The SLCIR is not deducted correctly for termination pays where leave accrual is paid out.

Functional Verification

Correction pay: 1. Assign the 'M SL' tax code and an SLCIR deduction to a New Zealand employee. 2. Calculate an ordinary pay period with entitlements loaded. 3. Confirm the standard student loan and SLCIR are deducted. 4. Open the adjust Correction Pay for employee function and enter the same period end date as the ordinary pay. 5. Add extra hours (e.g. overtime) and calculate the correction without entitlements loaded. 6. Confirm the standard student loan is deducted correctly. 7. Confirm the additional Student Loan deduction SLCIR is deducted correctly. i.e. 41.67% of standard student loan deduction. Termination Pay: 1. Calculate a termination pay for the employee above. 2. Confirm the standard student loan is deducted for the ordinary pay and the termination leave correctly. 3. Confirm the SLCIR is deducted correctly for the total of all standard student loan deductions.

Solution Implemented

Amended the pay process to deduct SLCIR correctly for correction and termination pays.

HRPC-17 - Cannot run pays concurrently - Payroll Processing

Functional Issue

When processing payroll from concurrent processes, i.e. multiple DP's, one or more of the processes may terminate displaying a Duplicate Key violation error, resulting in not all of the pays being processed.

Functional Verification

Process payroll concurrently from multiple DP's and verify each pay run completes successfully (i.e. without duplicate key errors).

Solution Implemented

The pay process has been amended to check for duplicate key violations on document number that can occur due to concurrent processing. The process will retry for a unique document number to a maximum of 5 attempts before failing to save a specific employee pay.

HRPC-110 - New Zealand ANZ & HSBC bank downloads

Functional Issue

The system does not currently ship a New Zealand bank download script for the ANZ bank. The $HRPAY_NZHSBC bank download script does not set the pay paid date when an additional document type is specified or a bulk bank download is being processed.

Functional Verification

$HRPAY_NZANZ: 1. Create a New Zealand bank branch (region $NZ), specifying its Download Script as $HRPAY_NZANZ. 2. Create a new Bank Download Format and assign the bank branch created in Step 1. 3. Calculate an ordinary pay period. 4. Run the Bank Download for the pay period using the new Bank Download Format for NZ ANZ. 5. Confirm the bank download process completes without error. 6. Confirm the bank download file is created correctly (as per the NZ ANZ format). 7. Confirm the pay is marked as paid. $HRPAY_NZHSBC: 1. Create a New Zealand bank branch (region $NZ), specifying its Download Script as $HRPAY_NZHSBC . 2. Create a new Bank Download Format and assign the bank branch created in Step 1. 3. Calculate an ordinary pay for an employee. 4. Run the Bank Download for the pay period, ensuring the 'R' (Back Pay) additional document type is specified. 5. Confirm the bank download process completes without error. 6. Confirm the bank download file is created correctly (as per NZ HSBC format). 7. Confirm the pay is marked as paid. 8. Calculate an ordinary pay period for a group of employees. 9. Run the Bank Download for the pay period. 10. Confirm the bank download process completes without error. 11. Confirm the bank download file is created correctly. 12. Confirm the pays are marked as paid.

Solution Implemented

Added a New Zealand bank download script for the ANZ bank and National bank. Amended the New Zealand HSBC bank download script to ensure the paid date is saved to the pay.

HRPC-112 - Multi Company Payroll Processing

Functional Issue

The main objective of the Multi Company Payroll Processing enhancement is to improve productivity and usability for payroll users by providing a single interface to process pays across multiple companies that share the same pay cycle. For example, calculate all fortnightly employee pays due 2/10/2014. In addition to calculating pays, other bulk payroll processes that can be enhanced by processing across multiple companies include: 1. Leave accruals 2. Payroll liabilities 3. Leave liabilities 4. Special pays 5. Bonus pays 6. Correction pays 7. Bank download 8. Payroll posting to financial ledgers The summary and statutory reports associated with these payroll processes will also support multiple company selection. For example, pay advice, payment summaries, EFT (bank download).

Functional Verification

1. Log on as Payroll Officer 2. From the Processing tab, choose from the additional Multiple Company processing functions available: 3. Bank Download for Multiple Companies ($HR.PAY.BNKDLMC.PRC) 4. Correction Pay Run for Multiple Companies ($HR.PAY.PAYR.CMC.PRC) 5. Special Pay Run for Multiple Companies ($HR.PAY.PAYR.SMC.PRC) 6. Calculate Payroll Liability for Multiple Companies ($HR.PAY.PAYR.GMC.PRC) 7. Calculate Leave Liability for Multiple Companies ($HR.PAY.PAYR.FMC.PRC) 8. If you have custom Payroll workplaces, ensure the users have access to these new Multiple Company processing functions (via System Administrator). 9. To permit companies to be processed by the Multiple Company Bank Download function, ensure that bank format details are specified for each company via Company Maintenance. 10. To specify default file names for bank downloads, set file name defaults in the Bank Download Format Maintenance function. Options include: a. Default File Name b. Append Pay Period End Date to File Name. (Yes/No) Will place the date of the latest unpaid pay after the default file name. E.g. Wages.20141231.aba c. Default Archive File Name d. Default File Suffix (e.g. .aba, or .txt) These file name defaults can be changed in the Bank Download process function as required.

Solution Implemented

Phase 2 Delivery: 1. Additional Multiple Company payroll processing functions have been delivered, including: a. Bank Download for Multiple Companies ($HR.PAY.BNKDLMC.PRC) b. Correction Pay Run for Multiple Companies ($HR.PAY.PAYR.CMC.PRC) c. Special Pay Run for Multiple Companies ($HR.PAY.PAYR.SMC.PRC) d. Calculate Payroll Liability for Multiple Companies ($HR.PAY.PAYR.GMC.PRC) e. Calculate Leave Liability for Multiple Companies ($HR.PAY.PAYR.FMC.PRC) 2. Enhancement to Bank Download Format Maintenance enables all customers to specify file naming defaults for any bank download format defined. New fields include: a. Default File Name b. Append Pay Period End Date to File Name. (Yes/No) Will place the date of the latest unpaid pay after the default file name. E.g. Wages.20141231.aba c. Default Archive File Name d. Default File Suffix (e.g. .aba, or .txt) 3. Enhancement to Bank Download function that indicates when Corrective Access is turned ON for the user. Additionally information text on the screen also informs the user that a reproduction of a complete bank download file will occur. i.e. Including both unpaid and paid employee pay for the selected criteria in the generated bank file. 4. Enhancement to Company Maintenance to include new Bank Download Detail fields (BSB and Account). This identifies which format will be used for the company pay. Company's on the same pay cycle can be included in a single bank file by using the same Bank Download details (Format with BSB and Account). NOTE: To obtain the full functionality as outlined for this enhancement, the following packages must also be installed: 1. Human Resource & Payroll Core 2. Payroll Management 3. Payroll Processing

HRPC-140 - New Zealand Legislative changes effective 1 April 2015

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2015.

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2015 and are for the correct percentage and maximum levy. The Earners Levy percentage for 1 April 2015 is 1.45% for annual income less than $120,070.00 and the maximum levy is $1741.01. 2. Calculate an ordinary pay after the 1st April 2015 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Truncate pay period income for PAYE calculation of Special tax codes specified on an IR23 Certificate: 1. Create a new employee and assign their tax details to the STC tax code and enter an Specified Tax Rate. 2. Add to an ordinary pay a base pay item for $999.99. 3. Calculate the pay. 4. Review the tax calculation section of the calculation audit. 5. Confirm the tax was calculated on the pay period amount of $999.00. Regular monthly bonuses covering more than one pay period (E.g. paid fortnightly or weekly): 1. Confirm the $NZ region configuration code 'BONUS_REG' - Regular Bonus is defined on pay component type 100 - ordinary Time, 110 - Back pays, 200 - Overtime, 400 - Allowances - Manual Entry Only, 410 - Allowances, 500 - Absences and 600 - Lump Sum Payments. 2. Create a taxable pay component with the regular bonus configuration selected. 3. Add a regular bonus item to an fortnightly period ordinary pay and calculate. 4. Review the calculation audit and confirm the bonus is taxed as a monthly bonus covering multiple pay periods, per the IRD calculation steps. 5. Confirm that a separate PAYE tax item is generated for the regular bonus. NOTE: Monthly regular bonuses paid in a monthly pay period do not need require the "BONUS_REG" configuration.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2015: - The ACC Earners Levy tax scales have been updated and apply to pay on or after 1 April 2015. - The tax calculation process was updated to truncate the pay period income correctly for employees on the Special Tax Code (STC) with a tax rate specified on the IR23 certificate. - The pay calculation process has been updated to enable the calculation of PAYE tax for monthly regular bonuses that are paid across more than one pay period. A new payroll NZ configuration code has been introduced to identify these pay items - BONUS_REG. The IRD have changed the description for the WT tax scale code from 'Withholding Tax' to 'Schedular Payment'. Although changed within our shipped standard codes, the description of this code will not be updated on existing installations. If you wish to update the employee tax details description, maintain the Standard Code Type 'TAX_SCALE_CODE' Code Id 'WT' description to 'WT - Withholding Tax (Schedular Payment)'. NOTE: The WT tax scale code has not been changed by the IRD. Ensure that a Package Finalise is executed after applying this update which will load the new tax data into your database(s). Verify that this update has successfully uploaded the correct Tax and other scales from the Payroll Officer Administration Console. The Package Finalise process may take a long time to run.

RELEASE October 2014

AR 201875, 284913, 304617 - Asking for 1 payslip from Process Payment Advice function

AR 317446 - Special pay not showing on PAYG summary when balancing payroll

AR 323851 - Multi Company Payroll Processing

AR 329872, 333475, 343905 - Optional Super based on a percentage does not calculate correctly

AR 332381, 337012, 338156, 338327, 338299, 338743, 338735, 339569, 340769, 340954, 341545 - Unable to process leave accrual for employee

AR 337263, 337135, 338008, 338004, 337896, 338252, 338819, 342251 - Pay item explanation not showing for non superannuation pay components in Adjust Payroll

AR 201875, 284913, 304617 - Asking for 1 payslip from Process Payment Advice function

Functional Issue

Additional Pay Advices are generated when the Date Paid selection criteria is used to filter report results. This issue occurs when: 1. similarly grouped pay advices (i.e. same company, pay group and pay period end date) have different paid dates, and 2. the pay advices are generated from the Process Payment Advices function (E.g. Payroll Officer workplace > Processing tab > Payroll Processing menu > Pay Advice).

Functional Verification

1. Find two pays with the same pay period end date but differing paid dates (Company Code and Pay Group need to be the same for the two pays) 2. Navigate to the Process Payment Advices function (E.g. Payroll Officer workplace > Processing tab > Payroll Processing menu > Pay Advice) 3. Specify criteria to filter pays to process by setting the Paid Date equal to one of the pays above 4. Select the returned Periods to Process with the number of Employees included (i.e. 1) and Start Processing 5. Verify that only one pay advice is generated and which matches the Paid Date criteria specified.

Solution Implemented

Amended the Pay Advice reporting process to correctly use the specified Date Paid selection criteria when selecting employees to report on.

AR 317446 - Special pay not showing on PAYG summary when balancing payroll

Functional Issue

PAYG Payment Summaries are not created for a financial year in which an employee has only received a reversal of a deduction (e.g. salary sacrifice or FBT).

Functional Verification

1. For an employee who has salary sacrifice amounts to be reversed after their termination date and in the next financial year period (i.e. a negative deduction only): 2. Load their PAYG Payment Summary for the financial year in which they were terminated and received payroll and had salary sacrifice deductions. 3. Verify the Salary Sacrifice amount is correct (along with the other Payment Summary details). 4. Rehire the employee in the next financial year in order to calculate a Special Pay reversing out a portion of the salary sacrifice paid 5. Load the employee's PAYG Payment Summary for the next financial year (i.e. where only one negative deduction was repaid) 6. Verify the PAYG Payment Summary loads the correct amounts for Salary Sacrifice, Gross and Tax.

Solution Implemented

Amended the Payment Summary process to generate PAYG details based on negative deduction amounts, FBT, Reportable Superannuation and non-zero tax amounts. This is in additional to generating PAYG details based on normal payroll and ETP payments.

AR 323851 - Multi Company Payroll Processing

Functional Issue

The main objective of the Multi Company Payroll Processing enhancement is to improve productivity and usability for payroll users by providing a single interface to process pays across multiple companies that share the same pay cycle.  For example, calculate all fortnightly employee pays due 2/10/2014. In addition to calculating pays, other bulk payroll processes that can be enhanced by processing across multiple companies include: 1. Leave accruals 2. Payroll liabilities 3. Leave liabilities 4. Special pays 5. Bonus pays 6. Correction pays 7. Bank download 8. Payroll posting to financial ledgers The summary and statutory reports associated with these payroll processes will also support multiple company selection.  For example, pay advice, payment summaries, EFT (bank download).

Functional Verification

1. Log on as Payroll Officer 2. From the Processing tab, choose from the Multiple Company processing functions available: 3. Calculate Pays for Multiple Companies 4. Calculate Leave Accruals for Multiple Companies. 5. Once pays are completed, print pay advices for all the companies selected. 6. Run Pay Calculation and Pay Summary across Multiple Companies reports for the companies selected in the pay run.  i.e. From the Reports tab or function links in the Calculate process functions.

Solution Implemented

Phase 1 Delivery: 1. Additional Multiple Company payroll processing functions have been delivered, including:   a. Calculate Payroll for Multiple Companies   b. Calculate Leave Accruals for Multiple Companies. 2. The following new Payroll reports have been provided to support pay calculations for Multiple Companies:   a. Pay Calculation Report across Multiple Companies   b. Pay Summary Report across Multiple Companies. 3. Changes to Pay Advices   a. Additional versions of the standard Pay Advices have been provided to support multiple company pay processing for both Australia and New Zealand.   b. When customising a new pay advice, an additional Multiple Company pay advice version is also required if you wish to run pay advices from the Multiple Company processes.    This is due to the change of primary criteria from Company to Pay Group for this processing.  The shipped pay advices should be used as a template.   c. A default Pay Advice document definition can now be set for the Pay Advice links in your pay process functions.   This means that you can now update or create custom functions for Calculate Pay by Group and Adjust Payroll by Employee, then set your custom pay advice as the default using the new Parameter:   Default Pay Advice Document Definition. 4. Pay Group codes have been extended to support a maximum length of 10 characters. To obtain the full functionality as outlined for this enhancement, the following packages must also be installed: 1. Human Resource & Payroll Core 2. Employee Administration.

AR 329872, 333475, 343905 - Optional Super based on a percentage does not calculate correctly

Functional Issue

Optional Super based on a percentage does not calculate correctly where the employee has a secondary positon. i.e. When calculating superannuation on the Secondary position, the percentage value used is sourced from the Pay Component definition rather than the Employee's Superannuation details. NOTE: The calculation on the Primary Position superannuation correctly uses the percentage value from the Employee's Superannuation details.

Functional Verification

1. For an Australian employee who has a currently active Secondary position 2. Ensure that their employee superannuation details specify an extra contribution pay component that is defined as a percentage contribution type 3. Calculate an ordinary pay that includes base pay on both Primary and Secondary positions 4. Review the superannuation extra contribution pay items 5. Confirm the extra contribution is deducted at the rate specified in the employee superannuation.  i.e. Rather than the pay component rate.

Solution Implemented

Changed the pay calculation to ensure percentage extra superannuation contributions are deducted at the specified employee's contribution rate for all positions.

AR 332381, 337012, 338156, 338327, 338299, 338743, 338735, 339569, 340769, 340954, 341545 - Unable to process leave accrual for employee

Functional Issue

The Accrual process results in a duplicate key error occurs when an accrual calculation is run for an employee on the same date as an existing accrual adjustment. This error may occur during individual or bulk accrual processing.

Functional Verification

1. Calculate an accrual adjustment for an employee 2. Calculate accruals for the employee on the same date 3. Verify the accrual calculation completes without any errors 4. Ensure the employees accrual balances are correct.

Solution Implemented

Amended the process to load accrual summary data to allow the accrual process to be run after an accrual adjustment has been made on the same date. To obtain the full resolution related to the issue as outlined in the listed ARs, the following package must also be installed: 1. HRP Accruals

AR 337263, 337135, 338008, 338004, 337896, 338252, 338819, 342251 - Pay item explanation not showing for non superannuation pay components in Adjust Payroll

Functional Issue

The pay item explanation is not being displayed in the adjust payroll screen (HRPAY710) for non superannuation pay items.

Functional Verification

1. Load an employee's pay via the Adjust Payroll function for an employee with superannuation in their pay. 2. Manually enter an additional Base Pay item and enter text into the Explanation column. 3. Calculate the pay. 4. Confirm the manually entered explanation for the Base Pay is still displayed. 5. Confirm the explanation for the Net Pay displays the bank details. 6. Confirm the explanation for the Superannuation displays the superannuation fund description. 7. Navigate to the Adjust Accruals function for the same employee and pay period date. 8. Calculate the accruals. 9. Confirm the pay item's explanation fields display the accrual details.

Solution Implemented

Amended the adjust payroll form (HRPAY710) to ensure the pay item explanation is displayed correctly when it has been loaded manually, or for bank details and superannuation contributions.

RELEASE June 2014

AR 205325 - Lump Sum A Type does not load the correct code for the termination type processed

AR 206821 - CDEP Payment Summary Includes Payroll Liability Pay Comp 75.0

AR 291303 - New Zealand termination pay over deducts termination leave student loan

AR 297479, 287961 - Cannot select super fund on manual pay item

AR 311695 - Leaving Loading not paid for redundancy terminations

AR 321584, 290934, 297465, 228843 - Termination calculation accruals not paid correctly

AR 325057 - Student Loan not correct on Termination or Correction calculations

AR 326005 - Tax Calculation Issue - SFSS not calculating correctly

AR 328408 - Amendments to the Pay Calculation and Summary reports

AR 329972 - Pay advice leave accruals and pay rate precision

AR 330088 - Amendments to the PAYG Payment Summary Listing Report

AR 332066 - ETP Termination tax calc RTE - Invalid date for preservation age

AR 332961 - Amendments to the ETP Listing Report

AR 333950 - Australian End of Year Legislative Changes 2014 - 2015

AR 334927 - Update Papua New Guinea Tax Scales

AR 205325 - Lump Sum A Type does not load the correct code for the termination type processed

Functional Issue

The PAYG Payment Summary load process does not default the correct Lump Sum A Type code for the termination type processed.

Functional Verification

1. Terminate an employee with a termination type of Redundancy. 2. Calculate a termination pay for the employee ensuring the pay includes a Lump Sum A payment. 3. Load the PAYG Payment Summaries for the Company and Financial Year that includes the employee's termination. 4. Review the Employee's PAYG Payment Summary details using the Adjust PAYG Payment Summary function. 5. Verify the Lump Sum A Type is set to "R".

Solution Implemented

Amended the PAYG Payment Summary load process to set the Lump Sum A Type code to "R" for Genuine Redundancy payment, Early Retirement Scheme payment or Invalidity segment of an ETP. For all other termination types, the Lump Sum A Type code will be set to "T".

AR 206821 - CDEP Payment Summary Includes Payroll Liability Pay Comp 75.0

Functional Issue

The load process for the PAYG Payment Summary includes Payroll Liability amounts in the calculation of CDEP Payments.

Functional Verification

1. Set up an employee with a Base Pay component that has the CDEP_SAL System Configuration code ticked 2. Calculate a pay for the employee 3. Calculate a payroll liability for the employee at a date in the same financial year as the normal pay 4. Load the PAYG Payment Summary for the financial year 5. Verify the CDEP Payment field contains only the base pay amount from the normal pay. The amount calculated in the payroll liability is not included.

Solution Implemented

Amended the PAYG Payment Summary load process to utilise the values from the "Exclude from YTD" Control Variable in the calculation of CDEP Payments.

AR 291303 - New Zealand termination pay over deducts termination leave student loan

Functional Issue

The New Zealand student loan for termination leave is calculated incorrectly by the termination process.

Functional Verification

1. Create a New Zealand employee and assign the tax scale code M SL to their tax details. 2. Ensure the employee entitlements include annual leave accrual paid on termination. 3. Calculate a number of ordinary pay periods in the employee's current accrual anniversary period to ensure sufficient termination earnings. 4. Create a termination activity within the last completed pay period. 5. Calculate the termination pay with load entitlements selected. 6. Review the pay details and calculation audit. 7. Confirm the ordinary pay student loan is calculated and deducted correctly. 8. Confirm the termination leave previous year accrual calculation audit has calculated the student loan deduction correctly and the pay item has been generated. 9. Confirm the termination leave current year 8% earnings calculation audit has calculated the student loan deduction correctly and the pay item has been generated.

Solution Implemented

Amended the New Zealand termination calculation to ensure student loan is deducted correctly for termination leave.

AR 297479, 287961 - Cannot select super fund on manual pay item

Functional Issue

The Adjust Payroll and Correction Pay functions do not allow the selection of the employee's superannuation fund for manually entered employee contributions.

Functional Verification

1. Select an employee who has employee superannuation contributions. 2. Load the Correction Pay or Adjust Payroll for Employee function with the current pay period for the employee. 3. Add a pay item for the employee contribution component of the superannuation fund. 4. Calculate the pay. 5. Review the pay item details. 6. Confirm the pay calculation has completed without error. 7. Confirm the manually entered item has the superannaution fund code displayed in the Superannuation Fund / Deduction Payee column.

Solution Implemented

Amended the Adjust Payroll function (HRPAY710) to ensure the Superannuation Fund is available to manually entered employee contributions.

AR 311695 - Leaving Loading not paid for redundancy terminations

Functional Issue

The leave loading for termination annual leave was not being paid for a genuine redundancy termination.

Functional Verification

1. Select an employee who has annual leave with leave loading in their entitlements. 2. Ensure the leave loading checkbox is selected in the employee's tax details. 3. Terminate the employee with a termination type of genuine redundancy. 4. Calculate the termination pay. 5. Review the calculation audit and pay details. 6. Confirm the annual leave is paid and taxed as a lump sum A component. 7. Confirm the leave loading has been calculated on the paid out annual leave. 8. Confirm the leave loading is paid as a lump sum A component. 9. Confirm the tax on leave loading has been calculated at 32%.

Solution Implemented

Amended the termination pay process to generate annual leave loading correctly for a genuine redundancy termination. This leave loading calculation on termination also applies to invalidity and early retirement scheme.

AR 321584, 290934, 297465, 228843 - Termination calculation accruals not paid correctly

Functional Issue

The termination accruals from the previous employment period were being included in the current termination accruals calculation. Unused accruals from previous jobs within the current employment period were causing the termination earnings to be paid twice. Public holidays occurring after termination within the unused accrual period were paid for both the previous and current job within the employment period.

Functional Verification

1. Rehire an employee who had an annual leave accrual in their previous employment period that was paid out on termination. 2. Ensure the employee's current entitlements do not have termination leave accrual pay components. 3. Terminate the employee from the current job. 4. Calculate the termination pay. 5. Review the calculation audit and pay details. 6. Confirm that leave accruals from the previous employment period are not being included in the current termination pay. 1. Select an existing employee with annual leave to be paid on termination. 2. Create new job details and entitlements which have an additional annual leave that accrues on a different accrual pay component code. 3. Terminate the employee from the current job. 4. Calculate the termination pay. 5. Review the calculation audit and pay details. 6. Confirm that the unused accrual from both annual leave components is paid. 7. Confirm that the percentage of earnings (8%) is calculated and paid once only. 8. Confirm that the total of earnings since the employee's anniversary includes the unused accrual balance from both of the current employment period's annual leave components. 9. Confirm the unused accrual periods from both jobs are used sequentially to locate the public holidays to be paid.

Solution Implemented

Amended the termination pay process to ensure leave from previous job periods are not included in the current calculation. Amended the termination pay process to ensure the termination percentage of earnings is only calculated once when the employee's job history includes multiple annual leave components within the current employment period. Amended the termination process to ensure unused accrual periods from multiple jobs are used correctly for the search of public holidays after termination.

AR 325057 - Student Loan not correct on Termination or Correction calculations

Functional Issue

The New Zealand student loan deducted was incorrect when calculating an additional pay with the same date of a previously calculated ordinary pay. When a Correction or other special pay was calculated on the same date as a previously calculated ordinary pay, the process does not assign the result of the total pay period calculation to the ordinary tax and the student loan payment.  The result is an inflated student loan payment and a deflated normal tax component for the correction pay.

Functional Verification

1. Create a New Zealand employee and assign the tax scale code M SL to their tax details. 2. Calculate an ordinary pay period for the employee within the current tax year. 3. Review the pay details and calculation audit and confirm the ordinary tax and student loan deducted are correct. 4. Load the Process or Adjust Correction Pay function for the employee on the same Pay Period End Date as the ordinary pay. 5. Enter a base pay and taxable item to the pay and calculate. 6. Review the pay details and calculation audit. 7. Confirm the correction pay calculation audit has included the taxable income from the previous ordinary pay. 8. Confirm from the Calculation Audit that the Total ordinary tax and student loan for both pays are correct. 9. Confirm the Net ordinary tax and student loan for the current Correction Pay are correct; and that the corresponding pays items are generated correctly.

Solution Implemented

Amended the New Zealand tax calculation process to calculate Student Loan and Tax amounts correctly for additional pay adjustments.

AR 326005 - Tax Calculation Issue - SFSS not calculating correctly

Functional Issue

The tax calculation for SFSS repayment income is based on taxable income. It should be based on total reportable income which includes reportable fringe benefits (as reported on your payment summary), total net investment loss (which includes net rental losses), reportable super contributions, and any exempt foreign employment income amounts.

Functional Verification

1. Create an employee with the SFSS indicator selected on their tax details. 2. Assign a reportable super contribution deduction to their Employee Superannuation (i.e. the Pay Component Code has the System Configuration Code 'SUP_REPORT' selected). 3. Calculate an ordinary pay with Entitlements loaded. 4. Review the Calculation Audit. 5. Confirm the tax calculation has the correct Total SFSS repayment income, which comprises of the total taxable income plus the reportable super contribution. 6. Confirm the SFSS tax payable is correctly calculated for the repayment income (refer to SFSS scales for current financial year).

Solution Implemented

Amended the tax calculation process to ensure reportable superannuation, exempt foreign income and reportable FBT are included in the SFSS repayment income.

AR 328408 - Amendments to the Pay Calculation and Summary reports

Functional Issue

The Extended Criteria for some fields do not work correctly on the Pay Calculation and Pay Summary reports. These fields include Gross, Take Home, Tax amounts, Pre and Post Tax Allowances and Deductions. When including these amounts in the Extended Criteria to restrict the number of employee pays included in the report, not all items in each employee's pay are included in the report. For example:  Specifying "Take Home Amount <> 0" prevents Tax and Gross amounts from being included in the report.

Functional Verification

1. From the reports tab on the Payroll Officer workplace, open the Pay Calculation report 2. Generate the report using the extended criteria to restrict the employee pays returned.  i.e. by specified values of Gross, Take Home or Tax amounts.  E.g. "Take Home Amount = 0" 3. Verify the report results include the employee pays expected and that all lines of each employee's pay are included in the report. 4. From the reports tab on the Payroll Officer workplace, open the Pay Summary report 5. Generate the report using the extended criteria to restrict the employee pays returned.  i.e. by specified values of Take Home or Tax amounts.  E.g. "Take Home Amount = 0" 6. Verify the report include the employee pays expected and that all amounts of each employee's pay are included in the report.

Solution Implemented

Amended the report extended criteria to be based on table columns instead of report formula fields. NOTE:  Pre and Post Tax Allowances and Deductions are no longer available for selection in the Extended Criteria of the Pay Summary Report.

AR 329972 - Pay advice leave accruals and pay rate precision

Functional Issue

The Leave Balances on the Pay Advice do not group accruals together.

Functional Verification

1. Generate a Pay Advice for an employee who has multiple leave accruals within the same accrual grouping, i.e. two annual leave accruals. 2. Verify the Pay Advice displays both leave accruals combined within one leave accrual group.

Solution Implemented

Amended the pay advice to group leave accruals by accrual group. Additionally, the pay advice has been updated to display pay Rates to 4 decimal places.

AR 330088 - Amendments to the PAYG Payment Summary Listing Report

Functional Issue

The PAYG Payment Summary Listing report requires amending to bring it up to date which will better meet customer requirements.

Functional Verification

1. Run the PAYG Payment Summary Listing report for a range of employees and verify the following changes. 2. Each Lump Sum value is reported in a separate column. 3. Lump Sum A Type is report adjacent to the Lump Sum A amount. 4. Other Income, Exempt Foreign Income, Deductible Amount of the Undeducted Purchase Price (UPP) and Union Name are displayed on the report. 5. Id Number allows values up to 10 characters. 6. Nett Amount does not appear on the report. 7. Verify Pay Group is available as non-mandatory report criteria and filters records in the report as expected. 8. The report displays a count of the number of PAYG documents per company and as a total for the whole report. 9. The end of the report displays the correct selection and sort criteria as entered. 10. Subtotal exist for Company grouping.

Solution Implemented

Amended the PAYG Payment Summary Listing report to ensure it is valid and meets customer requirements. The following updates were made: 1. Report each Lump Sum value in a separate column. 2. Include Lump Sum A Type on the report, adjacent to the Lump Sum A amount. 3. Include new columns for Other Income, Exempt Foreign Income and Deductible Amount of the Undeducted Purchase Price (UPP) and Union Name. 4. Increase the Id Number column to cater for up to 10 characters. 5. Remove the Nett Amount column as it is not a valid requirement for this report. 6. Added "Pay Group" as report selection criteria. 7. Added a document count by Company and for the report total. 8. Included Selection and Sort criteria details to the end of the report. 9. Added subtotals for Company grouping.

AR 332066 - ETP Termination tax calc RTE - Invalid date for preservation age

Functional Issue

A run time error occurs when calculating a Termination pay with an ETP where the employee's date of birth is the 29th of February. This process calculates the employee's age as at the end of the income year to compare with their preservation age to determine the rate of tax applicable.

Functional Verification

1. Set up an employee with a Date of Birth of the 29th February (i.e. on a leap year). 2. Generate Entitlements for the employee that include Leave Accruals. 3. Terminate the employee in a non-Leap year with a termination type of Redundancy. 4. Ensure the employee's accruals are set up correctly to pay out an ETP on redundancy termination. 5. Calculate the Termination Pay. 6. Verify the Termination Pay calculates without error. 7. Ensure the Termination Pay and ETP payment are correct.

Solution Implemented

Amended the tax calculation to correctly cater for key dates that occur on the 29th February.

AR 332961 - Amendments to the ETP Listing Report

Functional Issue

The ETP Listing report requires amending to bring it up to date which will better meet customer requirements.

Functional Verification

1. Run the ETP Listing report for a range of employees and verify the following changes. 2. Verify Pay Group is available as non-mandatory report criteria and filters records in the report as expected. 3. The end of the report displays the correct selection and sort criteria as entered. 4. The report displays a count of the number of ETP documents per company and as a total for the whole report. 5. Id Number allows values up to 10 characters. 6. Verify the extended criteria worked correctly.

Solution Implemented

Amended the PAYG Payment Summary Listing report to ensure it is valid and meets customer requirements. The following updates were made: 1. Added "Pay Group" as report selection criteria. 2. Included Selection and Sort criteria details to the end of the report. 3. Added a document count by Company and for the report total. 4. Increase the Id Number column to cater for up to 10 characters. 5. Added extended criteria to the report.

AR 333950 - Australian End of Year Legislative Changes 2014 - 2015

Functional Issue

The Australian Tax Scales including HELP income thresholds and SFSS repayment thresholds are to be updated for the 2014 - 2015 financial year. Genuine redundancy payments and early retirement scheme thresholds are to be updated from 1 July 2014. ETP withholding rates are to be updated from 1 July 2014. The ETP Cap will increase from 1 July 2014. Withholding rates for unused leave payments on termination of employment are to be updated from 1 July 2014. The Maximum super contribution base amount will increase from 1 July 2014.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Normal Tax Scales (Tax Scales -> $AU - Australia): 4. Confirm that Tax Scales 1, 2, 3, 4a, 4b, 5, 6 are available for the 1 July 2014 5. Confirm that Tax Constants for tax scales 2 and 6 are available for the 1 July 2014. 6. Navigate to the HELP income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP): 7. Confirm that HELP income thresholds are available for the 1 July 2014. 8. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS): 9. Confirm that SFSS repayment income thresholds are available for the 1 July 2014. 10. Navigate to the Genuine Redundancy Tax Free Limit thresholds (Other Tax Scales -> $AU - Australia -> AU_GRTFL): 11. Confirm that the Genuine Redundancy Tax Free Limit thresholds are available for the 1 July 2014. 12. Verify the following ETP calculations in a termination pay that produces the relevant ETP: 13. A Life Benefit ETP for an amount under the ETP cap received under the preservation age withholds tax at a rate of 32% 14. A Life Benefit ETP for an amount under the ETP cap received above the preservation age withholds tax at a rate of 17% 15. A Life Benefit ETP for an amount over the ETP cap withholds tax at a rate of 49% 16. A Death Benefit ETP paid to a non-dependant for an amount under the ETP cap withholds tax at a rate of 32% 17. A Death Benefit ETP paid to a non-dependant for an amount above the ETP cap withholds tax at a rate of 49% 18. A Death Benefit ETP paid to a dependant for an amount under the ETP cap has no tax withheld 19. A Death Benefit ETP paid to a dependant for an amount above the ETP cap withholds tax at a rate of 49% 20. Navigate to the Taxation section of the default control variables: 21. Confirm that the ETP Cap Amount is 185,000 (NOTE:  Override with 180,000 until 1 July 2014). 22. Navigate to the Superannuation section of the default control variables: 23. Confirm that the Max Quarterly Base is 49,430. 24. NOTE: Check if ETP Cap Amount or Max Quarterly Base need to be updated for other customised Control Variable groups. 25. Verify the following unused leave payment calculations in a termination pay: 26. Unused Long Service Leave relating to the period August 78 to August 93 from a normal termination withholds tax at a rate of 32% 27. Unused Long Service Leave relating to the period August 78 to August 93 from a genuine redundancy withholds tax at a rate of 32% 28. Unused Long Service Leave relating to the period post August 93 from a genuine redundancy withholds tax at a rate of 32% 29. Unused Annual Leave from a genuine redundancy withholds tax at a rate of 32% 30. Unused Annual Leave Loading from a genuine redundancy withholds tax at a rate of 32%.

Solution Implemented

Added new Australian Tax Scale co-efficients, HELP income thresholds and SFSS repayment thresholds for the 2014 - 2015 financial year (refer to ATO website). Updated the Genuine redundancy payments and early retirement scheme thresholds (refer to ATO website). Updated the ETP withholding rates (refer to above summary and ATO website). Updated the withholding rates for unused leave payments on termination (from 31.5 % to 32% as noted in above summary and ATO website). Updated the Control Variable for ETP Cap Amount (from 180,000 to 185,000). Updated the Control Variable for the Superannuation Maximum Quarterly Base (to 49,430). NOTE: Ensure that a Package Finalise is executed after applying this update which will load the new tax details into your database(s). Please note, the Package Finalise process may take a long time to run.

AR 334927 - Update Papua New Guinea Tax Scales

Functional Issue

The Papua New Guinea Tax Scales are to be updated effective from 1 July 2012.

Functional Verification

1. Logon with a user that has access to the Payroll Officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the Normal Tax Scales (Tax Scales -> $PG - Papua New Guinea). 4. Confirm that Tax Scales R - Resident, NR - Non Resident and ND - No Notification are available for the 1 July 2012.

Solution Implemented

Added new Papua New Guinea Tax Scale co-efficients effective from 1 July 2012. NOTE: Ensure that a Package Finalise is executed after applying this update which will load the new tax details into your database(s). Please note, the Package Finalise process may take a long time to run.

RELEASE April 2014

AR 282286, 259034, 280990 - Automate ETP Payments for Australian Terminations

AR 302695 - Discrepancy with bank download file

AR 302855 - PAYG limited to 2 ETP payment details

AR 303304 - System is unable to process extra payments for a termination.

AR 306270 - PAYG payment summary - employment termination payment wording is incorrect

AR 314676, 273787, 272649, 272536, 271853, 270960, 270714, 270228, 269131, 266955, 281476, 306672, 294621, 262730, 261156, 257880, 288382, 281427, 280330, 280316, 279653, 279013, 276085, 275550, 274467 - Bank Download Function shows pay items that can't be downloaded

AR 318642 - Database Enquiry functions failing with Oracle Error

AR 323450 - Save as workset from calculate pays tab results in an application error.

AR 324923 - Pays will not calculate for PNG region

AR 328593 - Oncost Pay Component to be Suppressed from New Pay Advice

AR 328595 - System Variable HR_PAYSLIPPOS is not being used on the new pay advice.

AR 328596 - Add IRD Number and Tax Code as standard to the New NZ Pay Advice

AR 328615, 327793 - Kiwisaver ESCT not correct in termination pay

AR 329005 - Superannuation on Termination Pay dropping fund details

AR 329276 - Payslip showing incorrect Leave Balance

AR 282286, 259034, 280990 - Automate ETP Payments for Australian Terminations

Functional Issue

The system is unable to automatically pay Other Leave as an ETP component on termination pay calculation.  E.g. Sick or RDO. The system is unable to process current ATO ETP life and death benefit codes against pay components. i.e. post 1 July 2013.

Functional Verification

1. Confirm that all Pay Component Codes for the Absences pay component type (500) have the 'ETP_AUTO' Australia region configuration code available.    NOTE:  The type of Termination for the employee will determine on what Lump Sum code (O or R) the leave is paid out.           Only Sick and RDO leave are eligible for termination pay out.  Annual and Long Service leave will not be automatically paid as ETP.           Where the termination is a Death benefit, any leave configured for ETP payment is not paid out. 2. Confirm that all Pay Component Codes for the Lump Sum Payments pay component type (600) have the following Australian region ETP configuration codes available:    ETP_DTH_B - Previous Year Death Benefit Non Dependant (Code B)    ETP_DTH_D - Death Benefit Dependant (Code D)    ETP_DTH_N - Death Benefit Non Dependant (Code N)    ETP_DTH_T - Death Benefit Trustee (Code T)    ETP_LFE_O - Life Benefit Other (Code O)    ETP_LFE_P - Previous Year Life Benefit Other (Code P)    ETP_LFE_R - Life Benefit Redundancy, Invalidity, etc (Code R)    ETP_LFE_S - Previous Year Life Benefit Redundancy (Code S).    NOTE:  The following Australian configuration codes for ETP Payments have now been superseded by above equivalents:    ETP - Employment Termination Payment    ETP_DTH_O - Death Benefit Type O (superseded by Death Benefit Non Dependant Code N)    ETP_TRANS - Transitional Payment    Additionally note that, existing pay component codes for Death Benefit Type O will be automatically updated to Non Dependant Code N during the package finalise process. 3. Confirm that all Pay Component Codes for the Taxation pay component type (990) have the following Australian region configuration codes available:    TAX_ETP_B - Employment Termination Payment Code B    TAX_ETP_D - Employment Termination Payment Code D    TAX_ETP_N - Employment Termination Payment Code N    TAX_ETP_O - Employment Termination Payment Code O    TAX_ETP_P - Employment Termination Payment Code P    TAX_ETP_R - Employment Termination Payment Code R    TAX_ETP_S - Employment Termination Payment Code S    TAX_ETP_T - Employment Termination Payment Code T.    NOTE:  The following Australian configuration codes for ETP Tax have now been superseded by above equivalents:    TAX_ETP - Employment Termination Payments    TAX_ETP_TR - Transitional - Employment Termination Payments. 4. Create and update ETP pay component codes in your system, by:    (a) ensuring existing pay component codes for Australian ETP processing have the updated configuration codes selected and the superseded configuration codes unselected.    (b) marking superseded ETP lump sum and taxation pay components as obsolete and no longer in use. E.g. Transitional and basic ETP lump sum payments used prior to 1 July 2013.    (c) ensuring that new taxable pay component codes are created for all the ETP Lump Sum Payments that do not exist in your payroll implementation.    (d) ensuring that new tax free pay component codes are created for all Life Benefit ETP Lump Sum Payments codes (O, P, R, S).    (e) ensuring that a new tax free pay component code is created for the Death Benefit ETP Lump Sum Payment codes D and T. (Dependant and Trustee).    (f) ensuring that new pay component codes are created for all Taxation ETP codes that do not exist in your payroll implementation.    (g) ensuring that sick and/or RDO leave components that you require automatic payment on termination are marked as termination payments (TERMINATE and ETP_AUTO). 5. To confirm pay out of Sick Leave on an employee's Termination:    (a) Create or update an absence pay component for sick leave, selecting the TERMINATE and ETP_AUTO configuration codes.    (b) Ensure there is a taxable lump sum pay component code with the configuration code ETP_LFE_O selected and also a corresponding taxation pay component code with the configuration code TAX_ETP_O.    (c) Terminate an employee who has an accrual in their current entitlements that is reduced by the component in (a).    (d) Calculate the termination pay with the calculation option Leave Accrual Payout selected.    (e) Confirm the sick leave is paid on the taxable lump sum and the tax is deducted with the pay components created in (b).    (f) Confirm the employee's accrual balance has been reduced to zero.

Solution Implemented

The system has been updated to support the current ATO ETP codes for lump sum payments and taxation (as stated above). The system has been updated to allow leave pay components to be included in terminations for automatic lump sum payments. The Termination pay calculation will automatically:   1. pay out and tax other leave (e.g. Sick, Rostered Days Off) as ETP Lump Sum Payment components if the corresponding Absence pay components have the ETP configuration codes selected (TERMINATE and ETP_AUTO); and reduce the employee's corresponding accrual balance to zero;   2. classify leave paid out on Invalidity terminations as Code R (which has tax free components);   3. classify leave paid out on Genuine Redundancy as Code O (which does not have tax free components);   4. calculate the tax free portion for manually entered Genuine Redundancy payments (entered as code R or S ETP lump sums).  E.g. severance pay, pay in lieu of notice, gratuity;   5. default all other automatic termination payments to the ETP Life Benefit code O;   6. apply ETP caps to taxable ETP Lump Sum Payments;   7. proportion tax free components for pre-1983 employment service on all ETP Lump Sum Payments; NOTE:  If the Termination is being processed for an employee due to Death, the termination process will not generate a lump sum payment. The user must enter the ETP death payment manually by selecting the appropriate ATO Lump Sum Payment pay component code, depending on the type of recipient for the payment i.e. Dependant, Non Dependant or Trustee.  Payments made to Dependants, will have a tax free portion applied.

AR 302695 - Discrepancy with bank download file

Functional Issue

Whenever a pay contains a Deduction Payee pay item and no Nett Pay, that pay will not be processed by the Bank Download function when initiated from the Payroll Officer's workplace Processing tab. If the Bank Download is initiated from either the Calculate Pays or Adjust Payroll functions the pay will be process by the Bank Download.

Functional Verification

1. Log in with a user account that has access to the Payroll Officer workplace 2. Configure an employee to have a Deduction Payee pay component with an amount in their entitlement records. 3. Configure that same employee to have their entire pay (apart from the Deduction Payee amount) salary sacrificed into Employee Contribution Superannuation which will result in no nett pay being generated when the employee's pay is calculated. 4. Calculate a pay for the employee. 5. Navigate to the Processing tab and access the Bank Download function in the Payroll Processing listing. 6. Enter the Pay Group and Pay Period End Date from the pay calculated in Step 4 as filters for the Periods to Process. 7. Confirm that the available Periods to Process contains the pay calculated in step 4. 8. Confirm that the Nett Total amount in the Periods to Process grid is the amount specified for the Deduction Payee pay item amount. 9. Perform the Bank Download and review the Bank Download file generated. 10. Confirm that the Bank Download file contains the Deduction Payee pay item generated in the pay calculation in Step 4. 11. Load the pay calculated in the Step 4 in the Adjust Payroll function. 12. Confirm that the pay has been marked as paid.

Solution Implemented

Deduction Payee pay items are now correctly identified in a pay that does not include a Nett Pay or Additional Banking pay items.

AR 302855 - PAYG limited to 2 ETP payment details

Functional Issue

The system currently can only load, store, print and transmit 2 ETP payment details within the PAYG payment summary process.

Functional Verification

1. Process the termination of an Australian employee. 2. Open the Process Termination Pay for Employee function and enter an ETP payment for both code 'O' and 'R'. 3. Calculate the termination pay with load entitlements selected and confirm the ETP payments have been processed correctly. 4. Bank download the termination pay. 5. Open the Adjust Post Termination ETP Correction for Employee function, enter a pay period end date that is within the same financial year as the termination pay. 6. Add an ETP payment for code 'R', calculate and confirm the ETP payment has been processed correctly. 7. Bank download the termination correction. 8. Open the Adjust PAYG Payment Summary function, enter required fields and select Load. 9. Review the payment summary details and confirm they are loaded correctly. 10. Review the ETP payment details grid and confirm all three ETP payments are loaded correctly. 11. Select Print PAYG payment summaries and print the payment summary. 12. Confirm the payment summary is printed correctly with separate page for each ETP payment. 13. Open the Electronic PAYG Summaries function; enter the required fields and Start Processing. 14. Confirm the EMPDUPE file is created in the server folder specified correctly and confirm the file validates successfully within the ATO ECI utility program.

Solution Implemented

Amended the PAYG payment summary processes to allow the processing of multiple ETP payments within the same financial year.

AR 303304 - System is unable to process extra payments for a termination.

Functional Issue

Once an Australian termination pay is finalised extra ETP payments can not be processed correctly.

Functional Verification

1. Open the Payroll Officer workplace, select the processing tab and confirm the function Adjust Post Termination ETP Correction for Employee in listed within the Special Processing menu list. 2. Process termination for an Australian employee. 3. Open the Process Termination pay function, add an ETP termination item code 'O' and calculate the termination pay. 4. Confirm the termination pay has calculated correctly and bank download the pay. 5. Open the Adjust Post Termination ETP Correction for Employee function and add an ETP item code 'O'. 6. Calculate the termination correction pay and review the pay items and calculation audit. 7. Confirm the ETP tax calculation has included the previous ETP payment in the assessment of the applicable ETP cap. 8. Confirm the ETP payment is taxed correctly based on the amount of cap remaining and exceeding the cap. 9. Confirm the pay items are generated correctly per the calculation audit.

Solution Implemented

Amended the system to include a function to enable processing of post termination ETP correction payments. i.e. "Adjust Post Termination ETP Correction for Employee" available in the shipped Special Processing menu of the Payroll Officer workplace. Amended the pay process to ensure post termination ETP correction payments are processed correctly, the previous ETP payments are included in the assessment of the current ETP cap.

AR 306270 - PAYG payment summary - employment termination payment wording is incorrect

Functional Issue

The Notice To Payee wording of the amended PAYG payment summary - employment termination payment, was incorrect.

Functional Verification

1. Load an PAYG payment for an employee whose termination pay includes an ETP payment. 2. Print the payment summary. 3. Confirm the Notice To Payee wording for the employee termination payment is correct. 4. Generate an EMPDUPE file for the employee; ensure the Production Run checkbox is selected. 5. Retrieve the payment summary, select the PAYG  Payment Summary Amended checkbox and save the change. 6. Print the amended payment summary. 7. Confirm the Notice To Payee wording for the employee termination payment is correct.

Solution Implemented

Changed the amended PAYG payment summary - employment termination payment, to display the correct Notice To Payee wording.

AR 314676, 273787, 272649, 272536, 271853, 270960, 270714, 270228, 269131, 266955, 281476, 306672, 294621, 262730, 261156, 257880, 288382, 281427, 280330, 280316, 279653, 279013, 276085, 275550, 274467 - Bank Download Function shows pay items that can't be downloaded

Functional Issue

Pays with negative Nett amounts appear in the Periods to Process grid for the Bulk Bank Download function.

Functional Verification

1. Using the Payroll Officer workplace create a correction pay with a negative Nett pay amount for an employee. 2. Using the same Pay Period End Date from the pay created in Step 1 create a correction pay with a positive Nett amount for another employee. 3. Load the Bulk Bank Download function from the Processing Tab and filter on the Pay Period End Date used for the correction pays created in Steps 1 and 2. 4. Confirm that the employee count is 1. 5. Confirm that the Nett total amount is the Nett pay amount for the pay calculated in Step 2. (i.e. The positive Nett pay amount) 6. Select that Pay Period and perform the bank download. 7. Confirm that no errors appear during the bank download process for the pay calculated in Step 1. (i.e. The negative Nett pay amount) 8. Confirm that the pay calculated in Step 2 has an entry in the Bank Download file. 9. Confirm that the pay calculated in Step 2 has been marked as paid. 10. Refresh the Bank Download function and confirm that the Pay Period used for the pay calculations in Steps 1 and 2 do not appear in the Periods to Process grid.

Solution Implemented

The Bank Download process has been modified to not include pays with negative Nett pay amounts.

AR 318642 - Database Enquiry functions failing with Oracle Error

Functional Issue

Oracle database clients with a large number of employees can experience database exceptions while performing a Payroll Enquiry for a specific company and pay group.

Functional Verification

1. Open the Payroll Enquiry function. 2. Enter a  Start Date and End Date that covers an extended period. 3. Enter a Company Code and Pay Group. 4. Perform the Enquiry. 5. Confirm the enquiry completes without error due to timeout or memory problems. 6. Confirm the enquiry displays payroll data correctly.

Solution Implemented

Changed the system to optimise the Payroll Enquiry process when processing large amounts of payroll data within an Oracle database.

AR 323450 - Save as workset from calculate pays tab results in an application error.

Functional Issue

The Save as Workset process on the Calculate Payroll by Group function results in an error.

Functional Verification

1. From the Payroll Officer workplace, click the Calculate Pays tab to open the Calculate Pays by Group function 2. Enter criteria for Company Code, Pay Group and Pay Period End Date 3. Select the Processing Option to Process Selected Employees that match the Criteria or Workset. 4. Enter criteria to select a set of specific employees 5. From below the Employees grid, select the link to "Save as Workset" 6. Enter Workset details 7. Click Save and close 8. Verify the Workset details saved correctly by clearing the screen and retrieving the Workset results 9. Ensure the Employees displayed in the grid are correct for the Workset selected

Solution Implemented

Amended the Workset Save as process to correctly save Workset details.

AR 324923 - Pays will not calculate for PNG region

Functional Issue

Pays that include superannuation components fail for companies that are not in the Australia or New Zealand regions, i.e Papua New Guinea and West Samoa.

Functional Verification

1. Set up an employee with Job details that specify a PNG region company 2. Add a Superannuation fund to the Employee, including a Superannuation Member Number 3. Calculate a pay for the employee 4. Verify the Superannuation details on the pay and the pay summary data analyser

Solution Implemented

Amended the base superannuation business component to include a member number for populating the pay summary table.

AR 328593 - Oncost Pay Component to be Suppressed from New Pay Advice

Functional Issue

The new pay advices for the Australian and New Zealand regions display Oncost pay components.  (i.e. pay components of Type 2000)

Functional Verification

1. Set up an employee with entitlements that include an On Cost pay component 2. Pay the employee 3. Verify the Oncost appears correctly in the calculated pay 4. Generate a Pay Advice for the employee 5. Verify the Oncost does not appear on the Pay Advice

Solution Implemented

Amended the new pay advices for the Australian and New Zealand regions to always exclude Oncost pay components.

AR 328595 - System Variable HR_PAYSLIPPOS is not being used on the new pay advice.

Functional Issue

The new pay advice does not allow the user to determine whether Employee Position Details are displayed.

Functional Verification

1. Ensure the system variable HR_PAYSLIPPOS is set to "N", i.e. do not display Employee Position details on the pay advice 2. Generate a pay advice for an employee using the new New Zealand pay advice 3. Verify the Employee Position details are not shown on the pay advice

Solution Implemented

Amended the new New Zealand Pay Advice to allow the user to determine whether Employee Position Details are displayed. The following System Variables have been verified to function correctly for both the Australian and New Zealand region pay advices: - HR_PAYSLIP_RATE - HR_PAYSLIP_BANK - HR_PAYSLIP_EMPID - HR_PAYSLIPPOS - HR_PAYSLIPICON

AR 328596 - Add IRD Number and Tax Code as standard to the New NZ Pay Advice

Functional Issue

The Employee IRD Number and Tax Code are not standard fields displayed on the new NZ pay advice

Functional Verification

1. Ensure the System Variables for displaying IRD Number and Tax Code on the Pay Advice is set to "Y" 2. Generate a pay advice for a New Zealand employee based on the new NZ pay advice 3. Verify the employee's IRD Number and Tax Code are displayed on the pay advice

Solution Implemented

Amended the new NZ pay advice to allow IRD Number and Tax code as standard fields. These fields can be controlled to display on the New Zealand pay advice using the System Variables HR_PAYSLIP_IRDNUMBER and HR_PAYSLIP_TAXCODE.

AR 328615, 327793 - Kiwisaver ESCT not correct in termination pay

Functional Issue

New Zealand termination pays that include Kiwisaver employer contributions were not calculating Employer Superannuation Contribution Tax (ESCT) correctly.

Functional Verification

1. Create an employee with New Zealand job details. 2. Assign to the employee entitlements annual leave that is paid on termination and contributes to superannuation ordinary time earnings. 3. Assign to the employee superannuation Kiwisaver fund details. 4. Create a termination activity for the last completed pay period. 5. Calculate a number of ordinary pays leading up to the termination activity. 6. Calculate the termination pay as at the date of the termination activity. 7. Review the pay items generated and calculation audit. 8. Confirm the ESCT is calculated and deducted from the employer contribution correctly for both the ordinary and termination pay item types. Note: Terminating an employee currently occupying secondary position(s) will generate separate ESCT and employer superannuation contribution items per position.

Solution Implemented

Amended the pay calculation (i.e. New Zealand superannuation process) to ensure Kiwisaver ESCT is processed correctly in a termination pay.

AR 329005 - Superannuation on Termination Pay dropping fund details

Functional Issue

Superannuation details on Termination Pay are not recording correctly in the summary tables and therefore not appearing correctly on the termination pay advice.

Functional Verification

1. Calculate a Termination pay for an employee with superannuation and leave accruals 2. Verify the Superannuation Details, including fund code are recorded correctly in the Termination Pay 3. View the Termination pay details from the Payment Summary Data analyser 4. Verify the Superannuation Details are recorded correctly in the Payment Summary Data analyser 5. Generate a Payment Advice for the Termination Pay 6. Verify the Superannuation Details are displayed correctly on the Termination Pay Advice

Solution Implemented

Confirmed that this issue only impacts the pay summary table. While the issue was previously resolved in the development environment, the code change was not released correctly with other related changes. Merged the required code for release.

AR 329276 - Payslip showing incorrect Leave Balance

Functional Issue

The leave balances on the new pay advice are incorrect following the addition of a new accrual initial load, i.e. after an accrual initial load is added, the employee's leave taken balance is set back to zero. In the case of the accrual summary table this is not occurring and as a result affecting the amounts displayed on the pay advice.

Functional Verification

1. Add a new initial load for an employee that has a units taken balance in their employee maintenance leave accruals. 2. Calculate a pay (without leave) and process accruals for the employee. 3. Generate a pay advice for the employee. 4. Confirm the accrual balances from the accrual summary data analyser and pay advice match the employee's accrual balances from employee maintenance (and the employee's leave taken balance is zero).

Solution Implemented

Amended the process that populates the accrual summary table to calculate leave taken for the period after the effective date of the latest accrual initial load.

RELEASE March 2014

AR 283452 - Ordinary Time Override on Super Fund Not Working

AR 295298, 296273, 295879 - New Zealand SLCIR deduction does not stop when the debtor balance reaches zero

AR 325514 - Report printing as Letter size instead of A4 size.

AR 326177 - Some Non Taxable payments are missing on the Pay Summary Report

AR 326200, 326032 - Pay Component details do not show on report if zero amount

AR 326572 - Kiwisaver not deducting for superannuation funds with an ordinary time override

AR 326650 - New Zealand SLCIR changes do not work if Employee debtor details are added

AR 326832, 326847 - When processing a termination pay any amendments are not captured on the new Pay advice

AR 326896 - New Pay Calculation Report does not itemise differing rates for same pay component

AR 283452 - Ordinary Time Override on Super Fund Not Working

Functional Issue

The Superannuation calculation for Australian region payroll users does not use the Ordinary Time Override configuration.

Functional Verification

1. Set up a user defined configuration code for Ordinary Time Override 2. Assign the user defined configuration code to the Base Pay pay component 3. Ensure the Base Pay pay component has the System Config Code SUP_ORDHRS checked on 4. Create two superannuation funds with different Superannuation pay components, assign the user defined configuration code as the Ordinary Time Override to one fund only 5. Update an employee with entitlements that include the Base Pay pay component, another pay component for Additional Hours worked that just has the System Config Code SUP_ORDHRS checked on and superannuation details with both funds specified above 6. Calculate a pay for the employee 7. Verify the Super Pay Component from the Fund that has the override calculates super based only on the Base Pay pay component. The Super Pay Component from the Fund without the override calculates super based on both the Base Pay pay component and the Additional Hours pay component

Solution Implemented

Amended the Australian region Superannuation process to use the Ordinary Time Override configuration where applicable

AR 295298, 296273, 295879 - New Zealand SLCIR deduction does not stop when the debtor balance reaches zero

Functional Issue

The New Zealand SLCIR calculation was not monitoring the employee debtor outstanding balance.

Functional Verification

1. Create an employee with a New Zealand based job. 2. Assign the student loan compulsory extra deduction pay component (SLCIR) to the employee's entitlements. 3. Add the SLCIR pay component to the employee debtors with a positive initial balance. 4. Calculate the ordinary pay periods until the debt outstanding balance is zero. 5. Confirm the SLCIR deduction is automatically stopped when the debts' outstanding balance reaches zero.

Solution Implemented

Changed the New Zealand SLCIR calculation to ensure the employee debtor outstanding balance is monitored.

AR 325514 - Report printing as Letter size instead of A4 size.

Functional Issue

Crystal Reports have their page size set to Letter.

Functional Verification

1. Generate each of payroll reports impacted by this update and view using the Crystal report viewer, i.e. Pay Calculation, Pay Summary and EFT Payments report 2. Open the Print dialog box 3. Verify the layout tab shows the Printer Paper size as A4

Solution Implemented

The Crystal Report (source) page size has been defaulted to A4 in the recently shipped reports, however, customers must also: 1. Check their printer default page setting 2. Check and change the Adobe page setting (if possible. N.b. Readers may not save page setting changes). Reports affected include: Pay Calculation Report Pay Summary Report EFT Payments Report

AR 326177 - Some Non Taxable payments are missing on the Pay Summary Report

Functional Issue

The Pay Summary Report does not include non taxable payment amounts other than those configured as "allowances".

Functional Verification

1. Terminate an employee as a redundancy termination 2. Run the termination pay with a non taxable ETP pay component 3. Generate a Pay Summary Report for the Termination Pay 4. Verify the non taxable ETP amount appears in the Post Tax Allowances column 5. Ensure all of the amounts, sub total and totals on the Pay Summary Report are correct

Solution Implemented

Amended the Pay Summary report to include all non taxable payments as Post Tax Allowances (i.e. Pay Component Types < 800).

AR 326200, 326032 - Pay Component details do not show on report if zero amount

Functional Issue

The Pay Advice and Pay Calculation reports do not show pay component details of valid transactions that have a zero amount. For example, Leave Without Pay (LWOP).

Functional Verification

1. For an employee, generate approved Leave Without Pay during the current pay period 2. Calculate the pay for the employee 3. Ensure the pay has a zero amount based on the leave without pay 4. Generate a pay advice for the calculated pay 5. Verify the Pay Advice shows a transaction in the detail section of the pay advice for the leave without pay

Solution Implemented

Amended the Pay Advice and Pay Calculation reports to show valid transactions that have a zero amount (i.e. all zero transactions excluding allowances and deductions).

AR 326572 - Kiwisaver not deducting for superannuation funds with an ordinary time override

Functional Issue

New Zealand superannuation funds with an ordinary time override specified were not being processed by the pay calculation.

Functional Verification

1. Create a New Zealand Kiwisaver fund and assign a user configuration code to the ordinary time override field.  E.g. 'U_SUPEREMP'. 2. Assign pay components to the fund, including member and company contribution components. 3. Create an New Zealand employee and assign base pay entitlement that has the user configuration code above selected. 4. Also ensure the base pay entitlement does not have the system configuration code 'SUP_ORDHRS' selected. 5. Assign the Kiwisaver fund to the employee's superannuation contribution details. 6. Calculate an ordinary pay period. 7. Review the pay items generated to confirm both the member and company contributions are generated. 8. Review the calculation audit to confirm the superannuation calculation is correct and was based on the user configuration code assigned to the fund.

Solution Implemented

Changed the pay calculation process to ensure New Zealand superannuation funds are processed when they have an ordinary time override.

AR 326650 - New Zealand SLCIR changes do not work if Employee debtor details are added

Functional Issue

The New Zealand SLCIR deduction was not generated when the pay component was added to the employee debtors.

Functional Verification

1. Create an employee with a New Zealand based job. 2. Assign the student loan compulsory extra deduction pay component (SLCIR) to the employee's entitlements. 3. Add the SLCIR pay component to the employee debtors with a positive initial balance to be repaid. 4. Calculate an ordinary pay period. 5. Confirm the SLCIR deduction is generated correctly. NOTE: SLCIR is calculated based on the percentage (41.67% maximum) of the standard student loan deduction. As per the IRD Student loan compulsory extra deduction notice issued for the affected employees.

Solution Implemented

Changed the pay process to ensure New Zealand SLCIR deductions assigned to the employee debtors are deducted.

AR 326832, 326847 - When processing a termination pay any amendments are not captured on the new Pay advice

Functional Issue

The Pay Advice report does not correctly reflect the termination pay results after adjustments have been made.

Functional Verification

1. Calculate a Termination pay for a Terminated employee. 2. Manually add an ETP pay item with an amount and set the pay item type to Termination. 3. Save changes and recalculate the Termination Pay. 4. Confirm that the nett pay amount has changed to reflect the manually added ETP pay item. 5. Generate a Payment Advice report for the Termination pay. 6. Confirm the Take Home Amount on the report is the nett pay amount from the recalculated pay and not the nett pay amount from the initial pay calculation in Step 1. 7. Execute the Payroll Summary Data Analyser. 8. Confirm the nett pay pay item amount is the nett pay amount from the recalculated pay and not the nett pay amount from the initial pay calculation in Step 1.

Solution Implemented

The Pay Calculation process has been modified to allow amendments to a calculated Termination pay to appear in the following: 1. Payment Advice Report 2. Pay Summary Report 3. Pay Calculation Report 4. Payroll Summary Data Analyser

AR 326896 - New Pay Calculation Report does not itemise differing rates for same pay component

Functional Issue

The Pay Calculation Report does not itemise transactions based on multiple positions per employee (i.e. primary and secondary).

Functional Verification

1. Set up an employee with a primary and secondary position 2. Generate entitlements for both positions, ensuring there is at least one pay component that is in both entitlement sets 3. Run a pay from the employee 4. Generate a Pay Calculation report 5. Verify all pay components are reported correctly for each position

Solution Implemented

Amended the Pay Calculation report to itemise pay transactions based on position.

RELEASE January 2014

AR 290584 - New Zealand Payroll Legislative Enhancements for 1 April 2014

AR 305142, 304189, 241478, 264871 - Super Percentage Increase from 9% to 9.25% not working correctly

AR 315739 - Pay Summary Table is populated with unnecessary pay components when running accruals

AR 321143 - Leave accrual calculation producing false warning messages.

AR 321993 - Expected Payment Date of Super not required on New Zealand Pay Advice

AR 323200 - When trying to add additional leave an error occurs

AR 290584 - New Zealand Payroll Legislative Enhancements for 1 April 2014

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2014.

Functional Verification

Earners Levy Changes: 1. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2014 and are for the correct percentage and maximum levy.    The Earners Levy percentage for 1 April 2014 is 1.45% for annual income less than $118,191.00 and the maximum levy is $1713.76. 2. Calculate an ordinary pay after the 1st April 2014 for an employee with tax code M. 3. Review the calculation audit. 4. Confirm the new earners levy rate and threshold were used for the tax calculation. Truncate pay period income for PAYE calculation of NSW, CAE, EDW, ND and secondary income tax codes: 1. Create a new employee and assign their tax details to the NSW tax code. 2. Add to an ordinary pay a base pay item for $999.99. 3. Calculate the pay. 4. Review the tax calculation section of the calculation audit. 5. Confirm the tax was calculated on the pay period amount of $999.00. Student Loan compulsory extra deductions (SLCIR) 1. Create an deduction pay component with SLCIR configuration flag selected and the components' amount is derived from the percentage of the total of config type code 'TAX_SL'. 2. Create an employee with the  'M SL' tax code and the SLCIR pay component for 41.67% is assigned to their entitlements. 3. Calculate an ordinary pay period with entitlements loaded. 4. Review the tax calculation section of the calculation audit. 5. Confirm the SLCIR component amount is 41.67% of the standard student loan deduction.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2014: - The Normal and ACC Earners Levy tax scales have been updated - The tax calculation process was updated to truncate the pay period income correctly for employees on tax code NSW, CAE, EDW, ND and the secondary income codes. - The tax calculation process was updated to process Student Loan compulsory extra deductions (SLCIR) at the percentage of the student loan standard deduction. Per the Student Loan compulsory extra deduction notice.   Note: A guide is attached to the Action Request to provide assistance in the system configuration changes required. Ensure that a Package Finalise is executed after applying this update which will load the new tax data into your database(s).  Verify that this update has successfully uploaded the correct Tax and other scales from the Payroll Officer Administration Console. The Package Finalise process may take a long time to run.

AR 305142, 304189, 241478, 264871 - Super Percentage Increase from 9% to 9.25% not working correctly

Functional Issue

When an increase is made to the superannuation rate, the employee superannuation calculation applies the increase to the whole month instead of the current pay period.

Functional Verification

1. Set up an employee who is paid weekly and earning $1000pw with a super fund that pays Super at 9%. 2. Calculate the first pay period for the month. 3. Verify superannuation calculates correctly as 9% of 1000 = 90. 4. Change the superannuation percentage on the employee's fund from 9% to 9.25%. 5. Calculate the second pay period for the month. 6. Verify superannuation calculates correctly as 9.25% of 1000 = 92.50.

Solution Implemented

Amended the employee superannuation process to check the minimum monthly threshold only when there have been no superannuation contributions made in the current month. Where contributions already exist for the current month, superannuation will be calculated on the current pay period. The employee superannuation calculation now includes manual and imported superannuation transactions.

AR 315739 - Pay Summary Table is populated with unnecessary pay components when running accruals

Functional Issue

When processing accruals the pay summary table is populated with unnecessary additional YTD transactions which will appear in payroll summary drag and analyse results.

Functional Verification

1. Set up a new employee with entitlements that include accruals. 2. Calculate a normal pay. 3. Calculate accruals. 4. Verify using payroll summary drag and analyse that the accrual transactions (document type A) do not include transactions from the normal pay, i.e. pay component 100.

Solution Implemented

Amended the pay process to only populate the pay summary table with accrual transactions when calculating accruals.

AR 321143 - Leave accrual calculation producing false warning messages.

Functional Issue

Incorrect warning messages are returned when calculating accruals if an accrual group is not assigned.

Functional Verification

1. Set up an employee with a calendar based leave accrual. 2. Ensure the leave accrual has an accrual type but not assigned an accrual group. 3. Process accruals for the employee. 4. Verify the accruals process correctly and no warning messages are returned.

Solution Implemented

Amended the Accrual Summary function to remove incorrect warning messages.

AR 321993 - Expected Payment Date of Super not required on New Zealand Pay Advice

Functional Issue

The Zealand Pay Advice does not need to include details for Expected Payment Date of Superannuation.

Functional Verification

1. Set up an employee with a New Zealand based company and New Zealand based superannuation. 2. Pay the employee. 3. From the Reports tab, ensure the Pay Advice is configured to use the New Zealand Pay Advice report PayAdviceNZ.rpt. 4. Generate a Pay Advice for the employee based on the calculated pay. 5. Verify the Expected Payment Date of Superannuation label does not appear in the Superannuation section of the Pay Advice.

Solution Implemented

Amended the New Zealand Pay Advice to no longer show Expected Payment Date of Superannuation.

AR 323200 - When trying to add additional leave an error occurs

Functional Issue

The Leave Accrual Adjustment process results in errors when modifying an employees leave accrual balance.

Functional Verification

1. Set up an employee with entitlements that include leave accruals 2. Add additional leave to an employees leave accrual balances using the Leave Accrual Adjustment function 3. Ensure the adjustment calculation processes without error 4. Verify the employees leave accrual balances are correct

Solution Implemented

Amended the validation of leave accrual data when populating the accrual summary table.

RELEASE October 2013

AR 201479 - Calculate pays status is incorrect when an Accruals pay component type (1200) exists in the pay.

AR 272328 - HELP not calculating correctly

AR 276205, 258105, 262740, 223400 - Split costing for super on secondary positions

AR 289482, 290728 - Payroll Summary Tables Enhancement

AR 290728 - New Standard Reports for Payroll Processing

AR 302641, 305488 - Error received processing Electronic PAYG Summaries (HRTAX125) - EMPDUPE file is not generated.

AR 309273 - Pay Advice processing enhancements

AR 201479 - Calculate pays status is incorrect when an Accruals pay component type (1200) exists in the pay.

Functional Issue

The calculate pays status is being displayed as 'Posted Not Paid' when the pay includes an Accruals pay component type (1200).

Functional Verification

1. Logon to the system with a user that has access to the Payroll Officer Workplace. 2. Create a new employee with entitlements. 3. In the adjust payroll screen, add an Accruals pay component (1200) to the pay transactions and calculate the pay. 4. On the Calculate Pays screen [HRPAY410], enter the Company, Pay Group and Pay Period End Date. 5. In the Processing Options section, select 'Process Selected Employees that match the Criteria or Workset below'. 6. Retrieve the employee created in step 2. 7. Confirm that the Status displayed in the Employees grid is displayed correctly.

Solution Implemented

Changed the calculate pays status to display correctly when the calculated pay includes an Accruals pay component type (1200).

AR 272328 - HELP not calculating correctly

Functional Issue

The tax calculation was not including reportable superannuation in the HELP repayment income.

Functional Verification

1. Create an employee with the HELP indicator selected on their tax details. 2. Assign a deduction to their entitlements that has the System Configuration Code 'SUP_REPORT' selected. 3. Calculate an ordinary pay with Entitlements loaded. 4. Review the Calculation Audit. 5. Confirm the tax calculation has the correct Total HELP repayment income. 6. Confirm the HELP tax payable is correct.

Solution Implemented

Amended the tax calculation process to ensure reportable superannuation, exempt foreign income and reportable FBT are included in the HELP repayment income.

AR 276205, 258105, 262740, 223400 - Split costing for super on secondary positions

Functional Issue

The superannuation calculation does not split expense costings by position. Superannuation should also be disbursed correctly by position.

Functional Verification

1. Create an employee with a primary and secondary position, entitlements and a superannuation fund that pays 9.25% based on current salary. 2. Set up expense costing for superannuation to derive from position details, e.g. Cost Centre. 3. Ensure that the primary and secondary positions have different cost centres. 4. Run a pay for the employee. 5. Verify the superannuation amounts and expense costings have resolved correctly between primary and secondary positions.

Solution Implemented

Enhanced the superannuation calculation to split expense costings by position.

AR 289482, 290728 - Payroll Summary Tables Enhancement

Functional Issue

The TechnologyOne Human Resource and Payroll product has been enhanced to improve performance of reporting and simplify ongoing report development by flattening the table structure of pay and accrual summary data.

Functional Verification

Pay Summary Table 1. Set up an employee with various entitlements including allowances, deductions, accruals and superannuation 2. Approve Leave for the Employee in future pay periods to be picked up by the pay process 3. Run various pay types for the employee over a number of pay periods 4. Using a data analyser (See Solution Implemented for details), query the pay summary table hrpay_payitems_summpmnt 5. Confirm for each pay run the YTD, Previous Amounts, Banking and Superannuation details are correct Accrual Summary Table 6. Using the same employee pay as above, run the accrual and accrual adjustment processes over a number of periods which include the paid approved leave 7. Using a data analyser (See Solution Implemented for details), query the accrual summary table hrpay_payitems_summaccr 8. Confirm for each accrual process run the Period Accrual, Period Taken, Opening, Closing and Previous Amounts, and accrual groups are correct Reporting Groups 9. For each Pay Component used within a pay, including Net Pay, Additional Banking, Tax and Accruals, ensure all have been allocated an appropriate reporting group. This is mandatory for the Pay Advice to generate correctly. See the Solution Implemented section below for details.

Solution Implemented

Enhancements have been made to simplify data storage for pay and accrual summary information and to improve the ongoing development of reports based on this information. This includes new reporting groups to provide additional flexibility when reporting at the pay component level. *IMPORTANT NOTE* Allocating a Reporting Group from Report Group 1 to pay components used by calculated pays MUST be completed to use the new Pay Advice. The two new summary tables are: 1. Pay Summary Table (hrpay_payitems_summpmnt) 2. Accrual Summary Table (hrpay_payitems_summaccr) Data in these tables can be viewed directly using new Data Analysers shipped in the latest HRP Core package or implementing them as custom data analysers from the file HRPaySumm_DataAnalysers.xml. The Data Analysers will be available from the Payroll Officer workplace. New columns have been added to Pay Component Maintenance (hrpcm_paycomp_ref) to allow for additional flexibility in reporting. The new columns are Rpt_Group_1, Rpt_Group_2, Rpt_Group_3, Rpt_Group_4, Rpt_Group_5. The Reporting Group Enhancement is available by installing the latest Payroll Management Package. Reporting Groups are based on Standard Codes and are user definable. Each Report Grouping is based on a Standard Code Type of the same name. Report Group 1 includes a number of standardised codes for use by the Pay Advice. It is not recommended to remove or change any pre-defined codes provided by TechnologyOne. The shipped reporting groups and sequence numbers for the Pay Advice are as follows: - Base Income  10 - Other Income  20 - Deductions  30 - Post Tax Deductions 50 - Post Tax Allowances 70 - Bank Details  200 - Superannuation 300 - Accruals  400 - Tax   500 Additional Pre Tax Codes can be added with sequence numbers between 10 and 50 Additional Post Tax Codes can be added with sequence numbers between 50 and 100

AR 290728 - New Standard Reports for Payroll Processing

Functional Issue

The TechnologyOne Human Resource and Payroll product has been enhanced to improve performance of reporting and simplify ongoing report development by flattening the table structure of pay and accrual summary data. This enhancement includes a newly formatted pay advice and enhancements to the Pay Summary and Pay Calculation Reports.

Functional Verification

Pay Advice 1. Ensure Employee pays have been calculated based on new table structures, See AR 289482: Payroll Summary Tables Enhancement 2. Generate pay advices from either adjust payroll, calculate pays, the payroll processing menu or the reports tab 3. Confirm all the details in the Pay Advice are correct, including Name and Address, Job and Position details where applicable, Summary and Detail pay details, Banking, including additional banking, superannuation, and accruals, YTD Amounts, Pay Advice grouping and Pay Advice customisation via System Variables. The Opening Balance and Period Accrual are shown with 4 decimal places to provide greater clarity of the amounts calculated in the case of rounding discrepancies. Additional Document Types are reported separately on individual pay advices. When emailed, pay advices are sent as one attachment on one email. When the Save Pay Advice option is ticked, pay advices are saved as separate documents against the relevant pay type in employee self service. Enhanced Reports 1. The Pay Summary Report is available from the Reports Tab as well as an option from the Calculate Pays tab 2. The Pay Calculation Report is available from the Reports Tab as well as an option from the Calculate Pays tab

Solution Implemented

Enhancements have been made to simplify data storage for pay and accrual summary information and to improve the ongoing development of reports based on this information. This includes new reporting groups to provide additional flexibility when reporting at the pay component level. *IMPORTANT NOTE* Allocating a Reporting Group from Report Group 1 to pay components used by calculated pays MUST be completed to use the new Pay Advice. Refer AR 289482: Payroll Summary Tables Enhancement New pay advices are provided for Australia and New Zealand regions, called - PayAdviceAU.rpt - PayAdviceNZ.rpt To run the Pay Advice from Pay Master or Adjust Payroll, the following Document Definitions are shipped with the latest CS Common package: - $P1PAYADAU - $P1PAYADNZ To run the Pay Advice as a report, the following Functions are shipped with the latest CS Common package: - $HR.PAY.PAYADAU.RPT - $HR.PAY.PAYADNZ.RPT To obtain the full functionality the following related packages must be installed: 1. HRP Core 2. HRP Payroll Processing The following Report enhancements include: 1. Pay Summary Report The Pay Summary report is based on the new pay summary tables and has been enhanced to improve the summary detail of employee's pay, including breaking down pre and post tax amounts and deductions, which correspond to the new Pay Advice. When running the Pay Summary report, the extended selection criteria includes the same options as the Calculate Pays selection criteria. The existing Pay Summary report has been relabelled "Pay Summary Report (Incl. Historical Data)" and is available from the Reports tab on the Payroll Office Workplace. This report allows reporting pay data prior to implementing this enhancement which is based on the existing table structure. 2. Pay Calculation Report is based on the new pay summary tables and includes a grand total of the reported calculated pays. When running the Pay Calculation report, the extended selection criteria includes the same options as the calculate Pays selection criteria. The existing Pay Calculation report has been relabelled "Pay Calculation Report (Incl. Historical Data)" and is available from the Reports tab on the Payroll Office Workplace. This report allows reporting pay data prior to implementing this enhancement which is based on the existing table structure.

AR 302641, 305488 - Error received processing Electronic PAYG Summaries (HRTAX125) - EMPDUPE file is not generated.

Functional Issue

The Electronic PAYG Summaries process would error and not generate the EMPDUPE file when an employee has ETP payment details only.

Functional Verification

1. Create an employee whose job details are based in the Australia region. 2. Create a termination activity. 3. Calculate a termination pay with a lump sum ETP payment only. 4. Bank download the termination pay. 5. Load the PAYG details for the employee only. 6. Process the Electronic PAYG Summaries for the financial year that includes the employee. 7. Review the generated EMPDUPE file. 8. Confirm the employee has a DEMP detail line only in the EMPDUPE file. 9. Validate the EMPDUPE file with the current ATO Electronic Commerce Interface (ECI).

Solution Implemented

Amended the Electronic PAYG Summaries process to enable transmission of PAYG details that have ETP payment(s) only.

AR 309273 - Pay Advice processing enhancements

Functional Issue

The Process Pay Advice function is generating the pay advice twice when emailing and saving.

Functional Verification

1. Logon as a user with access to the Payroll Officer workplace. 2. Setup employees with job details with a Pay Advice Transmit Method set to Email. 3. From the Calculate Pays function [HRPAY410], select the employees and click on the Pay Advice link. 4. From the Process Payment Advices function [HRPAY750], ensure the Save Pay Advice checkbox is checked. 5. Run the job. 6. Confirm that the saving of Pay Advices does not transmit the report a second time. This can be confirmed by viewing information in the logfile.

Solution Implemented

Enhanced the Pay Advice process to generate the pay advice once when emailing and saving. * Note: This functionality will require the latest Financials Management package.

RELEASE June 2013

AR 205256 - Improved formatting for Lump Sum A Type on PAYG Payment Summary screen

AR 206775, 289794 - Pay Component Summary Report numeric field sizes are insufficient

AR 235211, 280732, 286515 - Taxation incorrectly calculated for new employees starting mid pay period

AR 237892 - PAYG Summaries prints blank line in the middle of the employee's address

AR 274379 - Enhance PAYG Payment Summary

AR 289482 - AR 289482: New Reporting Columns for Pay Transactions

AR 293447 - UK Regionalisation

AR 294308 - Enhance ETP Payment Summary

AR 297554 - Australian End of Year Legislative Changes 2013 - 2014 (HELP and SFSS threshold rates)

AR 297554 - Australian EOY Legislative Changes PAYG ETP Report Formatting

AR 298656 - Employee Banking Reference Number now appears in Bank Download files.

AR 299806 - ETP Listing Report

AR 205256 - Improved formatting for Lump Sum A Type on PAYG Payment Summary screen

Functional Issue

The Lump Sum A Type field on the Adjust PAYG Payment Summary screen is not in the correct tabbing order and allows lowercase codes to be entered

Functional Verification

1. Open an Employee record from the Adjust PAYG Summaries screen. 2. Enter a valid code as a lower case letter into the Lump Sum A Type field. 3. Verify the valid value entered is forced to display as an upper case letter. 4. Verify the tab order on the screen is correct, particularly for the Lump Sum fields.

Solution Implemented

Corrected formatting issues around the Lump Sum values on the Adjust PAYG Payment Summary screen to ensure tab order is correct and codes are entered in uppercase

AR 206775, 289794 - Pay Component Summary Report numeric field sizes are insufficient

Functional Issue

The field size for Total Amounts on the Pay Component Summary report are not correct for very large numbers

Functional Verification

1. Calculate a pay for an employee where payments and deductions total an amount of up to 10 numerics plus two decimals 2. From the Reports tab, open the Pay Component Summary report found under the Payroll Transaction Reports menu 3. Run the report using criteria to include the pay calculated above 4. Verify the calculate pay is displayed in teh report, and the full amounts are reported

Solution Implemented

Increased the field size of all amount fields on the Pay Component Summary report to suit values of up to 10 numerics plus two decimals

AR 235211, 280732, 286515 - Taxation incorrectly calculated for new employees starting mid pay period

Functional Issue

The system was calculating tax based on worked ratio when employee started mid pay period.

Functional Verification

1. Create a new employee with a hire date in the middle of a pay period. 2. Calculate the pay for the first pay period after commencement. 3. Review the calculation audit. 4. Confirm the tax is calculated on a whole period basis.

Solution Implemented

Amended the tax calculation process to calculate based on a whole period when an employee starts mid pay period.

AR 237892 - PAYG Summaries prints blank line in the middle of the employee's address

Functional Issue

The PAYG Payment Summary does not suppress Employee Address Line 2 when it is blank

Functional Verification

1. Load PAYG Payment Summaries. 2. From the Adjust PAYG Summaries screen, open an employee record and confirm the Employee Address contains details for Address line 1, City, State and Post Code, but not Address Line 2. 3. Print the PAYG Payment Summary for the selected employee. 4. Ensure there is not a blank line between Address Line 1 and the City, State, PostCode details.

Solution Implemented

The PAYG Pay Summary has been updated to correctly format employee name and address details

AR 274379 - Enhance PAYG Payment Summary

Functional Issue

The PAYG Payment Summary requires a new field for the Deductible Amount of the Undeducted Purchase Price of an Annuity, on the Adjust PAYG screen, PAYG report document and EMPDUPE file. Format changes are required to the PAYG report document to meet ATO requirements and it should print correctly on one page. Included is the ability to exclude an employee’s PAYG record from the EMPDUPE file.

Functional Verification

1. Load PAYG Payment Summaries 2. Open the Adjust PAYG Payment Summary screen for an employee 3. Verify the new field “Deductible amount of the undeducted purchase price of an annuity” appears on the Adjust PAYG screen (and can edit and save) 4. Verify a new check box exists called "Exclude from EMPDUPE file" 5. From the Print PAYG Summaries, process documents for a number of employees to the window (displayed using Adobe Reader) 6. Verify the new field “Deductible amount of the undeducted purchase price of an annuity” appears on the PAYG Payment Summary report document 7. Verify the field "Total Allowances" appears in the Allowances section when allowances appear on the report 8. Ensure all documents display correctly on one page 9. Print the documents to the printer from the window view (Adobe reader) 10. Ensure all documents printed from Adobe reader print on one page 11. Print the documents to printer directly from TechOne 12. Ensure all documents printed directly from TechOne print on one page 13. Generate the EMPDUPE file 14. Verify the value for “Deductible amount of the undeducted purchase price of an annuity” appears in the EMPDUPE file (character positions 346-353) 15. From the Adjust PAYG screen, set an employee record to Exclude from EMPDUPE file and generate the EMPDUPE file 16. Verify the employee record does not appear in the EMPDUPE file

Solution Implemented

Enhanced the Adjust PAYG screen, PAYG report document (to Version 5.2) and EMPDUPE file (to Version 11.0) to include the field "Deductible Amount of the Undeducted Purchase Price of an Annuity", include new formatting changes and ensuring the PAYG report document displays on one page for print preview and print functions.

AR 289482 - AR 289482: New Reporting Columns for Pay Transactions

Functional Issue

The TechnologyOne Human Resource and Payroll product has been enhanced to provide some additional columns to assist in reporting requirements

Functional Verification

1. From the Payroll Officer workplace, set up an employee and calculate a pay 2. Run the Pay Transactions Data Analyser and verify the following columns exist and the data is correct: Pay Period Start Date, Period End Position Code, Period End Job Effective Date, Period End Tax Effective Date

Solution Implemented

New columns have been added to the pay master table (HRPAY_MASTER_CTL). The new columns are: - Pay Period Start Date - Period End Position Code - Period End Job Effective Date - Period End Tax Effective Date These columns can be used for reporting for Crystal and XLOne Reports. The Pay Transactions data analyser has been updated to include these new columns.

AR 293447 - UK Regionalisation

Functional Issue

Clients in the United Kingdom region have no facility to store values for the following: 1. Company Number for a Company. 2. Employee National Insurance Number. 3. Effective Position Occupation Code.

Functional Verification

1. Add a new Company and enter $GB into the Region field. 2. Tab out of the Region field and confirm the Company Number field is visible. 3. Enter a Company Number and save the change. 4. Retrieve the Company and confirm the entered Company Number is retrieved correctly. 5. Maintain an Employee with an effective United Kingdom job. 6. Maintain the employee's Tax details. 7. Confirm that the National Insurance Number field is visible. 8. Enter a National Insurance Number and save the change. 9. Retrieve the employee's Tax details and confirm the entered National Insurance Number is retrieved correctly. 10. Maintain an Effective Position for a United Kingdom company. 11. Confirm that the Occupation Code field is visible. 12. Confirm that the Occupation Code field is a list of standard codes of the OCCUPATION_CODE standard code type. 13. Select a Occupation Code and save the change. 14. Retrieve the Effective Position and confirm the entered Occupation Code is retrieved correctly.

Solution Implemented

Added a new United Kingdom region. Added a new Company Number field to the Company Maintenance function for United Kingdom companies. Added a new National Insurance Number field to the Employee Tax function for United Kingdom employees. Added a new Position Occupation Code field to the Effective Position maintenance function for United Kingdom positions. Added a new Occupation Code (OCCUPATION_CODE) standard code type for storing Effective Position Occupation Codes. Ensure that a Package Finalise is executed after applying this update which will load these new United Kingdom region fields into your database(s). Please note, the Package Finalise process may take a long time to run.

AR 294308 - Enhance ETP Payment Summary

Functional Issue

The Employment Termination Payment (ETP) form does not allow for multiple ETP details to be entered with the new Life Benefit ETP Codes for an employee's End of Year processing. The new ETP details should correctly generate the ETP report document and EMPDUPE file with the new codes. The ETP document should print correctly on one page.

Functional Verification

1. From the Adjust PAYG screen, confirm new fields are available in the Employment Termination Section for up to two ETP transactions to be entered 2. Load End of Year details for an existing employee with a termination pay that includes an ETP pay component 3. Verify the ETP details are loaded in the first column for ETP details and are correct, and the ETP code appears in the new ETP code field 4. Where the ETP is not a death benefit type, the ETP code defaults to 'R' 5. Ensure the only value that can be entered and saved are: R, O, S, P, D, B, N, T 6. Verify details for a second ETP can be entered and saved in the second column for ETP details 7. Print the PAYG document, and ensure a separate ETP report document is printed for each ETP code 8. The ETP report document displays on screen and prints correctly on one page 9. Run the EMPDUPE file and ensure a separate record is generated for each ETP 10 Verify ETP code appears in the ETP record (Character Position 247)

Solution Implemented

Enhanced the ETP functionality to allow multiple ETP details to be entered for End of Year processing including on the ETP reporting document (Version 5.2) and EMPDUPE file (Version 11.0). The ETP report document displays on one page for print preview and print functions.

AR 297554 - Australian End of Year Legislative Changes 2013 - 2014 (HELP and SFSS threshold rates)

Functional Issue

The Australian HELP income thresholds and SFSS repayment thresholds are to be updated for the 2013 - 2014 financial year.

Functional Verification

1. Logon with a user that has access to the payroll officer workplace. 2. Navigate to the Manage Payroll Tab. 3. Navigate to the HELP income thresholds (Other Tax Scales -> $AU - Australia -> AU_HELP - HELP) 4. Confirm that HELP income thresholds are available for the 1-july-2013. 5. Navigate to the SFSS repayment thresholds (Other Tax Scales -> $AU - Australia -> AU_SFSS - SFSS) 6. Confirm that SFSS repayment income thresholds are available for the 1-july-2013.

Solution Implemented

Added new Australian HELP income thresholds and SFSS repayment thresholds for the 2013 - 2014 financial year. Ensure that a Package Finalise is executed after applying this update which will load these new HELP and SFSS thresholds into your database(s). Please note, the Package Finalise process may take a long time to run.

AR 297554 - Australian EOY Legislative Changes PAYG ETP Report Formatting

Functional Issue

The PAYG and ETP Report documents have been updated by the ATO as at 1 July 2013

Functional Verification

1. Print a PAYG / ETP report for an existing employee with both PAYG and ETP data 2. On the PAYG document, in the section "Notice to payee" the bullet point "refer to tax pack" has been removed 3. On the ETP document, in the section  "Notice to payee" the bullet point "refer to tax pack" has been removed 4. On the ETP document, "Tax Free Component" wording and box has been moved to align beside "Taxable Component" wording and box 5. On the ETP document, wording and boxes have been removed for "Is this a transitional termination payment" 6. On the ETP document, wording and boxes have been removed for "Is the payment part of a payment made in an earlier income year for the same termination" 7. On the ETP document, wording and boxes have been removed for "Death benefit" 8. On the ETP document, wording and boxes have been removed for "Type of death benefit"

Solution Implemented

The formatting of the PAYG and ETP documents have been updated based on advice provided by the ATO

AR 298656 - Employee Banking Reference Number now appears in Bank Download files.

Functional Issue

A requirement exists to allow the Employee Banking Reference Number to appear in the Bank Download files.

Functional Verification

1. Log in with user that has access to the Payroll Officer workplace. 2. Maintain an employee and add a value in the Bank Reference Number field for an employee's banking record. 3. Navigate to the Adjust Payroll tab and generate a pay. 4. Confirm that the Bank Reference Number entered in step 1 appears in the Reference Number field in the pay items grid. 5. Generate a Bank Download file for the pay generated in Step 2 above. 6. Confirm that the Bank Reference Number value appears in the Bank Download file.

Solution Implemented

The Employee Banking Reference Number will now appear in the Pay Items grid in the Adjust Payroll function and in the subsequent bank download file. NOTE: The Banking Reference Number entered in the Employee's Banking details section: 1. Will be truncated to 30 characters whenever viewed in the Adjust Payroll pay items grid. 2. May be truncated to 18 characters or less when viewed in the generated Bank Download files depending on the Bank Download format used.

AR 299806 - ETP Listing Report

Functional Issue

New report required for reviewing and verifying details of Employment Termination Payment (ETP's)

Functional Verification

1. From the Payroll Officer workplace of TechnologyOne HR and Payroll, click on the Reports tab 2. Verify a new report link exists under the Tax Reports heading for ETP Listing Report 3. Click the link for the ETP Listing Report to open the ETP Listing Report criteria screen 4. Enter criteria which will allow the report to be refined by Financial Year End Date and a range of Employee Id Numbers 5. Run the Report 6. Verify the ETP Listing report generates without error and correctly displays ETP details for employees defined by the selection criteria

Solution Implemented

Developed a new report called the ETP Listing Report for reviewing and verifying details of Employment Termination Payment (ETP's)

RELEASE February 2013

AR 177615 - Pre-paid leave not paying part period leave in particular circumstances

AR 244480 - New Zealand Termination Tax calculation incorrect for unpaid accrual

AR 265975 - Timesheets already paid are being paid again when a timesheet pay item is deleted

AR 279120 - Pay calculation fails when leave taken is from a prior position code due to leave loading

AR 290584 - New Zealand Payroll Legislative Enhancements for 1 April 2013

AR 177615 - Pre-paid leave not paying part period leave in particular circumstances

Functional Issue

When pre-paying whole periods the system was not processing pre-paid timesheet lines for a partial period correctly.

Functional Verification

1. Ensure the Control Variable 'Pre-paid Whole Period' is set to Yes. 2. Create approved pre-paid leave for an employee that spans both a full pay period and a partial pay period. 3. Calculate the ordinary pay for the Prepaid Period Date. 4. Review the pay details and confirm the full pre-paid period has been included. 5. Load the following pay period and calculate the pay. 6. Confirm the following pay period has paid the partial leave correctly.

Solution Implemented

Changed the system to ensure pre-paid timesheet lines are paid correctly when they include a partial pay period.

AR 244480 - New Zealand Termination Tax calculation incorrect for unpaid accrual

Functional Issue

The New Zealand termination process was calculating tax for unpaid accrual from previous years on a pay period basis.

Functional Verification

1. Create an New Zealand employee that includes annual leave accrual. 2. Create a Termination Activity for a date after the first accrual period. 3. Calculate a termination Pay for the employee. 4. Review the Calculation Audit Annual Leave Termination Calculations section. 5. Confirm the Leave Termination Tax Calculation is based on the Normal Pay Weekly Amount.

Solution Implemented

Changed the New Zealand termination process to calculate leave accrual tax based on the normal weekly pay.

AR 265975 - Timesheets already paid are being paid again when a timesheet pay item is deleted

Functional Issue

Pay items generated from timesheet lines were not locked from editing or deletion.

Functional Verification

1. Create an approved timesheet entry. 2. Calculate the pay period for the timesheet. 3. Confirm the timesheet pay item cannot be edited. 4. Delete the timesheet pay item. 5. Confirm the timesheet pay item deletion displays a message box and does not delete the pay item.

Solution Implemented

Amended the system to ensure timesheet generated pay items cannot be edited or deleted. Important Note: When a timesheet generated pay item is incorrect the user can either: (a) delete the whole pay, amend the incorrect timesheet line(s) and recalculate the pay or (b) create a reversal pay item and an adjustment item with the correct values.

AR 279120 - Pay calculation fails when leave taken is from a prior position code due to leave loading

Functional Issue

The pay process errors when processing approved leave from a prior position due to leave loading.

Functional Verification

1. Create an employee and enter a mid-pay period Job Details change. 2. Select the Leave Loading check box in the Employee Tax section. 3. Create one day of annual leave in leave maintenance for a day before the job change. 4. Calculate the pay. 5. Review the pay items and calculation audit. 6. Confirm the leave loading has been processed correctly.

Solution Implemented

Changed the pay process so that an error does not occur when processing approved leave from a prior position due to leave loading.

AR 290584 - New Zealand Payroll Legislative Enhancements for 1 April 2013

Functional Issue

The New Zealand Payroll functionality requires modifications to meet the requirements for the Inland Revenue Payroll Specification Document effective from 1 April 2013.

Functional Verification

1. Verify the Tax Scales for 1 April 2013 exist, they are correct and they do not include the removed scales 'ML' and 'ML SL'. 2. Verify the Low Income Tax Credit scales (NZ_MLR) exist for 1 April 2013 and the values have been cleared. 3. Verify the Earners Levy scales (NZ_EL) exist for 1 April 2013 and are for the correct percentage and maximum levy.    The Earners Levy percentage for 1 April 2013 is 1.70% for annual income less than $116,089.00 and the maximum levy is $1973.51. 4. Verify the Student Loan scales (NZ_SL) exist for 1 April 2013 and are for the correct percentage and threshold.    The Student Loan percentage for 1 April 2013 is 12.00% and the annual income threshold is $19,084.00. 5. Verify the Child Tax Credit scales (NZ_CTC) exist for 1 April 2013 and the values have been cleared. 6. Verify the Withholding Tax scales (NZ_WT) exist for 1 April 2013 and they include the new scales Non-resident contractors who are a company (WT24) and Public office holders (fees) (WT25).    The Non-resident contractors who are a company percentages for 1 April 2013 are 15% Normal Rate and 20% if no Tax Code is declared.    The Public office holders (fees) percentages for 1 April 2013 are 33% Normal Rate and 48% if no Tax Code is declared. 7. Verify new Tax Details with an Effective Date 1 April 2013 have been created for current employees on Tax Code 'ML'.    The new Tax Details are created with Tax Code 'M' and all other details are copied correctly from the previous details. 8. Verify new Tax Details with an Effective Date 1 April 2013 have been created for current employees on Tax Code 'ML SL'.    The new Tax Details are created with Tax Code 'M SL' and all other details are copied correctly from the previous details. 9. Verify new Tax Details with an Effective Date 1 April 2013 have been created for current employees who have Claim Child Tax Credit selected.    The new Tax Details have Claim Child Tax Credit not selected and all other details are copied correctly from the previous details.

Solution Implemented

The following changes have been made to support the IRD Tax changes effective the 1 April 2013: - The Normal and ACC Earners Levy tax scales have been updated - The Normal scales 'ML' and 'ML SL' have been removed and employee tax details updated accordingly. - The Child Tax Credit has been removed and employee tax details updated accordingly. - The Student Loan rate has been updated. - The Withholding tax scales were updated with two new scales. Ensure that a Package Finalise is executed after applying this update which will load the new tax data into your database(s).  Verify that this update has successfully uploaded the correct Tax and other scales from the Payroll Officer Administration Console. The Package Finalise process may take a long time to run.

RELEASE November 2012

AR 177922, 217778, 266783 - Tax "incorrect" in the period after pre-paid leave (not pre-paying whole weeks)

AR 282103 - Accrual start date to be used instead of date hired in leave liability

AR 283387 - Bank Download screen showing incorrect Nett Figures

AR 177922, 217778, 266783 - Tax "incorrect" in the period after pre-paid leave (not pre-paying whole weeks)

Functional Issue

The pay process was not proportioning tax for prepaid leave when calculating for part of a pay period.

Functional Verification

1. Create an employee whose entitlements include annual leave. 2. Set the control variable Prepaid Whole Period (HR_PREPAY_ALL_LEAVE) to 'No'. 3. Create an approved prepaid leave item for two and a half weeks. 4. Calculate the pay period that is set in the leave maintenance prepaid period date. 5. Review the calculation audit and confirm the tax calculation number of pay periods is correct for all prepaid leave pay periods. 6. Calculate the pay period the employee returns from leave. 7. Review the calculation audit and confirm the tax calculation number of pay periods is correct per the base pay paid for the remainder of the week.

Solution Implemented

The pay process was amended to ensure the tax calculation of a part pay period for prepaid leave is proportioned correctly. Note: All allowances and deductions are prepaid with leave, including Percentage and Based on Units Worked entitlements

AR 282103 - Accrual start date to be used instead of date hired in leave liability

Functional Issue

Leave Liability does not use the Accrual Start Date when calculating probability for an Accrual Rule.

Functional Verification

1. Create a new Accrual Rule and enter Probability factors. 2. Add the Accrual to an Employees' Entitlement. 3. In the Initial Load for the Employee Accrual enter an Accrual Start Date (prior to the Date Hired) and Accrual Pro-rata. 4. Open the Adjust Leave Liability function for the employee and calculate liability for a Period End Date prior to the eligibility period being reached. 5. Confirm the Leave Liability Probability is calculated correctly.

Solution Implemented

Changed Leave Liability Calculation process to use the Accrual Start Date instead of the Date Hired.

AR 283387 - Bank Download screen showing incorrect Nett Figures

Functional Issue

Pay Item amounts are doubling up on the Bank Download "Period to Process" grid (HRPAY415) where the employee has multiple banking records in Employee Maintenance (HRHMN410). The result inflates the Nett Total amount displayed, however does not affect the bank download file.

Functional Verification

1. Set up an employee with additional banking to pay a set amount each pay (HRHMN410) 2. Run a pay for the employee (HRPAY710) 3. Confirm the bank download "Periods to Process" shows the pay to be bank downloaded and the Nett total is equal to the sum total of Nett Pay and Additional Banking (HRPAY415)

Solution Implemented

The bank download "Period to Process" grid enquiry has been changed to ensure pay item amounts do not double up where an employee has multiple banking records in Employee Maintenance.