# Financial Actions by Payout ID Report The Financial Actions by Payout ID Report provides a detailed record of all financial activity associated with a specific settlement. For each payment in the settlement, it chronologically lists all lifecycle actions that impact your sub-account's _Available_ and _Pending_ balances. You can link each financial action ID to the payment using the payment ID, and to the settlement using the payout/settlement ID. Use this report to: - Reconcile payments and any associated fees for settlements together with the [Payouts Report](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/settlement-reports/payouts-report.md). - Understand the financial impact of each action and any foreign exchange (FX) rates applied to accurately assess your cost of sale. > **Note** > > You cannot use this report to reconcile with the [Financial Actions by Date Range Report](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/balance-reports/financial-actions-by-date-range-report.md), which covers only a single day. > If you use [same-day settlement](https://www.checkout.com/docs/funds-management/receive-settlements.md#Same-day_settlements), adjustments to your _Available_ balance can mean that the amount of the settlement can change up until it is paid out. > **Information** > > For information about the financial actions in this report, see [Breakdown types](https://www.checkout.com/docs/funds-management/retrieve-financial-reports/breakdown-types.md). --- ## Report availability This report is created when your settlement is generated according to your [settlement speed](https://www.checkout.com/docs/funds-management/receive-settlements.md#Settlement_speed), between 2:00 AM and midnight 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 every settlement that is paid out, in line with your [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 that has payout/settlement ID `00000000CFJU`. The report is generated at midnight PT on August 4, and includes all financial activity held in `USD` from August 3 at midnight to 11:59 PM PT. 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_using_the_API) - [Using Secure File Transfer Protocol (SFTP)](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Access_reports_using_SFTP) - [Using webhooks](https://www.checkout.com/docs/business-operations/retrieve-reports.md#Receive_reports_using_webhooks) You can also download this report for a specific settlement in the Dashboard: 1. Sign in to the [Dashboard](https://dashboard.checkout.com). 2. Go to _Settlements_ and select the relevant settlement. 3. On the _Settlement details_ page, for _Financial Actions By Payout ID_, select _Download CSV_. --- ## 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}_{Payout Date: YYYYMMDD}_{PayoutID}_1.csv` - Dashboard reports – `{Entity_name}_{PayoutID}_{Currency}_1.csv` For SFTP, the report is uploaded in the following folder structure:
`{Entity_name} > reports-{Entity_name} > financial-actions > payout-id` --- ## Sample reports Download as a CSV file a sample: - [Financial Actions by Payout ID Report](https://www.checkout.com/docs/files/SAMPLE-BY-PAYOUT-ID-financial-actions_ent_tnu3ld65mm4e3bgxmx7oj62t2y_20221116_000G7HDD96SH_1.csv) - [Financial Actions by Payout ID Report](https://www.checkout.com/docs/files/Sample_FA_by_payout_balance_carried_forward.csv) when the `Carried forward` [settlement status](https://www.checkout.com/docs/funds-management/receive-settlements/manage-settlements.md#Settlement_statuses) is enabled > **Information** > > If you're using Safari, hold the _Option_ key when you download. --- ## Report fields > **Information** > > - To enable any optional fields, 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 the settlement was paid out to, prefixed with `ent_`. | | Client Entity Name

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

`string` | The unique identifier for the sub-entity the settlement was paid out to, 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

Merchants can have multiple category codes. | | Currency Account ID

`string` | The unique identifier for the sub-account impacted by the financial action, 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
Example – `yyyy-mm-ddThh:mm:ss.sss` | | Processed On

`date-time` | The date and time when the financial action was processed, in your settlement time zone.
Standard – ISO 8601 code
Example – `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.

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

`string`
`optional` | Your identifier used to track the financial action. | | 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 transaction amount, 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`
`optional` | The specific type of card scheme or interchange fee charged.

Example – `VISA ACQUIRER CLEARING FEE`

**Predictive Interchange** `Beta`

With the Predictive Interchange feature, this field enables you to [confirm your reduced Level 2 or Level 3 interchange fees](https://www.checkout.com/docs/payments/manage-payments/enhanced-scheme-data/submit-level-2-or-level-3-data.md#Confirm_reduced_interchange_rates_).
This field then has a specific suffix per card scheme:

Mastercard:
- `Data II` – For example, `MC US DOMESTIC COMMERCIAL`
- `Data III` – For example, `CREDIT - WORLD ELITE - DATA II`

Visa:
- `Level 2` – For example, `VISA US DOMESTIC COMMERCIAL`
- `Level 3` – For example, `CREDIT - PURCHASING - LEVEL 3` | | 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
Example – `yyyy-mm-ddThh:mm:ss.sss` | | Reserve Release Date

`date-time`
`optional` | The date and time when the reserve:

- Is scheduled to be released for a Rolling Reserve Deducted financial action
- Was released for a Rolling Reserve Released financial action

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

`string`
`optional` | The [processing channel's](https://www.checkout.com/docs/business-operations/use-the-dashboard/manage-processing-channels.md) 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-not-present (CNP) payment. This 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
Example – `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. Format – ISO 8601 code
Example – `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
Example – `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
Example – `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` | | 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` |