Dayforce — formerly Ceridian — moves payroll, benefits, and HR data as scheduled files over SFTP, in both directions. Files.com is the managed endpoint on your side: it lands the exports, routes them to every vendor, pushes imports to Dayforce’s site, and catches the feed that silently fails.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Dayforce file exchange runs through Integration Studio: outbound integrations deliver delimited, fixed-width, and XML exports to an SFTP destination on a schedule, and inbound integrations collect CSV, XML, and JSON files from the SFTP site Dayforce hosts. The mechanics are solid — and everything around them is on you: the carrier fan-out, the PGP each vendor demands, the push that has to reach Dayforce’s site on time, and the feed that fails without a sound.
Files.com runs everything around the Dayforce exchange. Exports land and Automations route them, Remote Server connections deliver imports to Dayforce’s hosted SFTP on schedule, PGP runs as a folder setting, and monitoring turns the silent feed failure into a same-hour alert.
Exports out, imports in, carriers fanned out, and the silent failure caught — running on Files.com in production.
Dayforce Integration Studio delivers delimited, fixed-width, and XML exports to an SFTP destination on a schedule. Files.com is that destination — and an Automation routes each export to the vendor or system that consumes it the moment it lands.
Inbound Dayforce integrations collect CSV, XML, and JSON files from the Dayforce-hosted SFTP site. A Remote Server connection pushes your prepared files there on schedule — candidate imports, employee data, time files — with every push logged.
One Dayforce export becomes deliveries to every carrier and record-keeper — each vendor scoped to its own folder and credential, each file encrypted under that vendor’s key where mandated.
When the downstream system wants a different shape than Dayforce exports, TransformScript converts delimited, fixed-width, XML, and JSON in the flow — no custom middleware between payroll and the system that needs the data.
Dayforce carrier feeds are notorious for failing silently and sending bad data downstream. Delivery monitoring knows when each feed is due and alerts the moment one is late or missing — before the carrier calls.
Deliveries, pickups, pushes to Dayforce’s site, decryptions, retries — all of it lands in the audit log, so the payroll question has a timestamped answer.
Both directions covered — Dayforce delivering to you, and your imports reaching Dayforce’s hosted site.
Outbound Dayforce integrations point at a host, directory, and credential. Files.com provides all three as a service — a stable endpoint with a static IP, under your own domain.
Inbound integrations read from the SFTP site Dayforce hosts. A Remote Server connection delivers your import files there on schedule, so nothing depends on a person with an SFTP client.
Payroll and benefits files moving to carriers and vendors encrypt and decrypt as folder settings, with keys in the platform’s key manager.
Payroll, benefits, GL, and time feeds each get their own scoped service user — rotating one credential touches one feed, and the audit trail reads per-feed.
“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 HRIS and payroll teams ask most when wiring Dayforce (Ceridian) file exchange.
Receive, route, encrypt, and audit every file moving to and from Dayforce — on one platform, with no server of your own to run.
No credit card required • Free for 7 days • Live in minutes