Credit Card Statement to Excel

On a bank account, money in raises the balance. On a credit card, the balance is what you owe, so a purchase raises it and a payment lowers it. A converter that treats a card statement like a bank statement produces signs that look right and totals that never reconcile.

The balance check here tries both conventions and reports which one the statement follows. When previous balance + purchases − payments and refunds = new balance, the summary says it reconciles "as a balance owed" — which checks the arithmetic but does not prove every charge was read.

Purchases, fees and interest land in Money out; payments and refunds in Money in; the signed Amount column follows the same rule, so summing it gives the change in what you owe with the sign flipped. Foreign-currency purchases keep the amount charged to the card; where the statement prints the original-currency figure on the line below, it usually ends up in the description.

The summary boxes a card statement is full of — minimum payment, credit limit, available credit, rewards — are not transactions and are not in the table. The QIF and OFX downloads are written as a credit card account, so budgeting apps file the transactions correctly.

Use the statement opening and closing dates, not the payment due date. A due date tells you when to pay a bill; it is not the date of every purchase. Confirm the previous balance, purchases, fees, interest, payments and refunds against the source. A minimum payment, available credit figure or rewards total belongs in the statement summary, not in the transaction list.

For example, if a fictional card starts at $300 owed, adds a $50 purchase and receives a $100 payment, the new amount owed is $250. The signed transaction amounts here are -50 and +100. Their sum is +50, while the liability fell by $50: that difference in convention is intentional. A refund also reduces the liability; a charge increases it. Check those signs explicitly when your importer previews the rows.

Convert each card account separately. A transaction may show an original EUR amount alongside the USD amount charged to the card. Use the billed account-currency amount for reconciliation; the original currency wording may remain in the description. This is not an exchange-rate conversion tool or a tested mixed-currency ledger.

QIF, OFX, QBO and QFX use the credit-card account structure when the balance checks identify the owed-balance convention. Do not import the result into a checking account simply because both show debits and credits. QuickBooks' upload error guide explains that an account-type mismatch can be rejected. Choose the actual card account and inspect a purchase, a payment and a refund before adding anything.

A passing check does not prove every charge was found. A missing payment and missing purchase of equal size can cancel out; wrong dates or merchant names do not change the balance at all. Count the source rows and review the individual fields. If Sonomir says "No transactions were found", make sure the upload includes the itemised activity pages rather than only a payment summary.

A three-page card statement with two free pages available costs $0.25 at the $5-pack rate or $0.30 at the $3-pack rate, with downloads included. The minimum purchase is $3 and unused credits remain. Frequent statement conversion may cost less with a subscription; ProperSoft offers local desktop processing. Actual imports of Sonomir's card files remain untested. Compare QBO and QFX, and use the old statements guide when rebuilding a missing period.

Upload a bank statement — the PDF your bank emailed, a scan, or phone photos of the pages — and every transaction comes back as a row: date, description, money out, money in, a signed amount and the running balance. Transactions from every page land in one table, so a twelve-page statement is one list, not twelve fragments to stitch together.

Then comes the part that matters: the tool checks its own work. It adds up what it read and compares the result with the balances printed on the statement. When they agree to the cent, the extracted amounts are consistent with those balances. Offsetting errors can still cancel out, so a passing check is a useful review aid, not proof of accuracy. When they do not, it tells you by how much and flags the rows where the running balance breaks, so you check three lines instead of three hundred.

Two independent checks run on every statement.

1. Opening + money in − money out = closing. The opening and closing balances are read from the statement's summary or its first and last lines. If the transactions read in between do not produce the closing balance exactly, something is missing or wrong, and the difference is shown.
2. Row by row. Where the statement prints a running balance, each one must equal the previous balance plus that line's money in minus its money out. A break points straight at the problem: the flagged row, or the one just above it.

The arithmetic is done in whole cents, never in floating point, so a check cannot pass by rounding. Statements listed newest-first are recognised, and so are card and loan statements, where the balance is money owed and runs the other way.

A passing check shows that the extracted amounts agree with the balances that were read. It cannot rule out offsetting errors, omitted pairs of transactions, or incorrectly read balances. Check dates and descriptions, compare the row count with the source, and review important amounts before importing.

