Field Reference

Use this guide as a detailed field-by-field map when you are parsing the Disbursement & Fee Report (DFR), building imports, or troubleshooting values in your own reporting systems. When you use this reference, focus on the field groups that matter most for your current task.

If you are integrating the DFR, focus on:

Identification fields: Record ID, Merchant Account ID, Transfer ID, Order ID, Customer Id
Amount fields: Gross Settlement Amount, Total Net Fees, Net Disbursed Amount, Tax Amount

If you are troubleshooting fees, focus on:

Amount fields: Gross Settlement Amount, Total Net Fees, Net Disbursed Amount, Tax Amount
Fee Breakdown fields: Variable Fee, Fixed Fee, Foreign Exchange Fee, Cross-border Fee, Chargeback Protection Fee
Interchange fields: Plan Code, Interchange Currency, Interchange Rate, Interchange Fixed, Total Interchange Fees
Scheme & Pass-through fee fields: Total Scheme Fees, Total Pass-through Fees, Total Processing Fees

Prerequisites: Report Structure

RS (Report Summary) Fields

The RS section summarizes each bank transfer. Start here for reconciliation.

Core Reconciliation Fields

Use these fields when you need to match a bank deposit to a specific transfer and confirm that the DFR totals align with your bank statement.

Field	Data Type	Nullable	Description
`Merchant Account ID`	String	No	The merchant account that processed these transactions
`Transfer ID(s)`	String	Yes	Bank statement reference. PRIMARY RECONCILIATION KEY. Match exactly to the bank statement. If Net Disbursed exceeds banking limits, multiple Transfer IDs will be comma-separated.
`Bank Account`	String	Yes	Last 2 digits of the receiving bank account. Useful if multiple bank accounts configured.
`Currency`	String (ISO 4217)	No	ISO 4217 3-letter currency code. All monetary amounts in this row are in this currency.
`Net Disbursed Amount`	Decimal	Yes	Actual bank deposit/withdrawal. MUST MATCH THE BANK STATEMENT.

Amount Breakdown Fields

Use these fields when you want to see how each bank transfer breaks down into sales, refunds, disputes, returns, adjustments, and fees.

Field	Data Type	Nullable	Description
`Sales`	Decimal	Yes	Sum of Gross Settlement Amount for all Sale records
`Refunds`	Decimal	Yes	Sum of Gross Settlement Amount for all Refund records (includes Referenced and Non-Referenced)
`Disputes`	Decimal	Yes	Net sum of chargebacks and chargeback reversals
`Returns`	Decimal	Yes	Sum of all Returns (ACH/direct debit failures)
`Adjustments`	Decimal	Yes	Sum of all Adjustments (reserve movements, manual adjustments)
`Other`	Decimal	Yes	Sum of Gross Settlement Amount where Record Type is not Sale, Refund, or Dispute
`Gross Fees`	Decimal	Yes	Total fees tracked but not yet debited. Gross Settlement only; zero in Net Settlement.
`Net Fees`	Decimal	Yes	Total fees already deducted from transactions. Net Settlement only; zero in Gross Settlement.

Error Recovery Fields

Use these fields when a transfer includes recovered amounts from failed disbursements or other error conditions and you need to see what was carried forward.

Field	Data Type	Nullable	Description
`Balance`	Decimal	Yes	Funds held in system balance due to bank issues. Contact support if populated.
`Previous failed disbursement amount(s)`	Decimal	Yes	Amount from a prior failed transfer now included in this transfer. Multiple values comma-separated.
`Previous transfer ID(s)`	String	Yes	Transfer ID of the failed disbursement being recovered. Multiple values comma-separated.

RD (Report Details) Fields

The RD section provides transaction-level detail. Filter by Transfer ID to see all items in a specific bank transfer.

Total: 65 fields

Identification Fields

Use these fields when you are mapping DFR records into your own systems and need stable IDs to track, join, or deduplicate transactions and events.

Field	Data Type	Nullable	Description
`Record ID`	String	Yes	Unique identifier for this transaction or event. Primary key for tracking.
`Merchant Account ID`	String	No	The merchant account that processed this record.
`Transfer ID`	String	Yes	Links this record to its RS summary row. Used to reconcile deposit entries against line items.
`Order ID`	String	Yes	Your internal order/transaction reference (only present if passed at transaction time). Used to cross-reference with your internal systems.
`Customer Id`	String	Yes	Unique identifier for the customer. Can be Braintree-generated or merchant-supplied at customer record creation.

Transaction Classification Fields

