Defect Fixes V12.21

CY-2546

Billing

Closing a Non-Timesheet Based Invoice or Credit Note is not being recorded in the Audit database. As such users are unable to tell when an open Invoice/Credit Note was closed.

This issue has been resolved. Now when closing a Non-Timesheet Based Invoice or Credit Note, this action is recorded in the Audit database.

TR-4276

Recruitment Manager

Where a job is created for a Client with a Monthly Timesheet Frequency, the Cycle Start Date populated on the job is incorrect as it’s been calculated based on a fortnightly cycle.

This issue has been fixed. Where the Frequency is ‘Monthly’, on creation of a Job, the system will insert a Cycle Start Date based on the Client Cycle Start Date ‘Day’ value and the Month and Year of the Job Order. This process will also run where a Job Template with a Frequency of ‘Monthly’ is applied, where the ‘Day’ value is defaulted to what is in the Job Template. Please be aware when using ‘Monthly’ frequency, the ‘Cycle Start Date’ day value needs to be based on your monthly timesheet cycle, for example the 1st of the month or the 15 are the usual values. Note: Tickets have been raised to update this strategy where Copying a Job and also to any related API actions. These will be completed in a future release.

CY-2450

Recruitment Manager

When a job that doesn’t have any Last Updated details (ie job hasn’t been edited) is first submitted to timesheet, an oops error occurs due to an audit entry not being able to be saved. It will appear as if the job has not been submitted to timesheet, however the action has been performed and the timesheets have been created. If Submit to Timesheet is clicked again, the system will reload the page, showing the job has been submitted however the system will not re-create the timesheets.

This item has been resolved. Now where submitting to timesheet, if the job has not been edited, no error is displayed and the timesheets generate as expected. The page is refreshed and the ‘Unto Submit to Timesheet’ action displays at the header.

CY-2410

Payroll 🇳🇿

Payday Reporting errors if it includes a Payee with a combined Firstname and Surname of > 50 characters. This issue also results in the FT Standard Report > Payroll > NZ > Payday Reconciliation (NZ) report not returning any data if the Payment Date criteria includes the date of the batch included in the payday submission.

This issue has been fixed. Now where Payday Reporting is run, there is no error if a Payee with Firstname Surname value of > 50 is submitted. The FT Standard Report > Payroll > NZ > Payday Reconciliation (NZ) report is returning data as expected.

NE-430

Payroll 🇬🇧

UK Tax parameters have been loaded twice for the same tax year.