Why convert a card statement to CSV?
- Checked, not guessed. Card statements rarely have a live feed to reconcile against, so the balance check ties the transactions to the statement's own previous- and new-balance lines and flags anything that doesn't add up.
- No bank feed to rely on. When a card was closed, or never connected to your accounting software, a PDF is the only record — this gets the transactions out without re-keying.
- Right signs for import. Charges land as negative and payments as positive, so QuickBooks or a spreadsheet reads spend and payments the way you expect.
How it works
- Open the converter. No registration is required.
- Upload the statement. Drag and drop your PDF credit-card statement, or browse from your device.
- Convert to CSV. Choose the CSV target format and click Convert.
- Download and review. Preview the extracted rows, unlock the full CSV (one-time $15), review any flagged rows, then use it in QuickBooks, Xero, or Excel.
What gets flagged
Before the CSV is handed back, a deterministic reconciliation check runs. It flags the statement for review when:
- A row's printed running balance doesn't equal the previous balance plus that row's amount.
- The previous balance plus the sum of every transaction doesn't equal the new statement balance.
- The transaction dates run out of order — a later row dated before an earlier one.
- No transactions could be read from the statement at all.
Flagged rows are surfaced for you to review — never silently exported as correct. That review step is the difference between a converter you can trust with your books and one that just dumps the text and hopes.
Good for
- Expense tracking and categorising a card's spend.
- Getting a closed or feed-less credit card into accounting software.
- Catch-up bookkeeping across several billing cycles at once.
Why credit-card signs need flipping — and how that's handled
This is the one thing that quietly ruins a credit-card import, so it's worth knowing what the converter does about it.
A bank statement's balance is money you have, so a withdrawal reduces it and prints negative. A credit-card statement's balance is money you owe, so a purchase increases it — and most issuers print purchases as plain positive numbers, showing your monthly payment as the negative or parenthesised one. Accounting software expects the opposite: a purchase is money out, a refund is money in.
Export a card statement with its printed signs untouched and every expense arrives as income. The books still balance, which is exactly why it can go unnoticed until the category totals look absurd at period end.
So a card statement is detected and its amounts are flipped before export. Purchases and fees come out negative, payments and refunds positive. Detection reads the statement's own text — a card statement carries disclosures a chequing statement doesn't, like a credit limit, an APR, and a minimum payment due — and requires more than one of them, so a current account that merely mentions an overdraft limit isn't mistaken for a card.
The direction is then confirmed arithmetically rather than assumed: the previous balance plus the transactions has to equal the new balance printed on the statement. When that ties out, the flip is verified and the file is ready to import.
When it can't be confirmed — a statement that doesn't print both balances, or one whose figures don't reconcile — the statement is flagged for review rather than quietly guessed at, telling you exactly what couldn't be checked. Take ten seconds to look at one row you recognise: your monthly payment should be positive and your purchases negative. If it reads the other way, multiply the amount column by −1 before importing.
One thing to expect either way: your card payment appears on this statement and on the bank account that funded it. That's one transfer seen from both sides. If both accounts are in your books, categorise it as a transfer rather than as income and an expense, or it gets double-counted.
FAQ
How do you know a purchase is money out when the statement prints it as positive? A credit-card statement is identified from disclosures a deposit account doesn't carry — a credit limit, an APR, a minimum payment due — and more than one has to be present. Its amounts are then flipped so purchases are negative and payments positive, and the direction is confirmed against the statement's own previous and new balance. If that can't be confirmed, the statement is flagged for review instead of guessed at.
How are charges and payments signed? Charges (money leaving the card) come through as negative amounts and payments or credits as positive, in a single signed Amount column — the way QuickBooks and spreadsheets expect a transaction feed to read.
What columns are in the CSV? A dated transaction table: Date, Description, and a signed Amount. It imports cleanly into QuickBooks Online and opens in Excel or Google Sheets first.
What happens to rows that don't reconcile? They're flagged, not dropped. The row still appears in your CSV, but the statement is marked as needing review with the specific checks that failed, so you can compare against the original before importing. Nothing that fails the balance check is passed off as verified.
Is my card statement kept private? Files are deleted after 1 hour, never used to train any AI model, and we never connect to your card issuer. All transfers are encrypted. This is a conversion utility, not financial or accounting advice.
Related
- Bank statement → CSV → for bank statements
- Bank statement → QuickBooks → QuickBooks-specific CSV
- Bank statement → Excel → open it in a spreadsheet
- All supported formats →