Use these fields when you need to understand what happened for each record—sale, refund, dispute, return, fee, adjustment, or transfer—and route it to the right accounting or reporting bucket.

Field	Data Type	Nullable	Description
`Record Type`	String	No	High-level category: Sale, Refund, Dispute, Return, Fees, Adjustments, Transfer, Failed Disbursement
`Record Subtype`	String	Yes	Specific classification within Record Type. New subtypes may be introduced with new fees and regional availability. See Transaction Types for all values.

Account Fields

Use these fields when you need to group or filter records by merchant account, payment instrument, or other account-level attributes.

Field	Data Type	Nullable	Description
`Account Name`	String	Yes	Business name visible to the consumer. Primary value is the Descriptor set in the API; secondary value is Business name on file.
`Account ID`	String	Yes	Account ID for the specific Payment Instrument. For American Express Direct: the Amex Account ID. For Venmo (US only): Venmo Profile ID.

Date/Time Fields

Use these fields when you are analyzing timing, such as comparing authorization, settlement, and disbursement dates or building time-based reports.

Field	Data Type	Nullable	Description
`Created At`	DateTime	No	UTC timestamp when record was created. Format: `YYYY-MM-DDTHH:MM:SSZ`
`Settlement Date`	Date	Yes	Date the card network confirmed settlement. Local timezone to acquiring region. Format: `YYYY-MM-DD`
`Disbursement Date`	Date	Yes	Date the bank transfer was initiated. Local timezone to acquiring region. Format: `YYYY-MM-DD`

Currency Conversion Fields

Use these fields when you work with multi-currency flows and need to understand how presentment amounts were converted into settlement currency.

Field	Data Type	Nullable	Description
`Presentment Currency`	String (ISO 4217)	Yes	Currency of original customer transaction (e.g., USD, CAD, AUD)
`Gross Presentment Amount`	Decimal	Yes	Transaction amount in customer's native currency
`Exchange Rate`	Decimal	Yes	Conversion rate from Presentment to Settlement currency
`Settlement Currency`	String (ISO 4217)	No	Your configured settlement currency

Amount Fields

Use these fields when you are checking per-transaction amounts for reconciliation, verifying fee math, or explaining why a specific record contributed a given amount to a transfer.

Field	Data Type	Nullable	Description
`Gross Settlement Amount`	Decimal	Yes	Transaction amount in settlement currency before fees (the "face value")
`Total Gross Fees`	Decimal	Yes	Fees accrued for later billing (Gross Settlement only)
`Total Net Fees`	Decimal	Yes	Fees deducted immediately (Net Settlement only)
`Net Disbursed Amount`	Decimal	Yes	Amount contributing to bank transfer. Calculated as: Gross Settlement Amount − Total Net Fees
`Tax Amount`	Decimal	Yes	Tax amount passed during transaction (presentment currency). Null if not provided.
`Tax Exempt`	Boolean	Yes	Whether transaction was marked tax exempt. Merchant-supplied value.

Linking Fields

Use these fields when you are tracing relationships between records, such as linking refunds and disputes back to the original sale, or following a dispute across multiple DFR files.

Field	Data Type	Nullable	Description
`Original Record ID`	String	Yes	Links to original sale for refunds/disputes. A refund record contains the Original Record ID of the Sale.
`Original Order ID`	String	Yes	Order ID of the original Sale transaction
`Dispute ID`	String	Yes	Tracks dispute case across multiple DFR files
`Dispute Case Number`	String	Yes	Dispute Case Number of the Dispute associated with this record
`Purchase Order Number`	String	Yes	PO number if provided during transaction
`Acquirer Reference Number`	String	Yes	ID assigned by acquirer for escalations

Payment Details Fields

Use these fields when you need to analyze payments by method, network, or channel, such as card vs bank, card brand, or digital wallet.

Field	Data Type	Nullable	Description
`Payment Instrument Type`	String	Yes	Payment method: Credit Card, Debit Card, Prepaid Card, Apple Pay, Google Pay, Bank Account (US only), Venmo (US only), Samsung Pay. New types may be added.
`Payment Instrument Subtype`	String	Yes	Card brand: MasterCard, Visa, Discover, American Express, Union Pay, US Personal Account, US Business Account, Maestro, Elo (Brazil), Carte Bancaire, Hipercard (Brazil), Venmo Wallet. Apple/Google Pay adds card type prefix.
`Payment Network`	String	Yes	Card network: MasterCard, Visa, EFTPOS, Access, Pulse, Discover, American Express
`Card Product Name`	String	Yes	Specific card product tier used by buyer (e.g., Visa Signature, World Elite)
`Payment Method Token`	String	Yes	Vault token if payment method was stored
`Payment Entry Mode`	String	Yes	Entry method used for the Payment (card present transactions)
`Payment Channel`	String	Yes	The channel for the payment transaction
`Source`	String	Yes	The source of the transaction (card present)

