Voiding Check in Current Period; QB Seeing it as Prior Period

 I agree that answering no takes care of that one particular transaction, but my question is why only this particular clients data file gets this message in the first place while voiding a check from a current period..  QB normally offers to do this only if a check from a closed prior period is being voided.  I have not seen this on any of my other clients files, nor even my own QB file when working in the current period.

Thanks for responding.

 Are all of your other clients using qb 2012?

Do they have a different tax year/fiscal year?  

do they have a closing date/password set up?

 Thanks for sticking with me on this one.

My clients don't alll run 2012.  It's a mixture of 2009-2012, but probably about a quarter to a third run 2012.  

A couple have different tax/fiscal year, but the vast majority (including the one I'm asking about) are jan 1-dec 31.

Some have password/closing date set up; some don't.  

The one with the problem is a fairly uncomplicated setup. It's cash basis; no credit card acceptance; no inventory; no QB payroll.  They process about 150-200 bank transactions a week which is more than most of my clients; they download their bank transactions weekly and match to their checking account.  

They don't usually use bill entry, usually preferring to just write a check (although I should probably double check that to see if this qb message shows for both bill  paymen checks and write checks checks  .  Should probably also try to void a deposit to see what happens).    Any thoughts?

Any ideas?

 The suggestion for creating a journal entry is new to qb 2012, and maybe 2011 years, so that may help explain some of the differences between companies.

After I wrote I checked it in my 2012, and you are correct that it doesn't ask unless it is a different year, so I'm not sure what is going on with that.  

I would make a backup, and try to void a different check in the current year and see what happens. 

Hi,

Just a followup.  I called the QB ProAdvisor Hotline yesterday.  Turns out (no surprise) that it's a bug in the software.  The Advisor wrote up and submitted a bug report and it will be fixed.

Interestingly, though, it only seems to be a problem if you're voiding a check that's posted to an expense account.  If you're voiding a check to a balance sheet account, it's fine.  If you're voiding a bill payment check, it's fine.  If you're voiding a deposit against an income account, it's fine.  Robert, (the hotline person) and I spent some time experimenting with various scenarios. The existence or absence of a closing date doesn't seem to make a difference.

I guess I'd never seen it before because most of my other clients use Accounts Payable and would void a bill payment check.  And in my own QB file, the only time I had occasion to void a check, it was written against a current liability account.  Interesting!

Thanks for pitching in to get this resolved.

Here's my cynical take on how to stop stupid messages that the software generates because of a bug:  Isn't there a pop-up window about "stop messages like this in the future?"  And can't you just check off that "stop-it" box?