# Settlement Breakdown Report The Settlement Breakdown Report shows all financial movements that relate to a specific settlement. --- ## Report availability The Settlement Breakdown Report is created when your settlement is generated, between midnight and 2:00 AM in your entity's [settlement time zone](https://www.checkout.com/docs/funds-management/receive-settlements.md#Settlement_time_zone). A report is created for each settlement, in line with your specified [settlement schedule](https://www.checkout.com/docs/funds-management/receive-settlements.md#Settlement_schedule). For example, your settlement time zone is `America/Los_Angeles` Pacific Time (PT) and your settlement schedule is daily. - You receive a `USD` settlement from Checkout.com on August 4 with the payout ID `00000000CFJU`. - The report with the report ID `00000000CFJU` on August 4 explains that settlement, including all financial movements in USD from August 3, midnight to 11:59 PM PT. - The report is available by midnight PT on August 4. See instructions on how to download the report on demand or on a schedule: - [Using the API](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Retrieve_reports_via_API) - [Using Secure File Transfer Protocol](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Access_reports_via_SFTP) (SFTP) - [Using webhooks](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Receive_reports_using_webhooks) --- ## Report format The report is provided as a CSV file. By default, the file name uses the following format: - API and SFTP – `settlement-breakdown_{EntityID}_{Payout Date: YYYYMMDD}_{PayoutID}_1.csv` - Dashboard scheduled reports – `settlement-breakdown__{Your Entity-ID}_{Payout date: YYYYMMDD}_{PayoutID}_1.csv` For SFTP, the report is uploaded in the following folder structure:
`{Entity_name} > reports-{Entity_name} > settlement-breakdown` --- ## Sample report [Download a sample Settlement Breakdown Report](https://www.checkout.com/docs/files/Sample-Settlement-Breakdown.csv) (CSV file). > **Information** > > If using Safari, hold down the _Option_ key when selecting the link to download the file. --- ## Report fields The report can include the following fields in this order: | Field name | Description | | --- | --- | | Client Entity ID
`string` | The unique identifier for the entity the financial movement was processed for, prefixed with `ent_`. | | Client Entity Name
`string` | The name of the entity the financial movement was processed for. | | Processing Channel ID
`string` | The [processing channel's](https://www.checkout.com/docs/business-operations/use-the-dashboard/manage-processing-channels.md) unique identifier, prefixed with `pc_`. | | Processing Channel Name
`string` | The processing channel's name. | | Type
`string` | The type of financial movement processed.
Example – `Partial Refund` | | Payment ID
`string` | The unique identifier for the payment the financial movement relates to, prefixed with `pay_`. | | Reference
`string`
`optional` | Your reference for the payment as provided in the payment request.

If you provide multiple references relating to one payment, Checkout.com relates the reference to the latest financial movement.

For example, if you provide different references on authorization and then on capture, Checkout.com relates the reference to the capture. | | Processed On
`date-time` | The date and time when the financial movement is reflected in your _Pending_ balance, in your settlement time zone.

This is not the time when you requested the payment.

If the funds do not enter _Pending_ and go directly into _Available_, this is the date and time when the financial movement is reflected in your _Available_ balance.

Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Available On
`date-time` | The date and time when the financial movement is reflected in your _Available_ balance, in your settlement time zone.

Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Holding Currency
`string` | The currency in which the financial movement was held and paid out.
Standard – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | Payout ID
`string` | The unique identifier for the payout the financial movement was included in.
Example – `000ABC1DE23F` | | Gross In Holding Currency
`decimal` | The amount of the financial movement, before any deductions or adjustments, in the holding currency. | | Deduction In Holding Currency
`decimal` | The total amount of any fees, taxes, or reserves deducted from the financial movement, in the holding currency. | | Net In Holding Currency
`decimal` | The amount settled for the financial movement, in the holding currency. | | Processing Fee In Holding Currency
`decimal` | The total amount of Checkout.com processing fees charged for the financial movement, such as gateway or premium fees, in the holding currency. | | Scheme Fee In Holding Currency
`decimal` | The amount of the scheme fee charged for processing the financial movement, in the holding currency. | | Interchange In Holding Currency
`decimal` | The amount of the interchange fee charged for processing the financial movement, in the holding currency. | | Tax In Holding Currency
`decimal` | The amount of tax on the fees charged for the financial movement, in the holding currency. | | Reserve In Holding Currency
`decimal` | The reserve amount deducted from the capture of the financial movement, in the holding currency. | | Processing Currency
`string` | The currency the financial movement was processed in.
If the Gross in Holding Currency amount is `0`, this field is empty.

Standard – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | Gross In Processing Currency
`decimal` | If the customer was charged in a different currency than your account’s default, this field reflects the amount the customer sees.

If Gross in Holding Currency is `0`, this field is empty. | | FX Rate Applied
`decimal` | The foreign exchange rate applied to gross-processed financial movements.

If the processing currency and holding currency are the same, this value is `1`. | | Payment Method
`string` | The payment method used for the financial movement. | | Card Type
`string`
`optional` | The type of card used for the payment. This can be one of:

- `Credit`
- `Debit` | | Card Category
`string`
`optional` | The category of card used for the payment. This can be one of:

- `Commercial`
- `Consumer` | | Issuer Country
`string`
`optional` | The country where the card was issued.
Standard – [ISO alpha-2 country code](https://www.checkout.com/docs/developer-resources/testing/codes/country-codes.md)
Example – `US` | | Entity Country
`string`
`optional` | The country where your entity is registered.
Standard – [ISO alpha-2 country code](https://www.checkout.com/docs/developer-resources/testing/codes/country-codes.md)
Example – `US` | | Region
`string`
`optional` | The region where the payment was made. This can be one of:

- `Domestic`
- `International`
- `Intra`
- `IntraEEA`
- `IntraEuropean_SEPA` | | MID
`string`
`optional` | The merchant identifier used to segment your payments traffic with card schemes. | | Merchant Category Code
`string`
`optional` | Your four-digit [merchant category code](https://www.checkout.com/docs/developer-resources/testing/codes/merchant-category-codes.md) for this payment.
Format – ISO 18245 code
Example – `1731` | | Acquirer Reference Number
`string`
`optional` | The unique 23-digit identifier for the payment assigned by the acquirer. This is used to track the payment as it moves through the payment flow between the cardholder's bank and the merchant's bank. | | Account Funding Transaction
`string`
`optional` | A flag for transactions that debit funds from an account to fund a non-merchant account.

For example, to load a prepaid card or add funds to a wallet. | | Entity Segment
`string`
`optional` | The name of the entity segment the payment relates to. | | Issuing Bank
`string`
`optional` | The bank that issued the card used to make the payment. | | BIN
`string`
`optional` | The bank identification number (BIN) for the financial institution that issued the card. | | Payment Type
`string`
`optional` | The type of card payment used for the card-not-present (CNP) payment. | | Processed On UTC
`date-time`
`optional` | The date and time when the financial movement is reflected in your _Pending_ balance, in UTC.

If the funds do not enter _Pending_ and go directly into _Available_, this is the date and time when the financial movement entered your _Available_ balance.

Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Available On UTC
`date-time`
`optional` | The date and time when the financial movement is reflected in your _Available_ balance, in UTC.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | UDF 1
`string`
`optional` | A user-defined field (UDF) you configured when setting up this report. An optional ID passed in the request. | | UDF 2
`string`
`optional` | A UDF you configured during setup. | | UDF 3
`string`
`optional` | A UDF you configured during setup. | | UDF 4
`string`
`optional` | A UDF you configured during setup. | | UDF 5
`string`
`optional` | A UDF you configured during setup. | | Action ID
`string`
`optional` | The unique identifier for a specific financial movement that affects your balances.

If multiple movements relate to one payment, the Action ID corresponds to the latest movement.

For example, if the payment underwent authentication, authorization, and capture, the Action ID relates to the capture. | | Timezone
`string`
`optional` | The time zone the report was generated in.
Example – `Etc/UTC` | | Card Product Type
`string`
`optional` | The name of the card product type used for the payment.
Examples – `Visa Classic` and `Mastercard Business Debit` | | Card Present Transaction
`string`
`optional` | For in-person payments, indicates whether the card was present for the transaction. | | Terminal ID
`string`
`optional` | For in-person payments, the identifier of the terminal where the transaction took place. | | Card Entry Mode
`string`
`optional` | For in-person payments, how the card was presented to the terminal.
Values – `manual`, `chip`, `contactless_chip`, `magnetic_stripe` | | Regulated Debit Indicator
`string`
`optional` | Specifies whether the card is assigned to an interchange-regulated bank identification number (BIN) range.
Values – `True` or `False` |