ADP exchanges payroll, benefits, and HR files over SFTP: PGP-encrypted, strictly named, on windows that don’t forgive. Files.com is the managed endpoint on your side of that exchange. It encrypts under ADP’s key, hits the window, routes what comes back, and keeps the record.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
ADP’s recurring file exchange runs on flat files over SFTP: paydata batches in, reports and confirmations out, PGP key exchange up front, and an automation schedule ADP configures on their side through a Statement of Work. That setup takes weeks and assumes a stable endpoint on your side. A self-hosted server, a departing employee’s WinSCP session, or a rotating cloud IP can’t promise that.
Files.com is the permanent other end of the ADP exchange. A hostname and credential that survive every change behind them, PGP handled in the flow with managed keys, Automations that enforce ADP’s naming and windows with retries, and an audit trail that settles every did-it-arrive question with a timestamp.
Files.com carries every payroll and benefits feed a company runs the same way: in from employer clients, out to carriers and processors, and between the HR and finance systems that cannot talk to each other.
Payroll delivery, benefits feeds, and the odd corners of the ADP exchange all run on Files.com in production.
ADP tells you the PGP key, the file format, and the destination folder. An Automation encrypts each payroll file under ADP’s own key and delivers it to their folder on their schedule. The hand-driven WinSCP session retires for good.
ADP processes files inside fixed windows under strict naming rules. A misnamed file drops into an unprocessed folder instead of the payroll run. Automations enforce the name, hit the window, and retry on failure.
ADP feeds can run with the file encrypted as it moves while the unencrypted audit copy never leaves your own servers. The outbound-only Agent makes that split possible without a firewall change.
Benefits, leave-of-absence, and demographic files move on the same rails. Each feed gets its own scoped credential and folder, so the benefits vendor never sees the payroll drop and rotating one credential touches one feed.
Some ADP outputs arrive as emailed reports, and a downstream vendor wants SFTP. Inbox email addresses turn the email into a file in a folder, bridging ADP email to vendor SFTP without running a server.
Delivery, pickup, encryption, and retry all land in the audit log, so “did the payroll file reach ADP before the window closed?” is a search with a timestamp, not a support ticket to ADP.
ADP’s setup process asks a lot of your endpoint before the first feed goes live.
Recurring transfers run through ADP’s Automatic Export Service, set up via a Statement of Work naming your ADP Workforce Now Client ID and security contact: a weeks-long process you only want to do once. Files.com gives ADP a hostname that never changes, no matter what you rebuild behind it.
Files going to ADP encrypt under ADP’s public key, and files coming back decrypt under yours. Both are folder settings, with every key in the Files.com GPG Key Manager instead of on someone’s laptop. ADP’s Automatic Export Service authenticates with the SSH key ADP provides.
Paydata moves as header-based CSV and tab-separated files, named to ADP’s convention. Automations rename and validate before delivery, so the file that arrives is the file the run accepts.
Payroll, benefits, HR, and leave feeds each get their own service user scoped to its own folder: least privilege by construction, and an audit trail that reads per-feed.
Vendor-owned FTP servers and the manufacturer’s in-house ERP could keep working as they always had while Files.com reconciled the exchange between them.
Read The Story
Files.com applied ADP’s encryption key and automated SFTP delivery, unblocking the payroll migration without changes to the operator’s payroll systems or new in-house encryption tooling.
Read The Story
Files.com automated critical exchanges with banks, agencies, and internal teams while the provider kept most data in the Azure storage its systems already used.
Read The Story
Outbound-only Files.com Agents connect the agency’s on-premises systems to scheduled PGP delivery while audit copies remain on servers the agency controls.
Read The Story
“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 payroll and HRIS teams ask most when setting up ADP file feeds.
Yes. SFTP flat-file exchange is ADP’s standard mechanism for recurring payroll and HR feeds, moving header-based CSV or tab-separated files as paydata batches. Files.com is the managed endpoint those transfers run against: encryption under ADP’s key, naming, scheduling, and the delivery record all handled in the flow.
PGP is optional with ADP but standard practice for payroll data. You generate a key pair and share the public key with ADP; on Files.com the private key lives in the GPG Key Manager and files decrypt automatically on arrival. Outbound files to ADP encrypt under ADP’s key the same way: as a folder setting, not a desktop tool.
A file that misses ADP’s window or arrives misnamed lands in an unprocessed folder instead of the payroll run. Automations enforce ADP’s naming and deliver on schedule with automatic retries, and delivery monitoring alerts when an expected feed hasn’t moved, before payroll notices.
Yes. The Files.com outbound-only Agent lets files encrypt as they move while the plaintext audit copy stays on your own servers, with no inbound firewall rule. Where the data requires it, the HIPAA business associate agreement included with Files.com Enterprise covers the platform.
Yes. Files.com replaces ADP-hosted SFTP as the endpoint your integrations point at, and teams make that move regularly. Owning the endpoint instead of borrowing ADP’s means connections move over one at a time rather than in a flag-day cutover, and the next payroll-vendor change becomes a configuration update, not a rebuild of every connection.
ADP’s Automatic Export Service runs recurring transfers from ADP’s side. It is configured through a Statement of Work naming your Workforce Now Client ID and a security contact, and typically goes live in three to four weeks. That timeline is why the endpoint you hand ADP needs to be one that never changes.
ADP expects header-based CSV and tab-separated paydata files, named to ADP’s conventions. Automations rename and validate each file before delivery, so what arrives is what the payroll run accepts instead of what lands in an unprocessed folder.
Yes. Files.com Automations split, rename, and route each ADP output to benefits carriers, record-keepers, and accounting folders, encrypting per recipient where a vendor mandates PGP. Adding a vendor is a folder and a routing rule.
Yes. Every delivery, pickup, encryption, and retry lands in the Files.com audit log with a timestamp, so you answer the payroll team from a search result instead of waiting on a ticket with ADP.
Receive, encrypt, route, and audit every file moving to and from ADP on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes
Payroll, enrollment, and eligibility files between HR systems, carriers, and processors, encrypted and on schedule.
Encrypt and decrypt files automatically as they move, with managed keys.
Schedule copies, moves, syncs, and imports down to the off-peak hour.