# GDR, GRN, and GMR
source: https://developer.mastercard.com/mastercard-send/documentation/reports/gdr-grn-gmr/index.md
This page describes the contents and specifications of these Mastercard Send version 8.x reports:
* Global Daily Transaction Report (GDR)
* Global Reconciliation Report (GRN)
* Global Mismatched and Adjustment Report (GMR)
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/gdr-grn-gmr/index.md#general-layout) but contain different sets of transactions:
| Report | Description |
|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Global Daily Transaction Report (GDR) | This report shows all approved and declined transactions processed by Mastercard Send APIs. By default, this report contains yesterday's transactions from 00:00 am until today 00:00 am. The GDR does **not** show the amount that will be debited from the Acquirer's Settlement Account with the 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. |
| Global Reconciliation Report (GRN) | This report shows approved transactions (including lifecycle transactions) that are settled on the report date, including Funding Reversals. The report will include data on days when the Mastercard Settlement Account Management (SAM) system settles. For other days, the files will be delivered but will not contain any transactions. The GRN does **not** include declined transactions. The report identifies the Network that approved the transaction, and users may filter the report by Receive Network. |
| Global Mismatched and Adjustment Report (GMR) | This report shows transactions that are settled in a different way (and for a different amount) than what was processed and reported by the Mastercard Send APIs. The report will include data when exceptions occur and only on settlement days. Otherwise, the files will be delivered but will not contain any transactions. The GRN and GMR reports can be used to reconcile settlement positions. The GRN contains transaction data as it was processed by the Mastercard Send APIs. When differences appear between what is provided in the GRN and what was actually settled, details for the exception amount and those differences are provided in the GMR. |
### General layout {#general-layout}
The reports have the same general layout, which includes:
* [File Header](https://developer.mastercard.com/mastercard-send/documentation/reports/gdr-grn-gmr/index.md#file-header):
* 100 record of column names and 101 record of values
* 110 record of column names and 111 record of values
* For each OI/TI (Reseller/Sponsor OI reports might contain data for multiple OIs/ TIs):
* [Batch Header and Records](https://developer.mastercard.com/mastercard-send/documentation/reports/gdr-grn-gmr/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/gdr-grn-gmr/index.md#batch-trailer): 300 record of column names and 301 record of values
* [File Trailer](https://developer.mastercard.com/mastercard-send/documentation/reports/gdr-grn-gmr/index.md#file-trailer): 900 record of column names and 901 record of values
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.
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. The report generation systems will include additional escape double quotes when API fields contain double quotes. 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/gdr-grn-gmr/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'.
### Example {#example}
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 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 these Mastercard Send version 8.x 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.
All the fields will be present for all types of report, but the field's value will be blank if it is not relevant to that transaction record or to that report (as identified in the field description), or when the value was not present in the API request or resulting network messages.
Depending on what you request during implementation, Mastercard Send provides the reports in one of these versions, which affect how account numbers are shown:
* 8.1 = Last 4 digits of account number
* 8.2 = Last 4 digits of account number, full Transaction Funding PAN
* 8.3 = Full account number, last 4 digits of Transaction Funding PAN
(Transaction Funding PAN relates to a Sender's token, when such a token is passed in the API request as the Sender's account number.)
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.
### File header {#file-header}
| Column Name | Description | Format | Max Length |
|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|------------|
| Report Name | The report name: 'Global Daily Transaction Report', 'Global Reconciliation Report' or 'Global Mismatched and Adjustment Report'. | Alphanumeric | 40 |
| Parent Partner Name | The name of the Parent Partner for which the report has been generated. | Alphanumeric special | 100 |
| Parent Partner Id | The Partner Reference ID of the Parent Partner for which the report has been generated. | Alphanumeric special | 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) | |
| Partner ID | The Partner Reference ID of the partner OI/TI under the Parent Partner. | Alphanumeric special | 40 |
| Partner Name | The name of the partner OI/TI under the Parent Partner. | Alphanumeric special | 100 |
| ICA | The ICA associated with the Sponsor OI. Not populated in the U.S. | Numeric | 11 |
| Sponsor Bank Name | The name of the Parent Partner that is the Sponsor OI. | Alphanumeric special | 100 |
### Batch header and records {#batch-header-and-records}
| Column Name | Description | Format | Max Length |
|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-----------------------|
| Partner ID | The unique Partner Reference ID of the OI/TI. | Alphanumeric special | 40 |
| Partner Name | The name of the OI/TI. | Alphanumeric special | 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 | 40 |
| Acquiring ICA | The Mastercard-assigned Interbank Card Association (ICA) ID for the acquiring member registered with Mastercard. Not populated in the U.S. | Numeric | 11 |
| Acquiring Institution Name | The name of the acquiring institution. | Alphanumeric special | 100 |
| Acquiring Institution Country | For future use only. The field appears blank. | Blank | |
| Acquirer Reference ID | The 6-digit numeric value under which the acquiring member is registered with Mastercard. For GDR and GRN, a value will be present when it is a dual message transaction. For GMR, a value might be present. | Numeric | 6 |
| Acquiring Institution Processor ID | For future use only. The field appears blank. | Blank | |
| Acquiring Institution Identification Code | The 9-digit Federal Reserve Routing and Transit Number (RTN) of the acquiring member, or the 9-digit pseudo-number assigned to the acquiring member by Mastercard. | Numeric | 9 |
| Transfer Acceptor Name | The business name of the TI, which will be shown on the Recipient's statement. | Alphanumeric special | 22 |
| Transfer Acceptor ID | The Card Acceptor ID, which uniquely identifies a TI. | Alphanumeric special | 15 |
| Transfer Acceptor Mastercard Assigned Merchant ID | For future use only. The field appears blank. | Blank | |
| Transfer Acceptor Terminal ID | For future use only. The field appears blank. | Blank | |
| Merchant Category Code | The Mastercard-defined merchant category code, which identifies the type of business of the merchant. If provided, this merchant category code should match one of the valid codes set by the Mastercard rules. | Numeric | 4 |
| Transfer Acceptor City | For future use only. The field appears blank. | Blank | |
| Transfer Acceptor State | For future use only. The field appears blank. | Blank | |
| Transfer Acceptor Postal Code | For future use only. The field appears blank. | Blank | |
| Transfer Acceptor Country | For future use only. The field appears blank. | Blank | |
| Authorization Code | The transaction response identification code assigned by the Authorizing Institution. Not applicable for Account-based transfers. | Alphanumeric | 6 |
| Local Date Time | The date and time transaction was processed, in CST (ISO 8601 timestamp). This field will be blank if a processed time is not returned from the issuing network. | MM/DD/YYYY HH:MM:SS | |
| DateTime Created | The date and time transaction was originated in the API, in CST. | MM/DD/YYYY HH:MM:SS | |
| 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, and CASH. Mobile Money Account and Cash are not enabled as valid funding sources for the Mastercard Send Service. | Alpha special | 20 |
| Interchange Amount | 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 relevant network. Example: "0.050". If there is a negative interchange amount (debit) to the OI from the RI, this is shown as a negative value, for example "-0.930". Value not present in GDR. | Numeric, up to 999999999999 | 12 |
| Rate Type Indicator | Regulated Rate Type Indicator. Valid values: * B = Base regulated * 1 = Regulated with Fraud Protected * N = Not regulated * R = Regulated * U = Not regulated
Value not present in GMR and GDR. | Alphanumeric | 1 |
| MTI | The Message Type Identifier (MTI) describing the type of interchange message. | Numeric | 4 |
| Payment Type | The payment type associated with the transaction, for example, 'P2P' (General Person-to-Person Transfer). For a list of 3-character codes, see 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 | 3 |
| 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. | Numeric | 6 |
| Transaction 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. The last 4 digits or the full account number is provided. Participants should request configuration if they require the full account number. | Numeric | 19 |
| Transaction Amount | The amount transferred. Decimals are explicit. | Numeric, 3‑999999999999 | 12 |
| Transaction Currency | The currency code of the transaction amount. | Alpha | 3 |
| Transaction Funding PAN | This field is applicable only for transactions where a token is passed in the request (for Sender's account number). It shows the funding PAN associated with the token. The last 4 digits or the full account number are provided. Participants should request configuration if they require the full account number. Not applicable for Account-based transfers. | Numeric | 20 |
| 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 | 15 |
| Transaction Indicator | Indicates the Settlement position of CREDIT or DEBIT. | Alpha | |
| Transaction Status | The status of the transaction, which can be one of the following: * 0 = APPROVED * 1 = DECLINED | Numeric | 1 |
| Transaction Status Reason | A code indicating the reason for the decline (approved transactions will have the code 00): * 00 = Success * 04 = Failure
**NOTE:** If a transaction is in an UNKNOWN status, the code will be 04. However, customers must perform an API lookup (GET request) call to confirm final status. | Numeric | 2 |
| Transaction Type | The type of transaction. Valid values include: * FUNDING * PAYMENT * FUNDING_REVERSAL * PAYMENT_REVERSAL * FUNDING_REFUND * FUNDING_REPRESENTMENT * PAYMENT_REPRESENTMENT * FUNDING_CHARGEBACK * PAYMENT_CHARGEBACK * FUNDING_CHARGEBACK_REVERSAL * PAYMENT_CHARGEBACK_REVERSAL For descriptions, see [Transaction Type](https://developer.mastercard.com/mastercard-send/documentation/reports/transaction-type-status/index.md#transaction-type). | Alpha special | 50 |
| Unique Transaction Reference | The Unique Transaction Reference number for Mastercard Payment and Funding Transactions. | Alphanumeric | 19 |
| Sender First Name | The first name of the Sender. | Alphanumeric special | 100 |
| Sender Last Name | The last name of the Sender. | Alphanumeric special | 100 |
| Sender Account Number | The Sender's account (Funding Account) number. The last 4 digits or the full account number are provided. Participants should request configuration if they require the full account number. | Alphanumeric special | 50 |
| Sender Account Alias | The Account Alias of the Sender, if used in the API request. This is relevant to participants using the Consumer Mapping Service. | Alphanumeric special | 50 |
| Sender Add Ln1 | The first line of the Sender's street address. | Alphanumeric special | 50 |
| Sender City | The Sender's city. | Alphanumeric special | 25 |
| Sender State/Province | The Sender's state or province. For U.S.A. or Canada, the country's state or province is required. | Alpha | 3 |
| Sender Country | The 3-character ISO 3166-1 alpha-3 country code where the payment originated, if provided in the API request. | Alpha | 3 |
| Sender Postal Code | The Sender's ZIP code or postal code. | Alphanumeric special | 10 |
| Receiver First Name | The first name of the Recipient. | Alphanumeric special | 100 |
| Receiver Last Name | The last name of the Recipient. | Alphanumeric special | 100 |
| Receiver Account Number | The Receiving Account number. The last 4 digits or the full account number are provided. Participants should request configuration if they require the full account number. | Alphanumeric special | 50 |
| Receiver Account Alias | The Account Alias of the Recipient, if used in the API request. This is relevant to participants using the Consumer Mapping Service. | Alphanumeric special | 50 |
| Receiver Add Ln1 | The first line of the Recipient's street address. | Alphanumeric special | 50 |
| Receiver City | The Recipient's city. | Alphanumeric special | 25 |
| Receiver State/Province | The Recipient's state or province. For U.S.A. or Canada, the country's state or province is required. | Alpha | 3 |
| Receiver Country | The 3-character ISO 3166-1 alpha-3 country code of the Recipient. | Alpha | 3 |
| Receiver Postal Code | The Recipient's ZIP code or postal code. | Alphanumeric special | 10 |
| Network Advice Reason Code | The exception transaction advice code from the Receive Network. Value not present in GDR and GRN. | Alphanumeric | 7 |
| Network Advice Reason Description | The description of the exception transaction advice code from the Receive Network. Value not present in GDR and GRN. | Alphanumeric | 100 |
| Network Response Code | The response code provided by the relevant Receive Network, normally an ISO 8583 response code. 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. **For GDR:** 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 | 5 |
| System Trace Audit Number | The System Trace Audit Number (STAN) provided by the relevant Receive Network. 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 Account-based transfers. | Numeric | 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 Account-based transfers. | Numeric | 24 |
| Acquirer Reference Number | A unique transaction identification number (Acquirer reference number) generated by an Acquirer. A value will only be present when it is a dual message transaction. | Numeric | 23 |
| Switch Serial Number | A unique transaction identification number (switch serial number) generated or assigned by Mastercard Send and passed to the appropriate network. Not applicable for Account-based transfers. | Alphanumeric | 9 |
| Network Transaction Reference Id | A unique Transaction Reference ID that links the Funding and Payment Transaction. For the Mastercard Network, this field will be the same as the Unique Transaction Reference. Not applicable for Account-based transfers. | Alphanumeric | 19 |
| Payment Account Reference | The Payment Account Reference (PAR) is a unique value associated with a single PAN and attributed to all tokens associated with that PAN. A PAR can be used to link transactions containing PANs or tokens associated with the same underlying payment account. | Alphanumeric | 29 |
| 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. Value not present in GDR. | Numeric | 12 |
| Conversion Rate | The factor used in converting the Transaction Amount to the Settlement Amount. Value not present in GDR. | Numeric | 12 |
| Settlement Currency | The ISO currency code defining the currency of Settlement Amount. Value not present in GDR. | Alpha, ISO currency code | 3 |
| Settlement Service ID | The settlement service ID code uniquely identifying the Mastercard settlement service used by the receiving customer. Value not present in GDR. | Alphanumeric | 10 |
| Settlement Indicator | The settlement position for the transaction: DEBIT or CREDIT. Value not present in GDR. | Alpha | |
| Settled By | The settlement entity for the transaction. Valid values: * Mastercard * Visa * STAR * NYCE * PULSE * FPS
Value not present in GDR. | Alpha | 20 |
| Settlement Date | The date that the settlement service initiates settlement for the transaction. Value not present in GDR. | Date, YYYY-MM-DD | |
| Trace ID | Only populated for transactions that are authorized using the Mastercard Network. The Trace ID is assigned during authorization and provides a unique reference to all messages in the transaction's lifecycle. The value has two trailing spaces. | Alphanumeric | 15 |
| Exception Reason | The exception scenario. Valid values and descriptions: * Chargeback = Chargeback was initiated by the Issuer. * Processing Error = A relevant Receive Network reconciles a transaction differently from how it was processed in Mastercard Send. * UNKNOWN = A relevant Receive Network has not responded to Mastercard Send or has reconciled a transaction that is not recognized in Mastercard Send.
Value not present in GDR and GRN. | Alpha | 20 |
| Payment UID | The unique ID that was passed to the Faster Payments Network. Applicable only for transactions routed through Faster Payments. | Alphanumeric | 36 |
| Faster Payment ID | A unique ID generated by the Faster Payments Network. Applicable only for transactions routed through Faster Payments. | Alphanumeric | 36 |
| Destination Sort Code | The sort code for the Recipient account. Applicable only for transactions routed through Faster Payments. | Alphanumeric | 6 |
| Destination Account Name | The Recipient's name on the account. Applicable only for transactions routed through Faster Payments. | Alphanumeric special | 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. | Alphanumeric | 8 |
| Source Sort Code | The sort code for the Funding Account. Applicable only for transactions routed through Faster Payments. | Alphanumeric | 6 |
| Source Account Name | The name on the Funding Account. Applicable only for transactions routed through Faster Payments. | Alphanumeric special | 40 |
| Transfer Priority | The type of Payment instruction. Applicable only for transactions routed through Faster Payments. | Alpha | 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 | 125 |
| Extended Precision Amounts | Interchange Amount calculated to 6 decimals converted to the reconciliation currency. This field will only be populated for dual message transactions when customers are participating in the Extended Decimal Precision (EDP) service. Value not present in GDR. | Numeric | 18 |
| Sender Account Type | The Funding Account type. Valid values: * 00 = Other * 01 = RTN (Bank Account) * 02 = IBAN * 03 = Card Account * 04 = Email * 05 = Phone Number * 06 = Bank account number (BAN) + Bank Identification Code (BIC) * 07 = Wallet ID * 08 = Social Network ID | Numeric | 2 |
| Receiver Account Type | The Receiving Account type. Valid values: * 00 = Other * 01 = RTN (Bank Account) * 02 = IBAN * 03 = Card Account * 04 = Email * 05 = Phone Number * 06 = Bank account number (BAN) + Bank Identification Code (BIC) * 07 = Wallet ID * 08 = Social Network ID | Numeric | 2 |
| ECI | The electronic commerce indicator identifying the level of security for an e-commerce transaction. For GDR and GRN, a value will be present for Funding and Payment Transactions. For GMR, a value might be present. | Numeric | 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 | 2 |
| Acceptance Brand | The acceptance brand code for the Mastercard account: DMC, MCC, or MSI. Value only present in GDR. | Alpha | 3 |
| Reserved7 | Reserved for future use. *This field is due to become 'Transaction Link ID (TLID)' 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=7).* | | |
| Reserved8 | Reserved for future use. | | |
| Reserved9 | Reserved for future use. | | |
| Reserved10 | Reserved for future use. | | |
| Reserved11 | Reserved for future use. | | |
| Reserved12 | Reserved for future use. | | |
| Reserved13 | Reserved for future use. | | |
| Reserved14 | Reserved for future use. | | |
| Reserved15 | Reserved for future use. | | |
| Reserved16 | Reserved for future use. | | |
| Reserved17 | Reserved for future use. | | |
| Reserved18 | Reserved for future use. | | |
| Reserved19 | Reserved for future use. | | |
| Reserved20 | Reserved for future use. | | |
| Reserved21 | Reserved for future use. | | |
| Reserved22 | Reserved for future use. | | |
| Reserved23 | Reserved for future use. | | |
| Reserved24 | Reserved for future use. | | |
| Reserved25 | Reserved for future use. | | |
| Reserved26 | Reserved for future use. | | |
| Reserved27 | Reserved for future use. | | |
| Reserved28 | Reserved for future use. | | |
| Reserved29 | Reserved for future use. | | |
| Reserved30 | Reserved for future use. | | |
| | **Optional:** | | |
| *Custom Field Name* | Up to four custom fields can be added to the GDR and GRN. 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 = 40 Value = 200 |
### Batch trailer {#batch-trailer}
| Column Name | Description | Format |
|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|
| Batch Count | The total number of detail (201) records in the batch. | Numeric, 1‑999999999999 |
| Batch Checksum | The absolute value of all the batch transaction totals to confirm 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 detail (201) records in the file. | Numeric, 1‑999999999999 |
| File Checksum | The absolute value of all the batch transaction totals to confirm 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 |
For GDR, the checksum values will have a currency exponent appropriate to the transaction amounts (no scaling). For example, if the amounts are a mix of exponent 2 (such as 123.45) and 3 (such as 123.456), the checksum will have an exponent of 3.
For GRN and GMR, the checksum will have an exponent of 3 regardless of the transaction amount exponent. The checksum is purely for validating the integrity of the file and should not be used as the total settlement amount. To calculate the total settlement amount, sum the Settlement Amount for each transaction within the report, which will all be in the same Settlement Currency.