> 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/finance-settings/beta-billing-groups-overview.md).

# 账单组概览

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FQGXWz7Mrs2AYjU8gbGU7%2Fpay-350-2.mp4?alt=media&token=eaa9eefa-46a8-4e56-9410-a92b1cfbd4db>" %}

您可以使用账单组来管理不同计划中的合作伙伴费用和平台费用如何开票及支付。每个账单组都可以关联一个特定的资金账户，您可以根据需要更新该账户。

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-83e55d3fc1ad704139fce857729f66b0e69ff9c2%2F7e6285c61d7b5bb6a0b8483d3ed43ca4926a8f524b7d16499b23a4336a0114cf.svg?alt=media" alt=""><figcaption></figcaption></figure></div>

{% hint style="success" icon="memo-circle-info" %}
**注意：** 如果您创建新的账单组，之前已处理的付款和发票仍会保留在关联的账单组中，不会转移到新的账单组；只有即将发生的付款和发票会分配到新的账单组。
{% endhint %}

#### 前提条件

* 您必须拥有多个计划。
* 如果您需要单独开具发票，或者需要使用不同的资金账户为各个计划提供资金，则可以分别开具不同计划的费用发票。

#### 主要功能

账单组功能支持您执行以下操作：

* [创建](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/create-a-billing-group.md) 和 [编辑](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/beta-manage-billing-groups-and-funding-accounts-as-a-brand.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/finance/finance-settings/beta-billing-groups-overview.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.
