Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Description of Issue

What is causing the could not match PSD to city code error?

Example: 

Emp: [Affected Emp#], PSD 1: [1st affected PSD value], PSD 2: [2nd affected PSD value] - could not match PSD to city code

Emp: 123456, PSD 1: 450104, PSD 2: 450104 - could not match PSD to city code

Context
  • Payroll
  • Pennsylvania
  • PA Act 32 Report
Cause

When the LIT Local Code Deductions option in the Payroll Control Settings program is either 1 (Primary Location and City Code in the Master) or 3 (Job/Salary Location and City Code from the Master), this error indicates that the system can't figure out which PSD is the residence PSD.  

Error can be caused by inaccurate define of the PA Act 32 Generate screen, or if the City Code is either not populated, or has never been never populated with a code that correlates to the PSD code.

Resolution
  1. Ensure that a 5000 range deduction has not been populated anywhere on the screen except for the Deduction Exclusion, if applicable. 

  2. Correct setup for future payrolls by populating the City Code in the Employee Master

  3. For the current reporting quarter, manually maintain the PA Act 32 Period Records for the employee in question before creating the submission file.

Additional Information

Review PA Act 32 Report - Setup for additional details on creating and linking City Codes.

Review PA Act 32 Report - Processing for additions details on Generate define.





  • No labels