Bank statements
Amex statement PDF to CSV
Convert readable Amex statement PDFs into reviewable CSV transaction rows for expense cleanup, spreadsheet review, and later accounting import prep.
What makes card statements different from bank statements
Amex statements still need transaction-row cleanup, but card activity adds a few extra review traps: payments against the card, refunds, credits, fees, interest, and merchant descriptions that often wrap across lines. The goal is to keep one row per real transaction instead of treating every visible line as import-ready data.
- Upstream input: original Amex statement PDF or readable scan
- Review output: Date, Description, Amount
- Downstream job: spreadsheet review, expense cleanup, or later import prep
What the CSV should contain
For a practical first CSV, keep the core transaction fields simple and reviewable. Signed Amount is usually easier to inspect than separate debit and credit columns when the source started as a statement PDF. Optional fields such as card member, page note, or running balance can stay in a review layer instead of the final import file.
- Date
- Description
- Amount
- Optional review columns such as card member, page note, or balance
What to review before import or expense coding
Review before import matters even more for credit-card statements because payments and credits can be mistaken for spend rows. Check whether purchases stay negative, refunds or credits stay positive where appropriate, and annual fees, finance charges, or payment lines are labeled clearly enough for the downstream workflow.
- Purchases, fees, and interest lines are not merged together
- Refunds and statement credits are distinguishable from purchases
- Payment rows are not confused with ordinary card spend
- Wrapped merchant descriptions still belong to the right transaction
Trust and file-quality guidance
Original PDFs work best, but clear scans and phone photos can still be tested if the transaction table is readable. DocuRows does not require bank login, and redacted files are fine as long as dates, descriptions, and amounts remain visible. This page is an Amex-specific workflow guide, not a claim that every Amex layout has been exhaustively validated.
Amex review CSV example
Date,Description,Amount,Review Note 2026-04-03,DELTA AIR LINES,-482.16,Travel expense 2026-04-07,STATEMENT CREDIT,45.00,Keep as credit 2026-04-18,ANNUAL MEMBERSHIP FEE,-95.00,Do not merge with purchases
Card statements often mix purchases, credits, and fees in one section, so review before import or categorization is still required.
FAQ
Can I use this for old Amex statements if CSV export history is missing?
Yes. That is one of the main reasons to use a review-first statement-to-CSV workflow, especially for older cleanup periods.
How should refunds or statement credits appear in the CSV?
They should stay distinguishable from purchases so the user can review sign direction and categorize them correctly before import.
Does this page mean every Amex layout is already verified?
No. It is a workflow guide for readable Amex statements and keeps the claim at reviewable CSV output rather than guaranteed bank-specific coverage.
Turn a statement file into reviewable rows
Upload a PDF, scan, screenshot, or clear photo and review the rows before downloading CSV.