Convert bank statement PDF to CSV on iPhone (2026)

To convert a bank statement PDF to CSV on iPhone, send the statement from Mail or Files to a converter that reads the transaction table and writes one row per transaction: date, description, and a signed amount, with money out negative. Save the CSV to Files. Before you import it anywhere, check that the opening balance plus the sum of the amounts equals the closing balance printed on the statement.

The app that does this on iPhone is ignitai. It reads the statement on the phone with Apple’s built-in text recognition, and an AI turns the recognized text into exactly the columns your plain-English instruction names. The PDF stays on the iPhone; only the recognized text goes to ignitai’s servers, where the CSV is built. Your first document, up to 4 pages, converts free, which covers a typical short monthly statement.

In this guide12 sections

Why statements fight a plain copy and paste

Copying the transaction table out of a statement PDF and pasting it anywhere gives you lines of text, not columns. Even after you split them by hand, statements carry four traps:

• Wrapped descriptions. Many banks print a transaction over two or three lines: the merchant, then a location or reference, then a foreign-currency note. A CSV needs one row per transaction, not three.
• Two amount columns or one. Some statements print separate Withdrawals and Deposits columns; others print one Amount column and mark debits with a minus sign, parentheses or DR. Importers want a consistent convention, usually one signed column.
• The running balance. It sits right next to the amount and looks just like it. Pick up the wrong one and every row is plausible and wrong.
• Everything that isn’t a transaction. The account summary, interest and fee boxes, page headers repeated on every page, and the marketing insert at the back.

Getting those right is what turns a statement into a file an importer accepts on the first try.

Convert a bank statement PDF to CSV on iPhone: the steps

1. Send the statement to ignitai. Open the PDF in Mail or Files, tap Share, and choose ignitai. If you saved the statement from your bank’s website, it is usually in Files ▸ Downloads. A paper statement can be scanned with ignitai’s camera instead.
2. Describe the columns. A prompt is required, so Convert stays disabled until there is one. Start from the Table starter or type your own; the instruction in the next section works on most US and European statements. Saved instructions are one tap away next time, so next month’s statement is a share and a tap.
3. Choose CSV and convert. ignitai shows how many pages the run will use and how many you have left before it starts. Converting needs an internet connection and is usually ready in under a minute. Progress shows on the Lock Screen and in the Dynamic Island, and a notification arrives when the file is ready.
4. Check the table. Tap the amount column heading to see its total, average, minimum, maximum and count; the next sections explain what each tells you. Rows are numbered, Original Pages shows the statement page to compare against, and if a column came back empty, ignitai says so.
5. Share the CSV to Files. Share… is in every finished file’s menu. Save to iCloud Drive if you will run the import from a Mac or iPad, which for most tools you will (more on that below). Cells are edited in a spreadsheet app, not in ignitai.

Get ignitai on the App Store — free download; your first document (up to 4 pages) converts free with Sign in with Apple, and one subscription covers iPhone, iPad, Mac, and Vision Pro.

An instruction that produces an import-ready CSV

“One row per transaction. Columns: date (YYYY-MM-DD), description, amount. Amount is a signed number: negative for withdrawals, card payments and fees, positive for deposits and refunds. Join a description that wraps onto several lines into one cell. Skip the account summary, page headers, the running balance and any non-transaction pages.”

What each part does:

• “Signed number” with both directions named. Saying which transactions are negative and which are positive removes the most common import error, a statement read with every sign flipped, which doubles your apparent spending in a budgeting app.
• ISO dates. 2026-09-14 cannot be misread as 9 February or 14 September in another order, and most importers recognize it.
• Joining wrapped lines. One transaction, one row. Keep the reference text in the description; it is often the only way to match a transfer later.
• Skipping the balance. The running balance is for checking, not importing. Leave it out of the CSV and use the statement’s printed opening and closing balances to check the file.

Two variations come up often. If your importer wants separate money-in and money-out columns, ask for date, description, credit, debit with both as positive numbers and the other cell left blank. If you need to keep several accounts apart in one file, add account_last_four and statement_period, taken from each statement’s own header.

Shape the CSV for the tool that will import it

Every importer has its own rules, and the fastest route is to read them first, then name those exact columns in your instruction. The rules for three common destinations, from their own help pages as of October 2026:

Two practical notes. Strip currency symbols and thousands separators from amounts by asking for “amount as a plain number, no currency symbol, no thousands separator”. And if a year of statements runs past an importer’s per-upload limit, split the CSV by month or quarter before uploading.

Where the import actually happens

This is the part iPhone guides tend to skip: the CSV is easy to make on the phone, but many tools don’t take file imports in their iPhone apps. YNAB’s help pages say file-based import works in its web app and on iPad, not on iPhone. QuickBooks Online’s upload lives in Bank transactions in its web version. Check your own tool’s help page before you plan the workflow around the phone.

The practical pattern:

1. Convert on the iPhone, where the statement arrived.
2. Save the CSV to iCloud Drive in Files.
3. Run the import from a Mac or iPad browser, where the file is already waiting.

If you want to look the file over first, Numbers on iPhone opens a CSV directly. The finished file is also in your ignitai account, so after you sign in with Apple on the Mac or iPad, it is there too.

