BOD: Load Response Match Document

The purpose of the LoadResponseMatchDocument is to LoadResponse to the communication of a Change or Update of the MatchDocument information concerning invoice matching from another business application.

The invoice matching process may include several document types, including the following:

Two way match - Purchase Order and the Invoice

Three way match - Purchase Order, Invoice, and the Receipt

Four way match - Purchase Order, Invoice, Receipt, and Inspection results

Note: For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching.

When matching takes place in the purchasing application, the purchasing application may have to request the accounts payable application to provide the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched. This is the generally the situation when the invoice is initially entered into the accounts payable application.

Note that in some situations, accounts payable will send invoices to the purchasing application unsolicited. In others, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters.

When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. Alternatively, the accounts payable application can request the information.

Child Components

Release Identifier 1..1
Version Identifier 0..1
System Environment Code 0..1
Language Code 0..1
Application Area 1..1
Data Area 1..1
      Load Response 1..1
      Match Document 1..∞

Scenarios in which Load Response Match Document is used

Feedback

OAGi and its members welcome your feedback.

UUID: ac6ff94fc7fc4ed7b8e4b372fadb5167

OAGIS Version 10.12