Setup and Processing in the Business Service Provider Model

When implemented as the Business Service Provider model, multiple buyers are involved, and all of the same features and functionality apply.

This section discusses:

  • Setting up the Business Service Provider model.

  • Processing in the Business Service Provider model.

For a Business Service Provider implementation:

  1. Create a buyer bank account and a buyer template.

  2. Create buyers (buying organizations) and assign their security and processing parameters.

    Buyer registration populates several underlying PeopleSoft tables, creating a PeopleSoft Payables, Purchasing, and General Ledger business unit for each buying entity, along with all necessary procurement processing options.

  3. Create local buyer administrators.

    The first user profile that you create for each new buying entity is its local buyer administrator. You also assign business unit security and data access to the buyer administrator, defining the buying entities to which the buyer administrator has access. Then, you define the processing options for the buyer administrator, including preferences such as the ability to record payments or override match exceptions.

  4. Create local buyer users (this is done by each buying organization's buyer administrator).

    The buyer administrator then completes the implementation process, updating and finalizing the registration for the buying entity by specifying matching preferences and creating additional users within the organization.

  5. Create buyer pay cycles and assign associated security.

  6. Create a selling entity (supplier) by defining subscription and system access, and then create a local supplier administrator for this new supplier.

    If financial sanctions validation is enabled at the installation level, and you create a new supplier, the system validates the supplier against the financial sanctions lists either when you attempt to save the supplier or on an ad hoc basis, depending on how you set up financial sanctions validation. If there is a possible match, the system updates the supplier's financial sanctions status on the Supplier Information component (VNDR_ID) to Review and displays a warning message that the supplier 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. Specify security by defining which suppliers the supplier administrator can access, and establish processing preferences for the supplier administrator role.

  8. Register suppliers.

    The supplier administrator completes supplier registration by adding information specific to the selling entity. The supplier administrator can create new user profiles for additional individuals within their organization. Creation of a supplier treasurer is required if the supplier subscribes to payment notifications.

  9. Create agreements.

    The buyer 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 it and returning it to the buyer for completion.

Once you've set up a Business Service Provider model, processing follows these steps:

  1. Create purchase orders, invoices, and receipts.

  2. Review invoices in self-service pages.

  3. Run the PeopleSoft Payables Voucher Build process to create vouchers.

  4. Run the Matching process.

  5. Approve invoices and invoice lines, if required.

  6. Run pay cycle to select payments.

  7. Approve and create payments.

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.