> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/performance-bonus/performance-bonus-faq.md).

# 绩效奖金常见问题

<a href="https://pxa.impact.com/student/activity/1117596?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=con-350&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

使用绩效奖金为您的合同添加更高或额外的支付费率。这可以激励合作伙伴为您的项目带来更多收入或行为。

* 绩效奖金在您的模板条款中指定，并与某种事件类型相关联。
* 您可以查看您的 [绩效奖金支付](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/performance-bonus/view-performance-bonus-payouts-and-reports.md) 随时在 *财务* 平台中的该部分。

<details>

<summary>当我将绩效奖金添加到生效中的合同中时会发生什么？</summary>

如果您将绩效奖金添加到生效中的模板条款中，所有已签署该合同的合作伙伴都会收到通知，并被提示接受您的新条款。在 [变更通知期](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/set-and-manage-template-terms-rules.md#template-terms-rules-0-1)之后，任何先前已签署的合作伙伴将自动加入该合同。

</details>

<details>

<summary>绩效奖金如何影响支付？</summary>

在为您的绩效奖金创建层级时，奖金金额将被计算为模板条款的 *默认返佣* 和 *默认返佣* 您为绩效奖金层级设置的金额与模板条款的 *默认返佣* **不会改变** 当达到某个绩效奖金层级时——总支付金额会发生变化。

</details>

<details>

<summary>绩效奖金如何计算？</summary>

impact.com 会按月计算最终绩效奖金，适用于 [已锁定的操作](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/understand-the-action-life-cycle-and-finance.md)。确定绩效奖金何时生成取决于合同中指定的锁定期。此外，impact.com 会增加 3 天缓冲，以应对潜在的系统或处理延迟。

{% hint style="warning" %}
**默认支付金额与总支付金额：** 请记住，绩效奖金规则 **不会更改默认付款**——总支付金额会发生变化。
{% endhint %}

</details>

<details>

<summary>你能举个例子吗？</summary>

合作伙伴 A 签署了一份合同，该合同为每笔在线销售/CPA 订单提供默认固定支付金额 200 美元，并设置了三级绩效奖金，可在超过各层级后的行为上提高支付金额：

* `如果行为数达到 1-10，则默认支付金额为每项 1000 美元`
* `如果行为数达到 11-15，则默认支付金额为每项 2000 美元`
* `如果行为数达到 16-20，则默认支付金额为每项 5000 美元`

在某个月中，合作伙伴 A 产生了 20 个行为，这意味着每项 5000 美元的奖金适用。这个固定金额会覆盖默认支付金额，而不会叠加到默认支付金额上。

如果合作伙伴 A 在待处理期间有行为被撤销，导致其数量降至 20 以下，那么他们只能获得每项 2000 美元的支付金额。

</details>

#### 其他资源

要了解更多有关向合同添加绩效奖金或查看支付金额和报告的信息，请查看以下文章：

* [向合同添加绩效奖金](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/performance-bonus/add-a-performance-bonus-to-a-contract.md)
* [查看绩效奖金支付金额和报告](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/performance-bonus/view-performance-bonus-payouts-and-reports.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/performance-bonus/performance-bonus-faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
