Recognition and Invoice Data Issues

Use this table to troubleshoot recognition, invoice data, Invoice Completion, and anomaly-control issues.

Issue	What to check	Corrective action
Supplier isn’t recognized	Compare supplier name, address, tax-registration details, and supplier-site data with the invoice.	Correct supplier master data and verify that supplier details match invoice content as closely as possible.
Incorrect supplier is recognized	Check for duplicate supplier sites, similar supplier names, identical addresses, or internal suppliers affecting prediction.	Clean supplier data, remove avoidable ambiguity, and review internal-supplier handling.
Supplier site is incorrect	Check whether multiple supplier sites use similar or identical addresses.	Update supplier-site details and avoid maintaining duplicate address patterns where possible.
Purchase order isn’t recognized	Check whether the purchase order number is visible on the invoice and whether synchronization has completed.	Verify the purchase order format, wait for synchronization if needed, and retest with invoices that clearly display the purchase order number.
Incorrect purchase order is recognized	Check whether purchase order numbers are numeric-only or easily confused with invoice numbers, dates, or amounts.	Use distinctive purchase order formats where possible, such as alphanumeric formats.
Invoice lines aren’t recognized as expected	Check Document Recognition and Processing Options for matched- and unmatched-invoice line recognition.	Update line-recognition options and retest matched, unmatched, service, and utility-invoice scenarios.
Tax or freight isn’t handled as expected	Check the tax, freight, and proration options configured for document recognition and invoice import.	Adjust recognition options and validate the resulting invoice lines, tax behavior, and freight handling.
Invoice Completion policy doesn’t populate the target attribute	Check whether the invoice was imported, the policy condition was met, the target field was blank, and the required source attributes were available.	Correct the policy condition or source data and test with another imported invoice. Invoice Completion doesn’t override an existing target value.
Invoice Completion policy populates an unexpected value	Check the natural-language instruction, the source-and-target combination, and whether more than one policy applies to the target attribute.	Refine the instruction, maintain a separate policy for each target attribute, and retest before broader use.
Invoice Completion policy doesn’t apply to a manually created invoice	Check how the invoice was created.	No corrective action is required. Invoice Completion applies during invoice import and doesn’t apply to manually created invoices or invoices inserted directly into Payables base tables.
Anomaly control doesn’t mark an expected invoice	Check whether the anomaly pattern is enabled and whether the invoice meets the configured historical period, threshold, or comparison criteria.	Enable or refine the control and test it with an invoice that meets the configured criteria.
Too many invoices are marked as anomalies	Check whether the threshold is too broad, the historical period is inappropriate, or the selected comparison attributes are too inclusive.	Refine the control criteria and retest with both normal and anomalous invoice populations.
Expected duplicate invoice isn’t marked	Check the configured duplicate-invoice criteria and the invoice-number values being compared.	Correct the control criteria and retest using known duplicate examples.
Invoice remains in review after the issue is resolved	Check whether the invoice requires revalidation after a policy violation or anomaly has been reviewed.	Complete the required correction or override and revalidate the invoice.

Invoice Completion applies during import, populates only blank target attributes, and doesn’t override existing values. Anomaly patterns must be explicitly enabled and configured before they affect invoice processing.