Maintenance on a rest day
Planned downtime maintenance happens on Sunday. Those hours separate out at the weekly rest rate, and the maintenance team’s cost is visible apart from the line’s.
Raw records from attendance merge with the roster and approved leave to become a timesheet. Overtime, weekly rest days and night work are each calculated at their own premium rate.
What this runs on today

Timesheets and overtime
It all comes together in one module.
Entered from the same screen, tracked from the same place.
The three situations we run into most often. If one of them sounds familiar, we have something to talk about.
Card reader exports, leave lists and the overtime ledger all arrive separately, and someone tries to merge them into one spreadsheet.
Weekly rest days, public holidays and night work are paid at different rates; which hour falls into which rate becomes an argument.
What the overtime actually cost is only learned once payroll closes, when there is no chance left to act on it.
Every item is a real screen or flow in the product; we walk through them one by one in the demo.
Clock-in records, the shift roster and approved leave combine into daily and monthly timesheets.
Overtime, extra hours, weekly rest days, public holidays and night work are calculated separately under Turkish Labour Law No. 4857.
Employees approaching the annual overtime cap are flagged during the period, not after it.
Overtime is requested and approved in advance; hours worked without approval are shown separately on the timesheet.
Where overtime is settled in time rather than pay, the hours are added to the leave balance and tracked there.
Hours and estimated cost are followed by department and line before the month closes.
Once it is set up, every period runs in the same order, and most of the steps happen on their own.
Clock-in and clock-out movements land in the system daily from attendance.
The roster and approved leave are applied; missing and excess hours are flagged.
Hour types are separated, premium rates and statutory limits are calculated.
A manager reviews the variances and approves; the timesheet reaches payroll untouched by hand.
The same data is entered once. What this module takes in and produces is below — you do no extra work to move data between modules.
Takes the data in once and shares the same record with the other modules.
Not promises with numbers, but real setups. Let us go into the one closest to yours in the demo.
Planned downtime maintenance happens on Sunday. Those hours separate out at the weekly rest rate, and the maintenance team’s cost is visible apart from the line’s.
Overtime rises in the busy period. Employees nearing the annual cap are flagged during the period, and the roster distributes hours accordingly.
Hours worked over a public holiday are collected under their own code; one report shows which branch generated how much holiday time.
A demo is not a presentation: we build your scenario and run it on screen. You leave with a written proposal covering scope and timeline.