Zoho CSV Import Format

What makes Zoho's importer different from Xero's or QuickBooks' is that single question it asks about the amount. It offers three ways to read money in and money out, and picking the wrong one is the quietest way to get a statement that imports cleanly and still posts every figure backwards. The rest of this guide is the format, field by field, with the three amount modes laid side by side.

The required columns

Zoho Books reads more than just these, but a bank statement only ever needs a handful. Everything else on a printed statement is for a human, not the importer.

The running balance has no field here. Zoho Books doesn't store a running balance against imported lines, so the Balance column off your statement has nowhere to go on the mapping screen. Don't bin it too early, though — it's the one column that proves your file is complete, and there's more on that below.

The three amount modes

This is the part worth slowing down for. After you upload, Zoho Books asks how your file expresses money, and gives three choices. Match the one to how your CSV is actually built:

Most UK, Australian and Irish statements print money out and money in as two separate columns, so they fit Double Column without any reshaping — money out maps to Withdrawals, money in to Deposits. If your file shortened those headings to "Dr" and "Cr", you don't edit the file; you point Zoho at the right field on its own screen. The mistake to avoid is feeding a signed Amount column into Double Column mode, or a two-column file into a Single Column mode. The numbers go in, nothing errors, and half your transactions land on the wrong side of the ledger.

What an accepted file looks like

Here's a Double Column file the way Zoho Books reads it — separate Withdrawals and Deposits, bare numbers, no currency symbol and no thousands commas:

```csv Date,Description,Withdrawals,Deposits 06/02/2026,Opening balance brought forward,,2400.00 06/04/2026,Card payment - office supplies,86.40, 06/09/2026,Client invoice 1042,,1250.00 06/14/2026,Direct debit - utilities,142.18, ```

And the same four transactions as a Single Column with Negative Values file, where the minus sign does the work the second column was doing:

```csv Date,Description,Amount 06/02/2026,Opening balance brought forward,2400.00 06/04/2026,Card payment - office supplies,-86.40 06/09/2026,Client invoice 1042,1250.00 06/14/2026,Direct debit - utilities,-142.18 ```

Same information, two shapes. Pick whichever your statement already resembles — a two-column statement converts most naturally to the first, and you tell Zoho it's Double Column on the way in.

Getting the date format right

The date field bounces more rows than anything except the amount mode, and the cause is always the order, not the digits. Written `06/04/2026`, a date is the 4th of June in the United States and the 6th of April across the UK, Australia and Ireland. Zoho Books doesn't guess. You set the format on the mapping screen, and if that choice doesn't match how the dates are actually written in your file, every line either lands on the wrong day or gets rejected.

Two habits keep this clean. Keep one date order through the entire file — a statement that switches format partway down will never map properly. And when you're editing dates by hand, write them as `YYYY-MM-DD`, which is unambiguous and which Excel is far less likely to silently rewrite on save. Whatever order you settle on, set the matching option in Zoho and then sanity-check one transaction you remember. If a payment you know the date of has landed right, the rest have too.

File rules Zoho expects

Beyond the columns, the file itself has to meet a few plain conditions, or the importer either refuses it or scrambles the rows:

• CSV, TSV or XLS. Zoho's Import Statement tool also takes OFX, QIF and CAMT, but not a PDF — a PDF is a document to it, not data.
• One header row, then one transaction per row. No title rows, no bank-logo rows, no blank spacer lines above or between the data.
• One account per file. Zoho imports into the single account you've selected, so don't merge two accounts into one CSV.
• No merged cells in an XLS. They survive the import as misaligned columns and break the mapping.
• Bare numbers. Strip the currency symbol and the thousands separators; `1,180.00` should read `1180.00`.

If your statement starts life as a PDF, none of this applies until you've converted it. The import PDF statements into Zoho Books guide walks the full convert-then-upload route, and there's a worked bank example in convert Barclays statements to Zoho Books.

The check the format can't do

Here's the part a format spec quietly steps around. A CSV can satisfy every rule on this page — the right columns, the correct amount mode, a clean date order — and still be wrong. Format only tells you a file is *readable*. It says nothing about whether the file is *complete*. A converter can hand you a tidy, well-shaped CSV that imports into Zoho Books without a single complaint and is missing one transaction, because a direct debit dropped off the foot of page four during extraction. A clean file that's incomplete is the dangerous kind, precisely because you'll trust it.

This is why that running-balance column earns its place before you delete it. It works as a built-in checksum: opening balance, plus money in, minus money out, has to equal the printed closing balance. Walk it row by row and the first line where your total stops agreeing with the bank's figure is the exact transaction that went missing or got misread. You want to find that *before* the import, not at quarter-end when Zoho won't reconcile and you've no idea which row to blame.

Export Bank Statement is the web app built around that check. It converts the PDF — including scanned and photographed statements, through OCR — into a clean CSV or Excel file, then runs the reconciliation 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. It writes the file in Zoho Books' native bank-import format too, so the Withdrawals and Deposits columns arrive in the shape the importer expects. We once watched a neat-looking file fail the check over a single transfer lost at a page break; the flag turned a quarter-end scramble into a one-minute fix.

Be plain on what it is, though. You convert, then you upload. It doesn't push transactions into Zoho Books through a certified bank-feed API, and it isn't a bookkeeping service — you decide what gets imported and what gets matched. Bank feeds only fetch recent activity in any case, so older months and catch-up work have to come in as a file regardless. More sits on the Zoho Books pillar, with country detail on the UK hub.