# Financial Actions by Date Range Report The Financial Actions by Date Range Report lists all actions during a payment’s lifecycle that impact your sub-account's _Available_ and _Pending_ balances. Understanding the financial impact of each action and any foreign exchange (FX) rates applied helps you accurately assess your cost of sale. The report contains financial actions across a specified time frame, in chronological order. Every row features a unique financial action ID that can be linked to one of the following: - A specific payment, using the payment ID - A settlement payout, using the payout ID > **Information** > > For information about the financial actions available in this report, see [Breakdown types](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/breakdown-types.md). --- ## Report availability The report is updated between midnight and 3:00 AM in your entity's [settlement time zone](https://www.checkout.com/docs/funds-management/receive-settlements.md#Settlement_time_zone). You can generate it on a daily, weekly, or monthly basis. For example, your settlement time zone is `America/Los_Angeles` Pacific Time (PT) and financial actions occur on August 3. The daily report captures all financial movements from August 3 at midnight to 11:59 PM PT. It is generated at midnight PT on August 4. See instructions on how to download the report on demand or on a schedule: - [In the Dashboard](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Generate_reports_in_the_Dashboard) - [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. The file name uses the following formats by default: - API and SFTP – `financial-actions_{EntityID}_{Start Date: YYYYMMDD}_{End Date:YYYYMMDD}_1.csv` - Dashboard scheduled reports – `financial-actions_{Your Entity-ID}_{Start Date Range:YYYYMMDD}_{End Date Range:YYYYMMDD}_1.csv` For SFTP, the report is uploaded in the following folder structure:
`{Entity_name} > reports-{Entity_name} > financial-actions > date-range` --- ## Sample reports Download a sample [Financial Actions by Date Range Report](https://www.checkout.com/docs/files/Sample_Financial_Actions-By_Date_Range_Report.csv) (CSV file). > **Information** > > If you're using Safari, hold the _Option_ key when you download. --- ## Report fields > **Information** > > - To enable any optional fields for this report, contact your account manager or [request support](https://dashboard.checkout.com/support/new?topic=case_account_management_and_access&issue=issue_account_changes). > - Sub-accounts are referred to as currency accounts in the report fields. > - All decimal amounts are expressed in the [major currency unit](https://www.checkout.com/docs/payments/accept-payments/format-the-amount-value.md), with fixed-point notation with up to eight decimal places. For example, 500 USD is represented as `500.00`. The report can include the following fields in this order: | Field name | Description | | --- | --- | | Client Entity ID

`string` | The unique identifier for the entity for which the payment was processed, prefixed with `ent_`. | | Client Entity Name

`string` | The entity's name. | | Sub Entity ID

`string` | The unique identifier for the sub-entity for which the payment was processed, prefixed with `ent_`. | | Sub Entity Name

`string` | The sub-entity's name. | | 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_`. | | Merchant Category Code

`string` | The merchant's [merchant category code](https://www.checkout.com/docs/developer-resources/testing/codes/merchant-category-codes.md).

Format – Four-digit ISO 18245 code | | Currency Account ID

`string` | The unique identifier for the sub-account the financial action amount was charged to, prefixed with `ca_`. | | Currency Account Name

`string` | The sub-account's name. | | Currency Account Custom ID

`string` | Your identifier for the sub-account. | | Action Type

`string` | The type of financial action.

See [Breakdown types](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/breakdown-types.md). | | Action ID

`string` | The financial action's unique identifier, prefixed with `act_`. | | Payment ID

`string` | The unique identifier for the payment the financial action is associated with, prefixed with `pay_`. | | Requested On

`date-time` | The date and time when the gateway request was made for the financial action, in your settlement time zone.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Processed On

`date-time` | The date and time when the financial action moved into your _Pending_ balance, in your settlement time zone.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Processing Currency

`string` | The currency in which the financial action was processed.
Standard – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | FX Rate Applied

`decimal` | The foreign exchange rate applied to the financial action.

If the processing currency and holding currency are the same, this value is `1`. | | Holding Currency

`string` | The currency in which the financial action is held and paid out.
Standard – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | FX Trade ID

