Quicken Community is moving to Single Sign On! Starting 1/22/21, you'll sign in to the community with your Quicken ID. For more information: http://bit.ly/CommunitySSO
Error sending Check Pay payment: QCS-0400

I tried to send the following Check Pay payment, and I got the error "Could not initiate payment ... Date to send cannot be in the past (Code: QCS-0400)." Perhaps someone's getting confused about time zones:


Changing the "arrive by" date to 12/8 from 12/7 worked around this bug, but users shouldn't have to do that.


Changing the "arrive by" date to 12/8 from 12/7 worked around this bug, but users shouldn't have to do that.
0
This discussion has been closed.
Answers
See this webpage for more information on lead time, the time it takes to print and mail a check and allow for it to be processed by the biller before the due date.
Based on what I've read here in the Community, you should allow at least 10 calendar days of lead time to allow for delays.
Alternatively, if the biller offers payment by direct debit (or APS, PAC Draft, etc.) from your checking account or a credit card, I would go that route. Avoids mailing and handling delays resulting in late fees.
Except that last night, it said "will be sent on 11/29/2020".
Quicken should pick an initial arrive-by date that won't cause an obscure, obviously incorrect error message, "Date to send cannot be in the past". (The date-to-send was 11/29, which is not "in the past" on 11/29.)
Premier on Windows 10
Agreed, as I wrote in my first post.
I set a payment for today, Quicken adjusted it to 12/10 (4 business days starting Monday), and my bank kicked it back. I changed the date to 12/11 to make it 5 business days not counting today. Once I corrected the "too early to process" problem, my wonderful little problem of having a Send Payments button in the Things to Do panel with no payments to send has come back. I think I have finally figured out what was causing that, but have yet to figure out a solution after correcting the payments so they will go or updating them to synchronize with scheduled payments at the bank. I sent two payments, both requiring check payment. One was dated for 12/14, and the other for 12/10, as described above. The one dated for 12/14 went through, but the one for 12/10 created the error, and the error message indicated both were rejected. NOT TRUE. I checked, and the 12/14 payment is actually scheduled. After correcting the date on the payment for 12/10, Quicken marked it as sent, however, because it errored out from the bank, Quicken did not change the status on an otherwise unrelated successful transaction. The only relationship between the two payments is the instructions were sent in the same request to the bank. Quicken left the status on the payment as "Send", albeit, the bank had actually received and processed the request. I ran the update again, which showed no transactions to send (in contrast to saying I did in the Things to Do panel) which I expected, and it now refuses to allow me to check payment status for the one payment that still says Send. It's sent, already. Why can't I check status with my bank and match upcoming payments with what I have in Quicken? THAT I think is the disconnect between Quicken and the banks direct connect systems, and there is no incentive for Quicken to fix it. Think about it. If direct connect works perfectly with every bank, who needs Quicken Bill Pay or online aggregation of their banking information through Quicken's servers, which is a pay service (yes, part of that annual fee for having Quicken now). If no one needs it, no one pays for it, right? Aside from the obvious conspiratorial comments, I'd just like a simpler method to correct synchronization for upcoming payments. What I normally have to do to make the Send button go away and change the payment status to Sent is:
PLAN A:
1. Go to my bank's website, and delete the offending upcoming payment so that I won't have a duplicate. My bank's software most generously prevents me from sending duplicate payments. Dunno if each transaction uses a checksum identifier or what, but that starts a whole other avalanche of transaction issues. Strangely enough, though, I CAN duplicate the payment on their website. Go figger.
2. Go back to Quicken, DELETE (not VOID) the payment, and run a One-Step Update. This can be done selectively for the bank with the issue, but will still update all accounts at that bank. That I know of, there is no way to update only one account at any bank where multiple accounts are held. No instruction is sent for the payment that still shows as SEND, so no new payment generated at the bank, and the payment cancellation notice comes back from the bank.
3. Manually re-enter the payment reminder, generating a new instruction to Send through One-Step.
4. Pray I've waited long enough for the bank to update the scheduled payments, and re-send the request by running One-Step again.
PLAN B:
1. VOID the payment in Quicken. This won't send anything to the bank because Quicken seems to think it still needs to send the original instruction (that it is not generating) to the bank.
2. Go to the bank's website. Cancel the offending scheduled payment that was sent from Quicken, and then re-enter it on the website.
3. Run One-Step again, and I then get an update from the bank with the scheduled payment to replace the voided transaction.
4. Delete the voided transaction which Quicken still wants to generate a Send Payment request.
ONLY if the desynchronized scheduled payment is deleted at the bank and in Quicken will Quicken finally give up trying to generate a send message. I fully recommend running a file SUPER Validate and Repair after doing this too. Just hold the Shift key when you poke File/File Operations/Validate.
If all goes as intended, this normally gets rid of the annoying unnecessary Send button and gets the cute little grey envelope in the first column of the register view fixed and the status set to Sent. There seems to be an awful lot of status checking going on, yet, not enough to fix what Quicken screwed up to start with. Either of these processes are a complete PITA. The normal Reset Online Connection method does bugger all to fix this, and I've found that the Reset Online Connection is a real good way to get locked out of your account if the bank detects something hinky (or thinks it has) with multiple login attempts.
Quicken REALLY should change the name of One-Step. It's ALWAYS a minimum of two steps when I use it. Click to initiate that one step, and then click again to confirm the instructions. I call that two steps.
Rant over. Hope someone finds something useful in this.