Skip to main content

Overview

You’ll transmit Nacha formatted ACH files via SFTP.
Standard Nacha formatting guidelinesWe validate your incoming files to ensure completeness and formatting accuracy before forwarding to the Fed for further processing.
When Lead delivers a file to your SFTP server, we send you a Slack alert. If the file has issues or fails validation, you’ll also receive a Slack alert.

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
FileSubmitterFolder NameFile Example
ACH OutgoingYouach/outgoing20260115T171640Z_outgoing_ach_1768557400.ach
ACH FailedLeadach/failed20260115T171640Z_outgoing_ach_1768557400.ach
ACH IncomingLeadach/incoming20260115T171640Z_incoming_ach_retun_noc_768557400.ach

20260115T171640Z_incoming_ach_return_768557400.ach

20260115T171640Z_incoming_ach_noc_768557400.ach

20260115T171640Z_incoming_ach_forward_768557400.ach
ACH ProcessedLeadach/processed20260115T171640Z_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 particulare file
  • Prevent filename colliions for similar files

Example File Format

20260115T171640Z_incoming_ach_forwards_1768497400.ach
20260115T171640Zincoming_ach_forwards1768497400
Content IdentifierFile TypeEpoch 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 fiels from colliding and preserves generation time ordering for similarly name 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”.
Original20260115T171640Z_incoming_ach_forwards_1768497400.ach
Updated Resubmission20260115T171640Z_incoming_ach_forwards_1768642400.ach

Notice the updated epoch timestamp

File Header Guidelines

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.
Field NameOutoing (You to Lead)Incoming (Lead to You)
Immediate OriginThis 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 NameBlankLead Bank
Immediate Destination1010196449999999999 Contact Lead if you need to set this to a specific value.
File Creation DateDetermined at file generation timeDetermined at file generation time
File Creation TimeDetermined at file generation timeDetermined at file generation time
File ID MidifierDetermined at file generation timeDetermined at file generation time
Reference CodeBlankBlank