How to convert a credit card statement to CSV

How a card statement differs from a bank statement

The two look similar and behave in opposite directions. On a current account the balance is an asset: money in raises it. On a card the balance is a liability: spending raises it and paying it off lowers it.

The missing running balance matters more than it looks. On a bank statement, each row's balance lets every single line be verified. A card statement usually offers only totals, so the checks are aggregate ones — which is why the summary box is worth reading carefully.

Which way the signs go

Exports here keep the convention the statement itself uses: a purchase is positive because it increases what you owe, and a payment towards the card is negative because it reduces it. The Debit column holds spending and the Credit column holds payments and refunds.

Date,Description,Debit,Credit,Balance
2026-08-09,MOBILE PAYMENT - THANK YOU,,3700.80,
2026-08-15,PORKBUN* PORKBUN.COM SHERWOOD OR,11.08,,
2026-08-17,APPLE.COM/BILL CUPERTINO CA,29.99,,

In the standard profile, which uses a single signed Amount column, the same three rows read +11.08 and +29.99 for the purchases and −3700.80 for the payment.

Accounting software often wants the opposite sign for a card account, because it models the card as a liability from the ledger's point of view. Check the destination's convention before importing, and use the Debit and Credit columns rather than a single signed column where you can — they cannot be misread.

The QBO and OFX exports handle this for you: those formats define their own sign convention for card accounts and the converter writes it, so a purchase arrives in QuickBooks or Quicken the way those applications expect.

The account summary is your proof

Card statements print a box showing how last month's balance became this month's. It is the best evidence you have that an export is complete, because it is produced by the issuer independently of the transaction list.

Two things should hold. The box should add up on its own, and the movements it lists should equal what you extracted: the payments line against the sum of your credits, and charges plus fees plus interest against the sum of your debits. Both are checked automatically and reported before you download.

If the charges line says 3,561.59 and your rows total 2,289.30, you are missing 1,272.29 of spending — usually a block of transactions on a page the extractor did not read, not a rounding problem.

Layout traps particular to card statements

• Two dates per row. Issuers print the transaction date and the posting date, sometimes marking one with an asterisk. The full CSV profile keeps both in separate columns.
• Descriptions across several lines. A merchant's city, country and phone number often sit on their own lines beneath the name; they belong to the row above, and rows assembled this way are flagged as merged so you can confirm them.
• Reward columns. Cash-back and points columns sit between the description and the amount and must not be mistaken for the transaction amount.
• Foreign currency rows. The original amount and the exchange rate are printed alongside the charge; the charge in your own currency is the one that belongs in the export.
• Sectioned statements. Payments, purchases, fees and interest are often separate blocks, each with its own header, and each section's subtotal is not a transaction.
• Multiple cardholders. Charges are grouped per card, and the same merchant can appear under two names in one statement.

Converting one

Upload the PDF, check the extracted rows against the page image beside them, then export. Points worth a moment:

• Choose the accounting profile if the file is going into bookkeeping software, and the standard profile if it is going into a spreadsheet for analysis.
• Set the date format to match the destination rather than the statement. YYYY-MM-DD is the safest for anything that will be sorted.
• Read the Conversion Report before downloading. It says which checks ran and which passed.
• Statements that are scans rather than text convert too; see converting scanned statements.

If the card is password-protected, as issuer-mailed PDFs often are, see converting password-protected statements.