Registering Buyers

Buyer registration establishes the buying entity in PeopleSoft eSettlements and a corresponding business unit in the underlying PeopleSoft system. This creates the underlying business units from which the voucher processing options appear by default. These include pay from bank information, as well as the matching and value-added tax (VAT) preferences that automatically appear on the voucher, either during application messaging or the Voucher Build process.

Each buyer has a unique PeopleSoft Payables business unit associated with it. If you plan to enable suppliers to use OAG XML functionality when transacting with a particular buyer in the Business Service Provider model—or when transacting with your organization in the Buyer Direct model—you must provide each supplier with the respective business unit value (identifier) for each buyer during buyer registration, so that each supplier can embed this identifier in the Header/Parties/BillToParty/PartyID/ID tag of the OAG XML file that they send.

If, for example, suppliers cannot embed this identifier in their files, the system administrator must define the identifier in their systems for this buyer. They must map this identifier to the buyer ID using code sets, so that each XML file provides a return value (translated value). This value uses the code set functionality for data translations in the Application Engine Transform program (EM_INV_OAG and CXML2PSFT).

Supplier XML files must either contain this return value or must have the correct value in the appropriate corresponding tag.

Note:

Read the code set sections in this topic if you are not providing a valid identifier for the PeopleSoft eSettlements application, because you must set up the code set to perform the data translation for the buyer value you provide in the XML file. If you don't provide a valid identifier, the subscription PeopleCode generates an email notification that the invoice failed edits.