How Files.com Fits With Acumatica

Acumatica moves data through import and export scenarios that run as files on a recurring schedule over SFTP — transactions and master data coming in, reports and feeds going back out to partners and downstream systems. The part that breaks is rarely the scenario; it is collecting files from partners on time, each in its own format, and shaping them into what the import scenario expects.

Files.com is the SFTP layer around that exchange. Partners and systems send to your Files.com site over SFTP, FTPS, or HTTPS; an Automation validates each file, converts it into the format the import scenario expects, and stages it where Acumatica reads it on schedule. The same flow runs in reverse for what the export scenario writes out — collected, encrypted, and delivered to each partner with a full record of what went where.

What You Would Use

Be The SFTP Endpoint For Scenarios

Give Acumatica a stable, monitored SFTP endpoint with a static IP to allowlist, where import scenarios read files and export scenarios write them — no server of your own to patch or expose.

See File Transfer

Convert Before Import

Convert inbound CSV, JSON, XML, and EDI into the format an Acumatica import scenario expects, and pull values out of each file to route it, before Acumatica reads it.

See Transform & Extract

Stage And Deliver On Schedule

An Automation drops each file where your scheduled Acumatica import scenario reads it, and collects what the export scenario writes to deliver back to each partner — on a schedule or the moment a file lands.

See Automations