Credit Card Statement Conversion Workflow: From PDF to Reconciliation-Ready CSV/Excel

Intro

A credit card statement is a PDF that mixes transaction rows with summary lines. If your export keeps totals inside the transaction dataset, reconciliation fails silently. This post gives a repeatable workflow: extract only transaction rows, normalize dates and signs, validate totals against the statement, then export to CSV/Excel for bookkeeping.

What you must preserve

Checklist workflow

1. Keep the PDF unchanged as source of truth.
2. Extract transaction rows only (use preview).
3. Normalize date formatting so Excel reads them as dates.
4. Enforce one sign convention (e.g., charges negative, payments positive).
5. Exclude summary/totals lines from the import sheet.
6. Validate counts and net movement against the statement.

Common failure modes

• Summary rows included: filter by keywords like "Total".
• Sign flipped payments: confirm against a known payment line.
• Refunds treated as charges: watch for negative amounts and reversals.

CSV vs Excel decision

Internal links

• Parse My Statement: /
• PDF to CSV: /blog/pdf-bank-statement-to-csv
• PDF to Excel: /blog/bank-statement-pdf-to-excel

FAQ

What’s the biggest mistake?

Including summary lines as transactions or flipping signs.

How do I validate before import?

Compare net movement and row counts to the statement.