Acumatica’s import and export scenarios run on schedules and expect the right file to be in the right place. Files.com is the endpoint your counterparties deliver to and the staging layer your scenarios read from. Counterparties send over SFTP or whatever they run, files reshape to each import’s mapping, and exports flow back out governed.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Acumatica handles the mapping side of file integration well: import scenarios turn a CSV into records, export scenarios turn records into files, and the Automation Scheduler runs both on cadence. What the scenarios assume is that the right file is sitting in the right place at the right time. That assumption is carried by an FTP server and a set of scripts nobody wants to own.
Files.com makes the scenarios’ assumption true, as a service. Counterparties deliver into scoped folders over their own protocols, TransformScript matches each file to the scenario’s mapping, Automations deliver the exports onward, and monitoring alerts when an expected feed runs late.
Imports staged on schedule, exports delivered onward, and counterparties on their own terms.
Acumatica import scenarios run on automation schedules and process whatever file is waiting. Files.com is where those files wait: arrived from counterparties, validated, reshaped to the scenario’s layout, and staged before the schedule fires.
Export scenarios produce the files; delivery is the other half. Automations pick each export up, rename it per recipient, encrypt where mandated, and deliver over whatever protocol the counterparty runs.
Banks, 3PLs, and EDI partners each connect their own way: SFTP, FTPS, plain FTP, AS2 where retail mandates it, or a browser. Each gets its own scoped folder and credential, and the ERP side never changes.
Orders and confirmations arrive in partner formats. TransformScript converts CSV, XML, and JSON into the shapes the import scenarios map, so a partner’s format quirk is fixed once, in configuration.
Bank and payroll files around the ERP commonly mandate encryption. PGP runs as folder settings: decrypted on arrival, encrypted on delivery, keys in the platform’s key manager.
A scheduled import over an empty folder succeeds — at importing nothing. Delivery monitoring knows when each inbound feed is due and alerts when one is late, before the scenario runs on silence.
What the file layer under scheduled scenarios has to get right.
A permanent hostname with scoped credentials per counterparty, static IPs for the allowlists, and every protocol a partner might run, so the exchange side is settled before the first scenario is mapped.
Import scenarios fire on the Automation Scheduler’s cadence. Automations land validated, reshaped files in the pickup folder ahead of each run, and archive the originals under retention policies.
Acumatica’s REST and OData APIs carry record-level, real-time integration. The file layer carries the counterparty exchange and bulk loads. Files.com webhooks and its REST API join the two.
Banks, 3PLs, EDI partners, and internal systems each get their own folder and credential: one rotation touches one relationship, and the audit trail reads per-party.
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What ERP and finance teams ask most when wiring file exchange around Acumatica.
Acumatica exchanges files through import and export scenarios: mapped, file-based loads that run on automation schedules. REST and OData APIs carry record-level integration alongside them. Files.com is the managed layer that stages files for the import scenarios and delivers what the export scenarios produce.
Yes. That’s the standard pattern: the Automation Scheduler runs the scenario at intervals, and Files.com makes sure a validated, correctly shaped file is waiting when the schedule fires. Monitoring alerts when the upstream feed that stages it runs late.
Partners send to Files.com however they can: SFTP, FTPS, FTP, AS2, the S3-compatible API, or a browser upload. Each counterparty delivers into its own scoped folder, and every arrival is logged and can fire an automation.
Yes. TransformScript converts CSV, XML, and JSON and remaps columns in the flow, so the scenario’s mapping stays stable no matter what shape the sender exports.
Yes. Files.com Automations collect each export, rename per recipient, encrypt where mandated, and deliver on each counterparty’s protocol and schedule, with every hand-off logged.
Yes. Partner documents arrive at Files.com over the protocol the partner mandates, convert into the shapes your import scenarios map, and route onward. AS2 with signed MDN receipts is built in for the partners that require it.
Acumatica’s REST and OData APIs carry the record-level, real-time work. The file layer carries the counterparty exchange and the bulk loads. Files.com webhooks can trigger API-side processing the moment a file lands, joining the two cleanly.
Files.com delivery monitoring defines when each feed is due and alerts when one runs late, so a scheduled scenario never quietly processes nothing.
Files.com replaces the FTP server and scripts standing between the ERP and its counterparties, plus the manual uploads, the desktop decryption step, and the discovery that a scheduled import has been processing nothing for a week.
Imports staged before the schedule fires, exports delivered after it does, and an alert whenever a feed runs late.
No credit card required • Free for 7 days • Live in minutes