UKG

UKG file interfaces can connect HR, payroll, timekeeping, and document workflows with the other systems a business runs. Files.com can receive an export into a controlled folder, collect files from a UKG-hosted SFTP server, or stage files for delivery back. The UKG application determines the file layout and the business processing; Files.com handles the exchange around it.

Identify the UKG product and enabled integration before choosing a connection. A UKG Pro report export, a workforce-management interface, and UKG HR Service Delivery do not necessarily share the same host, port, credential rules, or processing folders. Use the connection details supplied for that particular feed.

Receiving Exports or Collecting Them

For a UKG integration that delivers to your endpoint, create a dedicated machine account with SFTP enabled and upload access to the receiving folder. Give the integration your Files.com hostname, port, username, and the path visible to that user. Register its SSH public key when it uses key authentication. The SFTP connection settings explain host keys, network access, and account requirements.

For a feed held on UKG-hosted SFTP, configure an SFTP Remote Server. UKG supplies the endpoint and account; Files.com uses that credential to connect outward. Give UKG the source addresses of the selected connection route if it requires allowlisting.

A scheduled Sync can collect completed exports into a Files.com intake folder. Select a schedule that follows the UKG export's availability rather than assuming the file exists at the start of the business day. Keep export production and collection as separate stages when defining the expected delivery window.

UKG HR Service Delivery

UKG's HR Service Delivery exchange protocol describes a client-initiated SFTP connection for both sending and receiving. For this arrangement, Files.com connects as the client through a Remote Server. Use the endpoint, port, SSH key, and directories assigned for the correct hosting location and environment. The Files.com inbound port is not the port to assume for this remote service.

The protocol uses input and output directories and temporary filenames ending in .filepart. Exclude *.filepart from collection so a Sync does not retrieve an export UKG is still writing. Files supplied to HR Service Delivery must follow its upload-completion and naming rules, including publishing the final name only after transfer completes. A flow that uploads directly under the final name does not satisfy that temporary-name requirement.

Keep test and production connection details separate. A valid SSH credential does not identify the intended business environment on its own.

Decryption and Downstream Use

For encrypted exports, use the private key that matches the public key provided to the sender. If a Sync collects the original files for retention, collect them into an unchanged intake folder and decrypt in a separate workflow stage. An Automations v2 Decrypt With GPG node retains that encrypted source and passes the decrypted output onward. For encrypted deliveries into UKG, use the recipient's public key. These file-encryption keys are separate from the SSH credential used by the Remote Server.

Let downstream systems collect from a prepared folder after decryption and any required transformation finish. For example, a roster delivered for an internal application can retain its source export separately from the application's ready-to-import copy. That separation allows the source to be reviewed without asking the application to process encrypted or unfinished input.

Remote retention and cleanup rules belong to the specific UKG service. Choose the Files.com collection and retention policy around the period your team needs for recovery. Do not rely on a vendor's transfer folder as the only copy of a required record.

Collection and Import Results

Test with a completed export and check its name, reporting period, and contents at the destination. If delivery includes an import into UKG, also review the application's processing result or returned report. Collection of a response file and acceptance of its contents are separate outcomes.

Use Sync logs to distinguish a connection failure, a pattern that excluded the file, and a file already present at the destination. An Expectation on the receiving folder can detect a missed feed; a successful collection run alone does not establish that UKG produced the expected period's export.