SFTP integration

Connect files from banks, suppliers and legacy applications with Uplyst. Bring recurring data exchanges into the same business context as your connected enterprise systems.

Connect recurring files from partners and legacy systems
  1. Secure transferFiles exchanged over SSH with an approved endpoint
  2. Dataset validationFile structure, reporting period and agreed control totals
  3. Uplyst business contextRecords linked to customers, suppliers and transactions

Connect partner files to Uplyst

SFTP transfers files over an encrypted SSH connection. It remains useful for banks, suppliers and older applications that exchange scheduled files rather than publish APIs or events.

Uplyst connects these deliveries with its intelligence layer, mapping approved file data to accounts, transactions, customers and other business entities. File format, delivery schedule and reporting period define how the exchange relates to the business process.

SSH authentication and server identity

SFTP clients such as OpenSSH support public-key authentication and verification of the server's host key. A dedicated account can limit access to the directories and operations required for the exchange.

Endpoint identity, credentials and network access are agreed with the source operator. These establish the connection used for recurring deliveries.

Recurring and corrected deliveries

A filename alone may not distinguish a new delivery from a correction or a resend. Source partner, reporting period and content references help identify which business data a file represents.

This matters when a bank reissues a statement, a supplier corrects an invoice extract or a legacy system republishes a daily report. The updated data needs to remain connected to the existing business history.

Settlement delivery example25 Sep 2026 · GBP
Source partner
Settlement bank · BANK-04
Reporting period
25 Sep 2026
Business dataset
Daily settlement
OriginalSHA-25608c1…7b42
Records842
GBP1,284,615.42

Published

ResendSHA-25608c1…7b42
Records842
GBP1,284,615.42

Duplicate · no change

CorrectionSHA-2569df2…1a06
Records843
GBP1,289,815.42

Awaiting review

Correction validation

Control totals supplied with the delivery

Record count
843 / 843Matched
Settlement amount
£1,289,815.42Matches source total

The correction is ready for review. Publishing it replaces the current business version while retaining the delivery history.

File validation and business mapping

Required fields, source identifiers and agreed totals establish whether a delivery is complete enough for its intended use. Related files can be considered together when they form one settlement, reporting period or operational dataset.

Mapping those records into Uplyst connects partner data with enterprise transactions and provides the context needed to investigate mismatches.

Reconciliation across organizations

SFTP exchanges support bank reconciliation, supplier reporting and recurring imports from legacy systems. Uplyst relates that file data to the business records held elsewhere, making differences easier to investigate.

A delivery schedule also gives meaning to missing data. Teams can distinguish a quiet connection from an expected statement or report that has not arrived.

Connect your systems
with Uplyst.

Talk with our team about the systems you use and the decisions they need to support.

Discuss an integration