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. 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.
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.
Exports out, imports in, carriers fanned out, and the silent failure caught: all 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. Every push is 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, XML, and JSON in the flow, with no custom middleware between payroll and the system that needs the data.
A carrier feed that quietly stops is a benefits incident nobody has noticed yet. Delivery monitoring knows when each feed is due and alerts when the window closes without a file, 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.
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 export after it is the same three fields, and the import push is one Remote Server connection.
“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.
Yes. SFTP is Dayforce’s standard file-exchange mechanism in both directions. Integration Studio delivers outbound exports (delimited, fixed-width, or XML) to an SFTP destination on a schedule, and inbound integrations collect CSV, XML, and JSON files from the Dayforce-hosted SFTP site. Files.com serves both sides: the destination for exports, and the automated push to Dayforce’s site for imports.
Yes. Ceridian renamed itself Dayforce, after its flagship HCM platform. Integrations, documentation, and vendor setups you have under the Ceridian name run the same Dayforce file exchange: nothing about the SFTP mechanics changed with the name.
Dayforce exports once; Files.com Automations split, rename, and route the file to each carrier and record-keeper folder, encrypting per recipient where the vendor mandates PGP. Adding a carrier is a folder and a routing rule, not another integration project.
Files.com delivery monitoring catches the Dayforce feed that quietly stops and sends nothing downstream. It defines when each feed is expected and alerts the hour one goes missing, instead of the week the carrier notices.
Yes. Files.com reshapes Dayforce exports with TransformScript, which converts delimited, XML, and JSON in the flow. The file arrives in whatever shape the downstream system imports, with no middleware or custom code.
Dayforce Integration Studio exports delimited, fixed-width, and XML files, delivered to an SFTP destination on a schedule you define. Files.com receives whichever shape the integration produces and routes it onward the moment it lands.
Import files reach Dayforce through the SFTP site Dayforce hosts, where inbound integrations collect CSV, XML, and JSON files. A Remote Server connection pushes your prepared files there on schedule, so no import depends on a person with an SFTP client.
An SFTP destination for Dayforce needs a host, a directory, and a credential, held stable because the integration configuration points at them. Files.com provides all three as a service, with a static IP for allow-listing and your own domain on the endpoint.
Yes. Payroll and benefits files moving to carriers and vendors encrypt and decrypt as folder settings on Files.com, with each recipient’s key in the platform’s key manager rather than on a desktop.
Yes. Every delivery from Integration Studio, every push to Dayforce’s hosted SFTP, and every vendor pickup lands in the Files.com audit log with a timestamp, so payroll questions get answers with evidence attached.
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
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.