Payroll · Daily operations · 7 min read

Close a run and correct a posted run

Close a paid run and fix mistakes in a posted run with a correction run, without reversing anything.

Before you begin

• To close: the run is posted, payslips are published and every payment instruction is accepted.
• To correct: the run is Posted or Closed. You hold payroll.prepare; a correction run still needs approval by someone else and posting.

Steps

Close a run

1. Open the run and click Close.
2. The run becomes Paid / Closed.

If something is missing, the message names it: 'The run cannot close: payslips are not published; 2 payment instruction(s) are not accepted by the bank.'

Raise a correction run

1. On the original run, click Correction run.
2. Add one line per correction. Choose the Payslip (of that run), enter the Element code (it must be in the run's rule package, for example BONUS), the Amount and a Reason.
3. The amount is not zero; negative reduces pay. The reason is 5 to 500 characters.
4. Confirm. A new run (number ...-02, type Correction) is created already Calculated, with one delta payslip per person.
5. A different person approves it, then Finance posts it, publishes and pays it as usual. See Approve, post and publish a payroll run.

What happens next

• The original run, its payslips and journal are not touched. There is no reversal.
• The correction posts a second journal for the difference only.
• Example: the September run paid AED 500 too much bonus to employee E. The correction line BONUS -500.00 produces a delta payslip of -500.00. Across the two runs, E's net equals the corrected amount.
• The payroll register lists both runs.

Good to know

• Posted runs cannot be cancelled, recalculated or sent back: 'A posted run cannot be cancelled. Raise a correction run.'
• A correction line must name a payslip of the original run: 'Each line must name a payslip of the original run.'
• Wrong element: 'XYZ is not in the run's rule package.'
• 'A correction line needs a non-zero amount.'
• 'Say why the run is being corrected.' if the reason is too short.
• Repeating the same request returns the first answer; a different request with the same key is refused: 'That idempotency key was already used for a different request.'
• If an amount is typed as letters on the correction form, the system may fail with a server error instead of a field message. Retype it as a number.
• Late HR changes to a frozen period do not need a correction run; they queue as adjustments for the next regular run. See Manual inputs, adjustments and eligibility.
• Cancel run (from the menu) is only for draft, frozen or calculated runs, and frees the period for a new regular run.