How hours land in the right month

Work weeks start on Monday, but months don't. Atteny resolves that by counting every shift's hours in the month the work actually happened — not in the month the week began.

Two rules do the work:

1. Work-date attribution. Each shift's regular and overtime hours count in the month of its own work date. When a Monday-start week straddles the month end, overtime lands in the month it was worked, not smeared across both.
2. Month-boundary split. A shift that crosses midnight into a new calendar month is split at midnight, so each part counts in its own month. Ordinary overnight shifts in the middle of a month are never split.

An example

A closing shift runs 22:00 on 30 June to 06:00 on 1 July — 8 hours, no break. Atteny books 2 hours in June and 6 hours in July. If the shift had 2 hours of breaks, the 6 worked hours are shared in the same 2:6 proportion — 1.5 in June, 4.5 in July.

In Timesheets → Records that shift appears as two rows, each with a small 1/2 and 2/2 badge beside the date. Only the first row can be edited or approved; acting on it applies to the whole shift.

Why it matters

Because each shift is counted where it was worked, the hours you add up in Timesheets match the hours Payroll uses for that month's estimated gross. Your team's own monthly figures follow the same rule.

An older calculation spread a straddling week's hours across both months by how many of its seven days fell in each. It isn't offered in Settings, and every new company uses work-date attribution.

Changing the setting

Go to Settings → Payroll → Overnight shifts. Split at month boundary is on by default. Turn it off and a boundary-crossing shift counts entirely in its start month, as one row.