Check numbers on long payments

Dynamics AX 2009 for Retail, we have multiple vendors where the number of invoices to be paid on any given payment are more than will fit on the check stub of a single page. When we print a check for these vendors, we get a check number applied to the first page of the check and its accompanying stub. The payment then continues onto a second page, where the check area is "Void"ed, and the check stub contains the continuing list of invoices being paid. Unfortunately, this second page has a sequentially incremented check number, both in the check number area and in the check stub header.

So, if we paid everything on check 1234, the second stub seems to say we paid those invoices on check 1235. But there is no actual check 1235 - the number is “wasted” on that voided check. Nobody will ever deposit a check 1235.

This results in vendor confusion, A/P confusion, and SOX issues (checks issued are not sequential).

How can we stop check numbers from being wasted in this way? We want the primary check number to be used consistently on all pages of the single payment, and then the next check (to the next vendor) gets the next sequentail check number.

how did you solve this…?

We did a (simple?) customization in Reports\Cheque_US\chequeNumber and …\fetch to identify whether this was the first page of output for a vendor, use and store/save a new check number if so, and to return the First check number of any subsequent page where the vendor does not change.

is it ChequeDP\fetch method…?
Do you mind sharing the code snippet that you have added…?