Release Notes

Payroll Calculate

Release:

Version 05.14.06.00.06, August 13, 2014 - addendum release

Feature:

Payroll Calculate &endash; Oregon Income Tax

Issue #:

261889

Change:

The Oregon Income Tax withholding tables and payroll calculate have been updated to correct the phase-out amount for employees that claim Single with 3 or more exemptions and to eliminate personal exemptions credits for taxpayers with federal adjusted income above certain limits.

Reason:

Previously, the calculation was inaccurate for employees that claim Single with wages greater than $100,000 or Married with wages greater than $200,000 and Single with 3 or more allowances and wages greater than $125,000

Menu:

HR\PA\UT\PA\TA\PT

HR\PA\CP\CA

 

Release:

Version 05.14.06.00.04, July 16, 2014 - addendum release

Feature:

Payroll Calculate &endash; Other

Change:

The Idaho state tax table has been updated.

Reason:

New rates are effective July 1, 2014

Menu:

HR\PA\UT\PA\TA\PT

 

Release:

Version 05.14.06.00.03, July 12, 2014 - standard release

Feature:

Leave Sale

Issue #:

244925, 247195

Change:

The entry of leave sale transactions through time off has been changed to populate the earning period and retirement hours on the resulting pay record with the earning period and hours of the time off transaction.

Leave Sale payroll processing has been changed to process retirement hours when the pay code is non-rate type, but has a retirement status code that allows hours.  Work hours for unemployment and Worker’s compensation are not calculated on non-rate type pay codes.  

Reason:

Previously the earning period was incorrect and retirement hours were not processed.

Menu:

Pac:  HR\PR\IT, HR\PA\CP\CA

Web:  WH\EP\TB\TI\TR

 

Release:

Version 05.14.02.00.03, March 8, 2014 - standard release

Feature:

Payroll Calculate Payroll Gross Value Message

Issue #:

238150

Change:

The message has been changed to detect changes to payroll gross values that occur in the 2nd pass only.

Reason:

Previously, the message was generated when payroll gross values were changed in the 1st and 2nd pass.

Menu:

Human Resources \ Payroll \ Current Payroll \ Calculate

 

Release:

Version 05.14.02.00.03, March 8, 2014 - standard release

Feature:

Payroll Calculate Washington Error # 40

Issue #:

253897

Change:

Error #40 now occurs when there are multiple pay records with the same pay code on the employee profile, but the deduction or benefit code does not exist on all of the pay codes.

Reason:

Previously, the error was not generated if the deduction or benefit code existed on one of the pay codes.

Menu:

Human Resources \ Payroll \ Current Payroll \ Calculate

 

Release:

Version 05.14.02.00.03, March 8, 2014 - standard release

Feature:

Payroll Calculate Washington Error # 52

Issue #:

244079

Change:

Error #52 now occurs when there is no Member Profile in effect for any of the earning periods on a contract.

Reason:

Previously, the error was only being generated if there was no Member Profile in effect for the entire contract.

Menu:

Human Resources \ Payroll \ Current Payroll \ Calculate

 

Release:

Version 05.14.02.00.03, March 8, 2014 - standard release

Feature:

Payroll Calculate Washington Error # 59

Issue #:

245460

Change:

Error #59 now occurs when both the Contract and Pay Record are deleted from the employee's profile after payroll transactions are selected.

Reason:

Previously, the error did not occur when both were deleted.

Menu:

Human Resources \ Payroll \ Current Payroll \ Calculate

 

Release:

Version 05.14.02.00.03, March 8, 2014 - standard release

Feature:

Payroll Calculate Efficiency

Issue #:

E3871

Change:

The payroll calculate process has been enhanced to identify Washington and other exceptions in one calculate.  Processing will stop if a blue screen error occurs and unemployment-related errors will only be generated for employees who are subject to unemployment.

 

The capability to batch additional payroll reports has also been added.

Reason:

This new feature prioritized and funded through the WSIPC Enhancement process.

Menu:

Human Resources \ Payroll \ Current Payroll \ Calculate

Implementation Note:

Total processing time of a single payroll calculate run may increase by 25% due to the additional processing, however fewer runs of the calculate will be needed to resolve exceptions.

 

Release:

Version 04.12.02.00.12, May 10, 2012 - addendum release

Feature:

Payroll Calculate

Ticket:

244501

Change:

Quick Voided LWOP transactions processed with a transaction pay code are excluded from contract rebalancing.  

Reason:

Previously Quick Voided LWOP transactions processed with a transaction pay code were included in contract rebalancing.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.12.02.00.09, April 11, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

PR 1615460, FP 244143, 241285

Change:

Distribution of WC charges based on WC hours configuration now uses the WC rate and hours instead of just hours to determine charged WC deduction and benefit amounts.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

Previously a defect in the calculation caused the total charged deduction and benefit amounts to not equal the total calculated amounts when the total wc hours equaled zero, but the individual pay code wc hours were not zero.  The defect caused the Check Register to not match the AP invoice WC amounts.

 

Release:

Version 04.12.02.00.07, March 21, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

E3748, 210442

Change:

Proration of WC hours across pay codes will no longer include the total reversal of hours from a pay code.  If the hours on a pay code now net to zero, the WC hours will only reverse for that pay code and not be included in the proration of hours across pay codes.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

Previously, if all the hours were removed for a pay code, the large number of negative hours was included in the proration of hours across pay codes and caused large negative WC deductions and benefits.

 

Release:

Version 04.12.02.00.07, March 21, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

236842

Change:

Adding retirement deductions and benefits to just the payroll selection(s) and not the pay record on the profile will now generate a payroll exception error.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

