Import a Bank Statement Into ZipBooks (CSV)

ZipBooks imports a CSV, not a PDF

ZipBooks, the free-to-start accounting app, brings transactions in two ways: an automatic bank connection, and a CSV upload for when that is not an option. What it does not read is a PDF, which is a printed statement rather than rows of data. So when your bank only gives you a PDF, or you are importing history the connection did not pull, the statement has to become a CSV first. Converting it produces that file, and then the ZipBooks import tool can take it, which is how a month of transactions gets into your books without hand-entering each line.

Paste into the ZipBooks template

ZipBooks is specific about the CSV: it wants your data in its own template. You copy each column from your converted file into the matching column of the ZipBooks import CSV, and the rules are strict, do not change the header line, add no extra formatting, and fill every field. Then you click Choose File, select the CSV, and click the Import button. Because a converted statement comes out as clean, separated columns, dropping them into the template is a quick copy rather than a reformatting exercise, and the strict header keeps the import from rejecting the file.

Categories must already exist, named exactly

One ZipBooks rule catches people: the Category column is optional, but if you do fill it in, the category has to already exist in ZipBooks and be named exactly as it is there. A category that does not match will not map. So the simplest approach is to leave Category blank in the CSV and assign categories inside ZipBooks after the import, where you can pick from the real list, or to set your categories up first and match the names precisely. Either way, the converted transactions carry the date, description, and amount, and categorization happens against ZipBooks' own list.

Import versus bank connection, and reconciling

ZipBooks can connect to your bank through its Manage Banks feature, which covers ongoing activity, so the CSV import is for what that misses: a bank it cannot connect, or transactions older than the feed brought in. Once the transactions are in, ZipBooks reconciles by having you check off each one that appears on your bank statement, and it tells you how many and what total remain unverified. A converted statement that matches the bank exactly makes that tick-and-verify pass quick, since every line you are checking against is accounted for.

Accuracy and privacy

Because ZipBooks requires every field filled and a clean header, the file you paste in has to be tidy, and every transaction is reviewable in the converter before export so a misread does not break the import. The output drops cleanly into the ZipBooks template. Since the statement holds real account activity, the file is processed to build the CSV and then deleted automatically, with nothing retained on a server afterward, so the transactions end up only in your own ZipBooks account.

Frequently Asked Questions