ACH file integrations are not currently available for new partners. Please refer to our full suite of API-based ACH functionality here. Overview
You will transmit ACH files in Nacha format via SFTP.
We validate all incoming files to ensure completeness and compliance with standard Nacha formatting before forwarding to the Federal Reserve for further processing.
When Lead delivers a file to your SFTP server, you will receive a Slack notification. You will also receive a Slack alert if a file fails validation or contains formatting issues.
Folder Structure
All program related files will be dropped into folders on the SFTP server with the following access:
- Read/Write: For all folders where you are the submitter
- Read Only: For folders where Lead is the submitter
File Naming
We utilize a consistent filename format that aims to:
- Indicate the type of file
- Indicate the content represented in the particular file
- Prevent filename collisions for similar files
20260115T171640Z_incoming_ach_forwards_1768497400.ach
File versions can be represented by either an epoch timestamp (not ISO 8601) or an incremental version label such as v1, v2, etc. Each subsequent submission must use a higher version value.
Example Invalid File Name
If the initial file version is invalid or changes are required, you must submit the updated version of the file — with an updated epoch time of version label, such as “v2”.
Nacha file headers have some flexibility on the values of certain fields. The following table outlines what values to use/expect for certain fields for both outgoing and incoming files.
We do not require you to send a balanced Nacha file.
