Set up company
Legal entity, jurisdictions, tax accounts, pay schedules, bank rails, and reporting preferences.
Full-service payroll, built for review
Runbook brings payroll runs, taxes, approvals, corrections, filings, payments, and accounting into one reviewable record. Your team can handle payday and answer questions later without rebuilding the story from exports, screenshots, and support tickets.
Runbook connects the everyday payroll work—people, pay, taxes, approvals, payments, filings, and reports—so every handoff starts from the same record.
Legal entity, jurisdictions, tax accounts, pay schedules, bank rails, and reporting preferences.
Employees, contractors, pay rates, tax elections, direct deposit, deductions, reimbursements, and documents.
Hours, PTO, tips, bonuses, commissions, HR changes, benefits, off-cycle items, prior-provider YTD, and approvals.
Gross pay, net pay, employee taxes, employer taxes, deductions, benefits, reimbursements, and cash required.
See what changed, clear exceptions, confirm funding, and approve the run before payments and filings move forward.
Payments, tax work, accounting entries, corrections, reports, and supporting records stay connected to the run.
One ordinary payday
This walkthrough uses the test-backed Marlow Goods demo to show one payroll moving from preparation to employee explanation, approval, advisor review, correction, and independent verification.
Who changed? Name the affected workers and the recorded reason. What will leave the bank? Show net pay, taxes, and deductions separately. When? Put the planned debit date beside payday. What is unresolved? Keep every evidence or funding hold visible. What will each worker see? Gross pay, taxes, deductions, take-home pay, and the reason for any change.
Hours, pay rates, elections, work locations, and the governing rules form the prepared run. Missing support stays visible before approval.
Can I act? Yes—review the recorded facts and resolve the open evidence hold.
The statement connects take-home pay to hours, rate, taxes, deductions, and employer-provided value. A later question starts from the same record.
Why is it true? Every amount keeps its source sentence and calculation lineage.
Approval records who accepted the run and what the system knew at that moment. It does not pretend that payment settlement has already happened.
What needs attention? The approval boundary and any unsettled payment or filing work remain explicit.
The advisor rollforward carries filed amounts, liabilities, evidence, and open next-run items without asking someone to rebuild the payroll from a stack of exports.
Can I close the books? The rollforward shows the amount, its status, and the record that supports it.
A $26.00 hourly rate was effective during Run 9 but recorded after approval. Runbook preserves the filed run, recomputes from the later fact, and carries the delta forward.
What changed? The engine derives a $58.50 gross correction; nobody types an adjustment to force the answer.
The sample packet connects facts, rules, the derived correction, and the reconciled notice answer. A Quittance is Runbook’s sealed, independently verifiable payroll proof record: the facts, rules, calculation, approval, correction history, and available external evidence behind a payroll. It can be checked in the browser without a Runbook account.
Does the answer stand up? The notice claim and deposited correction both equal $15.14, leaving a $0.00 residual.
Owners, payroll teams, HR staff, workers, accountants, and support teams see the work they need without creating competing versions of payroll.
Cash required, open liabilities, approval deadline, exposure, tax calendar, and what remains unsettled.
Worker deltas, exceptions, funding, tax deposits, filing queue, approvals, and correction history.
W-4, I-9, direct deposit, documents, compensation changes, job status, locations, and terminations.
Paystub, YTD, tax forms, direct deposit, withholding elections, reimbursements, and why-pay-changed notes.
Payroll journal, liability rollforward, filing receipts, exports, notice packets, and verification trail.
Returned ACH, missed payday, worker dispute, filing rejection, tax notice, and amendment workflows.
Concept views show how each role can work from the same payroll record. See current product availability.
Accrued liability report
A payroll register tells you what ran. The liability report shows what the business accrued, what was settled, what remains open, and which evidence supports each line when the answer is questioned.
Illustrative display. Live amounts will be calculated from the recorded payroll facts.
This is the customer moment where Runbook feels different: the system assembles the run, liability, settlement, filing, correction, and evidence trail instead of sending the owner to hunt through exports.
Example notice
The owner does not need to know where every receipt lives. Runbook identifies the affected period, pulls the payroll record, and shows what was accrued, paid, filed, corrected, and still open.
Runbook is designed to bring routine payroll, tax work, worker records, accounting, corrections, and support into one service. See current availability.
Regular payroll, off-cycle checks, bonuses, contractor-only runs, final pay, and multiple schedules.
Federal, state, and local withholding, employer taxes, deposits, quarterly and annual filings, W-2s, and 1099s.
Missing-data checks, change flags, reminders, approval rules, and clear stop conditions.
Direct deposit, checks, contractor payments, return handling, status visibility, and worker communication.
Paystubs, W-4 changes, direct deposit, personal information, YTD totals, documents, and pay explanations.
Employee onboarding, I-9 and W-4 collection, compensation changes, locations, roles, and terminations.
Benefit elections, payroll deductions, employer contributions, remittances, and worker-facing explanations.
Hours, PTO, tips, job codes, approvals, imports, and inconsistency checks before payroll runs.
Payroll journals, liability rollforwards, class and location mapping, reconciliation exports, and advisor review.
Wrong-pay questions, agency notices, amendments, filing issues, and preserved correction history.
Missed payroll, returned payments, worker questions, filing rejections, and escalation workflows.
Role-based access, audit history, monitored operations, recovery procedures, and provider review.
Pay registers, payroll journals, liability reports, period totals, worker stubs, accounting exports, and notice packets.
Source facts, rule sources, calculations, approvals, corrections, and verification stay connected.
Trust and security model
Trust cannot be only cryptographic proof. The product must protect worker data, bank details, tax identifiers, approvals, agent proposals, and provider credentials with explicit controls.
See security postureMid-year switching is not just import convenience. It is accrued payroll liability continuity: wage bases, local taxes, W-2 continuity, and prior-provider facts that need a defensible record.
Real payroll problems come with messy support files: timecards, EFTPS confirmations, provider letters, worker comp audits, duplicate PDFs, notices, and year-end records. Runbook turns those into organized payroll evidence.
Upload timecards, prior-provider reports, payment confirmations, filings, notices, worker comp documents, and support files to the relevant company, worker, period, or run.
Identify document type, period, jurisdiction, tax type, provider, duplicate files, and missing support without exposing sensitive data publicly.
Connect each file to the run, accrued liability, payment, filing, correction, notice, or provider switch it supports.
Create advisor-ready packets for agency notices, worker questions, audits, mid-year switching, and year-end reconciliation.
Store sensitive files privately while a reviewer receives only the minimum information needed to check the record.
Late documents and corrections add new events instead of overwriting the original payroll record.
Explore a test-backed example of how Runbook connects a payroll result to the facts, correction history, and evidence behind it.
Explore proof demo