Schwab - wrong transaction dates

I can also confirm that:
a) date issue: this 'date problem' has shown up for a few days now. I have to manually correct the date while accepting into the register.

b) download frequency topic (brought up above, but unrelated to date issue): with Schwab (using EWC+), I can download intra-day, BUT ONLY one or two times, NOT MORE. Once I download intra-day, I have to wait a few hours before l can successfully do it again. (I used to be able to download any number of times successfully from Schwab in previous years, probably before EWC/EWC+). With Fidelity brokerage (DC), I get the data only the next day.

@JPG, the data is not in the OFX file, but in the Cloud Sync log file. (I am guessing it is this way for all EWC+ connections.)

I checked the Cloud Sync data file for the Schwab transactions. They show the incorrect date: For example: For a transaction that occurred on Aug. 1, it shows "postedOn":"2024-07-31" instead of "postedOn":"2024-08-01".

Could be the CrowdStrike issue related - the time frame seems to coincide roughly. And Schwab had severe issues during that outage.

With these multi-party data transfer issues, the customer gets caught between all the finger pointing between parties.

At this time, I think it is more likely that it is a Schwab issue - the fact that their web site shows correct dates means their base transaction data is correct, but it does not indicate it is not a Schwab data transfer issue IMO. Other code/servers within Schwab are likely involved in the data transfer.

I have created a problem report with Schwab.

I'll just confirm that my observations/conclusions are the same as @veegee:

• Intra-day downloads are supported but seem to be limited in frequency (likely to prevent a possible denial-of-service problem on Schwab's servers). I typically download once in the morning and once after market close, and I see all of that day's transactions, including ones that may have occurred minutes before downloading.
• My Cloud Sync Log also shows that the "txnOn" and "postedOn" dates that are included with each transaction are incorrect (specifically, they have the prior day's date).

I also agree that this issue is likely on Schwab's side as it seems unlikely the EWC+ servers (which are run by Intuit, I believe) are messing this up for only a single data source. Hopefully, the three parties involved (Quicken, Intuit, Schwab) can get together and quickly determine where in the process the data is being corrupted.

@Rich Gaughan , please submit a report to Schwab technical support if you can. (Don't forget to mention the fact that the timeframe coincides with the CrowdStrike outage.)

@Bill44 Agree this seems to be getting no / little traction or attention. I and others have submitted the problem as requested via "in-Quicken" report a problem tool. I wonder if it's being underreported as many people might just hit "accept" transactions and not notice or, as one previous commenter mentioned, thinks "it doesn't matter that much". Would be nice to not have to manually change EVERY SINGLE transaction. I am patient with quicken about getting things fixed, but would love to know that it's being looked into and they're not just pointing to Schwab.

Just confirming I have the same issue and it started on 7/24. Crossing fingers for a fix from someone… Now that I have detected the problem I can fix the new transactions as they occur. BTW - also getting old transactions previously downloaded with new ones, but not with every new download…

This has been happening to me for at least two weeks; every txn downloaded from Schwab to Quicken Windows Desktop via One-Step Update shows a date one day earlier than correct (as verified by comparing the same transaction in Schwab.com, nightly confirmation emails, and StreetSmart Edge, which all show the correct date). No non-Schwab accounts (credit card and bank accounts) have the same problem. And I too have gotten the same response from Schwab tech support: "We're sending out the correct info, the problem has to be on Quicken's end; call Quicken."

Hard to find info on the place and path of the files that move from Schwab to Quicken. I probed around some files that the HELP menu report itme asks you to generate. I do not have a definitive opinion, not sure how this is "supposed" to process, but I saw dates written in UTC format (I know that can happen is transferring data sets, all times converted to meridian, then the receiver has to then convert it back to its own time zone.

If there is a conversion going on, the problem could be on Quicken side. But why just Schwab? Is the Web Connect protocol not consistent between banking source accounts on how they make web connect datasets available? We layman users here don'y have enough to go on to solve the problem.

If this forum is supported by a Moderator, which I rarely see, we have to hope that person can take these reports, and get to the debugging team.

Something they or Schwab did in a recent patch, broke the date handling. I can't make sense how CrowdStrike scare has anything to do with it.

BUT THIS IS A TERREBILY ANNOYING problem. Manually updating the dates in Investments is extremely cumbersome. After fetching 20 Options transactions - it is 15 seconds each to alter the dates.

PLEASE MODERATOR - MAKE YOUR SELF KNOWN, and REPORT WHERE THIS IS GOING to be handled.

Submitted another report to Quicken with CloudSyncLog data highlighted… showing the error in the data from the 'Quicken server'. (Whose server? Quicken's? Intuit's? And did the server get the wrong data from Schwab or messed up delivering it? All good questions I do not know the answer to.)

Hi Janean, Any update on this issue? As you can see there is an increasing number of users with this problem!

I too have been having this problem for two weeks or so and it is very annoying. I have been with Schwab and Quicken for over 20 years and neve had a problem like this. I am sure all users have the problem but most probably aren't paying that close of attention to notice. I do 50+ trades per week and fixing them manually is really frustrating.

Quicken Janean,

Sorry, but how does uploading screen shots help you? IT IS CLEAR FROM ALL THE COMPLAINTS. The register has "YESTERDAY's" transaction date right after you sync web connect. Then we are all painstakingly, alter each date manually to "TODAY."

The troubleshooting team at Quicken needs to test and replicate this problem. They don't need a picture!!

try harder?

As requested by Quicken Janean earlier today, I just uploaded a problem report in Quicken with screenshots.

@Quicken Janean

And so have I. Many problem reports should be there now.