Overview

This topic is very complex. The process differs based on the situation.

Example Situation 1

Situation Description

A Cost Type was remapped to a different payroll item since the Cost Rates were originally reconciled.

Context

This might happen if you change payroll systems.

We saw this happen with a company that was acquired and moved to a new system.

In the old system, they had recorded California Meal Penalties as Regular Hours, but in the new system, Meal Penalties had their own Payroll Item. When Payroll Costs were imported, all the Meal Penalty-coded costs got shuttled into AdHoc Overhead.

Thankfully, the company had been using a custom Cost Type to identify Meal Penalties.

How to Solve - Case Study

First, you remap the Cost Type.

In the example above, when we went to Quick Launch > Reference Types > Cost Types and looked at Meal Penalty, we originally found it mapped to "REGHR," we remapped it to "PNLTY."

So remapping the Cost Type fixes it? Not quite.

Do we recalculate the Cost Rates for the Payroll Period? You might be tempted to think this would solve the problem, but it doesn't. Here's why: When you first open the Payroll Period card, if nothing has been changed, the Cost Types table will be empty. You might assume this means the system is using whatever Cost Type mapping is currently in-effect, but this is not correct. It is using the Cost Type mapping that was in-effect at the time of original recalculation. Any time you update Cost Type mapping after Payroll Costs have been imported/synced, you MUST "update cost mapping" here AND THEN Recalculate Cost Rates:

This should fix the problem

[Article Under Construction - More Coming Soon]