Did it balance for some period in the past?

If you have an amount that you are off continually,  it sounds like you have a permanent difference which would mean something was posted to the g/l and not to the bank rec or vice versa.   You can check for this by comparing the g/l balance as far out into the future as you can to the amount in bank code maintenance.

If have a technique that I posted for finding timing differences you mentioned which I shared on these forums a long time ago but I can't find it at the moment.   I've run out of time,  but I will try to post it for you over the weekend.   It uses a/p payment explorer to automatically identify mismatched check and g/l posting dates.

It looks like we have a couple permanent differences but quite small so those we can get rid of with a journal entry.  I agree that these must have been posted as a general journal entry or something when it should have been done as a transaction journal entry or done in the a/p or a/r module.

I did some more research today on the variances that are moving up and down each month and I confirmed my suspicion that some checks are being posted with check dates in one month and posting dates in another during month end time.  Most of them are due to check reversals because the original check date shows up and my staff were never instructed by the previous manager to change this check date to match the posting date.  I have done this now so these temporary timing variances should get all caught up this month and we shouldn't have this problem moving forward.  (let's hope!)

Thanks for everyone's input!  This site is a really great resource!

You can  use the Business Insights Explorer – Vendor Payments View to fnd checks with mismatched dates.  Create a calculated field that  will be non-zero if the dates are mismatched.

The calculated field (MonthYearTran) formula in the above example is as follows:

{fn MONTH("AP_CheckHistoryHeader"."TransactionDate")} + 100 * {fn YEAR("AP_CheckHistoryHeader"."TransactionDate")} - (

{fn MONTH("AP_CheckHistoryHeader"."CheckDate")} + 100 * {fn YEAR("AP_CheckHistoryHeader"."CheckDate")})

Then filter for this new column having a value not equal to 0.