Blog Industry

Costing labour to the job

5 min read

In a field operation, a crew’s hours are a cost of the jobs they worked. Getting that right on the payroll is a matter of where the division on each cost line comes from. One invented crew member’s fortnight, followed to the export file, shows why an allocation made after payroll cannot be reproduced next quarter.

Maintained by the TriblockHR Compliance Team. Updated 2 October 2026. No statutory figure is stated here; every amount and percentage is invented.

Why the desk is the wrong default

In an office business, a person’s cost belongs to the department they sit in. In a field business, nobody sits anywhere. An electrician employed by the installations team may spend half a fortnight on maintenance call-outs. A technician may be lent to one large contract for three months. If their pay is charged to the department on their record, the cost lands where they were dispatched from, away from where they worked.

That matters because field businesses price and review work job by job. A maintenance contract that looks profitable because half its labour is charged to installations is not profitable. The cost has to follow the work.

In TriblockHR, a site is a division: latitude, longitude, map address, a geofence radius in metres and a GL code. There is no separate locations table, so eleven sites are eleven divisions. Everything below sits on top of that.

Division, department and island

The accounting export splits payroll cost three ways, and every line carries its GL code:

  1. By division. Each site is a division with its own GL code, so the labour at each one arrives on its own lines.
  2. By department. Installations and maintenance are separable within a site, so a contract’s labour is not buried in a site total.
  3. By island. For an operation working across more than one island, that is a dimension of its own.

The part that makes the cost follow the work is where the division comes from. For the pay types you choose, it is taken from the timesheet line. Hours booked at a site carry that site’s division into the export, so the labour lands against the work.

Pay types where that is not wanted keep the employee’s own division, which is usually right for salaried office staff. The payroll page covers the run the export comes out of.

One fortnight, resolved

Take an invented electrical contractor, Bright Current Services, and one of its electricians, Marcus. He is on the books at the Nassau depot, which is where his employee record puts him.

Week one. Marcus works at the depot’s own installations all week. His timesheet lines carry the depot’s division, and the record agrees with them.

Week two. A maintenance contract at the Freeport site is short-handed, and Marcus spends most of the week there. His week-two timesheet lines carry Freeport’s division.

Across the fortnight his timesheets show 70 hours: 42 at Nassau and 28 at Freeport. Because hourly pay is one of the pay types set to take its division from the timesheet line, the export splits his gross the same way. His invented gross is $2,100:

  • Nassau depot: 42 hours, $1,260, on the depot’s GL code;
  • Freeport site: 28 hours, $840, on the Freeport GL code.

Nobody moved that $840 afterwards, and nobody had to know it needed moving. The hours were recorded at Freeport, so the cost went to Freeport.

Had his employee record governed instead, the whole $2,100 would have landed on Nassau, and the Freeport maintenance contract would have looked more profitable than it was — which is the error this exists to prevent, and the one a wage total by employee cannot express at all.

Compare the spreadsheet approach. After each run, someone in finance takes the payroll total and allocates it to jobs in a workbook, using whatever rule they remember that month. In October, when the client queries June’s labour charge, nobody can say exactly how June was split. The workbook has been reused, the rule has changed, and the person who did it may have moved on. An allocation made after payroll is a calculation nobody can reproduce. One made inside the run, off the timesheet lines, is a record.

The export

The run leaves TriblockHR as an export file carrying the GL codes, with a Sage-ready sheet among the formats. There is no push into any ledger, and no accounting product is integrated; the file is reviewed and imported on the accounting side.

Before the run is approved, the pre-run review includes an accounting-mapping-gaps check, so a pay element with nowhere to post is caught before the export. Payroll Intelligence covers the review.

TriblockHR allocates payroll cost. It does not do job costing beyond that, estimating, quoting, fleet, equipment or dispatch. Hours reach the timesheets from the rota and the clock; shift scheduling covers the rota side, and the field services page the wider operation.

Questions

How is a field worker’s labour cost split?

By division, department and island, each line carrying its GL code. For the pay types you choose, the division is taken from the timesheet line.

What if someone works at more than one site in a period?

Each timesheet line carries the division of the site the hours were worked at, so the cost follows the hours.

Is cost pushed into the ledger?

No. It leaves as an export file with the GL codes, imported on the accounting side.

Let labour cost follow the work, off the timesheet lines the hours were recorded on.

Book a demo

  • SOC 2 Type II attested
  • AES-256 at rest
  • 99.9% uptime
  • Built in The Bahamas