Why Overtime Goes Missing From Your DTR on Overnight and Extended Shifts

• A fixed DTR window may not capture hours worked beyond a standard shift.
• Time-outs outside the configured window may be treated as missing or linked to the wrong shift, which can lead to wrong absence or undertime tags and missing OT.
• Different schedules, such as overnight, 12-hour, and extended duty shifts, may need different DTR settings.
• Per-schedule Pre-Shift and Post-Shift values give each shift a window suited to its actual hours. In Sprout HR, each value can be set from 1 to 24 hours.
• Setting the window too wide can overlap with the employee’s previous or next shift, so thresholds need to be configured carefully.
• A wider window captures time logs, but it does not approve overtime. OT approval, Labor Code rules, and occupational safety and health (OSH) limits on fatigue still apply.
• HR and payroll teams need accurate time records for a more complete basis for reviewing OT and processing payroll.

Overtime (OT) goes missing from the daily time record (DTR) when an employee’s time-out falls outside the window the timekeeping system uses to match logs to a shift. A single company-wide window works for a standard eight-hour office schedule, but it can drop hours from overnight, 12-hour, and duty-based shifts. The fix is to set the window per schedule, using Pre-Shift and Post-Shift values sized to how long each shift actually runs, without overlapping the next one.

When a time-out falls outside the window assigned to a shift, the system may fail to link it to the right schedule. The employee can then be tagged absent or undertime, basic pay can be deducted in error, and OT can drop out of the payroll run, even though the employee actually worked the hours.

That risk is not limited to a few edge cases. Services made up 62.8% of employed Filipinos in July 2026, and the sub-sectors that added the most workers year on year included accommodation and food service, administrative and support services, and transportation and storage, based on the Philippine Statistics Authority’s July 2026 Labor Force Survey. Overnight, rotating, and extended shifts are common in all three.

One rule has to fit every schedule, and a window sized for an office day is too short for an overnight or extended duty. Companies can have regular office hours alongside graveyard shifts, 12-hour duties, split shifts, and extended field assignments. Using the same DTR window for all of them means the system has to evaluate very different work patterns using the same rule.

In Sprout HR, schedules without custom values fall back to a system default, shown in Sprout’s help guide as two hours before the shift starts and 12 hours after it ends (the default in your environment may differ). That easily covers a 9-to-6 office day. It does not cover a duty that runs well past midnight and into the next morning.

HR then has to go back through the employee’s assigned hours, attendance records, and overtime entries to figure out what happened. It gets even more complicated when employees work across different locations or shifts.

Set Pre-Shift and Post-Shift values on each schedule so the window matches the shift’s real length. Making the company-wide DTR window larger doesn’t always work. A better approach is to set the DTR window based on the hours of each work shift.

With per-shift settings, managers, HR administrators, and super admins can define separate Pre-Shift and Post-Shift values through a Schedule Adjustment in Sprout HR. These determine how far before and after the shift the system will look for time entries. Together, they form what Sprout HR calls the overtime-detection window. Each field accepts a minimum of 1 hour and a maximum of 24 hours, and leaving a field blank applies the system default.

The Post-Shift value is especially useful for extended or overnight work. For example, if a shift ends at 5:00 PM and the Post-Shift Value is set to 17 hours, the system can still evaluate a time-out as late as 10:00 AM the following day as part of that shift. Time that crosses midnight is attributed to that shift day, so a graveyard shift’s hours stay together.

Example: a 5:00 PM shift end with a 7:30 AM time-out

An employee’s scheduled shift ends at 5:00 PM, but an extended duty keeps them on site until 7:30 AM the next day. Under a 12-hour Post-Shift default, the window for that shift closes at 5:00 AM. The 7:30 AM time-out falls outside it, so it isn’t linked to the shift, and the day can show a missing time-out. The overnight hours between 10:00 PM and 6:00 AM, which should carry night shift differential, are affected too. With the Post-Shift Value set to 17 hours, the window runs until 10:00 AM and the 7:30 AM time-out is evaluated as part of that shift.

It gives each shift enough room to capture the hours that belong to it without applying one unnecessarily wide window across the entire workforce.

Per-schedule values currently apply to Normal Shift schedules for monthly, semi-monthly, and daily-paid employees. Schedules on Standard Shift Basis and First Shift Basis keep their existing behavior, and holiday pay rules are unchanged. For setup steps, see Sprout’s Pre- and Post-Shift threshold configuration guide.

Here’s how per-schedule configuration compares with using one fixed window:

Your goal isn’t to make the window as large as possible but to make it appropriate for each schedule.

Wide enough to cover the longest realistic duty for that schedule, but not so wide that it reaches into the employee’s previous or next shift. Making the DTR window too large may extend into an employee’s previous or next scheduled shift. It can be a problem when employees have consecutive or closely scheduled duties. If evaluation windows overlap, the system may have difficulty determining which shift a time entry belongs to.

Sprout HR shows an overlap warning banner when a value is large enough to create that risk, giving administrators a chance to review the settings before saving them. The threshold should give the system enough time to capture actual work hours without extending too far into the next shift. A practical check: the current shift’s end time plus its Post-Shift Value should land before the next shift’s start time minus that shift’s Pre-Shift Value.

Capturing an extended duty accurately is not the same as endorsing it. Sprout’s setup guide reminds employers to make sure employees get adequate rest before saving extended working hours, since prolonged continuous work raises the risk of fatigue and workplace hazards. Employers remain responsible for OSH requirements under Republic Act No. 11058 and its Revised Implementing Rules and Regulations, DOLE Department Order No. 252, Series of 2025.

By payroll cutoff, even a small timekeeping discrepancy can require HR or payroll to check the employee’s schedule, time-in and time-out records, OT approval, and applicable Philippine payroll rules.

