Overtime, week against pay period

Overtime thresholds are weekly. Payroll is by period. Boundary weeks belong to both, and the delivered path leaves the split to whoever owns the spreadsheet, practitioner-reported. Day grain makes the boundary a non-event.

RuleCompute overtime on weeks from day-grain hours, then map days to periods for payroll. Two rollups of one fact, never a conversion.

Neverapportion a boundary week by ratio. The days are known; splitting by fraction invents hours no one worked on either side.

Two clocks, one fact. At day grain the boundary week is arithmetic instead of a spreadsheet argument.

◆ The matrix, May 2026overtime hours by department and week, sums shown.

Department	w/e May 8	w/e May 15	w/e May 22	w/e May 29	Total
Sales	96	88	102	94	380
Technology Delivery	132	140	128	135	535
Support	61	58	66	59	244
Total	289	286	296	288	1,159

Rows and columns sum, checked by the battery, and the departments are the same three the labor cost report prices, so overtime cost lands beside overtime hours in one review. Technology Delivery carrying 46 percent of the overtime on 32 percent of the population is the finding this table exists to surface. Sample values are illustrative, never client data.

◆ The boundary, handled by graina week in two periods, without apportioning.

When a week crosses a period boundary, its days are already tagged with both keys on the double calendar: the weekly threshold computes on the week’s seven days, and payroll takes exactly the days inside its period. Nothing is apportioned, nothing is estimated, and the same hours sum correctly in both views because they are the same rows.

The delivered path, practitioners report, has no source holding both calendars at once, which is why this table usually lives in a spreadsheet.

◆ The queryone fact, two rollups.

Schema and joins for everything on this page live on the time-tracking star.

Use case

Problem

Weekly overtime and period payroll never align, so boundary weeks are split by hand and the split is nobody’s system of record.

What we build

Overtime computed on weeks from day-grain rows, with payroll reading the same rows by period key.

What you get

One overtime number that is right in both calendars, by department, beside the cost it drives.

Who splits your boundary weeks today, and how?

We ship the day-grain overtime that never needs splitting.

Talk to us

Terms on this page

battery: The automated set of checks, including the crossfoot arithmetic, run on every build of this catalog.
weekly threshold: The hours level, per week, where overtime begins.
boundary week: A week split across two pay periods.
apportioning: Splitting a week’s hours by ratio. The workaround day grain retires.
premium hours: Hours paid above base: overtime, double time.
period key: The pay period each day maps to on the calendar.
week key: The week each day maps to. Both ride on every row.
matrix: Departments by weeks, rows and columns summing.