Requirement:

• First year → accrue 1 day monthly
• After 1 year → front load balance based on lookup table

I created 2 accruals:

• Years of Service < 1
• Years of Service >= 1

But after employee crosses 1 year, the balance is not calculating correctly. Looks like overlap/proration/front load transition issue.

Has anyone implemented something similar? Did you use separate accruals or a different approach?

I’m new to Workday Studio and trying to build my first integration, so any help would be really appreciated.

I have a RaaS report that pulls employees with an Accrual Override where End Date is blank and the employee is in a transition status. The business logic is that employees normally get 2 weeks accrual until 3 years of service, but some have negotiated overrides (for example, 3 weeks). Once they hit the 3-year mark, they should automatically go back to the standard policy, so the override needs to be end-dated.

What I’m trying to build (boomerang use case):

• Pull the report into Workday Studio
• Use XSLT to transform the data
• Call Put_Absence_Input_Request to update the End Date in Workday

Current status:

• RaaS report is ready
• Outbound EIB is already built
• Now I’m working on the Studio piece (first time doing this)

What I need help with:

• How to structure this properly in Studio (components, etc.)
• How to handle the filtering logic for blank End Date + transition status
• Best way to transform RaaS output into Put_Absence_Input_Request using XSLT
• Any common pitfalls or things to watch out for when doing this kind of boomerang update

Any guidance or examples would really help 👍