The timesheets that never arrived

The reported-to-paid reconciliation is precise about the timesheets it has: every submitted hour traced to what payroll paid. But it starts from submitted rows, and a worker who submits nothing has no row. They are not a discrepancy the reconciliation can flag; they are an absence it cannot see, and their hours go unpaid until someone notices at the desk.

Every control that begins with the data present shares this blind spot. Completeness is the one question that must start from the population that should be there, not the rows that are.

Expected equals submitted plus missing, checked by the battery. The six who submitted nothing are the finding, and the reconciliation processed the other 114 without ever noticing they were short a population. Each of the six is named, with a status, so the follow-up is a call, not a census.

Sample values are illustrative, never client data.

Derive the expected population from the schedule fact, left join it to the time entries, and the workers with no entry fall out as the missing list. Run it daily through the approval window, the same rhythm as the pre-deadline control on the reconciliation, and the missing timesheet becomes a nudge on the day rather than a short paycheck after it.

-- expected to submit, with no timesheet for the period: the missing list
SELECT s.worker_key
FROM (SELECT DISTINCT worker_key FROM fct_schedule_day
      WHERE pay_period = '2026-05-B' AND is_hourly) s
LEFT JOIN fct_time_entry t
  ON t.worker_key = s.worker_key AND t.pay_period = '2026-05-B'
WHERE t.worker_key IS NULL
ORDER BY 1

With this control beside the reconciliation, the loop closes: expected equals submitted plus missing, and submitted reconciles to paid. Every hourly worker is either paid correctly or on a named list, and no one falls silently into the gap between.