Leave Management App: Accrual and Adjustable Leave Features
Enterprise client
In short
How can a Power Apps leave app support hourly and daily accrual per policy?
A leave app that applies one accrual type to every policy and cannot adjust a balance sends HR back to manual corrections. The client already ran a leave app built on Power Apps and SharePoint. We built two new features, hourly or daily accrual per policy and adjustable leave, in about 20 hours.
Results in numbers
- tasks, two features
- 14
- for both features
- 20 hrs
At a glance
- Hourly or daily accrual for each leave policy
- Adjustable leave with earned and taken balances
- 14 tasks delivered in about 20 hours
The client
It runs a leave management app built with Power Apps and SharePoint, with leave policies, employee leave records, a settings area, notifications with calendar events and reports saved to SharePoint.
What it was costing them
- Rigid accrual: the app could apply one accrual type to all policies, but not choose hourly or daily for each policy.
- Manual balance corrections: users could not adjust a leave balance up or down inside the app.
- Reporting gaps: reports needed extra rows to show adjusted leave.
- Install drift: every change to the lists must also reach the initial installation process, or new installs differ from live ones.
What we built
We built two features for the existing leave app and delivered the work task by task.
- Accrual that fits the policy: a new accrual type column on the leave policies lets each policy accrue hourly or daily.
- Control in one place: a new toggle in the Settings tab chooses hourly or daily accrual, and the option to apply one accrual type to all policies is hidden.
- Consistent installs: the initial database installation process includes every new column and field value.
- Adjustable leave: a new flag on each policy marks it as adjustable, with its own toggle in Settings.
- Easy adjustments: the leave request screen lets a user change the time allocation for an adjustable policy, with a toggle and a time period selection.
- Correct balances: new columns on the employee leave records hold the adjustments, in step with earned and taken time.
- Clear messages: notifications and calendar events get new message types for adjusted leave.
- Better reports: the file saved to SharePoint and the app report include extra rows for adjustments.
Results
- The work was split into 14 tasks across two features and built in about 20 hours in total.
- HR no longer needs to correct balances by hand outside the app.
- Each leave policy can accrue in hours or days from settings, with no code change.
The risk most teams miss
Changing columns on live SharePoint lists is where leave apps break. By month three a list change without a matching install update leaves new setups with a different structure, adjusted balances drift from the real earned and taken time, and nobody can explain a number. We log every adjustment with who, when and why, test the migration of existing balances first, and make the install process the single source of the list structure.
What we would add today
Improvements we would add on top of what is live.
- Move leave policies, balances and adjustments from SharePoint lists to Dataverse, with an adjustment ledger table so every balance can be rebuilt.
- Use Dataverse row and field security so employees see their own balance, managers their team, and HR everyone.
- Require a Power Automate approval for adjustments, with auditing of who changed what.
- Package the app as a solution with environment variables and connection references, and release it through Power Platform pipelines instead of an install script.
- Add a Copilot Studio agent in Teams that answers how much leave an employee has left.
Technology
Power Apps, SharePoint lists, Power Automate notifications and calendar events.
Tell us which leave rules your current app cannot handle, and we will tell you what it takes to add them safely.
Products and capabilities
- Power Apps
- SharePoint
- Power Automate
- leave management
- leave accrual
- HR app
The service behind this work
Power Platform development
Related use cases
HR and peopleOvertime Management in Microsoft Teams
When overtime requests arrive by paper, mail, chat and phone, nobody can say with confidence who worked extra hours, and the data is too poor to report on. The client wanted to digitalise overtime requests but keep its formal PDF template. We delivered an app in Teams with multi-level approvals that prints each request on that template.
Travel Approval App on SharePoint with Teams Approvals
Travel approvals sent by email wait for someone to notice them, go to the wrong person when teams change and leave no clean record. We built a light solution on SharePoint and Teams Approvals that routes each request by team and writes the decision back, without a heavy custom build.
- 30 hrs
- build effort
- 2
- SharePoint lists
Onboarding Solution Assessment and Action Plan
The onboarding solution is a global onboarding solution that people and culture teams rely on. It ran in a single production environment, so every hand edit added a hidden layer that blocked later updates. We assessed the whole solution and gave the client a clear action plan to bring it back under control.
- c. 30
- connection references
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.