> 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/cross-channel-performance-insights/optimize-reports/participation-bonus-report-and-bulk-partner-funds-transfers.md).

# 参与奖金报告和批量合作伙伴资金转账

#### 运行参与奖金报告

{% hint style="warning" %}
This feature is only available with specific impact.com editions or add-ons. If you see the ![](https://1651675991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpVKEIcehMut8QKRmaUZu%2Fuploads%2F5ikfGgRSMOFn089EEFxy%2Foptimize.svg%20\(1\).svg?alt=media\&token=91ff61f9-8618-4503-b0df-791e0353d124) **Optimize** icon, your account is eligible for the upgrade. Select the icon and get the Optimize add-on directly in the platform!
{% endhint %}

该 *参与奖金报告* 将向您显示您应通过以下方式向每个合作伙伴发送的金额 [合作伙伴资金转账](/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/partner-funds-transfer/transfer-funds-to-a-partner.md).

由于实际发放参与奖金的流程是手动的，您应该 *认真考虑* 安排此报告按固定间隔运行。了解如何 [安排报告](/brand/zh/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/manage-reports.md).

1. 从左侧导航栏中选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1e02b2659c94fa0756772cc6c1880977fc9aba73%2F6ad16bf9b7edb0a28ab3574d313014f32392aa7f9508686b63bfacfafc7a9735.svg?alt=media) **\[Optimize]**.
2. 在左侧导航菜单中，选择 **付款 → 参与奖金**.
3. 设置 *日期范围* 将筛选条件设为介于您上次发放参与奖金的时间和今天之间。
   * 如果这是您第一次发放参与奖金，请将开始日期设为您在模板条款中设置付款调整的日期。
4. 设置 *互动类型* 筛选出您要发放参与奖金的对象。
5. 设置 *佣金费率* 将筛选条件设为与您在 *第4步* 在 *调整参与奖金的付款* 上面的部分。
6. 选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-26956d35e17c61868ca8dba76097721fd6066ab4%2F69945c787eb2db89761c82e0cd32fb31d2fc690bfb8592d9a08b7e7983b7445b.svg?alt=media) **\[搜索]**.
7. 记录 *合作伙伴ID* 及其对应的 *合作伙伴奖金* 从报告中获取。您将需要这些字段来创建批量 **合作伙伴资金转账** 文件。

#### 创建并发送批量合作伙伴资金转账

一旦您从报告中获得合作伙伴ID和参与合作伙伴应获得的奖金金额，就可以创建批量合作伙伴资金转账文件来发送这些奖金。了解如何发送单个 [合作伙伴资金转账](/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/partner-funds-transfer/transfer-funds-to-a-partner.md).

1. 在顶部导航中，选择 **您的余额 → 转账**.
2. 在屏幕右上角，选择 **批量上传转账**.
3. 在 *上传 Excel/CSV 文件*中，选择 **选择文件**.
   * 批量 PFT 上传仅支持 .CSV、.XLS 和 .XLSX 文件格式。请在上传前确保文件大小小于 10MB。
4. 在您的电脑中找到并选择该文件。
5. 选择 **提交**.

{% hint style="success" %}
**注意：** 您将收到一封包含批量上传结果的电子邮件。该邮件将列出哪些转账成功、哪些未成功，以及失败转账失败的原因。如果您在提交文件后 48 小时内未收到此邮件，请联系您的 CSM（或 [联系支持团队](https://app.impact.com/support/portal.ihtml)).
{% endhint %}


---

# 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/cross-channel-performance-insights/optimize-reports/participation-bonus-report-and-bulk-partner-funds-transfers.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.