Credit Card Statement to CSV: How to Export and Read It

If you work with credit card statements regularly, you will eventually need the transactions in a spreadsheet rather than in a PDF you read line by line. Converting a credit card statement to CSV turns a read-only document into a file you can sort, filter, total, and import into your bookkeeping software.

A statement PDF is fine for a human checking one charge, and useless for a month of reconciliation, a spend breakdown by category, or a client onboarding file that has to match the issuer totals exactly.

There are two routes to the same CSV. The first is the issuer’s own export button, when your card provider offers one. The second is a converter that reads the statement PDF and writes the rows for you. This guide covers both, explains what the columns actually contain, and shows how to check the result before it reaches a client file.

What a credit card statement CSV actually contains

A CSV file is a plain-text format where each row is a record and each column is separated by a delimiter, most often a comma. Applied to a credit card statement, each row becomes one transaction and each column becomes one attribute of that transaction, such as the transaction date, the description, the amount, and the balance after the charge posts.

Because the export is produced by the issuer, the column set is not standardised across issuers, so a reconciliation process cannot assume a fixed header order. One issuer may lead with a card number, another with a posting date, and a third may split a purchase into separate fields for the original charge and its adjustment.

That variation is the most common reason a clean looking CSV fails to import or fails to reconcile. The format itself is stable, the headers are not. Our guide to the bank statement CSV format explains the underlying structure in more depth, and the same rules apply to card statements.

The columns you will usually see

Most card exports carry a date field, a merchant or transaction description, a signed amount, and a running balance. Corporate cards add a cardholder name, a cost centre, a general ledger code, or a receipt flag. Some exports add tax or tip fields, and some separate the merchant name from the terminal location.

None of those additions trouble a spreadsheet. They only trouble code or a fixed template that expects one header in one position, which is why the header mapping step matters more than the export step.

Grid of cells with an arrow from a document stack into the grid
Every card export produces the same structure, one row per transaction and one column per attribute, even when the headers differ between issuers.

Issuer export first, where the download lives

Credit card issuers render a statement as a PDF or a web document by default; the CSV export is the issuer’s own download feature, and its availability differs by issuer. In practice, personal card portals often offer a transaction download while business card portals put the export inside an expense or reporting section rather than the statement view.

The reliable way to find it is to open the statement period you need, then look for a download control near the date range or statement selector. Typical labels include Download transactions, Export CSV, Export statement, or Download data. If the statement page only offers PDF or Print, that view has no export.

When an issuer export does not exist, the statement PDF is still a complete record and can be converted instead. We cover that route in how to convert a PDF bank statement to CSV, which uses the same extraction and verification steps you would apply to a card statement.

What to check before you download

Export the format you actually need rather than the easiest one to find. If your downstream tool expects comma separated values, choose that rather than a tab separated or semicolon separated file, because some spreadsheet applications open a tab separated file correctly and then save it back with a different delimiter.

Confirm the date range covers the full statement period and that the file includes every card on the account. A partial export produces a balance mismatch that looks like a data problem much later.

From Bank Statement to QuickBooks-Ready File

That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.

Start Converting

The merchant category code and what it tells you

Visa and Mastercard both define the merchant category code as the four-digit number carried on the transaction message, which is why a statement export shows a code that can be mapped back to a merchant type. When your card statement includes a category column, you have a classification signal that does not depend on reading the merchant description.

Use it as a grouping key, not as a final expense category. A four-digit code tells you a charge was processed in a particular industry, which is often enough to separate travel, restaurant, and office supply spend without touching each row.

The mapping lives with the card networks. According to the Mastercard Quick Reference Booklet, the merchant category code is a four-digit number assigned by the acquirer to identify the merchant’s primary business activity, and the booklet publishes the full list of codes with their descriptions.

The same four-digit structure appears in the Visa merchant data standards manual, which documents the merchant identification fields carried on Visa transaction messages.

Why the same merchant can show two codes

The MCC that appears on the statement is assigned by the acquirer based on the merchant’s primary business, so the same merchant can show different codes across issuers only when its primary business or its acquirer assignment differs. In practice this happens when a business sells several kinds of goods and the acquirer classifies it by its largest line of business.

A code difference between two issuers is not a data error on its own. Before treating it as a duplicate or a missing transaction, check that the merchant is the same entity and whether one of the statements came from a different card network.

Mapping headers without hard-coding positions

Because the column set is not standardised across issuers, the reliable approach is to read the header row first and map by name rather than by position. Most spreadsheet tools and scripts can do this in a single pass: read row one, find the fields you need, and pull those columns for every row below.

