Import PDF Statements into Zoho Books

Do one thing before you upload anything. Check that every transaction balances against the running total on the statement. A file that doesn't reconcile after conversion is hiding a missing or misread line, and importing it means you'll repair your accounts later instead of catching the gap now.

Why Zoho Books rejects the PDF

A bank statement PDF is built for a person to read, not for software to parse. The amounts sit in visual columns that look tidy on screen but carry no structure underneath. So when you try to import one, Zoho Books either refuses the file outright or accepts it and scrambles the rows — dates landing in the description, two transactions fused into one, a wrapped line split across two.

The importer is happiest with a CSV: plain rows, one transaction each, columns it can map to its own fields. That's the file you're aiming to produce. The conversion itself isn't the hard part. The hard part is being sure the converted file holds *every* line the PDF held, which is where the running balance comes in.

Convert the PDF to a Zoho Books CSV

Here's the sequence that holds up across a year of catch-up statements:

1. Gather every PDF you need, oldest to newest, with no months missing. A gap gives you a wrong opening balance, and each import after it inherits that error.
2. Convert each PDF to a spreadsheet. Pull date, description, the money-out and money-in figures, and the balance for every line. Scanned or photographed statements go through OCR first, because there's no text to copy off an image.
3. Check the reconciliation. Recompute opening balance plus money in, minus money out, across the whole statement, and confirm it lands on the printed closing figure. Walk it line by line against the Balance column. The first row where your total stops agreeing with the bank is where a transaction was dropped or misread.
4. Shape the file and download the CSV. Keep Date and Description, decide how you'll express the amount (covered below), and strip currency symbols and thousands commas.

Step three is the one almost every converter skips, and it's the reason it's worth doing. Lifting text out of a PDF is easy. Knowing you lifted *all* of it is the part that protects your numbers. Catch a misread "1,180.00" that should read "1,780.00" while you're still converting and it costs nothing. Chase that same 600 hole through a month you've already reconciled and it costs you an afternoon.

How Zoho Books reads the amount column

This is where Zoho Books behaves unlike Xero or QuickBooks, and where people trip. After you upload, Zoho asks how your file states money in and money out, and it offers three modes. Match the one to your CSV:

Most UK and AU statements print separate money-out and money-in columns, so that shape maps cleanly to Double Column. Zoho labels its two sides Withdrawals and Deposits — money out becomes Withdrawals, money in becomes Deposits. If your file shortened the headings to "Dr" and "Cr", you point them at the right fields on Zoho's screen rather than editing the file.

After the amount mode, Zoho shows a column-mapping preview. Confirm that Date, Description and the amount columns line up with the right fields, and that the date format matches what your CSV actually contains — a DD/MM date read as MM/DD turns a January line into December, the kind of quiet error that surfaces months later. The running-balance column has nowhere to go here. Zoho Books doesn't import a running balance, so use it for your reconciliation check and then leave it out of the file. The Zoho CSV import format guide goes deeper on the exact columns and these three amount modes.

Import the file and reconcile in Zoho Books

Open Banking in the left sidebar and select the account you're importing to (add it first if it isn't listed). Click the gear icon at the top right and choose Import Statement. Upload your CSV, pick the amount mode, confirm the column mapping and the date format, then import. The transactions arrive in the account ready to be categorised, matched to invoices and bills, and reconciled.

Reconciling the file *before* the import is what keeps the work clean. If the CSV already balances opening to closing, you know the month is whole and you're matching a complete set of lines — not hunting for a phantom transaction that never made the jump. The Zoho Books reconciliation guide walks through the matching side once the lines are in.

One honest note, because it matters. Export Bank Statement converts and verifies; Zoho Books imports. There's no certified bank-feed push that shoves a PDF straight into your ledger. If a tool promises one-click API sync from a statement file, be sceptical — the convert-then-import route is the one that actually holds together for older months and catch-up work. Feeds only fetch recent activity anyway, so anything older than a few months has to come in as a file regardless.

Why the running-balance check is the part that counts

Converting the PDF is the straightforward half. Knowing the converted file is *complete* is the hard half, and it's the step nearly everyone leaves out. A tool can hand you a tidy CSV that's quietly short one transaction — and a tidy file that's wrong is more dangerous than an obvious mess, because you trust it and import it.

Export Bank Statement converts the PDF — including scanned and photographed copies, via OCR — into clean CSV or Excel, then runs the running-balance check itself. It recomputes the totals against the printed closing balance and flags any statement that doesn't reconcile, so a dropped or misread line shows up before it ever reaches Zoho Books. We've watched a clean-looking file fail this check over a single transfer lost at a page break; finding it took a minute rather than a quarter-end scramble. It exports in Zoho Books' native bank-import CSV format, so the Withdrawals and Deposits columns arrive in the shape the importer expects.