How to Import a PDF Bank Statement into Zoho Books

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

TL;DR

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.

Why Zoho Books Can't Open a PDF Statement

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.

The Setup Choice That Actually Matters: Amount Column Type

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.

Step-by-Step: PDF to Zoho Books

  1. Get the PDF from your bank's portal. Statement periods are usually selectable before download, so pull the exact range you plan to reconcile.
  2. Run it through ClearlyLedger. The converter identifies the bank layout, pulls every line item, and confirms the totals balance before it lets you download — pick OFX to skip the Amount Column Type decision below, or CSV if you want a spreadsheet check first.
  3. Open the account's Import Statement tool. Go to Banking in the left sidebar, select the bank account, and click Import Statement on the account's Details page.
  4. Choose the file and its Amount Column Type. Select your converted file, then pick Double Column, Single Column and Amount Type, or Single Column with Negative Values to match its structure, plus the character encoding and delimiter.
  5. Map the fields. On the Map Fields screen, match your file's headers to Zoho Books' fields — the exact fields offered depend on the Amount Column Type chosen in the previous step.
  6. Preview, then import. Zoho Books shows a preview before committing. Imported transactions land as uncategorized and are ready to match or categorize afterward.

Why a General Chatbot Won't Get the Amount Column Type Right

Pasting the statement text into ChatGPT or a similar tool and asking for a CSV back is the obvious shortcut once you realize Zoho Books won't take a PDF directly. It sometimes produces something usable. It also runs into a problem specific to what this particular import needs:

  • It doesn't know Zoho's amount convention. A general chatbot has no reason to structure its output as Double Column, Single Column and Amount Type, or Single Column with Negative Values — it picks whatever layout looks reasonable, and you're the one who has to notice it doesn't match any of Zoho's three options before hitting the misclassification risk described above.
  • Output drifts between runs. Multi-page PDFs, wrapped merchant names, and running-balance columns aren't parsed the same way twice by a model that wasn't built for tabular bank data. A layout that happened to import cleanly last month can come back structured differently this month, with no signal that anything changed.
  • Your statement becomes chat input. Account number, balance, and every transaction line get typed into a third-party conversation. For a banking record, that's a different exposure than a converter built to process the file and discard it.

Does ClearlyLedger Keep a Copy of the Statement?

No. The PDF is processed in memory during conversion, and the source file is deleted within seconds of the output being generated — nothing about the run is written to permanent storage, shared onward, or used to train a model. Worth stating plainly, since "AI" gets used loosely enough in this space that it's fair to ask what it actually means for your data here.

Frequently Asked Questions

Can Zoho Books read a PDF bank statement directly?

No. Zoho Books' manual import accepts CSV, TSV, XLS, OFX, QIF, CAMT.053, and CAMT.054 files, but not PDF. Convert the PDF first.

What happens if I pick the wrong Amount Column Type in Zoho Books?

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.

Does Zoho Books support bank feeds instead of manual import?

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.

Which file format should I use for Zoho Books, CSV or OFX?

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.

Is it safe to use an online tool to convert a bank statement?

Check the retention policy specifically, not just whether the tool mentions AI. A converter that processes in memory, deletes the source file immediately, and states outright that it doesn't train on your data is the bar to look for — ClearlyLedger meets all three.

Key Takeaways

  • Zoho Books accepts CSV, TSV, XLS, OFX, QIF, CAMT.053, and CAMT.054 — never a PDF directly.
  • The Amount Column Type setting (Double Column, Single Column and Amount Type, or Single Column with Negative Values) determines transaction direction — match it to your file or deposits and withdrawals get misclassified.
  • Bank feeds (Yodlee, Token, Plaid) are the automatic path when your bank and Zoho Books edition support them; manual import is the fallback.
  • Imported transactions land as uncategorized, ready to match or categorize afterward.

Ready to get your first statement into Zoho Books? Use ClearlyLedger's bank statement converter for a balance-checked OFX or CSV file. Using QuickBooks, Wave, or FreshBooks instead? See the same conversion for QuickBooks, Wave, or FreshBooks.

Written by John Snow, Financial Data Specialist.

Loading interactive converter… Try ClearlyLedger free