While working on this, I've found a few idiosyncracies in the plumbing of GP and I wanted to share them before I forgot.
- The received/not invoiced report is used to balance accrued purchased to the GL. But it's not a true historical report so I've found your better off running it as of today and comparing to today's balances. In spite of that, my numbers kept moving around. Ultimately, I figured out that an Invoice Matching transaction that is still in Work (not posted, still being edited) is treated on the report as if it's complete. So if someone starts and saves an Invoice Match, that receiving is removed from the received/not invoiced report (ie, the subledger is affected WITHOUT a subledger posting) but the transaction is not in the GL until its posted. This creates a difference because the subledger is not really posted but the subledger report is showing as if it were posted and you're stuck!
My fix, was to include the work tables in my comparison. Using only GP tools, you need to make sure that there is no unposted invoice matching when comparing the sub to the GL.
- There is a similar issue in AP. In our case, we see it when we create a Payables Voucher and on the same transaction, pay the voucher with a credit card. The payment appears as a transaction in the subledger, even though the voucher is still in the works. For us, this only presents an issue when processing Amex expense reports so for now, we just live with it for a couple days a month and compare the difference to the Amex payments that have been processed.