> 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).

# 账单组概览

您可以使用计费组来帮助您管理在各个项目中伙伴费用和平台费用的开票和付款方式。每个计费组都可以关联一个特定的资金账户，您可按需更新。

<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 %}

#### 前提条件

* 您必须有多个项目。
* 您需要分别开具发票，或者需要通过不同的资金账户为每个项目注资，以便分别为不同项目的费用开票。

#### 主要功能

计费组功能允许您执行以下操作：

* [创建](/brand/zh/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/create-a-billing-group.md) 和 [编辑](/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.