Previously, if retirement ded\bens were added to only the payroll selection, no error would be generated.  The contribution amounts were included in the transactions reported to DRS but were not added to the retirement deduction and benefit amount for the employee.

 

Release:

Version 04.12.02.00.07, March 21, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

237934

Change:

Plan 3 employee contributions are no longer calculated for payrolls after the employee has become ineligible.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

This was previously corrected for contract pay and is now corrected for non-contract pay also.

 

Release:

Version 04.12.02.00.07, March 21, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

232729, 232742

Change:

Error #61, ”r;Contract to Date amount does not equal pay history for the pay code” exception message, will no longer be generated when caused by a retro pay code being deleted and re-added.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

Previously if a retro pay code for a contract was deleted and re-added, creating a new pay record id for the retro pay code, the retro code pay history amount was excluded from the calculated CTD amount during the WESPaC part of the payroll calculate.  

 

Release:

Version 04.12.02.00.05, March 7, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

233293

Change:

New Warning generated for Worksheets that were imported into a different payroll selection after being imported into the selection being calculated.

In order to process retirement earnings to the correct earning period, worksheet detail is assigned a payroll transaction id when imported into a payroll transaction.  If the same worksheet is subsequently imported into a different run, a calc on the original run will not find the worksheet detail, causing the earnings to be reported to the current earning period rather than the earning period on the worksheet detail.  

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

