> For the complete documentation index, see [llms.txt](https://docs.wandreferrals.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wandreferrals.com/referrals-sales-and-reversals/hold-period-and-keep-commission.md).

# Commission hold periods

Two program controls protect you (and your affiliates) around refunds and payout timing.

## Commission hold period (approval delay)

**What it does.** Delays a commission from becoming payable until a set number of days pass — long enough for the return/refund window to close, so you don't pay on orders that later get refunded.

**How it works.** Choose immediate approval, a configurable delay, or manual approval. New or previously unconfigured programs default to a 30-day delay. Existing programs keep their prior effective behavior. When a commission is awarded:

* **Immediate** starts the commission approved and ready to become payable.
* **Delay** starts it pending and makes it payable after `order date + delay days`.
* **Manual** holds it pending until an authorized merchant approval.

Affiliates see held commissions as "in hold period" in their earnings so expectations are clear.

## Keeping / protecting a commission (reversal policy)

**What it does.** A commission may be explicitly **Protected** while continuing through Payable and Paid. Protection blocks automated reductions from refunds, lost disputes, and other reversals. The attempted event is recorded as a manual-review item, and an authorized merchant may preserve or manually adjust the commission with a reason and audit trail.

Existing programs may also use these campaign-level compatibility policies:

| Policy                      | Behavior                                                                                                    |
| --------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Auto clawback** (default) | Automated refund and lost-dispute events reduce the commission unless it is Protected                       |
| **Keep on refund**          | Refund events are preserved for compatibility; lost disputes still adjust unless Protected                  |
| **Keep all**                | Legacy automated reductions are preserved for compatibility; explicit protection remains a separate control |

Explicit protection takes precedence over every automated policy. The legacy policies remain supported for existing programs but are not the preferred configuration for new programs. Every preserved or adjusted outcome is appended to the commission history rather than rewriting the original award.

## Choosing settings

* Conservative (protect margin): a hold period covering your return window + *Auto clawback*.
* Affiliate-friendly: a shorter or zero hold + *Keep on refund* (you absorb refund risk to keep affiliates happy).

## Related

* [How refunds, returns & chargebacks affect commissions](https://github.com/wand-referrals-app/wand-referrals/tree/codex/gitbook-docs-foundation/docs/manual/reversals/refunds-returns-chargebacks/README.md)
* [Clawback — reclaim or waive paid commissions](https://github.com/wand-referrals-app/wand-referrals/tree/codex/gitbook-docs-foundation/docs/manual/reversals/clawback/README.md)
* [Creating a program](https://github.com/wand-referrals-app/wand-referrals/tree/codex/gitbook-docs-foundation/docs/manual/programs/creating-a-program/README.md)