Service overview

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

Diagram: Payflow service overview

For outbound Payflow services:

  1. The system maps data it extracts from fields in supported HCM objects to a download file. It uses the configuration in Mapping HCM to Download Files.

  2. The download file specification takes the information from mapped fields. It formats it into a download file that the third-party provider can consume.

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

  3. When the download batch runs, the system transfers the file to the Sage People SFTP provider. It uses the outgoing server address and folder path you specify in the download configuration.

  4. You can configure the SFTP provider 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. Configure your third-party system to transfer its upload file to the Sage People SFTP provider.

  2. When the upload batch runs , Payflow retrieves the file from the incoming server and path you specify in the upload configuration.

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

  4. Data from the upload file initially maps to Payroll Line or Inbound Staging Line objects. The system uses these objects to store the uploaded data before it updates data in Sage People HCM objects.

  5. Data you store in the Payroll Line or Inbound Staging Line objects maps to fields in supported HCM objects. The system uses it to update information it holds in Sage People HCM.