Schwab - wrong transaction dates

Agree, the last two days the incorrect date is reflected in the download.

Same problem here (Windows version). I have multiple Schwab accounts. Yesterday (Wednesday, 7/24), ALL downloaded transactions from Schwab were dated one day earlier than their actual execution date. This included transactions from Tuesday (which were dated as Monday) as well as intra-day transactions I executed yesterday (which were dated as Tuesday!). Today the problem continues — downloaded trades from yesterday are dated as of the day before and dividends being paid today have yesterday's date.

During match up, these transactions show as "Near Match" and, when Accepted, the date of the matching transaction is changed to the bogus date. I then must edit each of the accepted transactions to correct the date. (Or I delete each download transaction and manually mark their matching item in the register as "Cleared".)

Also, though probably unrelated to the date issue, I see another odd glitch. The download triggered a pop-up reporting a mismatch in the quantity of a T-Bill that I bought a couple days ago. The download reported a face value quantity that included a fractional share (####.11). Logging into Schwab, however, I see the Position and History data are correct — they show only a whole dollar face value for the bond.

Schwab would do well to borrow from the Quicken code that they inherited from TD Ameritrade. I never had any glitches. One thing that TD downloads did more accurately was to report reinvested dividends as a single "ReinvDiv" transaction (thereby matching my register) as opposed to Schwab, which breaks it into 2 transactions — a dividend and a buy.

The date problem has been reported to Schwab. No idea whether the problem is with them or the intermediary servers, but it would appear to be on Schwab's end since they appear to be the only institution exhibiting the issue.

Regarding "nightly update" relative to Express Web Connect, that is outdated documentation, at least as far as Express Web Connect Plus is concerned. Intermediary servers are now fully capable of intra-day data updates and routinely do so, but that is dependent upon the willingness of each financial services firm to participate. Many still only do nightly updates. Intra-day update support is more common for brokerage accounts than for bank checking/saving accounts (which makes sense, since most banks follow a once-per-end-of-day posting process). J.P. Morgan and Schwab brokerages (and no doubt others) currently support intra-day trade transaction updates via EWC+.

Thanks for your update about the problem having been reported to Schwab. I have been experiencing the same problem since Wednesday. In addition, over the last week, I have occasionally been receiving duplicate transactions from mid-June with the current day's update. Never had any problem like this for more than a decade when it was a TD Ameritrade account.

This morning, I downloaded from Schwab 2 option-related transactions that executed at close of business Friday. These were dated as of today (the next business day) and that is NORMAL date behavior for such transactions. Conclusion: It is possible they have fixed the problem. Standing by…

Still having the problem here! Today's transactions were all dated one day early (7/28). I sent a message center to Schwab customer service explaining the problem and asking that they have their technical people fix it. Fingers crossed.

maeagle

If you haven't already done so, could you report the issue to Schwab. Perhaps, if they receive enough reports about the problem, they will do something to fix it.

I have heard back from Schwab regarding my report of the date problem, which is not very helpful. Schwab's position is that "if any information is coming through incorrectly on Quicken's end, that would need to be discussed with their [Quicken] technical support team even if it is Schwab data." I plan to reach out to Quicken support as soon as I have time to spend on the phone.

Never had a problem like this in over 20 years as a TD Ameritrade client. My main brokerage account is with Morgan Stanley and I use Schwab only for a modest account that I like to try some out some ideas (options, futures, etc) without bothering my advisors at MS. I will have to look at alternatives to Schwab for this account.

Contacting Schwab was worthless…just got the runaround. ..and as I have already stated this "wrong date issue" started around July 23. It is interesting that this happened after the Crowdstrike incident. None of my other accounts outside Schwab are affected.

"I received a response from Schwab technical team. They state that they are sending correct date data to Quicken's intermediary — the transaction dates that appear in account History on Schwab.com. So, they believe the problem is with the intermediary or Quicken."

I believe that this is probably correct. As a test, I downloaded a .csv history file from my Schwab account, and it shows the correct dates. I would guess that this or something similar is being fed to the intermediary, so the corruption must be taking place after the data leaves the Schwab system.

Per Quicken Jasmine's suggestion, I will submit a problem report to Quicken support tomorrow with the requested documentation.

After seeing this for the 1st time I looked at my download from yesterday.

I did the download mid-day. I had transactions from the previous day 30th that showed up as the 29th and a current day transaction 31st dated as the 30th. It does show that dates are dated incorrectly. It also shows that you can download current day transactions.

Sometimes I have to wait for 3 days to get transactions even though I try every day. Once in a while I give up and reset the online connection and it consistently fails on the 1st try to connect all of the accounts and works on the 2nd.

I thought there was something going on with Quicken and now find that there is an intermediary. This sure has been a headache since transferring to Schwab. At least now I know where it is happening.

I have found it has worked better (not perfect) when run after 10:am CDT.