Zoho Books accepts CSV, TSV, XLS, OFX, QIF, CAMT.053, and CAMT.054 files but never a PDF directly. This guide covers the exact import steps, the Amount Column Type setting that determines whether deposits and withdrawals get classified correctly, and when to use bank feeds instead of a manual import.
Last updated 2026-08-23
Zoho Books' Import Statement tool (Banking > your account > Import Statement) accepts CSV, TSV, XLS, OFX, QIF, CAMT.053, and CAMT.054 files — not PDF. The one setup choice that trips people up is the Amount Column Type: Zoho asks whether your file has two columns (deposits/withdrawals), one column with a separate debit/credit indicator, or one column using negative numbers for withdrawals, and picking the wrong one during field mapping misclassifies every transaction's direction.
Zoho Books can pull transactions automatically through its bank feeds partners (Yodlee, Token, and Plaid), but availability depends on your Zoho Books edition and whether your specific bank is supported. When it isn't, or you need older history than a live feed provides, the fallback is a manual statement import — and Zoho Books' importer, despite accepting a wide range of formats, still doesn't read a PDF.
Zoho Books' own documentation lists exactly seven accepted formats for a manual statement import: CSV, TSV, XLS, OFX, QIF, CAMT.053, and CAMT.054. That's a broader list than most accounting tools support, but PDF isn't on it. A bank statement PDF is laid out for printing, not for a program to read as typed date, amount, and description fields, so it has to become one of those seven formats first.
During import, Zoho Books asks you to choose how your file represents transaction direction. Getting this wrong doesn't fail the import outright — it silently classifies deposits as withdrawals or vice versa, which is worse than an error because it looks like it worked.
| Option | When to use it |
|---|---|
| Double Column | Your statement has separate columns for deposits and withdrawals |
| Single Column and Amount Type | One amount column, plus a separate column marking each row as debit or credit |
| Single Column with Negative Values | One amount column where positive means deposit and negative means withdrawal |
Match this choice to how your converted file actually represents amounts before you get to the Map Fields step — that's where the column-type selection determines which headers you're offered to match against.
A common next step is pasting the PDF text into a general-purpose AI chatbot and asking for a CSV or OFX back. It can work. It also comes with three problems that show up quickly once you're doing this every statement cycle:
This is the right question to ask, and it's the exact concern that makes pasting a statement into a general chat tool uncomfortable. The answer depends entirely on the converter's data-handling policy, not on whether "AI" is involved anywhere in the pipeline.
ClearlyLedger processes PDFs in memory and deletes the source file within seconds of conversion. Your statement is never stored, never shared, and never used to train AI models.
No. Zoho Books' manual import accepts CSV, TSV, XLS, OFX, QIF, CAMT.053, and CAMT.054 files, but not PDF. Convert the PDF first.
The import still completes, but deposits and withdrawals can be misclassified against each other, since Zoho Books uses that setting to determine transaction direction. Match it carefully to how your file actually represents amounts before mapping fields.
Yes, through partners like Yodlee, Token, and Plaid, though availability depends on your bank and Zoho Books edition. Manual import is the fallback when a live feed isn't available or you need older history.
Both are accepted. OFX carries typed date, amount, and description fields already, so it skips some of the manual field-mapping a CSV import requires. CSV is fine too if you want a spreadsheet copy to check before importing.
It depends on the tool's retention policy, not on whether it uses AI. Look for in-memory processing, immediate deletion of the source file, and an explicit statement that data isn't used to train models. ClearlyLedger does all three.
Ready to get your first statement into Zoho Books? Use ClearlyLedger's bank statement converter for a balance-verified OFX or CSV file. Using QuickBooks, Wave, or FreshBooks instead? See the same conversion for QuickBooks, Wave, or FreshBooks.
Loading interactive converter… Try ClearlyLedger free