Card Details Fields

Use these fields when you are doing card-level analysis, such as issuer behavior, country mix, or regulated vs unregulated debit.

Field	Data Type	Nullable	Description
`BIN`	String	Yes	First 6-8 digits of card number identifying the issuer
`Durbin Regulated`	Boolean	Yes	Reports if the BIN is regulated. Used for PIN-less transactions to identify whether the Debit BIN is regulated.
`Issuing Bank`	String	Yes	Name of card-issuing bank
`Card Issuing Country`	String	Yes	Country where card was issued (2-letter ISO)
`Authorization Code`	String	Yes	Code generated by the card issuing bank at time of successful pre-authorization
`Direct Bank Return Code`	String	Yes	ACH return reason code (R01, R02, R10, etc.) for rejected direct payments

In-Store Transaction Fields

Use these fields when you are working with card-present or in-store transactions and need to break down activity by store or terminal.

Field	Data Type	Nullable	Description
`Store Id`	String	Yes	Merchant or Braintree-supplied Store ID for point-of-sale records. In-store transactions only.
`Reader Id`	String	Yes	Terminal ID of the device used to make the payment. In-store transactions only.

Installment Fields (Brazil Only)

Use these fields when you are handling Brazilian installment transactions and need to understand how each installment is paid out over time.

Field	Data Type	Nullable	Description
`Number Of Installments`	Integer	Yes	Total number of installments for paying the transaction amount. Brazil only.
`Installment Number`	Integer	Yes	The installment number being paid out in this disbursement. Brazil only.

Bank Account Field

Use this field when you disburse to multiple bank accounts and need to verify which account received a particular transfer.

Field	Data Type	Nullable	Description
`Bank Account`	String	Yes	Last 2 digits of the bank account where funds were disbursed (previously 4 digits)

Fee Breakdown Fields

Use these fields when you are troubleshooting how processing fees were constructed on a transaction, such as fixed vs variable, FX, cross-border, or chargeback protection.

Field	Data Type	Nullable	Description
`Variable Fee`	Decimal	Yes	Percentage-based fee component assessed by Braintree
`Fixed Fee`	Decimal	Yes	Fixed per-transaction fee component assessed by Braintree
`Foreign Exchange Fee`	Decimal	Yes	FX conversion fee assessed by Braintree
`Cross-border Fee`	Decimal	Yes	Fee for international transactions assessed by Braintree
`Chargeback Protection Fee`	Decimal	Yes	Fee for chargeback protection if enrolled

Interchange Fields

Use these fields when you are analyzing interchange costs or validating how card-network pricing was applied to specific events.

Field	Data Type	Nullable	Description
`Plan Code`	String	Yes	Interchange Plan Code assessed on the transaction
`Interchange Currency`	String (ISO 4217)	Yes	Currency in which interchange fees were charged
`Interchange Rate`	Decimal	Yes	Rate at which interchange was applied to the settlement amount
`Interchange Fixed`	Decimal	Yes	Per-transaction Interchange fee applied to the event
`Total Interchange Fees`	Decimal	Yes	Total interchange fees applied to the event

Scheme & Pass-through Fee Fields

Use these fields when you want to understand total pass-through and processing fees at the event level or reconcile fee months to your own statements.

Field	Data Type	Nullable	Description
`Total Scheme Fees`	Decimal	Yes	Card network fees applied to the event
`Total Pass-through Fees`	Decimal	Yes	Sum of Total Interchange Fees + Total Scheme Fees
`Total Processing Fees`	Decimal	Yes	Total Braintree processing fees charged to the event
`Pass-through Fee Month`	String (YYYY-MM)	Yes	Month the pass-through fee was assessed for disbursement
`Processing Fee Month`	String (YYYY-MM)	Yes	Month the processing fee was assessed for disbursement

Description & Metadata Fields

Use these fields when you need human-readable context for a record or when you rely on counts and custom metadata in downstream reporting.

Field	Data Type	Nullable	Description
`Description`	String	Yes	Contextual description for: Fee program name, Event fees, Aggregate scheme fees, Fee adjustment, Chargeback description, Manual adjustment, Processing Adjustments
`Count`	Integer	No	The count of events in this record
`Custom fields`	String	Yes	Custom fields associated with the record type

Next: Settlement Models