Setting Up the PeopleSoft Financial Gateway Integration

To set up your PeopleSoft Financial Gateway integration, use the following components:

  • Source Registration (PMT_REGISTRATION).

  • User Preferences (OPR_DEFAULT).

  • Payment Selection Criteria (PYCYCL_DEFN).

This section provides an overview of the PeopleSoft Financial Gateway integration setup and lists prerequisites.

Page Name

Definition Name

Usage

Source Registration Page

PMT_REGISTRATION

Register a subsystem to integrate with PeopleSoft Financial Gateway, and define high-level registration details.

PayCycle Page

OPR_DEF_TBL_PYCYCL

Define default output destinations for the Pay Cycle Manager and the Express Check Manager components. These default values are not required to perform any pay cycle process.

See Establishing Payment Errors Email Notification

Payment Selection Criteria - Preferences Page

PYCYCL_DEFN_OPT

Set pay cycle general options.

PeopleSoft Payables integrates with the PeopleSoft Financial Gateway functionality as an alternate electronic payment processing method. PeopleSoft Financial Gateway acts as a broker between PeopleSoft Payables and a financial institution, formatting payments and managing payment messages between the systems.

For PeopleSoft Payables, integration with the PeopleSoft Financial Gateway functionality involves the following steps:

  1. Registering PeopleSoft Payables as a source subsystem with PeopleSoft Financial Gateway.

  2. (Optional) Defining payment errors email notification defaults.

Source registration is a required implementation step. Once registered as a source subsystem, PeopleSoft Payables uses the existing PeopleSoft Financial Gateway infrastructure during pay cycle processing to settle PeopleSoft Financial Gateway-specific payments.

Registering PeopleSoft Payables also enables PeopleSoft eSettlements to integrate with PeopleSoft Financial Gateway. PeopleSoft eSettlements leverages both the PeopleSoft Financial Gateway and Payables infrastructures to manage PeopleSoft Financial Gateway-specific payments. As PeopleSoft eSettlements uses the existing architecture, it does not need to be registered as an independent source.

Oracle delivers default source registration data, applicable to most organization's needs.

Important! You should carefully analyze the delivered data with your organization's business needs before changing any values. Editing certain registration values might adversely affect payments' settlement through the applications. Also, system administrators should configure the appropriate security for this page, limiting user access to avoid accidental edits.

After registering as a source, you can optionally set up payment errors email notifications. This alerts designated users when payments cannot be settled through PeopleSoft Financial Gateway.

To process payments through the PeopleSoft Financial Gateway, you must correctly configure and activate payments' bank accounts using the External Accounts - Payment Methods page. On the page, you must specify at least one layout that is settled by PeopleSoft Financial Gateway.

Use the Source Registration page (PMT_REGISTRATION) to register a subsystem to integrate with PeopleSoft Financial Gateway, and define high-level registration details.

Navigation:

Financial Gateway > Administration > Source Registration

This example illustrates the fields and controls on the Source Registration page (1 of 2).

 Source Registration page (1 of 2)

This example illustrates the fields and controls on the Source Registration page (2 of 2).

 Source Registration page (2 of 2)

Oracle delivers PeopleSoft Payables with defined integration values, as shown in the page screenshots. Your organization's integration values may be different, based on your business needs.

You should avoid editing any of the delivered values, except for these:

  • Dispatch Status: Add any required payment dispatch statuses.

  • Display in Payment Details: Select or deselect check boxes to determine field display on the Review Payment Details page.

  • Seq (sequence): If you select a field for display, entering a sequence value determines the display order. You can edit this value.

Use the PayCycle page (OPR_DEF_TBL_PYCYCL) to define default output destinations for the Pay Cycle Manager and the Express Check Manager components.

These default values are not required to perform any pay cycle process.

Navigation:

Set Up Financials/Supply Chain > Common Definitions > User Preferences > Define User Preferences

Click the Paycycle link on the User Preferences page.

To establish payment error notification emails for user IDs:

  1. Define an email address on the User Preferences - PayCycle page.

  2. Define a payment error notification user ID on the Payment Selection Criteria - Preferences page.

See User Preferences - PayCycle Page.

See Payment Selection Criteria - Preferences Page.