> 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/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/beta-billing-groups-overview.md).
# Billing Groups Overview
You can use billing groups to help you manage how partner and platform fees are invoiced and paid across your various programs. Each billing group can have a specific funding account associated with it which you can update as needed.
{% hint style="success" icon="memo-circle-info" %}
**Note:** Should you create a new billing group, any previously processed payments and invoices will remain in the associated billing group and will not be moved to the new billing group; only upcoming payments and invoices will be allocated to the new billing group.
{% endhint %}
#### Pre-requisites
* You must have more than one program.
* You need separate invoices or you need to fund each program from different funding accounts to invoice costs from different programs separately.
#### Key features
The billing group feature allows you to do the following:
* [Create](/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/create-a-billing-group.md) and [edit](/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/beta-manage-billing-groups-and-funding-accounts-as-a-brand.md) multiple billing groups by assigning which programs' costs are to be associated with each group.
* Create a funding account for each billing group (that can also be used to fund other billing groups).
* Manage document settings for each billing group.
* Filter partner invoices by billing group.
---
# 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/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/beta-billing-groups-overview.md?ask=&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.
