# Balance summary report

Reconcile your Stripe balance and download your categorized transaction history.

The [Balance summary report](https://dashboard.stripe.com/reports/balance) works like a bank statement, helping you reconcile your Stripe balance at the end of each month. You can export an itemized CSV of your complete transaction history, including any associated custom metadata. Transactions appear in your settlement currency after any required foreign currency conversion.

This report doesn’t associate payouts with payment transactions. It includes all transactions and payouts that occurred during the selected period. If you use automatic payouts and need to reconcile the transactions associated with each payout, use the [Payout reconciliation report](https://docs.stripe.com/reports/payout-reconciliation.md) instead. It includes transactions prior to the selected period that are associated with payouts during the selected period. To compare report types, see [Select a report](https://docs.stripe.com/reports/select-a-report.md#reconciliation).

## Export data

You can export the Balance summary report in PDF or CSV format.

### Export PDF

To export a summary PDF, click **Export** in the upper-right corner of the **Balance summary** or **Balance change from activity** section, then select **PDF**. If prompted, select **Summary**.

A summary PDF includes complete summary data from the **Balance summary**, **Balance change from activity**, and **Payouts** sections.

To include itemized transaction data, click **Export** in the **Balance change from activity** section, select **PDF**, then select **Itemized**. An itemized PDF includes the same complete summary data and the first 5,000 rows of itemized **Balance change from activity** data. To export all itemized rows, export the data as a CSV file.

PDF export isn’t available for Stripe accounts based in India.

### Export to CSV

To export data from a report section as a CSV file, click **Export** in the section’s upper-right corner, then select **CSV**. CSV files contain data only from the section where you start the export.

The **Balance summary** section provides only a summary CSV. The **Balance change from activity** and **Payouts** sections offer two report formats:

### Customize exported columns

You can customize the columns that appear in the reports when you export them in the Dashboard or through the [Reporting API](https://docs.stripe.com/reports/api.md). The available columns in each type of report are described below.

### 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. |
| balance_type |  | The type of balance this transaction belongs to (for example, payments, issuing, corporate_card). |
| 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). |
| fee_net_of_withheld_tax |  | The Stripe processing fee after removing withheld tax. Calculated as fee minus withheld_tax — represents Stripe's actual processing charge excluding any tax withheld. |
| fee_transaction_id |  | Fee Transaction ID associated with the credit. |
| 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. |
| is_managed_payments |  | Whether this transaction was processed through Stripe Managed Payments. True when the charge was handled via Stripe Managed Payments, regardless of whether any tax was withheld. |
| 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. |
| withheld_tax |  | Sales tax, VAT or GST withheld. This amount is already included within the fee column. |

### 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`. |

### Additional columns

Itemized reports you can download from the Dashboard include the following additional columns:

### Additional columns for itemized reports

- **Product IDs**: The unique identifiers of the products associated with the transaction.
- **Product Names**: The names of the products associated with the transaction.
- **Country**: The country associated with the transaction. For card payments, this is the card’s country of issuance or billing address country. For local payment methods, it’s inferred from the payment method type. For multi-region payment methods like SEPA or PayPal, it defaults to your account country.

## Schedule reports

If you frequently download the same report, you can schedule report exports to occur on a daily, weekly, or monthly basis. Learn how to [set up scheduled reports](https://docs.stripe.com/reports/options.md#scheduled-reports).

## Report sections

Use [controls](https://docs.stripe.com/reports/options.md) to select the date range, currency, and time zone for your report. The following table describes each report section:

| Section | Description |
| --- | --- |
| **Balance summary** | 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 available, pending, and reserved funds (if applicable). |
| **Balance change from activity** | Shows a detailed breakdown of your transactions by [reporting category](https://docs.stripe.com/reports/reporting-categories.md). This section includes all transactions that affect your balance, except payouts: charges, refunds, disputes, other adjustments, and fees. |
| **Payouts** | Shows the quantity and total amount of payouts to your bank account during the period. Download a list of individual payout transactions by clicking **Export**. |

> #### Connect platforms
> 
> Activity breakdown is available only when a Connect platform views its platform account report. The amounts reflect activity in the platform account’s Stripe balance; activity breakdown isn’t available for reports scoped to connected accounts. In the **Balance change from activity** section, click an amount to review summary totals and audit individual transactions. Learn more about [activity breakdown](https://docs.stripe.com/reports/activity-breakdown.md).

## Report terminology

The Balance summary uses [Balance Transactions](https://docs.stripe.com/api/balance_transactions/object.md) to calculate opening and closing pending and available balances for the selected reporting period. It uses two dates:

- **Created:** When a transaction begins affecting your Stripe balance. For payments, this usually happens after capture. Creating a `PaymentIntent` doesn’t affect your balance.
- **Available on:** When a transaction’s net amount moves from pending to available. You can generally use available funds for payouts, refunds, transfers, and other balance debits.

A `PaymentIntent` with a [processing status](https://docs.stripe.com/payments/paymentintents/lifecycle.md) means Stripe is still determining whether the payment will succeed or fail. It doesn’t mean the funds are in your pending balance. Funds appear in your pending balance only after Stripe creates a Balance Transaction for the payment. They remain pending until the transaction’s **Available on** date.

## Reporting periods and data availability

Stripe groups account activity by calendar day in the time zone selected for the report, from 12:00 AM through 11:59 PM. Complete data for each day appears in the **Balance summary** tab by 12:00 PM the following day in that time zone. For example, activity from September 16, 2025, is available by 12:00 PM on September 17, 2025, in the selected time zone.

Dashboard reports include only complete days. To report on part of a day, use the [Reporting API](https://docs.stripe.com/reports/api.md).

For API integrations, Stripe sends webhook events when new reporting data is available, at 12:00 AM UTC and 12:00 PM UTC. Learn more about [Reporting API integration patterns](https://docs.stripe.com/reports/api.md).