CSV tools for bookkeepers: from bank export to accounting import

A bank or card export is rarely ready for Xero, QuickBooks or Sage. The dates follow the bank’s locale, the amounts may use a decimal comma, a second download repeats last week’s transactions, and payee names arrive with broken accents. Every one of those problems is small, and every one of them can stop an import or post a transaction twice.

The pages below cover that path from download to import. Whichever one you start from, the totals check adds up each amount column before and after cleaning, so you can show a client or a reviewer that no figure moved while the file was being tidied.

The order that works

  1. 1

    If the period spans several downloads, stack them into one file first, so overlapping days show up as repeated rows.

  2. 2

    Repair the text and the layout: broken characters in payee names, padded descriptions and the blank spacer rows some banks insert.

  3. 3

    Rewrite every date in one unambiguous format (YYYY-MM-DD by default, or DD/MM/YYYY or MM/DD/YYYY from the date rule’s settings), and turn decimal-comma amounts into plain numbers.

  4. 4

    Read the removed rows in the preview before you export: two identical card payments on the same day can both be real.

Statements and imports

Start here when the file is a statement you downloaded, or a sheet you are about to load into accounting software.

Dates, amounts and repeated transactions

The three problems that most often change what the ledger shows, rather than just how the file looks.

Guides for bookkeeping files

Why these problems happen, how to fix them by hand in Excel or Google Sheets, and where a tool helps.

Import guides, bank by bank

One bank’s export into one accounting product: the columns each side uses, every mismatch between them, and the help pages and parsers behind each claim.