Used when the settlement date differs from the one submitted in the Transactions files.
Applicable 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
Inaccurate data may risk proper account funding and disrupt program operations.
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 thesettlement_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.