How to Import Bank Statements into Wave from a PDF
Wave does not accept a PDF statement. Its uploader reads OFX, QBO, QFX, ASO and CSV files, and a printable PDF from your bank is none of those — so every PDF has to become a file first. Once you know Wave's rules, it is a short job: the free Starter plan uploads statements by hand, bank connections sit on the paid Pro plan, and a connected feed only reaches back 30 to 60 days. This guide shows how to import bank statements into Wave from a PDF: convert the file with a bank statement converter, shape it to Wave's strict three-column CSV, upload it, and check that what landed matches the statement.
When you need to import bank statements into Wave by hand
Use a manual upload when the automatic routes cannot give you the lines. The three common cases are history older than a month or two, a bank Wave cannot connect to, and a statement that exists only as a PDF. Wave connects to banks through Plaid, but connecting a bank account is part of the paid Pro plan, and even a connected feed only fetches recent activity — Wave's own help points to statement upload for anything older than 30 to 60 days. On the free Starter plan, manual upload is not a workaround; it is how transactions get in.
The other reason to upload by hand is control. A feed brings in whatever it finds, whenever it finds it. A file covers exactly the statement period you choose, for exactly one account, and you can check it line by line before Wave ever sees it. That matters most during a cleanup — a new client, a year of unfiled statements — where a mistake imported in bulk is far harder to undo than one caught in a file.
- Write down the missing date range for one bank account before you start.
- Keep each bank and card account in a separate file — Wave imports one account at a time, and the file must be in the same currency as that account.
- Keep the original PDF beside the converted file, so any row can be traced back to the page it came from.
- Import one month at a time for a long cleanup, rather than a whole year in one file, so a mistake stays small.
What Wave accepts, and what your PDF becomes
Wave accepts OFX, QBO, QFX and ASO files, and CSV as the fallback. Wave's own help says the four structured formats are easier to import than a CSV and recommends them where possible — they carry dates, amounts and descriptions in a fixed structure, so there is no column mapping. But a bank that only gives you a PDF gives you none of those formats either, which is why this guide follows the CSV route: it works for every bank and every period, and a CSV can be checked before upload.
| Route | When to use it | What to watch |
|---|---|---|
| CSV (recommended here) | Any bank, any period; the route this guide follows | Wave is strict about columns, dates and signs — shape the file first |
| OFX | You import the same account every month and want no column mapping | A paid export on this site (Starter and Pro); Wave reads dates and amounts directly |
| Bank connection (Pro) | Live transactions from a supported bank, recent weeks only | Paid Pro plan; only reaches back 30 to 60 days |
| Manual entry | A handful of missing lines, not a whole statement | Slow and error-prone for a full month |
Do not upload the PDF itself, and do not paste statement rows into a spreadsheet by hand. Copying by hand is where transposed digits and skipped lines come from, and a spreadsheet saved as .XLS still has to be re-saved as CSV before Wave will read it. Our comparison of OFX, QBO and QIF formats explains when each format earns its place.
Step 1: Convert the PDF to a file Wave can read
Wave cannot read a PDF statement, so convert the PDF first. Drop it into the bank statement converter and review every row against the PDF page before you download anything. Check the balance result: opening balance plus money in, minus money out, should equal the closing balance printed on the statement. That check is the whole point of converting through a tool that verifies balances, rather than copying numbers by hand.
A balance check matters more for Wave than for a spreadsheet. A spreadsheet error stays visible on screen; a wrong line inside Wave gets categorised and can end up on a report before anyone notices. Our guide on how to check a bank statement conversion explains the test, and our guide to why a bank statement does not balance covers the common causes when the numbers refuse to agree.
- Convert one account and one statement period per file — never mix two accounts in one CSV.
- If the PDF is a scan, confirm the converter read it with OCR and check the figures, not just the dates: OCR misreads digits more often than words. Our guide to scanned vs digital bank statements explains the difference.
- If the PDF is password-protected, unlock it once for the conversion; the password is used to open the file and is never stored. See our guide to password-protected bank statement PDFs.
- If you have a year of statements, convert them in batches and import month by month — our guide to converting multiple bank statements at once shows how to keep the batch organised.
Step 2: Shape the CSV to Wave's three-column layout
Wave's CSV importer is simple because it is rigid. A file must have three or four columns: a date, an amount — in one column, or one column each for deposits and withdrawals — and a description. Nothing else. A normal statement conversion gives you those three, plus a running balance, so the shaping step is mostly deletion. Download CSV from the bank statement converter, then reshape it to the layout below. Keep the header row: Wave's mapping screens read the headers to offer the match.
| Converted file | Wave CSV | Notes |
|---|---|---|
| Date column | Date | Year first: YYYY-MM-DD or YYYY/MM/DD; full month names or 3-letter names also work |
| Money in + money out | Amount (signed) | One column: deposits positive, withdrawals negative, two decimal places |
| Description / narrative | Description | Must contain words — a column of cheque numbers alone is rejected |
| Running balance | Remove | Wave does not need it on import, and it is not a transaction |
| Summary and header rows | Remove | Opening balance, totals and fee notes are not transactions |
- Delete every column except Date, Amount and Description — a file with more than four columns is refused with "Wave is having difficulty reading the file you uploaded".
- Use one date column only. Two date columns, such as transaction date and posting date, cause a date error — keep one and delete the other.
- Dates cannot be in the future, and one format must run through the whole file. A bank export in MM/DD/YYYY needs converting to year-first first.
- Remove currency symbols, commas inside numbers and blank rows, and keep one transaction per row, even when the PDF wrapped its description over two lines.
- Save the file with a short name such as month-year-account.csv — Wave notes that a long file name can itself cause an error.
- One currency per file. Wave takes the currency from the payment account you pick at upload, not from the file, so split a statement that mixes currencies and upload each part into an account in that currency.
Step 3: Get the signs right — bank accounts and credit cards run opposite
This is the trap that catches the most Wave imports, because the rule flips by account. For a bank account, money in is positive and money out is negative — use a minus sign or brackets for the negatives. For a credit card, Wave reverses it: purchases must be positive, payments to the card negative. A converted statement usually signs both kinds of account the same way, so a card file needs its signs flipped before upload.
| Row | Bank account | Credit card |
|---|---|---|
| Money in / deposit | Positive | Negative (a payment to the card) |
| Money out / purchase | Negative | Positive |
| How to mark a negative | Minus sign or brackets | Minus sign or brackets |
The date rule flips too, in a smaller way. For a bank statement, pick the transaction date — the date you made the purchase. For a credit card statement, pick the posting date — the date the bank took the money from the card. Wave asks which date column to use during the upload, so decide before you start, and make sure the column you keep is the right one of the two.
Step 4: Import bank statements into Wave, step by step
- In Wave, add the payment account first if it is not there yet: the upload goes into an existing bank or credit card account, under your Chart of Accounts.
- On the left-side menu, click Accounting, then Transactions.
- At the top right, click More and choose Upload transactions.
- Under Statement, click Choose File and select your CSV. (On Starter or Pro, download OFX from the converter instead — Wave then skips the mapping screens and reads the file directly.)
- In the Payment account field, pick the bank or credit card account the statement belongs to. The statement must be in the same currency as that account.
- Click Upload.
- On the Select date page, choose the column with the date Wave should assign to each transaction — the transaction date for a bank account, the posting date for a credit card.
- On the Select amounts page, choose the column with the amounts you paid into or charged to the account.
- On the Select description page, choose the column with the best description for your transactions.
- On the Confirm import page, check the columns are highlighted correctly — dates the right way round, withdrawals negative for a bank account — then click Upload my statement. The transactions land on your Transactions page.
If you upload an OFX file and Wave answers that it needs a small change to the file, open the file in a text editor and switch the encoding line — ENCODING:USASCII to UTF-8, or UTF-8 to USASCII — then save and upload again. That is Wave's own fix for the one OFX error most people meet. For a CSV, there is no mapping to skip: the three screens above are the import, and the Confirm page is your last chance to catch a wrong column before the lines land.
After the upload: categorise, then reconcile
Importing and bookkeeping are two separate jobs, and keeping them separate is what lets you review the file before it touches the books. Each imported line needs attention: categorise it, match it to an invoice or receipt, or mark it as a transfer between your own accounts. Work through the oldest transactions first, and reconcile the account as you go. If the Wave balance for the month does not match the PDF closing balance, the file was wrong before Wave saw it — go back to the conversion check rather than fixing lines one by one inside Wave.
The same discipline applies whatever system you use. Our guides to importing bank statements into Xero, importing bank statements into QuickBooks, importing bank statements into Sage, importing bank statements into FreeAgent and importing bank statements into Zoho Books follow the same pattern — clean, balance-checked file, the target system's own layout, a defined date range, review before reconcile. And if you reconcile in a spreadsheet first, our guide to reconciling a bank statement in Excel after converting PDF to CSV shows how to catch conversion errors before they reach any accounting system.
Duplicates, date errors and other import problems
| Problem | Likely cause | What to do |
|---|---|---|
| "Wave is having difficulty reading the file you uploaded" | More than four columns, or a totals row in the file | Keep only Date, Amount and Description; delete balance and totals rows |
| Dates are a month and day swapped | File uses MM/DD/YYYY but Wave read it year-first | Reformat all dates to YYYY-MM-DD and re-import |
| Money out shows as money in | Signs are reversed for the account type | Flip the signs in the file — remember cards run opposite to bank accounts |
| Credit card purchases land as payments | Card file signed like a bank file | Make purchases positive and payments negative, then re-import |
| The same lines appear twice | The period overlaps a bank connection or a previous import | Start the next file the day after the last transaction already in Wave |
| A description is rejected | The description column holds numbers only, such as cheque numbers | Add words to the description — a payee name or short note |
| Currency mismatch | The file mixes currencies, or the account is in another currency | Split one file per currency and upload each into an account in that currency |
| Upload fails on the file name | An over-long file name | Rename to something short, such as month-year-account.csv, and try again |
Before you upload a second month, check where the first one ended. Open the Transactions page, find the last imported date for that account, and start the next file the day after. Overlap is how duplicates happen — a feed that caught a few days, a month imported twice. That loop — convert, balance-check, shape, import, verify — turns a shoebox of PDFs into monthly imports you can prove, one statement at a time.
Sources and further reading
- Upload a bank or credit card statement in .csv format — Wave Help
- Upload bank and credit card statements — Wave Help
- Accounting made easy — Wave Help
- Import a Bank Statement PDF into Wave — GetLedgerReady
Put it into practice
Convert a statement now and watch the balance check run on your own file. The first 10 pages each month are free, and exports are never cut short.
More guides
How to Convert a Bank Statement PDF to CSV · How to Convert a Bank Statement PDF to Excel · How to Import Bank Statements into QuickBooks (QBO Files) · OFX vs. QBO vs. QIF: Which Format Should You Download? · Why a Converted Bank Statement Does Not Balance — and How to Fix It · How to Check a Converted Bank Statement Is Correct · Scanned vs. Digital Bank Statements: Why One Converts and the Other Does Not · How to Convert a Password-Protected Bank Statement PDF · How to Convert Many Bank Statements at Once (and Merge Them Cleanly) · Is It Safe to Convert Bank Statements Online? A Privacy Checklist · How to Import Bank Statements into Xero · How to Reconcile a Bank Statement in Excel After Converting PDF to CSV · How to Import Bank Statements into Sage from a PDF · How to Import Bank Statements into FreeAgent from a PDF · How to Import Bank Statements into Zoho Books from a PDF