ERS Vouchers

The Voucher Build process creates ERS vouchers from procurement receipt records. The receipts must be priced and have extended merchandise amounts.

The Voucher Build process creates ERS vouchers from receipts that reference a purchase order, as well as receipts that do not (non-PO receipts). For non-PO receipts, the process creates ERS vouchers only for receipt lines that have unit prices (priced receipts). These unit prices can be populated online from the item master or supplied by an external receipt load interface module.

To create ERS vouchers, you must identify the supplier location as an ERS supplier and set up the PeopleSoft Payables business unit (on the Payables Definition - Voucher Build page) to allow ERS transactions. You establish ERS options on the Procurement Control - ERS Options page, but you can also override them on the Payables Definition - Voucher Build page.

The Voucher Build process creates separate ERS vouchers for each packing slip that is referenced on a single receipt and multiple ERS vouchers from a single receipt, as receipt lines are marked as received. You can either create the ERS voucher invoice date from the receipt date or let the freight terms on the ERS receipt determine whether to use the receipt of the shipment date as the invoice date.

If the same packing slip number is used as the invoice number on multiple ERS vouchers (because an ERS receipt was partially invoiced), the pre-edit subprocess adds an ERS sequence number (ERS_INV_SEQ) to the ERS voucher header. This prevents the Duplicate Invoice Checking feature from rejecting ERS vouchers that have the same packing slip number and have been built from the same receipt.

You can search using packing slip number information on two voucher entry pages:

• Regular voucher entry, on vouchers with an ERS source type.

• Summary Invoice Entry voucher.

Note:

Matching does not create ERS vouchers in PeopleSoft Payables. However, on the receiver you can require that ERS vouchers be matched after they pass the voucher edit subprocess. If you do not require matching, the voucher edit subprocess flags the receipts as approved for payment.