Defect Fixes V12.32, V12.32P1, V12.32P2, V12.32P3

The following defects have been fixed in this release:

Item No.	Release	Module	Description	Resolution

Item No.	Release	Module	Description	Resolution
TR-4546	12.32	Interpreter	When viewing an interpreted timesheet, in some situations the amount displayed is not the database value which is causing confusion.	This issue has been resolved and the interpreted timesheet is displaying the correct database value.
TR-4857	12.32	Time & Attendance	Where the ‘Default Wild Card’ search option is not selected in Recruitment Manager > Maintenance > General Settings users can still do partial searches by manually adding the % wildcard character. However, the manual wildcard does not work when the 'Default Wild Card Search' option is not selected in Search Timesheet > Available, Incomplete, Submitted, Historical or Expired tabs.	This issue has been resolved. Now where a user manually adds the % symbol to invoke a wildcard search in Time & Attendance this will prompt a wildcard search even where the 'Default Wild Card Search' option is not selected.
NE-898	12.32	Payroll UK	When forms are received from HMRC, a matching process occurs where a HMRC Works Number has been supplied. Where a Payee has been terminated, and then rejoins, the same name and NI Number is used however the system is not auto matching the current Payee record.	This problem has been fixed. Now where a Payee is terminated and later re-joins, the system automatically matches to the correct active Payee.
CY-3102	12.32	Payroll UK	The amounts displayed in the results grid in a pay batch were incorrect, where a payee had multiple timesheets with different end dates. The Taxable Wage in the results grid was double the actual amount. In the Review stage, all amounts, ie Statutory Deduction, Wage Costs were also doubled.	This issue has been resolved. Now where a payee has multiple timesheets with different end dates in the same pay batch, the amounts displayed in the stages of the process are correct and not duplicated.
CY-3108	12.32	Payroll UK	A payee’s pay group was changed and they were then included in a pay batch for the previous pay group, however there were no items within the current pay period. The payee was not included in the Gross to Net By Pay Batch report when it was run while the batch was open. For example, the payee was included in a pay batch where: the pay period end date fell within the current open validity period the batch pay group fell within their previous (closed) validity there were no entries within the current pay period, e.g. only a prior period timesheet was being paid When the batch was subsequently closed, the payee was then included in the report.	Now where a payee’s pay group is changed and they are included in a pay batch where the period end date falls within the current open validity period and the batch pay group falls within their previous closed validity, where a prior timesheet is being paid, the payee is included in the Gross to Net By Pay Batch Report where the report is run in an open batch.
CY-3117	12.32	Payroll UK	A payee’s ‘Payslip Delivery Method’ was set to ‘Print' or 'Email’, and a pay batch was run that included items for a prior pay period. When the payslip was delivered: Multiple payslips appeared with only 1 marked as delivered. Then the other payslips were marked as delivered and multiple payslips still displayed. The Net Wage for each payslip was for a separate pay period, not the total amount for the pay batch. In the Candidate Record/Portal, the Payslip List only displayed the amount that has been marked as delivered. Then when all payslips were marked as delivered, the list displayed a single entry with the batch total. When viewing either payslip, the total amount for the pay batch was displayed.	This issue has been fixed. Now where a payee’s ‘Payslip Delivery Method’ is set to ‘Print’ or ‘Email’ and a pay batch is run that includes items for multiple pay periods, where the payslip is delivered only one payslip is generated with all earnings as per the pay batch combined on one consolidated payslip.
MO-6287	12.32	Payroll UK	A user created a future payee validity, and then processed a pay batch with this payee and the system displayed an oops error.	Now where a future payee validity exists for a payee and a pay batch is processed with that payee included, the pay batch process will refer to the relevant payee validity up to the end of the processing pay period end date and no error will display.
CY-2261	12.32	Payroll (all countries)	It was not possible to add a new pay group and the following error message was displayed if the period end date that was selected fell on the end date of a financial/tax year: Cannot generate pay periods because the End Date entered is after a valid tax period. Check the settings in Tax Period maintenance.	A new pay group can now be added without error if the period end date falls on the end date of a financial/tax year.
TR-4407 TR-4426 TR-4427	12.32	Payroll (all countries)	In some circumstances, the system was not validating that the start date of a validity period on a Payee record aligned with the start of a pay cycle of the pay group that was selected for that validity period. For example, if multiple validity periods were added to a Payee record prior to the payee having been paid, it was possible to change the start date of the second validity period on the payee record to a date that did not match the start date of the pay group that applied for that particular validity period. Because of this, a payee’s timesheets failed to appear in a pay batch for any pay group and therefore could not be paid.	When a Payee record is saved, the system now validates that start dates of validity periods, other than the first validity period, align with the start date of a pay cycle for the pay group that is selected for each period respectively. That ensures that timesheets get correctly allocated to a pay group and can be paid as expected if a payee’s pay group changes during the course of their employment.
TR-4535	12.32	Payroll (all countries)	If you clicked the Save button on the Payee Entry screen and then attempted to close the screen, the following erroneous and confusing confirmation message was displayed if you had added a new validity period to the Payee record without changing any other settings: Payee has changed. Do you wish to continue to lose your changes?	When you attempt to close the Payee Entry screen after having saved any changes you have made, you are no longer prompted with the erroneous confirmation message.
CY-2655	12.32	Billing	Where the interpreted timesheet details of a timesheet included multiple lines where all of the details except the pay code type were identical, when the timesheet was billed and an invoice was generated, some invoice line items were incorrect because they were erroneously being treated as duplicates. Because of this, while the invoice total was correct, the invoice items did not sum to the invoice total.	This problem has been resolved. Invoice items are no longer incorrect when the described situation applies.
TR-4685	12.32	Billing	Where multi-currency is enabled and a currency has been applied to a Debtor and the document format has ‘Display Currency Symbols' selected for amount fields, on occasion the wrong currency symbol is displayed on the invoice. For some currency’s the wrong symbol is displayed on the invoice. Instead of the symbol for the Debtor Currency, it’s displaying the symbol for the Debtor Country.	This item has been resolved. Now where multi-currency has been applied to a Debtor and the document format has ‘Display Currency Symbols' selected for amount fields, the correct currency symbols display on the invoice.
CY-3204	12.32 P1	Interpreter	An adjustment timesheet failed to be interpreted when the previous version of the timesheet was edited in interpreter (a manual item was added). An error message ‘Error interpreting timesheet.: The given key was not present in the dictionary.' displayed. Then when we did subsequent adjustments to that timesheet, the timesheet failed to interpret with an error ‘Error interpreting timesheet.: TimesheetResultMissing_PossiblyTimesheetToAdjustFailedToProcess.’	This issue has been fixed. Now where a timesheet is interpreted, and a manual item is added and a subsequent adjustment timesheet is then generated in Time & Attendance and Approved, the adjustment is interpreted as expected and no error is triggered. Any subsequent adjustments will also interpret as expected.
CY-3090	12.32 P1	Interpreter	We were unable to use the bulk status update in Interpreter Review, for the same job order and week ending date (i.e. an original and one or more adjustment timesheets or adjustment timesheet 1 and adjustment timesheet 2 etc) even if the current status of the selected timesheet is the same. We tried to change from ‘Not Reviewed’ to ‘Reviewed - Pay Only’ or ‘Reviewed - Pay and Bill’. However a user tried to change the status from ‘Not Reviewed’ to ‘Reviewed – Bill Only’, in which case the system allowed which is as expected. The same problem happened when we tried to bulk revert the status of timesheets (e.g. from Reviewed – Pay & Bill to Not Reviewed) except that only the status of the latest timesheet changed. We were forced to change the status one-by-one, starting from the (latest) adjustment timesheet.	This defect has been resolved. Now when changing the status in bulk and all timesheets for the same job and same week ending date (for example original and subsequent adjustments), from ‘Not Reviewed’ to ‘Reviewed - Pay Only’ or ‘Reviewed - Pay and Bill’, the status is bulk updated as expected and the timesheets are released to Pay or Pay and Bill as per the status applied.
CY-3011	12.32 P1	Recruitment Manager	The system was not allowing attachments that should be accepted where the file type is capitalised ie; .PNG; .JPG	The front office attachments process will now accept acceptable file types where the extension has been capitalised.
CY-3235	12.32 P2	Rates & Rules	When trying to save a Pay Agreement, the screen hung and the save did not occur.	This issue has been fixed. Now when saving a Pay Agreement, the screen does not hang and the agreement is saved.
CY-3168	12.32 P2	Pay	The amount that displayed on the Payment Method report was incorrect for Contractor Payee’s linked to a Supplier that is VAT Registered and uses Proforma Remittances.	This problem has been fixed. Where a Payment Method Report is generated for a Contractor Payee linked to a Supplier that is VAT Registered and uses Proforma Remittances, the amounts displayed are correct to what was paid.
CY-3164	12.32 P2	Pay	There were payees who did not show timesheet details in the Pay Batch Items Detail screen. The summary screen showed a value, but when you drilled into the person, the rows were blank.	This issue has been fixed. Now timesheet details display in the Pay Batch Items Detail screen for all applicable payees.
CY-3163	12.32 P2	Pay	In the Payment Method Report where a pay batch was run with multiple pay periods, the Payees were duplicated, rather than showing once with the total amount paid.	This has been resolved. Now where a pay batch is run for multiple pay periods, in the Payment Method Report the payees display in a single line with the total amount paid.
CY-3162	12.32 P2	Pay	A payee had a deduction that did not calculate in a pay batch.	Now where a deduction is applicable to a payee in a pay batch the calculation is made as expected and deducted from their earnings.
CY-3161	12.32 P2	Pay	A Contractor Payee registered for VAT was paid a Reimbursement including VAT, at the VAT stage of the pay batch, VAT was recalculated on the VAT inclusive Reimbursement amount. The VAT amount was then updated to the new amount.	This problem has been fixed. Now where a Contractor Payee registered for VAT is paid a Reimbursement including VAT, at the VAT stage of the pay batch, the VAT is not re-calculated.
CY-3160	12.32 P2	Pay	When terminating a Payee in a pay batch, an Oops error displayed.	This defect has been fixed. Now when terminating a Payee via a pay batch, the Payee is successfully terminated and no error displays.
CY-3159	12.32 P2	Pay	When moving back a stage in the pay batch, an Oops error displayed.	This issue has been resolved. Now when navigating back a stage in the pay batch, the user is successfully taken back to the previous stage and no error displays.
AV-1548	12.32P2	Job Order	A job was set to ‘Monitoring Not Required’ AWR. When a user applied job rates via the Connect screen, the system did not suppress the parity rate rows and related validations.	This defect has been fixed. Now where ‘Monitoring Not Required’ is set for an AWR Job Order, the parity rate row is not displayed and AWR validations are not triggered.
NE-1489	12.32 P3	Job Order	When using the PUT/PATCH Update Single Temporary Joborder and Single Contract Job Order API it was removing the data relating to AWR: AWR Monitoring Not Required Flag AWR Comparator Job Title AWR Enhanced Holiday Override AWR Clock Count	This issue has been resolved that where a job order is replaced, the system will determine if these fields remain by referring to the default Payees excluded from AWR. If the job order payee type is excluded, the data is removed, else it is retained for PUT. For PATCH, it will no longer remove the data out of these fields when patching other fields.
NE-1488	12.32 P3	Job Order	When submitting to timesheet via Vincere that uses APIs to apply updates and if a payee is not monitored for AWR, it was outputting an error message to say parity rates are mandatory. However, as a payee is not monitored for AWR, this validation should not have been output.	This is has been resolved to only show this message where a job order is monitored for AWR and the parity rate is missing.
CY-3424	12.32 P3	Payee	When using the POST Create Single Payee API, the API was erroring requesting a tax code where one was not provided. It should have referred to the starter declaration entry to determine the tax code.	This validation has been updated and the tax code will be created automatically based on the starter declaration submitted for a PAYE payee.
NE-1469	12.32 P3	Pay Batch	Where the first payee in a pay batch had an enhanced holiday override accrual percentage from the Job Order, it was applying the override accrual percentage to all payees within the pay batch.	This has been resolved so that it will apply the percentage relating to the individual payee accrual percentage rate.