How to Import Bank Statements into Wave

When you need to import a bank statement into Wave

Wave is popular with freelancers, contractors, and small business owners because it keeps bookkeeping workflows lighter than enterprise accounting tools. Manual bank statement import becomes useful when a connected account is unavailable, a feed misses older transactions, a client sends historical PDFs, or a business owner needs to catch up on several months of activity.

Most bank statements arrive as PDFs. Use the PDF as the official source record, then convert it into spreadsheet rows, review the extracted transactions, and prepare a simple CSV file for Wave.

This guide focuses on that path: PDF bank statement to reviewed CSV or Excel, then CSV import into Wave. The goal is to create rows that are clean enough for bookkeeping review, categorization, cash-flow checks, and accountant handoff.

Wave CSV format requirements

Wave-style CSV imports are easiest when the file is simple. A practical CSV usually uses three columns: Date, Description, and Amount. The amount column is a single signed column. Outgoing money should be negative, and incoming money should be positive. This differs from some accounting tools that accept separate debit and credit columns.

Dates should be consistent. Use a format that Wave accepts in your account, commonly MM/DD/YYYY or YYYY-MM-DD. Descriptions should be readable and specific enough for later categorization. Amounts should be plain decimal numbers. Remove currency symbols, thousands separators, parentheses for negatives, and extra text from the amount column.

During review, it is fine to keep extra columns such as balance, reference, check number, card suffix, category, receipt needed, or question for accountant. The final Wave import copy should be simpler than the review workbook. Keep the working file for your records, then save a clean CSV for import.

PDF to CSV workflow for Wave

1. Start with the statement period.

   Use the monthly PDF that matches the period you want to update in Wave. Confirm the account, opening date, closing date, and currency.

2. Convert the PDF to CSV or Excel.

   Use BS Conv to extract the transaction table. Export Excel first if you want to review categories, add notes, or check totals before creating the final CSV.

3. Review the extracted rows.

   Compare the first transaction, last transaction, one large debit, one large credit, and the ending balance where available.

4. Simplify the import copy.

   Keep Date, Description, and Amount. Remove helper columns, statement summaries, repeated headers, blank rows, and disclosure text.

5. Import the CSV into Wave.

   Use Wave’s CSV import workflow, review the preview, confirm signs and dates, then import the transactions into the correct account.

How to import the prepared CSV in Wave

Wave’s exact navigation can change, but the import workflow is typically inside the banking or connected accounts area. Open the account that should receive the transactions, choose the CSV import option, upload the prepared file, and review the preview before completing the import.

Use the preview as a quality gate. Confirm that dates are recognized, outgoing payments are negative, incoming deposits are positive, descriptions are readable, and the imported period is separate from transactions already in Wave. If the preview needs work, fix the CSV before importing.

After import, review categories and matches. Wave is often used by freelancers and small businesses, so the most important rows are usually client payments, payment processor deposits, software subscriptions, office expenses, bank fees, refunds, transfers, and owner draws. Imported data gives that review a cleaner starting point.

Common Wave import errors and fixes

Tips for regular Wave imports

Keep a simple folder structure for recurring imports. Store source PDFs, review workbooks, and final CSV files by year, month, business, and bank account. Clear naming prevents duplicate imports and makes it easier to answer accountant questions later. A useful file name includes business name, bank, account suffix, statement period, and status.

Import one period at a time. Monthly chronological processing makes missing periods, duplicate periods, and reconciliation issues easier to see. If your bank provides a complete CSV for the exact same period, use it. If the reliable source is only a PDF, convert it, review it, and keep the PDF with the import file.

Keep business and personal review decisions in the workbook first. If a row may be an owner transfer, personal expense, refund, or duplicate payment processor deposit, mark it before import. Then import the clean transaction file and finish categorization inside Wave.

Wave versus heavier accounting tools

Wave is often a good fit for freelancers and small teams because the bookkeeping workflow can stay simple. That simplicity makes CSV quality more important. A clean three-column CSV is easier to import and review than a complicated workbook full of helper fields.

If your business needs advanced bank feeds, multi-entity controls, approval workflows, or specialized accounting imports, tools such as QuickBooks, Xero, or Zoho Books may be a better fit. If the goal is practical small-business bookkeeping from historical PDF statements, a reviewed CSV workflow can be enough to get Wave back in sync with the source records.

Best fit for Wave users

This workflow is best when a freelancer, contractor, or owner has PDF statements and needs a spreadsheet starting point for bookkeeping. It is also useful for catch-up bookkeeping, tax prep, payment processor review, and months where a connected account did not pull every transaction.

The safest path is convert, review, simplify, import, preview, and categorize. That sequence gives small business owners the speed of automation without giving up the source checks that protect the books.