Product
Approved hours in, payroll-ready data out
Timesheet and payroll integration handles everything between a shift ending and your payroll run — without asking you to change the payroll system you already use.
- Timesheet submitted
- Reviewed and approved
- Payroll-ready export
- Your payroll systemUnchanged
Submission
Hours come from the phone that took the shift
A worker submits their hours right after a shift ends, from the same device they used to apply for and confirm it. There is no separate paper timesheet to fill in or hand over later.
One-tap approval, with variance flagged before it is approved
A manager reviews submitted hours against what was actually booked. If the two do not match, the platform flags the difference before approval — it does not wait until the pay run to surface a discrepancy.
- Booked and submitted hours shown side by side
- A plain match state when they agree
- A flagged state when they do not, with the difference calculated
Approve timesheet
The difference is flagged before approval, not discovered at pay run.
Variance
What counts as a variance, and what happens to one
A flag is a prompt, not a block. Nothing about it stops a pay run — it makes sure a discrepancy is a decision somebody made rather than something that slipped through.
- Submitted hours fall outside the booked window
- A shift booked 7:00 to 15:00 with 16:30 submitted is flagged as 1.5 hours over. It is not rejected — it is surfaced with both figures side by side, so a manager can approve the real hours or query them.
- A shift ends with no submission
- A confirmed shift that passes its end time without a timesheet is flagged as outstanding, so it appears before the pay run rather than as a gap somebody notices afterwards.
- Hours submitted against a cancelled shift
- Flagged rather than silently dropped, because a cancelled shift somebody still worked is a conversation, not a data error.
Who resolves a flagged variance
The manager who owns the booking. They can approve the submitted hours as they stand, adjust them, or leave the timesheet pending while they check with the worker. A pending timesheet stays visible as outstanding rather than disappearing, so it cannot quietly miss a pay run — and it does not hold up the approved timesheets around it.
Export
What a payroll-ready export contains
Approved timesheets export in a format built for handoff to a payroll system — the fields your payroll process already expects, rather than a generic spreadsheet somebody has to reformat first.
- Worker, and the entity or site they worked for
- Approved hours — as approved, not as submitted
- Rate or pay category applying to that shift
- Shift reference, so a line traces back to a booking
- Date and pay period
Described by field rather than by file format on purpose. The exact format is matched to your payroll system during setup, so committing to one here would be wrong for most readers.
Upstream of payroll, not instead of it
Aroha Connect does not replace your payroll platform. It produces the data your payroll process needs and hands it off in the format that platform expects, so the change happens before payroll rather than to it.
Invoicing
Invoices and payroll come from the same approved record
Once a timesheet is approved, an invoice generates from it automatically — built from the same approved hours that feed the payroll export, so the two cannot disagree with each other.
- Approved timesheetSingle source
- Invoice
- Payroll export
This removes a whole category of reconciliation work. When an invoice and a payroll figure are generated from two different records, somebody eventually has to explain why they differ. Steps 4 and 5 of How it Works cover the same path at a lighter level.
Interface images on this page are illustrative layouts, not screenshots of live data.
Bring your payroll export format to the demo
We will show you what an export looks like using the fields your payroll process actually needs.