Business Applications

Payroll, finance, and operational systems exchange files with processors, banks, vendors, and the other applications a business runs. Files.com provides a shared exchange point for those files. An application can deliver an export into Files.com, collect an import from it, or leave files on its own SFTP server for Files.com to transfer. The application continues to generate and interpret the business data.

This separates the application's file interface from each recipient's connection requirements. A payroll export can arrive through one account, be encrypted for a processor, and be delivered to that processor's server. Changing the processor need not change how the payroll system delivers its original export.

Connection Direction

When the application connects to Files.com, give it a dedicated machine account, enable SFTP access, and grant folder permissions for its work. A sender needs upload access; a collector needs listing and download access. Add deletion or move permissions only when the application's workflow uses those operations.

When Files.com connects to an application or vendor's server, configure an SFTP Remote Server. That connection uses the remote operator's account and credentials. A Sync transfers files between the remote location and another folder; a Mount exposes the remote working files through Files.com.

These directions use different credentials. A Files.com user represents a client signing in to your site. A Remote Server credential represents Files.com signing in to another server.

File Preparation and Acceptance

Agree on the file layout, filename, delivery window, and completion signal with the application owner. A file can transfer successfully and still fail its application's import. Use Transformations where the exchange needs a different layout, and GPG encryption or decryption where a recipient requires encrypted files.

Keep files awaiting processing separate from files ready for collection. The processing order determines when folder actions occur. If uploads to a mount are buffered, the client can finish its upload before onward delivery finishes.

Folder-based decryption can leave an unchanged file when decryption fails. For a workflow that must route only decrypted output, an Automations v2 Decrypt With GPG node passes successfully decrypted files to the next node. Configure its error handling separately from the delivery path.

Treat the application's receipt or processing result as part of the workflow when it determines whether work can advance. Files.com records the transfer; the application supplies the outcome of its own processing. Delivery Verification & Failure Recovery explains how to recover a partially completed exchange without repeating successful business actions.