If the new warning (#74) is included in the WESPaC exceptions, the worksheets indicated in the warning need to be reimported into the current payroll selection in order for the retirement to be reported to the correct earning period.

 

Release:

Version 04.12.02.00.04, March 3, 2012

Feature:

Payroll Calculation

Issue #:

231682

Change:

Retro Pay Codes on Contracts no longer require an employee have a Retirement Profile.

Previously when attempting to pay retro pay on a contract to an employee who had no retirement profile, a false error was generated ”r;Retro Pay Code for a Contract subject to Retirement is Missing Retirement Deduction and\or Benefit Code.”

Reason:

Defect correction

Menu:

HR\PA\CP\CA

 

Release:

Version 04.12.02.00.04, March 3, 2012

Feature:

Payroll Calculation

Issue #:

237353

Change:

New Warning generated for Worksheets that will not be paid because pay code has reached the FTD maximum. Worksheet history is not created for worksheets not paid due to reaching the FTD maximum.

Previously when payroll worksheets exceeded the FTD maximum, the employee’s pay amount was reduced, but worksheet history was created for all worksheets.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

Worksheet history will be created for worksheet detail for a pay record until the FTD max is met.  If a worksheet detail amount is only partially paid because the FTD max is met, worksheet history is not created for that worksheet detail or any more detail for that pay record.  Any partial earnings from the worksheet that is partially paid are reported to the current earning period.

 

Release:

Version 04.11.10.00.18, February 8, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

225188\225183

Change:

Employee correction from Plan 2 to 3 has been corrected.

Reason:

Previously when an employee was incorrectly enrolled in Plan 2 and later changed to Plan 3, none of the Plan 2 retirement history was reversed and re-reported to Plan 3.

Menu:

HR\PA\CP\CA

Implementation Note:

Plan 2 retirement history will be reversed and re-reported to Plan 3 when the Plan 3 member profile does not contain a choice date and the Plan 2 profile has the same end date as the start date.  Plan 3 member profiles with a choice date are considered plan transfers, so Plan 2 history is not reversed.

 

Release:

Version 04.11.10.00.18, February 8, 2012 - addendum release

Feature:

Payroll Calculation

Issue #:

None

Change:

Work hours calculation is rebalanced like WC Work hours.

Reason:

Previously Work hours were calculated with Retirement hours, but this was not entirely correct because Retirement hours are rounded to 1 decimal place and Work hours are not.  Now the total Work hours for the contract though the period end date are compared to the Work hours history and the difference added to the current payroll.

Menu:

HR\PA\CP\CA

Implementation Note:

Work hours calculated on the first payroll after the release will rebalance for the whole current contract period.

 

Release:

Version 04.11.10.00.04, November 5, 2011

Feature:

Payroll Calculate (Negative .01 Reported to DRS)

Issue #:

234336

Change:

The Payroll Calculate process was modified so Error 52 no longer occurs for +- .01 retirement transactions that are generated for earning periods after the employee’s eligibility end date.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.11.10.00.04, November 5, 2011

Feature:

Payroll Calculate (Retirement Hours on Subsequent Calc)

Issue #:

240458

Change:

The Payroll Calculate process was modified to properly process retirement hours in subsequent calculates when the hours are prorated across multiple payroll transactions for a pay code where the factor nets zero. When the hours are prorated across multiple payroll transactions for a pay code which has a factor that nets zero, a factor of 1 is used to prorate the hours correctly, this factor of 1 will no longer be retained and will not be added to the pay code with the highest number of hours on subsequent payroll calculates.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.11.10.00.04, November 5, 2011

Feature:

WESPaC Payroll Calculate (Plan 2 to Plan 3)

Issue #:

225183

Change:

The Payroll Calculate program was modified to properly rebalance retirement when an employee’s member profile is corrected from Plan 2 to Plan 3.  Previously, appropriate rebalancing did not occur when there was no choice code for selecting or defaulting into Plan 3.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.11.06.00.16, October 18, 2011

Feature:

Payroll Calculate

Issue #:

240001

Change:

Earnings do not distribute to the correct retirement earning periods on payroll worksheets which have a single pay code associated with multiple transaction pay codes where the transaction pay codes have multiple earning periods and the single pay code only has one payroll transaction.  

 

The total retirement compensation is correct, however it is not distributed to the correct earning periods and an earning period may have negative compensation.

 

Retirement adjustments will be necessary for districts affected by this defect. A statewide query is being run with this release and WSIPC will notify districts affected of the retirement adjustments that are required.

Reason:

Defect correction.

Menu:

HR\PA\ CP\CA

 

Release:

Version 04.11.06.00.05, August 13, 2011

Feature:

WESPaC Payroll Calculate (Warning 8)

Issue #:

230867

Change:

The Payroll Calculate process was modified to generate Warning 8 when an employee is subject to retirement, but none of the employee’s pay records have retirement deduction\benefit codes attached to them.  Previously, when an employee had at least one pay record included in the payroll that had retirement deduction\benefit codes attached, Warning 8 was generated for pay records that didn’t have retirement deduction\benefit codes attached to them. It didn’t matter if they were contract or pay items. If none of the employee’s pay records had retirement deduction\benefit codes attached, the warning was not generated.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.12, July 9, 2011

Feature:

WESPaC Payroll Calculate (Work Hours &endash; Quarterly Wage Detail)

Issue #:

231771

Change:

The Payroll Calculate program was modified to properly calculate Work Hours when there is no retirement member profile.  Previously, Work Hours were zero (not calculated) when there was no retirement member profile.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.12, July 9, 2011

Feature:

WESPaC Payroll Calculate (Worksheet Transactions &endash; Optional Transaction Paycodes)

Issue #:

238024

Change:

The Payroll Calculate program was modified to properly calculate compensation when Optional Transaction Pay Codes are used in Worksheets.  Previously, if a single pay code was associated with multiple transaction pay codes and the corresponding transactions spanned different earning periods, negative compensation values could occur.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.12, July 9, 2011

Feature:

WESPaC Payroll Calculate (WC Hours)

Issue #:

228320

Change:

The Payroll Calculate program was modified to properly calculate WC Hours when there are zero WC Work hours and leave is also being processed.  Previously, WC Hours was always resolved to zero when there were zero WC Work Hours, even when leave was being processed which should have resulted in negative WC Hours.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.09, June 4, 2011

Feature:

WESPaC Payroll Calculate (Rounding Retirement Pay Amounts)

Issue #:

234336

Change:

The Payroll Calculate program was modified to properly round retirement pay amounts.  Previously, an employee’s worksheet pay total amount could be different from the amount actually paid because of differences in how the pay rate times the factor\hours were summarized and rounded on the worksheet as compared to the import into the payroll selection. The total amount reported to retirement matched the amount paid, but rounding differences in calculating retirement may have caused a penny to be reported in the current earning period even though there were no earnings for the current earning period. The penny in the current earning period could occur when an employee had multiple worksheet entries with different earning periods. The penny (negative or positive) reported to retirement in the current earning period was because of rounding by earning period.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.09, June 4, 2011

Feature:

WESPaC Payroll Calculate (Plan 3 contributions after ineligibility)

Issue #:

229625

Change:

The Payroll Calculate program was modified to properly end Plan 3 contributions after becoming ineligible.  Previously, when an employee was on a contract and their Plan 3 eligibility ended and all of the earnings for the contract were for Plan 3 eligible earning periods and the employee was still receiving pay for that contract after becoming ineligible, Plan 3 contributions continued to be deducted for the employee until the contract was paid off. These contributions were rejected by DRS.

 

EXAMPLE:

Employee Jane Doe worked from September through March on Contract A. Her eligibility for retirement ended at the end of March. The contract was being paid through the end of August. The calculate took Plan 3 deductions from April through August, even though her eligibility ended in March.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.09, June 4, 2011

Feature:

WESPaC Payroll Calculate (Retirement &endash; Transfer from TRS Plan 0 to Plan 1)

Issue #:

230661

Change:

The Payroll Calculate program was modified to properly rebalance retirement when an employee transfers from TRS Plan 0 to Plan 1.

 

EXAMPLE:

A previously retired TRS 1 employee returned to work and was on TRS Plan 0 at the start of the contract in July and August.  Then the employee became an active TRS 1 member in September. The same contract was active during the Plan 0 and Plan 1 membership. The Payroll Calculate process incorrectly reported the days in both plans.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.09, June 4, 2011

Feature:

WESPaC Payroll Calculate (Rebalancing when Work Start date is changed)

Issue #:

231693

Change:

The Payroll Calculate program was modified to properly rebalance retirement when a work start date is changed to a later earning period.  Previously, if retirement history already existed and the contract work start date was changed to a later earning period, appropriate rebalancing did not occur.

 

EXAMPLE:

Employee contracts (HR\PR\CF) had a work start date of 8\27\2010 and the contracts were paid in September 2010. After the September payroll, the work start dates were changed to 9\1\2010 in Employee Management and exported\imported.

An October payroll calculate was done and the Retirement Activity Report (HR\PA\RE\PA\RE\RA) created. The retirement amounts for August were listed in the History columns of the Retirement Activity Report and were not being backed out properly in the Current columns.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.09, June 4, 2011

Feature:

WESPaC Payroll Calculate (Rebalance from single earning period to many)

Issue #:

227985

Change:

The Payroll Calculate program was modified to properly rebalance retirement when all retirement was reported to a single earning period, but is being re-distributed over multiple earning periods. Previously, if significant changes were made to contract work start and work end dates mid-contract, the payroll calculation program did not rebalance retirement earnings previously reported to a single earning period to many earning periods. This occurred when the Contract Work Start and Work End dates were revised to dates in the past.  Rather than distributing the earnings to the past earning periods, the earnings continued to be moved to the current earning period.  Earnings could be distributed to months past their last work end date.  

 

EXAMPLE:

If for several months contract payments had been accumulating\reported to single earning period, e.g. June\the current earning period (contract work start 6\1\xx &endash; 6\1\xx), then the contract work start or end dates were changed to multiple earning periods, e.g. 9\1\xx &endash; 06\20\xx, the program did not redistribute the accumulated earnings.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.12.02.00, May 7, 2011

Feature:

WESPaC Payroll Calculate (Data Manipulation)

Issue #:

230646

Change:

WSIPC released an update to the WESPaC Payroll Calculate in the November 6, 2010 SR which addressed worksheet issues such as invalid earning period dates, invalid work dates, negative earnings and\or multiple earning periods.  Subsequently, WSIPC executed a data manipulation within the May 7, 2011 SR that found and corrected any retirement contributions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.

Reason:

Defect correction

Menu:

HR\PA\CP\CA

Implementation Note:

  1. The first retirement transmittal created after the May 7, 2011 release includes the processed adjustments created by the data manipulation.  Clients wishing additional time to review the processed adjustments have been advised to create their transmittal file before the May 7, 2011 release.  There is no need for it to be transmitted to DRS; it just needs to have been created before the release.

  2. After the data manipulation, the Unreported Payrolls list (HR\PA\RE\PA\RE\DT) appears to include the payroll that was last transmitted, even though that transmittal file has already been created.  This is for the processed adjustments.  No action is required; the adjustments will be included in the next transmittal.

  3. Retirement adjustments were not created for compensation amounts between -$10.00 and $10.00.  DRS approved not moving these small amounts of compensation to the correct earning periods.

  • Districts should be aware that because DRS has approved not creating adjustments for amounts between +\- $10.00, an employee can end up over or under-reported for that amount.

  • For example:  Employee was paid $212.37 on worksheets in the 6\30\2010 paycheck.  $9.89 was earned in 03\2010 and $202.48 was earned in 04\2010.  The entire amount of $212.37 was reported to the 05\2010 earning period.  The data manip will not create the $9.89 adjustment to add those earnings to 03\2010; it will subtract $212.37 from 05\2010 and add $202.48 to 04\2010.  These adjustments will be unprocessed, because the EE and ER amounts do not net zero.

 

Release:

Version 04.10.12.01.03, March 12, 2011

Feature:

WESPaC Payroll Calculate (Query Only)

Issue #:

230646

Change:

WSIPC released an update to the WESPaC Payroll Calculate in the November 6, 2010 SR which addressed worksheet issues such as invalid earning period dates, invalid work dates, negative earnings and\or multiple earning periods. WSIPC ran a query that finds any retirement contributions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.  

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Note:

WSIPC ran a query that finds any retirement contributions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.  A data manipulation that will actually fix the retirement contribution issues identified by this query is planned for a future release.

 

Release:

Version 04.10.12.00.02, January 18, 2011 NSR

Feature:

WESPaC Payroll Calculate (Error 55)

Issue #:

233850

Change:

The payroll calculate program was modified to generate Error 55, ’r;Retirement Deduction\Benefit control record not attached to Pay Record’, when the appropriate deduction\benefit code is not attached to the pay code for a retirement adjustment.  Previously, this did not trigger Error 55, and the payroll process was allowed to continue, rather than terminate. The associated employee and employer contributions were not included in the paycheck.

Reason:

Defect correction.

Menu:

 HR\PA\CP\CA

Implementation Note:

Employer and Employee Contributions on retirement adjustments affected by this defect were not included in the paycheck.  WSIPC will contact data centers serving districts affected by this issue to convey the next steps required after the release.

 

Release:

Version 04.10.06.02.03, November 6, 2010

Feature:

WESPaC Payroll Calculate (Check Register Out-of-Balance)

Issue #:

225315

Change:

The Payroll Calculate program was modified to eliminate the occurrence of an Out-of- Balance error during the Check Register process when Workers’ Compensation deductions\benefits net to zero on a worksheet. Previously, if the district was distributing their WC by hours and the total hours (factor) for worksheet detail for the person netted to zero, but there were hours, the Payroll Calculate assigned a ded\ben amount of zero, but Skyward’s process then assigned an invalid amount for the net-ded-ben.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.06.02.03, November 6, 2010

Feature:

WESPaC Payroll Calculate (Worksheets- Negative earnings and\or multiple earning periods)

Issue #:

226451, 227799

Change:

The Payroll Calculate program was modified to properly process retirement transactions when payroll worksheets contain multiple earning periods. Previously, in some cases, when an employee had payroll worksheets that contained multiple earning periods, all the earnings were accumulated to a single earning period.  Employer and Employee contribution amounts are calculated based on the earning period on the retirement transaction, so if this earning period had a different rate than the correct earning period, the Employee and Employer amounts may be incorrect.

 

This modification applies to Payroll Calculates run after the November 6, 2010 SR.  WSIPC will create a data manipulation to be run in a future release that will find and correct any retirement contributions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

This modification applies to Payrolls run after the November 6, 2010 SR.  WSIPC will create a data manipulation to be run in a future release that will find and correct any retirement contributions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.

 

Release:

Version 04.10.06.02.03, November 6, 2010

Feature:

WESPaC Payroll Calculate (Worksheets - Invalid Earning Period or Work Date)

Issue #:

227575

Change:

The Payroll Calculate program was modified to generate a warning when an invalid Work Date or Earning Period is encountered in a payroll transaction imported from a worksheet. Previously, the Payroll Calculate program did not generate a warning if it encountered an invalid date on a payroll transaction that was imported from a worksheet.  In some cases, this caused the Calculate process to stall.

 

New HR Messages are:

  • Warning 67 - Earning Period on Worksheet is invalid, Earning Period changed to match Work Date.

  • Warning 68 - Work Date and Earning Period on Worksheet are invalid, Earning Period changed to current Earning Period.

 

This modification applies to Payrolls run after the November 6, 2010 SR.  WSIPC will create a data manipulation to be run in a future release that will find and correct any payroll transactions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

Since worksheet detail Earning Periods are modified as indicated in the new warnings, subsequent calcs will not generate the same warning.  The exception warnings include the Work Date\Earning Period values as they were prior to modification by the calc for reference.

 

This modification applies to Payrolls run after the November 6, 2010 SR.  WSIPC will create a data manipulation to be run in a future release that will find and correct any payroll transactions that may have been processed incorrectly for payrolls run between April 10, 2010 and November 6, 2010.

 

Release:

Version 04.10.06.01.16, October 9, 2010

Feature:

WESPaC Payroll Calculate (Retirement Adjustments)

Issue #:

225227

Change:

The Payroll Calculate program was modified to process retirement adjustments marked ”r;Include in Retirement Balancing” as entered for the current payroll, but not include them in rebalancing until the next pay period.  From that point forward, the adjustments will continue to be included in the balancing process.  Previously, retirement adjustments marked ”r;Include in Balancing” were processed as entered the first time the payroll calculate was run for a given pay period.  But, on the second and any subsequent calculate, these adjustments were included in the balancing.  Compensation, hours, and deduction\benefit amounts could have been adversely affected if any rebalancing occurred as a result of the entered adjustments.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.06.01.08, September 11, 2010

Feature:

WESPaC Payroll Calculate (Worker’s Compensation Hours)

Issue #:

227487

Change:

The Payroll Calculate program was modified to calculate workers’ compensation hours from the calendar when an employee has contract pay, but does not have a retirement member profile.  Previously, the program was using retire hours from the pay record rather than calculating the hours based on the Calendar that is selected for the associated contract.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

This is a duplicate of ticket 226201 and the defect correction was included in the July 10, 2010 SR.

 

Release:

Version 04.10.06.01.08, September 11, 2010

Feature:

WESPaC Payroll Calculate (Worker’s Compensation Hours)

Issue #:

226647, 226743

Change:

The Payroll Calculate program was modified to calculate workers’ compensation hours correctly when contract payment is for retro only (zero $ on the contract).  Previously, all workers’ compensation hours to date were backed out and the employee and employer amounts were refunded (negative values) if the contract payment was retro only.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.10.06.01.08, September 11, 2010

Feature:

WESPaC Payroll Calculate (Simultaneous E2 and T3 Retirement Reporting)

Issue #:

227282

Change:

The Payroll Calculate program was modified to correctly report retirement when there is compensation being paid on E2 and T3 simultaneously.  Previously, if an employee transferred from E2 to T3, but E2 compensation was still being paid, the residual E2 compensation was being inappropriately reported to the T3 period while T3 compensation was incorrectly redistributed and reported to the prior E2 period.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 23, 2010 NSR

Feature:

WESPaC Payroll Calculate (Retirement Deductions\Benefits)

Issue #:

228714

Change:

The Payroll Calculate program was modified to correct Retirement Deduction and Benefit Amounts to match retirement transactions.  Previously, in some cases involving retirement transaction reversals, the Retirement Deduction and Benefit Amounts were approximately double the retirement transaction ded\ben amounts.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 23, 2010 NSR

Feature:

WESPaC Payroll Calculate (Retirement and Work Hours)

Issue #:

228023

Change:

The Payroll Calculate program was modified to zero out Retirement Hours and Work Hours if there are hours on a pay code with Retirement Status of ’r;M’ which does not allow Hours and Days.  Previously, when there were hours on a pay code with Retirement Status of ’r;M’, the Retire hours and Work hours were not zeroed out to match the retirement transaction which adversely affected Retire, Work, and Unemployment hours.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 23, 2010 NSR

Feature:

WESPaC Payroll Calculate (Unemployment Compensation work hours)

Issue #:

227755

Change:

The Payroll Calculate program was modified to correct overstated Unemployment Compensation hours when retirement transactions are reversed.  Previously, when retirement transaction reversals contained hours, the hours were not subtracted from Work Hours causing the Unemployment Compensation hours to be overstated.  

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

WSIPC will apply a data manipulation to correct Unemployment from July 30 when the data manipulation was previously applied, to August 23, the date of this release.  No client action is required.

 

Release:

Version #: 04.10.06.00.00, August 23, 2010 NSR

Feature:

WESPaC Payroll Calculate (Plan 3 Deductions)

Issue #:

228610, 227802

Change:

The Payroll Calculate program was modified to ensure that retirement contributions (deductions) for employees on Plan 3 are properly charged the first time the Calculate process is run for any given payroll.  Previously, in some cases, Plan 3 deductions for lump sum pay items (pay codes with rate code and contract flags set to ’r;no’) with hours were not charged the first time the Calculate process was run and the amounts that weren’t charged were added to the next employee.  However, the deductions were properly charged on subsequent runs of the Calculate process.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 23, 2010 NSR

Feature:

WESPaC Payroll Calculate

Issue #:

228609

Change:

The program was modified to properly calculate workers’ compensation hours and tax when the employee had reached the maximum values of retirement projections and history.

Reason:

Workers’ compensation hours were being reversed when the retirement accumulations\history matched the projected value and the employee was receiving no other gross pay (benefits only).

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 14, 2010

Feature:

WESPaC Payroll Calculate (Plan 3 to Plan 0 transfers)

Issue #:

226030

Change:

The Payroll Calculate program was modified to properly report earnings as Plan 3 during the month when eligibility changes from Plan 3 to Plan 0, all earnings for that month should be reported as eligible.  Previously, on the retirement activity report, the projected amounts were correct but the current earnings being reported during the month that eligibility changed were being reported as Plan 0 rather than Plan 3.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 14, 2010

Feature:

WESPaC Payroll Calculate (Plan 0 to Plan 3 transfers)

Issue #:

213631

Change:

The Payroll Calculate program was modified to properly report earnings as Plan 3 during the month when eligibility changes from Plan 0 to Plan 3, all earnings for that month should be reported as eligible.  Previously, on the retirement activity report, the projected amounts were correct, but the current earnings being reported during the month that eligibility changed were being reported as Plan 0 rather than Plan 3.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.06.00.00, August 14, 2010

Feature:

WESPaC Payroll Calculate (Locks Up\Hangs)

Issue #:

227544

Change:

The Payroll Calculate program was modified to allow the process to continue when only reversing retirement transactions exist.  Previously, if all retirement profiles had start and end dates set as equal, the process assumed the employee should never have been on retirement and attempted to back out reported compensation, but stalled since there was no plan to place it in.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.01, July 10, 2010

Feature:

WESPaC Payroll Calculate (Workers’ Compensation Hours)

Issue #:

226201

Change:

The Payroll Calculate program was modified to calculate workers’ compensation hours from the calendar when an employee has contract pay, but does not have a retirement member profile.  Previously, the program was using retire hours from the pay record rather than calculating the hours based on the Calendar that is selected for the associated contract.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.01, July 10, 2010

Feature:

WESPaC Payroll Calculate (HR Messages)

Issue #:

225130

Change:

The Payroll Calculate program was modified to prevent the occurrence of HR Message #52 (Error - Retirement Deduction and\or Benefit exists and no active Retirement Member Profile found for earning period.) when an employee on Plan 3  has no compensation, but has retirement contributions dated the month after the employee’s retirement eligibility stop month.  However, error 52 will continue to be generated if an employee on Plan 3 has compensation and retirement contributions dated the month after the employee’s retirement eligibility stop month.  Error 52 will also still be generated if an employee on any plan other than Plan 3 has retirement contributions dated the month after the retirement eligibility stop month.  Previously, if an employee on Plan 3 had retirement contributions dated the month after the employee’s eligibility stop month, but no compensation, Error 52 was generated.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.01, June 22, 2010 NSR

Feature:

WESPaC Payroll Calculate (HR Messages)

Issue #:

225816

Change:

The Payroll Calculate process was modified to include two new HR Messages:

  1. Error 63 - Deduction and\or Benefit Code has Group not equal to Retirement and is assigned to a Retirement System\Plan.  

  2. Error 64 - Multiple Retirement Deduction and\or Benefit Codes assigned to one System\Plan are assigned to a Pay Record.

Previously, neither of these conditions which could cause Retirement Deduction\Benefit Amounts to differ from the Retirement Transactions triggered Payroll Exceptions.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

A data manipulation was applied to add the new HR Messages. No client action is necessary.

 

Release:

Version #: 04.10.01.01.01, June 22, 2010 NSR

Feature:

WESPaC Payroll Calculate (Retirement Deduction\Benefit Amounts)

Issue #:

225816

Change:

The Payroll Calculate program was modified to correct the following:

  1. Rounding of retirement deduction and\or benefit amounts.  Previously, in some cases, rounding issues caused the deduction and\or benefits amount to differ slightly from the retirement transactions which were correct.

  2. Inaccurate retirement deduction and\or benefit amounts that result when rebalancing previously reported earning periods if the following conditions are met:

1) The employee has a contract.

