Generate settlement recon report
Follow these steps to generate and download a Settlement Recon report:- Log in to the Merchant Dashboard.
- Navigate to Payment Gateway > Reports > Download Reports.
- Click the Generate New Report button.
- Configure your report settings:
- Report Type: Select Settlement Recon from the dropdown.
- Date Range: Choose the time period for the report.
- File Format: Select CSV or XLSX.
- File Name: Modify if needed, this is optional.
- Click Generate Report.
- Once generated, click the three dots (⋮) next to your report.
- Click Download Report to save the file.
- Click Share Report to share the report via email or mobile number and set the validity period.

Settlement recon report specification
- Settlements
- Transaction details
The Settlements section provides one row per settlement batch, showing what was settled, when it was processed, and the final amount credited to your bank account.The following table describes the parameters available in the settlements section of the settlement recon report:
| Parameter | Sample value | Flag | Description |
|---|---|---|---|
| ID | 208386848 | id | Unique ID for the settlement generated by Cashfree. Use this ID to cross-reference the settlement in other reports. |
| Total Transaction Amount | 110.00 | amount | Sum of all eligible transaction amounts considered for this settlement before any charges, taxes, refunds, chargebacks, or other adjustments. |
| Settlement Amount | 20.00 | amount | Amount left after deducting Cashfree’s charges and other fees from the total transaction amount, before applying adjustments. |
| Adjustment | 14.32 | amount | Net effect of all adjustments linked to this settlement, such as chargebacks, refunds, and other adjustments. Can be positive or negative. |
| Net Settlement Amount | 14.32 | amount | Final amount credited to your bank account for this settlement after charges, taxes, and adjustments. This should match the credit seen in your bank statement. |
| From | 2025-10-08 18:18:03 | datetime | Date and time of the earliest transaction included in this settlement batch. |
| Till | 2025-10-08 18:18:03 | datetime | Date and time of the latest transaction included in this settlement batch. |
| Status | Processed | enum | Current status of the settlement for example: Processed, Pending, Failed. |
| UTR No. | AXISCN1169361047 | id | Bank reference number (UTR) for this settlement payout. You can use this to match the settlement with the entry in your bank statement. |
| Settlement Date | 2025-10-08 18:18:03 | datetime | Date and time when the settlement was successfully processed and confirmed. |
| Settlement Type | STANDARD | enum | Type of settlement, such as STANDARD, INSTANT, or ON_DEMAND. |
| Settlement Charge | 20.00 | amount | Total settlement-level charges applied for this settlement batch. |
| Settlement Tax | 10.00 | amount | Tax amount applied on the settlement charges. |
| Remarks | Settled | text | Any additional comments or notes added to the settlement, usually to highlight exceptions or special handling. |
Custom reconciliation fields (order_tags)
Use the order_tags object on the Create Order API to attach custom string key-value pairs to an order. Each key and value must be between 1 and 255 characters. You can pass up to 10 tags per order.
The first three key-value pairs from order_tags surface in the Transaction details section of this report as Key_1/Value_1, Key_2/Value_2, and Key_3/Value_3. Additional tags remain on the order but don’t appear in the Settlement Recon export.
Use order_tags for any business-specific identifiers you need at settlement time—for example branch or outlet ID, campaign code, internal invoice reference, or membership tier. Pass only the fields you need for reconciliation and limit order_tags to three keys so they map clearly to Key_1 through Key_3.
The first three keys in your request determine which columns appear in the report. Name keys consistently across orders so finance teams can filter and pivot on
Value_1, Value_2, and Value_3.Value_1, Value_2, or Value_3 to reconcile collections by institute, student, or division. The same approach applies to other use cases using different key names.