2. Actuals SFTP server

📂
Actuals SFTP is an Actuals-hosted SFTP server. You (or your automation) push files to Actuals. This is different from External SFTP, where Actuals pulls from a server you or a vendor own.
A common pattern is to export data on a schedule and upload the files to Actuals SFTP.

Credentials

Ask your implementation consultant for access. Typical connection details:
  • Host: sftp.actuals.io
  • Username / password: provided by Actuals
  • Port: 22

File format and naming

  • Prefer .csv (ask your consultant before using other formats).
  • Clear names help operations, for example: CustomBackend_orders_2025-01-01.csv
    • Application / system name
    • Dataset / table name
    • Period as YYYY-MM-DD

Large files

For regular large CSVs (rough guideline: ~250 MB uncompressed), prefer compressed formats Actuals can unpack:
  • .csv.gz, .csv.zst / .csv.zstd, .csv.bz2, .csv.deflate, .csv.raw_deflate
Compression often shrinks files by about 10×.

Folder structure

Create a folder per dataset. Suggested pattern: [Source application] - [Dataset].
Example:
  • Backend - OrdersBackend_orders_2025-01-01.csv
  • Backend - PaymentsBackend_payments_2025-01-01.csv

Manual upload (FileZilla example)

  1. Install an SFTP client (for example FileZilla) per your IT policy.
  1. QuickConnect with host sftp.actuals.io, your username/password, port 22.
  1. Drag files from Local site to Remote site.
  1. Confirm under Successful transfers and that files appear remotely.

In the new app

After files land, watch ingestion under Import › Files and map them via Transformation › Setup › Mapping. Credentials for SFTP-based sources still sit under Import › Setup › Credentials when Actuals stores them for connectors; for Actuals-hosted SFTP your team holds the outbound credentials Actuals issued.

Related

      1. External SFTP server — when Actuals must pull from your host
  • Import › Files — ingestion status