Understanding Payment Run

Payment Run (PYR) is used to settle selected outstanding transactions on creditor/payables accounts. It can also settle transactions on client accounts with a credit balance. Payment Run can trigger the creation of the necessary payment documentation, for example, remittances and cheques. It can also produce a bank transfer file for electronic transmission.

Payment Run can be initiated from the SunSystems menu, or from a control desk, or from Payment Selection and Review (PYS) (which is a specific control desk function that allows you to save sets of selected transactions for review and payment). The method you choose determines how the transactions to be considered for payment are chosen:

• If you initiate Payment Run from the SunSystems menu, the transactions are selected by the payment profile you choose, and any run time selection criteria you enter. You can define any number of payment profiles although only one can apply to a particular payment run. Each profile can contain different selection criteria, including account selection criteria, currency codes, due dates, and so on.
• If you initiate Payment Run from a control desk, the transactions considered for payment are those displayed on the control desk in-tray when you initiate the payment run process. A filter is used to extract the transactions for payment using the selection criteria defined within the filter.
• If you initiate Payment Run by using Payment Selection and Review (PYS), the transactions considered for payment are those in the payment set (saved set) that you create.

Payment Run does not automatically pay all of the transactions it is presented with for payment. It only pays those that are eligible for payment according to the many different payment criteria that can apply.

When you initiate Payment Run you must choose a payment profile, even if you run it from a control desk or from Payment Selection and Review. This is because the payment profile determines other important payment details including the type of payment output required, and the payment bank details.

Before you initiate a Payment Run, regardless of the method you use, you should identify or define the payment profile that contains the payment run requirements. You may also want to preview the payment selections.

If the Authorization facility is enabled and authorization stages have been defined for payment processing, Payment Run checks whether the transactions selected for payment require authorization. If they do, the payment run is suspended until the transactions are fully authorized. When they are fully authorized, the payment run is completed automatically and all you will need to do is produce the payment documents, if required.

When you run the Payment Run, you can choose to produce the payment run details report only and use this to verify that the correct payments are produced. This allows you to review the proposed payments and make adjustments, if necessary.