Zoho Books will not read a PDF statement, and its bank feed does not cover every account or reach far enough back. Upload the PDF here and get a clean CSV with date, description, and amount columns that the Import Statement screen accepts on the first try. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
Zoho Books imports bank statements as CSV, TSV, XLS, OFX, QIF, camt.053, or camt.054, and it does not accept a PDF. So when your bank feed misses an account or you need older history, the working path is to convert the PDF statement into a clean CSV and upload it under Banking, then the account, then Import Statement. BankXLSX turns the PDF into exactly that file: one row per transaction with date, description, and amount.
Zoho Books has a perfectly good import screen. The trouble is what it will and will not take, and how much cleanup a raw statement needs before it gets there.
The accepted formats are CSV, TSV, XLS, OFX, QIF, camt.053, and camt.054. A PDF statement, which is what your bank actually gives you, is not on the list.
Automatic feeds cover the banks the aggregator supports, and they fetch going forward. For a closed account, an unsupported bank, or last year's books, you are importing a file by hand.
Feeds pull roughly every 24 hours for banks that do not require multi factor authentication, and a manual refresh is limited to once a day, so a stalled feed can cost you a day of catch up work.
Pasting a PDF statement into a spreadsheet merges the date into the description, splits amounts across cells, and turns page headers into fake transactions.
Zoho Books expects one of three shapes: two columns for deposits and withdrawals, one amount column plus a transaction type column, or a single column using negative values. A messy paste fits none of them.
The import screen asks you to set character encoding and the file delimiter. A file exported with the wrong encoding produces mangled descriptions or a failed upload.
Upload the PDF and the converter reads the transaction table, not the layout, then writes a file the Zoho Books importer maps in one pass.
Every transaction becomes one row with a date, a description, and an amount, which is the shape the Import Statement mapper expects.
Choose separate deposit and withdrawal columns or a single signed amount column, matching whichever structure you select in Zoho Books.
Dates come out in one format across the whole file instead of the mix a PDF produces, so the date mapping does not fail halfway down.
Download whichever of the Zoho Books accepted formats you prefer. CSV is the simplest to map, OFX and QIF carry the structure for you.
Convert a full year of statements at once and get a single continuous transaction list instead of twelve separate files.
256-bit encryption in transit and you can delete your uploaded files whenever you want.
No software to install and no credit card to start.
Upload your PDF statement above and download the result as CSV. Pick the column structure that matches how you want to map it.
Tip: A signed amount column is the simplest.
In Zoho Books go to Banking, select the bank or credit card account, then click Import Statement on that account's details page.
Tip: Import into the matching account.
Set the character encoding and delimiter, map date, description, and amount to your columns, then import. Transactions arrive uncategorized, ready to categorize or match.
Tip: Check the first rows before confirming.
Zoho Books is the accounting system of choice for a lot of US small businesses and the bookkeepers who serve them, especially inside the wider Zoho One suite.
Bring a new client onto Zoho Books by importing a year of historical statements the bank feed cannot reach.
Get an account the feed does not support into the books without keying in every line.
Clean up a year end when the feed dropped a month, using the PDF statement as the authoritative record.
Migrate a client from another accounting platform by loading opening history from statement PDFs.
Last updated July 2026
Zoho Books accepts CSV, TSV, XLS, OFX, QIF, camt.053, and camt.054 files when you import a bank or credit card statement. PDF is not an accepted format. That single fact is why almost everyone importing history into Zoho Books converts the statement first: the bank hands you a PDF, and the importer wants a table.
| Format | Accepted by Zoho Books | Notes |
|---|---|---|
| CSV | Yes | The most common choice. You map the columns yourself. |
| TSV | Yes | Same as CSV with a tab delimiter. |
| XLS | Yes | An Excel workbook, mapped the same way as CSV. |
| OFX | Yes | Carries its own structure, so there is less mapping to do. |
| QIF | Yes | The older Quicken interchange format. |
| camt.053 and camt.054 | Yes | ISO 20022 XML, usually only from corporate banking. |
| No | Convert it to CSV first. |
Go to the Banking module, select the bank or credit card account you want the transactions to land in, and click Import Statement on that account's details page. Zoho Books then asks for the file, the character encoding, and the delimiter, and finally walks you through mapping your columns onto its fields. Imported transactions arrive as uncategorized and wait for you to categorize or match them against existing records.
This is where most failed imports happen. Zoho Books needs to know how your file expresses money in versus money out, and it supports exactly three shapes. Pick the one your converted file matches before you start mapping.
| Structure | How it looks | Best when |
|---|---|---|
| Double Column | Separate Deposit and Withdrawal columns | Your statement already prints debits and credits apart. |
| Single Column with Amount Type | One Amount column plus a type column | Your file labels each row as a deposit or a withdrawal. |
| Single Column with Negative Values | One Amount column, positive in, negative out | The simplest to produce and the least error prone. |
Zoho Books can pull transactions automatically through third party aggregators, and the US and Canada editions offer a Plaid integration alongside Yodlee. Feeds are genuinely convenient, and for a supported bank you should use one. They stop helping in four situations, and all four end in a manual import.
First, the bank is not supported by the aggregator, which is common with small community banks and credit unions. Second, the account is closed, so there is nothing left to connect to. Third, you need history from before you connected the feed, because a feed starts fetching from the day you link it. Fourth, the feed breaks, usually after a bank password change or a multi factor prompt, and Zoho Books itself points you at manual import as the fallback. Feeds refresh roughly every 24 hours for banks without a multi factor requirement, and you can only force a manual refresh once a day, so a broken feed is not something you fix in five minutes.
Worth knowing for the security review your client will ask about: Zoho states it does not store your bank login credentials and transmits data over 256-bit SSL.
Zoho Books accepting camt.053 and camt.054 is unusual for a small business accounting package, and it matters if your bank has moved to ISO 20022 reporting. If your corporate bank sends the XML statement, you can import it directly without any conversion. If you would rather work with rows first, or you need to check the file before it hits the books, convert it with the camt.053 to Excel converter and import the resulting CSV instead.
Once the statement rows are in, the work is categorization and reconciliation. Our guide to importing bank transactions into Zoho Books walks through the mapping screen field by field, and the transaction categorization page covers cleaning up descriptions before import. If you keep more than one account, see how to reconcile multiple bank accounts. Using a different platform for some clients? There are matching guides for the Xero bank statement converter, the Wave bank statement converter, and the Odoo bank statement converter. When you only have the PDF, start at the bank statement converter.
Bank rows are only half of a clean set of books. The receipts and bills behind them still have to be captured, which you can do by pulling the line items off each one with receipt and invoice data extraction, and teams paying a high volume of supplier bills each month usually automate the approval and coding side with accounts payable automation.
Go to the Banking module, select the bank or credit card account, and click Import Statement on that account's details page. Upload a CSV, TSV, XLS, OFX, QIF, camt.053, or camt.054 file, set the character encoding and delimiter, then map your date, description, and amount columns onto the Zoho Books fields.
No. Zoho Books accepts CSV, TSV, XLS, OFX, QIF, camt.053, and camt.054 for statement imports, and PDF is not on that list. Convert the PDF into a CSV first, keeping one row per transaction with a date, a description, and an amount, then import that file through the Import Statement screen.
One row per transaction with a date column, a description column, and either a single signed amount column, a single amount column plus a type column, or separate deposit and withdrawal columns. Those are the three structures Zoho Books supports. Set the correct character encoding and delimiter on the import screen so descriptions do not come through garbled.
Zoho Books points you to manual import as the fallback. Download the PDF or CSV statement from your bank for the missing period, convert it to a CSV if needed, then use Banking, the account, and Import Statement. Manual refresh of a feed is limited to once a day, so importing is usually faster than waiting.
Both, depending on your edition. The US and Canada editions offer a Plaid integration, while Yodlee serves the feeds more broadly, and Token covers the UK and EU. Feeds fetch about every 24 hours for banks that do not require multi factor authentication.
There is no history limit on a manual import the way there is with a bank feed, which only starts collecting once you link the account. If you have the statement PDFs, you can convert and import several prior years, which is how most bookkeepers handle a catch up or a migration from another platform.
That is expected. Imported statement transactions arrive as uncategorized and wait for you to categorize them or match them to an existing invoice, bill, or payment. Cleaning up the description column before you import makes the matching noticeably faster.
Yes. Zoho Books accepts both camt.053 and camt.054 ISO 20022 XML files, which is unusual for a small business accounting package. If your corporate bank has migrated to ISO 20022 statement reporting, you can import the XML directly rather than converting it to CSV first.
Convert statements for Odoo Accounting.
Convert ISO 20022 camt.053 XML statements.
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
