PDA

View Full Version : Quicken Problem - PEBKAC or software error?


Mandi
04-17-2003, 11:47 AM
Financial whiz, I am not. We will just state that as a given here at the outset.

I use Quicken for bookeeping functions related to our personal banking. Every month when the checking account statement comes, I use the Reconcile function built into Quicken. It's worked JUST FINE for several years now.

This morning, I got to the end and noticed I didn't come out to a nice and tidy "0.00" balance difference at the end of the process - we were -39.80. Usually that means I didn't click hard enough to effectively clear one or two items, so I scanned through for items that weren't reconciled. I noticed that three or four items remained unreconciled from the past 2 statement periods, which seemed odd. (I mean, we've had a few transactions that NEVER cleared, but this was stuff like an ATM withdrawl, a Wal-Mart purchase - things that hit the bank without fail.)

I pulled those statements, and in fact - they WERE included in last month (and the previous month's) statements. I MUST have properly marked them the past two times I reconcilled because I came up with the proper "0.00" balance difference, and got that nice little "Congrats, your account balanced" splash screen :D LOL both times. (Nothing like a little immediate reinforcement for those of us with mediocre skills.)

The only explanation is that A) either my husband or myself "unreconciled" the item in the register (but it gives a warning not to do that, and we'd both understand that would be a bad thing to do) or B) the software messed it up.

So, upon realizing the problem, I just backed out of the new reconcilation this morning - just cancelled it altogether - and went and reconciled those old items by hand. Then I started the reconcile process again, from the begining. However, it took my "starting balance" (last month's statement balance) and altered it by the amounts I'd hand reconciled. I understand why it thinks it had to do this, but I don't know how else to fix the error %) !

If you hung in here this long, congratulations! So, here's my actual questions:

1) Would deleting the problematic transactions (the ones I know cleared one of the previous statement periods, but then got "unreconciled") altogether - since I know my balance reflects them and I can't reconcile them TWICE - fix the problem?

2) Any thoughts on why Quicken would do this after years of flawless operation?
******
PS, I read "PEBKAC" here years ago as way to describe user error: Problem Exists Between Keyboard and Chair . . .

Randall
04-17-2003, 10:00 PM
Mandi, I have no experience with Quicken per se, but I've run into problems like that in its big brother QuickBooks. After several frustrating go-rounds, I believe I ended up unclearing every transaction since the last clean reconciliation and started over. I don't think you need to delete the offending transactions. That may not even help.

I can't tell you why they became uncleared in the first place -- mine were self-inflicted -- but I do know that once these programs get it in their heads that something's been cleared, good luck convincing them otherwise.

Randall

Syneryder
04-18-2003, 12:42 AM
Which version of Quicken are you using Mandi? I'm very familiar with Quicken Deluxe 7.5 (I absolutely love my Quicken, couldn't live without it) but perhaps newer versions have different features I'm not aware of.

I'd agree with Randall, un-reconcile all the transactions from this month's statement (clicky clicky the little R's until they go away). If you're *sure* that that you reconciled the items from last months statement, just keep clicking until you get the little R back on those items. Then try reconciling this month again.

Otherwise, you could try un-reconciling all this month and last month's transactions, and reconciling the two months at once. Take the opening balance from your earlier statement, and the closing balance from the latter statement.

Here's hoping my advice doesn't make a mess of your finances :D

ryount
04-18-2003, 07:40 AM
Originally posted by Randall:
Mandi, I have no experience with Quicken per se, but I've run into problems like that in its big brother QuickBooks.

Same problem here with Quickbooks. Sometimes it doesn't mark the service charge or interest for the current month as cleared. I generally hate the way they do a bank rec anyway. It shouldn't show future deposits or checks written after the bank statement date.

Randall
04-18-2003, 05:34 PM
My sentiments exactly. I work part-time for an accountant, and I like most things about QuickBooks (just as I hate most things about the "professional" accounting software we use for some of our clients). But the bank rec could use some work.

Randall

Syneryder
04-19-2003, 07:38 AM
Can I just ask what versions of Quicken & Quickbooks everyone uses? 'Cos I've been running my copy since mid-2000, and it's one of the most solid programs I've ever used - haven't found any bugs at all. Has it gone bad in later editions?

ryount
04-19-2003, 09:28 AM
How about a complete rundown... We have 1 condo association on Quickbooks 2000 and 7 of them on DAC Easy v9 (DOS). Our hotel and advertising companies run on MS Great Plains Dynamics v7. We have a merchandising company that uses Quickbooks 99, but I don't really have any involvement with them. They have really outgrown Quickbooks though.

I wish I could say Dynamics, the "professional" software was that much better than Quickbooks. The main thing we get out of it is reliability and scalability. Unfortunately there really isn't much middle priced software between Quickbooks, Peachtree, etc. and other products. MS has quietly bought up quite a bit of competition.

Randall
04-19-2003, 03:33 PM
We have clients running running QuickBooks 99 through 2003. There's a huge jump in resource requirements with QB 2000, and the UI has seen some changes the past few years. People who used the old tax tables for payroll got forced into signing up for Intuit's payroll service (starting with 2000, I think), which wasn't nice. And the automatic update feature in QB 2000 was so much of a CPU hog in NT that I had to physically disable it on some machines. They fixed that problem in 2001.

If you have a decent PC and don't need payroll, you won't see any real disadvantage to the newer versions -- but there haven't been any truly compelling new features, either. I know someone who's happily running QB 4.0 on a WinXP machine. I think that version goes back to 1996.

On the other hand, the new Accountant's Edition they started in 2002 finally addresses some of the limitations on our side of the equation, so we're actively encouraging our clients to upgrade for the first time in several years. Anything that helps us do our job helps our clients.

As for Quicken, PCWorld's review (http://www.pcworld.com/reviews/article/0,aid,104318,00.asp) of Quicken 2003 said to skip it altogether.

Randall

Mandi
04-19-2003, 04:48 PM
We're using Quicken 98 - we were using Quicken ver 0.003 (well, not really - but it was old!!) right up until Jan 1, 2000 when I realized it wasn't Y2K compliant, LOL - (the Intuit site let you upgrade to Y2K compliant Quicken 98 for free.)

I really like the idea about clearing the reconcilliations back a few statements, prior to where the problems exist, I'm gonna try that. Thanks 8} . . . I'll be back from Scary Financial Land with a field report soon . . .

Mandi
04-22-2003, 04:44 PM
I have just spent the last 90 minutes performing this very exciting task :rolleyes:, and came out with a much smaller difference. I just let Quicken "adjust" the balance, and we'll see if we come out even next month. Fingers crossed . . . I strongly suspect a few of the long-term uncleared items were actually credit card purchases rather than cash card (checking acct.) purchases - we have to be careful, as the cards are nearly identical! I actually used my little label maker and marked them clearly. I think I need to do the same for the other card user in my house, who shall go unnamed but clearly made the above purchases, LOL :D (I was out of town!) . . .

Thanks for the suggestions, everyone!