Audit trail
Commission is money, and money attracts questions months after the fact. Lokom records who did what so those questions have answers that are not somebody's memory.
Lokom records the trail, but reads it back in the place each record belongs — plan version history, statement diagnostics, the manual-pay line. The complete audit log is available as a file, in your data export, not as a page you browse. → Download your data
Where each part of the trail lives
| What you want to know | Where to look |
|---|---|
| Who changed a plan, when, and what changed | The plan's Version history — every version, with a diff against the previous one |
| Which plan version produced an old payout | The statement itself; superseded versions stay readable forever |
| Who validated or rejected a statement | The statement's Diagnostics panel — statement ID, version, status, approved by, approved at, rejection reason, version history |
| Why a manual pay line exists | The line on the statement — author, date and reason code, never folded invisibly into a total |
| Which deals were excluded | Review & Close → Deal review, filtered to Excluded |
| Everything, as raw records | Settings → General → Danger Zone → Download your data → audit log |
Why the version model matters here
Because superseded plan versions are retained, an old statement points at the rules that actually produced it. Without that, changing a rate would silently rewrite the explanation of every past payout — the numbers would stay, but the reason would now be wrong.
Role targets work slightly differently: a target follows the sum of its members' quotas until someone overrides it by hand, and both the override and its later removal are recorded with who did it and what the previous value was. Once a period is computed, the figure the bonus was measured against is stored on the payout and does not move afterwards.
Answering "why was I paid this?"
For the dispute-resolution path — checking components, attainment, deals, attribution, plan version, and manual adjustments — see Payout lineage § Working a dispute.
Things the trail cannot help with
It records what happened in Lokom. It does not record a promise made verbally in a one-to-one, or a spreadsheet someone kept alongside. If an exception is agreed, put it in Lokom as a manual pay line — that is what makes it survive the person who agreed it.