Matching notes and limits

These notes are important when the visible matching results do not line up with what users assume the system should do.

Receipt Comparison Is Not Fully Implemented

The current matcher can store the most recent receipt number on the header match result when it finds one for the purchase order.

However, active receipt-line comparison is still a placeholder. In practice, the visible matching flow is mainly comparing the invoice against the purchase order and its lines, not fully comparing invoice lines against receipt lines.

The status value Receipt Not Found exists, but the active matching flow does not set that status today.

Some Visible Approval And Warning Options Are Not Wired Into The Active Processor Path

These settings exist in setup or analyzer configuration, but they are not currently used by the main document-processing path:

Require Order Match for All Invoices
Auto-Post if Matched
Auto-Approve Within Tolerance
Warning if Outside Tolerance
analyzer-level Auto-Approve if Matched

Outside-Tolerance Results Do Not Control The Final Processing Decision By Themselves

The matching engine writes detailed results, including Outside Tolerance, but the document processor does not currently use the returned matching success value to stop automatic document creation on its own.

That makes the results list the most reliable place to understand matching exceptions for a processed invoice.

Partial Matching Is Broader Than The Label Suggests

When Allow Partial Matching is enabled, the current logic can let the overall match return success even when some line results are unmatched or outside tolerance.

Users should review line-level results instead of assuming that a successful overall run means every line matched cleanly.

Header Match Method Reporting Is Simplified

The header result always records the match method as External Document No. even if the alternate reference lookup found the purchase order.