> 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/ja/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/assign-primary-finance-contact.md).

# 主要財務担当者を割り当てる

<a href="https://pxa.impact.com/student/activity/1087833?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=con-250&#x26;utm_campaign=help-center" class="button primary">PXAコースを受講する</a>

メインの財務連絡先は、アカウントの請求に関するすべての問題についての主な窓口です。メインの財務連絡先を設定するには、ユーザーをimpact.comアカウントに招待し、次の権限を付与します。 *財務* 権限。この権限により、請求書、支払いリクエスト、財務レポートにアクセスできるようになります。詳しくは、ユーザーをアカウントに [招待する方法](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/invite-account-users.md) および [アクセス権を編集する方法](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/account-administration/account-settings/invite-and-manage-users/understanding-user-management-as-a-brand.md).

1. 上部のナビゲーションバーから、 **残高** → **設定** → [**一般**](https://app.impact.com/secure/advertiser/finance/fr/customer-settings-general-view.ihtml?u=%2Fsecure%2Ffinance%2Fapp%2Fcustomer-settings-general-view.ihtml).
2. 「 *財務連絡先* 」セクションの *メインの連絡先*で、 **既存のアカウントユーザー** を選択するか、 **その他の連絡先**.
   * メインの財務連絡先には、メール配信が設定されているすべての書類が自動的に送信されます。この既定の設定は、書類ごとにいつでも変更できます。
3. 必要に応じて、財務連絡先を追加できます。
4. を選択します。 **保存**.

{% hint style="warning" %}
**重要：** ここで連絡先情報を更新しても、すべての書類に登録されている連絡先が更新されるわけではありません。各書類に対応する設定ページで、連絡先情報を個別に更新する必要があります。
{% endhint %}

<div data-with-frame="true"><figure><img src="https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FgARfjJYDmh0zZoTe0cug%2FScreenshot%202026-07-28%20at%2010.24.48.png?alt=media&amp;token=c7d95d87-4155-4be7-8748-35cf5596bfe3" alt="" width="563"><figcaption></figcaption></figure></div>

詳しくは、以下をご覧ください： [impact.com手数料の書類設定](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/manage-impactcom-fees-document-settings.md), [パートナー手数料の書類設定](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/manage-partner-fees-document-settings.md)および [資金口座の書類設定](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/finance/add-funds-to-your-funding-account/manage-funding-account-document-settings-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/ja/what-would-you-like-to-learn-about/platform-features/finance/finance-settings/assign-primary-finance-contact.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.
