It has been my experience, that DBA will put the liability back into accounts payable when a check is voided.
 
If one is not going to pay the original invoice, i.e. and you want it removed, you can go back into AP-B and enter the invoice number and select "REVERSE" this entry to clear the invoice from A/P and its aging.
 
Or if the invoice is against a p.o., go into A/P-C and edit the invoice, but inventory may be affected if the subject invoice was against a purchase order for inventory.

Aging looks at BKAPINVT and BKAPCHKH - since these are old invoices, if you want to use the brute force method, those are the tables.

Had the same kinds of problems with VOIDs showing up on the aging.  Seems like DBA handles the G/L transactions fine, but in the files Lynn mentioned it doesn't always get all the correcting done.  For us it only is a problem on a multi-line payments.  It handles line #1 and leaves the rest on the aging.
 
You'll need to go into the files and find the record (line) with the invoices still showing on the aging, one of the columns has an invoice amount and another is either the amount paid or the remaining balance (can't get my tired mind to remember which!)  From there adjust the balance to show it as paid, then it'll drop off your A/P Aging without making entries to G/L that put your detail out of sync with the control account!