Exchange protocol via SFTP file transfer

This section describes the data exchanges between UKG HR Service Delivery and the IS client in terms of protocols, procedures, and naming conventions.

All CSV files transmitted as part of data synchronization must respect this protocol (see: Synchronizing data).

Exchange protocol

The protocol used for file exchanges is SFTP (SSH File Transfer Protocol).
This service uses the SSH-2 protocol version.

Sessions must be established from the client to UKG HR Service Delivery, whether it involves sending or receiving data.
The company has a single account used for identification.

UKG HR Service Delivery verifies that the login request originates from the company using an identification/authentication mechanism, which is performed using an encryption key provided by the company.

SFTP server address

UKG HR Service Delivery provides different SFTP servers for data transfer.

This section details the information required for SFTP data transfer from customer IS to UKG HR Service Delivery (ingress) and from UKG HR Service Delivery to customer IS (egress).

European Platform

For clients hosted on the UKG HR Service Delivery European platform there are 2 servers:

EU Platform

Staging server

Production server

Server

sftp.staging.eu.people-doc.com

sftp-9d87a130f70b.eu.people-doc.com

Ingress IP

37.188.117.11

159.135.141.101

Port

9030

9030

ED25519 Host key

OPENSSH (download), RFC4716 (download)
Fingerprint SHA256: SHA256:BiLqJYqDM9pbF2vEa6bSxH3+chDG5Pi0k/Mbnb0bNjQ
Fingerprint MD5: MD5:36:be:db:b9:b2:8a:1f:3a:7d:38:cf:ff:21:d9:ef:2e

OPENSSH (download), RFC4716 (download)
Fingerprint SHA256: SHA256:tSms1ujVmnbGb4jv00SzpkShwTsLMWvhLll9APPdrYU
Fingerprint MD5: MD5:97:64:be:7e:9e:a9:a6:5f:4c:07:99:46:2b:34:77:d5

RSA-SHA2-512 Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:xTibRl51c1iM6ruLB3VXLbJqPd/VqgZjIlrEqQtAg98
Fingerprint MD5: MD5:3f:ae:e3:f8:20:ad:cd:de:27:79:7d:6e:aa:42:0a:53

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:LPUUHGMuAJPQALt1U6c8Um4KOVqfaXUb8x2Svh8ZsBA
Fingerprint MD5: MD5:7d:fe:ef:8e:d6:1d:7b:c2:9a:6b:d8:15:3f:f7:0c:e1

RSA-SHA2-256 Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:SpoFjSdsL/eMIABbpS/0SInudCwzbE1hJv1UXl6K8I8
Fingerprint MD5: MD5:91:4b:80:99:6a:13:98:6b:64:39:5a:a6:e7:f8:ef:56

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:BB7jo3nhZ2gqt99aTmPqKk1Zj1GSVofNjbYGqGz2A4E
Fingerprint MD5: MD5:b2:1e:8b:80:27:b2:90:1b:89:2b:e2:c7:9f:0c:99:fa

RSA Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:MkcoN64Eq5bJHVqDVq04eCnlh2AZySBBLTYoTkb28GY
Fingerprint MD5: MD5:75:4d:59:6e:6e:00:67:f2:7d:79:85:57:bf:d1:eb:2a

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:ive4HBotUcJPNCA6dF3V+qCB9ETnPqteGUbxNgnXUjE
Fingerprint MD5: MD5:bf:7b:ee:18:f5:1e:03:e0:52:2d:26:c5:9e:ee:6c:b8

PGP encryption public key

pgp-staging-eu-pub.asc (download)

pgp-production-eu-pub.asc (download)

Egress IP

162.13.159.37

159.135.141.79

Egress public key

outgoing-sftp-staging-rsa.pub (download)

outgoing-sftp-production-rsa.pub (download)

United States Platform

For clients hosted on the UKG HR Service Delivery United States platform there are 2 servers:

US Platform

Staging server

Production server

Server

sftp.staging.us.people-doc.com

sftp.us.people-doc.com

Ingress IP

166.78.156.49

173.203.147.43

Port

