Payroll Files To The Provider
Workday delivers the payroll file; an Automation encrypts it under the provider’s own PGP key and hands it to ADP, Paychex, or the bank on their schedule. That step used to be a person with a desktop PGP tool.
Workday moves data as files over SFTP: payroll to the provider, benefits to the carriers, new hires to the directory. The other end is yours to provide. Files.com is that endpoint, run as a service. It receives, decrypts, routes, verifies, and audits every feed, and stages the inbound ones for Workday to pick up.
No credit card required · 7-day free trial · Live in minutes



Real companies. Real file flows. Real results.






















Every Workday integration that moves a file needs an SFTP destination. Enterprise Interface Builder (EIB) integrations deliver custom-report output on a schedule; Core Connectors push payroll, benefits, and worker data in vendor formats; Workday Studio assemblies deliver whatever the integration team builds; report-as-a-service feeds write extracts the rest of the business consumes. Workday points all of them at a host, a directory, and a credential. Everything that happens after delivery is somebody else’s problem.
Files.com is the somebody else. The file lands and the platform takes over: PGP decryption as a folder setting, Automations that split and route each feed to the right vendor, monitoring that notices the feed that never came, and an audit trail that turns every payroll-delivery question into a lookup. No server of your own, no scripts, no person babysitting the Monday run.
Payroll, benefits, identity, and vendor intake: the feeds every Workday shop operates, running on Files.com in production.
Workday delivers the payroll file; an Automation encrypts it under the provider’s own PGP key and hands it to ADP, Paychex, or the bank on their schedule. That step used to be a person with a desktop PGP tool.
One Workday delivery becomes many vendor deliveries: an Automation renames, splits, and routes each feed to the right carrier or record-keeper folder, each partner scoped to its own walled space, with retries instead of pages.
EIB runs inbound too. Vendor eligibility files, bank acknowledgements, and demographic data land in Files.com, where they’re decrypted, validated, and staged in the folder Workday retrieves from on its next scheduled run.
New-hire and termination feeds move from Workday to identity and downstream systems through one governed exchange point. The X.509 certificate authentication some Workday integrations require is handled as configuration.
A payroll integration that silently didn’t run is a payroll incident. Delivery monitoring knows when the Workday file was supposed to land and alerts when it doesn’t. The payroll file-watching scripts retire for good.
Every delivery, pickup, decryption, and permission change lands in a tamper-proof audit log, so the answer to “did the 401(k) file go out on the 3rd?” is a search, not an investigation.
Litera replaced the person who ferried HR files between Workday and Active Directory with a Files.com exchange point both systems authenticate to, X.509 certificate included, while integrating the employees of 24 acquisitions.
Your Workday administrator asks for the same things before every feed goes live. Files.com answers each one.
Workday integrations point at a hostname that never changes and an IP your network team can allowlist, under your own domain if you want it.
Password, SSH key, or X.509 certificate authentication, including the key formats Workday’s Create x509 Private Key Pair task generates.
Each EIB or Core Connector gets its own credential, scoped to its own folder, so one integration can never read another’s files. Rotating one key touches one feed.
Workday encrypts with the PGP public key you load into the tenant; Files.com holds the private key in its key manager and decrypts on arrival. Outbound, the reverse.
The evaluation is not a project. The whole loop validates inside the 7-day free trial:
That’s the whole cutover, rehearsed on one feed. Every other Workday feed after it is the same three fields.
Manufacturing
Workday could not absorb the archive, so Files.com received, organized, and preserved every record under BlueScope’s governance.
Read story →

Transportation & Logistics
The migration preserved partner workflows with a hostname-and-credential change while Files.com made encryption, retention, identity, and auditing enforceable.
Read story →
Software & Technology
Replacing the on-premises endpoint meant moving a live payroll workflow to unattended service accounts while preserving its audit trail.
Read story →
Banking & Finance
Moving the bank’s sensitive production transfers took a flow-by-flow lift-and-shift that preserved its encryption, service accounts, and surrounding integrations.
Read 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 Workday administrators ask most when setting up SFTP delivery.
Receive, transform, route, and audit every file moving to and from Workday, with no server of your own to run. The first delivery can validate today.
No credit card required • Free for 7 days • Live in minutes