AND

2) The contract has prior work days that cross an employee\employer rate change boundary, e.g. August 2009.

AND

3) The calculation program is making compensation adjustments to earning periods containing different employee\employer rates than the current period.

Previously, the calculation was not updating some temporary records with the correct deduction\benefit amount.  The temporary records were then summarized to assign the deduction and\or benefit. Retirement transactions were correct, but the deduction and\or benefits were incorrect.  Deductions for plan 1 and plan 3 employees were not affected.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.01, June 5, 2010

Feature:

WESPaC Payroll Calculate (Worksheet Detail Pay Amounts)

Issue #:

225936

Change:

The Payroll Calculate program was modified to correct rounding of worksheet detail pay amounts which previously triggered the false occurrence of HR Message #54 (Error &endash; Worksheet Detail can’t be found, remove amounts on Pay Transaction and reimport the worksheet. Paycode [].).

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.01, June 5, 2010

Feature:

WESPaC Payroll Calculate (HR Messages)

Issue #:

224738

Change:

The payroll calculation program was modified to include the new HR Message #62.  This error message was added to indicate that retirement deductions\benefits are required on a retro pay code when the associated contract code is subject to retirement.  The new error message reads as follows:

”r;Retro Pay Code for a Contract subject to Retirement is Missing Retirement Deduction and\or Benefit Code.”

 