9030

9030

ED25519 Host key

OPENSSH (download), RFC4716 (download)
Fingerprint SHA256: SHA256:iSrWPZwXi1a18HyNpcqdbIJDxT9zaj0cLbPYz2TWiJk
Fingerprint MD5: MD5:e7:69:38:4f:13:c5:e0:16:e5:9e:5e:be:75:36:bb:56

OPENSSH (download), RFC4716 (download)
Fingerprint SHA256: SHA256:BY09Cy+E56NThd3mZt9PRV7sSfm0j09vyB17hZOOUH4
Fingerprint MD5: MD5:e5:66:d7:b8:23:1d:61:7b:b6:0a:e2:fb:9e:dd:10:5e

RSA-SHA2-512 Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:8IOYNlsO7ymI4qn144eX+qbRXq0ElhEC+QjsuU94diA
Fingerprint MD5: MD5:e3:5b:3b:8f:17:39:b7:53:19:61:a2:df:eb:c8:ec:26

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:/bNQSvrByAWmvB2R8rZ12HLgB/ykGif/Nev7Q4FbK+s
Fingerprint MD5: MD5:a7:65:fc:23:82:25:e1:1a:20:71:df:2e:ee:1e:0a:bd

RSA-SHA2-256 Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:xzozGhDNfd1hCC2b8eUv8T8zDvH3C9PRH1BG40zgAfE
Fingerprint MD5: MD5:84:d8:7a:1b:3b:b0:52:dc:d4:34:bc:e8:26:e9:cb:89

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:VgovloQv4e/aUB59sHpxKBXWlEvxdEDkkOEYKuM1EnI
Fingerprint MD5: MD5:d0:82:85:c6:67:6d:fe:ff:9d:6b:e0:0b:ab:c3:a9:b5

RSA Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:L8dk4Oe2InAnZBqEFHd0AM4J6S5bULgE0ftrIyKAg58
Fingerprint MD5: MD5:2c:da:f1:84:a7:d3:a5:35:30:33:96:4a:b2:69:9b:f5

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:e5sTobCfhnTuQAY8so3nhYGo5PH1w7wq/8I/JVioS5I
Fingerprint MD5: MD5:e5:d2:22:45:1d:14:68:5e:0c:4a:b5:df:36:37:2a:4b

PGP encryption public key

pgp-staging-us-pub.asc (download)

pgp-production-us-pub.asc (download)

Egress IP

162.209.78.123

146.20.165.237

Egress public key

outgoing-sftp-staging-rsa.pub (download)

outgoing-sftp-production-rsa.pub (download)

USG/Ultimate Platform

For clients hosted on the Ultimate Software platform there are 2 servers:

Ultimate Software Platform

Atlanta server

Toronto server

Server

sftp-a5g0wchkaeb5.hrsd.ultipro.com

sftp-h2ohy6ogo7ew.hrsd.ultipro.ca

Ingress IP

135.84.64.194

206.152.14.144

Port

9030

9030

ED25519 Host key

OPENSSH (download), RFC4716 (download)
Fingerprint SHA256: SHA256:z54xDqUHVlOI7WlFS0ythEmJAPiM+ON+mJ7+fkOudjE
Fingerprint MD5: MD5:75:35:e8:d9:20:ac:b6:ea:eb:8d:33:25:d8:4a:67:93

OPENSSH (download), RFC4716 (download)
Fingerprint SHA256: SHA256:8pZ0d5zOEklFzS0YjVKP8Gud75fLs9P1E0g/sZlbkWk
Fingerprint MD5: MD5:d9:7c:aa:27:b2:cc:b0:64:4d:45:c0:54:03:48:23:2f

RSA-SHA2-512 Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:4XV3QJ1n6e6SnRKZBMFAg4R1ZQ81b7igJWLXxVSpxdc
Fingerprint MD5: MD5:d2:5e:30:18:06:54:e9:cd:9b:c8:4f:70:24:91:de:b5

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:bRjlDOpAzMTcc/DKUlpXS0B9Fl7kQyC1ehdj6f74L1A
Fingerprint MD5: MD5:6c:23:ad:98:4a:a6:78:d7:16:a2:22:13:c5:41:2d:56

