Setting Up Pay Cycles

After completing the prerequisites, the system administrator must set up the pay cycles.

Important:

In the Buyer Direct model, you must assign the appropriate pay cycles to each user that is responsible for reviewing approving pay cycles from PeopleSoft eSettlements. In the Business Service Provider model, each buyer administrator must notify the exchange host which users from the buying entity will be responsible for reviewing and approving pay cycles.

To set up pay cycles, use the Secure Pay Cycles component (EM_SEC_PYCYCL_OPR).

This section describes how to assign pay cycle access and process pay cycles.

Page Used to Set Up Pay Cycles

Page Name	Definition Name	Usage
Pay Cycle by User ID Page	SEC_PYCYCL_OPR	Assign access for one or many pay cycles to the user responsible for reviewing and approving pay cycles.

Pay Cycle by User ID Page

Use the Pay Cycle by User ID page (SEC_PYCYCL_OPR) to assign access for one or many pay cycles to the user responsible for reviewing and approving pay cycles.

Navigation:

eSettlements, and then Administration, and then Secure Pay Cycles, and then Pay Cycle by User ID

Field or Control	Description
Pay Cycle	Assign the accessible pay cycles to the user ID that you selected to access the page.

Processing Pay Cycles

After you complete all relevant configuration, you run the pay cycle. The system administrator or buyer user accesses the Create Pay Cycle component and Pay Cycle Manager to create a pay cycle and select the payments.

Note:

If you have enabled financial sanctions at either the installation or bank level, the system does not select payments for a supplier with a financial sanctions status of Blocked or Review. However, if financial sanctions validation is enabled at the bank level and you no longer validate for a particular supplier's bank, the system may select a supplier with a financial sanctions status of Review for payment.

See PeopleSoft Payables: Understanding Pay Cycle Alerts.

The system administrator can specify that pay cycle approval is required either on the buyer Registration page in PeopleSoft eSettlements, or in the Payment Selection Criteria component (PYCYCL_DEFN) in PeopleSoft Payables.

A pay cycle containing any buying organizations that specified their payment approvals be performed in PeopleSoft eSettlements, will be eligible for the payment selection process only, and will not be eligible to have both the payment selection and payment creation processes run together.

System administrators or buyers can select any payment method other than draft payment methods when they create a pay cycle.