Build gross pay from approved inputs

How to calculate gross pay for a payroll run

Start by defining the run rather than opening a spreadsheet and adding whatever has arrived. Record the employing entity, payroll period, intended payment date, input cut-off, preparer, reviewer and exception owner. A monthly payroll might process July records for payment on 31 July, but not every input will have been earned during July.

Three period references answer different questions:

These references matter for late timesheets, back pay, commission, holiday pay and minimum-wage checks. Moving a late item into the next payroll does not change when the work occurred. Preserve the earned-period reference and the reason for the timing so a later reviewer can understand the history.

Define the cut-off without treating it as law

An internal cut-off gives managers and payroll enough time to approve changes. It does not by itself decide whether pay can legally or contractually be delayed. When information arrives late, identify what happened: did a worker submit a timesheet late, did the employer already know that the work occurred, or did an authorised pay change fail to reach payroll? Check the contract, payment obligations and relevant minimum-wage allocation rules before choosing an off-cycle payment or a controlled later adjustment.

Assign ownership

Name the person or controlled system that supplies each source, the person authorised to approve it and the reviewer who checks the schedule. A small employer may give more than one role to the same person, but approval must still be explicit. Payroll should not infer approval merely because a timesheet exists or a manager mentioned a bonus in a message.

Build the source pack

Gather the contractual salary or hourly rate, approved ordinary hours, overtime, paid travel time, bonuses, commission, holiday pay, statutory payments, allowances and effective-dated changes that may affect this run. Record every item against a stable employee ID and a stable source-record reference.

For a calculated item, retain the quantity, unit and rate as well as the result. Ninety-six hours at £13 per hour should be stored as 96 hours × 1,300 pence = 124,800 pence, not only as £1,248. This lets the reviewer reproduce the amount without relying on memory or a separate calculation that may later change.

Fixed items still need evidence. A £50 bonus might not use quantity and rate, but it needs the approval, reason, employee, earned period and payment date. An effective-dated salary change needs the authorised instruction and the employer’s documented contractual proration method.

Reconcile hours before calculating pay

Compare approved hours with the rota, timesheet or other controlled source. Investigate missing shifts, duplicate imports and adjustments rather than compensating with a balancing figure. Two approved items with the same amount are not necessarily duplicates. Duplication is tested using the stable element and source references in the employee and payroll-period context.

Statutory payments are inputs with a separate owner

Statutory payments may be recorded through payroll and may enter gross pay. This lesson does not determine entitlement or calculate their amount. Bring an authorised statutory-payment result into the source pack and retain the supporting calculation from its owning workflow. GOV.UK explains the types of payments recorded in payroll.

Separate pay from related money and records

Classify every source item before summing it:

Classifying an item as grossPay does not determine whether it is taxable, subject to National Insurance, pensionable, counted as minimum-wage pay, recoverable as a statutory payment or reportable as a benefit. Those are separate downstream questions. Lesson 7 explains the different pay bases rather than assuming they all equal gross pay.

Paid travel time may be remuneration for working time and enter gross pay. Mileage reimbursement is an expense that follows its own rules. Do not combine the two under a generic “travel” label. Likewise, an employer pension contribution is a cost but does not increase the employee’s gross pay.

Keep unresolved items visible

Pending and rejected elements should stay in the review evidence even though they do not enter the approved total. This allows the reviewer to see that an expected item was considered and why it was omitted. Do not delete a late or rejected input merely to make the schedule reconcile.

Control corrections and reversals

Ordinary inputs should not be negative. A genuine correction or reversal may be negative, but it must reference the original element, state the reason and receive enhanced approval. A negative employee total or schedule total is an approval blocker until the reviewer establishes why it is valid and how it should be handled.

Build Tariro’s gross-pay schedule

Riverside’s fictional care-worker example combines regular and variable inputs. Use the builder to see how changing an approval state affects the schedule. Mileage stays visible but outside gross pay.

The complete approved schedule is:

The example demonstrates traceability and arithmetic. It does not establish that every employer must apply the same overtime, sleep-in or travel treatment. The contract, working arrangement and applicable rules still govern the source values.

Minimum wage is a separate control

Gross pay is the starting point for a separate minimum-wage check. Do not assume every gross-pay element counts as minimum-wage pay or that every payroll hour is treated identically under minimum-wage rules.

The pay-reference period cannot exceed one calendar month. Expenses and many allowances do not count as minimum-wage pay, premium portions of overtime or shift pay may need separate treatment, and working-time treatment depends on the type of work. Deferred payments and genuinely late timesheets also have allocation rules. Do not use gross pay divided by every recorded hour as a universal compliance test. Use the current minimum-wage calculation guidance and working-time guidance.

Review the schedule, not only the grand total

Produce control totals for employee count, employees with positive gross pay, zero-pay employees, ordinary pay, variable pay, statutory pay, total approved gross pay, pending or excluded inputs and the variance from the previous period. A stable grand total can hide one omitted employee and one duplicated employee, so reconcile the population and categories as well as the money.

Investigate missing starters, unexpected zero pay, duplicate IDs, repeated source records, stale effective dates, negative totals and material changes. An exact duplicate ID must stop calculation; the system must not silently choose one version. Separate legitimate records that happen to have equal amounts should both remain.

Decide how to handle a late input

Ask what the employer knew, when the work was performed, what the contract requires and whether the delay affects minimum-wage or payment obligations. A genuinely late employee timesheet may follow different allocation rules from hours the manager had already approved but failed to send to payroll. Record whether the resolution is an off-cycle payment, inclusion in the current run or a controlled following-period adjustment. Preserve the earned-period reference in every case.

Three key takeaways

1. Preserve payroll period, earned period and payment date instead of flattening them into one date.
2. Gross pay includes only supported and approved pay elements; related expenses and employer costs remain separate.
3. Approve a reconciled schedule with control totals before deductions are calculated.

What comes next

Lesson 7, Understand deductions and net pay, starts with this approved gross-pay schedule. It explains why gross, taxable, National Insurance and pensionable pay may differ and how a reviewer follows the result through to net pay.