Setup and Processing in the Buyer Direct Model

In this implementation, the buyer controls the PeopleSoft eSettlements application, which functions as a front end for the buyer's PeopleSoft Payables application.

This section discusses:

  • Setting up the Buyer Direct model.

  • Processing in the Buyer Direct model.

Note: To implement either the Buyer Direct or the Business Service Provider model, you must first establish your control data by defining information in the PeopleSoft system's global, core, and additional application tables. The information that you define in these tables lays the foundation for your PeopleSoft eSettlements-specific setup.

For a Buyer Direct implementation:

  1. Specify the Buyer Direct model.

  2. Create and name your own roles and permission lists.

  3. Create at least one user in a PeopleSoft Payables administrator role type.

  4. Create a buyer template.

  5. Enable PeopleSoft Payables business units as PeopleSoft eSettlements buyers.

    If you enable PeopleSoft Payables business units for use as PeopleSoft eSettlements buyers, ensure that the business unit is set up for automatic voucher numbering. Auto-numbering is used for self-service and XML invoices.

  6. Enable PeopleSoft Payables suppliers as PeopleSoft eSettlements suppliers.

    If financial sanctions validation is enabled, and you are enabling a PeopleSoft Payables supplier with a financial sanctions status of Blocked or Review, the system displays a warning message that the supplier selected is currently under financial sanctions review. You can decide to proceed with creating the supplier. However, the system does not allow payments to a supplier with a financial sanctions status of Blocked or Review.

    Note: How the system validates your suppliers is dependant upon how you set up financial sanctions validation options. Financial sanctions validation is discussed in detail in these topics and in PeopleSoft Source-To-Settle Common Information.

    See Understanding Supplier Registration.

  7. Create a local supplier administrator, who then completes supplier registration by adding information specific to the selling entity. The supplier administrator can then create new user profiles for additional individuals within the organization.

    Note: Creation of a supplier treasurer is required if the supplier subscribes to payment notifications.

  8. Create an agreement.

    This is a multistep process. The buyer administrator (or system administrator) initiates an agreement and offers it to the supplier. The supplier administrator reviews the terms and adds its organization's terms for the buyer before approving and returning the agreement to the buyer for completion.

Note: In the preceding steps, it is assumed that you have already implemented PeopleSoft Payables.

Once you've set up the Buyer Direct model, processing follows these steps:

  1. Enter vouchers into the system.

  2. Enter self-service and XML invoices in PeopleSoft eSettlements, and enter vouchers in PeopleSoft Payables.

  3. Review invoices in self-service pages.

  4. Run the PeopleSoft Payables Voucher Build Application Engine process (AP_VCHRBLD) to create vouchers.

  5. Run the Matching Application Engine process (AP_MATCH).

  6. Approve invoices and invoice lines, if required.

  7. Run pay cycle to select payments.

  8. Approve and create payments.

    Note: If payment approval is required, first create and assign pay cycle security.

Note: If financial sanctions validation is enabled, and you are using PeopleSoft Payables functionality, the system performs validations similar to those performed during the PeopleSoft Payables process.