To get a credit card statement to Excel, use the card issuer's CSV download if the statement is recent enough to be covered by it, and extract the PDF for anything older: statements from a closed card, statements a client emails over, and paper statements that were scanned. Either way, the finished sheet has one row per charge, payment, credit, fee and interest line, with one sign convention used throughout. Before the sheet goes anywhere, check it: the previous balance plus purchases, fees and interest, minus payments and credits, must equal the new balance printed on the statement. That one check catches a dropped line, a missed payment and a flipped sign.
That check is the part most guides to converting a credit card statement PDF to Excel leave out, and it matters because a card statement is not a bank statement. It is the statement of a liability account. Charges increase what you owe; payments and refunds reduce it. A spreadsheet built the way you would build one for a bank account goes wrong in predictable places on a card statement:
- the month's repayment is printed in its own block, away from the purchases, and gets left behind
- each line carries two dates, the transaction date and the posting date
- a purchase made abroad carries an original amount, an exchange rate and often a separate fee line
- interest and fees appear as lines of their own in a separate section
- on a business card, each supplementary cardholder's spending sits in its own block with a subtotal
The sheet you are aiming for, in Excel or as a CSV, is short: Date, Description, Amount, with the amount signed one way for every statement, plus the few columns a card adds. Whether you type the lines, use Excel's own PDF import or a credit card statement converter, the decisions below are what make the result balance.
Issuer download, Excel's PDF import, or extraction: picking the route
There are four ways to convert a credit card statement into Excel, and the statements you hold decide which one applies.
The issuer's download. Most card issuers let you export recent activity from online banking as a CSV file, and many also offer a QuickBooks or Quicken file. If you only need to export a credit card statement to Excel for the last few months, start here. The window is limited, though, and its length differs by issuer: statements older than it, cards you have since closed, and statements a client sends as PDFs are out of reach. Some issuers offer several kinds of export; the guide to converting American Express statements to Excel walks through one issuer's choices.
Excel's own PDF import. Data › Get Data › From File › From PDF opens the statement in Power Query, which can be enough for one clean, digitally generated statement. On card statements it breaks in familiar places: a description that wraps onto a second line becomes two rows, tables often arrive page by page with the headers repeated, the separately printed payments block comes in as its own table that is easy to leave unselected, and a scanned or photographed statement has no text layer to read at all.
Typing it in. Fine for a statement with fifteen lines. Across a year of statements, transposed digits and skipped lines are close to certain.
Extracting the PDF. An extraction tool reads the statement itself, so it covers what the other routes leave: old statements, closed cards, client PDFs, scans and phone photos, and a year's backlog at once.
| What you have | Route |
|---|---|
| Recent statements on an open card | Issuer CSV download |
| One clean digital PDF, a one-off | Excel's Get Data From PDF |
| A handful of lines | Typing |
| Older or closed-card statements, client PDFs, scans, a backlog | Extract the PDF |
Keep the repayment line, and pick one sign convention
The payment you made to the card this month belongs in the sheet. It is a transaction on the card account, the same as a purchase, and without it the account cannot be carried from one statement's closing balance to the next. Leave it out and the balance check will be wrong by exactly the amount of the payment.
The worry behind leaving it out is double counting: the same money already appears as an outgoing on the bank statement. It does, and that is correct. In the books the repayment is a transfer from the bank account to the card account, not an expense, so it gets categorised as a transfer rather than deleted. The expenses are the purchases; the repayment just moves the debt.
It is also the line most often lost by accident. Issuers commonly print payments in their own section, headed something like Payments and Credits, apart from the list of purchases. Copy the purchases table by hand, or select only that table in a PDF import, and the payment never arrives.
Then the signs. On a card, a charge increases the balance you owe and a payment or refund reduces it. That runs the opposite way to a bank account, where money in is the positive figure, which is why rules carried over from converting a bank account statement to Excel produce a sheet whose signs fight the statement. Two layouts work:
- One signed Amount column. Charges, fees and interest positive; payments, refunds and other credits negative. The column then moves the same way as the balance on the statement, and its sum is the change in what you owe.
- Two columns, Charges and Credits, both holding positive numbers. Easier to read at a glance, and some imports ask for it.
Either is fine. Mixing them is not: a sheet where January's payments are negative and February's sit as positive numbers in the same column has totals that mean nothing. Decide once and apply it to every statement in the file.
Take the sign from what the line is, not from how it was printed. Some statements mark credits with a trailing CR, some with a minus sign, and some only by printing them in the credits section with no marker at all. A refund lifted from that section without its section heading looks exactly like a purchase. If your accounting software wants the signs the other way round, flipping them is one step at import.
Dates, foreign currency, fees and cardholders: one column decision each
Transaction date or posting date. Many issuers print both, side by side; Canadian bank cards commonly do. The transaction date is when you bought something, and the posting date is when the issuer recorded it, usually a day or two later. Posting date ties every line to the statement period, so it is the natural choice when the sheet exists to match the statement. Transaction date is what counts for a tax-year cut-off and for matching a receipt: a purchase made on 30 June and posted on 2 July belongs to a financial year ending 30 June, whatever the posting date says. Pick one as the Date column, or keep both in two columns, but never use posting dates for some statements and transaction dates for others.
Foreign-currency purchases. A purchase made abroad usually shows the original amount and currency, the exchange rate the issuer applied, and the amount billed in your card's currency. The billed amount is the transaction; it is what the balance moved by. Put it in Amount, and if you need the detail for expense claims or VAT, add Original Amount, Original Currency and Rate as columns of their own. The fee is a separate matter. Many issuers charge a foreign transaction fee (a non-sterling transaction fee on a UK card, for example) and print it as its own line, sometimes directly under the purchase, sometimes in the fees section. Some fold it into the converted amount instead. Where it is printed separately, it is a row of its own, not a note on the purchase.
Interest and fees. Interest, the annual fee, a late payment fee and cash advance fees are rows, dated and signed like any other charge. They are usually printed in their own interest and fees section, often as a short list with a total underneath, and the total makes them look like a summary to skip. They are real costs that belong in the books, and they are the rows a balance check most often finds missing.
Cardholder blocks. A business credit card statement with supplementary or additional cardholders prints each person's transactions as a block, headed with the cardholder's name and the masked last digits of their card, and closed with a subtotal. Getting a business credit card statement to Excel cleanly means flattening those blocks without losing who spent what: add a Cardholder column and fill it on every row. Keep each block's subtotal aside as a check on that cardholder's rows, not as a row of its own. Coding each employee's spend to general ledger accounts is the next job, and splitting a multi-cardholder corporate statement by employee covers it.
With those decisions made, the columns look like this:
| Column | What goes in it | Why |
|---|---|---|
| Statement Date | The statement's closing date, on every row | Traces each row back to its statement and lets you check one statement at a time |
| Date | Transaction date or posting date, the same choice for every statement | Tax-year cut-off and receipt matching, or the statement period |
| Posting Date | Optional second date | Keeps both when you need both |
| Description | The merchant or line text, joined onto one line | Wrapped descriptions otherwise become extra rows |
| Amount | Signed: charges, fees and interest positive; payments and credits negative | Moves the same way as the balance owed |
| Original Amount, Original Currency, Rate | Only for foreign purchases | Expense claims and tax records |
| Cardholder | Name or masked last digits | Supplementary cardholder statements |
| Type | Purchase, payment, credit, fee or interest | Lets you total each kind for the balance check |
The tie-out: proving the sheet holds every row
A card statement carries its own proof of completeness. The balance at the top and the balance at the bottom are linked by every line in between:
Previous balance + purchases + fees + interest − payments − credits = new balance
With a signed Amount column, the same check is one formula: the previous balance plus the sum of the Amount column must equal the new balance. For a stronger check, total the Amount column by Type and compare each total with the purchases, payments, fees and interest figures the statement prints: errors that cancel out in the overall sum, such as a dropped fee and a purchase captured twice, show up there. If the check fails, something is missing or has the wrong sign, and the size of the gap usually tells you which.
Here is a worked example, with invented figures:
| Statement figure | Amount |
|---|---|
| Previous balance | 2,480.00 |
| Purchases | 3,215.40 |
| Fees | 35.00 |
| Interest | 41.27 |
| Payments | 2,000.00 (reduces the balance) |
| Credits | 129.99 (reduces the balance) |
| New balance | 3,641.68 |
The arithmetic: 2,480.00 + 3,215.40 + 35.00 + 41.27 − 2,000.00 − 129.99 = 3,641.68. In the sheet, the signed Amount column for this statement should sum to 1,161.68, which is the new balance minus the previous balance.
On a consumer card, every figure the check needs is printed because the law requires it. Under Regulation Z's periodic statement rule (12 CFR 1026.7(b)), a consumer credit card's periodic statement must show the previous balance, each transaction, credits with their amounts and dates, interest charged and fees grouped and totaled by type, and the billing cycle's closing date with the new balance. Regulation Z governs consumer credit and largely exempts credit extended for business purposes, so these statement rules do not reach a business card. Business card statements commonly use the same layout, though, as do card statements from issuers outside the United States, and the check works on them in the same way.
Those printed totals are controls, not transactions. The previous balance, the new balance, the total of purchases, the interest total and each cardholder's subtotal are what you check the rows against. None of them belongs in the sheet as a row; a sheet that includes the purchases total alongside the purchases counts them twice.
When the check fails, compare the gap with the statement's own figures:
- The gap equals the payment. The payments block was not captured.
- The gap equals the fees or interest total. The interest and fees section was skipped.
- The gap is twice a refund. A credit went in as a charge; its sign is wrong.
- The gap is an amount that appears nowhere. Look for a split description that became a row with no amount, or a row captured twice across a page break.
Run the check on each statement separately, never on a year's total, where one statement's missing payment can hide behind another's duplicated charge. Then check the chain between them: each statement's previous balance should equal the prior statement's new balance. A break in the chain means a whole statement is missing from the set.
Extracting a year of card statements from PDF in one batch
The case where the PDF route earns its keep is the backlog: a client hands over twelve monthly statements at tax time, some downloaded, some scanned from paper, or a card was closed in March and the issuer's download no longer reaches it. Done by hand, that is twelve separate conversions and twelve chances to drop a payments block. Done as one batch, the decisions above are made once, and every statement comes back in the same columns.
Two things make a backlog workable, and they are what to ask of any credit card statement data extractor: every row carries the statement it came from, its closing date or period, so the tie-out can be run one statement at a time; and the column rules are stated once, up front, not fixed afterwards in twelve places.
Invoice Data Extraction is an AI extraction assistant that can convert credit card and bank statements to Excel or CSV. Bank and card statements are one of the document types it reads, one row per transaction, from PDF or scanned statements, and phone photos of paper statements are accepted too. You upload the year's statements as one batch and say what you need in plain words. An empty prompt box offers ready-made prompts by document type, credit card statements among them. Picking that one fills the prompt box with a short prompt in plain words, which you can change before extracting and save to your Prompt Library as your own. To carry the decisions above, write them into the prompt. For example:
I'm preparing a year of credit card statements for bookkeeping.
One row per transaction, including payments, refunds, credits, fees and interest.
Do not add rows for balances, totals or cardholder subtotals.
Columns:
Statement Date (the statement's closing date, YYYY-MM-DD)
Date (the transaction date, YYYY-MM-DD)
Description
Amount
Original Amount
Original Currency
Cardholder
Type (classify as Purchase, Payment, Credit, Fee or Interest)
- Show charges, fees and interest as positive amounts, and payments, refunds and credits as negative.
- For foreign purchases, Amount is the amount billed in the card's currency.
- Show a foreign transaction fee as its own row.
To fix the exact headers in the exact order every month, the same rules go into a Structured Prompt instead, with each column's instruction beside its header.
Two columns come back after yours. Source File gives the file and page each row came from, so a row in the year's sheet leads straight back to its statement. Review Needed flags a value or a row the panel of AI agents cannot agree on, with what to check, so you know which lines to look at first. The tie-out is still yours to run: filter by Statement Date, sum the Amount column, and compare it with each statement's balances.
Card numbers masked to the last few digits, the way statements print them, are fine to upload; nothing needs unmasking first. There are 50 free pages every month, with no subscription and no credit card to start.
Importing the sheet into QuickBooks or Xero as a credit card account
A balanced sheet goes into your accounting software against a credit card account, the liability account that represents the card, never into the bank account. Imported there, the repayment lands where it should: as a transfer from the bank account that pays down the card, not as an expense on one side or as income on the other.
Accounting imports take CSV, and they want only the columns they map, typically a date, a description and an amount, or a date, a description and separate debit and credit columns. So keep the full sheet in Excel as your working copy, with the cardholder, statement date and original-currency columns intact, and save a CSV copy containing only what the import asks for. Getting a credit card statement to CSV for an import is that second step, not a separate conversion.
Which sign the import expects for a charge depends on the package and on the layout you choose, so test before loading a year. Import one statement's rows, then check that a purchase you know shows as a charge on the card account and the repayment as a payment. If they come out inverted, undo that import, multiply the Amount column by minus one in the sheet, save the CSV again, and reimport. The steps for each package, including the column layouts they accept, are in the guides to importing statement transactions into QuickBooks and importing statement lines into Xero.
If you extract the statements with a Structured Prompt, the columns can match the import layout from the start: the exact headers in the order the import expects, with the Source File and Review Needed columns left out in Preferences so the file carries nothing but those columns.
Once the lines are in, matching each one to its receipt and to the ledger is the next job, and the guide to reconciling the card account against receipts and the ledger picks it up from there.