A Matching Document is a document in and of itself. It may exist in an ERP application, just like a Sales Order. The Matching Document essentially holds a cross reference among the documents being matched. The header contains general and financial information. The document references used in the Header are for all of the doucments being matched in addition to documents that are not explicitly part of the matching process, but still need to be referenced, such as a Quote. However, since matching is essentiall N-way, even a Quote could be matched.
Note that the Status on the MatchDocument indicates whether the Match was successful or was a failure.
|
Elements: |
Name
|
Type
|
Description
|
Distribution
|
reference
|
Indicates the Financial Entities involved in the transaction.
A distribution identifies how monetary amounts are distributed accross an organization.
|
InvoiceDate
|
DateTimeAny
|
The date on which the original invoice document was issued
|
MatchingDate
|
DateTimeAny
|
The date on which the associated document was matched
|
MatchType
|
Type
|
contains the information that determines the type of invoice document matching process. Suggested values associated with this field are:
2 Way: Invoice is matched to the Purchase Order
3 Way: Invoice is matched with the Purchase Order, and Receipt
4 Way: Invoice is matched with the Purchase Order, Receipt, and Inspection results.
|
Parties
|
reference
|
|
Remittance
|
Remittance
|
Remittance refers to a reference identifier to print on a remittance advice, for example, supplier invoice number.
When a RemittanceAdvice BOD exists this could be a DocumentReference name RemittanceReference.
A reference identifier to print on remittance advice, for example, supplier invoice number.
|
UserArea
|
reference
|
|
|