RSA-SHA2-256 Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:tFFFD35lzmBY8r5xCqopvJGh5pAbGr33qyt/r5TFMaA
Fingerprint MD5: MD5:30:3a:e0:1b:09:9c:d6:d2:17:6b:13:1c:79:12:4b:6e

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:4WXbaJHgPjbP+T8gO/d5Pfcc7HuzS6jM3cO4nbJwQ4k
Fingerprint MD5: MD5:7d:f0:7d:de:13:cc:e4:6d:fd:fe:f1:b6:b9:ca:2c:c8

RSA Host key

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:jf+5OOP3XoLg6zw7s/vamhYI9nShkbhVH2P1PrscL6E
Fingerprint MD5: MD5:a7:07:75:c5:6c:51:6c:b5:78:60:71:4f:c6:84:85:c3

OPENSSH (download), RFC4716 (download), PKCS8 (download), PEM (download)
Fingerprint SHA256: SHA256:KMxkep9GGPs4c63HZUzpi2fYMf4qzC5ZDK4Ne1pW6ew
Fingerprint MD5: MD5:c5:e9:43:a3:d9:fe:d2:99:92:eb:b8:75:ce:3e:41:5c

PGP encryption public key

pgp-production-atl-pub.asc (download)

pgp-production-tor-pub.asc (download)

SFTP account

Authorization (Firewall filtering)

To use our SFTP service, you must be able to contact our SFTP servers.

  • Request an authorization from your IT department if they are filtering outgoing connections.

    • Your IT department must allow outbound traffic through the port used by the SFTP server.

  • Communicate to UKG the public IP addresses that must be allowed.

    • Please request the list of public IP addresses from your IT department.

    • Up to 254 IP addresses can be allowed.

Network recommendations

  • It is strongly recommended to assign a unique IP address to the flow to our SFTP server.
    Please contact your IT department for more information.

Warning

UKG HR Service Delivery can ban the concerned IPs if a suspicious behavior is detected (flood, too many connections, dangerous payload, …)

Authentication (SSH key access)

Each SFTP account allows up to two authentication methods:

  • Using public SSH keys:

    • Method to use by default.

    • Minimum security requirements apply.

  • Password based: (Warning: upcoming deprecation in 2022)

    • Disabled by default.

    • Only enabled if you can’t use SSH keys.

SSH key specifications

UKG HR Service Delivery only accepts public SSH keys of the following types. Other SSH key types, sizes and formats are rejected.

Key type

Format

Min. size

Recommendation level

ed25519

OpenSSH

Recommended

rsa-sha2-512

OpenSSH

3,072 bits

Recommended

rsa-sha2-256

OpenSSH

3,072 bits

Not recommended

rsa

OpenSSH

3,072 bits

Will enter depreciation shortly, not recommended

SSH key best practices

  • Comment your SSH key

    • It is strongly recommended to assign a comment to each of your SSH keys in order to differentiate them and thus allow an easier access revocation.

  • Secure your SSH key:

    • It is strongly advised to provide a passphrase when generating your SSH key pair to ensure its security.

  • Keep your SSH key secret:

    • Never communicate your private key

    • UKG HR Service Delivery will never ask you to provide your private key: We only request your public key.

Generate SSH Key and configure tool

Warning

The ssh-keygen tool exists on the 3 main operating systems (Linux, Mac, Windows) to allow you to generate your SSH key.
The customer is free to use any tool, as long as it complies with UKG HR Service Delivery safety regulations.

Our service is based on OpenSSH 7.4 and unsecured communication algorithms are disabled.
Ensure your software is compatible with UKG HR Service Delivery version.
Here are a few compatible softwares:

  • AsyncSSH >= 1.18 (2019-08-23)

  • FileZilla >= 3.13.0 (2015-08-15)

  • J2SSH Maverick >= 1.7.14 (2019-04-23)

  • libssh >= 0.9.1 (2019-10-25)

  • OpenSSH >= 6.6 (2014-03-15)

  • Paramiko >= 2.5.0 (2019-09-06)

  • SSHJ >= 0.27.0 (2019-01-24)

  • Winscp >= 5.9.4 (2017-02-15)

