Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Integration

SFTP ERP Integration: File Exchange with Banks, Partners and Plants

For finance and IT teams that swap files with banks, distributors and plants on a schedule, and want those files to come from and go into the right records.

A dispatch manager placing a document pouch into a lockbox in a castings workshop

An SFTP ERP integration is often the only door a bank, a large customer or a logistics partner offers. They publish a server, you drop a payment file or pick up a statement, and the whole thing runs on a timetable.

Apragya's file connector handles FTP and FTPS, which is FTP over TLS. It uploads a file, downloads a file, lists a folder with sizes, and deletes a file. Many setups called SFTP are in fact FTPS, so check with your partner first.

SSH-based SFTP is a different protocol and is not in the ready-made connector yet. This page shows what works today and how to plan around that gap.

What manual file exchange costs

Missed cut-offs

A payment file uploaded after the bank's window waits a day.

Wrong versions

Someone uploads yesterday's file from their desktop.

Unread replies

Acknowledgement files sit on the server unnoticed.

Shared passwords

Server credentials pass between people by chat.

An example: a Rajkot castings exporter

Take an illustrative exporter whose largest overseas customer publishes an FTPS server for purchase orders and expects dispatch files back each evening.

A day of file exchange, without a desktop

  1. Morning listing

    The inbound folder is listed on schedule.

  2. Order file downloaded

    New purchase orders are fetched.

  3. Sales orders created

    Mapped into orders for review.

  4. Evening dispatch file

    Built from the day's shipments.

  5. Uploaded and tidied

    Sent, and processed files removed.

Orders are reviewed as records, not opened as attachments.

The sales desk stopped downloading files each morning, and the customer received dispatch files on time every evening. When a file failed to upload, the error was recorded with its reason and the next run picked it up.

Two lockboxes on a shelf, one open with a pouch, one tied with a ribbon
Orders collected in the morning and dispatch files delivered every evening.

How FTPS file transfer from the ERP works

Step 1 of 5

Add the connection

Host, port, user and password, stored encrypted.

  1. Add the connection: Host, port, user and password, stored encrypted.
  2. Choose TLS: Use FTPS where the partner supports it.
  3. List folders: Check what is waiting before fetching.
  4. Get and put files: Download inbound files and upload outbound ones.
  5. Schedule it: Run transfers at the times your partner expects.

Automated file transfer in India: FTPS today, SFTP planning

If your partner offers FTPS, the connector covers you now. If they require SSH-based SFTP, talk to them about FTPS or an HTTPS API, which the custom adapter can call, or keep a small transfer job on your side that drops files into a location Apragya can read, such as an S3 bucket.

Partner protocols and Apragya

FeaturePartner serverApragya file connector
Plain FTPStill common inside plantsSupported
FTPS (FTP over TLS)Common with banks and large buyersSupported
SFTP over SSHCommon tooNot in the ready-made connector yet
HTTPS APIOffered by some partnersCustom adapter
CredentialsIssued per partnerStored encrypted

Checked against public information on 16 September 2026.

What makes scheduled transfers dependable

Runs on time

Schedules match the partner's cut-offs.

Named errors

Auth failures and timeouts are recorded clearly.

Reach inside plants

A Tenant Runner reaches servers on your network.

Review before posting

Imported orders can wait for a person.

No shared passwords

Credentials live in the connection, not in chat.

Into real records

Files become orders, shipments or payments.

See sales orders, bank statement import and the SharePoint integration for document libraries.

Getting started

  1. Ask the partner which protocol their server uses.
  2. Agree folders, file names and cut-off times.
  3. Add the connection and list the inbound folder.
  4. Map one file type to records and test it.
  5. Schedule the transfer and watch the first week.

Confirming the protocol first avoids a week of failed logins.

What it costs to start

Free
Up to 3 users
CRM, HR and Vendor Onboarding
INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus a choice of apps
INR 7,999
Pro, a month
Up to 25 users and every enterprise app

SFTP ERP integration, answered

Does Apragya support SSH-based SFTP?
No. SSH-based SFTP is not built yet; the file connector supports FTP and FTPS. Ask the partner for FTPS, exchange files through an S3 bucket, or contact Apragya to discuss your case.
How do we tell FTPS from SFTP?
Ask the partner. FTPS uses FTP with TLS; SFTP runs over SSH, usually with a key or password on the SSH port.
Can it reach a server inside our plant?
Yes, through a Tenant Runner that connects out from your network.
What happens if a transfer fails?
The error is recorded against the connection with its reason, such as a refused login or a timeout, and a plain-English explanation helps an admin fix it before the next scheduled run.
Can it delete files after processing?
Yes. The connector can delete a remote file once it has been handled.
What does it cost to start?
The free plan covers up to 3 users with CRM, HR and Vendor Onboarding and 1,000 AI Credits a month. Starter is INR 3,999 a month for up to 10 users, with CRM and HR plus a choice of apps such as Sales and POS, Inventory, Payroll, Purchase and Payables, Support and Manufacturing. Pro is INR 7,999 a month for up to 25 users with every enterprise app, including Finance and Accounting, plus 5,000 AI Credits, single sign-on and audit logs.

Put partner files on a timetable

Connect your FTPS partners and let files turn into records.