Hello All,
I’m currently trying to build a budget for the next year and running into issues on how to lock data down.
Example: Set up a budget for FY26
Current Date: 12/19/25
Current Month = Dec 2025
Latest Actual Month (Switchover Month) = Nov 2025
OpEx Planning: I will set the switchover month as Nov 2025, so the data is locked down already.
Headcount Planning: Our headcount roster is being loaded on a daily basis and overwritten until the last day of each month so our most up to date data is 12/19/25.
Let’s say I want to say today is the day I want my budget to be set and won’t change after 12/19/25. I can create a scenario based on my current scenario which locks down the data for OpEx but my headcount data will essentially be still moving because by tomorrow, it would be using a new transaction list on 12/20/25.
I’ve thought of few proposals to resolve this issue but each has its own flaws so I would like to know the best practice to lock down the data.
Proposal 1: Use Headcount data as of Nov 2025
This method ensures my numbers won’t change because all data is fixed already but I lose the potential of using the most updated data when I set budget for 2026.
Proposal 2: Creating a snapshot
This method ensures my numbers won’t change but defeats the point of creating a Budget scenario because the snapshot will not align with the scenario. And the snapshot is less flexible than using scenarios.
Proposal 3: Stop importing headcount data until the next month
This method ensures my numbers won’t change but I’m also able to use the most current data for my forecast. The issue for this is Workday imports have to be scheduled on a cadence and this method would need manual uploads.
Thank you!