SFTP Security

SFTP algorithms

Algorithms order

  • Kex algorithms: curve25519-sha256@libssh.org, curve25519-sha256, diffie-hellman-group18-sha512, diffie-hellman-group16-sha512, diffie-hellman-group14-sha256, diffie-hellman-group-exchange-sha256

  • Server host key algorithms: ssh-ed25519-cert-v01@openssh.com, ssh-rsa-cert-v01@openssh.com, ssh-ed25519, rsa-sha2-512, rsa-sha2-256,ssh-rsa

  • Encryption algorithms (ciphers): chacha20-poly1305@openssh.com, aes256-gcm@openssh.com, aes256-ctr, aes128-ctr

  • Mac algorithms: hmac-sha2-512-etm@openssh.com, hmac-sha2-256-etm@openssh.com, hmac-sha2-512, hmac-sha2-256

  • Compression algorithms: none, zlib@openssh.com

Details of the algorithms

Kex algorithms

Kex algorithms

OpenSSH 7.4

curve25519-sha256

yes

curve25519-sha256@libssh.org

yes

diffie-hellman-group-exchange-sha1

no

diffie-hellman-group-exchange-sha256

yes

diffie-hellman-group1-sha1

no

diffie-hellman-group14-sha1

no

diffie-hellman-group14-sha256

yes

diffie-hellman-group16-sha512

yes

diffie-hellman-group18-sha512

yes

ecdh-sha2-nistp256

no

ecdh-sha2-nistp384

no

ecdh-sha2-nistp521

no

Server host key algorithms

Server host key algorithms

OpenSSH 7.4

rsa-sha2-256

yes

rsa-sha2-512

yes

ssh-dss

no

ssh-ed25519

yes

ssh-rsa

yes

Encryption algorithms (ciphers)

Algorithm

OpenSSH 7.4

3des-cbc

no

aes128-cbc

no

aes128-ctr

yes

aes128-gcm@openssh.com

no

aes192-cbc

no

aes192-ctr

no

aes256-cbc

no

aes256-ctr

yes

aes256-gcm@openssh.com

yes

arcfour128

no

arcfour256

no

arcfour

no

blowfish-cbc

no

cast128-cbc

no

chacha20-poly1305@openssh.com

yes

rijndael128-cbc

no

rijndael192-cbc

no

rijndael256-cbc

no

rijndael-cbc@lysator.liu.se

no

Mac algorithms

Algorithm

OpenSSH 7.4

hmac-md5-96-etm@openssh.com

no

hmac-md5-96

no

hmac-md5-etm@openssh.com

no

hmac-md5

no

hmac-ripemd160-etm@openssh.com

no

hmac-ripemd160@openssh.com

no

hmac-ripemd160

no

hmac-sha1-96-etm@openssh.com

no

hmac-sha1-96

no

hmac-sha1-etm@openssh.com

no

hmac-sha1

no

hmac-sha2-256-96

no

hmac-sha2-256-etm@openssh.com

yes

hmac-sha2-256

yes

hmac-sha2-512-96

no

hmac-sha2-512-etm@openssh.com

yes

hmac-sha2-512

yes

umac-128-etm@openssh.com

no

umac-128@openssh.com

no

umac-64-etm@openssh.com

no

umac-64@openssh.com

no

Compression algorithms

Algorithm

OpenSSH 7.4

none

yes

zlib@openssh.com

yes

Moduli file

Modulus

OpenSSH 7.4

Modulus size

>= 2048 bit

SFTP retention

Customer data - Account configuration

  • An SFTP account with no activity for 12 months is disabled.
    Customers can request reactivation for 6 additional months before definitive deletion of the account and its accesses.

  • A Firewall rule with no activity for 12 months is disabled.

  • An RSA key whose size is between 3072 bits and 4095 bits is valid for 2 years.

  • An RSA key greater than or equal to 4096 bits is valid for 5 years.

  • An ED25519 key is valid for 5 years.

