> 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/agency/ja/what-would-you-like-to-learn-about/finance/finance-settings-overview-for-agencies.md).

# 代理店向け経理設定の概要

あなたの **財務設定** は、財務担当者を割り当てたり、請求書設定を行ったり、その他の設定をしたりできる場所です。

#### 財務設定を見つける

1. 左側のナビゲーションメニューから、選択します ![](https://2576906605-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTNfAIjBtFchXJ9pC2q%2Fuploads%2Fgit-blob-2353e6dbc5652c0304edc7da554b01277ad88839%2F380bebd18697484deff243a63d0ed3fda5b8b3ae7a5d1da26278c64764d33cd9.svg?alt=media) **\[メニュー] → 財務**.
2. 〜から *財務* ナビゲーションメニューから選択します **設定** **→** 管理したい設定グループ。

|                                                                                                                                                                                                         |                                                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **設定**                                                                                                                                                                                                  | **説明**                                                                                                                                                 |
| [法人](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/create-and-manage-your-legal-entities#create-a-legal-entity)                           | 請求先住所や税務情報など、法人情報を管理・編集します。                                                                                                                            |
| [請求グループ](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/beta-billing-groups-overview#key-features)                                         | ここで請求グループを管理します。名前や資金口座を編集したり、表示したりできます [書類設定](/agency/ja/what-would-you-like-to-learn-about/finance/manage-document-settings-as-an-agency.md) この画面から。 |
| [資金口座](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/finance/add-funds-to-your-funding-account/your-funding-account-overview-explained#required-funding-scenarios) | ここで資金口座を管理します。名前を編集し、どの通貨と請求グループに属しているかを確認できます。                                                                                                        |


---

# 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/agency/ja/what-would-you-like-to-learn-about/finance/finance-settings-overview-for-agencies.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.