The failure this prevents
When payroll reads everything logged, a mis-keyed shift, a duplicated entry or a forgotten running timer becomes money. Approval inserts a human who knows the week between the keystroke and the payment, which is the cheapest error check available.
Enforcement, not policy
A written policy that payroll should use approved hours will be broken by the first urgent month end. In Flocci Timesheets payslip generation reads Approved time exclusively at the query layer, so there is no toggle, screen or API shape in which unapproved hours are paid.
What happens to hours that never get approved
They stay unpaid until reviewed, which is the correct incentive: it makes approval somebody’s actual job rather than an aspiration. Rejected entries come back with a reason and can be corrected and resubmitted before the next run.
Retrying a run safely
Pay runs fail for boring reasons. Settlement in Flocci Timesheets is keyed to the run id, so a retried run collapses onto one ledger entry rather than charging twice, and a credit refusal returns the run to Draft with nothing half-produced.
