Receiving Accounts Payable Payments
Page Name |
Definition Name |
Usage |
---|---|---|
Payment Interface Page |
PAYLOAD_REQUEST |
Define run parameters for the Payment Loader process to load Accounts Payable payments into the payment application tables. Select the Accounts Payable Payments check box. See Updating Payment Application Tables. See the Payment Interface Page for more information. |
PeopleSoft Accounts Payable payments processing enables customers to automatically create deposits and payments in PeopleSoft Receivables when the Payables system pays interunit vouchers. Using integrated Accounts Payable payments processing, you can set up interunit billing to settle payables vouchers internally and create corresponding deposits in receivables.
The staging tables created by Accounts Payable use a data source value, APP, which is designated for Accounts Payable payments only. This data source value distinguishes payments received from PeopleSoft Payables as opposed to payments received from other sources.
The APP data source identifies records in the Payment Loader staging tables to be built specifically for Payables input. The Payment Loader application engine processes those records to create required deposit, payment, and reference records so that payments can be applied to the specified open items in Receivables. Payment Loader does not use split stream processing for APP items. Deposit and payment records as well as all reference records are sent in the same batch process.
The Customer InterUnit Billing setup (Customers, Customer Information, General Information, General Info, Bill To Options) identifies an interunit customer. The setup also defines which receivables business unit is associated with each customer.
An interunit customer can use an internal netting account. Netting accounts are used in the system for the treasury netting process. The netting account functionality will be extended to allow for a deposit to be created for payments from PeopleSoft Payables.
Processing for APP items uses one type of payment method—check—for interunit billing, however, no external processing occurs. Each payment that Payables sends to Receivables will have a check number, billing business unit, billing customer, and other pertinent payment information. The system will generate the next available payment ID for the transaction. Each reference item will have a payment amount, and the system creates a separate deposit for each payment, assuming one customer per payment.
This table shows how the APP process maps the fields on the payables voucher to the fields in the payment staging tables:
Accounts Payable Fields |
Payment Staging Table Fields |
---|---|
Billing Business Unit |
BUSINESS_UNIT |
Billing Customer |
CUST_ID |
Accounts Payable Check Number |
PAYMENT_ID |
After you load the payables vouchers into the payment application tables, you can use Payment Predictor to apply the payments to the items associated with the vouchers. In order to apply this payment from Payment Predictor, the items must have been created using Receivables Update.
Use the Payment Interface page (PAYLOAD_REQUEST) to define run parameters for the Payment Loader process to load Accounts Payable payments into the payment application tables.
Navigation:
Select the Accounts Payable Payments check box.
Note: Match criteria options are not functional for Accounts Payable payments.