Service overview

The following diagram shows the end-to-end flow of information between Sage People Payflow and a third-party service using a managed SFTP provider to store and forward upload and download files.

Diagram: Payflow service overview

For outbound Payflow services:

  1. Data extracted from fields in supported HCM objects is mapped to a download file using the configuration in Mapping HCM to Download Files.

  2. The download file specification takes the information from mapped fields, and formats it into a download file that can be consumed by the third-party provider.

    The download configuration specifies where to send the file, and the default properties of the file.

  3. When the download batch is run, the file is transferred to the Sage People SFTP provider, using the outgoing server address and folder path specified in the download configuration.

  4. The SFTP provider can be configured to transfer the file to your third-party system (store and forward). Alternatively, you can configure the third-party system to retrieve the file. .

For inbound Payflow services:

  1. Your third-party system must be configured to transfer its upload file to the Sage People SFTP provider.

  2. When the upload batch is run , Payflow retrieves the file from the incoming server and path specified in the upload configuration.

  3. The upload file configuration specifies some default properties of the uploaded file to enable Sage People to interpret the data and map it to data objects.

  4. Data from the upload file is initially mapped to Payroll Line or Inbound Staging Line objects. These objects are used to store the uploaded data before it is used to update data in Sage People HCM objects.

  5. Data stored in the Payroll Line or Inbound Staging Line objects is mapped to fields in supported HCM objects and used to update information held in Sage People HCM.