# Daily Transaction and Reconciliation Reports
source: https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md
This page describes the contents and specifications of the Mastercard Send version 7.x Daily Transaction and Reconciliation reports.
For an overview of Mastercard send reporting, see [here](https://developer.mastercard.com/mastercard-send/documentation/reports/index.md).
## Overview {#overview}
The reports have the same [layout](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#general-layout) but contain different sets of transactions:
| Report | Description |
|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Daily Transaction Report (DTR) | This report provides detailed information for transactions processed during the network's previous cutoff day, including approved and declined transactions. This report does **not** show the amount that will be debited from the Acquirer's Settlement Account with the Receive Network or the TI's Funding Account with the Sponsor OI (depending on your implementation). This report will not always contain the final status of a transaction. See also [Transaction Status](https://developer.mastercard.com/mastercard-send/documentation/reports/transaction-type-status/index.md#transaction-status). |
| Reconciliation Report | This report shows only approved transactions that are expected to settle on the report date; transactions falling after the cutoff time will be included in the next day's Reconciliation Report. This report helps to reconcile all debits from and to the Settlement/Funding Account. Only approved transactions require settlement of funds; therefore, the report does not include declined transactions. The standard (non-FPS) version of the report identifies the Receive Network that approved the transaction, and users may filter the report by Receive Network. |
Reports are batched by Partner Reference ID ("Partner ID" in the report) and will display multiple batches if more than one Partner Reference ID is used and consolidated reporting is set. For example, some participants might be set up with a parent Partner Reference ID (shown in the header) and child Partner Reference IDs shown in individual batch detail.
### General layout {#general-layout}
The Daily Transaction, Reconciliation, and [MAT reports](https://developer.mastercard.com/mastercard-send/documentation/reports/mat/index.md) have the same general layout, which includes:
* [File Header](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#file-header): 100 record of column names and 101 record of values
* For each OI/TI (Reseller/Sponsor OI reports might contain data for multiple OIs/ TIs):
* [ICA Batch Header](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#ica-batch-header-and-records-fps-report-only) (FPS report only): 110 record of column names and 111 record of values
* [Batch Header and Records](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#batch-header-and-records): 200 record of column names and 201 records for each transaction
* [Batch Trailer](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#batch-trailer): 300 record of column names and 301 record of values
* [File Trailer](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#file-trailer): 900 record of column names and 901 record of values
All reports are provided in a comma-separated values (CSV) file. Fields are separated by embedded commas and double quotes to allow for special characters. Any decimals provided in transaction amounts are explicitly displayed. The reports are sent in bulk files, which are in variable block format (record maximum length 27994, block size 27998) during file transfer.
Note: The tables in the [Report Specifications](https://developer.mastercard.com/mastercard-send/documentation/reports/dtr-recon/index.md#report-specifications) section below identify the report fields that support special characters. However, be aware that other fields might be updated to include special characters.
When opening report CSV files in spreadsheet applications, such as Microsoft Excel, be aware that some applications attempt to convert the imported data and might incorrectly alter or truncate the data. For example, date formats might be altered, and long numbers exceeding 15 digits (such as PANs and numeric Reference IDs) might have subsequent digits converted to zeros: '72715118484282248412' becomes '72715118484282200000'.
### Examples {#examples}
Daily Transaction Report:
Reconciliation Report:
For report samples, see [here](https://developer.mastercard.com/mastercard-send/documentation/reports/report-samples/index.md).
### No data report {#no-data-report}
If there is no transaction activity to report in the Daily Transaction or Reconciliation reports for a Program participant, only the file header and trailer with details will be sent, as shown below. The File Count and File Checksum will be 0 (zero).
## Report specifications {#report-specifications}
The following tables describe the contents of the Mastercard Send version 7.x Daily Transaction and Reconciliation reports. We recommend you also refer to the [Mastercard Send Release Notes](https://developer.mastercard.com/mastercard-send/documentation/send-release-notes/index.md) to see details of any recent changes and proposed future changes.
To support future items, the report has placeholder columns, which are identified by "Reserved for future use" in the tables below. No new columns will be added to the reports until these fields are exhausted. Updates to these fields, such as column name, data type and length, are considered backward compatible and will be added without changing the report version. Applications consuming these resources should be written such that new fields appearing in reporting will not cause errors.
Mastercard Send provides the reports in one of the following versions:
* **Standard reports---apply to most implementations:** Version 7 or 7.1, which contain the same columns but differ in what is shown for the account number: last 4 digits (version 7) or full number (version 7.1).
* **FPS reports---apply to FPS participants and non-card account implementations:** Version 7.4.
The tables identify the columns that are present in a particular report version. For each column, a field will be blank if it is not relevant to that transaction record or to that report, or when the value was not present in the API request or resulting network messages.
### File header {#file-header}
| Column Name | Description | Format |
|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|
| Report Name | The report name: 'Daily Transaction Report' or 'Reconciliation Report'. | Alphanumeric, max length 40 |
| Parent Partner Name | The name of the participant for which the report has been generated. | Alphanumeric special, length 100 |
| Partner Id | The Partner Reference ID of the participant for which the report has been generated. | Alphanumeric special, max length 40 |
| Generated Date | The date and time the report was generated, in 24-hour time. **NOTE:** The value has a trailing space after the time zone, for example, '04/18/2023 18:17 CDT '. | MM/DD/YYYY HH:MM TTT (TTT denotes the time zone alpha code) |
### ICA batch header and records (FPS report only) {#ica-batch-header-and-records-fps-report-only}
| Column Name | Description | Format |
|-------------------|---------------------------------------------------|--------------------------------------|
| Partner ID | The Partner Reference ID of the partner OI/TI. | Alphanumeric special, max length 40 |
| Partner Name | The name of the partner OI/TI. | Alphanumeric special, max length 100 |
| ICA | The Acquiring ICA associated with the Sponsor OI. | Numeric, max length 11 |
| Sponsor Bank Name | The name of the Sponsor OI. | Alphanumeric special, max length 100 |
### Batch header and records {#batch-header-and-records}
| Column Name | Description | Format |
|----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------|
| Partner ID | The Partner Reference ID of the OI/TI. | Alphanumeric special, max length 40 |
| Partner Name | The name of the OI/TI. | Alphanumeric special, max length 100 |
| Reference ID | The unique transaction reference ID provided by the OI/TI, which is carried through from the following transaction API request fields: * Disbursement = `disbursement_reference` * Payment Transfer = `transfer_reference` * Funding = `transfer_reference` This ID can be used by partners to link report transactions to their back office. When additional fields are needed to uniquely identify transaction data, custom fields may be coded to and included in the reports; see the "Custom Field Name" table row. | Alphanumeric special, length 6-40 |
| Transaction Type | The type of transaction. Valid values include: * FUNDING * PAYMENT * FUNDING_REVERSAL * FUNDING_REFUND For more values and descriptions, see [Transaction Type](https://developer.mastercard.com/mastercard-send/documentation/reports/transaction-type-status/index.md#transaction-type). | Alpha special, max length 50 |
| Payment Type | The payment flow associated to the transaction, for example, 'P2P' (General Person-to-Person Transfer). For a list of 3-character codes, see the `payment_type` field description in the API Reference documentation on Mastercard Developers or the *Use Cases and Payment Types* section of the *Mastercard Send Implementation and Operations Guide for API Connections*. Valid payment types are configured for each Partner Reference ID. | Alphanumeric, length 3 |
| DateTime Created | The date and time the transaction was originated in the API, in CST. | MM/DD/YYYY HH:MM:SS |
| DateTime Processed | The date and time the transaction was processed, in CST. This field will be blank if a processed time is not returned from the issuing network. | MM/DD/YYYY HH:MM:SS |
| Source | The source of the settlement funds. Valid values include: * Settlement * STAR * NYCE * Pulse * Maestro\* * MoneySend * MoneySend DM * MasterCard\*\* * VISA AFT * VISA * VISA Returns * FPS Outbound\*\*\* * FPS Inbound\*\*\*
\* Maestro is just a label for transactions submitted as return transactions (TC20) using the Mastercard Single Message Network. \*\* Mastercard transactions are submitted as return transactions (TC20) using either the Mastercard Dual Network (Global) or Mastercard Dual Messages related to Faster Payments to Accounts Network (FPS). \*\*\* FPS Outbound and FPS Inbound networks are related to Faster Payments to Accounts. **NOTE:** Source and Destination fields are used in conjunction. When the Source field = Settlement, the flow of funds is a debit to partner (funds pulled from the Settlement Account and sent to the relevant Receive Network). This is the normal flow for Payment Transactions and funding reversals. When the Source field = a network, the flow of funds is a credit to partner (funds are moved from the relevant network to the Settlement Account). This is the normal flow for exception item payment reversals and Funding Transactions. | Alpha, max length 20 |
| Destination | The relevant Receive Network, which is the destination network of settlement funds. If the value is 'Settlement', the transaction funds are a credit to the participant. Valid values include: * Settlement * STAR * NYCE * Pulse * Maestro\* * MoneySend * MoneySend DM * MasterCard\*\* * VISA AFT * VISA * FPS Outbound\*\*\* * FPS Inbound\*\*\*
\* Maestro is just a label for transactions submitted as return transactions (TC20) using the Mastercard Single Message Network. \*\* Mastercard transactions are submitted as return transactions (TC20) using either the Mastercard Dual Network (Global) or Mastercard Dual Messages related to Faster Payments to Accounts Network (FPS). \*\*\* FPS Outbound and FPS Inbound networks are related to Faster Payments to Accounts. **NOTE:** Source and Destination fields are used in conjunction. See the note for the Source field. | Alpha, max length 20 |
| Settled By | The settlement entity for the transaction. Valid values: * Mastercard * Visa * STAR * NYCE * Pulse * FPS | Alpha, max length 20 |
| Account Number | For records relating to a Funding Transaction, this is the Sender's account (Funding Account) number. For records relating to a Payment Transaction, this is the Receiving Account number. Depending on the report version, this is the last 4 digits of the account number (version 7) or the full account number (version 7.1/7.4). | Version 7: Numeric, length 4 Version 7.1/7.4: Numeric, length 12-19 |
| Transaction Amount | The amount transferred. Decimals are explicit. | Numeric, 3‑999999999999 |
| Transaction Currency | The currency code of the transaction amount. | Alpha, length 3 |
| Interchange Amount | **Daily Transaction Report:** Field will be blank. **Reconciliation Report:** If the network is collecting interchange on this transaction as part of the Settlement Amount, this field will show the interchange amount charged by the network. Example: "0.050". Not applicable for Account-based transfers (in other words, FPS transfers or bank account transfers). | Daily Transaction Report: Blank Reconciliation Report: Numeric, up to 999999999999 |
| Rate Type Indicator | For future use only. The field appears blank. | Blank |
| Error | Whether the transaction succeeded: 0 = Success, 1 = Failure. See [Transaction Status](https://developer.mastercard.com/mastercard-send/documentation/reports/transaction-type-status/index.md#transaction-status). | Numeric, length 1 |
| Response Code | A code indicating the reason for error: 00 = Success, 04 = Failure. **NOTE:** If a transaction is in an UNKNOWN status, the Response Code will indicate 04. However, customers must perform an API lookup (GET request) call to confirm final status. The Error and Response Code fields are simplified to ease coding. | Numeric, length 2 |
| Network Response Code | The response code provided by the relevant Receive Network. For a list of possible response codes, see the *DE 39 (Response Code)* section of the [*Mastercard Network Processing Dual Message Authorization System Guide*](https://trc-techresource.mastercard.com/r/bundle/m_DMAS_en-us/page/d/en-US) or [*Mastercard Network Processing Single Message System Guide*](https://trc-techresource.mastercard.com/r/bundle/m_SMS_Guide_en-us/page/d/en-US) in the [Technical Resource Center](https://trc-techresource.mastercard.com/) on Mastercard Connect. If a transaction error occurs at the API level, the API returns a specific error detail code in the API response and this report field will be blank. | Alphanumeric, max length 5 |
| Cutoff Date | The Network cutoff date for settlement. | MM/DD/YYYY |
| Sender First Name | The first name of the Sender. For Disbursement transactions, this field might be blank. | Alphanumeric special, length 1-100 |
| Sender Last Name | The last name of the Sender. For Disbursement transactions, this field might be blank. | Alphanumeric special, length 1-100 |
| Receiver First Name | The first name of the Recipient. | Alphanumeric special, length 1-100 |
| Receiver Last Name | The last name of the Recipient. | Alphanumeric special, length 1-100 |
| Payment Origination Country | The country code where the payment originated, if provided in the API request. Otherwise, this field will be blank. Blank for Funding Transactions. | Alpha, max length 3 |
| Institution Country | The country of the Receiving Institution. | Alpha, max length 3 |
| System Trace Audit Number | The System Trace Audit Number (STAN) provided by the relevant Receive Network that processed the transaction. The STAN is unique for each transaction initiated by a message originator on any single UTC date. When Mastercard Send receives no data from the relevant Receive Network or gateway, this field will be blank. Not applicable for FPS transfers. | Numeric, max length 6 |
| Retrieval Reference | The unique reference number that identifies the transaction in the Receive Network. It refers to the original source document of the transaction and is used to assist in locating that source document or a copy thereof. When Mastercard Send receives no data from the relevant Receive Network or gateway, this field will be blank. Not applicable for FPS transfers. | Numeric, max length 24 |
| Funding Source | The source of funds for payments that is provided in the `funding_source` field of the API request. Valid values: * CREDIT * DEBIT * PREPAID * DEPOSIT_ACCOUNT * MOBILE_MONEY_ACCOUNT * CASH Mobile Money Account and Cash are not enabled as valid funding sources for the Mastercard Send Service. Blank for customer-initiated Funding Reversals. | Alpha special, max length 20 |
| Statement Descriptor | A string that might be displayed on the Recipient's bank or card statement. If not provided in the API request, the system will use the value defined in the onboarding process. While most Financial Institutions display this information consistently, some might display it incorrectly or not at all. Blank for customer-initiated Funding Reversals. | Alphanumeric special, max length 22 |
| Card Acceptor ID | Uniquely identifies a TI. If a Receive Network does not support Card Acceptor ID, this field will be blank. Not applicable for FPS transfers. Blank for customer-initiated Funding Reversals. | Alphanumeric special, max length 15 |
| Merchant Category Code | Identifies the type of business of the Recipient. The merchant category code will either match a valid code set by Mastercard rules or the merchant vertical for approved use cases. Not applicable for FPS transfers. Blank for customer-initiated Funding Reversals. | Numeric, max length 4 |
| Processing Code | The value in Data Element 03 of the transaction network message, which describes the effect of the transaction on the account and type of account affected. Not applicable for FPS transfers. | Numeric, max length 6 |
| Switch Serial Number | A unique transaction identification number generated or assigned by Mastercard. Not applicable for FPS transfers. | Alphanumeric, max length 9 |
| | **The columns below are only present in standard reports (version 7 and 7.1):** | |
| Sender Address Line 1 | The first line of the Sender's address. Blank for Funding Transactions. | Alphanumeric special, max length 50 |
| Sender Address City | The Sender's city. Blank for Funding Transactions. | Alphanumeric special, max length 25 |
| Sender Address State | The Sender's state or province. Blank for Funding Transactions. | Alpha, max length 3 |
| Sender Address Postal Code | The Sender's postal code. Blank for Funding Transactions. | Alphanumeric special, max length 10 |
| Receiver Address Line 1 | The first line of the Recipient's address. | Alphanumeric special, max length 50 |
| Receiver Address City | The Recipient's city. | Alphanumeric special, max length 25 |
| Receiver Address State | The Recipient's state or province. | Alpha, max length 3 |
| Receiver Address Postal Code | The Recipient's postal code. | Alphanumeric special, max length 10 |
| Card Product Type | The receiving card BIN product type: Debit, Prepaid, or Credit. | Alpha, max length 7 |
| Acquirer Reference Number | Data supplied by Mastercard Send in an Acquirer-originated message that might be required for an Issuer to return a transaction to the Acquirer in a subsequent message. | Numeric, max length 23 |
| Acceptance Brand | The acceptance brand code for the Mastercard account: DMC, MCC, or MSI. Value only present in DTR. | Alpha, length 3 |
| Reserved12 | Reserved for future use. *This field is due to become 'Transaction Link ID' from 2 June 2026 in production. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.4.pdf#page=8).* | |
| Reserved13 | Reserved for future use. | |
| ECI | The electronic commerce indicator identifying the level of security for an e-commerce transaction. | Numeric, max length 3 |
| Transaction Purpose | The purpose of the transaction. Valid values: * 00 = Family Support * 01 = Regular Labor Transfers (expatriates) * 02 = Travel \& Tourism * 03 = Education * 04 = Hospitalization \& Medical Treatment * 05 = Emergency Need * 06 = Savings * 07 = Gifts * 08 = Other * 09 = Salary * 10 = Crowd lending * 11 = Crypto currency * 12 = Refund to original card * 13 = Refund to new card | Numeric, length 2 |
| | **The columns below are only present in FPS reports (version 7.4):** | |
| ICA | The ICA of the Sponsor OI. | Numeric, max length 11 |
| Sponsor Bank Name | The name of the Sponsor OI. | Alphanumeric special, max length 100 |
| Funding PAN | The PAN associated with the token. This field is applicable only for transactions where a token is passed in the request (for Sender's account number). By default, the last 4 digits will be provided. Participants should request configuration if they require the full account number. | Alphanumeric, max length 19 |
| Network Transaction Reference Id | A unique Transaction Reference which will link the Funding and Payment Transaction. Not applicable for FPS transfers. | Alphanumeric, max length 20 |
| Authorization Code | An Authorization Identification Response Code assigned by the Authorizing Institution. Not applicable for FPS transfers. | Alphanumeric, max length 6 |
| Payment UID | The unique ID that was passed to the Faster Payments Network. Applicable only for transactions routed through Faster Payments. | Alphanumeric, max length 36 |
| Faster Payment ID | A unique ID generated by the Faster Payments Network. Applicable only for transactions routed through Faster Payments. | Alphanumeric, max length 42 |
| Destination Sort Code | The sort code for the Recipient account. Applicable only for transactions routed through Faster Payments. | Alphanumeric, max length 6 |
| Destination Account Name | The Recipient's name on the account. Applicable only for transactions routed through Faster Payments. | Alphanumeric special, max length 40 |
| Source Account Number | The Funding Account number. By default, the last 4 digits will be provided. Participants should request configuration if they require the full account number. Applicable only for transactions routed through Faster Payments. | Alphanumeric, max length 8 |
| Source Sort Code | The sort code for the Funding Account. Applicable only for transactions routed through Faster Payments. | Alphanumeric, max length 6 |
| Source Account Name | The name on the Funding Account. Applicable only for transactions routed through Faster Payments. | Alphanumeric special, max length 40 |
| Transfer Priority | The type of Payment instruction. Valid values include: * SIP = Single Immediate Payment * FDP = Future Dated Payment Applicable only for transactions routed through Faster Payments. | Alpha, max length 3 |
| Non Card Token | A system identifier that is generated by Mastercard, which is returned as part of the account-mapping response. Populated when an alias is used. Applicable only for transactions routed through Faster Payments. | Alphanumeric, max length 125 |
| Transaction ID | The unique transaction ID provided by the other networks (such as Visa). For the Mastercard Network, this field will always be blank. | Numeric, max length 15 |
| Settlement Amount | The amount of funds to be transferred between the Acquirer and the Issuer equal to the Transaction Amount in the currency of settlement. Decimals are explicit. | Numeric, max length 12 |
| Settlement Currency | The ISO currency code defining the currency of Settlement Amount. | Alpha, length 3 |
| ECI | The electronic commerce indicator identifying the level of security for an e-commerce transaction. | Numeric, max length 3 |
| Transaction Purpose | The purpose of the transaction. Valid values: * 00 = Family Support * 01 = Regular Labor Transfers (expatriates) * 02 = Travel \& Tourism * 03 = Education * 04 = Hospitalization \& Medical Treatment * 05 = Emergency Need * 06 = Savings * 07 = Gifts * 08 = Other * 09 = Salary * 10 = Crowd lending * 11 = Crypto currency * 12 = Refund to original card * 13 = Refund to new card | Numeric, length 2 |
| Acceptance Brand | The acceptance brand code for the Mastercard account: DMC, MCC, or MSI. Value only present in DTR. | Alpha, length 3 |
| Reserved17 | Reserved for future use. *This field is due to become 'Transaction Link ID' from 2 June 2026 in production. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.4.pdf#page=8).* | |
| Reserved18 | Reserved for future use. | |
| Reserved19 | Reserved for future use. | |
| Reserved20 | Reserved for future use. | |
| | **Optional:** | |
| *Custom Field Name* | Up to four custom fields can be added to the Daily Transaction and Reconciliation Reports. These fields are configured for the participant during setup, see [Custom Fields for Reconciliation](https://developer.mastercard.com/mastercard-send/documentation/reports/index.md#custom-fields-for-reconciliation). The participant sends both the configured field name and the individual transaction data in the transaction API call. If transaction data is not sent for this column, the field appears blank. Custom fields will not appear if the participant is not configured to receive them. To configure custom fields after initial setup, contact a Mastercard representative. | Each custom field can be alphanumeric: * Name = max length 40 * Value = max length 200 |
### Batch trailer {#batch-trailer}
| Column Name | Description | Format |
|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
| Batch Count | The total number of records in the batch. | Numeric, 1‑999999999999 |
| Batch Checksum | The total batch transaction amount for confirming complete transmission of the batch data. The value should equal the total of the values in the **Transaction Amount** column for the batch. | Numeric, 0‑999999999999 |
### File trailer {#file-trailer}
| Column Name | Description | Format |
|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
| File Count | The total number of records in the file. | Numeric, 1‑999999999999 |
| File Checksum | The total file transaction amount for confirming complete transmission of the file data. The value should equal the total of the values in the **Transaction Amount** column for all batches. | Numeric, 0‑999999999999 |
The checksum values will have a currency exponent appropriate to the transaction amounts (no scaling). For example, if the amounts are exponent 2 (such as 123.45), the checksum will have an exponent of 2.