# AP Invoices - Credited/Paid but still showing in Aged Payables Report **Category:** [Epicor ERP 10](https://www.epiusers.help/c/e10/5) **Created:** 2016-11-10 04:04 UTC **Views:** 4863 **Replies:** 9 **URL:** https://www.epiusers.help/t/ap-invoices-credited-paid-but-still-showing-in-aged-payables-report/36176 --- ## Post #1 by @David Hey all, A bit of a different area for me! :slight_smile: Finally not talking about quoting haha :stuck_out_tongue: We have an issue where our AP personnel have credited/paid an invoice, and it's been all matched off, but they are still appearing in the Aged Payables report. Is there some process I can run that will go through all the invoices, check if the Doc Pay Amount equals the Doc Invoice Amount, and close the invoice if this has been completed? **EDIT: Just read over the question and it could be misunderstood. I see that the invoices in question are indeed paid (DocPayAmounts equals DocInvoiceAmt) yet the OpenPayable is still true. Posted & GLPosted for those that are interested is also True.** **EDIT 2: I've just checked and we have a few records like this. Is this an issue? Not 100% sure what I should be checking here :wink:** **EDIT 3: I think there will be more edits than original information here! Different suppliers, different post dates, different batches, different people posting the invoices, different amounts, different currencies, different banks - nothing stands out among these as 'similar' or leading to believe to be the causation.** Any advice is greatly appreciated! Cheers, Dave. --- ## Post #2 by @MikeLowe Is the full balance outstanding or pennies? Are you using multi-currency? Mike --- ## Post #3 by @David @MikeLowe It's the full balance. For example, I have a debit memo for $300.00 in a foreign currency, then I have an invoice for $300.00 in the foreign currency that I apply to it - when I try to apply the invoices, it comes back as 'Transaction does not balance'. It then goes to the RJ. Understandably the foreign currency rates have changed between the two dates, but for whatever reason (the part I don't quite understand), the debit amount matches the book debit amount after conversion, and the difference in currency revaluation is credited, but it is debited from the book debit amount meaning we end up with the book debit amount equaling the original book debit amount PLUS the book debit amount for the currency revaluation; meaning the original book debit amount for the invoice is incorrect because it is showing the value at the later conversion rate instead of the earlier conversion rate, and debiting the extra conversion loss. I hope that rambling makes an ounce of sense. It's difficult to explain normally, now it's compounded with the fact that I have no real understanding of why it's working like this! --- ## Post #4 by @MikeLowe It doesn’t sound like this is the problem but want to confirm that your staff are indeed running the currency revaluation process and have all the appropriate rates installed. Mike --- ## Post #5 by @David Yeap, currency revaluation process is being run and all the current rates are in the system. I've sent the RJ list to the team and they've had a look - the BookDebitAmount and BookCreditAmount are not balancing, therefore we are getting the 'Transaction does not balance' issue - which makes sense. However they are at a loss as to how the invoice could be posted if it didn't balance in the first place. I think I need to investigate this one a bit further and see what is happening (and understand it!) --- ## Post #6 by @David So far I've found this occurring in the PE Log Viewer: "Unable to get account GLControlCode" for the debit memo. The applied invoice seems to be hitting the correct GL Controls though. Interestingly, if I create a new Debit Memo, post it, then try to apply an invoice to it, I get the following: "Getting account from GL Control AP Apply Debit Memo--Line--Invoice--GL Control Type AP Invoice for context Payables book MAIN GLControlCode Reusable Ref GLRef APInvHed|VendorNum¯**AppliedInvoiceNum** Unable to get account GLControlCode Reusable Ref GLRef APInvHed|VendorNum¯**AppliedInvoiceNum**" Looking in the GL Control setup, I can find the AP Account GL Control Type, and find the Payables Account Context - all have the GL Accounts set. Losing my mind slowly but surely :slight_smile: --- ## Post #7 by @MiguelS I am not sure about the other stuff, but in E9 I was given this file. CVAPHDRCM.r to clear it. It worked most of the time. --- ## Post #8 by @David Hmm, I am not too sure what the CVAPHDRCM.r would be equivalent to (if there is a process in E10 somewhere that replicates it) - any chance you have that file lying around (as long as it doesn't contain any sensitive info)? I've just tried recreating the exact same invoice and debit memo and that worked flawlessly - so it's definitely not related to the GL - maybe a corrupt invoice? --- ## Post #9 by @David Alrighty, getting closer to isolating the issue. During the "Apply Debit Memo/Correction Invoice" process, it 0's out the UnpostedBal/DocUnpostedBal, but **DOES NOT** effect the InvoiceBal/DocInvoiceBal where a normally processed invoice **DOES**. Maybe this info will make more sense - note TEST* is the one that I've duplicated the invoices (just changed amounts). Any ideas? --- ## Post #10 by @David Hey Miguel, Seems that CVAPHDRCM is the fix that Epicor supply! They've identified the issue and are working on it now :slight_smile: Thanks very much for all your help everyone :slight_smile: Cheers, Dave. --- **Canonical:** https://www.epiusers.help/t/ap-invoices-credited-paid-but-still-showing-in-aged-payables-report/36176 **Original content:** https://www.epiusers.help/t/ap-invoices-credited-paid-but-still-showing-in-aged-payables-report/36176