Remediation The Payroll Studio
Payroll remediation checklist: a practical guide for Australian employers
Use this payroll remediation checklist to track the actions, owners and evidence needed to correct underpayments. Work through eight stages, from recording the issue to reconciling payments and testing lasting fixes.
How to use this checklist
Start with the stage that matches your programme, then check the earlier dependencies. These are working checkpoints, not a requirement to finish every stage in sequence: employee communication, current-pay fixes and investigation often run together.
For the explanation behind each stage, read our payroll remediation guide. This companion focuses on what to record and who needs to act.
Download the editable payroll remediation checklist (CSV) — 24 checks ready to open in Excel or Google Sheets. No email address is required.
For each check, record a named owner, status, due date, evidence reference and next decision. Suggested statuses are Not started, In progress, Blocked, Ready for review, Complete and Not applicable—with a reason. An activity is not complete merely because a meeting occurred or a file was delivered: retain the evidence supporting the outcome.
The owner suggestions below are starting points, not fixed allocations. Scale the work to your organisation and agree the responsibilities of the employer, TPS, calculation provider and specialist advisers. Avoid putting employee-level personal information in the tracker; use controlled references to records held securely elsewhere.
This is an original TPS working tool informed by Rebecca Wade's practitioner input and official guidance. It does not certify compliance or replace advice on your specific circumstances.
1. Record the issue and assign ownership
Suggested owner: Programme sponsor and payroll lead.
| Check | Action | Evidence to retain |
|---|---|---|
| 01 | Describe the observed discrepancy separately from suspected causes. | Issue record with source, observation date and next decision. |
| 02 | Identify whether incorrect pay may still be occurring and assign an immediate response. | Current-pay assessment, interim action and accountable owner. |
| 03 | Confirm programme resources, decision authority and advice needed on notification or escalation. | Named sponsor, workstream owners, resourcing plan and advice/action record. |
Do not wait for a final historic calculation to decide who will investigate an ongoing pay issue. Record what is known, what remains uncertain and the next decision required.
2. Define the population and review period
Suggested owner: Programme lead with HR and relevant advisers.
| Check | Action | Evidence to retain |
|---|---|---|
| 04 | Map potentially affected employees, former employees, entities, instruments and entitlements. | Scope register with inclusion and exclusion reasons. |
| 05 | Document the basis for the review period and how newly discovered issues can expand scope. | Approved period rationale and scope-change log. |
| 06 | Plan how employees and representatives can contribute information about actual work practices. | Consultation plan and record of information that changes scope or assumptions. |
A six-year limitation period is not automatically the correct boundary for every remediation review. Establish the period with appropriate advice and document the rationale. Keep excluded groups visible so that new information can trigger reconsideration.
3. Prepare data and approve the methodology
Suggested owner: Data owners, calculation provider and relevant specialists.
| Check | Action | Evidence to retain |
|---|---|---|
| 07 | Inventory source records, time periods, owners and versions; log missing or inconsistent data. | Data inventory, completeness checks and gap register. |
| 08 | Map the rules, classifications and effective dates used in calculations to approved decisions. | Instrument/rule mapping and methodology decision log. |
| 09 | Escalate assumptions and any prior-payment or offsetting treatment for appropriate review. | Documented rationale, approval and traceability to affected calculations. |
If a file is missing, record the gap and the decision needed; an empty field is not evidence that no entitlement exists. Preserve the distinction between source data, an assumption and an approved interpretation.
4. Validate results before release
Suggested owner: Validation lead and designated approver.
| Check | Action | Evidence to retain |
|---|---|---|
| 10 | Agree test coverage across relevant instruments, employee groups, periods and unusual scenarios. | Validation plan with independently established expected outcomes. |
| 11 | Investigate exceptions and record how each was resolved or escalated. | Test results, exception register and impact assessment. |
| 12 | Check that changes to data or methodology trigger the necessary retesting. | Version history, retest evidence and release recommendation. |
Use the validation guide for detailed test planning. A successful software run is not the same as evidence that inputs, rules and employee outcomes are correct.
5. Reconcile previous remediation payments
Suggested owner: Finance, payroll and methodology approvers.
| Check | Action | Evidence to retain |
|---|---|---|
| 13 | Match earlier payments to reliable employee identifiers, periods and payment components. | Prior-payment register with source records and unmatched items. |
| 14 | Separate revised entitlement, approved treatment of previous payments and remaining amounts. | Reconciliation using the approved methodology; no unexplained netting. |
| 15 | Check tax, superannuation, interest and reporting treatment with the responsible specialists. | Component-level schedule, treatment decisions and approvals. |
Define what “net” means in each report. Remaining entitlement after approved prior-payment treatment and the employee cash amount after tax are different measures. This checklist intentionally provides no universal offsetting or interest formula.
6. Prepare the employee communication and payment journey
Suggested owner: HR/communications with payroll and data-security owners.
| Check | Action | Evidence to retain |
|---|---|---|
| 16 | Plan initial updates, progress messages, individual outcomes and accessible review channels. | Audience/channel plan, approved messages and query owners. |
| 17 | Provide secure routes for current and former employees to confirm relevant payment details. | Detail-verification procedure, alternative access route and exception handling. |
| 18 | Explain how employees can query results, and how new evidence feeds back into the programme. | Review workflow, case register and wider-cohort assessment process. |
Use the employee communications guide to plan the handoffs. Confirming bank or super details should not be presented as acceptance of the calculation or waiver of an employee’s rights.
7. Authorise payments and reconcile execution
Suggested owner: Payroll and finance approvers.
| Check | Action | Evidence to retain |
|---|---|---|
| 19 | Check the authorised population and amounts against the final payment instructions. | Approved release file, control totals and authorisation record. |
| 20 | Track successful, failed and outstanding payments and reconcile them to approved instructions. | Payment-status reconciliation with named follow-up owners. |
| 21 | Confirm required reporting and keep former-employee contact and unresolved-payment work visible. | Reporting confirmations, contact log and outstanding-items register. |
A transmitted payment file is not proof that every employee received payment. Keep failed and outstanding items separate from paid items, and make their next action visible.
8. Fix the driver and hand over ongoing controls
Suggested owner: Process, policy, system or data owners with the sponsor.
| Check | Action | Evidence to retain |
|---|---|---|
| 22 | Connect each confirmed cause to a corrective action and test the changed behaviour. | Cause/action register and evidence that the fix addresses the original scenario. |
| 23 | Account for the period between the review cut-off and the effective fix, and assign ongoing monitoring. | Coverage decision, control owner, monitoring evidence and escalation route. |
| 24 | Document closure decisions and retain ownership of residual payments, queries or unresolved risks. | Closure record, residual-action register and business-as-usual handover. |
Use the root-cause guide to connect the finding to a system, process, policy or data change. A paid historical amount and an effective future control need separate evidence.
Worked example: when a payment is complete but the action is not
Consider a hypothetical missing allowance caused by an incorrect system mapping. The historical calculation has been validated and the affected employees have been paid. However, the mapping change has not been tested and the next pay run could repeat the error.
In the tracker, check 20 can record the completed payment reconciliation with its evidence reference. Check 22 remains In progress until the system owner provides evidence of the fix and testing. Check 23 identifies how the period up to the effective correction is covered. The sponsor can see the remaining exposure without calling the whole programme complete.
If testing reveals that a second employee group uses the same mapping, reopen the scope decision at check 04. Do not treat the initial checklist as a fixed boundary. This example illustrates the workflow; it is not a client case or an entitlement calculation.
What should be escalated rather than ticked off?
Bring a decision forward when missing evidence could affect an employee outcome or a release decision. Useful escalation records identify the issue, affected scope, evidence available, options, decision owner and consequence of delay.
Examples include an unresolved rule interpretation, an unmatched previous payment, a material validation exception, a current-pay fix that has not been tested, or employee information that suggests a wider affected population. Record who decides whether the issue affects release or requires further review; do not hide it behind an overall percentage-complete score.
Where can your team get help?
The Payroll Studio can help manage remediation programmes, investigate underpayment drivers, develop validation and reconciliation approaches and coordinate the employee-payment journey. Explore our payroll remediation support to discuss the work your team needs and the responsibilities of existing providers and advisers.
Sources and scope
The Fair Work Ombudsman's Payroll Remediation Program Guide, April 2025 provides a suggested employee-centred framework, rather than a universal compliance checklist. Relevant sections cover programme design (printed pages 6–12), methodology (13–17), communications and payments (18–27), corrective measures and ongoing compliance (27–31), and reporting issues (31–35).
For salaried employees, read Fair Work's offsetting and record-keeping guidance. Assess the arrangement and current legal position with appropriate advisers rather than applying a general netting rule.
Portions adapt the Payroll Remediation Program Guide, April 2025. © Fair Work Ombudsman, www.fairwork.gov.au, licensed under Creative Commons Attribution 3.0 Australia. Guidance has been condensed and reorganised into original TPS actions and evidence prompts, with practitioner context and a hypothetical example. No Fair Work Ombudsman endorsement is implied.
Sources checked 27 September 2026. This local draft is prepared for Rebecca Wade's review; author approval and publication are not yet recorded.
Your questions, answered
Frequently asked questions
Who should own a payroll remediation checklist?
Give the overall programme a named accountable sponsor and assign each action to someone with authority to complete it. HR, Finance, Payroll, data and system owners, calculation providers and specialist advisers may have different responsibilities. Agree the allocation for your engagement rather than assuming Payroll owns every decision.
Does completing this checklist prove payroll compliance?
No. This is a planning and evidence-tracking tool. Completion needs to reflect the actual scope, applicable obligations, approved methodology and evidence. It is not regulator certification, legal advice or a substitute for a case-specific review.
What if we have already remediated the same period?
Keep a separate record of prior payments and the revised assessment. Confirm how earlier amounts may be treated under the approved methodology, trace them to supporting records and investigate unmatched items. Do not assume every earlier payment can automatically be deducted from the revised result.
Can a stage be marked complete while employee queries remain open?
Record the status precisely. A payment batch may be completed while review requests or failed payments remain unresolved. Each outstanding item needs an owner, next action and escalation route; new evidence may affect other employees or require earlier work to be revisited.
How do we use the downloadable tracker?
Open the CSV in Excel or import it into Google Sheets. It contains the 24 checks, suggested owners and expected evidence, with blank fields for your accountable owner, status, due date, evidence reference, next action and approval. Store completed copies in your organisation's approved environment; do not enter employee banking or payroll records into a public document.
From findings to action
Make the next remediation decision clearer.
Discuss your programme stage, the findings you need to act on and where your team needs support.
Explore payroll remediation support