Payment Workflow

Payments >

The PayGate Desktop Workflow

A key concept of PayGate Desktop is something we call 'payment workflow'. We have split the BACS payment process into 5 steps. Each step can be carried out by the same person, a different person or a mixture of the two. Using this workflow we are able to assign different tasks to different users and restrict some users from being able to carry our certain functions. For example, some organisations may wish to restrict the 'Approve' step to a specific, senior member of staff.

The five steps in the Payment Workflow are as follows:

Roll Role Description

Create This user uploads the original payment file into PayGate Desktop or manually keys the payment data in. The user will use PayGate to validate and, if necessary, amend the payment data.

Sign This user holds a bank issued BACS smartcard and knows the PIN. The user checks the payment data and is responsible for digitally signing the submission using their smartcard. Once the submission is signed it cannot be modified in any way but it is not yet approved for submission and cannot yet be sent to BACS for processing.

Approve This user is responsible for approving the submission. All submissions must be approved before they can be send to BACS for processing.

Submit This user sends the submission to BACS. They hold a bank issued BACS smartcard and know the PIN. They are responsible for authenticating to the BACS service and uploading the submission to the BACS or Faster Payments service and collecting the initial Submission Summary report.

Collect This user downloads BACS reports in a variety or formats from the BACS or Faster Payments service. They have access to a bank issued smartcard and know the PIN.

Roll	Role Description
Create	This user uploads the original payment file into PayGate Desktop or manually keys the payment data in. The user will use PayGate to validate and, if necessary, amend the payment data.
Sign	This user holds a bank issued BACS smartcard and knows the PIN. The user checks the payment data and is responsible for digitally signing the submission using their smartcard. Once the submission is signed it cannot be modified in any way but it is not yet approved for submission and cannot yet be sent to BACS for processing.
Approve	This user is responsible for approving the submission. All submissions must be approved before they can be send to BACS for processing.
Submit	This user sends the submission to BACS. They hold a bank issued BACS smartcard and know the PIN. They are responsible for authenticating to the BACS service and uploading the submission to the BACS or Faster Payments service and collecting the initial Submission Summary report.
Collect	This user downloads BACS reports in a variety or formats from the BACS or Faster Payments service. They have access to a bank issued smartcard and know the PIN.