Why Your Timesheet System Shouldn't Do the Math

Ask a timesheet vendor what their product does and you will get a list of calculations.

Overtime after eight hours in a day, or forty in a week, or forty-four depending on where you operate. Time-and-a-half, double time on a seventh consecutive day, shift differentials, statutory holidays, and a considered position on what a statutory holiday is worth to somebody who worked half of one.

It is a genuinely impressive amount of machinery. It is also the single most dangerous part of the system, because payroll is one of the very few places in a business where being wrong does not cost you a bad afternoon — it costs you the trust of everyone who works for you, and it takes weeks to unwind.

The Opterion-IT Time Card module does none of it. That is not an omission. It is the design.

The Rules Engine You Do Not Need

In Opterion-IT, ten hours worked on a Tuesday is not one line that the software then interprets. It is two lines: eight hours of Regular and two hours of Overtime, entered by the person who worked them.

The system records what the employee said about their own time. It never derives, classifies, or reinterprets it.

Removing that one behaviour removes an enormous amount of everything else. There is no work-week versus pay-period boundary problem, because nothing needs to know where the boundary falls. There is no union agreement to encode, no compressed four-day schedule to special-case, no rule for a weekend shift swapped for a Tuesday off, and no mechanism required for time taken in lieu. Every one of those situations is simply a line on a card, entered by the person it happened to.

Nobody had to teach the software about them. More importantly, nobody has to maintain them the next time an employment agreement changes — which is where rules engines quietly go wrong, long after the person who configured them has moved on.

The trade-off is honest, and worth stating plainly: somebody still has to look at the numbers. That somebody is the manager, who was always accountable for them.

The same principle shows up in the small details. Pick a date that falls on a public holiday, or on a day the employee has approved leave, and the entry changes colour as the date is chosen. Nothing is pre-filled and nothing is blocked — an employee called in for two hours in the middle of their vacation simply enters the two hours, and sees that the system already knew. It surfaces what it knows and leaves the judgement where it belongs.

A Number That Stops Moving

The second design decision matters as much as the first, and follows from the same instinct.

Only the employee ever edits their own time card. A manager can approve it, or return it with a required reason that sends it back as a draft — but a manager can never reach into it and change a figure. That is not an oversight in the permissions model. It is the point. An employee can never credibly claim that their recorded hours were altered by somebody else, because there is no mechanism by which that could have happened.

Once a card is approved, it is locked. Not locked against the employee — locked against everyone. The employee cannot reopen it, the approving manager cannot revise it, and HR cannot quietly correct it. An approved figure in Opterion-IT is a permanent record of what was agreed between an employee and their manager at a point in time.

Pay periods work the same way. Once HR closes a period, it cannot be reopened. A closed period is a settled one, and it stays settled.

Corrections Without Rewriting History

None of that would be workable if corrections were impossible, because corrections are routine. Somebody arrived late and said so afterwards. Somebody forgot a Tuesday entirely. A card was approved in good faith with the wrong number on it.

Opterion-IT handles all of this by adding, never by editing. An HR adjustment is a new signed line — plus or minus, with a reason, attributed to the person who posted it — that sits alongside the approved figure rather than replacing it.

If the pay period is still open, the adjustment lands on the original card. If the period has already closed, it carries forward onto the employee’s next card with a pointer back to the card it corrects. The employee opens the following period and sees the correction, what it relates to, and who made it. Nothing is done to somebody’s pay behind their back.

Payroll receives both figures separately. Approved hours in one column, adjustments in another, exported as a file your payroll process can actually consume. The two are never silently added together into a single number that nobody can subsequently explain.

The Card Nobody Filled In

There is a smaller feature here that tends to matter more in practice than any of the above.

When a pay period opens, Opterion-IT creates a card for every enrolled employee automatically. Nobody has to request one, and nobody has to remember to start one.

The consequence is that an employee who has not submitted anything does not simply fail to appear. They show up on their manager’s approval list as an empty card, from the first day of the period. Chasing timesheets was never really the hard part of running payroll — not knowing who needed chasing until the Friday afternoon deadline was.

The module also holds an approval failsafe for the people at the top of the reporting tree, who by definition have no manager to approve them. Without it, one person with nobody above them stalls the entire payroll run. With it, HR can cover exactly those cases and no others, and the approval list says why each row is there.

What the Hours Were For

Payroll is the obligation. It is rarely the reason a business wants time recorded.

Every line on a card can also carry what the work was for. That might be an internal piece of work described in free text, or a specific live customer order chosen from a list. Book two hours to an order, and those hours appear on the order itself — who worked them, when, how many, and what they noted — sitting alongside the material that shipped against the same job.

That is the difference between knowing what a job cost you in parts and knowing what it cost you altogether. It is also the answer to the question every business asks after the fact and can rarely evidence: was that job actually worth doing?

The charge-to feature is deliberately optional and module-aware. An organisation running Opterion-IT for HR alone still gets it, because internal work is free text and depends on nothing else. The customer order list appears only for organisations that also run Quotes & Orders. The module stands on its own, and gets better in company.

The Point

A timesheet system that calculates is a system you have to trust with a set of rules that change, that somebody has to maintain, and that will eventually be wrong about somebody’s pay.

A timesheet system that records what your people tell it, locks it once their manager agrees, and corrects by appending rather than editing does not have that failure mode at all. What it asks in exchange is that a human being looks at the numbers before approving them — which, in a company of twenty or a hundred people, they were always going to do anyway.

---

Time cards are part of the Opterion-IT Human Resources module, alongside employee records, leave, and hiring. See how the HR module works →