PDA

View Full Version : A/P default incorrect


bkpr913
06-19-2002, 07:16 AM
This is a real puzzle. For some reason, Peachtree intermittently changed the A/P default account to an expense account on many entries. Not always the same expense account, either. This results in credits to expense accounts instead of the Accounts Payable default account, thus throwing off my statements. I can't figure out when and how this is happening because, every time I enter a purchase, the correct default account shows on the screen. I've had to delete the paid invoice, go back and correct the A/P default, and then pay it again.

Anybody else experience this???

bluegal
06-19-2002, 11:05 AM
I had some strange things happen when I marked some jobs "inactive" when there were still open transactions for them. Peachtree threw the transactions into the first available account in my chart of accounts.

bkpr913
06-19-2002, 11:25 AM
You might have something there! When I first started working here, we changed some G/L accounts to "inactive", moved some transactions around, deleted some G/L accounts, etc. As long as it's caused by human error, I can deal with it. Thanks for the reply.

dringstrom
06-19-2002, 05:25 PM
I've had two clients experience this recently. I haven't determined the cause yet, though. You corrected the problem in the proper manner. With three separate, unrelated occurrences, this is starting to look like a potential bug.

bkpr913
06-20-2002, 05:12 AM
So happy to know I'm not imagining this. Keep us posted, David.

TheWolf
06-20-2002, 03:21 PM
Not sure how that can happen as that field is a "remember last field". If it changes then someone is changing it. Once changed it will stay to what you changed to until you change it again and post.

dringstrom
06-20-2002, 03:31 PM
I agree that's how it's supposed to work, but it's rather odd how in two situations, with only one experienced Peachtree user in each situation, that random transactions would have the default AP account change. I initially wrote it off to a user error, but in each case, it was a single transaction, not a string of transactions. In any case, I don't have anything concrete on this yet...it's just starting to look suspicuous. Plus, BKPR's experience makes 3.