The Excel workbook has three sheets:

• Transactions — one row per transaction, in the order printed, with the page it came from and a Check column that says why a row was flagged.
• Balance checks — each check, whether it passed, and the numbers behind it.
• Statement summary — bank, the last four digits of the account, period, currency, opening and closing balances, totals, and whether it reconciles.

Amounts are stored as numbers, not text, so SUM works straight away. Dates are written as year-month-day when the statement makes the year clear, which sorts correctly everywhere. Choose the full transaction CSV to keep the review columns, or a QuickBooks Online, Xero or YNAB CSV layout for its documented import fields. All layouts share one CSV purchase for the same result. Accounting layouts leave out balances and check notes; each statement has a separate file, and multiple files download as a ZIP.

Upload several PDFs at once — twelve monthly statements, say — and they come back in one workbook with a Statement column, plus a summary row for each.

A PDF downloaded from online banking often already contains its text. That text is read with its printed column positions before a model turns it into records. This avoids recognising letters and digits from pixels, but the model can still misinterpret a column or a wrapped description.

A scanned statement, or photos of printed pages, is read from the image. That works well on a flat, straight, well-lit page. It struggles with faint thermal-style printing, pages shot at an angle, and folds across the amount columns. The balance check is your safety net here: if a digit was misread, the running balance breaks at that row.

Photos uploaded together are treated as the pages of one statement, in the order you chose them. Each PDF is its own statement.

It is built for current, checking and savings account statements, and reads card and loan statements too. It is not built for investment or brokerage statements, where a row is a holding rather than a movement of cash. If your bank locks its statements with a password, enter it when the page asks: the PDF is unlocked in your browser, the password never leaves your device, and only the unlocked copy is uploaded. Without the password the tool cannot open it and will not try to get around it.

It has not been tested against a named list of banks, and this page will not pretend otherwise. Statement layouts vary enormously; what the tool offers instead is a result you can verify. If the checks pass, the extracted numbers agree with the balances read from the source. If they fail on your bank's layout, the job tells you so plainly.

We compared the model's extracted rows with labelled, fictional statements: separate debit and credit columns, signed amounts, German decimal commas, Indian number grouping, wrapped descriptions, a dense multi-page list, a credit card, scans and phone photos. These are synthetic examples, not a certification for any named bank.

The eight text-PDF cases and two scanned-PDF cases matched every labelled date, description, amount and direction in this run. A photographed statement lost a digit from two transaction descriptions even though its balance checks passed. Review the source rows, especially long reference numbers in photos. Results can vary between runs; this test does not establish an accuracy percentage for your files, mixed-currency support or successful imports into accounting software.

Compare QBO, QFX, OFX and QIF before importing. The Xero CSV page explains its preset, while password-protected statements covers opening a PDF with your own password. For spreadsheet review, use Google Sheets. Each route uses the same converter; no accounting-app import pass is claimed. Still need the statement itself? How to extract a bank statement covers downloading it from online banking, and getting a year of statements ready for your accountant covers tax-season batches.

Statements are sensitive, so here is exactly what happens. The uploaded file is sent to the reading model and deleted from storage when the job ends, whether it succeeded or not. Only the last four digits of an account number are kept. The transactions you see are stored with your job so the download still works if you come back later; use Delete this result to remove it sooner. Nothing you upload is ever published. To weigh this against other converters, see is it safe to use a bank statement converter?

The first 2 pages a day are free, with the balance checks, and you can copy every row you see. That is enough to see whether the tool reads your bank's layout correctly before you pay anything.

Past that, pages are $0.25 each (5 credits, at the $5-pack rate), and a statement with paid pages gets every download free: Excel, CSV, QBO, QFX, QIF and OFX. With the two free pages still available, a six-page statement costs 20 credits for the other four pages, workbook included. If you have no credits, the smallest purchase is $3 for 50 credits, before any applicable tax; the statement uses $1.20 of it and 30 credits remain. A statement that fits inside the free pages downloads as Excel or CSV free; QBO, QFX, QIF and OFX are 2 credits, once per job. Credits never expire, there is no subscription, and a job that fails is not charged.