nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Synchrony (aka Synchrappy) Credit Card for Amazon, Giving Wrong Year for Transactions

James J

This happened last year, maybe the year before last also.

We made a few purchases at the end of December 2024 that Quicken was not auto-matching and instead was showing them as "new" transactions.

But check out the date. Its December of THIS year. I opened the downloaded QFX in Notepad and sure enough, Synchrony is once again messing up the dates.

This is just a public service announcement.

Find more posts tagged with

Comments

splasher

What dates does Synchrony show on their website? It may not be Synchrony's fault since Quicken's aggregator (Intuit) might be messing up.

I'd download a Web Connect (.QFX) file from the Synchrony website and look at its contents to see what year is in the file that is generated by them, not the aggregator.

Based on what you find, you know who to complain to.

James J

https://community.quicken.com/discussion/comment/20469288#Comment_20469288

I downloaded the QFX from Synchrony and looked at it in Notepad. The dates in the QFX are December 2025 so it appears to be a Synchrony problem. I had this exact problem with them in previous years where their system changes the dates on transactions at the end of the year to be in the future. So at first glance it looks like Quicken isn't working but in fact it's the credit card's system that has sloppy programming.

I've also had problems with Synchrony reporting dates in their QFX using an incorrect format. I'd have to look up my notes I made on fixing the problem to give details. You just have to download the QFX and edit it in Notepad, then import it. That will work for the current issue as well - but now that is January I think Synchrony's system will now correctly be reporting the date.