Card statements, tied out and broken down.
A card statement is not just a list of charges. It is settlement volume, processing fees, chargebacks and refunds — four different things that all look like transactions until you separate them. SheetParser extracts the ledger and reconciles the card balance on the same pass.
First file free, up to 10 pages · paid packs run up to 600 pages per file · files shredded after conversion
Bookkeepers & controllers
Client card statements into the books without retyping, with the balance already proven.
Merchant & MCA underwriters
Read settlement volume as revenue evidence, and see what came back as chargebacks.
Expense reviewers
Separate fees and refunds from real spend before the month is closed.
What this actually fixes
Four things that look identical
Settlements, fees, chargebacks and refunds are all just rows. Summing them as spend produces a number that means nothing.
Multi-page statements with running balances
Page breaks, carried-forward balances and multi-line merchant descriptions break naive extraction.
The card balance never gets checked
Most converters give you rows without proving that opening + purchases − payments = closing.
What comes out
One upload, one set of compute-ready outputs — not a screenshot of a table.
Card balance tie-out
Opening + purchases − payments = closing, recomputed after every row, with breaks flagged where they occur.
Settlements vs fees vs refunds
The four categories are separated so volume and cost can be read independently.
Clean Excel and CSV
One row per transaction, no merged cells, negative and credit amounts preserved as numbers.
Every charge has a page
Click a line to jump to the highlighted region in the source statement.
Native, scanned or photo
Issuer PDFs, scans and phone photos all go through the same reconciliation.
Shareable proof
An optional hash-bound certificate lets a client or reviewer confirm the source document.
Documents we read
Native PDF, scan, phone photo, Word, Excel, PowerPoint, CSV, HTML, email or image.
How it works
Upload the card or merchant statement
One file is one credit, up to 600 pages on a paid pack. Free tier: one file per day up to 10 pages.
Rows are rebuilt and the balance proven
Settlements, fees, chargebacks and refunds are separated; the card balance chain is recomputed.
Export or fold it into the file
Download Excel/CSV, or keep it next to the bank statement report it supports.
Every plan, every audience
- One file = one credit, up to 600 pages on a paid pack
- No merged cells; numbers arrive as numbers
- Every extracted value traces back to its source page
- Files shredded after conversion, never used for training
- A fresh file allowance every billing cycle; cancel anytime
- An optional hash-bound certificate anyone can verify for free
Questions
Which issuers work?+
Amex, Chase, Citi, Capital One and regional business cards are the common cases. A statement with no running balance is reported as such rather than inferred.
Can it tell a chargeback from a refund?+
The rows are extracted faithfully and the description is kept, so the two can be separated. Classification is shown, not silently decided — you can always see the original line.
Is a card statement enough for a lending decision?+
No — it is supporting evidence. The primary input is the bank statement, where deposits and existing funder debits live.
How much is it?+
Per file: $79 for 10, $199 for 30, $499 for 100, each up to 600 pages. First file each day free up to 10 pages.
Do you keep the statements?+
Files are shredded after conversion and never used for training.
Run your next file
Upload the document, get compute-ready output with the source page behind every number. The first file each day is free.