Informe de saldo
El informe de saldo se asemeja al extracto bancario y te ayuda a conciliar el saldo de Stripe a fin de mes. Es posible exportar un CSV pormenorizado del historial completo de transacciones y de los metadatos personalizados asociados con esas transacciones. Todas las transacciones se muestran en tu moneda de cobro (después de cualquier conversión de moneda extranjera).
El informe de saldo es muy útil si tomas la cuenta de Stripe como cuenta bancaria para fines contables, ya que te permite conciliar el saldo a fin de mes. Si tienes habilitadas las transferencias automáticas y prefieres conciliar las transacciones acreditadas en cada transferencia, consulta el informe de conciliación de transferencias. ¿No sabes qué te conviene? Consulta nuestra guía para elegir el informe correcto.
Para empezar, usa los controles que se encuentran en la parte superior de la pantalla para seleccionar el intervalo de fechas.
La sección Resumen de saldo muestra el saldo de Stripe al principio y al final del intervalo de tiempo seleccionado, junto con un resumen general de tu actividad durante ese período. Tu saldo incluye los fondos disponibles, los fondos pendientes y los fondos reservados, según corresponda.
La sección Cambio de saldo conforme a la actividad proporciona un desglose más detallado de tus transacciones por categoría de informe. Esta sección incluye todas las transacciones excepto las transferencias que afectan a tu saldo, y comprende cargos, rembolsos, disputas, otros ajustes y comisiones.
La sección Transferencias te proporciona la cantidad y el importe total de las transferencias a tu cuenta bancaria durante el período. Puedes descargar una lista de transacciones de transferencia individuales haciendo click en el botón Descargar.
Cómo descargar datos
Puedes descargar los datos que aparecen en cada sección del informe como un archivo CSV haciendo click en el botón Descargar ubicado en la esquina superior izquierda de esa sección. Las secciones Cambio de saldo conforme a la actividad y Transferencias te permiten descargar varios tipos de informes:
- Resumen: permite descargar los datos en formato CSV tal como los ves en el Dashboard.
- Pormenorizado: permite descargar la lista completa de transacciones individuales resumidas en el Dashboard. Puedes incluir metadatos personalizados asociados con esas transacciones para acelerar el proceso de conciliación.
Además, puedes descargar de manera rápida datos pormenorizados de una categoría única de transacciones pasando el ratón por encima de esa categoría y haciendo click en el botón Descargar que aparece.
Columnas disponibles
Puedes personalizar las columnas que aparecen en los informes cuando los descargas en el Dashboard o a través de la API Reporting. Se describen a continuación las columnas disponibles en cada tipo de informe.
- Balance summary
- Balance change from activity summary
- Itemized balance change from activity
- Payouts summary
- Itemized payouts
Balance summary
Tipo de informe de API: balance.summary.1
Nombre de la columna | Valor predeterminado | Descripción |
---|---|---|
category | One of | |
description | One of | |
net_amount | Net amount for the transactions associated with | |
currency | Three-letter ISO code for the currency in which |
Balance change from activity summary
Tipo de informe de API: balance_change_from_activity.summary.1
Nombre de la columna | Valor predeterminado | Descripción |
---|---|---|
reporting_category | Reporting Category is a new categorization of balance transactions, meant to improve on the current | |
currency | Three-letter ISO code for the currency in which | |
count | The number of transactions associated with the | |
gross | Sum of the gross amounts of the transactions associated with the | |
fee | Sum of the fees paid for the transactions associated with the | |
net | Sum of the net amounts for the transactions associated with the |
Itemized balance change from activity
Tipo de informe de API: balance_change_from_activity.itemized.3
Nombre de la columna | Valor predeterminado | Descripción |
---|---|---|
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 | 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 | |
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, 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 for | |
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. | |
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_city | City 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 | |
customer_shipping_address_postal_code | Postal code 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_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_city | City 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_address_postal_code | Postal code of the customer address associated with this charge, if any | |
customer_address_country | Country of the customer 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_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 | |
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_city | City 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_address_postal_code | Postal code of the card address associated with this charge, if any | |
card_address_country | Country of the card 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. | |
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. | |
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. | |
is_link | Whether or not the payment was made using Link. | |
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. | |
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. | |
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
Tipo de informe de API: payouts.summary.1
Nombre de la columna | Valor predeterminado | Descripción |
---|---|---|
reporting_category | Reporting Category is a new categorization of balance transactions, meant to improve on the current | |
currency | Three-letter ISO code for the currency in which | |
count | The number of transactions associated with the | |
gross | Sum of the gross amounts of the transactions associated with the | |
fee | Sum of the fees paid for the transactions associated with the | |
net | Sum of the net amounts for the transactions associated with the |
Itemized payouts
Tipo de informe de API: payouts.itemized.3
Nombre de la columna | Valor predeterminado | Descripción |
---|---|---|
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 | 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 | |
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 ( | |
payout_reversed_at_utc | Typically this field will be empty. However, if the payout’s status is | |
payout_reversed_at | Typically this field will be empty. However, if the payout’s status is | |
payout_type | Can be | |
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. |