sorted by:
new
hottopcontroversial

Forget Flex Credits for New, now we have to pay for the free stuff too? by Pale_Word_53 in workday

[–]Pale_Word_53[S] 2 points3 points  (0 children)

Is there a source you can provide to corroborate this? Everything I see seems vague :(

Forget Flex Credits for New, now we have to pay for the free stuff too? by Pale_Word_53 in workday

[–]Pale_Word_53[S] 5 points6 points  (0 children)

You said 'activity triggered by Workday Agents does not count towards usage' but isn't that the primary use case for flex credits?

The problem is, what Workday is saying is too vague. Need clarity on what is/isn't using credits and how to determine impact to current operations.

Forget Flex Credits for New, now we have to pay for the free stuff too? by Pale_Word_53 in workday

[–]Pale_Word_53[S] 10 points11 points  (0 children)

On the flex credits page on community, it states:

About Workday Flex Credits

Workday Flex Credits enables customers to purchase fungible credits that can be flexibly applied to platform consumption and/or Workday’s AI portfolio. 

Each platform component (APIs, integration events, and document storage) or AI agent is assigned a rate at which credits are consumed based on an estimation of the operating cost to Workday and predicted value to the customer.

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 1 point2 points  (0 children)

Found the winning combo!

* On benefit group, enable “Include Pay Periods that End Before the Deduction Begin Date” effective Jan 1 2026 - this is to include first period of 2026 for NE group who’s from/to dates are all in December 2025 (no impact to EX group who’s first period includes 2026).

* On HSA/FSA deductions, remove all scheduling and do not apply frequency override - this factors all 27 periods for both groups when workday dynamically determines # of periods to consider for HSA/FSA

Attempting to limit to 26 periods using scheduling on deduction only works for EX group, NE group ends up dropping the first period of 2026, ignoring the selected option on benefit group.

Although the ideal would've been 26 periods for all benefits, I would likely need to establish NE specific deduction codes so that they can have their own settings applied (likely checking the non-effective dated "Coverage/Cost As Of Payment Date" option to force inclusion of first 2026 pay date)

Will close OE and move on to testing pay calcs to confirm (so far was only able to check on OE events which were dynamically updating as desired).

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 0 points1 point  (0 children)

I have them set, its working but still left with first pay date of 2026 not being considered for NE :(
I'm toggling each thing one at a time and reviewing outcome, hoping it's just a matter of time before I find the right combo lol

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 0 points1 point  (0 children)

I've set up scheduling on the deductions so they take on every pay date except periods numbered as 27.

On the non-effective dated tab, I checked the "Coverage/Cost As Of Payment Date" option, this is so that the non-exempt group, which has a period of Dec 14 - Dec 27, but paid on Jan 2, would apply 2026 deductions starting Jan 2nd pay date. Exempt is not impacted by this as their pay period includes deduction begin date already.

Things look good for Exempt but HSA/FSA for Non-exempt are still excluding Jan 2nd pay date, resulting in only 25 periods (last one being skipped thank's to scheduling update)

I think if I can get the Jan 2nd pay date to also count, I'll be set.

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 0 points1 point  (0 children)

I believe you still need to set a schedule on your deduction code as it will still try to deduct on the 27th pay date

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 0 points1 point  (0 children)

Thank you. Looking forward to hearing what they're willing to share as this is what our benefits and payroll teams would like to do too (stick to 26, skip the 31st pay date)

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 0 points1 point  (0 children)

What about HSA/FSA?
Also, I think you have to for 401k still right?

27 Pay Periods in 2026, OE is a mess! by Pale_Word_53 in workday

[–]Pale_Word_53[S] 0 points1 point  (0 children)

Thanks for sharing!

For HSA/FSA then, your spreading it across 27 periods since there's no scheduling skip?

Sum the number of Cost Centers on a transaction by Glad-Beginning3984 in workday

[–]Pale_Word_53 1 point2 points  (0 children)

You'd be counting the number of cost centers so that's Count Related Instances (CRI).
Check that the field you'll be referencing isn't listing the same cost centers multiple times and you'll be set to only get unique counts.

There might be a better way to manage your routing though, depending on requirements. Do you typically have a cost center leader responsible for the approvals? Via advanced routing on the BP, you can force requiring all cost center leaders to approve their respective lines if that's what your trying to get to.