ADP

Files.com can move payroll inputs, HR exports, and reports between an ADP file interface and the systems or vendors that need them. It can deliver to an ADP-provided SFTP server or provide a receiving endpoint for an ADP export. This gives the IT owner one place to manage file delivery, encryption, and transfer records while ADP owns payroll processing and the file interface enabled for the account.

ADP products and integration services have different import layouts, activation requirements, and transfer arrangements. Establish the specific service with the ADP administrator before configuring the connection. For example, Automated Paydata Integration for ADP Workforce Now accepts supported CSV or tab-separated hours-and-earnings files over SFTP and requires the Paydata import feature and a transfer schedule. That capability does not make every ADP account an SFTP import endpoint.

Deliveries to an ADP Server

When ADP supplies the receiving server, configure an SFTP Remote Server using the host, port, username, and authentication method ADP provides. Verify the server host key with ADP. If ADP requires source-address allowlisting, supply every outbound address for the connection route.

Prepare the final file in a Files.com outbound folder, then deliver it through a Sync or an Automation using the remote location. Match ADP's destination directory and filename convention exactly. A successful upload to the server does not establish that the file was selected for the intended pay period or accepted as a payroll batch.

Keep source preparation and submission separate. The system calculating hours or earnings produces the payroll data; a transformation can adapt a supported file layout. Files.com does not calculate payroll or supply an ADP import mapping automatically.

ADP Exports to Files.com

When the ADP service sends files to a customer-provided endpoint, create a dedicated machine account with SFTP enabled and upload permission to an intake folder. Supply its username, your Files.com hostname, the port, and the directory visible to that account. Register the sender's SSH public key when the agreed connection uses key authentication.

Use the Files.com SFTP connection settings for hostname, host-key, and network details. If a client root folder presents the intake folder as /, the ADP export should use the path inside that root.

The ADP administrator or representative configures the export service and schedule. Files.com supplies its receiving side; creating a Files.com account does not activate an ADP export. For a service where files remain on ADP-hosted SFTP instead, use a Remote Server and scheduled collection rather than asking ADP to connect to Files.com.

Per-Recipient Encryption

Agree on PGP requirements independently of SFTP authentication. An SSH key signs in to a server; a PGP key protects a file's contents.

For files delivered to ADP, import ADP's public PGP key into the GPG Key Manager and apply encryption before delivery. For an encrypted ADP export, provide ADP with the public key whose matching private key is stored in Files.com, then configure decryption on the receiving folder.

Use separate ready-for-delivery folders for counterparties that require different layouts or encryption keys. Route from the completed preparation result so the transfer does not collect a file while it is still being transformed or encrypted.

Payroll Cutoffs and Acknowledgments

Test the agreed filename and layout against ADP's test process before submitting a live payroll file. Confirm the transfer record and ADP's import or batch result. Where ADP returns acknowledgment or error files, collect those through the configured file interface and make them available to the person responsible for resolving the run.

An Expectation can detect a missing source export or a file that is not ready by the required cutoff. It does not certify the payroll calculations or replace ADP's processing result. Use the relevant Sync or outbound-connection logs to investigate delivery, and ADP's records to establish acceptance before retrying a submission.