Setting Up SFTP Bank Connections in Numeric Cash Management

Last updated: June 22, 2026

Some enterprise banks deliver transaction data through Secure File Transfer Protocol (SFTP) rather than aggregator feeds. This guide walks through the setup process, the timeline, what your treasury team needs to send the bank, and how the transition from manual uploads to live SFTP works.

Banks That Typically Require SFTP

The following enterprise banks generally deliver Bank Administration Institute Version 2 (BAI2) files through SFTP:

  • JPM Access (JPMorgan)

  • Wells Fargo CEO and Wells Fargo Vantage

  • Bank of America

  • Citi

If your bank isn't on this list but doesn't connect through Plaid or Quiltt, your Solutions Manager will let you know whether SFTP is an option.

Setup Timeline

Plan for 4 to 6 weeks from initial bank request to live connection. The timeline depends on:

  • Your bank's technical team availability

  • How quickly your treasury team can initiate the request internally

  • Bank-specific requirements (some require additional forms or testing windows)

Your Solutions Manager will help you plan around this lead time. While the SFTP connection is being provisioned, you can use manual uploads to begin building rules and running a soft close.

The Setup Process

  1. Kickoff alignment: Confirm with your Solutions Manager which accounts need SFTP and which can use Plaid, Quiltt, or manual uploads.

  2. Internal request: Your team sends the request to your bank. Numeric provides a template you can adapt (see below).

  3. Bank assignment: The bank assigns a technical contact to coordinate the setup.

  4. Connection coordination: Numeric works directly with your bank's technical contact to configure the SFTP endpoint, file format, and delivery schedule.

  5. Testing: The bank sends a test file. Numeric validates that the data parses correctly and maps to the right accounts.

  6. Go-live: Daily BAI2 files start flowing automatically.

What "Daily Prior-Day" Means

BAI2 files delivered through SFTP cover the prior business day's activity. Each morning, the bank sends a file with the transactions that posted the day before. Files typically arrive overnight or early in the morning, so the team can start daily reconciliation by mid-morning at the latest.

Template Language to Send Your Bank

The same template works across all SFTP-supported banks. Don't forget to cc sftp@numeric.io when you send the email!

Subject: New SFTP Connection

Hi,

We're implementing a cash management and treasury platform called Numeric and would like to establish an SFTP connection with [bank name] to enable secure delivery of our BAI2 files for daily cash and transaction reporting.

To confirm what we're requesting:

  • Connection type: SFTP; new PULL connection.

  • File format: BAI2.

  • Reporting: Prior day.

Could you let us know the appropriate next steps to set up this connection on your end? I've included our contact at Numeric on this email to coordinate the technical setup and address any questions as they arise.

While You Wait

During the 4 to 6 week setup window:

  • Download BAI2 or CSV files from your banking portal and use manual uploads.

  • Build and test rules against the manually uploaded data.

  • Run a soft close in parallel with your legacy process.

When the SFTP connection goes live, the dataset will look identical to the manual upload data, so your rules and matches won't break.

What Happens at Go-Live

When the SFTP connection goes live, your Solutions Manager will coordinate the transition from manual uploads to the live feed:

  • Historical backfill: SFTP backfill is configured at setup. Your Solutions Manager will confirm the backfill date with you so the live feed picks up where manual uploads left off, with no overlap or gap.

  • Manual uploads pause: Once SFTP is delivering reliably, your team stops uploading files manually. The dataset looks identical whether the data came from a manual upload or the SFTP feed, so your rules and matches won't break.

Don't run manual uploads and SFTP for the same date range. Overlapping data creates duplicate bank lines that break existing matches and trigger false exceptions. Your Solutions Manager will sequence the cutover so the two never overlap.

Troubleshooting

If you don't hear back from your bank within a week of sending the request, follow up with your treasury contact or relationship manager. Bank technical teams often need a nudge to prioritize SFTP requests.

Permissions

  • Initiating SFTP setup: requires coordination with your Solutions Manager.

  • Reviewing files after go-live: Administrator, Manager, Staff, and Viewer can view transaction data per their assigned role.

Need help? Contact your Solutions specialist or reach out to support@numeric.io.