Previously, if a retro pay code associated with a contract subject to retirement was missing a retirement deduction and\or benefit code, a false occurrence of HR Message 19 (Error: Invalid retirement status code for specified system and plan) was generated.

Reason:

Approved Enhancement.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.00, May 18, 2010 NSR (Postponed from May 15, 2010)

Feature:

Payroll Calculate (Workers’ Compensation Charged Benefits)

Issue #:

225170, 225339, 225228

Change:

A data manipulation was applied to correct inaccurate or missing workers’ compensation charged benefits for payrolls run after the April 2010 SR and prior to the May 2010 SR.  A modification to the payroll calculation program was released in the May 2010 SR to correct inaccurate or missing workers’ compensation charged benefit amounts for payrolls run subsequent to the May 8, 2010 standard release only.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

The data manipulation locates missing WC benefit amounts that were not charged on paychecks after the April 2010 SR and prior to the May 2010 SR.

There are 2 situations where WC benefits weren’t charged:

  1. The employee did not have a member profile.

OR

  1. The employee had a member profile, but there were selected pay code(s) with hours and WC deductions\benefits attached but no retirement deductions or benefits attached.

Once the missing benefit amounts are determined, the data manipulation does one of two things, depending on whether a WC benefit adjustment code exists in the database:

  1. If a WC benefit adjustment code does not exist in the database, the log file lists the adjustments that are needed for manual entry by the district.

  2. If a WC Benefit Adjustment code exists in the database, it will create the adjustment on the control file for the adjustment amount, start and stop dates of 5\1-5\31\2010 and attach it to the appropriate pay record.  If the pay record doesn’t exist nothing is added to the control file and the log file lists that the pay record was not found.

