Midnight is not always the end of the shift
A shift beginning at 22:00 and ending at 06:00 crosses a calendar boundary but can represent one working period. Splitting its punches by their calendar dates can leave an apparent missing checkout on one date and missing check-in on the next.
Attendify uses configured local-time shift windows to associate relevant punches with a work date. Matching overnight events belong to the date the scheduled shift started. Events outside the relevant windows can become unscheduled work rather than disappearing.
Walk through the arithmetic
Illustrative example: a shift starts at 22:00 on September 6 and ends at 06:00 on September 7, in one site time zone without a clock change during the interval. The duration is eight hours.
Scroll the table sideways to read all columns.
| Item | Result under this example’s configured rule |
|---|---|
| Work date | September 6 |
| Worked time | 480 minutes |
| Configured unpaid break | 30 minutes |
| Calculated paid time | 450 minutes, or 7.5 hours |
The example is arithmetic, not a legal instruction to deduct a break. Clock changes and jurisdiction-specific pay rules need separate evaluation.
Investigate missing endpoints
If the 06:00 checkout is absent, the engine leaves an open segment and an exception. A supervisor should investigate whether the event is pending, rejected or never captured. Do not enter the scheduled finish automatically just to complete the pair.
A reasoned correction can supply supported missing time. After application, recheck work-date attribution, the break and any remaining exceptions. If a payroll file has already been imported, follow the receiver’s correction process.
Check the receiving system’s date semantics
An exported work date, a UTC timestamp and a local calendar date are different representations. The receiver may use them differently. Test overnight rows in the actual mapping rather than assuming a familiar Date column has the same meaning.
The named export formats also differ in which timestamps and quantities they supply. Review integration layouts and reconcile calculated hours after transformation.
Include difficult cases in the pilot
Test missing checkout, early arrival, late departure, adjacent shifts, a date-range boundary and any daylight-saving transition relevant to the site. A happy-path eight-hour example is useful but does not prove every timezone or policy scenario.
See timesheet behavior and work-rule precedence for the configuration behind the result.