Balances live in a spreadsheet, and the version on your screen is not the one the manager is looking at.
A leave balance nobody has to reconcile.
Koldheim keeps leave as a ledger of movements with dates rather than a number in a column, so a balance is something you can read back rather than something you have to trust.
What it looks like now
Two managers approve on the same morning and the second approval quietly overwrites the first.
Your leave year does not start in January, so every report has to be adjusted by hand.

What you get, and where it shows up
The balance is its rows
A grant and a day taken are movements with dates. Approving leave adds a row rather than editing a total, so the balance can always be read back to where it came from.
More on thisTwo approvals cannot lose one another
Approvals landing together are written as separate movements. Neither overwrites the other, and the balance that results is the sum of both.
More on thisYour cycle, not the calendar
The anchor date, the length in months and the days per cycle are your organisation’s own record. Which cycle today falls in is derived, so it never goes stale.
More on thisWhere you work in it
Where to next
The rule the service runs, in your browser. No form, no call.
Stop chasing approvals. Start running the process.You own a process that lives in inboxes, spreadsheets and corridor reminders. Koldheim gives it a shape everyone follows, and shows you where every request is.
No spend without the right signature.Requests arrive priced from stock, with the department budget in front of the approver. Over your threshold, a second signature is required before anything moves.