`string` | The unique identifier for the foreign exchange trade executed for the financial action. | | Payout ID

`string` | The unique identifier for the settlement the financial action was included in.

Format – This field is always empty.

This is the same value as the settlement ID. | | Reference

`string` | An optional identifier used to track financial actions. | | Payment Method

`string` | The payment method used for the financial action. | | Card Type

`string` | The type of card used to make the payment. This can be one of:

- `Credit`
- `Debit` | | Card Category

`string` | The category of card used to make the payment. This can be one of:

- `Commercial`
- `Consumer` | | Issuer Country

`string` | 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` | The country where the 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` | The region where the payment was made. This can be one of:

- `Domestic`
- `EEA`
- `International`
- `Intra`
- `IntraEEA`
- `IntraEuropean_SEPA` | | MID

`string` | The merchant identifier used to segment your payments traffic with card schemes. | | Response Code

`string` | The [response code](https://www.checkout.com/docs/resources/codes/api-response-codes.md) for the payment request. | | Response Description

`string` | The description of the response code for the payment request. | | Breakdown Type

`string` | The [breakdown type](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/breakdown-types.md) of the fee or amount. | | Processing Currency Amount

`decimal` | The amount of the financial action in the processing currency. | | Holding Currency Amount

`decimal` | The amount of the financial action in the holding currency. | | Entity Country Tax Currency

`string` | The currency of the country your entity resides in for tax purposes, if applicable.
Format – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | Tax FX Rate

`decimal` | The foreign exchange rate between the holding currency and the tax currency when the financial action was processed. | | Tax Currency Amount

`decimal` | The amount of tax applied, expressed in the tax currency. | | Transaction Currency

`string`
`optional` | The currency in which the transaction was processed.
Format – [ISO 4217 code](https://www.checkout.com/docs/developer-resources/testing/codes/currency-codes.md)
Example – `USD` | | Transaction Currency Amount

`decimal`
`optional` | The amount of the transaction, expressed in the transaction currency. | | Processing to Transaction Currency FX Rate

`decimal`
`optional` | The foreign exchange rate between the processing currency and the transaction currency. | | Transaction to Holding Currency FX Rate

`decimal`
`optional` | The foreign exchange rate between the transaction currency and the holding currency.

This rate is inferred from both the FX Rate and Processing to Transaction Currency FX Rate fields to account for foreign exchange rates from multiple rate ticks. | | Fee Detail

`string` | The additional level of granularity for predicted scheme fees applied. | | Reserve Rate

`percentage`
`optional` | The percentage amount [reserved](https://www.checkout.com/docs/funds-management/manage-funds/balances/fixed-and-rolling-reserves.md) from the payment. | | Reserve Deducted Date

`date-time`
`optional` | The date and time when the reserve was deducted from the payment.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Reserve Release Date

`date-time`
`optional` | For a Rolling Reserve Deducted financial action, the date and time when the reserve is scheduled to be released.

For a Rolling Reserve Released financial action, the date and time when the reserve was released.


Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Processing Channel Name

`string`
`optional` | The processing channel's name. | | 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 merchant’s bank and the cardholder’s bank. | | Account Funding Transaction

`string`
`optional` | A flag that the transaction debited 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 is tagged 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. For example, for a recurring payment or mail order.

This value can be one of:

- `Installment`
- `Recurring`
- `Regular`
- `MOTO`
- `Unscheduled` | | Requested On UTC

`date-time`
`optional` | The date and time when the financial action was requested, in UTC.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Processed On UTC

`date-time`

`optional` | The date and time when the financial action entered your _Pending_ balance, in UTC.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | 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.
Example – `Visa Classic` or `Mastercard Business Debit` | | Available On

`date-time`

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

`date-time`
`optional` | The date and time when the financial action is expected to enter your _Available_ balance, in UTC.
Standard – ISO 8601 code
Format – `yyyy-mm-ddThh:mm:ss.sss` | | Checkout Legal Entity Code

`string`
`optional` | The code for the Checkout.com legal entity that processed the financial action.
Example – `cko-sas` |