THE SHORT ANSWER
A matching total
does not settle every payment.
A weekly payroll total can match the expected total even when individual employees, shifts or payment periods are wrong. Positive and negative differences can cancel, a payment can be allocated to the wrong work, or the comparison itself can omit the same records on both sides.
Use the weekly total as a reconciliation control, then review the underlying obligations and payments. A zero aggregate difference means only that the selected totals match under the scope and assumptions used.
This is a gross hourly-pay review process, not a determination of lawful offsets or a complete payroll, tax or entitlement audit.
WORKED EXAMPLE
One matching total.
Two questions still open.
Two fictional employees in the same review week.
Assume the expected gross amounts for the compared hourly-pay obligations have been independently established. The matching payroll amounts are allocated to the correct employees and work dates. No documented adjustment explains the differences. Dollar values are invented, not published Award rates.
| Employee | Expected | Matching paid | Variance |
|---|---|---|---|
| Employee A | $600.00 | $550.00 | −$50.00 |
| Employee B | $400.00 | $450.00 | +$50.00 |
| Weekly total | $1,000.00 | $1,000.00 | $0.00 |
Employee B’s additional $50.00 does not explain why Employee A received $50.00 less. Review A’s shortfall and B’s unexpected payment separately. A positive difference is not, by itself, proof of a recoverable debt.
The absolute differences add to $100.00 of items to investigate. That is not $100.00 owed to employees, nor a repayment demand. Do not confuse the volume of differences with their legal or payment outcome.
This example assumes the benchmark and allocations are correct. It illustrates arithmetic cancellation only and does not establish real employee entitlements.
STEP 01
Define exactly
what the total includes.
Write down the employees, work dates, entitlements and gross-pay components in scope. Keep payment date, work week and pay-period boundaries separate. A fortnightly payment is not automatically a weekly comparison.
Agree which adjustments, reversals, leave or other amounts are excluded or separately reviewed. Do not compare an hourly-pay benchmark with an unexplained whole-payrun gross amount.
STEP 02
Reconcile the population
before the money.
Check employee identifiers, included work dates, shift references and source-row counts. Compare the source records with the review dataset, including off-cycle records and reversals.
Investigate missing employees, duplicate exports, gaps and mapping errors even when totals agree. A record without an established expected amount is unresolved, not zero entitlement; an unmatched payment must not be silently assigned to a convenient shift.
STEP 03
Verify the expected amount
independently.
Check the employee facts, applicable instrument, dated rates, actual work and any complete-period evidence. A calculation based on the same faulty payroll defaults can reproduce the original error.
Fair Work’s underpayment review guidance starts with what the employee was entitled to and compares it with what was paid. A software benchmark is only as reliable as its facts, rules and scope.
STEP 04
Compare by employee,
work and entitlement.
Start with employee and work period, then inspect the relevant shift or earnings segment. Retain the source references and all matching payment components. Use our timesheet, roster and payslip comparison guide to connect the records.
Keep period-level obligations at period level unless a supported allocation basis exists. Do not distribute a weekly overtime amount or another cycle outcome evenly across shifts simply to make a table balance.
An employee total that matches can still require segment review. Conversely, a segment difference may be explained by a separately paid component or a valid arrangement that needs evidence.
STEP 05
Keep shortages
and positive differences visible.
Use one consistent sign convention, such as paid minus expected. Retain negative differences, positive differences, unresolved records and the net total as separate views. Define any investigation tolerance and check repeated small differences.
Do not describe a matching total as proof that every included employee was paid correctly. Nor does it establish that every apparent component difference is a legally separate debt. Any claimed offset or set-off requires assessment of the actual arrangement, entitlement and payment purpose.
STEP 06
Trace adjustments
to the work they correct.
For each back payment, reversal or off-cycle amount, retain the original period, correction period and reference. Count linked payments once and show which obligation they address.
A current-week payment for earlier work can legitimately affect a payrun total. Allocate it using the supporting records; do not move it between employees or periods just to eliminate a variance.
STEP 07
Resolve the individual issue
and recheck the control total.
Record whether each item is an evidenced shortfall, an explained payment, a data problem or an unresolved question. Follow the underpayment guide for shortages and the unexpected-payment guide for positive differences.
Arrange supported corrections through the employer’s authorised process. Reconcile the detailed changes back to the employee and period totals, then the overall total. A balanced report is a useful control, not a replacement for resolving the underlying question.
Keep a review record
that can explain the total.
- Identity and scope: employee ID, work date, period, shift or period-level obligation, entitlement and source rows.
- Benchmark: established payable quantity, dated rate, calculation, assumptions and missing evidence.
- Payment: matching gross components, payrun, payment date, reversal and correction references.
- Outcome: signed variance, explanation, unresolved facts, reviewer and follow-up action.
A useful control summary shows included employees and rows, missing or unmatched records, negative and positive differences, and the net amount. It must state the scope checked and the questions left open. These are suggested working fields, not a claim that every view is an existing WageReview screen.
Where WageReview
can help.
WageReview’s controlled demo compares represented hourly-pay amounts under Retail MA000004, Hospitality MA000009 and Restaurant MA000119. Supported calculations show pay segments, applicable rates and source references for human review.
Some outcomes depend on complete roster, written-pattern and period evidence. Missing or conflicting calculation facts can block an affected calculation or require manual review. The system does not decide legal Award coverage or invent missing inputs.
This guide’s working checklist is broader than automated scope and is not an upload template. Tax, superannuation, leave, termination and salary or annualised-wage reconciliation are outside current calculations. Unsupported exceptions and special arrangements need separate review.
Explore the review workflow · Prepare your records
Controlled demonstration. Production use remains disabled. WageReview does not create pay runs, write back to payroll, automatically correct payments or guarantee complete Award compliance.
Common questions.
Does a zero payroll variance mean everyone was paid correctly?
No. It means the compared totals match. Employee-level differences, missing records and an incorrect benchmark can still exist.
Can an extra payment to one employee fix a shortage for another?
An amount allocated to another employee does not explain the first employee’s payment. Investigate each person and the purpose of each payment separately.
Does a shortage on one shift always mean a separate amount is legally owed?
The apparent component difference needs investigation in the context of the instrument, arrangement and all matching payments. Do not assume either that every excess can offset it or that a worksheet row alone settles the legal result.
Should every weekly adjustment be allocated equally to shifts?
No. Preserve the obligation’s correct level and use a supported allocation basis. An arbitrary split can create misleading shift-level findings.
Does a positive variance establish a debt?
No. It may reflect an agreed higher rate, valid adjustment, allocation issue or payment error. Establish the explanation before considering any response.
Official sources
and related guides.
- Fair Work: I think I’ve underpaid my employee
- Fair Work: Record-keeping
- Fair Work: Overpayments
- WageReview: Underpayment checking guide
- WageReview: Unexpected-payment guide
Sources checked 16 October 2026. General information for Australian payroll review, not legal advice. Confirm the instrument and effective rules for the work dates. Examples use invented values and do not establish actual employee entitlements.