Check the CSV before it touches your books

An import is hard to undo cleanly, so check before you upload. Four checks, and the first three can happen inside ignitai on the phone before you export:

1. The balance tie-out. Opening balance plus the total of the amount column must equal the closing balance printed on the statement, to the cent. Tap the amount column heading to see the total, and compare it with closing minus opening. A match means every transaction is there with the right sign. A miss is a missing row, a duplicated row, or a flipped sign.
2. The count. Many statements print the number of deposits and withdrawals in the summary box. The count under the amount column heading, or the last row number, should match their sum.
3. The extremes. The minimum in the amount column should be your largest withdrawal and negative; the maximum should be your largest deposit, probably your pay. If the minimum is positive, the signs are flipped; fix the instruction and convert the statement again. A rerun uses pages again, so prove a new instruction on a short statement first.
4. Dates. Open the CSV in Numbers and sort by date. Every row should fall inside the statement period.

When the tie-out misses, the difference usually points to the cause. A difference equal to one transaction is a missing row; twice a transaction is a flipped sign. Find that amount, compare the row with Original Pages, and either fix the cell in your spreadsheet app or adjust the instruction and run it again.

A year of statements into one CSV

For taxes or a new budgeting app, you often need a year at once. In ignitai, choose the twelve statement PDFs from Files and convert them as one batch with the same instruction; the output is one CSV, one row per transaction across the whole year. Filenames don’t carry into the output, so add statement_period (and account_last_four for more than one account) to the instruction to keep every row attributable to its statement.

Mind the page count. The subscription includes 80 pages a week, up to 320 a month, and unused weekly pages don’t carry over. Twelve six-page statements is 72 pages, which fits in one week. Three accounts over a year doesn’t, so spread them over a few weeks or buy extra pages, which never expire. ignitai shows the page count before every run, and cancelling while it is still running charges nothing.

If one file fails, ignitai says why. A password-protected PDF is named rather than silently skipped; unlock it and run the batch again. Convert Again restarts a failed or cancelled run with the pages kept.

Before you convert: check what your bank and your tool already offer

• Your bank’s own export. Most online banking offers a transaction download as CSV, QFX or OFX for recent activity. If it covers the period you need, use it; it is the bank’s own data. The PDF route is for older periods past the download window, closed accounts, and statements someone emailed you.
• QuickBooks Online’s statement upload. QuickBooks Online now accepts an account statement as a PDF or image, as long as it is in English, alongside CSV, QBO and QFX files. If QuickBooks is your only destination, try that first. The CSV route still helps when you want to check every row before it reaches the books, when the same data has to go to more than one tool, or when the statement isn’t in English.
• Web converters. Plenty of sites convert a statement PDF to CSV. They work; the difference is what they receive. A web converter receives the whole PDF. ignitai receives the text recognized on your iPhone, which includes the transactions and account details, and keeps the finished file in your account until you delete it. Free tiers are also usually capped by files or pages per day.

Doing it by hand on iPhone

For a one-page statement, you can copy the transaction lines from the PDF in Files, paste them into Numbers, split the columns by hand, and export with Share ▸ Export ▸ CSV. This only works on statements with a text layer (not scans), and wrapped descriptions and two-column amounts all need manual repair. It is fine for ten rows and a slog for a hundred.

On iPad and Mac

The Mac CSV walkthrough covers a year of statements dragged in at once and the import into QuickBooks Online and Xero on a full-size browser. The iPad CSV guide covers the same job with a bigger screen and sorting in the table. If you want Excel rather than CSV, the iPhone Excel guide uses the same steps with Excel output, where amounts arrive as real numbers ready to total. For investment accounts, the brokerage-statement guide for iPhone has an instruction built for positions and dividends.

Bottom line

On iPhone, the statement PDF is usually already in Mail or Files. Share it to ignitai, ask for one row per transaction with a signed amount and ISO dates, pick CSV, and tie the column total to the printed balances before you export. Then run the import from wherever your tool accepts files, which for many tools is a Mac or iPad browser. Use your bank’s own CSV export when it covers the period, and QuickBooks Online’s PDF upload if QuickBooks is the only destination.

Get ignitai on the App Store — free download; your first document (up to 4 pages) converts free with Sign in with Apple, and one subscription covers iPhone, iPad, Mac, and Vision Pro.

FAQ

How do I convert a bank statement PDF to CSV on iPhone?

Send the statement from Mail or Files to ignitai, describe the columns (date, description, and amount as a signed number), choose CSV and tap Convert. It is usually ready in under a minute. Save the CSV to Files, then import it wherever your budgeting or accounting tool accepts files.

Does the statement leave my iPhone?

The PDF stays on the phone. ignitai reads it on the iPhone and sends only the recognized text, transactions included, to its servers, where the CSV is built. The finished file is stored in your ignitai account until you delete it.

How do I check the CSV is accurate?

Add the opening balance to the sum of the amount column; the result must equal the printed closing balance to the cent. On iPhone, tap the amount column heading in ignitai to see that sum before you export. If it doesn’t tie out, compare the rows with Original Pages and look for a missing or wrong-signed transaction.