We have recently began using DBA/Evo GL (approx. 9 months) for our main company.  About once every week, we get an out of balance transaction posted to the batch file and we can't process the batch until we delete the duplicate transaction.  It is never more than one transaction and the transaction is always one generated from receiving purchase orders.
 
I have been running another company using DBA/Evo and in the last 31/2 years, never had this happen, but with our primary company, it happens about once every week or two.  Has anyone experienced this and if so, what's causing.
 
Thanks,
 
Dennis

I reviewed the last 4 out of balance txns: 1) 2 purchase items bought to expense, 2) 1 purchase item bought to inventory, and 3) 1 outside process on a service po to a work order.  We are using average costing.

No error messages at time of entry (as best as we can ascertain).  The duplicate is always to the debit side against inventory or expense, never a credit to GL account "Received/Not Invoiced".  I can't tell if it is a first entry of a given day, midddle of day, etc.  At one point in time, this would happen every week, then around Agust 2007, it pretty much stopped.  Now in November 2007, it is again happening about once a week.  As I said earlier, in another company I am running, I have never had this happen.

Cathy,
 
You might be on to something.  When this was happening alot, we started doing our invoicing after end of 1st shift and things seemed to quiet down.  We now have someone new in the accounting department and they may be doing invoicing during the day.  I will follow up on this.
 
thanks,
 
Dennis

In reference to a coma placed in department field, this was happening before using Evo and there was no access to GL account or department.  However, keep those ideas coming.