# Query connected account data

Use Sigma and Data Pipeline to retrieve connected account information.

*Connect* (Connect is Stripe's solution for multi-party businesses, such as marketplace or software platforms, to route payments between sellers, customers, and other recipients) platforms can report on their connected accounts using Sigma or Data Pipeline. You can write queries that run across your entire platform in much the same way as your own Stripe account.

Additional groups of Connect-specific tables within the schema are located in the **Connect** sections of the schema. If you don’t operate a Connect platform, these tables aren’t displayed.

## Connected account information

The `connected_accounts` table provides a list of [Account](https://docs.stripe.com/api.md#account_object) objects with information about connected accounts. This table is used for account-level information across all accounts on your platform, such as [business name](https://docs.stripe.com/api.md#account_object-business_name), [country](https://docs.stripe.com/api.md#account_object-country) or the user’s [email address](https://docs.stripe.com/api.md#account_object-email).

The following example uses the `connected_accounts` table to retrieve a list of five accounts for individuals located in the US that have *payouts* (A payout is the transfer of funds to an external account, usually a bank account, in the form of a deposit) disabled because Stripe doesn’t have the [required verification information](https://docs.stripe.com/connect/required-verification-information.md) to [verify their account](https://docs.stripe.com/connect/identity-verification.md).

```sql
  select
    id,
    email,
    legal_entity_address_city as city,
    legal_entity_address_line1 as line1,
    legal_entity_address_postal_code as zip,
    legal_entity_address_state as state,
    legal_entity_dob_day as dob_day,
    legal_entity_dob_month as dob_month,
    legal_entity_dob_year as dob_year,
    legal_entity_first_name as first_name,
    legal_entity_last_name as last_name,
    legal_entity_ssn_last_4_provided as ssn_provided,
    tos_acceptance_date as tos_date,
    tos_acceptance_ip as tos_ip,
    legal_entity_personal_id_number_provided as id_provided,
    legal_entity_verification_document_id as document_id
  from connected_accounts
  where legal_entity_type = 'individual'
    and payouts_enabled = false
    and country = 'US'
  limit 5
```

All the required fields for individual accounts in the US are retrieved as columns. This allows you to see what information has been provided, and what’s needed, for each account. This can be seen in the example report below (some columns have been omitted for brevity).

| id            | email                     | city          | … | id_provided | document_id   |
| ------------- | ------------------------- | ------------- | - | ----------- | ------------- |
| acct_orWziM4… | jenny.rosen@example.com   | San Francisco | … | true        | file_orWziM4… |
| acct_orWziM4… | sophia.garcia@example.com |               | … | false       | file_orWziM4… |
| acct_orWziM4… | natalie.davis@example.com | Seattle       | … | true        | file_orWziM4… |
| acct_orWziM4… | ella.thompson@example.com | Austin        | … | false       | file_orWziM4… |
| acct_orWziM4… | james.smith@example.com   |               | … | false       | file_orWziM4… |

## Accounts with requirements

The `connected_accounts` table also contains information about the `requirements` and `future_requirements` for connected accounts. Use the table to retrieve lists of accounts that have requirements currently due and will be disabled soon. Use the `future_requirements` columns to [handle verification updates](https://docs.stripe.com/connect/handle-verification-updates.md).

The following example uses the `connected_accounts` table to retrieve a list of accounts that have upcoming verification updates.

```sql
select
  id,
  business_name,
  requirements_currently_due,
  future_requirements_currently_due
from
  connected_accounts
where
  future_requirements_currently_due != ''
```

| id                    | business_name | requirements_currently_due | future_requirements_currently_due                       |
| --------------------- | ------------- | -------------------------- | ------------------------------------------------------- |
| acct_1orWziM4j7CiRL8J | RocketRides   |                            | business_profile.url                                    |
| acct_1orWziM4j7CiRL8J | Kavholm       |                            | individual.email,settings.payments.statement_descriptor |
| acct_1orWziM4j7CiRL8J | FurEver       | external_account           | settings.payments.statement_descriptor                  |
| acct_1orWziM4j7CiRL8J | Pasha         | business_profile.url       | company.tax_id                                          |

The columns available to query `requirements` and `future_requirements` information are comma-separated lists of requirements on the account.

| requirements                        | future_requirements                        |
| ----------------------------------- | ------------------------------------------ |
| `requirements_past_due`             | `future_requirements_past_due`             |
| `requirements_currently_due`        | `future_requirements_currently_due`        |
| `requirements_eventually_due`       | `future_requirements_eventually_due`       |
| `requirements_pending_verification` | `future_requirements_pending_verification` |

## Transactional data for connected accounts

Sigma and Data Pipeline include a variety of [query templates](https://dashboard.stripe.com/sigma/queries/templates) for Connect platforms. Use these to get started with reporting on your connected accounts.

[Transactional](https://docs.stripe.com/stripe-data/query-transactions.md) and [subscription](https://docs.stripe.com/stripe-data/query-billing-data.md) data for connected accounts is contained within the `connected_account_` tables. The available data for connected accounts is organised and structured in the same way as data for your own account.

For instance, the `balance_transactions` table, located in the **Payments** section, contains balance transaction data for your Stripe account. The `connected_account_balance_transactions` table, located in the **Connect - Payments** section, contains balance transaction data for your connected accounts. Each Connect-specific table has an additional `account` column containing the identifier of a connected account. This can be used when joining tables to build advanced queries.

The following example is based on the default query that’s loaded into the editor. Instead of retrieving the ten most recent balance transactions on your account, it does so across all of your platform’s connected accounts.

```sql
    select
      date_format(created, '%m-%d-%Y') as day,
      account, -- Added to include corresponding account identifier
      id,
      amount,
      currency,
      source_id,
      type
    from connected_account_balance_transactions -- Changed to use Connect-specific table
    order by day desc
    limit 5
```

| day        | account       | id           | amount | currency | source_id   | type   |
| ---------- | ------------- | ------------ | ------ | -------- | ----------- | ------ |
| 19/03/2026 | acct_orWziM4… | txn_orWziM4… | -1,000 | usd      | re_orWziM4… | refund |
| 19/03/2026 | acct_orWziM4… | txn_orWziM4… | 1,000  | usd      | ch_orWziM4… | charge |
| 19/03/2026 | acct_orWziM4… | txn_orWziM4… | 1,000  | usd      | ch_orWziM4… | charge |
| 19/03/2026 | acct_orWziM4… | txn_orWziM4… | 1,000  | eur      | ch_orWziM4… | charge |
| 19/03/2026 | acct_orWziM4… | txn_orWziM4… | -1,000 | usd      | re_orWziM4… | refund |

Refer to our [transactions](https://docs.stripe.com/stripe-data/query-transactions.md) and [subscriptions](https://docs.stripe.com/stripe-data/query-billing-data.md) documentation to learn more about querying transactional and subscription data. You can then supplement or adapt your queries with Connect-specific information to report on connected accounts.

### Query charges on connected accounts

Use Sigma or Data Pipeline to report on the flow of funds to your connected accounts. How you do this depends on your platform’s approach to creating charges.

## Direct charges

If your platform creates [direct charges](https://docs.stripe.com/connect/direct-charges.md) on a connected account, they appear on the connected account, not on your platform. This is analogous to a connected account making a charge request itself. Platforms can use the Connect-specific tables (for example, `connected_account_charges` or `connected_account_balance_transactions`) to report on direct charges.

Access the [direct charges query template](https://dashboard.stripe.com/sigma/queries/templates/Direct%20charges) to retrieve itemised information about application fees earned through direct charges, and reports on the connected account, transfer, and payment that is created.

## Destination charges

If your platform creates [destination charges](https://docs.stripe.com/connect/destination-charges.md) on behalf of connected accounts, charge information is available within your own account’s data. A separate transfer of the funds to the connected account is automatically created, which creates a payment on that account. For example, the [destination charges query template](https://dashboard.stripe.com/sigma/queries/templates/Destination%20charges) reports on transfers related to destination charges made by your platform. One way to analyse the flow of funds from a destination charge to a connected account is by joining the `transfer_id` column of the `charges` table to the `id` column of the `transfers` table. This example includes the original charge identifier and amount, the amount transferred to the connected account, and the connected account’s identifiers and resulting payment.

```sql
select
  date_format(date_trunc('day', charges.created), '%y-%m-%d') as day,
  charges.id,
  charges.amount as charge_amount,
  transfers.amount as transferred_amount,
  transfers.destination_id
from charges
inner join transfers
  on transfers.id=charges.transfer_id
order by day desc
limit 5
```

| day        | id               | charge_amount | transferred_amount | destination_id |
| ---------- | ---------------- | ------------- | ------------------ | -------------- |
| 19/03/2026 | ch_acct_orWziM4… | 1,000         | 1,000              | acct_orWziM4…  |
| 19/03/2026 | ch_acct_orWziM4… | 800           | 800                | acct_orWziM4…  |
| 19/03/2026 | ch_acct_orWziM4… | 1,000         | 800                | acct_orWziM4…  |
| 19/03/2026 | ch_acct_orWziM4… | 1,100         | 950                | acct_orWziM4…  |
| 19/03/2026 | ch_acct_orWziM4… | 1,100         | 1,100              | acct_orWziM4…  |

Payment and transfer information for Connected accounts is also available within Connect-specific tables (for example, `connected_account_charges`).

### Separate charges and transfers

Report on [separate charges and transfers](https://docs.stripe.com/connect/separate-charges-and-transfers.md) using a similar approach to destination charges. All charges are created on your platform’s account, with funds separately transferred to connected accounts using [transfer groups](https://docs.stripe.com/connect/separate-charges-and-transfers.md). A payment is created on the connected account that references the transfer and transfer group.

Both the `charges` and `transfers` table include a `transfer_group` column. Payment, transfer, and transfer group information is available within the Connect-specific `connected_account_charges` table.