Recalculate a payout cycle safely

Recalculation can change employee results, cycle totals, and downstream review work. The Recalculate control was observed, but its scope, locking behaviour, effect on approved rows, and recovery path have not been verified.

Publication blocker: This article provides a decision checklist only. Do not run a production recalculation until the complete before-and-after behaviour has been tested with synthetic data and approved by Product and Finance.

Who can use this checklist

Primary Admins, Administrators, and authorised Finance users may prepare a recalculation review. The exact role requirement remains unverified.

Prerequisites

Before a recalculation is authorised, confirm:

The corrected source record, Metric Definition, scheme version, assignment, or other input
The affected cycle, period, employee population, and currency
The current calculation and approval states
The expected result from an independent calculation
The review owner, approval owner, and downstream Finance or payroll contact
A tested rollback or recovery approach

Review a proposed recalculation

Identify the first verified defect and correct only that defect under change control.
Record the current cycle status, employee states, totals, calculation version, and representative breakdowns.
Confirm whether any rows are approved, the cycle is finalised or closed, or results have entered a downstream payroll process.
Define the expected recalculation scope. Do not assume that Perslace will update only one employee, one scheme, or only unapproved rows.
Test the corrected input against a synthetic boundary case and, where available, an approved backtest.
Prepare a comparison covering employee amounts, earned commission, carry, adjustments, and cycle total.
Obtain explicit authorisation for the affected population and review plan.
Verify the Recalculate control’s scope, approval consequences, locking, audit record, failure handling, and recovery in a disposable cycle.
Stop here until those behaviours are confirmed. Do not select Recalculate in a live cycle from this guide.

Expected result

The team has an authorised recalculation plan, a preserved baseline, and a defined reconciliation. No live result has been changed by following this draft.

Important notes

Warning: Recalculation may change approved results. The exact effect on approvals, adjustments, and finalised or closed cycles is unverified.

A successful recalculation still requires human reconciliation.
Do not edit production inputs merely to obtain a preferred payout result.
Recalculation does not prove that any external payment was made or updated.

Troubleshooting

The expected scope is unclear

Do not continue. Capture the cycle, period, scheme, affected employee population, and current states, then ask the Product or Support owner to confirm scope.

The new total still does not reconcile in testing

Compare the same data refresh, population, period, currency, scheme version, carry, and adjustments. Return to the first stage where expected and actual results diverge.

Recalculate is unavailable or fails

Check role, Action Lock or access approval, visible validation, cycle state, and whether another calculation is in progress. Never bypass a control or repeatedly retry a high-impact action without understanding its state.

Last updated: August 2026