A reviewer sends a run back and the preparer fixes it
Who is involved
| Role | What they do |
|---|---|
| Payroll specialist | Prepares the run and fixes what the reviewer found. |
| Payroll approver | Rejects with a reason, reopens when the fix is ready. |
| Payroll manager | Is told about the rejection and its reason. |
Step by step
- Payroll specialist
Submits a computed run for approval.
What they see:The run is in review.
- Payroll approver
Finds a problem in the variance view and rejects the run, writing the reason.
What they see:The run is marked rejected.
- Payroll manager
Reads the rejection notice and tells the preparer what to fix.
What they see:The reason, in the app and in the e-mail.
- Payroll specialist
Fixes the data behind the reason, such as a contract or a work entry.
What they see:The corrected record.
- Payroll approver
Reopens the rejected run, so it can be recomputed.
What they see:The run is back to computed and the history shows the reopening.
- Payroll specialist
Recomputes the run through Copilot or the API, and submits it again.
What they see:The run is back in review.
- Payroll approver
Approves.
What they see:The run is approved.
Who is told what
A rejection notifies payroll managers in the app and by e-mail with the reason; the preparer is not notified directly. The reason is stored on the run and in its history, which Copilot or the API can read.