Districts should ensure that a benefit code exists with Group ’r;Tax’ and Tax Type of ’r;WC Adjustment’ before the release. After the release districts will be provided with the log files listing the database changes. The pay codes that have adjustments added to them must be selected into the next payroll in order to process the adjustments.

 

Release:

Version #: 04.10.01.01.00, May 15, 2010 NSR

Feature:

Payroll Calculate (HR Message 52)

Issue #:

225075

Change:

The payroll calculation program was modified to correct the erroneous occurrence of HR Message 52: ’r;Retirement Deduction and\or Benefit exists and no active Retirement Member Profile found for earning period.’  The message erroneously occurred when there was a plan 3 choice member profile without a plan 2 member profile immediately preceding it.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.00, May 15, 2010 NSR

Feature:

Payroll Calculate (Deductions\Benefits &endash; Retro Pay)

Issue #:

225329

Change:

The payroll calculate was modified to no longer double deduction and benefit contribution amounts associated with retro pay amounts.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

Payrolls processed since April 10th charged twice the contribution amount for retro pay amounts.  Prior to running your next Payroll, a reversing deduction and benefit will need to be added to affected employees.  The deduction and benefit code used cannot be group retirement but should otherwise have all the same attributes as the group retirement deduction and benefit codes.  Amounts can be derived by comparing the payroll’s retirement activity ded\ben totals to the check register ded\ben totals for retirement ded\bens.  The difference would be the reversing ded\ben amount.  Retirement transactions were correct but the benefit and deduction did not match for people with retro pay.  If you would like assistance from WSIPC, please contact us.

 

