How Files.com Fits With NetSuite

NetSuite exchanges data with partners as flat files. SuiteScript and scheduled jobs read and write the file cabinet, and B2B and EDI feeds move over SFTP — purchase orders, invoices, and ship notices arriving from partners, exports going back the other way. The work that breaks is rarely the import script; it is collecting files from partners who each send a different format on a different schedule.

Files.com is the SFTP front door for that exchange. Partners send to your Files.com site over SFTP, FTPS, or HTTPS; an Automation validates each file, converts X12 or EDIFACT EDI into the CSV or JSON shape NetSuite expects, and stages it where your scheduled import reads it. The same flow runs in reverse for the files NetSuite exports — picked up, encrypted, and delivered to each partner with a full record of what went where.

What You Would Use

Receive Partner Files Over SFTP

Trading partners and upstream systems send to one Files.com endpoint over SFTP, FTPS, FTP, or HTTPS, with per-partner credentials and an audit record on every transfer.

See File Transfer

Convert EDI To CSV And JSON

Transform inbound X12 or EDIFACT EDI into the flat-file shape NetSuite imports, and pull values out of each file to route it, before NetSuite ever reads it.

See Transform & Extract

Stage And Deliver On Schedule

An Automation drops converted files where your scheduled NetSuite import expects them, and collects NetSuite exports to deliver back to each partner — on a schedule or the moment a file lands.

See Automations