Timesheets & payroll

Stop re-typing timesheets into your payroll system

Staff fill in their hours on a form that looks like the paper sheet you use today. Supervisors and finance sign off on screen. Payroll comes out as one file per pay period — instead of thirty signed sheets someone re-keys by hand.

The same pay run, without the re-typing

Today
With Heion
Submitting hours
Printed, signed, handed in or photographed
Filled in on screen, submitted in one tap
Checking
Thirty sheets read by eye
Rules flag the odd ones; the rest just pass
Approval
Wet signature, chased in person
Two-step sign-off, on the record
Payroll entry
Re-typed line by line
One file for the pay run
Last quarter's sheet
A folder — if it was filed
Search, reopen, re-export

What the system does

  • It is your form, on screen

    Job number, client, contract, work description and the day-by-day labour table — laid out like the sheet your crew fills in today. There is no new format to learn.

  • The hours add themselves up

    Enter start and finish; total hours and the day of the week fill in on their own. One click lays out every day of the period. Leave is picked from a list, not written in longhand.

  • Mistakes are caught at entry

    A 25-hour day or a missing finish time is blocked before the sheet is submitted. Overtime beyond your policy, or leave beyond a balance, is flagged to the approver — not discovered on pay day.

  • Two-step approval, on the record

    Supervisor first, then finance. The chain is set by admin, so nobody picks their own approver and nobody approves their own sheet. Approvers can work from an emailed link or straight from their queue.

  • Corrections cannot slip past an approver

    Changing an already-submitted sheet means withdrawing it first, which clears any approval already given — an approval only ever applies to the version that was approved. Approved sheets are frozen; only an admin can void one, with a reason.

  • Three exports, deliberately separate

    A single timesheet in your paper layout; everyone's hours day by day for checking and filing; and the payroll file — approved hours only, one pay period, so nobody is paid twice or paid on hours nobody signed off.

Who it's for

Any company where staff still write their hours on paper or in a spreadsheet and someone re-types them — site and construction work, field service, shift rosters, contractors. Weekly, fortnightly and monthly pay cycles are a setting, not a rebuild.

Do we have to change accounting software?

No. This sits in front of your payroll: it collects and approves the hours, then hands over a clean file. Connecting directly to a payroll system such as Xero depends on your region and plan, so we scope that with you rather than promise it up front.

Everything is on the record

Every submission, withdrawal, approval, deletion and export is logged with who and when. Nothing truly disappears — a removed sheet drops out of every list and export but stays in the database for an audit or a dispute.

How we get there

  1. 01

    Show us your current sheet

    A short call and a copy of the timesheet you use today. That form is the specification — we do not ask you to change how you work first.

  2. 02

    See it as your own form

    We rebuild your sheet in the system and hand you a working version to click through: your job numbers, your pay period, your approval chain.

  3. 03

    Run one period in parallel

    Your team enters one real pay period in the system while payroll still runs the usual way. You compare the two, and only then switch.

  4. 04

    Go live, then extend

    Roll it out to everyone. Direct payroll integration, cost-per-job reporting and the rest come after — once the basics are earning their keep.

Let's talk

Tell us where the time goes.

Describe the manual work, the messy data, or the AI idea you have in mind. We reply to every serious enquiry — usually within a couple of business days.

Or email us directly at [email protected]

We'll only use your details to reply to this enquiry.