It can add extra work, especially for organizations with multiple branches, rotating shifts, logistics teams, healthcare workers, round-the-clock BPO and manufacturing operations, and other employees who work outside standard office hours. Teams still reconciling manual DTRs and spreadsheets feel this most, as Sprout’s guide to DOLE-compliant time tracking explains.

Sprout HR brings employee records, attendance, and timekeeping into one platform, while Sprout Payroll handles payroll processing. When the DTR window is configured correctly, payroll starts with a more complete time record instead of requiring HR or payroll teams to piece together missing hours during cutoff. For a closer look at how cutoff errors turn into compliance issues, watch the on-demand session Getting Payroll Right: Building Resilient Payroll Operations.

For teams managing large volumes of attendance and overtime data, this can translate into less manual checking and more efficient payroll operations. As Mario Ian Pabunan, Finance and HR Manager at Logwin Air + Ocean Philippines Inc., shared:

Read more customer stories here.

Article 87 of the Labor Code requires overtime pay for work beyond eight hours a day**: at least 25% on top of the regular hourly wage on ordinary days, and at least 30% on top of the applicable rate for work beyond eight hours on a rest day or holiday. Article 86** provides a night shift differential of at least 10% of the regular wage for each hour worked between 10:00 PM and 6:00 AM. Exemptions apply, for example to managerial employees and field personnel. See the DOLE-BWC Handbook on Workers’ Statutory Monetary Benefits and Sprout’s guides to computing overtime pay and night differential.

The Labor Code also counts as hours worked all time an employee is required to be on duty, or is permitted to work (Article 84). If the employee actually worked the hours, a log the system failed to capture still needs to be corrected, not dropped.

That makes accurate time records important. If a time entry is not properly linked to the employee’s shift, payroll may first need to resolve the attendance record before applying the appropriate OT or night shift treatment.

The DTR window doesn’t determine whether overtime is payable on its own. It determines which time entries are evaluated against the schedule. Recovered hours still go through your OT approval workflow in Sprout HR.

Connect them through an API so time logs reach Sprout without manual transfers. DTR settings are only one part of the timekeeping process. Managing attendance can also get complicated when data has to be moved manually between systems.

Sprout’s Time and Attendance API supports clock-in and clock-out data from external systems, such as biometric devices, along with employee schedules, daily logs, audited attendance records, and company timekeeping rules like grace periods and overtime. It allows organizations to connect their existing timekeeping systems without having to transfer attendance data manually. See integration use cases for examples.

If your team is using Sprout HR and Payroll, employee and attendance data can also stay within the same platform, which reduces manual steps before payroll.

Timekeeping discrepancies often lead to the same questions from employees: Why is my OT missing? Why was I marked undertime? Did my late time-out register?

Sidekick, Sprout’s AI companion built into Sprout HR, gives employees and managers role-aware access to schedules, leave balances, and attendance records, along with answers to everyday HR, payroll, and time-related questions. It doesn’t replace HR review or OT approval, but it can help reduce routine questions when the underlying records are already in the system. 

For more on how Filipino teams are adopting AI at work, see Sprout’s State of HR 2026 report, built on insights from more than 3,500 employees.

1. List the schedules whose shifts regularly end after midnight or run longer than the default window allows.
2. Pull recent attendance reports and flag days with missing time-outs, absences, or undertime tags for employees who were on duty.
3. For each affected schedule, set a Post-Shift Value that covers the longest realistic duty, and a Pre-Shift Value for early clock-ins.
4. Review the overlap warning and confirm each window closes before the next shift’s window opens.
5. Make sure OT applications are filed and approved for recovered hours, and that night shift hours are tagged correctly.
6. Check rest periods for anyone on extended duty so schedules stay within OSH requirements.

If your workforce includes overnight shifts, extended duties, or other non-standard schedules, getting timekeeping right can make payroll cutoff much easier. Sprout HR helps manage employee schedules, attendance, and time records, while Sprout Payroll uses those records as part of the payroll process.

Book a meeting with Sprout to discuss your organization’s timekeeping and payroll requirements. Stay tuned for Sprout’s upcoming overtime calculator!

A DTR window is the period around a scheduled shift when the system looks for and evaluates time-in and time-out records. In Sprout HR, it is called the overtime-detection window and is set with Pre-Shift and Post-Shift values.

Usually because the time-out fell outside the shift’s DTR window, so the system didn’t link it to that shift. It can also mean the OT application hasn’t been filed or approved yet. Check the schedule’s Post-Shift Value first, then the OT approval.

If an employee clocks out after the DTR window closes, the system may not associate the time entry with the correct shift. The employee may be tagged absent or undertime for hours they worked, and HR may then need to review the record manually.

Not necessarily. Different shifts may need different settings. Making the window too large can also cause it to overlap with another scheduled shift.

The Post-Shift Value sets how long after a scheduled shift ends the system continues to evaluate time entries. A longer value can be useful for extended or overnight shifts. In Sprout HR, it can be set from 1 to 24 hours.

No. It applies to Normal Shift schedules for monthly, semi-monthly, and daily-paid employees. Standard Shift Basis, First Shift Basis, and holiday pay computation follow their existing rules.

Managers, HR administrators, and super admins, through a Schedule Adjustment on the employee’s work schedule.

Start with extended, overnight, split, and consecutive shifts. These are more likely to have time entries that fall outside a standard DTR window.

Yes. Sprout’s Time and Attendance API supports clock-in and clock-out data from external systems, as well as access to schedules and attendance records.

If the employee was required to be on duty or was permitted to work, yes. Article 84 of the Labor Code counts that time as hours worked, so a missed log should be corrected rather than left out of payroll.