Getting Overtime Pay Calculation Right in HR Tech

Why overtime is the line item everyone disputes

Overtime calculation is the tensest moment of the payroll cycle for any company running a field workforce. An employee says "I stayed late that day," and HR looks at a spreadsheet without quite remembering where those hours came from. A paper sign-in sheet or a single turnstile swipe tells you who entered the building, not who was actually working and for how long. That gap is the single most common source of disagreement between what lands on a payslip and what an employee expected to see.

This piece walks through the legal framework around overtime in Turkey, how companies move from raw timesheets to automatic calculation, and the mistakes that show up most often when setting this up in a system.

The legal baseline: the 45-hour weekly limit and the premium rate

Under Article 41 of Turkish Labour Law No. 4857, the standard weekly working time is 45 hours. Anything worked beyond that in a week counts as overtime and must be paid at the normal hourly rate plus a 50% premium. Where the parties have agreed on a weekly working time below 45 hours, extra hours worked up to that 45-hour mark fall into a separate category — "extended-hours work" — paid at a 25% premium instead. Lumping these two together under one line item is a common payroll mistake.

The law also caps annual overtime at 270 hours and gives employees the option to take paid time off instead of overtime pay (1 hour and 30 minutes of free time for each hour of overtime worked). That choice has to be offered to the employee in writing and recorded; without a written record, an employer is left without proof if a wage dispute ends up in court. If your company has its own collective agreement or individual contract terms, confirm the calculation with your accountant or legal counsel before configuring it — this article isn't legal advice.

What feeds the calculation: a timesheet nobody can dispute

Getting overtime right is less a legal question than a data question. Knowing the right premium rate doesn't help if there's no reliable answer to "how many hours did this person actually work that day." Card swipes, paper sign-in sheets, or a "clocking in/out" message in a group chat all share the same flaw: they're entered by hand, and anything entered by hand is open to a later "that's not what happened" dispute.

In HR-Tech, timesheets are generated automatically on the server the moment an employee enters or leaves a site boundary — nobody writes down a time, nobody swipes a card. Every night, the previous day's total hours, first entry and last exit are calculated, and because the evaluation happens server-side rather than on the phone, the record is independent of the device and can't be padded after the fact. Behind that automatic generation sits one precondition: site boundaries drawn accurately on the map. If a boundary is drawn wrong, the entry and exit record is wrong too, and the overtime calculation is broken from the start.

Working hours and the holiday calendar: two prerequisites

For the system to tell overtime apart from regular work, two settings need to be defined up front: working hours and the public holiday calendar. In HR-Tech, both live on the same settings screen. Without defined working hours, the system has no way to separate regular time from overtime; without an up-to-date holiday calendar, work done on a public holiday gets calculated as an ordinary day and the extra day's wage the law requires never enters the calculation at all.

Tracking the 45-hour weekly limit also depends on which day the week is defined to start on — Monday for everyone, or something different per employee. This matters especially for shift-based teams: an inconsistent week-start setting can split one week's hours across two calendar weeks by mistake, quietly understating overtime.

Getting it to payroll: tagged data, a separate line item

Once the timesheet engine labels a day as "regular," "overtime," or "holiday work," that label has to survive the trip to payroll or an ERP system intact. Otherwise the accurate data HR produced turns back into a table the accounting team has to manually re-sort, and the time the automation saved gets spent again downstream.

That handoff typically happens one of two ways: a signed webhook notification fired the moment the record is created, or a read-only REST API pulled periodically at period end. We covered the tradeoffs between webhooks and APIs in an earlier piece; for a recurring, amount-affecting line item like overtime, which method you pick decides whether payroll has to re-tag these records by hand every month.

Setting it up: the steps worth following

1. Define working hours separately per branch or shift. A single national schedule rarely fits every branch; night-shift locations need their own start and end times.
2. Keep the holiday calendar current. Religious holiday dates shift every year on the Gregorian calendar, so entering the calendar once and forgetting it means next year's holiday work gets costed as a regular day.
3. Confirm the premium rates with your accountant. Make sure the 50% (overtime) and 25% (extended-hours work) rates are applied to the right cases before they're reflected in the system.
4. Record the time-off-in-lieu choice in writing. Capture which employees opted for paid time off instead of overtime pay, and verify that choice flows to their leave balance, not their payslip.
5. Cross-check against a sample payslip after the first month. Comparing the system's overtime total against a hand-calculated example is the most practical way to catch a setup mistake before it goes live.

Mistakes worth watching for

• Merging the 50% and 25% premiums into one line item. Overtime and extended-hours work rest on different legal grounds; reporting them under the same label causes problems in a payroll audit.
• Applying one working-hours template company-wide. Night shifts, part-time arrangements and flexible schedules each need their own definition.
• Rolling into a new year without updating the holiday calendar. As we detailed in setting up the public holiday calendar, this gap affects both timesheets and overtime calculation directly.
• Taking the time-off-in-lieu choice verbally. A preference recorded without anything in writing weakens the employer's position in any later dispute.
• Not tracking the 270-hour annual cap. Without an alert as employees approach that limit, months can pass before anyone notices the overrun.

In closing

Getting overtime right has less to do with knowing the premium rate than with whether a reliable timesheet sits underneath it. In a system with accurately drawn site boundaries and an up-to-date schedule and holiday calendar, overtime stops being a number argued over at month end and becomes a record that accumulates daily and holds up to scrutiny.

In HR-Tech's field-tracking HR platform, timesheets are generated automatically and overtime is calculated on its own from working hours and the holiday calendar; you can take a closer look on the HR-Tech product page. If you'd like to walk through your current overtime process together, reach out via our contact page.