American Express CSV to QBO Converter: Convert Amex CSV to QuickBooks

Sign in at americanexpress.com on a desktop browser, open Statements and Activity, pick your date range, and download the file in the CSV or Excel format. Upload that CSV here. The converter reads the date, description, and amount columns, checks the transaction total against your file, and returns a .qbo you import into QuickBooks Online or QuickBooks Desktop.

Open your card account at americanexpress.com, go to Statements and Activity, and choose the Download option. American Express offers a CSV or Excel download alongside Quicken (.qfx), Microsoft Money (.ofx), and a QuickBooks download. Select CSV, pick either a billing statement or a custom range, and save the file. The mobile app does not offer the export, so use a desktop browser.

The live American Express connection is widely reported to post some charges and skip others, which leaves the account looking reconciled when transactions are actually absent. Pending charges that later settle at a different amount are a common cause, and so are authorization holds that never convert. A CSV download of posted activity is complete for the range you pick, so converting it gives you a file you can trust.

American Express keeps recent activity plus roughly the past six billing statements available for download, and a single export usually covers about 90 days. Anything older has to be pulled statement by statement while it is still online. If you are catching up a year of bookkeeping, download each available statement as a CSV, convert them, and import the .qbo files in order.

American Express does offer a QuickBooks download for many card accounts, but it is bound to the same recent activity and six statement window as the feed, and the file it produces has been a frequent source of import complaints. The CSV export has no such reliability problem. Converting that CSV yourself produces a .qbo built to the Web Connect structure QuickBooks expects, with your account name and transaction types set correctly.

No. QuickBooks Desktop cannot import bank or credit card transactions from a raw CSV file. Its transaction import path is Web Connect, which accepts only .qbo files, so a CSV has to be converted first. QuickBooks Online can accept a CSV, but it requires you to map columns on every upload and it does not resolve the sign convention Amex uses for credits and payments.

Amex CSV exports carry extra columns such as card member name, account number, category, and reference, none of which QuickBooks expects. QuickBooks Online accepts a three column layout of date, description, and amount, or a four column layout that splits debit and credit. It also caps a single upload at 350 KB. The converter strips the extra columns, normalizes the dates, and sets the signs before it writes the .qbo.

American Express writes charges and credits into one amount column, and the sign convention on a credit card export is the reverse of what a checking account uses. The converter reads the sign in your file, maps charges as increases to the card balance and payments or refunds as decreases, and shows you the resulting totals in the preview before you download. That is what stops a reconciliation from ending up backwards.

Yes. Business Green, Gold, Platinum, corporate cards, and the Business Line of Credit all export the same CSV structure from the Activity page, and all convert the same way. Corporate card programs that distribute statements to individual card members work too, since each downloaded CSV is converted separately into its own .qbo before import.

QuickBooks caps a single CSV upload at 350 KB, which is roughly 1,000 transactions, and that limit is one of the reasons a heavy card month fails to import. A .qbo file is not held to the same cap. If you are converting a full year across several cards, run the files together with the bulk CSV to QBO converter rather than one at a time.

Yes, and the accuracy check is the point. Before the .qbo downloads, the converter totals every transaction it parsed and compares that figure to the total in your Amex CSV. A misread or missing row shows up in the preview instead of surfacing months later during reconciliation. Working from a different card or bank? Use the CSV to QuickBooks Online converter for any account, handle statements from other issuers with the credit card CSV to QuickBooks converter, turn a spreadsheet into a .qbo with the Excel to QBO converter, or compare tools on the best CSV to QBO converter roundup. Sister cards are covered by the Chase CSV to QBO converter and the Capital One CSV to QBO converter. For the long form walkthrough, read American Express CSV to QuickBooks, and for the import step itself see how to import a QBO file into QuickBooks. For a Discover card, whose Web Connect download Discover retired, use the Discover CSV to QBO converter. If your card is issued by Barclays, whose QuickBooks feed broke in 2026, use the Barclays CSV to QBO converter.

After the converter returns your file, the import path depends on which QuickBooks you run. In QuickBooks Online the upload sits under All apps, then Accounting, then Bank transactions, where you choose Link account and then Upload from file. Older accounts still show the same screen as Transactions, then Bank transactions, so use whichever navigation your company file presents. In QuickBooks Desktop the file goes through Banking, then Bank Feeds, then Import Web Connect File.

Point the import at your American Express liability account rather than a bank account. Getting that wrong is the usual reason a card import looks inverted afterwards, because QuickBooks applies the sign convention for the account type it is loading into.

No. Every transaction inside a .qbo file carries a FITID, a transaction identifier unique within the account that is never reused. QuickBooks tracks the FITIDs it has accepted and skips ones it has already seen, so reloading a file you previously imported adds nothing to the register.

That matters more on Amex than on most accounts, because the usual reason to re import is that charges were missing the first time. You can convert a wider date range and load it again without unpicking what is already there. A plain CSV carries no identifier at all, so the same approach with a spreadsheet would double every transaction in the overlap.

You can, and the FITID mechanism is what makes it safe. If the live connection has already pulled a charge and your converted file contains the same charge, QuickBooks recognizes the identifier and skips it. The two routes coexist rather than fighting, which is useful while you are backfilling history that the feed cannot reach.

The one thing to avoid is running a CSV paste alongside an active feed. Without transaction identifiers QuickBooks has no way to match the rows, and you get a duplicate for every transaction the feed already brought in. Convert first, then import, and the overlap takes care of itself.

Use MM/DD/YYYY for a United States QuickBooks company file. The Intuit CSV formatting article that ranks highest is the global edition and it recommends DD/MM/YYYY, which quietly misposts every transaction dated the 1st through the 12th when applied to a US file. The totals still tie, so the error hides until a month refuses to reconcile.

Be careful about opening the export in a spreadsheet before converting it. Two digit years from 00 to 29 become 2000 through 2029 and 30 to 99 become 1930 through 1999, and Windows Excel uses the 1900 date system while Mac uses 1904, which shifts every date by four years and a day when a file moves between them.

Reconcile against the American Express statement, not the activity screen. Amex billing periods almost never match a calendar month, and pending charges that appear in online activity are not on the statement at all, so reconciling to a month end downloaded from the website leaves a difference that has no explanation in your books.

Three diagnostics resolve most breaks quickly. A difference that divides evenly by nine is transposed digits. A difference exactly twice the value of a transaction is a sign flip, which is especially common on card accounts because charges and payments reverse meaning against a bank account. A difference matching a single transaction exactly is a row that either did not convert or was accepted twice.