Preparing for Invoice XML Integration

Subscription PeopleCode converts XML messages into PeopleSoft eSettlements transactions. This PeopleCode calls or references information that has been configured in PeopleSoft in a method similar to the way in which a save is accomplished through the online pages.

This section discusses how to:

  1. Register buyers.

  2. Register suppliers.

  3. Define agreements.

  4. Define voucher defaults.

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.

Supplier registration creates the selling entity in PeopleSoft eSettlements and a corresponding supplier ID in the underlying PeopleSoft system. During registration, the supplier establishes basic location information, such as address, payment terms, and pay to bank account information. The system references these default values during the Voucher Build process.

You use agreements to define general processing options that are unique to a given buyer-supplier combination. Agreements are by supplier location and contain processing options such as payment terms and pay from bank information. Subscription PeopleCode references this configuration as the system converts incoming voucher XML messages into PeopleSoft eSettlements transactions.

Note: If a transacting buyer-supplier pair is using OAG XML invoices, the buyer must enter EM_SUPPLIER_REF in the Supplier Reference ID field on the agreement.

The OAG tag can be populated with either the EM_SUPPLIER_REF value that corresponds to the unique value entered on the agreement, or with a supplier ID. If the system cannot determine the supplier ID using the value in the Supplier Reference ID field, the system assumes that the value submitted is a valid supplier ID.

Voucher transmission relies on the existence of tables established in previous tasks. These tables provide values for invoices that are not included in the XML feed or in the online entry.