> 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/finance/your-subscription/how-are-volume-usage-rates-calculated.md).

# 如何计算用量费用率？

impact.com 使用付款处理量（PPV）作为衡量我们为您的项目处理付款数量的指标。当您的已处理量超过您购买的 PPV 档位时，我们可能会收取增量处理量费用（或超额费用）。

#### 简而言之

* impact.com 会每月持续记录我们为您的项目处理的实际 PPV。
* 在每月结束时，impact.com 会将您的实际 PPV 与您购买的 PPV 档位进行比较。
* 如果您的项目的实际 PPV 超过了您分配的 PPV，我们将计算增量增长费用。

#### 增量增长费用计算

impact.com 在计算增量增长费用时使用以下主要因素：

|                         |                 |
| ----------------------- | --------------- |
| 您在适用期间的实际 PPV 值         | `实际值`           |
| 适用期间购买的 PPV             | `已购`            |
| 适用于超出已购 PPV 量的 PPV 的百分比 | `百分比`           |
| 增量增长费用                  | `（实际值 - 已购）百分比` |

{% hint style="info" %}
**示例：** 对于标准的每月付款处理量，增量增长费用按以下方式计算：额外每月付款处理量的 15.4%（例如，额外付款处理增量为 `$10,000 x 0.154 = $1,540`).

假设您的标准每月付款处理量档位为 $17,500。在某个月内，我们汇总得出为您的账户处理了价值 $20,000 的付款。

增量增长费用计算如下 `($20,000 - $17,500) x 15.4% = $385`.

该金额将作为下一张发票上的一项额外行项目。
{% endhint %}

#### 付款类型

付款处理量（PPV）一词包括通过 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) | 除佣金外支付的额外绩效奖金。                                            |
| 最低 EPC 成本                                                                                                                                                                        | 与每次点击最低收益（EPC）相关的成本。                                      |
| 陈列费                                                                                                                                                                              | 与收取陈列费或排位费的合作伙伴相关的成本。这些成本是按月滞后计费，并根据合同在计费周期内实际生效的天数按比例分摊。 |
| [合作伙伴资金转账](/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/finance/your-subscription/view-your-usage-volume-by-status-and-transaction-type.md).
* 查看您的 [*计划使用情况*](/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/your-subscription/view-your-impactcom-subscription-and-usage-details.md#view-your-usage-details-0-2) 在……上的详细信息 *订阅* 界面中进行设置。


---

# 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/finance/your-subscription/how-are-volume-usage-rates-calculated.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.