Turn a bank statement into a spreadsheet, without uploading it
Most bank statement converters work by uploading your statement to a server. You can extract dates, descriptions, amounts and balances into a CSV entirely on your Mac instead, including from scanned statements. Vocemo does this for $15 a month; the dedicated converters run roughly $20 to $49 a month and require the upload.
- What gets uploaded
- Your full transaction history, account numbers included
- The local alternative
- Extraction runs on your Mac, nothing transmitted
- Works on scans
- Yes, using text recognition built into macOS
- Output
- A CSV with date, description, amount and balance
Why be careful about statement converters specifically?
A bank statement is the single most revealing document most people own. It contains your account number, your income, your address history, your employer, your health spending, your subscriptions and everyone you pay. It is the raw material of both credit scoring and identity theft, in one file, already organised by date.
Compare that with the other things people convert. A recipe PDF leaking is an embarrassment. A statement leaking gives a stranger your salary, your bank, your account number and a map of your life for the past month. The documents are not in the same category, so the habit of dropping a file on the first free converter that appears in search results should not carry over.
The conversion itself is not difficult. It is table extraction from a PDF, a problem that has been solved for years. There is no technical reason it needs a server, which makes the upload a business decision by the vendor rather than a requirement of the job.
Should you just ask your bank for a CSV first?
Yes, and this is the step most people skip. Nearly every retail bank will export your transactions directly, and the export is exact rather than reconstructed, because it comes from the ledger instead of from a picture of the ledger. No extraction tool can beat that, including ours.
Look in online banking for a download or export control near the transaction list, usually beside a date range picker. The formats you will be offered are some of these:
- CSV, which opens directly in Excel or Numbers. Take this one if it is offered.
- OFX or QFX, which are designed for accounting software and carry a transaction type on every row. Most bookkeeping tools import them without any conversion.
- QIF, an older format, still widely accepted.
- MT940, common in Europe for business accounts.
Two limits push people back to the PDF. Many banks only expose the last 90 days, or the last 12 to 24 months, in machine readable form, while PDF statements go back years. And a closed account, or an account at a bank you have left, usually leaves you with nothing but the PDFs you saved. That is when extraction is the only route, and it is a real one.
How does local statement extraction work?
Two cases, depending on what kind of PDF you have.
- A digital statement downloaded from online banking has a text layer already. The extraction reads that layer, finds the dated lines that carry amounts, joins descriptions that wrapped onto a second line, discards the repeated column headers at each page break, and writes the rows out.
- A scanned or photographed statement has no text layer, so text recognition runs first to turn the picture into characters. macOS includes a strong recognition engine, so this also happens on the machine with nothing downloaded and nothing sent.
The awkward part is not reading the characters. It is the layouts, and there is no standard.
What actually breaks when a statement is converted?
These are the failure modes worth knowing about, because most of them produce a file that looks correct and is not. That is more dangerous than an obvious error.
- Date and number formats. European statements write 31.12.2026 and 1.234,56. US statements write 12/31/2026 and 1,234.56. A converter that assumes one silently mangles the other, and the damage is invisible until the totals disagree.
- Descriptions on two lines. A long merchant name wraps, and a naive parser turns one transaction into two rows, the second with no amount.
- Separate debit and credit columns. Many banks use two money columns rather than one signed column. Collapsing them into a single amount without flipping the sign on debits gives you a file where everything is income.
- Negative numbers in brackets. Accounting convention writes a withdrawal as (45.00). Read literally, that becomes positive 45, and your balance runs the wrong way.
- Carried forward balances. The opening balance line and the "balance brought forward" line at each page break are not transactions, but they sit in the same columns and get picked up as though they were.
- Foreign currency lines. A card payment abroad often prints two amounts, the original currency and the converted one. Only one of them belongs in your ledger.
- Repeated page headers and footers. Page two onwards usually repeats the column titles and often the account number, which lands as a junk row unless it is filtered.
- Cheque and reference numbers. These are long digit strings sitting next to money columns, and they are frequently captured as amounts.
None of this is exotic. It is why a statement converter is more than a table reader, and why you should reconcile the output rather than trust it.
Do you need text recognition, and how can you tell?
The test takes five seconds. Open the PDF in Preview and try to select a line of text with the cursor. If the text highlights, there is a text layer and no recognition is needed. If you get a selection rectangle over an image instead, the page is a picture and recognition has to run first.
A statement that was downloaded from online banking is almost always the first kind. One that was posted to you and scanned, or photographed on a phone, is the second. Recognition on a clean 300 dpi scan is close to exact on printed statement type. A phone photo taken at an angle in poor light is where accuracy falls away, so flatten the page, get even light, and shoot straight down.
What do the options cost?
Prices verified September 2026, from each company's own pricing page.
| Option | Uploads your statement | Price | What you get |
|---|---|---|---|
| Ask your bank for CSV or OFX | No | Free | Exact data, but usually a limited date range |
| Vocemo | No | $15 a month, or $144 a year | Unlimited local extraction, scans included, 3 Macs |
| DocuClipper Starter | Yes | $29 a month billed yearly, $39 month to month | 60 pages a month |
| DocuClipper Starter 300 | Yes | $79 a month | 300 pages a month |
| DocuClipper Business | Yes | $159 to $299 a month | Up to 1,500 pages a month |
| MoneyThumb Basic | Yes, or a paid desktop app | $24.95 a month, or $199.95 a year | 5 conversions a month, about $5.00 each |
| MoneyThumb Standard | Yes, or a paid desktop app | $49.95 a month, or $399.95 a year | 20 conversions a month, about $2.50 each |
| MoneyThumb Pro | Yes, or a paid desktop app | $99.95 a month, or $799.95 a year | 60 conversions a month, about $1.67 each |
| Doing it by hand | No | Free | About an hour per statement, and typos |
If you would rather this ran on your own Mac, that is what Vocemo does. Free for 7 days, then $15 a month for 3 Macs.
Download free for MacTwo things to notice in that table. The metered services charge by page or by conversion, so a year of catching up on a shoebox of statements costs far more than the headline monthly figure. And the free route, asking your bank, is genuinely the best answer whenever the date range covers what you need.
What do the upload services say they do with your file?
Read the privacy policy of any converter before you use it, and look for four specific things rather than a general reassuring tone.
- Retention. How long the file and the extracted data are kept. "Deleted after processing" and "deleted after 30 days" are very different promises.
- Sub-processors. Whether the file is passed to another company for recognition or model inference, which puts a second party you did not choose in the chain.
- Training. Whether your documents may be used to improve their models.
- Jurisdiction. Which country the servers sit in, which decides who can compel access to them.
Reputable services answer all four clearly, and some answer them well. The point is that a local tool makes all four questions moot, because there is no copy anywhere to retain, share, train on or subpoena.
How do you check the output is right?
Always check these before using an extracted CSV for anything that matters, whichever tool produced it. This is a five minute job that catches almost every silent failure.
- Count the rows against the number of transactions on the statement.
- Reconcile the balance. Take the opening balance, add every credit, subtract every debit, and compare with the closing balance printed on the statement. If it does not match to the penny, a row is missing, duplicated, or carries the wrong sign.
- Sort by amount and look at the largest and smallest values. A reference number captured as money shows up immediately at the top.
- Sort by date and check the range starts and ends where the statement does.
- Spot check any day above the twelfth of the month, which is the only place a swapped day and month becomes visible.
No extraction tool is exact on every layout, and any vendor who tells you otherwise is selling. Banks change their templates without notice and without telling anyone.
How do you handle several years of statements at once?
The common real job is not one statement, it is 60 of them for a tax year or a mortgage application. A few things make that manageable.
- Do one statement first and reconcile it fully before running the rest. If the layout parses cleanly once, it will parse cleanly for every month of that account.
- Keep one file per account per month rather than merging first. Merged PDFs mix layouts, and a failure in the middle is harder to find.
- Add an account column yourself when you combine the CSVs, or you will lose track of which rows came from where.
- Reconcile each year as a block. The closing balance of December should equal the opening balance of January, which catches any month you missed entirely.
- Expect older statements to be the awkward ones. Bank templates from five years ago are often a different layout from this month's.
Does the same apply to receipts and invoices?
Yes, and it is usually the same job with a different shape of output. Photographs of receipts and invoice PDFs can be read into one row each with the vendor, date, total, tax and currency, and written out as a single spreadsheet for an accountant. The privacy argument is weaker for a coffee receipt and identical for a medical invoice, a legal bill or anything that reveals a client.
Which route should you pick?
In order, stopping at the first one that works for you:
- Ask your bank for CSV or OFX. Free, exact, no conversion at all. This covers most people most of the time.
- Extract locally from the PDFs when the bank will not go back far enough, the account is closed, or you have paper statements. Nothing leaves your Mac.
- A metered upload service if you need features neither of the above gives you, such as direct posting into a specific accounting platform, and you have read what they do with the file.
Whichever you choose, reconcile the closing balance. That single check is worth more than the choice of tool.
Questions
Can I convert a bank statement PDF to CSV without uploading it?
Yes. Table extraction from a PDF is a local computation and needs no server. Software that runs on your Mac reads the statement, extracts the dated rows, and writes a CSV next to the original, with nothing transmitted.
Does it work on scanned or photographed statements?
Yes. A scan has no text layer, so text recognition runs first to read the characters. macOS includes a strong text recognition engine, so this also happens on your machine. Accuracy depends on the scan being straight and in focus.
Will it handle European date and number formats?
It has to, and this is where converters most often fail quietly. 31.12.2026 with 1.234,56 and 12/31/2026 with 1,234.56 must both parse correctly. Always spot check dates above the twelfth of the month, because that is where a swapped day and month shows up.
Is it safe to upload bank statements to a conversion website?
You are sending your account number, income, address history and complete spending record to a third party. Some services are reputable and encrypt properly. The question is whether the convenience is worth transmitting the document at all, when the same extraction runs locally.
Can I download my bank statement as a CSV directly from my bank?
Usually yes, and you should try this first. Most online banking sites offer CSV, OFX, QFX or QIF export near the transaction list. That data comes from the ledger rather than from a picture of it, so it is exact. The catch is the date range: many banks only expose the last 90 days or the last two years, while your PDF statements go back further.
How do I know the converted CSV is correct?
Reconcile it. Take the opening balance, add the credits, subtract the debits, and check you land on the closing balance printed on the statement. If it matches to the penny, no row is missing or wrongly signed. Then sort by amount to catch a reference number captured as money, and check any date above the twelfth of the month.
What fields can be extracted from a statement?
Date, description, amount and running balance for each transaction. Receipts and invoices extract differently, one row per document, with vendor, date, total, tax, currency and document number.
Sources
Every price on this page was read from the vendor's own page on the date shown above. Prices change; if you find one out of date, tell us and we will correct it.
Competitor prices in this article were checked in September 2026. Prices change; if you find one out of date, write to us and we will correct it.