Skip to main content

How clawbacks work

What triggers a clawback, what is and isn't taken back, where it shows in payroll and reports, and how Clawback Exempt protects paid milestones.

A clawback takes back pay a worker already received on a sale. It can happen automatically when a sale gets a cancel date and meets the product clawback rules, or when an admin changes the closer on a sale. Only money the worker actually received is clawed back, and it reduces the Commission or Overrides amount in a regular payroll. Mortgage companies see Loan instead of Sale.

Who can do this: Clawbacks are created automatically. Admins see them in Run Payroll (Payroll > Run Payroll & Approvals) and in the Reports > Sales Report Builder (requires Sales View permission). Setting a product's Clawback Exempt milestone needs the Setting > Products permission. Workers see their own clawbacks on My Earnings > Commission.

What triggers a clawback

A cancel date on the sale

  • Milestones that haven't been paid yet are removed. A cancelled sale never pays anything more.

  • Milestones the worker already received are clawed back. That includes amounts paid through payroll, amounts sent to the worker's reserve, and amounts marked as paid outside Sequifi with Mark as Paid.

  • Amounts marked Do Not Pay are never clawed back, because they were never paid.

  • Overrides on the sale are clawed back too, including manual overrides.

Changing the closer

If an admin changes the closer on a sale, the old closer's paid amounts are clawed back and the sale moves to the new closer. You can't change the closer once the final milestone is paid. You see "Apologies, the closer cannot be change because the M2 amount has already been paid". If your company uses reconciliation, the same block applies once reconciliation on the sale has been paid out.

Where the clawback shows up

  • Run Payroll: as a negative amount within Commission or Overrides, in the period set by the cancel date and the worker's pay frequency. Select that amount to see the clawback line; it is not in the Deductions column.

  • Sales Report Builder: the built-in Clawback view lists sales with a settled clawback, newest first. See Clawback, Pending Installs and Balance Due views.

  • The sale: its status shows Clawback.

  • The worker's Commission page: the line shows a Clawback pay status, and the Clawbacks card totals "Pay taken back after cancellation."

Protect paid milestones with Clawback Exempt

Sales Report Builder and Settings > Products are not available in every company setup. Each available product can set Clawback Exempt to None or to a milestone. "A job that reaches the selected milestone or beyond will not trigger a clawback deduction in the event of a cancel."

  1. In the Admin view, open Settings > Products and open the product.

  2. In Clawback Exempt, choose the milestone.

  3. Save the product.

A cancelled sale keeps what was paid only if that milestone has a date on the sale, the date is today or earlier, and the cancel date is not before it. Otherwise the full clawback applies.

When a clawback makes net pay negative

If a clawback pushes a worker's net pay below zero (not counting reimbursements), you can't finalize the payroll until you fix it. Filter Run Payroll by Net pay (Payroll) > Negative Amount, then move the negative rows to the next payroll, add an adjustment, or mark rows Do Not Pay. See Why can't I finalize payroll?

On the mobile app

Clawback settings and payroll are on the web only.

Common questions

What decides whether a cancelled sale is clawed back?

The cancel date and the product's Clawback Exempt milestone. If a clawback looks wrong, check the sale's cancel date and the milestone dates on the sale first.

Why was a worker clawed back for a sale they were never paid on?

Check whether the amount was marked paid outside Sequifi or credited to reserve. If the history still looks wrong, ask your payroll admin to investigate. Unpaid milestones on a cancelled sale are simply removed, which can make projected pay disappear.

Related articles

Did this answer your question?