Settle each period with a full record.

Freeze the numbers, record who approved them, publish to earners, then export the payroll file. Corrections are disclosed, never quietly edited.

SettlementOctober 2026Search ⌘K3A
Settlement
When to use this: to turn a computed incentive period into a payout. Freezing fixes the numbers, approval records who signed them off, and publishing is the moment the people being paid can see them.
SchemeField incentive, H2 2026 (field-h2-2026)
Period2026-09
Open this period
The run being settled

A period is settled against one run. Freezing pins it, and everything downstream cites it.

Run2026-10-02 09:40, actual, run-2026-09-a41c
Earners priced
24
Total payout
$612,000
Scope
Everyone in this account
This period openrevision 1

Nothing here has been shown to an earner yet.

Approvals: 0 of 1

4 steps
Freeze, approve, publish, export
SHA-256
Fingerprint recorded on every payroll file
Never
A paid run is never rewritten

Each step is recorded against a person.

Freezing pins the period to one run and fixes the numbers. Approval records who signed them off, with an optional note. Publishing gives every earner a statement and is confirmed first, because after it the period cannot be reopened.

The trail on the screen lists every transition with who, when and why. If two people act on the same period at once, the second is told someone else changed it and nothing is applied twice.

Late data has a proper road back.

A frozen or approved period can be reopened with a reason. Freezing before the settlement window has closed is possible but needs a reason, and that reason is recorded against you.

Once earners have seen a number, a correction is a restatement. It creates a new run, compares it with the old one, and appends the original figure, the new figure and the difference to the statement. Small differences below your materiality threshold are recorded and not carried. The restatement goes back through approval like any other run.

The payroll file is the file that was approved.

Exporting a published period produces a CSV for payroll and marks the period paid. Dexor records a fingerprint of the file, and every later download rebuilds it and checks the fingerprint before handing it over. If something feeding the file has changed, the download refuses rather than serving a different file.

For a restatement the export carries only the arrears or recovery, so nobody is paid twice. Payroll export is available through the Dexor API.

Questions people ask.

Who can freeze, approve and publish?
Moving a period is an account admin action, enforced by the server. Managers can read the period and answer questions raised about it.
What happens if numbers change after we publish?
An admin runs a restatement. It recomputes the period as a new run, shows earners the original figure, the corrected figure and the difference, and goes back through approval. The published record stays intact.
Can a payroll file be altered after export?
Every export records a SHA-256 fingerprint. A later download rebuilds the file from the run and refuses if it no longer matches.
What has to be true before a period can be settled?
Every month in the run must be closed and every result needing attention resolved. Dexor enforces both before a period is frozen, and neither check can be overridden.

Works well with.

Everything in incentives

Statements and disputes

Reps see each published statement with its working on their phone, and can raise a question about it within the dispute window.

Read more

Period close

Once a month is reported, close it. Sales, re-projection, target edits and orders for that month are kept out until someone reopens it with a reason.

Read more

See it on your own team.

Tell us your fleet and we will size a proposal. Complete roll-out may take up to 4 months, counted from signed requirements and first payment.