How Transactions are Selected for Payment or Collection

The transactions included in a payment run, or a payment collection run, are determined initially by the method you choose to initiate the payment or payment collection run.

If you initiate a Payment Run (PYR) from a control desk, the transactions considered for payment are those displayed on the control desks in-tray.

You cannot initiate a payment collection run from a control desk.

If you run Payment Run (PYR) or Payment Collection Run (PYC) directly from SunSystems, the transactions are selected at run-time by a combination of:

  • the selection criteria defined in the payment profile chosen at run time
  • the run time selection criteria entered for the payment run, or payment collection run.

These payment profile selection criteria may also be overridden by particular system, account or transaction settings.

The payment profile selection criteria determine the accounts selected for payment, then within this, the transactions selected for payment.

Note:  A transaction can only be selected for payment, if its account is selected for payment.

Which Transactions are Selected for Payment

A payment profile contains the following selection criteria that determine whether or not a transaction is selected for payment:

  • Base or Transaction Currency Code
  • Allocation Marker
  • Journal Source
  • Journal Type
  • Transaction Reference
  • Ledger Transaction Analysis Codes (1 to 10)
  • Amount Threshold, when it applies to transactions
  • Payment Due Date, depending on the run time Base Date for Payment
  • Discount Due Dates, depending on the run time Base Date for Discount and Next Payment Date.

Some of these criterion can be entered at run-time.

The transaction selection criteria is overridden in the following circumstances:

  • transactions with a Withheld allocation marker are excluded from all payment runs
  • transactions with an allocation marker of Force are always included in the payment run, provided the account is included
  • transactions with a numeric allocation marker are only selected if the marker is greater than the number set in the Minimum Allocation for Payment field on Ledger Setup (LES).

The following payment run and payment collection run selection criteria also determine whether or not a transaction is selected for payment:

  • Base Date for Payment
  • Base Date for Discount (Payment Run only)
  • Next Payment Date (Payment Run only).
Note:  A transaction must meet all of the payment profile criteria to be considered for payment or collection. However, it may still be rejected by the payment run or payment collection run selection criteria

If the transactions selected for payment on a particular account result in a net debit total due for payment, Payment Run does not forward the transactions for payment. Instead it identifies these transactions on the payment run details report.

Finally, a Payment Limit can be set for a payment run or payment collection run. This is the maximum amount that can be paid or collected in the run. If this limit is exceeded by the payment or payment collection run, the run is abandoned and no accounts are paid or collected.