Full-service payroll, built for review
Runbook is being built to connect payroll runs, taxes, approvals, corrections, filings, payments, and accounting in one reviewable record. Start with the implemented screens below to see how a payday can explain itself.
Fictional payroll records. No money moves and no returns are filed.
Inside the product
Actual screens from the interactive Runbook Demo Co. example, captured October 4, 2026. Every amount comes from fictional payroll facts and the calculation engine. This is a separate example from the Marlow Goods record below.
01 / Payroll review
See the approved record, the people in it, and each paycheck’s change. Open a paycheck to see every line beside the recorded facts that produced it, or expand cash requirements to see where payroll money belongs and which timing facts are missing.
Reviewing the demo does not approve payroll or confirm payment.
Explore payroll review →
02 / Payday Statement
Open a worker’s statement from payroll review. Compare take-home pay with the prior payday, inspect withholding and retirement contributions, and open the legal paystub.
This is an employer preview. Viewing it does not publish or deliver a worker document.
Open the demo, then View Payday Statement →
03 / Payroll Close
The Close rehearsal separates approval, funding, payments, filings, and accounting. Choose a failed-funding scenario to see the hold, the responsible role, and the next recovery step, or follow a late opening-wage correction from discovery to a refund settled on the simulated rail.
All receipts and outcomes in this rehearsal are simulated. They do not prove a payment or filing.
Explore Close rehearsal →
Your worker workspace
Start with your pay and documents. Make a private plan, find work and tax help, or download the data available to your account. The workspace is deployed for invited accounts; live customer payroll is not open.
Find released statements and their explanations. If none are available, the workspace says so and gives you a way to check again.
Keep a private plan for bills and goals between paydays. Saved drafts stay in place as you move between sections.
Find a next step for work or tax changes, including personal support after a recorded employment end. These tools do not submit a claim or file a return.
Keep retirement and account tools together. Live investment linking and provider services remain unavailable.
See which account is signed in, manage available security controls, and prepare your own data export.
Take your records with you
In Account & Security, choose Export Your Data, then Prepare My Export. Review the included and unavailable sections before choosing Download My Data or Download Available Data.
The JSON file contains data accessible to your signed-in account at download time. It includes saved records rather than unsaved entries, and is not a complete archive of every record Runbook retains. Downloading does not change your records or send them to an employer or agency.
Payroll and the books
Pay is part of running the business. Runbook is being built to keep payroll costs, amounts still owed, and later corrections connected to the payday that created them.
The payroll walkthrough separates worker take-home pay from taxes, deductions, and employer cost. Follow an amount back to the facts behind it.
The Close rehearsal keeps approval, funding, payments, filings, and accounting separate. Its simulated receipts show why approval alone does not mean the work is finished.
The sample payroll record preserves the original run and explains the change when a late fact arrives, so the next person can follow the history. The Close rehearsal carries one late correction through its derived consequences, recorded human answers, Form 941-X projection, adjusting entry, and simulated refund.
Explore these ideas with fictional data today. The Close rehearsal does not move money, file taxes, or post to an external accounting system.
The complete service is being built around people, pay, taxes, approvals, payments, filings, and reports. These are the intended lifecycle steps; payment and filing services are not yet available.
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.
The intended notice workflow brings the run, liability, settlement, filing, and correction history together. This is a planned service workflow; Runbook is not accepting paid notice work or sensitive evidence packets.
Example notice
The owner does not need to know where every receipt lives. The planned workflow identifies the affected period and brings together 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. See the deployed worker workspace and its current boundaries.
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.
The intended evidence workflow connects timecards, payment confirmations, provider letters, notices, and year-end records to the payroll they support. The steps below describe the planned service, not an invitation to upload sensitive records.
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 the interactive demo with fictional records. No account, payroll files, or bank details needed.
Open the interactive demo