Skip to content

Free tool

Bank statement to CSV or Excel. No account needed.

Upload a PDF statement and get the transactions back as rows you can reconcile against, sort and total. Works on text-based and scanned PDF statements.
Convert a statement

Converting something other than a statement? Use the PDF converter.

Convert a bank statement

Drop in a PDF statement, text-based or scanned. The extractor reads the transaction table across every page and returns rows you can open in Excel or import to your ledger.

What you get

Ungated, and it deletes your file.

This tool is the front door to Mammoth. Use it on its own, or carry the extracted data into a pipeline that runs every week.

  • No account required

    Upload and extract straight away. Your file is processed and deleted within an hour.

  • Every page, not just the first

    Statements run long and the transaction table continues across pages. The extractor reads the table on every page and keeps the headers, rather than returning page one and stopping. One file at a time, up to 100 pages.

  • It is the PDF converter

    There is no separate bank-statement engine and no list of supported banks. A statement is a PDF, and this is the same extractor as the PDF page — which is worth knowing before you upload rather than after.

Questions people ask

Is this built for bank statements specifically?
No, and it is worth being straight about that. This is the same PDF extractor as our PDF to CSV page, pointed at a statement — there is no bank-specific parser behind it and no list of supported banks. That cuts both ways: it will not have a hand-tuned template for your bank, and equally it does not care whether your bank is on anyone's list. It reads the table it finds.
Do I get an Excel file, or a CSV?
A CSV. Excel opens it directly — double-click and it lands in a sheet — and CSV is also what most accounting packages want on import, so it is usually the more useful of the two anyway. If you specifically need an .xlsx workbook, Save As once it is open gives you one. The page says CSV or Excel because that is the outcome either way; the file the converter hands back is a CSV.
Should I just use Excel's Power Query instead?
Sometimes, and it is free. If your statement is a text-based PDF with a table that holds the same shape every month, Data > Get Data > From PDF in Excel will pull it and you can refresh it next month. Where it struggles is scanned statements, layouts that change between months, and statements that split a transaction across lines. Try Power Query first if your statement is clean; come back here if it is not.
Can I not just download CSV from my bank?
If you can, do — it is cleaner than any conversion. The reasons people end up converting anyway are dull and common: the portal only goes back so far, the export is OFX or QIF rather than CSV, the account is closed, or the statement came from an accountant or a landlord as a PDF and there is no portal to log into.
Does it work on a scanned statement?
It reads scanned PDFs as well as text-based ones. A scan is genuinely harder than a text PDF, so check the output against the statement before you reconcile from it — particularly the columns where a stray mark can change a figure. We do not publish an accuracy number for statements, because we have not measured one, and a figure measured on clean structured documents would not be honest here.
What happens to my statement after I upload it?
It is processed and deleted within an hour, and no account is required to use the converter, so there is nothing to sign up for and nothing kept. If you would rather not upload a statement at all, the Power Query route above keeps the file on your machine.
I have twelve months of these, across three accounts.
That is the point at which a converter stops being the answer. Converting one file by hand is a two-minute job; doing it every month for several accounts and joining the results is a pipeline. Mammoth is the platform underneath this tool — the same extraction, plus the cleaning and joining recorded once so next month's statements land in the same shape without anyone rebuilding the steps. Uploading each new statement and replaying that recipe works on every plan; having Mammoth collect the files and run it on a schedule is a Pro feature.

Extracting once is useful. Extracting every week is the point.

Bring the output into Mammoth to clean it, join it to everything else, and have it delivered on a schedule.

  • 21-day Pro trial
  • No credit card
  • Viewers always free