How groups impact pay cycles
Defining multiple pay groups, process groups, and invoice groups will impact your payment cycle. This table describes the impact of groups on specific programs that you run in a pay cycle.
|
You can run AP150 once for an entire pay group or run it several times concurrently for individual process groups within the same pay group. Each time you run this job, you select records for different vendors and schedule those invoices for payment. If you run AP150 by process group, the program does not consider vendor priority when selecting invoices. To accomplish this kind of processing, you must define process groups by vendor priority. |
|
After you schedule all of the invoices you want to pay, run one of the payment creation programs to pay all scheduled invoices. The program creates one payment form or payment record for each vendor processed for each combined cash code and payment code in the pay group. If invoices are assigned with different invoice groups, the system creates a separate form for each invoice. For example, if you use two pay groups to process payments for two process levels, AP161 will create two payment files. If you use only one pay group, even if you have multiple process groups, AP161 will produce a single payment file. |
|
To close the payment cycle, run the payment closing program for an entire pay group or run the program concurrently for individual process groups. You can select either option, regardless of how you processed AP150. For example, even if you ran AP150 by process group, you would still have the option to run AP170 by pay group or process group. |