Customer data - Documents

  • Customers have 15 days to retrieve subscription reports made available on their account (out/ins directory).

  • Customers have 90 days to retrieve other reports made available on their account (out/ directory).

  • Files processed are saved and deleted 45 days after their processing date.

  • Files not processed are deleted 90 days after their creation date.

File deposit and withdrawal

Folder tree

The company has input/output directories on the UKG HR Service Delivery server by document type and by data type.

  • The input directory (in) and the output directory (out) are symmetrical.
    • The documents sent by the IS client are deposited in the in directory.

    • The processing reports associated with the input files are made available in the out directory (error report).

  • Some other specific purpose directories are not symmetrical.

Warning

Report files related to data synchronization and document distribution.
The provision of these reports is optional and must be planned during the project phase.

Warning

If the client’s tool does not automatically create a file with a “.filepart” suffix during its transfer, the client company must include the “.filepart” suffix when writing the file, which must be subsequently removed at the end of the transfer.
This step is necessary to prevent UKG HR Service Delivery from processing a file that is being sent or has failed to be sent before the transfer is complete.

UKG is responsible for the destruction or archiving of files after processing.

UKG HR Service Delivery uses the same mechanism (See .filepart above) to prevent the client company from retrieving a file in the process of being created.
The company is responsible for destroying the files after recovery; otherwise, UKG HR Service Delivery destroys them automatically after three months.

Customer agrees to deposit these files with at least file permissions 640 (rw-r—–).

Default directories for each SFTP account

Symmetrical INPUT directories

Symmetrical OUTPUT directories

Other directories

in
├── rpa
│ ├── emp
│ ├── gen
│ ├── prc
│ ├── req
│ └── sig
├── sal
├── sig
├── sir
└── usr

out
├── rpa
│ ├── emp
│ ├── gen
│ ├── prc
│ ├── req
│ └── sig
├── sal
├── sig
├── sir
└── usr

dev
in
├── dis
├── pro
out
├── bil
├── bir
├── ins
└── tra

Directories usage

Input file directory

Symmetrical INPUT directories

Usage

in/rpa/emp

Directory containing Zip File to Document Manager with Robotic Process Automation

in/rpa/gen

Directory containing Csv to Docgen to Document Manager with Robotic Process Automation

in/rpa/prc

Directory containing Csv to process with Robotic Process Automation

in/rpa/req

Directory containing Csv to requests with Robotic Process Automation

in/rpa/sig

Directory containing Csv to Docgen to Signature with Robotic Process Automation

in/sal

Directory containing the import and update employee files (see Employee synchronization)

in/sig

Directory containing mass signature distribution

in/sir

Directory containing the import and update files for the organizations (see Organization synchronization)

in/usr

Directory containing the document management user import and update files (see User profile synchronization)

Ouput file directory

Symmetrical OUTPUT directories

Usage

out/rpa/emp

Directory containing reports of Zip File to Document Manager with Robotic Process Automation

out/rpa/gen

Directory containing reports of Csv to Docgen to Document Manager with Robotic Process Automation

out/rpa/prc

Directory containing reports of Csv to process with Robotic Process Automation

out/rpa/req

Directory containing reports of Csv to requests with Robotic Process Automation

out/rpa/sig

Directory containing reports of Csv to Docgen to Signature with Robotic Process Automation

out/sal

Directory containing the employees synchronization error reports

out/sig

Location of the PGP public key that allows the signature of the generated files to be verified.

out/sir

Directory containing the organizations synchronization error reports

out/usr

Directory containing the users synchronization error reports

Other directories

Other directories

Usage

dev

Directory used for logging purpose

in/dis

Directory containing distribution files and spool
To automate distribution processing, the “projects” (grouping of distributions) must be performed in accordance with the protocol described in Creating a distribution project.

in/dse

Warning: upcoming deprecation
Directory containing the data sets synchronization files (see Data set import file format)

in/emp

Warning: upcoming deprecation
Directory containing the company document mass upload spools (ZIP with 1 CSV and several documents)

