Use cases / Payroll inputs
Run payroll from what was confirmed, not from an email.
A pay-period pack asks for hours, overtime, absences and changes in a table with one row per employee. Whoever knows the hours fills it in: a client’s office manager if you run payroll for other businesses, a site manager if you run your own. They save a draft and submit with a statement they are confirming. You see the totals, export the CSV, and accept it or send it back with a note.
September hours
Ardley Foods · one row per employee
Amira Begum
160 hours · started 2 June
Jess Whitfield
72 hours · 4.5 overtime
Tom Ellis
38.5 hours · 3 days absent
A table, not a thread
Hours are numbers in a column, not sentences in an email. Required cells are required before submission. A starter who is missing from the list gets added as a row. Totals are worked out for you.
- Presets for payroll hours, starters and leavers, and a stock count; or your own columns
- Drafts show as “in progress”; submitted tables as “submitted” with who approved them and when
- Download as CSV for your payroll software
September hours, submitted
Ardley Foods · totals across three people
Hours
Amira 160 · Jess 72 · Tom 38.5
Overtime
Jess 4.5
Absence
Tom 3
The monthly pack
The “Monthly payroll inputs” template starts a pack with the hours table, starters and leavers, new starter documents and the payroll summary to approve at the end.
Sent back, not re-typed
“Jess worked 76 hours on the rota, not 72.” The request goes back as needs correction; the client edits the one cell and submits again.
Reminders that stop
Schedule a reminder to the person who fills the table in. It lists only what is outstanding and ends itself once the pack is done.
Send next month’s pack from the template.
Free for 14 days, no card. Hours in a table, approved before you run payroll.