Payroll remediation communications: from first update to employee payment

What does a good remediation communication plan cover?

A useful plan connects what employees need to know with the actions the programme can actually deliver. It covers the first notification, progress updates, individual outcomes, payment arrangements and questions after payment.

For HR, Finance and Payroll leaders, the difficult part is often the handoff: an employee has confirmed their details, but who checks them, authorises the payment and follows up if it fails?

Rebecca’s practitioner input describes coordinating that journey, including employee communications, portal requirements and the handoff to Payroll. This article translates that experience into a working approach within the wider payroll remediation programme.

Fair Work’s Payroll Remediation Program Guide, pages 18–22, supports early, clear communication, accessible channels and meaningful opportunities to ask questions. The worksheet below is a TPS planning tool, not a prescribed regulatory form.

What should employees hear at each stage?

Match each message to a confirmed programme milestone. Avoid promising a payment date that the calculation, approval and Payroll teams have not agreed they can meet.

Define the audience as carefully as the message. Current employees, people on leave and former employees may need different channels. People within the reviewed cohort who receive no additional payment may still need an explanation of how their circumstances were considered. Plan appropriate engagement with unions and employee representatives too.

How can you communicate before all the answers are known?

State what is confirmed, what is being investigated and when employees will hear more. Acknowledge uncertainty directly rather than filling the gap with an estimate that looks like a commitment.

A first update should answer four questions:

1. Why are you receiving this message?
2. What is the organisation reviewing?
3. Is there anything you need to do now?
4. Where can you ask questions, and when will we update you?

For example, if the review population is confirmed but individual calculations are incomplete, explain that inclusion in the review does not yet establish an individual outcome. If a milestone moves, send an update explaining the change and the next communication point.

This follows Fair Work’s approach to communication timing and unknown information in pages 19–20. Have someone outside the project read the draft: can they explain what it means without knowing the programme’s terminology?

What should an individual payment explanation contain?

Give employees enough detail to understand their result and ask an informed question. A payment total alone does not explain which entitlements or periods were reviewed.

Build the explanation from the approved calculation record, covering:

• The employment periods and entitlements considered.
• A plain-language account of the issue and calculation approach.
• The relevant payment components, with tax, superannuation and interest explained as applicable.
• Any previous remediation payments and their approved treatment in the new outcome.
• Payment arrangements, supporting records and the route to request further detail or review.

Be precise about the word net. A residual amount after reconciling an earlier remediation is not necessarily the employee’s take-home payment after tax. Label those concepts separately and have the relevant specialists approve their treatment.

Fair Work discusses outcome detail in page 21 and payment information in pages 23–24. For the evidence supporting the figures, use our remediation results validation guide.

How should the employee portal connect to Payroll?

Treat the portal as one step in a controlled payment journey. A completed form needs to become an authorised instruction, then a reconciled payment outcome.

Map these five handoffs before launch:

1. Invitation to access: employees can independently verify that the communication and portal are genuine. Former employees do not need an active company login.
2. Access to detail confirmation: the employee can confirm the required banking and super information through the approved process, with help available when something does not match.
3. Confirmation to review: the responsible team checks exceptions and records which details are ready for use. A submitted form is not automatically an approved payment instruction.
4. Review to Payroll: authorised amounts, employee identifiers and confirmed details transfer together using the agreed file version and release approval.
5. Payroll to follow-up: completed, rejected and outstanding items return to the programme team for reconciliation and employee updates.

Keep a record of status changes, responsible owners and the evidence supporting release. Limit access to sensitive details according to the organisation’s approved controls, and test the process with its security and privacy owners.

Offer an alternative for people who cannot use the portal. Fair Work’s page 20 discusses authenticity, accessibility and avoiding unnecessarily burdensome processes. Confirming details should not be presented as accepting the calculation or waiving rights; its page 18 addresses releases and confidentiality.

Who owns the handoffs and employee questions?

Assign one accountable programme owner and a named owner for each decision. HR or Communications may coordinate messages, while Payroll owns execution checks and specialist advisers resolve technical questions. Record the actual responsibilities for your organisation rather than assuming job titles settle them.

Maintain separate statuses for communication, detail verification, calculation review and payment. One “complete” flag can hide important unfinished work.

For example, in a hypothetical programme, a former employee confirms their bank details while asking whether a period of higher duties was included. Their detail-verification status can be complete while the calculation review remains open. The reviewer investigates the evidence and the authorised decision governs the next payment instruction. The portal submission must not silently close the question.

Give the enquiry team a clear escalation route and agreed response expectations. Track the question, evidence, reviewer, decision and explanation sent. Repeated questions about one entitlement or assumption should feed back into validation, and potentially root-cause investigation.

Fair Work’s pages 21–24 emphasise useful responses and review processes, including considering other employees where new information affects their outcomes.

How do you include former employees?

Design the former-employee process from the start. They may no longer have access to work email, an intranet or the bank account held in historical records.

Use appropriate contact channels, record attempts and give people a way to independently confirm the programme is genuine. Track undelivered messages separately from messages that were delivered without a response. Provide assistance where access, language or detail-verification issues prevent progress.

Fair Work discusses reasonable efforts to locate former employees and outstanding amounts in pages 25–27. A failed contact attempt does not itself resolve an outstanding payment. Keep those cases assigned, with the next action and any specialist advice recorded.

What should be checked before calling the journey complete?

Reconcile what was approved with what actually happened. A successful file upload or accepted payment batch does not by itself establish that every employee received the intended outcome.

Before closing a batch, confirm:

• The employee explanation and Payroll instruction use the same approved result.
• Completed, rejected and outstanding payment items reconcile to the authorised population and amounts.
• Supporting payment records and relevant reporting have been checked by their owners.
• Employees know how to raise a missing-payment query or request review.
• Open questions, unsuccessful contacts and further payments remain assigned and visible.

Review delivery failures, access problems and recurring questions after each communication round. Use that evidence to improve the next round and feed relevant findings into the wider remediation programme.

Where can your team get remediation support?

If your team needs help turning these checks into a working program, explore our payroll remediation support. We can discuss root-cause investigation, program management, validation, reconciliation and the employee-payment journey, with responsibilities agreed around your existing providers and advisers.

Sources and scope

This article combines practitioner input supplied by Rebecca Wade with the Fair Work Ombudsman’s Payroll Remediation Program Guide, especially pages 18–27. The workflow, status model and hypothetical example are TPS editorial tools. Tax, superannuation, interest and any proposed settlement require decisions appropriate to the programme’s circumstances; this article does not prescribe their calculation or legal treatment.

Portions adapt the Payroll Remediation Program Guide, April 2025. © Fair Work Ombudsman, www.fairwork.gov.au, licensed under CC BY 3.0 Australia. Guidance has been condensed and combined with original commentary and planning tools. No FWO endorsement is implied.