We are closing 2012 and after reviewing the reports, have discovered that one of our AP bookkeepers entered, posted and cut the check for a batch in an open AP period but a closed GL period. So the transaction is fine on the AP side but missing from the GL side.
Ideas on how we can correct this?
We are still on GP 10.0.
Thanks in advance,
The AP check batch must be stuck in posting because it would ahve errors. If you do not see them go to Batch Recovery. You shoud then see them in Transactions->Purchasing->Process Checks.
Richard E. Wheeler 2013 MVP
MS Dynamics GP Support
www.rbsolutions.com Revered Business Solutions Ballston Lake, NY 518-877-0763 x10
As Richard said, the AP batch should be stuck in Batch Recovery. It's actually the GL batch that is stuck, the AP batch posted. The way to correct it is to 'free' it from Batch Recovery (Administration | Routines | Batch Recovery), open the fiscal period and then post the GL transaction.
You can even do this after you've closed the GL so long as you allow posting to history in the GL Setup window (it's allowed by default).
Here's what it should look like in Batch Recovery:
Leslie Vail, CPA, MVP, MCT, MCITP, MCP, MCITSASCI, Inc. * PO Box 600965 * Dallas, TX 75360 * 972-814-8550 * email@example.com
Thank you both so much!
I looked at the facility and the batch wasn't in batch recovery. Any other ideas?
I appreciate the help!!!
Do you see an unposted ledger entry? If not, do a check book inquiry looking for this check. Then look at the post date of the check and see if you can then find it in the ledger. Make sure it would have hit AP. If it did, then it is possible that a disconnect happened here. You could simply correct it be entering a ledger entry. Something else you go try would be to perform a backup and then run check links on the payables and financial series to see if the batch reappears. It sounds like this was a check not in a batch so you cannot reprint the posting journal. If you do post a journal entry make sure the posting period is open.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13