Workday SAM Pro – Worker Category mapping for Hourly vs. Salaried Workers

[SaiSomaC]

Hi everyone,
We are implementing the out-of-the-box Workday integration with SAM Pro and have a question regarding the Worker Category mapping.
Currently, we have the following Worker Category mappings configured in ServiceNow:
Hourly Worker → Worker Type: Employee, Employee Type: Regular, Time Type: Full Time
Salaried Worker → Worker Type: Employee, Employee Type: Regular, Time Type: Full Time
The issue is that both Hourly and Salaried workers have the same values for Worker Type, Employee Type, and Time Type. Therefore, we cannot uniquely distinguish between the two categories using the available OOB mapping fields.
From the Workday data, we found that the Pay Rate Type field differentiates them:
Hourly workers → Pay Rate Type = Hourly
Salaried workers → Pay Rate Type = Salary
However, Pay Rate Type does not appear to be available as a field in the SAM Pro Workday Worker Category configuration.
Has anyone encountered a similar scenario with the Workday → SAM Pro integration?
What would be the recommended approach?
Is there an OOB way to use Pay Rate Type for Worker Category mapping?
If not, is there a recommended way to bring the Pay Rate Type from Workday into ServiceNow and use it for the mapping?
Would a custom/derived field or customization of the Workday integration be recommended, or is there another OOB approach we should consider?
Any guidance from someone who has implemented Hourly vs. Salaried worker categorization in SAM Pro would be greatly appreciated.

[Dan_Junqueira]

Hi @SaiSomaC,

I think you’ve found a genuine limitation in the OOB mapping.

Looking at the current Workday SAM Pro configuration, the Worker Category mapping is based on Worker Type, Employee/Contingent Worker Type and Time Type. Pay Rate Type is not one of the available mapping criteria.

So if both populations are:

Employee + Regular + Full Time

then OOB there really isn’t enough information in that mapping to distinguish Hourly from Salaried.

Before customizing the integration, I would first check whether Workday can provide that distinction through one of the supported fields, particularly Employee Type.
If that isn’t possible and Pay Rate Type is the only reliable attribute, then I would look at bringing that value into ServiceNow and deriving the worker category before the SAM calculation uses it.

I would try to avoid modifying the OOB Workday/SAM Store application directly, though.
That can become painful during upgrades. I’d rather keep the OOB integration intact and add the additional logic around the inbound data or mapping layer.

One other important point: because Worker Category is used for the FSE calculation, I would also validate the approach against the actual Workday licensing terms before changing the classification logic.

You want the technical categorization to match how those worker populations are defined contractually.

So in short: I don’t see an OOB way to add Pay Rate Type to the Worker Category criteria today.
If Pay Rate Type is truly the only discriminator, some enrichment/derived mapping will probably be required.

Would be interesting to hear if anyone has solved this without extending the OOB mapping.

Hope this helps. If it does, please mark the response as useful.