The Invoice Validation process checks the matching tax, period status, exchange rate, and distribution information for invoices you enter and automatically applies holds to exception invoices. If an invoice has a hold, you can either manually release the hold (if allowable) or correct the exception that caused Invoice Validation to apply the hold and then resubmit Invoice Validation.
You can schedule regular submission of the Invoice Validation program when you define your submission options for the Invoice Validation program in the Submit Request window. You can specify the intervals in which you want to submit Invoice Validation, and Payables will submit Invoice Validation using the parameters that you specify up until the End Resubmission date you specify. See also: Submitting Standard Reports, Programs, and Listings.
Option.
All. Submit Invoice Validation for all invoices that do not have a status of Validated. Payables reviews all invoice distributions that Invoice Validation has not yet reviewed, and reviews invoices with unreleased holds.
New. Process only invoice distributions that were entered or imported after the last validation cycle. Invoice Validation only selects invoice distributions that Invoice Validation has not yet reviewed. If you choose this value, Invoice Validation does not review any invoice distributions already on hold.
Suggestion: Enter All to ensure you release any existing holds on invoices as well as place new holds. Submit Invoice Validation right before you make automatic payments to update the authorization status on all invoices.
Invoice Batch Name. Invoice Validation reviews invoices that are in the invoice batch you select. You can enter a value in this field only if you have enabled the AP: Use Batch Controls profile option. See Profile Options in Payables.
Start/End Invoice Date. If you want Invoice Validation to review invoices that have an invoice date in a range you specify, then enter a date range.
Supplier Name. If you want Invoice Validation to review invoices for a specific supplier, then enter the supplier.
Pay Group. If you want Invoice Validation to review invoices for a specific pay group, then enter the pay group.
Invoice Number. If you want Invoice Validation to review a specific invoice, then enter the invoice number.
Entered By. If you want Invoice Validation to review all invoices entered by a specific person, then enter the userid of that person.
This topic provides overview of Invoice Validation Parallel Processing. Invoice validation concurrent program now supports multiple child requests based on the Purchase Order matched invoice. A new profile option, AP: Maximum Invoice Validation Child Requests, lets you specify that. You submit a single Invoice validation program, and internally the program groups matched invoices to same Purchase Orders and ensures that each such group is processed by a single child request. Whereas for invoices that are not matched to any Purchase Orders, the system distributes such invoices equally amongst the maximum number of child requests specified for the profile.
A new profile, AP: Maximum Invoice Validation Child Requests, is added that controls the maximum number of child requests that can be spawned by the concurrent program.
Note: The maximum value is two times the number of CPUs. Also, number of paths to disk influence this setting. Consider the number of programs and activities that can be carried out in parallel without significantly degrading performance.
The existing option, Maximum Invoices Count, in Invoice validation concurrent program is renamed as, Minimum Threshold for Parallel Processing. The value entered in the option is considered as the minimum threshold value on the number of invoices, over which the invoice validation program uses the value mentioned in the profile and spawns multiple child requests. The default value is 1.
If the validation program selects a load with more than one invoice, then the program spawns multiple child requests as per the profile, AP: Maximum Invoice Validation Child Requests. If you run the validation on a single request without changing the profile, then set the value of the parameter to 0 or null or a very high value while submitting the program. The new child requests launched does not have any outputs but they will have log files containing valuable debug information about the validation run. The only output available would be the current validation report from the first/main validation request.
A new concurrent program, Invoice Validation Child Worker Process, is seeded and is spawned internally as child requests. This program is not available from the Submit Request Set (SRS) window to be submitted individually.
If two simultaneous Invoice validation program are submitted, then it is not guaranteed that invoices matched to same PO are grouped and processed by a single concurrent request.