# Stripe: Payout Itemized 3 ## Description * Modeled after the [titular report](https://stripe.com/docs/reports/balance#schema-payouts-itemized-3) from Stripe, each record represents a payout and its additional details such as expected arrival date and current status. This report belongs to the class of Balance reports. The Balance report is similar to a bank statement, helping you to reconcile your Stripe balance at the end of the month. 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. The Payout Itemized report information on each payout made to your bank account. ## Supported Data Sources * Stripe ## Columns | Type | Name | Description | | -------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | STRING | payout\_id | The Stripe object to which this transaction is related. | | DATETIME | 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. | | STRING | currency | Three-letter ISO code for the currency in which gross, fee and net are defined. | | STRING | balance\_transaction\_id | Unique identifier for the balance transaction. Specifically for Payout, the relation is the ID of the balance transaction that describes the impact of this payout on your account balance. | | INTEGER | gross | Gross amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | INTEGER | fee | Fees paid for this transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | INTEGER | net | Net amount of the transaction. Expressed in major units of the currency (e.g. dollars for USD, yen for JPY). | | STRING | reporting\_category | Reporting Category is a new categorization of balance transactions, meant to improve on the current type field. | | STRING | description | An arbitrary string attached to the balance transaction. Often useful for displaying to users. | | DATETIME | payout\_expected\_arrival\_date | Date the payout is scheduled to arrive in the bank. This factors in delays like weekends or bank holidays. | | STRING | 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. | | DATETIME | 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. | | STRING | payout\_type | Can be bank\_account or card. | | STRING | payout\_description | An arbitrary string attached to the payout. Often useful for displaying to users. | | STRING | payout\_destination\_id | ID of the bank account or card the payout was sent to. | | STRING | source\_relation | The source where this data was pulled from. If you are making use of the `union_schemas` variable, this will be the source schema. If you are making use of the `union_databases` variable, this will be the source database. If you are not unioning together multiple sources, this will be an empty string. |