Dayforce

Dayforce, formerly Ceridian, can exchange payroll, benefits, and HR files with Files.com through SFTP. Files.com receives exports for delivery to carriers, processors, or other systems and stages prepared files for Dayforce imports. Dayforce owns the employee data, integration mapping, and processing of those imports.

The direction matters. An outbound Dayforce integration can connect to Files.com as its destination. An inbound Integration Studio file integration retrieves files from Dayforce's own SFTP site, so Files.com delivers the prepared input to that site.

Exports to Files.com

For an Integration Studio export, select Transmit to SFTP Server and configure Files.com as the destination. Dayforce Link and Dayforce-hosted SFTP are other transmission choices with different destinations; select the method that matches the agreed exchange. Dayforce's transmission configuration describes those choices.

Create a dedicated Files.com machine account, enable SFTP, and give it upload access to the export's intake folder. Use your Files.com hostname or custom domain as the SFTP host, port 22, and the integration account's username. Enter the host without https://.

For SSH authentication, Dayforce requires a private key without a passphrase. Hold the private key in Dayforce and register its public key on the Files.com user. The password field supplies an account password when using combined authentication; it does not unlock an encrypted private key. Follow the account's SFTP authentication requirements.

Dayforce's Folder setting is relative to the login's landing directory. Check it against the Files.com account's root and home folder settings, and confirm the path with a test export. Use a filename that lets the receiving system distinguish each scheduled delivery.

Imports Through Dayforce SFTP

Integration Studio's Build My Own inbound file connector collects CSV, XML, or JSON input from Import/IntegrationStudio on Dayforce SFTP. It applies its mapping and produces the supported Dayforce import. Other import interfaces have their own requirements; obtain the correct directory and layout from the Dayforce integration owner.

Configure an SFTP Remote Server in Files.com with the Dayforce-provided hostname and account. Register the connection's public SSH key with Dayforce if that account uses key authentication, and verify its server host key. These credentials represent Files.com connecting to Dayforce, rather than Dayforce signing in to your Files.com site.

Stage the completed input in a dedicated Files.com folder and use a Sync or Automation to deliver it to the required Dayforce directory. Keep files awaiting preparation outside the delivery selection. A successful upload to Dayforce establishes delivery; the Dayforce integration and import results establish acceptance.

Carrier Delivery and Payroll Results

Keep the Dayforce export separate from each recipient's delivery copy. An export may need different names, layouts, or encryption for a benefits carrier and a payroll processor. Files.com Transformations and GPG processing can prepare those copies. Use the recipient's public PGP key for onward encryption, independently of the SSH key that authenticates the connection.

Test a representative file through Dayforce and the receiving system before enabling its recurring schedule. Check the Dayforce Integration Log, Files.com SFTP Logs, and any onward transfer result. A carrier's acknowledgment can be a later milestone than the Dayforce export.

Place an Expectation at the milestone that has a deadline, such as receipt of the Dayforce export or readiness of a carrier's delivery. This identifies a missing feed even when no failed transfer or import was recorded.