Approved run
The payroll period is sealed with the facts and rules known at approval time.
Corrections
Payroll gets questioned because reality arrives late: a missed timecard, a retro raise, a W-4 change, a garnishment, a prior-provider import, or an agency notice. Runbook treats correction as core payroll, not an afterthought.
The original run stays intact. The new fact creates a traceable delta.
This is the signature product experience that should make Runbook feel different from normal payroll software.
The payroll period is sealed with the facts and rules known at approval time.
A source event records what changed, when it was known, and who supplied it.
The engine recomputes the affected period under the correct knowledge horizon.
Runbook shows the exact employee, employer, tax, deduction, and liability difference.
The delta is proposed for the next run or amendment workflow with human approval.
The correction record travels with payroll reports, notice packets, and the Quittance.
These are the pages and demos worth building next.
A retroactive rate change reprices wages and taxes without overwriting the approved check.
Additional hours arrive after payday; the next run carries the corrected gross, taxes, and net.
A legal order changes withholding and needs evidence for both worker support and compliance review.
The effective date, old election, new election, and affected checks stay visible.
Prior-provider totals become founding facts, and later corrections show exactly what changed.
Runbook assembles the payroll, liability, payment, rule, and correction evidence into a response packet.
The buyer does not need cryptographic theater. They need an answer that survives review.
That is the core product wedge.
Request corrections demo