NetSuite
NetSuite can exchange files with Files.com over SFTP. A SuiteScript integration can collect vendor files or publish exports, while payment workflows can use NetSuite's SFTP Connector SuiteApp. Files.com provides the endpoint, controls access to the exchange folders, and handles delivery to the other systems or counterparties involved.
Choose the NetSuite component around the work it owns. The N/sftp SuiteScript module supplies file-transfer operations for server scripts. The SFTP Connector SuiteApp supports scheduled payment-file exchange with bank servers and works with Electronic Bank Payments. Receiving a file into NetSuite's File Cabinet is a transfer result; a separate NetSuite process must import or act on its contents where the workflow requires that.
Files.com Connection Values
Create a dedicated machine account with SFTP enabled. Grant access to the folders used by the NetSuite integration. Collection needs listing and download access; publication needs upload access. Include move or deletion access if the selected NetSuite workflow archives or removes files after transfer.
| NetSuite connection detail | Files.com value |
|---|---|
| Host or remote URL | Your site's [subdomain].files.com hostname or configured custom domain, without a folder path. |
| Port | 22, or the supported alternative in SFTP connection settings. |
| Username | The integration's Files.com username. |
| Password or SSH key | The credential matching that user's authentication method. With SSH, add the public key to Files.com and retain the private key in NetSuite's credential storage. |
| Host key and type | The SFTP host key presented for the chosen hostname, in the format the NetSuite component requires. |
| Remote directory | The path visible to this user over SFTP. Account for any client root folder. |
The server host key identifies Files.com to NetSuite. It is not the user's public authentication key, and a fingerprint is not interchangeable with the full host key. Obtain the required format from the host-key reference and verify the value against the hostname being configured.
NetSuite manages credential storage and supported authentication options. SuiteScript uses credential tokenization for stored passwords and requires the server host key when connecting. Follow the selected component's instructions, including Oracle's outbound configuration reference for the SuiteApp. Match the Files.com account to those requirements rather than placing a password directly in script source.
Import Staging and Export Delivery
For an inbound vendor feed, let the vendor deliver to a folder it can access, then prepare the file for NetSuite in a separate pickup folder. A transformation can change a supported source layout into the layout the import expects. Keep vendor access separate from the NetSuite account so neither needs access to unrelated feeds.
For an outbound payment or business export, NetSuite uploads the prepared file to Files.com. An Automation can route it, and an SFTP Remote Server connects to a bank or vendor that supplies the receiving server. Apply GPG encryption with that recipient's public key when required. Encryption is an explicit step; an SFTP connection alone does not produce a PGP-encrypted file.
Retain the required permissions for post-transfer operations. For example, a workflow that downloads from a Files.com pickup folder and then moves the file to a processed folder needs access to both paths. Granting only Read access can allow the download but leave the overall run unsuccessful.
Transfer Results and Business Processing
Test the actual NetSuite component with a representative file. Confirm the expected path, contents, and post-transfer archive behavior on both sides. For an import, verify the NetSuite import result as well as the download. For an onward bank delivery, verify the bank's acknowledgment when it determines acceptance.
NetSuite controls the limits and scheduling of its scripts and SuiteApp. If a transfer works for small files but fails for the real workload, check that component's file-size and execution limits before changing Files.com settings.
Use SFTP Logs alongside NetSuite's execution history to distinguish a rejected connection or path from a file that transferred but failed application processing. Before repeating a payment run, determine which files were delivered and accepted so recovery does not submit the same payment twice.