Re: Dupliicate check #s

On Saturday, May 6, 2023 at 12:52:06 PM UTC-5, Bernie Cosell wrote:
> Bernie Cosell wrote: 
> 
> } John Pollard wrote: 
> } 
> } } On Saturday, May 6, 2023 at 11:42:04?AM UTC-5, Bernie Cosell wrote: 
> } } > r49.29 -- I use online billpay a lot and a funny thing happened: after it 
> } } > made it to 9999 it seems to have wrapped to 5000 and is now colliding 
> } } > with my *actual* checks that began at 5000. 

> } } Doesn't sound like "wrapping" to me: 
> } } I would have expected the next check# 
> } } after 9999 to be 1, if the numbers were "wrapping". 
> } } Otherwise I would have expected the next check# to be 10,000. 

> } What I've learned is that this isn't a quicken matter, but a *bank* matter. 
> } Apparently with online billpay the *bank* issues the check number and my 
> } @#$%@#$ bank started numbering at 9000 and when it got to 9999 they then 
> } jumped to 5000, which is where my paper checks are. 

> } I just called my bank and got the online-quicken check # reset to 1000. 

So that's not going to conflict with any of your old check numbers?

[Earlier you said, 
"The last I used in the previous numbering was 1697 on 2/2/2001!"  
I assumed that meant you had probably used check numbers much lower
than 1000.]

Or maybe you did not record those old check transactions in Quicken.

> } I'll find out in a while if that worked, but that should give me a long 
> } time before there's trouble.

> Just for the record, this is wells-fargo... 
> if you're a w-f customer be careful if you get near 9999

I assumed it was likely the billpayer's issue: 
in my experience it is the billpayer who controls 
the billpay check numbers. 
I was going to suggest having the billpayer change 
their "next" check number, once it was clear it was their 
issue.

The alternative might have been to close your old account, then 
open a new account where you could specify your starting check#.