XML Invoices

Two ways are available to integrate XML invoices with the Voucher Build process:

  • Using XML invoices that are mapped to the VOUCHER_BUILD message definition for integrating with the Voucher Staging tables using Application Messaging.

    This process is also known as the Voucher EIP.

    Note:

    The Spreadsheet Voucher feature uses the Voucher EIP process (VOUCHER_BUILD) to import files to the PeopleSoft systems.

  • Using XML invoices that are defined in the Open Applications Group (OAG) standardized format, which are handled in Integration Broker, mapped to the PeopleSoft invoice structures by the Transform OAG to PSFT Invoice Application Engine process (EM_INV_OAG), and connected to the quick invoice tables using the EM_VOUCHER_IN application message definition.

    Important:

    When you are building XML invoices using Integration Broker, the date format must be YYYY/MM/DD, or the subscription process fails.

The OAG XML invoice interface with the Voucher Build process is discussed in full in separate documentation.

Note:

In addition to delivering the VOUCHER_BUILD and EM_VOUCHER_IN EIPs as application messages, PeopleSoft also delivers them as web services (Voucher and SelfServiceInvoice, respectively). Enabling web services is discussed in the PeopleTools: Integration Broker.

PeopleSoft Payables users should also know that:

  • PeopleSoft Payables users may need to define codesets in Integration Broker that differ from those that are used by eSettlements.

  • OAG XML invoices must use the GL_Element tag to identify the Account ChartField if the invoice includes distribution information.

  • The Voucher Build process assigns match delay days to XML transactions that require matching based on the PeopleSoft Payables hierarchy, business unit, origin, control group, supplier, and the ability to override on the voucher.

    If you do not define match delay days on the PeopleSoft Payables hierarchy, the Voucher Build process will not assign match delay days. As an example, if the match delay days are five days, the system adds five days to the entry date to determine the match due date. On the Match Request page, enter a date in the As of Date field to work in conjunction with the match due date. The Matching process selects only the vouchers that are ready to be matched as of that date. Match delay days are only applicable to EDI, XML, Document imaging, Spreadsheet vouchers, Online, Quick and Self Service invoices. These types of transactions usually are processed in the system before the lines are received. Using match delay days enables you to wait to include these transactions in the Matching process.

Related Topics