Synchrony CSV to QBO Converter: Convert a Synchrony Card CSV to QuickBooks

Not reliably. Synchrony does not support OFX Direct Connect, so QuickBooks and Quicken cannot pull Synchrony transactions automatically the way they do for a bank with a live feed. Some Synchrony cards can be added through Intuit's Express Web Connect aggregation, but those connections frequently drop, duplicate, or miss pending charges. Exporting the activity yourself and importing a .qbo file is the method that does not break month to month.

Sometimes, and it is inconsistent. Synchrony runs more than one version of its card website, and the older account pages included an Export button with CSV, Excel, Quicken (.qfx), and QuickBooks (.qbo) options, while the redesigned pages on many retail cards now offer only CSV, Excel, or a PDF statement. If your card no longer shows a QBO option, download the CSV and convert it here; the resulting .qbo imports exactly like a native Web Connect file.

Export your Synchrony card activity as a CSV, then upload it in the converter at the top of this page. The tool detects the date, description, and amount columns, normalizes the dates, strips dollar signs, and checks the parsed total against your file before it writes the .qbo. Download the .qbo and import it into the matching Synchrony account in QuickBooks. The whole pass takes under a minute, and nothing is entered by hand.

Sign in to your card's account site (for example the Amazon Store Card, Lowe's, or Sam's Club portal, all serviced by Synchrony), open the Activity or Statements area, and choose a date range or a specific billing statement. Select the download or export option and pick CSV or spreadsheet. If your card only shows PDF, download the statement PDF and turn it into a spreadsheet first, then convert that here.

Because Direct Connect is unavailable, the realistic choice is between a flaky aggregated feed and a clean manual import. This table lays out what each Synchrony card typically supports and what it means for your books.

The usual reason is that the card runs on Synchrony's platform, which has no Direct Connect and only a partial aggregated feed. When QuickBooks shows a connection error, a login loop, or an account that stops updating, it is hitting that limitation rather than a problem on your end. Downloading the CSV and importing a converted .qbo sidesteps the connection entirely, so a broken feed no longer blocks your close.

Yes. The Amazon Store Card, Amazon Business Prime cards, Sam's Club Mastercard, Lowe's, PayPal Credit, Venmo Credit Card, and CareCredit are all serviced by Synchrony and export activity as a CSV in the same way. Convert that CSV to a .qbo and import it into the matching credit card account in QuickBooks. Purchases import as negative and payments as positive, the standard card convention, so the balance reconciles against your statement.

In QuickBooks Online, open Bank transactions (newer accounts reach it from All apps, then Accounting, then Bank transactions), select the matching Synchrony card account, and use the upload option to add the .qbo file from your computer. QuickBooks reads the file, shows the charges and payments for review, and posts them once you accept. Because it is a Web Connect file rather than a raw CSV, you skip the column-mapping screen that raw CSV uploads force you through.

In QuickBooks Desktop, go to File, then Utilities, then Import, then Web Connect Files, and choose the .qbo you downloaded here. QuickBooks Desktop has no native import for a plain CSV of card transactions, so a .qbo is the only file it accepts for this. Match it to the correct Synchrony account when prompted and the charges post to that register.

QuickBooks Online caps a raw CSV upload at 350 KB, roughly a thousand rows, which splits long histories into several files. A .qbo import is not held to that CSV limit, so converting lets you bring a full year of Synchrony activity into QuickBooks in one file. To process several statements at once, the bulk CSV to QBO converter handles them in a single batch.

On a credit card account the sign convention is the reverse of a checking account, and this is where most Synchrony imports go wrong. In a single Amount column a purchase that increases what you owe is normally a negative number and a payment to the card is positive. Get it backwards and the card balance grows when you pay it down, which reconciles to nothing and is tedious to unwind after the fact.

Use a minus sign rather than parentheses. QuickBooks reads a leading minus and does not reliably read (45.00) as negative forty five dollars. If your Synchrony export arrives with separate Debit and Credit columns instead, keep it in the four column layout and let the converter combine them rather than merging the columns yourself in Excel.

No, and you should not want to. Each card is a separate liability account in QuickBooks with its own balance and its own reconciliation, so each card needs its own file. Merging an Amazon Store Card and a Sam's Club Mastercard into one upload produces a register that cannot be reconciled against either statement.

If a client holds four Synchrony cards, that is four exports and four conversions, and each one imports into the matching QuickBooks account. The upside is that the conversion is short work per card, since store card volume is usually low compared with an operating checking account.

Download by date range rather than by statement wherever the card site allows it, and set the range to run from the day after your last imported transaction through the statement close date. Card sites frequently offer a rolling activity window that does not line up with billing cycles, so a statement led download leaves gaps at both ends.

When you do end up with overlapping ranges, convert to .qbo rather than importing raw CSV. Every transaction in a .qbo file carries a FITID that is unique within the account, and QuickBooks skips identifiers it has already accepted, so an overlap is ignored instead of being posted twice. A CSV carries no transaction identifier at all, which is why a second upload of the same week silently duplicates it.

Yes. CareCredit runs on Synchrony, so the export and conversion work exactly as they do for the retail cards, and the resulting .qbo imports into whichever QuickBooks account you have set up for the card. Practices that carry CareCredit usually also want the coding to be consistent month to month, which the converted file supports because the description text comes through unchanged.

The same applies on the practice side of the relationship. Firms handling this kind of book regularly work from our CSV to QBO converter for medical practices and converter for veterinary practices pages, which cover the account structure rather than the file mechanics.

QuickBooks Direct Connect is being retired industry wide on 30 October 2026, and new enrollments already ended on 30 April 2026. For Synchrony cardholders this changes less than it does elsewhere, because Synchrony never supported Direct Connect in the first place. What it does mean is that the aggregated feed and the file import are now the only two routes for everyone, and the file import is the one that does not break when a bank changes its login flow.

Individual issuers have moved on their own timetables ahead of the industry date, so a notice from your own card site outranks the general deadline. If a card you rely on drops its feed, converting the CSV export is the immediate fallback and needs no enrollment, no bank approval and no waiting period.

Yes, and the accuracy check is the whole point. Before the .qbo downloads, the converter totals every transaction it parsed and compares that against your Synchrony file. If a row is missing or misread, you see it in the preview instead of during reconciliation weeks later. The tool only reads the transaction rows, date, description, and amount, to build the file, and does not ask for your card login.