Time and attendance: time accounts, flexitime and overtime under control
The time and attendance layer of Notory Hora runs flexitime, overtime and other accounts through one generic accounts engine: rolling balance, capping, carry-over and forfeiture - rule-based and fully traceable. Overtime goes through a clean request-approval workflow, with a choice of payout or time off in lieu. Real balances replace the informal shadow spreadsheets.
Time account with rolling balance
A generic accounts engine with account type, posting rate and a running balance. Capping as an amount plus behaviour plus cut-off date, with rule-based carry-over and forfeiture - covering flexitime, overtime, leave and sick accounts alike.
Flexitime with core and function hours
Flexitime models with or without core hours, plus function-hour windows. Allowed limits are mapped per working-time model, so balances stay within the agreed range.
Overtime with request-approval
Request to approval runs as a state machine, with a four-eyes principle to prevent self-approval. Choice between payout and time off in lieu; rule-based auto-approval up to a defined threshold is available.
Premiums for night, Sunday & holiday work
Premium rates for night, Sunday and public-holiday work can be configured and flow correctly into reporting and the payroll export.
Self-service "my account" view
Employees see their balance with a forecast and can - depending on configuration - request a flex day directly against their credit. Transparency instead of follow-up questions to HR.
Tamper-evident & sealable
A hash-chained audit trail with server timestamps, an undeletable change history, and cryptographically sealable month-end closes that can be verified against the underlying entries.
From clocking in to a clean monthly balance
A team works flexitime with a credit cap of 40 hours. Anyone working beyond that submits an overtime request; the team lead approves it under the four-eyes principle and chooses time off in lieu. The balance updates on a rolling basis, capping kicks in at the cut-off date, and night premiums are calculated in automatically. At month-end, HR seals the close - tamper-proof and verifiable at any time.
Related topics around time tracking
Time and attendance is part of Notory Hora. More on this topic:
Questions on time and attendance
What is the difference between extra hours and overtime?
Extra hours are additional time that can be freely offset through the time account; overtime is approved additional time that is typically payable. Notory Hora keeps the two cleanly separated: overtime runs through a request-approval workflow, while extra hours simply flow into the rolling balance.
Can I have overtime paid out or taken as time off?
Both. For approved overtime, the request lets you choose between payout and time off in lieu; premiums for night, Sunday and public-holiday work can be configured. The full status history is documented without gaps, replacing informal shadow spreadsheets.
How does flexitime capping work?
The time account is a generic accounts engine: for each account type you define a capping amount, its behaviour and a cut-off date, plus rules for carry-over and forfeiture. This lets flexitime, overtime and other accounts all run on the same rolling-balance model.
Is the time account tamper-evident?
Yes. Every entry and correction is written to a hash-chained, undeletable audit trail with the server timestamp as the authority. Month-end closes can be cryptographically sealed and later verified against the underlying entries.
Balances, not shadow spreadsheets
Time and attendance is part of Notory Hora, available as an add-on from Pro. Request a live demo or take a look at the plans.