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.
> can quicken not handle five-digit check #s?
Yes, Quicken can handle five-digit check #s.
But even if Quicken could not,
I would have expected to see 1000 in Quicken (truncating the final zero).
Or 0000 (dropping the leading 1).
It's hard to imagine how whatever actual check# followed 9999
could have become 5000 under any legitimate process designed to deal
with numbers that were "too large" to handle.
More importantly,
why do you assume that Quicken is the primary cause of what you're seeing?
Have you asked your bill payer what they do after their
billpay check numbers reach 9999?
> I'm not sure what to do.
>
> I rarely use paper checks. The last I used in the previous numbering was
> 1697 on 2/2/2001! The next check I wrote was #5001 on 12/6/2023,
> And my online has now collided with it.
Is there any way I can fix this problem??
That depends.
First I think it might help if you supplied some additional information.
- Financial institution (bill payer) name?
- Payment account type?
- Quicken "Connection Method"
("Online Services" tab of the "Edit Account Details" dialog for the Q account)?
The first thing I suggest you do is to save the results of the download containing
the problematic data.
I would create a new temporary backup folder and use Windows to copy your .QDF file there.
I would also (in your current Quicken file) go to Help > Contact Support > Log files, open the
"OFX Log" and use the "Save as" button to create a text file of the OFX Log contents ... in the same
new temporary folder where you made the Windows copy of your log file.