Custom data files (CDFs) are made available through the same method as <<glossary:RDF>>s. In general, CDFs are available a few hours after the RDFs. CDF data sets are securely delivered via SFTP in CSV format.

This document contains details about each of the CDFs, including field descriptions:

• [Expired Auth](🔗)

• [Early ACH](🔗)

• [ACH Returns](🔗)

• [Incoming ACH](🔗)

• [Overdraft](🔗)

• [Settlement](🔗)

• [MC SAFE Report](🔗)

• [Chargeback and Disputes](🔗)

• [Direct Deposit Switch](🔗)

• [Fleet Data](🔗)

### Expired Auth CDF

The Expired Auth CDF provides the expired authorizations for the prior day.

This table contains default fields for the Expired Auth CDF.

• The primary key for this file is `Program ID` + `Transaction ID` + `Network Code`.

• The filename format is `expired_auth_%Y%m%d.csv`.

📘

Note

The Expired Auth CDF contains data from these networks only: Mastercard debit, Mastercard credit, Visa, STAR.

### Early ACH CDF

The Early ACH CDF provides the ACH details along with the number of days of early posting.

This table contains standard fields for the Early <<glossary:ACH>> CDF.

• The primary key for this file is `Transaction ID`.

• The filename format is `early_ach_report_%Y%m%d.csv`.

### ACH Returns CDF

The ACH Returns CDF provides details on returned ACH transactions for the prior day.

This table contains default fields for the ACH Returns CDF.

• The primary key for this file is `TransID`.

• The filename format is `ach_returns_report_%Y%m%d.csv`.

### Incoming ACH CDF

The Incoming ACH CDF provides all incoming ACH for the prior day.

This table contains default fields for the Incoming ACH CDF.

• The primary key for this file is `Authorization Code` + `Transaction Type`.

• The filename format is `incoming_ach_report_%Y%m%d.csv`.

### Overdraft CDF

The Overdraft (OD) CDF provides information related to overdraft DDA accounts for prior days.

This table contains default fields for the OD CDF.

• The primary key for this file is `GPR_XID`.

• The filename format is `od_details_DDA_%Y%m%d.csv`.

### Settlement CDF

The Settlement CDF provides a BIN settlement summary report (similar to gAnalytics).

This table contains default fields for the Settlement CDF.

• The primary key for this file is `Basebin` + `Date` + `Network`.

• The filename format is `settlement_%Y%m%d.csv`.

📘

Note

This report looks back one day for Visa, Mastercard, and Discover; two days for Pulse, Allpoint and STAR; and three days for Maestro/Cirrus. In comparison, the gAnalytics report looks back one day for all.

### MC SAFE Report CDF

The MC SAFE Report CDF provides a BIN settlement summary report (similar to gAnalytics).

This table contains default fields for the MC SAFE Report CDF.

• The primary key for this file is `ARN`.

• The filename format is `mc_safe_<ica>%Y%m%d.csv`.

### Chargeback and Dispute CDF

The Chargeback and Dispute CDF provides chargeback and dispute information for the prior day. It is similar to the _Dispute Tracker Log_ report in gAnalytics.

This table contains default fields for the Chargeback and Dispute CDF.

• The primary key for this file is `DISPUTE_ID`.

• The filename format is `Dispute_Chargeback_Report_%Y%m%d.csv`.

• To link the transactions in this file to the original transactions in the Posted Transactions RDF, match the `AUTHORIZATION_CODE` + `ASSOCIATION` in this file with the `AUTHORIZATION CODE` + `NETWORK CODE` of the RDF.

### Direct Deposit Switch CDF

The Direct Deposit Switch CDF provides data on <a href="ref:direct-deposit-switch" target="_blank">direct deposit switch</a> transactions.

This table contains default fields for the Direct Deposit Switch CDF.

• The primary key for this file is `galileo_guid`.

• The filename format is `ddswitch_trans_%Y%m%d.csv`.

### Fleet Data CDF

The Fleet Data CDF contains the fleet data to enrich posted transactions.

• The filename format is `fleetfile_%Y%m%d.csv`.

• See <a href="doc:fleet-cards" target="_blank">Fleet Cards</a> for more information about the product.

• To interpret the codes in the fields, obtain the _IPM Clearing Formats_ guide from Mastercard.

For this CDF, three or more addendum rows are provided per transaction, according to this criteria:

• **Row 1** — Corporate card common data. Provided when the associated first presentment/1240 message meets all of these conditions:

  • The product is any corporate product.

  • The card acceptor country code (DE045 subfield 6) is "USA".

  • The cardholder transaction type (DE003 subfield 1) is `00` (purchase) or `18` (unique).

  • The transaction is not a reversal.

• **Row 2** — Corporate fleet transaction information. Provided when the associated first presentment/1240 message is a Mastercard Corporate Fleet Card transaction for a fuel or non-fuel purchase.

• **Rows 3–n** — Corporate line-item detail. Provided when non-fuel items are purchased alongside fuel, using a fleet card.

The corporate line-item detail is provided for each additional non-fuel item purchased using a fleet card, so if a cardholder purchases five items in one transaction, the CDF will contain seven rows: one common data requirements row, one fleet transaction information row and five detail addendum rows. All rows that belong to the same transaction will have the same `auth_code` + `network_code`.

The `auth_code` + `network_code` is the foreign key to the associated financial transaction in the <a href="doc:secondary-rdf-reference#posted-transactions-rdf-fields" target="_blank">Posted Transactions RDF</a>, matching the `AUTHORIZATION CODE` and `NETWORK CODE` fields in the RDF.

#### All rows

This table contains fields that are present in all row types.

##### Example

The three addenda types will be denoted as follows, assuming the purchase of three items:

**Row 1: Corporate card common data requirement** `usage_code: 98` `industry_red_no: 000` `occurrence_ind: 001`

**Row 2: Corporate fleet transaction info** `usage_code: 98` `industry_rec_no: 002` `occurrence_ind: 001`

**Row 3: Corporate line-item detail** `usage_code: 98` `industry_rec_num: 950` `occurrence_ind: 001`

**Row 4: Corporate line-item detail** `usage_code: 98` `industry_rec_num: 950` `occurrence_ind: 002`

**Row 5: Corporate line-item detail** `usage_code: 98` `industry_rec_num: 950` `occurrence_ind: 003`

#### Row 1 fields

These fields will be inside the `corporate_card_detail` field in a row that has `industry_rec_no: 000`. All of the top-level fields will be present, even if the value is `Null`.

##### Example

#### Row 2 fields

These fields will be inside the fleet_detail field in a row that has `industry_rec_no: 002`. All of the top-level fields will be present, even if the value is `Null`.

##### Example

#### Rows 3-n fields

These fields will be inside the `line_item_detail` field in a row that has `industry_rec_no: 950`. All of the top-level fields will be present, even if the value is `Null`.

##### Example