> ## Documentation Index
> Fetch the complete documentation index at: https://docs.driven.work/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Driven is a sales-compensation platform. Use its terminology: Compensation Plan, Compensation, KPI, Manual KPI, User Variable, Quota, Performance, Payout (Draft, Approved, Paid, Cancelled), Correction, Adjustment. Payout types are equal, deferred and advance. Default roles are Admin and Employee; companies can add custom roles. The Driven Agent builds plans from uploaded documents and chat. The Compensation Builder is where compensations are configured.

# Corrections

> A correction is the difference between what a locked payout paid and what the current rules say it should have paid. You choose whether to add it to the next payout or write it off.

Approved, paid and cancelled payouts do not change when you edit a compensation. See [Locking](https://docs.driven.work/payouts/locking.md). If the new rules would have paid a different amount, Driven does not guess. It shows you the difference and asks what to do with it. That difference is a **correction**.

A correction is created when you publish a compensation change that touches locked payouts, or when you change a [user variable](https://docs.driven.work/users/manage-user-variables.md) that those payouts used. The locked payout itself stays as it was approved.

A positive correction means the person was underpaid. A negative correction means they were overpaid.

## Review and publish

Click **Review & Publish** on a compensation that already has locked payouts. The dialog has three steps.

### AI Check

Driven reads the compensation for common problems, such as quotas that are turned on but empty. You can go back and fix them, or continue.

### Review Changes

This step only looks. Nothing is saved yet.

The heading tells you how many people are affected, for example **Your formula change affects 4 reps who were already paid.** Summary cards are:

* **People affected**, people whose net difference is not zero
* **To recover**, the sum of what people were overpaid
* **To pay out**, the sum of what people are still owed

The table has one row per person and period:

| Column | Meaning |
| - | - |
| **Was paid** | What they were already paid for that locked payout, including earlier corrections |
| **Should be paid** | What the rules you are about to publish would have paid |
| **Delta** | Should be paid, minus was paid |

**Example.** Q1 was approved at 8% and the person was paid €8,000. You change the rate to 10%. Should be paid is €10,000. Delta is **€2,000**.

Someone whose differences cancel out to zero is not listed. The underlying per-payout differences are still recorded, so a later payout can settle them.

### Settle Difference

**Choose recovery method per rep.** **Same for everyone** applies one method to all.

| Recovery method | What happens |
| - | - |
| **Add to next payout** | The delta is applied to the next payout. This is the default. The description is **Applied automatically to the next payout**. |
| **Write off** | The difference is recorded and nothing is paid or recovered. The description is **Logged but not deducted**. |

**Add to next payout** will not take a payout below zero. If a clawback is larger than the next payout, the payout becomes zero and the rest stays outstanding until a later payout can absorb it.

**Save & Publish** saves the compensation and the corrections together. If you cancel, neither is saved.

If nothing needs a correction, the last button is **Skip & Publish**, or **Publish anyway** when the AI check found issues you chose not to fix.

## Where the correction shows up

The correction is not edited onto the old payout. It is settled when a later payout is approved.

On that later payout, the person sees the settlement in the compensation breakdown, with the period it comes from and a signed amount. A top-up is added to the payout. A clawback is subtracted. The payout total already includes it.

Only the oldest draft payout in a series shows the settlement it is about to apply. Once you approve it, the settlement is fixed. See [Approve payouts](https://docs.driven.work/payouts/approval-flow.md).

Changing a user variable outside the builder opens the same kind of review, titled **Review changes**, before the new value is saved.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.