Skip to content
PerslacePerslace Help Centre

Understanding payout cycles and statuses

A payout cycle brings commission results for a defined period into one place for review. Perslace shows statuses at more than one level, so always check whether a label applies to the whole cycle, one employee, or an event in the employee timeline.

Who can use this guide

Section titled “Who can use this guide”

This guide is for Administrators, authorised Finance users, Managers, and Employees. The information each role can see depends on its Perslace permissions; the complete permission matrix has not yet been verified.

Prerequisites

Section titled “Prerequisites”

Before interpreting a status, confirm:

  • The payout cycle and period you are viewing
  • Whether the status belongs to the cycle, an employee row, or the employee timeline
  • The latest source-data refresh and calculation state
  • Your authorised role and organisation scope

Understand the status levels

Section titled “Understand the status levels”
  1. Open Payouts and select the relevant cycle.
  2. Confirm the period and the cycle-level status shown in the workspace.
  3. Review the employee rows and their Pending or Approved states.
  4. Select Review for an employee when you need the calculation status, finance or payroll status, timeline, and Earnings Breakdown.

A sanitised payout cycle and employee earnings breakdown

  1. Interpret the labels according to where they appear:

    • Draft, In Review, and Closed were observed as payout-cycle states. Exact transition rules, editing restrictions, and reopen behaviour have not been verified.
    • Pending and Approved were observed on employee review rows. Pending is not an approval.
    • Created, Approved, and Paid were observed in an employee timeline. They record workflow progress, but do not by themselves prove external finance activity.
    • Awaiting finance validation or payroll sync indicates that downstream work remains.

  2. Compare the status with the cycle totals, employee breakdown, comments, adjustments, and audit evidence before taking action.

Expected result

Section titled “Expected result”

You can identify the level to which each status applies and avoid treating an employee status as a cycle status—or a Perslace workflow label as proof of an external payment.

Important notes

Section titled “Important notes”

Important: A Paid label does not necessarily mean Perslace transferred money. Confirm funds movement in the organisation’s authoritative finance or payroll system. Perslace payment processing was not verified during the product review.

  • A Closed cycle must not be assumed to be editable, locked, or reopenable. Those behaviours remain unverified.
  • Approval and finalisation are separate high-impact actions.
  • Do not change source data, scheme rules, or assignments solely to force a preferred status.

Troubleshooting

Section titled “Troubleshooting”

The status looks out of date

Section titled “The status looks out of date”

Check the data-source Last Sync, calculation state, cycle period, employee row, and timeline. If the information still conflicts, preserve a sanitised screenshot and contact Support.

The cycle and employee statuses appear inconsistent

Section titled “The cycle and employee statuses appear inconsistent”

Confirm that you are comparing the same period and employee population. Review all employee rows and visible validation messages before assuming that the cycle state is wrong.

A Paid status cannot be matched to payroll

Section titled “A Paid status cannot be matched to payroll”

Use the external finance or payroll system as the source of truth for funds movement. Ask the authorised Finance owner to reconcile the Perslace record with that system.

Section titled “Related articles”

Last updated: August 2026