Release:

Version #: 04.10.01.01.00, May 15, 2010 NSR

Feature:

Payroll calculate (Retirement &endash; Transfer from Plan 2 to Plan 3)

Issue #:

225064

Change:

The payroll calculate was modified to no longer report earnings and contributions for earlier earning periods to plan 2 when the employee has transferred to plan 3. When adjusting contract pay for earning periods prior to the transfer to plan 3, the rebalancing process was reporting the earnings and contributions to plan 2.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.00, May 15, 2010 NSR

Feature:

Payroll Calculate (Retirement and Work Hours too high for TRS 1 employees)

Issue #:

225469, 225324

Change:

The payroll calculation program was modified to correct the retirement and work hours for TRS 1 employees.  After the retirement rewrite release, April 2010 SR, retirement and work hours were too high for employees with TRS plan 1 member profiles.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

A data manipulation was applied to correct the retirement and work hours for TRS 1 employees for payrolls run after the April 2010 SR and prior to the May 15, 2010 NSR.  No client action necessary.

 

Release:

Version #: 04.10.01.01.00, May 15, 2010 NSR

Feature:

Payroll Calculate (Workers’ Compensation Hours &endash; WC Average)

Issue #:

225920

Change:

The payroll calculation program was modified to correct workers’ compensation hours for WC Averaging employees.  The calculation was not adjusting the workers’ compensation hours appropriately for WC averaging employees if they already had one or more checks processed during the month.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.00, May 8, 2010

Feature:

Payroll Calculate (Workers’ Compensation)

Issue #:

225170, 225339, 225228

Change:

The payroll calculation program was modified to correct inaccurate or missing workers’ compensation charged benefit amounts. After the retirement rewrite release, April 2010 SR, workers’ compensation charged benefit amounts were incorrect or missing if an employee had no retirement member profile.  This also occurred if an employee had a retirement member profile and there were pay records selected for the current payroll with no retirement deduction or benefit attached. This affected not only the Workers’ Compensation Payroll Report, but any report that includes workers’ compensation charged benefit amounts such as the Check Verification Register and the Check Register.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

This modification corrects the issue for payrolls run subsequent to the May 8, 2010 standard release only. A data manipulation to correct the inaccurate or missing charged benefits for payrolls run after the April 2010 SR and prior to the May 2010 SR is forthcoming in a future release.

 

Release:

Version #: 04.10.01.01.00, May 8, 2010

Feature:

Payroll Calculate (Calculation of Retirement Benefit)

Issue #:

224828

Change:

The payroll calculation program was modified to accumulate retirement adjustment employer contribution amounts to the benefit associated with the adjustment’s system and plan.  The employee contribution amounts were accumulating to both the deduction and benefit amounts when the adjustment was for an earning period outside the current member profile.  

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

To be affected by the defect an adjustment would have the following conditions:

  • Have an earning period other than a period effective for the employee’s current profile.

  • Have an employer contribution amount.

  • Have been processed in a payroll since 4\10\10.

Note:  Since the rewrite, the calc assigns the system, plan and type to adjustments according to which system, plan and type is effective for the earning period on the adjustment.

 

Release:

Version #: 04.10.01.01.00, May 8, 2010

Feature:

Payroll Calculate

Issue #:

225418

Change:

The payroll calculation program was modified to correct retirement re-balancing issues.  Previously, retirement calculations did not always re-balance appropriately when there were months on the contract that had zero projections and the pay amount on the contract was zero.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version #: 04.10.01.01.00, May 8, 2010

