Digital leave requests: approval rules, balances and software selection
- Custom Software
- 5 min read
The request is in an inbox, approval in a chat and the remaining balance in a spreadsheet. Digital leave management should produce one dependable record. First establish who approves, which working days count and which system owns the balance. Those decisions make the choice between an existing product and a custom integration much clearer.
Document the existing process first
Map the path from request to payroll. Identify decision owners, absence cover, deadlines and the authoritative leave record. Check whether your existing HR or time-recording product already supports the process. Another application can otherwise create another reconciliation task.
For Austrian businesses, leave is generally agreed between employee and employer. Calendar availability alone does not replace that agreement. Have payroll or an appropriate adviser settle entitlement calculations and exceptional cases before automating them.
Separate requested, approved and taken leave
Show available balance, approved future absence and pending requests separately. Employees should be able to understand why a displayed figure differs from an annual spreadsheet total.
Changes after approval need their own process. Moving or cancelling a period must reverse the original booking transparently. A repeated message must not deduct leave twice. Cover arrangements must not allow two conflicting approval decisions to be recorded.
Use your working patterns as acceptance cases
Have the expected balances confirmed before testing. This is a software test template, not a legal formula for entitlement.
| Case | Expected evidence |
|---|---|
| Part-time pattern with fixed non-working days | the agreed working-day calculation is applied |
| Public holiday inside a leave period | correct handling for the location and work pattern |
| Leave crossing year-end | traceable allocation to the appropriate account |
| Substitute manager approves | authority, decision and time are recorded |
| Approved leave is changed or cancelled | calendar and balance are corrected together |
| Duplicate payroll export | one request produces one intended posting |
Limit what the shared calendar reveals
Scheduling often needs only a record of availability. Detailed reasons, documents and personal balances should not automatically appear in a shared calendar. Define separate views for employees, managers and payroll.
Specify access removal when someone leaves and who can inspect historical changes. Data minimisation provides a useful boundary: process the information necessary for the defined purpose.
Test a standard product before commissioning a custom tool
A product is a strong candidate if it supports your working patterns, approval rules and required exports. Test those capabilities directly. A custom integration becomes more useful where leave must connect closely with an existing scheduling system or essential rules would otherwise remain in spreadsheets.
Compare implementation, migration, training, licences, interfaces, operation and future changes over the same period. Custom software also has recurring costs. A claim that it pays for itself after a few years is incomplete without them.
Illustrative arithmetic using assumed prices: 25 employees at €6 a month cost €1,800 a year before setup or add-ons. A custom tool costing €8,000 plus €100 monthly operation totals €12,800 over four years. These are calculation inputs, not market prices or a recommendation of either option.
Scenario calculator · adjust values for your comparison
€0 + 48 × €150
€8,000 + 48 × €100
Illustrative assumptions: standard product for 25 people × €6/month; custom tool €8,000 + €100/month. Not market prices. Onboarding, add-ons and internal work are excluded.
Start migration with agreed opening balances
Record a cut-off date, balances and approved future leave. Resolve disputed figures before import. The first digital balance should be traceable to a signed-off starting record.
Pilot with a limited group and reconcile the calendar, balances and export after a complete payroll cycle. Then establish when all new requests move into the selected system. A short planned comparison with the old record can help; indefinite duplication creates new inconsistencies.
Measure questions, corrections and turnaround time. Fast approval is useful, but a correct and understandable balance is what gives people a reason to trust the tool.