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 | Submitter | Folder Name | File Example |
|---|
| ACH Outgoing | You | ach/outgoing | 20260115T171640Z_outgoing_ach_1768557400.ach |
| ACH Failed | Lead | ach/failed | 20260115T171640Z_outgoing_ach_1768557400.ach |
| ACH Incoming | Lead | ach/incoming | 20260115T171640Z_incoming_ach_return_noc_768557400.ach
20260115T171640Z_incoming_ach_return_768557400.ach
20260115T171640Z_incoming_ach_noc_768557400.ach
20260115T171640Z_incoming_ach_forward_768557400.ach |
| ACH Processed | Lead | ach/processed | 20260115T171640Z_outgoing_ach_768557400.ach |
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
| 20260115T171640Z | incoming_ach_forwards | 1768497400 |
|---|
| Content Identifier | File Type | Epoch Time of File Generation |
This will correspond to the content of the file.
For loan origination files, this will be a date.
For ACH files, this will be a date and time. | This indicates the meaning and format of the file. | This serves to prevent similar files from colliding and preserves generation time ordering for similarly named files. |
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”.
| Original | 20260115T171640Z_incoming_ach_forwards_1768497400.ach |
|---|
| Updated Resubmission | 20260115T171640Z_incoming_ach_forwards_1768642400.ach
Notice the updated epoch timestamp |
We do not require you to send a balanced Nacha file.
| Field Name | Outgoing (You to Lead) | Incoming (Lead to You) |
|---|
| Immediate Origin | This field is not used by the Lead’s ACH system as we have other ways to identify clients. We use CompanyID on the batch header for posting to identify your account. Please specify as 9999999999. Partners may in some cases need to specify this value and should work with Lead if this is needed. | 101019644 (Lead’s Routing Number) |
| Immediate Origin Name | Blank | Lead Bank |
| Immediate Destination | 101019644 | 9999999999 Contact Lead if you need to set this to a specific value. |
| File Creation Date | Determined at file generation time | Determined at file generation time |
| File Creation Time | Determined at file generation time | Determined at file generation time |
| File ID Modifier | Determined at file generation time | Determined at file generation time |
| Reference Code | Blank | Blank |
