Rapport de solde
De la même façon qu’un relevé bancaire, le rapport de solde vous aide à rapprocher votre solde Stripe en fin de mois. Il fournit un fichier exporté en CSV détaillant l’historique complet de vos transactions et toutes les éventuelles métadonnées personnalisées associées à ces transactions. Les transactions sont toutes exprimées dans la devise de règlement (après conversion en cas de devise étrangère, quelle qu’elle soit).
Le rapport de solde est utile si vous considérez Stripe comme un compte bancaire utilisé à des fins comptables, permettant de rapprocher le solde chaque fin de mois. Si vous avez activé les virements automatiques et que vous préférez rapprocher les transactions réglées dans chaque virement, consultez plutôt le rapport de rapprochement des virements. Vous avez un doute ? Reportez-vous à notre guide pour choisir le rapport approprié.
Pour commencer, sélectionnez une plage de dates à l’aide des commandes situées en haut de l’écran.
La section Récapitulatif du solde affiche votre solde Stripe aux dates de début et de fin de la plage sélectionnée, ainsi qu’une vue d’ensemble de votre activité au cours de cette période. Votre solde inclut les fonds qui sont disponibles, ceux en attente et ceux mis en réserve, le cas échéant.
La section Évolution du solde selon l’activité fournit une ventilation plus détaillée de vos transactions par catégorie de reporting. Elle inclut toutes les transactions, à l’exception des virements qui ont une incidence sur votre solde, notamment les paiements, remboursements, litiges ou autres réajustements, ainsi que les frais.
La section Virements indique la quantité et le montant total des virements effectués sur votre compte bancaire au cours de la période. Vous pouvez télécharger une liste répertoriant chaque virement en cliquant sur le bouton Télécharger.
Téléchargement des données
Vous pouvez télécharger dans un fichier CSV les données affichées dans chaque section du rapport, en cliquant sur le bouton Télécharger situé dans le coin supérieur droit de la section. Les sections Évolution du solde selon l’activité et Virements vous permettent de télécharger plusieurs types de rapports :
- Récapitulatif : cette option télécharge les données au format CSV tel que vous les voyez dans le tableau de bord.
- Détaillé : cette option télécharge la liste complète répertoriant chacune des transactions consolidées dans le tableau de bord. Vous pouvez inclure des métadonnées personnalisées associées à ces transactions pour accélérer le processus de rapprochement.
En outre, vous pouvez télécharger rapidement le détail des données pour une catégorie de transaction. Pour ce faire, survolez la catégorie correspondante avec votre souris et cliquez sur le bouton Télécharger qui s’affiche.
Colonnes disponibles
Vous pouvez personnaliser les colonnes apparaissant dans les rapports que vous téléchargez depuis le tableau de bord ou via l’API de reporting. Découvrez ci-dessous les colonnes disponibles dans chaque type de rapport.
- Balance summary
- Balance change from activity summary
- Itemized balance change from activity
- Payouts summary
- Itemized payouts
Balance summary
Type de rapport d'API : balance.summary.1
Nom de colonne | Par défaut | Description |
---|---|---|
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
Type de rapport d'API : balance_change_from_activity.summary.1
Nom de colonne | Par défaut | Description |
---|---|---|
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
Type de rapport d'API : balance_change_from_activity.itemized.3
Nom de colonne | Par défaut | 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 | 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
Type de rapport d'API : payouts.summary.1
Nom de colonne | Par défaut | Description |
---|---|---|
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
Type de rapport d'API : payouts.itemized.3
Nom de colonne | Par défaut | 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 | 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. |