leading zeros on check numbers

I use Meriwest Credit Union. For the past few months, downloading new transactions now has check numbers coming in with 6 leading zeros. This results in duplication, because I've manually entered the check number (XXXX) and payee, and now the downloaded transaction shows up as check number 000000XXXX. I can manually drag one onto the other, but then that results in the check number still having the useless leading zeros. What do I do? This isn't happening on other accounts that I write checks against, just this one.
Comments
-
Hello @KRD,
Thanks for reaching out to bring this issue to our attention!
To better assist you, could you please provide the following details?
- Where is your Quicken data file stored? Is it on your local hard drive or a cloud-based/external drive (e.g.: iCloud, DropBox, USB, etc.)?
- You said this isn't happening on any other accounts that you write checks from—are the other accounts with the same credit union as will or with different financial institutions?
- Were there any significant changes to your system or software before the issue began (updates, new installations, etc.)?
- Could you please provide your log file via Problem Report so we can dig a little deeper into this? You can do so by navigating to Help > Report a problem.
Your answers will help us diagnose the issue more effectively.
Looking forward to your response!
-Quicken Anja
Make sure to sign up for the email digest to see a round up of your top posts.0 -
There have been a few discussions in the past, all Mac - related, on this subject, but I can't figure out if there ever was a solution that was implemented. Just search the Community for "leading zero".
Once @KRD submits the log files for review, perhaps the programmers can find a global solution to eliminate leading zeros from downloaded check numbers.
0 -
I think this sort of thing is always dependent on how each financial institution encodes its data downloads. My bank at one point didn't send any check numbers; then they seemed to fix it. But currently, it sends "Check #1234" as the Payee name and puts nothing in the check number field.
Quicken Mac Subscription • Quicken user since 19930 -
For correct results, your bank should put the check number into both Check# field and Payee Name. Most other banks do it this way.
No leading zeros.
And no bogus number "55" to indicate ACH debits as discussed here.0 -
Why would I want the check number in the payee field? The check has a payee & that's what I expect it to say.
0 -
When a paper check is processed by the bank, is the Payee Name part of the computer-readable information?
No, it isn't. All the bank has is the check number from the MICR code line (and the routing and account number).If you have manually recorded a transaction at the time you wrote the check, then and only then will you have a Payee Name (and proper category) stored in Quicken to match with the downloaded transaction.
Exception to the rule: The biller converted the paper check to an ACH debit transaction and sent that thru the Federal Banking System. At that point in time, you will have the biller's name as the Payee Name, but you may not have a check number …
0 -
For correct results, your bank should put the check number into both Check# field and Payee Name.
Actually, I'm getting a downloaded check with a Payee name which lists the check number twice:
CHECK #1488 1488
Can we agree this is incorrect — by any standard? 😉
And it is not inserting that check number into the check number field, which is also wrong.
Quicken Mac Subscription • Quicken user since 19930
Categories
- All Categories
- 7 Product Ideas
- 27 Announcements
- 195 Alerts, Online Banking & Known Product Issues
- 18 Product Alerts
- 734 Welcome to the Community!
- 607 Before you Buy
- 1.1K Product Ideas
- 50.1K Quicken Classic for Windows
- 15.5K Quicken Classic for Mac
- 988 Quicken Mobile
- 778 Quicken on the Web
- 75 Quicken LifeHub