Feature:

Payroll Calculate

Issue #:

224998

Change:

Payroll calculation HR Message #55 was modified as follows:

From:  Retirement deduction\benefit from previous plan not attached to pay record.

To: Retirement deduction\benefit control record not attached to pay record.

The message was modified to be more generic because it might not always apply to the previous plan.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

Implementation Notes:

A data manipulation was applied to update the HR Message. No client action necessary.

 

Release:

Version #: 04.09.06.02.02, January 9, 2010

Feature:

WESPaC Payroll (Substitute Tracking Retirement Hours)

Issue #:

218451

Change:

The Payroll Calculate was modified to properly process retirement transactions for Substitute Tracking.  Previously, retirement hours were reported incorrectly when an individual had multiple substitute tracking transactions where one or more transactions had a split distribution.  

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.09.06.02.01, December 5, 2009

Feature:

Payroll Calculate (Disallow missing WC Deduction or Benefit codes)

Issue #:

219072

Change:

The payroll message, 58 "Pay record missing one of either WC Deduction or Benefit or deduction or benefit has mismatched stop\start date", will be changed from a warning to an error. Districts will no longer have the ability to update the message.  Currently, the calculate process doesn't correctly handle mismatched WC deductions or benefits.

Reason:

Defect correction.

Menu:

HR\PA\CP\CA

 

Release:

Version 04.09.06.00.01, August 15, 2009

Feature:

Payroll Calculate

Issue #:

3379

Change:

The Payroll Calculate process was updated due to changes implemented by the Retirement Rewrite project.

Reason:

Payroll Calculate process was updated because of:

  • Payroll Payables modifications for Washington Retirement

  • New ability to include or exclude retirement adjustments from the contract calculation process

  • New ability to not report an adjustment through the DRS transmittal process

Menu:

HR\PA\CP\CA

 

Release:

Version 04.09.02.00.01 May 9, 2009

Feature:

Payroll Calculation (Retirement Errors and Warnings)

Issue #:

213910

Change:

  1. Process was modified to display numerical values that exceed the limit per month rather than a series of ’r;?’ marks within the Payroll Calculate Exception Journal

  2. Modified the warnings associated with exceeding limits (hours, days, compensation, contributions) to display only for the current month rather than the fiscal year.

  3. Modified the warning ”r;Retirement transaction outside Eligibility Start\Stop Ranges” such that it will not display in the last month of employment.

  4. Warning ”r;Retirement deduction code not assigned to a retirement system and plan” was changed to an error and the deduction code was added to the message.

  5. The benefit code was added to the error message of ”r;Retirement benefit code not assigned to a retirement system and plan”

  6. Warning ”r;Retirement Deduction and\or Benefit exist and no active Retirement Member Profile found for earning period” will not display in the final earning period of employment.

  7. Removed warning message ”r;Worksheet detail total not equal to retirement transaction total for payroll transaction.  Call you data center.

  8. New error message:  ”r;Compensation, Contributions, Hours, or Days value exceeds DRS defined limits.

Reason:

  1. Client was unable to view the value.

  2. Reduce the volume of warnings within the exception journal.

  3. The system was giving a false warning in the last earning period of employment.

  4. The system should not allow the condition into the payroll process.  Also, adding the code to the message allows the client the ability to find and correct the code.

  5. Adding the code to the message allows the client the ability to find and correct the code.

  6. The system was giving a false warning in the last earning period of employment.

  7. The Message was no longer necessary.

  8. The system and DRS has limits per Earning Period on the following data fields:  Compensation (9,999,999.99), Days (99.9), Hours (999.9), and Contributions (9,999,999.99).  The system was modified to not progress to the next step without the client correcting the values that exceed the limits.  Previously values in excess of these limits were omitted from the transmittal, causing an out of balance transmittal file.  These limits are separate from the district-configurable HR Messages associated with Compensation, Days, Hours and Contributions.

Menu:

HR\PA\CA &endash; Payroll Calculate

 

Release:

Version 04.08.10.00.03, March 7, 2009

Feature:

Payroll Calculations

Issue #:

213116

Change:

Revised federal income tax and EIC tables to incorporate the new Making Work Pay credit,  as part of the American Recovery and Reinvestment Act.

Reason:

Required change by April 1st, 2009

Menu:

HR\PA\CP\CA

 

Release:

Version 04.08.10.00.01, December 16, 2008 NSR

Feature:

Payroll Calculate

Issue #:

211502

Change:

Payroll calculate will not issue the error "Disconnected Retirement Transactions" for disconnected transactions with a reporting period prior to the month of the earliest Paid Start Date of  any Pay record for the employee.

Reason:

Eliminate false errors.

Menu:

HR\PA\CP\CA

 

Release:

Version 03.07.02.00.00, April 7, 2007

Feature:

ESAM -- Verify Accounts Button

Remedy Ticket:

74626

Change:

A new button was added to the Payroll Calculate screen to allow the Forecast Payroll Accounts Report to be run from this location in addition to the Pre-Verify area.

Reason:

Not all Payroll runs go through the pre verify step. Because this report could identify any possible issues with the payroll it was included on the calculate screen to allow the use of this report without adding extra steps to payroll.

Menu:

Human Resources\Payroll\Current Payroll\Calculate

Note:

F109

 

Release:

Version 02.05.01.3, May 7, 2005

Change:

include\ighrchs02.i - version 010051

Reason:

The calculation to deal with contracts with a contract length that doesn't match the days in the calendar has been modified.  If a person worked fewer hours in a day than the default hours in the calendar, the calculation of hours was incorrect.  This will self-correct for employees that are still in the same position in the next payroll.

Menu:

Human Resources\Payroll\Current Payroll\Calculate