Skip to main content
Used when the settlement date differs from the one submitted in the Transactions files.
Applicalbe to Balance Type = Deposit Only
This file captures transactions where the actual settlement date differs from the one submitted in the Transactions file. It provides the updated settlement_date and supports financial reconciliation by ensuring accurate alignment of transaction timing.

Inaccurate data may risk proper account funding and disrupt program operations.

Overview

The purpose of this file is so that you can report when the settlement_date of a transaction previously reported in a Transaction file was different than initially forecasted. As an example, an ACH or Wire transaction can be initiated and reported as a transaction, but actual money movement may not always be deterministic (e.g., it may be held in manual review and not posted at the time you initially predicted). By reporting an updated settlement_date, this allows Lead to run reconciliation of bank accounts (typically an FBO) with the latest information of when funds should have been sitting in the account. In contrast, effective_at dates reported in the Transaction file cannot be updated. effective_at represents when the available balance for an end-user was updated. This is a deterministic timestamp and is independent of when underlying funds settle, which cannot always be accurately forecasted.
For all optional fields where you do not plan to pass through data, please include the header and an empty value.

Schema

IDS & Details

FieldDescriptionRequiredData Type
transaction_idThe unique ID for the transaction. Before including an ID in this file, please ensure that it has previously been submitted in the Transactions File so that Lead has an existing awareness of the ID.Requiredstring

Transaction Information

FieldDescriptionRequiredData Type
settlement_dateThe updated settlement date of this transaction.Requireddate
YYYY-MM-DD
transfer_idThe unique IDs for the related transfer object, if applicable (e.g. the ACH ID or Wire ID or Internal Transfer ID generated by Lead).Required if transfer_type = ach wire internal_transfer at Leadstring

Other

FieldDescriptionRequiredData Type
generated_atThe day this file is generated. This should always be the date the file is sent to Lead Bank.Requireddatetime
ISO8601
effective_atThe timestamp of when the related object(s) were polled to collect the information for this record.Requireddatetime
ISO8601

Transaction Type

Since the timing of certain transaction and transfer types are more deterministic than others, only the below combinations of transaction and transfer types should be included in this file. Any other combinations not listed below are not permitted or supported.
Transaction TypeTransfer Type
debitach, wire, check, internal_transfer, external_transfer, out_of_bank_settlement
creditach, wire, check, internal_transfer, external_transfer, out_of_bank_settlement
dispute_provisionalinternal_transfer, external_transfer, out_of_bank_settlement
dispute_lostAll available transfer types
escheatmentach, wire, check, internal_transfer, external_transfer, out_of_bank_settlement
charge_off_recoveryAll available transfer types
rewards_redeemedAll available transfer types
fee (overdraft)All available transfer types
fee (periodic maintenance)All available transfer types
fee (card)All available transfer types
fee (international transaction)All available transfer types
fee (other)All available transfer types
interest_paidAll available transfer types
adjustmentAll available transfer types