# 残高サマリーレポート Stripe 残高を照合し、カテゴリ別の取引履歴をダウンロードします。 [残高サマリーレポート](https://dashboard.stripe.com/reports/balance)は銀行明細書と似ており、月末に Stripe 残高との照合に利用できます。全取引履歴とそれらの取引に関連付けられたカスタムメタデータの項目別 CSV エクスポートを提供します。すべての取引は、(外貨換算後) 売上処理通貨で表示されます。 残高サマリーレポートは、Stripe を会計処理用の銀行口座として利用し、各月末の残高を照合する場合に最も役立ちます。自動入金を有効にし、各入金で売上処理された取引を照合する場合は、代わりに[入金照合](https://docs.stripe.com/reports/payout-reconciliation.md)レポートを参照してください。どのレポートを使用するべきか分からない場合は、[ガイド](https://docs.stripe.com/reports/select-a-report.md#reconciliation)をご覧ください。 開始するには、画面上部の[コントロール](https://docs.stripe.com/reports/options.md)を使用して日付範囲を選択します。 **残高のサマリー**セクションには、選択した日付範囲の期首と期末の Stripe 残高が、その期間内のアクティビティの概要とともに表示されます。残高には、利用可能な売上、保留中の売上、および該当する場合はリザーブされた売上が含まれます。 **アクティビティーによる残高変更**セクションでは、[レポートカテゴリー](https://docs.stripe.com/reports/reporting-categories.md)別に取引のより詳細な内訳が表示されます。このセクションには、入金を除き、残高に影響を与える支払い、返金、不審請求の申請、その他の調整、手数料などのすべての取引が含まれます。 **入金**セクションには、期間内の銀行口座への入金の回数と合計金額が表示されます。**ダウンロード**ボタンをクリックすると、個々の入金取引のリストをダウンロードできます。 ## データをダウンロードする レポートのセクションに表示されているデータは、そのセクションの右上隅にある **ダウンロード** をクリックして、CSV ファイルとしてダウンロードできます。**アクティビティによる残高変更** および **入金** セクションでは、複数のタイプのレポートをダウンロードできます。 - **概要**： ダッシュボードに表示されたとおりのデータが CSV 形式でダウンロードされます。 - **明細**： ダッシュボードで要約されている各取引の詳細なリストをダウンロードできます。これらの取引に関連付けられている[カスタムメタデータ](https://docs.stripe.com/reports/metadata.md)を含めることで、照合のプロセスをスピードアップできます。 さらに、取引のうちの単一のカテゴリーにカーソルを合わせて **ダウンロード** をクリックすると、そのカテゴリの項目別データをダウンロードできます。 ## アクティビティの内訳 ダッシュボードで合計サマリーや個々の取引の詳細などのデータを確認できます。**Balance change from activity** セクションで金額をクリックして、基になる取引の監査を行います。この機能は[プラットフォームアカウント](https://docs.stripe.com/connect.md)でのみご利用いただけます。詳しくは[アクティビティの内訳](https://docs.stripe.com/reports/activity-breakdown.md)の詳細をご覧ください。 ## 取得可能なデータ Stripe は、午前 12:00 から毎日お客様のデータを計算します。各日のデータとは、その日の 午前 12:00 から 午後 11:59 の間に発生するアカウントのアクティビティーデータです。 たとえば、2025 年 9 月 16 日 (午前 12:00 から午後 11:59) に行われたすべてのアカウントアクティビティーは、2025 年 9 月 17 日午後 12:00 までに「残高サマリー財務レポート」タブでご確認いただけます。 一部の期間のレポートは [Reporting API](https://docs.stripe.com/reports/api.md) を通じてリクエストできますが、Stripe ダッシュボード上のレポートは常に 1 日単位となります。 また、Stripe は、00:00 UTC と 12:00 UTC のデータがレポートに使用できるようになったときにも Webhook イベントを 1 日に 2 回発行します。詳細については、[Reporting API](https://docs.stripe.com/reports/api.md) 統合パターンを参照してください。 ## スケジュールによるレポート レポートのサブスクリプションスケジュールを設定する方法と、新しいデータに関する通知を受け取る方法については、[スケジュール済みレポート](https://docs.stripe.com/reports/options.md#scheduled-reports)を参照してください。 ## 利用可能な列 ダッシュボードまたは [Reporting API](https://docs.stripe.com/reports/api.md) を使用して、ダウンロードするときにレポートに表示する列をカスタマイズできます。各タイプのレポートで利用可能な列を以下に示します。 ### Balance Summary API report type: balance.summary.2 | Column name | Default | Description | | ----------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | category | ✓ | One of `starting_balance`, `ending_balance`, `activity` or `payouts`. | | currency | ✓ | Three-letter [ISO code for the currency](https://stripe.com/docs/currencies) in which `net_amount` is defined. | | description | ✓ | One of `Starting balance (YYYY-MM-DD)` - the balance at the start of the period, `Activity` - the net amount of all transactions that affected your balance except for payouts, `Total payouts` - the amount of payouts to your bank account, or `Ending balance (YYYY-MM-DD)` - the balance left over at the end of the period after subtracting payouts from the `Starting balance` and `Activity`. | | net_amount | ✓ | Net amount for the transactions associated with `category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | ### Balance change from activity summary API report type: balance_change_from_activity.summary.2 | Column name | Default | Description | | ------------------ | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | count | ✓ | The number of transactions associated with the `reporting_category`. | | currency | ✓ | Three-letter [ISO code for the currency](https://stripe.com/docs/currencies) in which `gross`, `fee` and `net` are defined. | | fee | ✓ | Sum of the fees paid for the transactions associated with the `reporting_category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | gross | ✓ | Sum of the gross amounts of the transactions associated with the `reporting_category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | net | ✓ | Sum of the net amounts for the transactions associated with the `reporting_category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | reporting_category | ✓ | [Reporting Category](https://stripe.com/docs/reporting/reporting-categories) is a new categorization of balance transactions, meant to improve on the current `type` field. | ### Itemized balance change from activity API report type: balance_change_from_activity.itemized.7 | Column name | Default | Description | | ------------------------------------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | application_fee | | Application fee paid to your platform, only relevant for standard connected accounts. | | automatic_payout_effective_at | | The date we expect this [automatic payout](https://stripe.com/docs/payouts#payout-schedule) to arrive in your bank account, in the requested timezone, or UTC if not provided. This is also when the paid-out funds are deducted from your Stripe balance. | | automatic_payout_effective_at_utc | | The date we expect this [automatic payout](https://stripe.com/docs/payouts#payout-schedule) to arrive in your bank account, in UTC. This is also when the paid-out funds are deducted from your Stripe balance. | | automatic_payout_id | | ID of the automatically created payout associated with this balance transaction (only set if your account is on an [automatic payout schedule](https://stripe.com/docs/payouts#payout-schedule)). | | available_on | ✓ | The date the balance transaction's net funds will become available in the Stripe balance. Dates in the requested timezone, or UTC if not provided. | | available_on_utc | | The date the balance transaction's net funds will become available in the Stripe balance. Dates in UTC. | | balance_transaction_id | ✓ | Unique identifier for the balance transaction. | | card_address_city | | City of the card address associated with this charge, if any | | card_address_country | | Country of the card address associated with this charge, if any | | card_address_line1 | | First line of the card address associated with this charge, if any | | card_address_line2 | | Second line of the card address associated with this charge, if any | | card_address_postal_code | | Postal code of the card address associated with this charge, if any | | card_address_state | | State of the card address associated with this charge, if any | | card_brand | | [Card brand](https://stripe.com/docs/api#card_object-brand), if applicable. | | card_country | | Two-letter ISO code representing the country of the card. | | card_funding | | Card [funding type](https://stripe.com/docs/api#account_card_object-funding), if applicable. | | card_network | | Card network, if applicable. | | charge_created | | Creation time of the original charge associated with this balance transaction. Available for charges, refunds and disputes. For charges that were separately authorized and captured, this is the authorization time. Dates in the requested timezone, or UTC if not provided. | | charge_created_utc | | Creation time of the original charge associated with this balance transaction. Available for charges, refunds and disputes. For charges that were separately authorized and captured, this is the authorization time. Dates in UTC. | | charge_id | | Unique identifier for the original charge associated with this balance transaction. Available for charges, refunds and disputes. | | connected_account_country | | For Stripe Connect activity related to a connected account, the two-letter ISO code representing the country of the account. | | connected_account_direct_charge_id | | (Beta) For Stripe Connect activity related to a connected account, charge id of the direct charge that happened on connected account. | | connected_account_id | | For Stripe Connect activity related to a connected account, the unique ID for the account. | | connected_account_name | | For Stripe Connect activity related to a connected account, the name of the account. | | created | ✓ | Time at which the balance transaction was created. Dates in the requested timezone, or UTC if not provided. | | created_utc | | Time at which the balance transaction was created. Dates in UTC. | | currency | ✓ | Three-letter [ISO code for the currency](https://stripe.com/docs/currencies) in which `gross`, `fee` and `net` are defined. | | customer_address_city | | City of the customer address associated with this charge, if any | | customer_address_country | | Country of the customer address associated with this charge, if any | | customer_address_line1 | | First line of the customer address associated with this charge, if any | | customer_address_line2 | | Second line of the customer address associated with this charge, if any | | customer_address_postal_code | | Postal code of the customer address associated with this charge, if any | | customer_address_state | | State of the customer address associated with this charge, if any | | customer_description | | Description provided when creating the customer, often used to store the customer name. | | customer_email | | Email address of the customer, if any, associated with this balance transaction. | | customer_facing_amount | | For transactions associated with charges, refunds, or disputes, the amount of the original charge, refund, or dispute. If the customer was charged in a different currency than your account's default, this field will reflect the amount as seen by the customer. | | customer_facing_currency | | For transactions associated with charges, refunds, or disputes, the three-letter [ISO currency code](https://stripe.com/docs/currencies) for `customer_facing_amount`. | | customer_id | | The unique ID of the related customer, if any. | | customer_name | | Name of the customer, if any, associated with this balance transaction. | | customer_shipping_address_city | | City of the customer shipping address associated with this charge, if any | | customer_shipping_address_country | | Country of the customer shipping address associated with this charge, if any | | customer_shipping_address_line1 | | First line of the customer shipping address associated with this charge, if any | | customer_shipping_address_line2 | | Second line of the customer shipping address associated with this charge, if any | | customer_shipping_address_postal_code | | Postal code of the customer shipping address associated with this charge, if any | | customer_shipping_address_state | | State of the customer shipping address associated with this charge, if any | | description | ✓ | An arbitrary string attached to the balance transaction. Often useful for displaying to users. | | dispute_reason | | Reason given by cardholder for dispute. Read more about [dispute reasons](https://stripe.com/docs/disputes/categories). | | fee | ✓ | Fees paid for this transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | gross | ✓ | Gross amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | invoice_id | | Unique ID for the invoice associated with this balance transaction. Available for charges, refunds, and disputes made in connection with a Stripe Billing invoice. | | invoice_number | | Number for the invoice associated with this balance transaction. Available for charges, refunds, and disputes made in connection with a Stripe Billing invoice. | | is_link | | Whether or not the payment was made using Link. | | net | ✓ | Net amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | payment_intent_id | | The unique ID of the related Payment Intent, if any. | | payment_metadata[key] | | Metadata associated with the related PaymentIntent, if any. If no PaymentIntent metadata exists, metadata from any related charge object will be returned. API requests including this column must specify a metadata key in brackets. This column can be specified multiple times to retrieve data from additional metadata keys. | | payment_method_type | | The type of payment method used in the related payment. | | payout_reference_token | | A unique reference token that displays on the beneficiary's bank statement. | | payout_statement_descriptor | | Extra information that displays on the recipient's bank statement. Most banks truncate this information and display it inconsistently. Some banks might not display it at all. | | refund_metadata[key] | | Metadata associated with the related refund object, if any. API requests including this column must specify a metadata key in brackets. This column can be specified multiple times to retrieve data from additional metadata keys. | | regulatory_tag | | ​​An identifier reflecting the classification of this transaction according to local regulations, if applicable. Accounts with automatic payouts enabled receive a separate payout for each regulatory tag. ​​This column is only populated for Brazilian accounts. | | reporting_category | ✓ | [Reporting Category](https://stripe.com/docs/reporting/reporting-categories) is a new categorization of balance transactions, meant to improve on the current `type` field. | | shipping_address_city | | City of the shipping address associated with this charge, if any | | shipping_address_country | | Country of the shipping address associated with this charge, if any | | shipping_address_line1 | | First line of the shipping address associated with this charge, if any | | shipping_address_line2 | | Second line of the shipping address associated with this charge, if any | | shipping_address_postal_code | | Postal code of the shipping address associated with this charge, if any | | shipping_address_state | | State of the shipping address associated with this charge, if any | | source_id | | The Stripe object to which this transaction is related. | | statement_descriptor | | The dynamic statement descriptor or suffix specified when the related charge was created. | | subscription_id | | Unique ID for the subscription associated with this balance transaction. Available for charges, refunds, and disputes made in connection with a Stripe Billing subscription. | | trace_id | | [Trace ID](https://stripe.com/docs/payouts/trace-id) is a unique identifier generated by bank for the Stripe payouts. Used by banks to locate specific transfers, sometimes referred to as a Reference number. | | trace_id_status | | The status of the trace ID. Either `pending`, `unsupported` or `supported`. | | transfer_metadata[key] | | Metadata associated with the related transfer object, if any. API requests including this column must specify a metadata key in brackets. This column can be specified multiple times to retrieve data from additional metadata keys. | ### Payouts summary API report type: payouts.summary.2 | Column name | Default | Description | | ------------------ | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | count | ✓ | The number of transactions associated with the `reporting_category`. | | currency | ✓ | Three-letter [ISO code for the currency](https://stripe.com/docs/currencies) in which `gross`, `fee` and `net` are defined. | | fee | ✓ | Sum of the fees paid for the transactions associated with the `reporting_category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | gross | ✓ | Sum of the gross amounts of the transactions associated with the `reporting_category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | net | ✓ | Sum of the net amounts for the transactions associated with the `reporting_category`. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | reporting_category | ✓ | [Reporting Category](https://stripe.com/docs/reporting/reporting-categories) is a new categorization of balance transactions, meant to improve on the current `type` field. | ### Itemized payouts API report type: payouts.itemized.5 | Column name | Default | Description | | ---------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | application_fee | | Application fees paid to your platform, only relevant for users on Standard connected accounts. | | balance_transaction_id | ✓ | Unique identifier for the balance transaction. | | currency | ✓ | Three-letter [ISO code for the currency](https://stripe.com/docs/currencies) in which `gross`, `fee` and `net` are defined. | | description | ✓ | An arbitrary string attached to the balance transaction. Often useful for displaying to users. | | effective_at | ✓ | For [automatic payouts](https://stripe.com/docs/payouts#payout-schedule), this is the date we expect funds to arrive in your bank account. For [manual payouts](https://stripe.com/docs/payouts#manual-payouts), this is the date the payout was initiated. In both cases, it's the date the paid-out funds are deducted from your Stripe balance. All dates in the requested timezone, or UTC if not provided. | | effective_at_utc | | For [automatic payouts](https://stripe.com/docs/payouts#payout-schedule), this is the date we expect funds to arrive in your bank account. For [manual payouts](https://stripe.com/docs/payouts#manual-payouts), this is the date the payout was initiated. In both cases, it's the date the paid-out funds are deducted from your Stripe balance. All dates in UTC. | | fee | ✓ | Fees paid for this transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | gross | ✓ | Gross amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | net | ✓ | Net amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | payout_description | | An arbitrary string attached to the payout. Often useful for displaying to users. | | payout_destination_id | | ID of the bank account or card the payout was sent to. | | payout_expected_arrival_date | ✓ | Date the payout is scheduled to arrive in the bank. This factors in delays like weekends or bank holidays. | | payout_id | ✓ | The Stripe object to which this transaction is related. | | payout_reversed_at | | Typically this field will be empty. However, if the payout's status is `canceled` or `failed`, this field will reflect the time at which it entered that status. Times in the requested timezone, or UTC if not provided. | | payout_reversed_at_utc | | Typically this field will be empty. However, if the payout's status is `canceled` or `failed`, this field will reflect the time at which it entered that status. Times in UTC. | | payout_status | ✓ | Current status of the payout (`paid`, `pending`, `in_transit`, `canceled` or `failed`). A payout will be `pending` until it is submitted to the bank, at which point it becomes `in_transit`. It will then change to `paid` if the transaction goes through. If it does not go through successfully, its status will change to `failed` or `canceled`. | | payout_type | | Can be `bank_account` or `card`. | | regulatory_tag | | ​​An identifier reflecting the classification of this transaction according to local regulations, if applicable. Accounts with automatic payouts enabled receive a separate payout for each regulatory tag. ​​This column is only populated for Brazilian accounts. | | reporting_category | ✓ | [Reporting Category](https://stripe.com/docs/reporting/reporting-categories) is a new categorization of balance transactions, meant to improve on the current `type` field. | | trace_id | | [Trace ID](https://stripe.com/docs/payouts/trace-id) is a unique identifier generated by bank for the Stripe payouts. Used by banks to locate specific transfers, sometimes referred to as a Reference number. | | trace_id_status | | The status of the trace ID. Either `pending`, `unsupported` or `supported`. | ### 追加された列 ダッシュボードからダウンロードできる項目別レポートには、次の追加された列があります。 ### 項目別レポートに追加された列 - **Product ID**: 取引に関連付けられた製品を特定する一意の識別子。 - **Product Names**: 取引に関連付けられた製品の名称。 - **Country**: 取引に関連付けられた国。カード決済の場合、これはクレジットカードの発行国または請求先住所の国です。国内主要決済手段の場合、決済手段の種類から推測されます。SEPA や PayPal などの複数地域で利用される決済手段の場合、デフォルトはお客様のアカウントが所在する国です。