Balance report

Reconcile your Stripe balance and download your categorized transaction history.

The Balance report is similar to a bank statement, helping you to reconcile your Stripe balance at the end of the month. It provides an itemized CSV export of your complete transaction history and any custom metadata associated with those transactions. All transactions are shown in your settlement currency (after any foreign currency conversion).

The Balance report is most useful if you treat Stripe like a bank account for accounting purposes, reconciling the balance at the end of each month. If you have automatic payouts enabled and prefer to reconcile the transactions settled in each payout, see the Payout reconciliation report instead. Not sure? Check out our guide to choosing the right report.

To get started, use the controls at the top of the screen to select a date range.

The Balance summary section shows your starting and ending Stripe balance for the selected date range, along with a high level summary of your activity during the period. Your balance includes funds that are available, pending, and any reserved funds, if applicable.

The Balance change from activity section provides a more detailed breakdown of your transactions by reporting category. This section includes all transactions except for payouts that affect your balance, including charges, refunds, disputes, other adjustments, and fees.

The Payouts section provides the quantity and total amount of payouts to your bank account during the period. You can download a list of individual payout transactions by clicking the Download button.

Downloading data

You can download the data displayed in each section of the report as a CSV file by clicking the Download button in the upper right corner of that section. The Balance change from activity and Payouts sections allow you to download multiple types of reports:

Summary: This downloads data in CSV format exactly as you see it in the dashboard.
Itemized: This downloads the full list of individual transactions that are summarized in the dashboard. You can include custom metadata associated with those transactions to speed up the reconciliation process.

In addition, you can quickly download itemized data for a single category of transactions by hovering over that category and clicking the Download button that appears.

Available columns

You can customize the columns that appear in the reports when downloading them in the dashboard or via the Reporting API. The available columns in each type of report are described below.

Balance summary
Balance change from activity summary
Itemized balance change from activity
Payouts summary
Itemized payouts

Balance summary

API report type: balance.summary.1

Column name	Default	Description
category		One of `starting_balance`, `ending_balance`, `activity` or `payouts`.
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).
currency		Three-letter ISO code for the currency in which `net_amount` is defined.

Balance change from activity summary

API report type: balance_change_from_activity.summary.1

Column name	Default	Description
reporting_category		Reporting Category is a new categorization of balance transactions, meant to improve on the current `type` field.
currency		Three-letter ISO code for the currency in which `gross`, `fee` and `net` are defined.
count		The number of transactions associated with the `reporting_category`.
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).
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).
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).

Itemized balance change from activity

API report type: balance_change_from_activity.itemized.3

Column name	Default	Description
balance_transaction_id		Unique identifier for the balance transaction.
created_utc		Time at which the balance transaction was created. Dates in UTC.
created		Time at which the balance transaction was created. 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.
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.
currency		Three-letter ISO code for the currency in which `gross`, `fee` and `net` are defined.
gross		Gross amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY).
fee		Fees paid for this 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).
reporting_category		Reporting Category is a new categorization of balance transactions, meant to improve on the current `type` field.
source_id		The Stripe object to which this transaction is related.
description		An arbitrary string attached to the balance transaction. Often useful for displaying to users.
customer_facing_amount		For transactions associated with charges or refunds, the amount of the original charge or refund.
customer_facing_currency		For transactions associated with charges or refunds, the three-letter ISO code for the currency for `customer_facing_amount`.
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.
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).
automatic_payout_effective_at_utc		The date we expect this automatic payout to arrive in your bank account, in UTC. This is also when the paid-out funds are deducted from your Stripe balance.
automatic_payout_effective_at		The date we expect this automatic payout 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.
customer_id		The unique ID of the related customer, if any.
customer_email		Email address of the customer, if any, associated with this balance transaction.
customer_name		Name of the customer, if any, associated with this balance transaction.
customer_description		Description provided when creating the customer, often used to store the customer name.
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_city		City of the shipping address associated with this charge, if any
shipping_address_state		State 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_country		Country of the shipping address associated with this charge, if any
charge_id		Unique identifier for the original charge associated with this balance transaction. Available for charges, refunds and disputes.
payment_intent_id		The unique ID of the related Payment Intent, if any.
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_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.
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.
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.
payment_method_type		The type of payment method used in the related payment.
card_brand		Card brand, if applicable.
card_funding		Card funding type, if applicable.
card_country		Two-letter ISO code representing the country of the card.
statement_descriptor		The dynamic statement descriptor or suffix specified when the related charge was created.
dispute_reason		Reason given by cardholder for dispute. Read more about dispute reasons.
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.
connected_account_country		For Stripe Connect activity related to a connected account, the two-letter ISO code representing the country of the account.
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.
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.
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.1

Column name	Default	Description
reporting_category		Reporting Category is a new categorization of balance transactions, meant to improve on the current `type` field.
currency		Three-letter ISO code for the currency in which `gross`, `fee` and `net` are defined.
count		The number of transactions associated with the `reporting_category`.
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).
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).
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).

Itemized payouts

API report type: payouts.itemized.3

Column name	Default	Description
payout_id		The Stripe object to which this transaction is related.
effective_at_utc		For automatic payouts, this is the date we expect funds to arrive in your bank account. For 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.
effective_at		For automatic payouts, this is the date we expect funds to arrive in your bank account. For 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.
currency		Three-letter ISO code for the currency in which `gross`, `fee` and `net` are defined.
gross		Gross amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY).
fee		Fees paid for this 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).
reporting_category		Reporting Category is a new categorization of balance transactions, meant to improve on the current `type` field.
balance_transaction_id		Unique identifier for the balance transaction.
description		An arbitrary string attached to the balance transaction. Often useful for displaying to users.
payout_expected_arrival_date		Date the payout is scheduled to arrive in the bank. This factors in delays like weekends or bank holidays.
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_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_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_type		Can be `bank_account` or `card`.
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.
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.