Watch for naming variations. Date may appear as transaction date, posting date, or trans date. The amount field may be labelled charge, debit, or amount, and the sign convention may differ, with some issuers using parentheses for credits and others using a negative number.

Our guide to taking a bank statement to CSV walks through that mapping logic step by step, including how to choose which date to keep when a statement shows both a transaction date and a posting date.

Keep a mapping sheet per issuer

Write down the header names you found for each issuer you work with. The next statement from that issuer then uses the same map without re-reading the file, and you get a consistent column order in the output even when the issuer reorders its export.

When you hand a file to a bookkeeper or client, keep the original issuer column names in the file and do the renaming in a separate step. That way the file can always be traced back to the statement it came from, which matters during a review.

Reconciling the file against the printed balance

The value of a converted statement is that you can check it. Every card statement ends with a closing balance or a new balance figure, and a correctly converted file should reproduce that figure when you total the transactions in the order the issuer applied them.

The check is a running total. Start from the opening balance on the statement, add each transaction in statement order, and confirm the final figure equals the closing balance the issuer printed. When it does not, the difference is usually a missing row, a duplicated row, or a fee the export left out.

This is the same method used on bank statements, and the comparison is laid out in bank statement PDF versus CSV. That piece explains why the balance check catches problems that a visual scan of the document misses, such as a duplicated authorisation that shifts every subsequent total.

Fees, refunds, and payments

Keep interest charges, annual fees, and monthly service charges in the transaction list rather than deleting them as noise. They are real movements on the account and they belong in the reconciliation, even when you later reclassify them to a different expense category.

Payments and refunds need a decision as well. A payment to the issuer reduces the balance but is not an expense, so most workflows separate it from purchases with a column or a filter. Do not delete it during reconciliation, because deleting it breaks the running balance check.

Moving the CSV into Excel, Google Sheets, or QuickBooks

Once the file reconciles, import it. A well formed CSV opens directly in Excel and in Google Sheets without a wizard in most cases, because the comma delimiter is the default on both. The steps for a clean import, including how to protect leading zeros, are in importing a CSV into Google Sheets.

For QuickBooks Online and Desktop, the goal is to avoid rekeying, because rekeying is where month-end books go wrong. Easy Statement Sheet produces a direct QBO export, with each row reconciled against the printed running balance and four clean columns of Date, Description, Amount, and Balance.

Where conversions most often go wrong

The most common failure is a delimiter mismatch. A file exported with semicolons or tabs opens as a single column in Excel, and every date and amount ends up inside one cell. The fix is straightforward: use Data and then Text to Columns, and choose the delimiter that matches the file.

The second is date formatting. Some issuers write dates as month, day, year and others write them as day, month, year, and a file containing both sorts incorrectly until the format is set explicitly rather than guessed by the spreadsheet.

The third is a duplicated export, where the same statement period was downloaded twice and pasted into the same file. The running balance check catches this at once, because the totals no longer reach the printed closing balance.

The fourth is a PDF conversion that skipped a page. If the statement has a page break in the middle of a transaction table and rows are missing, the balance check is the only reliable signal, so run it every time instead of trusting the conversion by default.

A six step workflow that holds up under review

Step one: pull the issuer export if it exists, otherwise save the statement PDF. Step two: confirm the date range and card coverage before you download anything.

Step three: map the headers by name into your own column order and record the map for that issuer. Step four: clean the amount column so one sign convention and one date format apply to every row.

Step five: run the running balance check against the printed figure and investigate any difference before going further. Step six: import into Excel, Google Sheets, or QuickBooks, and keep the source file next to the converted file for traceability.

That workflow takes a few minutes per statement and removes the two failure modes that cost bookkeepers the most time: retyping transactions, and discovering a mismatch after the file has already reached a client.

When the statement serves a purpose beyond bookkeeping

Card statements also appear in expense audits, dispute documentation, and fee reviews, and each of those needs the same underlying transaction list. Work from a converted file that you have checked against the printed balance rather than from a screenshot of a document.

If this is your first pass at converting statements, Easy Statement Sheet converts three statements free with no card required, and files are processed in memory, so nothing is stored once the conversion finishes.

Turn That PDF Into a Spreadsheet in Minutes

You've seen how to do it manually — now let the tool handle the heavy lifting. Upload your bank statement and get Excel, CSV, or QBO in a few clicks.

Try It Free
ESS Editor
ESS Editor

Samandya writes practical guides on converting bank statements into usable financial data, including PDF-to-Excel, CSV, and QBO files for QuickBooks. His articles help individuals, businesses, and bookkeepers review transactions, compare formats, and prepare financial documents for bookkeeping and reconciliation.