in/pro

Directory containing the project files (see Creating a distribution project)

in/rpa/custom_xxx

Directory containing specific or custom integration

out/bil

Directory containing the billing reports

out/bir

Directory containing business intelligence reports

out/emp

Warning: upcoming deprecation; use out/rpa/emp/ instead
Directory containing the company document mass upload reports

out/ins

Directory containing the employee registration reports

out/rpa/custom_xxx

Directory containing specific or custom integration reports

out/tra

Directory containing the file transmission reports through SFTP

Proof of safe receipt (optional)

For each file sent to UKG HR Service Delivery server via SFTP, the system generates a proof of receipt containing the hash of the received file.
This proof is stored in the folder out/tra.

The generated file complies with the following naming convention:

cdmat_{client}_tra_{flux}_{timestamp}.xml

With:

  • client: unique client identifier (the partner is not repeated in this name)

  • flux: type of file received corresponding to the proof of receipt:

    • dis: batched distribution files (payslip, etc.)

    • usr: document management user (user updates)

    • usa: people assist user (user updates)

    • sal: employee (employee updates)

    • ins: registration status

    • sir: company updates

    • bil: billing report

    • dse: data sets

  • timestamp: Timestamp, corresponding to the creation of the proof

And the content of the file is as follows:

<?xml version='1.0' encoding='utf-8'?>
<transfert_report version="1">
  <file>
    <file_name>ndmat_198538752_2011091610440841_sal_rhw_930_20130206113837.csv</file_name>
    <file_timestamp>2013-01-16T14:20:00+01:00</file_timestamp>
    <file_fingerprint algorithm="SHA1">9849a4d500126203a099aca0cd7017cb8748fb2a</file_fingerprint>
    <file_size>238</file_size>
  </file>
</transfert_report>

With:

  • file_name: Name of the file received corresponding to the proof

  • file_timestamp: Date the proof was generated as

  • file_fingerprint: Hash of the received file

  • file_size: Size of the received file in bytes

File naming conventions

The naming format of the uploaded files is as follows:

{dest}_{partner}_{client}_{flux}_{appemet}_{version}_{timestamp}.{extension}
or {dest}_{client}_{client}_{flux}_{appemet}_{version}_{timestamp}.{extension}
or {dest}_{client}_{client}_{flux}_{timestamp}.{extension}

With:

  • dest: destination application, may take the values:

    • ndmat: For files from the IS client to UKG HR Service Delivery

    • cdmat: For UKG HR Service Delivery files to the IS client

  • partner or client: unique identifier of the partner in the case of indirect clients.
    In the case of a direct client, provide the client identifier

  • client: unique identifier of the client

  • flux: type of the file. May take the values:

    • dis: batched distribution files (payslip, etc.)

    • usr: document management user (user updates)

    • usa: people assist user (user updates)

    • sal: employee (employee updates)

    • ins: registration status

    • sir: company updates

    • bil: billing report

    • dse: data sets

  • appemet: (optional) Sending application.
    Used in particular when multiple different applications must communicate with UKG HR Service Delivery

    • From client: application name (ex. SAP)

    • From UKG HR Service Delivery: UKG HR Service Delivery application name (ex. ndmat)

      For data sets synchronization, the appemet is used to pass the code of the dataset to synchronize.
      The code of the dataset is unique and available in the administration interface of UKG HR Service Delivery

  • version: (optional) If possible, use the exact version of the application, following the character set.
    Used in particular when multiple different applications must communicate with UKG HR Service Delivery

    • Note: For test files to be integrated into the client acceptance platform, indicate « tst »

  • timestamp: Timestamp, corresponding to the creation of the file, in yymmddhhmmss format

  • extension: zip, pdf, csv, xml, sig

    • Note: The sig extension corresponds to the signature file for each report file generated by UKG HR Service Delivery

For example, an employee file (flux = sal), for a direct client named macrosoft using an HRIS named hrmanager in version 6 would be named as follows:

ndmat_macrosoft_macrosoft_sal_hrmanager_v6_15486131891569.csv