Voucher Origins

Each transaction entered into PeopleSoft Payables must have a valid origin, such as online or batch processing, that you define in the Voucher Origin table. You must have at least one origin, and each user must be associated with an origin. You can set up control values at the voucher origin level to override business unit defaults and automatically appear lower levels in the control hierarchy.

For example, if you have automated systems that pass information to PeopleSoft Payables—such as an electronic data interchange (EDI) interface—you might define an origin specific to those systems. Or you might set up and assign particular origins to individual data entry clerks, associating each voucher origin with a specific group of approved suppliers and allowing each data entry clerk to create vouchers for those suppliers only. For example, suppose that certain foreign invoices have distinct payment terms and other processing rules; you could set up a voucher origin with those default values and assign the origin to the data entry clerk who handles foreign suppliers.