OK, all joking aside, this seems a real problem. I thought we were doing all right this year, and a $28k debit to my Absorbed Labor and Overhead account is something I'm going to do only while kicking and screaming.
 
My biggest question is what could have happened so that what was good on Feb 28 is now off by $20k?

I had installed the 022205 update in early April and had strange numbers for end of April. Tried to install the fixed IN-F from the website, but wouldn't work (license issues). I think you may need to be on the 032505 update to use it. Anyhow, I went back to the BKINF.run dated 100404 and IN-F matches my GL.  Also re-ran today with 033105 dates and these match reports I ran before the 022205 update was installed.
 
YMMV

I do re-set the period end close every month, but not so that it would prevent this type of thing.  I run the reports (IN-F value vs GL value) a day or two before the end of the month, and at the end of the month set the close date for one month before, because there are always things that trickle in for at least two weeks after the end of the month. Maybe I'm doing this wrong, but as I recall, the ability to select a previous date in IN-F is only a recent improvement, so it originally had to be done "as of now".
 
The point is that theoretically there shouldn't be any adjustments. I realize that because of the way DBA does stuff there will be some small ones. Ten or twenty dollars here and there, or even a hundred once in a while would not seem unreasonable to me. The fact that there may be a few transactions backdated should have an extremely small effect, I should think.
 
Or tell me I'm all wet, just tell me something.

I will take a very close look at the latest IN-F.  The only thing we changed (supposedly) was add filters for from/thru Primary Vendor and Customer so if you leave them blank, you should get everything but stranger things have happened.

Cross another one off the list...  Thanks David.  For anybody else following this thread, the file is at www.istechsupport.com/dl/inf.zip
 
If anybody continues to have problems using this latest IN-F, please let me know.

My BKINF.RUN.BAD file is dated 3/31/05/12:32 PM. The updated (good) one is 4/4/05/10:53 AM.

The only time I see real differences in my GL account balances and my inventory Value report by GL account is when( and I may be repeating myself):
 Purchases are posted to the wrong asset account either because the part purchased is a N type with the wrong class code or more recently the wrong GL account in the PO line item This past month we had problems with this at the end of the month. (before the last update 11/18 we were having errors with PO's putting the wrong account in the line item but it's been fixed) I find these by doing a detailed trial balance of the asset account in question for RP types and check the purchased parts to make sure they belong to the particular GL asset account I am looking at.
Issues , for one reason or another are done at $0 cost and the value report reflects that they are gone but the GL had no post since the total was $0.  I find these by printing all WO issues for a time period in JC-E and look for issues with $0 cost.
In Assembly ( what we call Accessories asset) and Finished Goods asset accounts, the work order has been finished and shipped but not invoiced ( or the invoice has not been posted).  Or the Finished Good cost posted to the asset account is way different from the average cost it comes out at.
We make adjustments ever month of under $30 dollars, and last month we were off by over $1000 in our Raw Materials Asset account.  It was all about Purchases not going where they should.  Thank goodness that is fixed.
Hope this helps.