Blog
An internal system for leave, purchases and approvals: how it is built and what it costs
6 min read
Short answer
An approvals system is a small project, because its core is four things: a request, an approver, a decision and a record. The price is set by the number of request types and approval rules, not by the number of employees. A limited version with two or three request types (leave, purchase, expense) can usually be built in the lower half of the €2,000–10,000 range, but only an audit gives the exact figure. If you already have Microsoft 365 or payroll software that handles leave, check first whether that is enough.
01What the system is made of
For each type of request the same things can be written down:
- 01A form: what it asks (leave dates, purchase amount and reason, supplier) and what is mandatory.
- 02An approval route: who approves, when and in what order. For example, leave by the direct manager, a purchase up to a set amount by the team lead and above it by the managing director too.
- 03Statuses: submitted, approved, rejected, returned for more information, cancelled. Everyone can see where their request is.
- 04Notifications: the approver gets a message by e-mail or chat and answers with one click, without logging in to yet another application.
- 05A record: who approved what and when. For purchases it is the basis for accounting, for leave the basis for payroll.
02Leave: what comes on top
Leave has its own surprises: the balance of days, public holidays, half days, entitlement carried over from last year and the rule that the whole team must not be away at once. Check the entitlement rules with whoever does your payroll rather than from the example of some tool.
On submission the system can flag that two colleagues from the same team are already away that week. The decision stays with a person, who now sees more than they do today.
03What pushes the price up
- 01The number of request types and distinct approval routes.
- 02Deputising: what happens when the approver is out. A seemingly small matter that has to be handled, or requests stall.
- 03Change after approval: cancelling or moving leave or an order that has already been approved.
- 04Integrations: the team calendar, payroll, accounting or stock. Each is a small project.
- 05Permissions: who sees others' requests. A manager sees their team, accounts sees every purchase, nobody should see the reasons for sick leave.
04When you do not need to build it
If you use Microsoft 365, Teams has an Approvals app, and for a single request type with a simple route it may be enough. Even a filled-in form e-mailed to a manager is fine while requests are few.
A custom system begins to pay off when request types multiply, when approvals get lost in inboxes, and when you need to look back at who approved what. Running costs are tens of euros a month and maintenance 10–20% of the build cost per year.
Frequently asked
- How much does an internal approvals system cost?
- A limited version with two or three request types usually lands in the lower half of the €2,000–10,000 range. The exact figure depends on the number of request types, the approval rules and the integrations.
- Can it be solved without a custom system?
- Often yes: approvals in Microsoft 365 or leave handled in payroll software. A custom system pays off when request types and rules pile up beyond what a ready-made tool carries.
- What is hardest about leave?
- The balance of days, carried-over entitlement, public holidays and deputising. Check the entitlement rules with your payroll person before they go into a system.