Somebody worked three hours on a Sunday. The boss said take Friday afternoon.
That is a complete business process. It has an agreement, an obligation and a settlement, and in most companies it is recorded nowhere at all. It lives in two people’s memories, and those memories will differ slightly within about six weeks.
It works until it doesn’t. The manager moves on and the obligation goes with them. The employee is certain it was four hours, not three. Somebody else did the same favour, never got the afternoon back, noticed, and quietly stopped volunteering. None of that shows up as a problem anyone can point at — it shows up as goodwill draining away for reasons nobody can quite name.
Why Most HR Software Is Bad At This
The gap is wider than you would expect for something so common, and part of the reason is legal rather than technical.
In the United States, the Fair Labor Standards Act generally prohibits private employers from giving compensatory time off instead of paying overtime to non-exempt staff. It is lawful for public-sector employers, and discretionary for exempt employees, but for the average private business it is not an option. A great deal of HR software is built for that market, and there is little commercial reason to build a feature most of your customers cannot legally use. So it tends to arrive as a leave balance somebody adjusts by hand, if it arrives at all.
Products built where time off in lieu is ordinary — the UK, Europe, Australia — do handle it, generally as an absence type sitting alongside vacation in the leave module.
The most thorough implementations go considerably further. Odoo, for instance, computes extra hours from clock-in and clock-out against each employee’s contracted working schedule, applies tolerance thresholds and overtime rulesets, and can automatically net the accrued time against a time-off request. It is genuinely well built. It also means configuring a working schedule and an overtime ruleset for every employee before any of it becomes true, and keeping those correct as agreements change.
Recording Instead of Deriving
Opterion-IT takes the opposite approach, and it follows from the same principle as the rest of the time card module: the software records what people tell it and never decides on their behalf.
The Sunday goes on the card as a Lieu Earned line. The Friday goes on as Lieu Taken. Both are entered by the person they happened to and approved by their manager, exactly like every other line. The balance is one minus the other, and it carries forward across pay periods indefinitely — a lieu balance that reset when a pay period closed would be worthless, so this is the one figure in the module that deliberately reads back through closed periods forever.
There is no working schedule anywhere in the system. There is nothing to configure per employee before the feature works, because the system is not trying to work out what you are owed. Two people agreed something; its job is to remember it accurately.
The Rate Is Yours, Not Ours
Jurisdictions differ on what an hour of overtime banks. In British Columbia, overtime credited to a time bank is banked at the overtime rate — three hours worked becomes four and a half hours off. Elsewhere it is hour for hour.
So the banking rate is a setting you control. Set it once, and the entry screen does the arithmetic as you type: enter the hours worked, and the hours banked are proposed for you.
What matters is what happens next. The proposed figure can be typed over, and what gets stored is the number the manager approved — not the rule that produced it. Nothing is ever recalculated later from a rate that might since have changed, which means adjusting your rate next year cannot silently rewrite last year’s balances. Opterion-IT ships no legislated rates and no jurisdiction table, so there is no compliance update you are waiting on from us.
And where banking overtime is not lawful at all, it is not a setting you switch off and hope nobody re-enables. Deactivate the two lieu time types and the feature is not there — not on the entry screen, not on the approval screen, not on the HR dashboard.
Where the Balance Actually Gets Seen
A balance nobody looks at is not much better than a balance nobody recorded.
The lieu balance appears on the manager’s approval screen, directly above the comment box — the last thing read before a time card is approved or returned. That placement is the feature. There is no report anyone has to remember to open, and a balance that has grown large and sat untouched for months arrives in front of a decision-maker every single pay period, with the date it last moved.
Employees see their own balance on their card and on their dashboard. HR sees everybody’s, ranked by who is carrying most, including anyone who has come off time cards while still holding hours — precisely the person who would otherwise be forgotten.
Use It or Lose It, Without an Expiry Engine
Plenty of organisations cap how long banked time can sit. Opterion-IT does not enforce that with a rule, and that is a deliberate decision rather than a missing feature.
When hours have gone stale under your policy, HR removes them with a signed, attributed adjustment — the same mechanism used for every other correction on a time card. It carries a reason, it names who made it, and the employee sees it on their own card. An expiry rule that quietly deleted someone’s banked time in the night would be faster and considerably worse.
Nothing stops a balance going negative either. Taking the Friday before working the Sunday is an ordinary arrangement, so a negative balance is shown in red rather than blocked. The system signals; the people decide.
The Point
Most companies do not need a system that works out what their staff are owed. They need one that does not forget what was already agreed.
The three hours on that Sunday were never a difficult calculation. They were an obligation with no home — and the cost of that shows up much later, in a conversation about fairness that nobody has the records to settle.
Time in lieu is part of the Opterion-IT Human Resources module, alongside time cards, employee records, leave and hiring. See how the HR module works →
The module behind this
Human Resources →
Employee data, leave, hiring, time cards, and a punch clock at the door — with hours booked to the job they were worked on, and without the spreadsheet sprawl.
Keep reading
- Why Your Timesheet System Shouldn't Do the Math
Almost every timesheet product sells you a rules engine that works out overtime. It is the part most likely to be wrong. Here is what happens without it.