Zoho Books Bank Statement Import: Formats, Steps and the Date Trap That Breaks US Imports
Aug 18, 2026 · Updated Aug 21, 2026
Convert your bank statement to OFX now
PDF, JPG, PNG, BMP, HEIC, TIFF
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF
Uploading...
All data: Extracts every table and text field from each page.
TL;DR: Zoho Books imports bank statements in CSV, TSV, XLS, OFX, QIF, CAMT.053 and CAMT.054. PDF is not on the documented list, so a statement downloaded from online banking has to be converted first. OFX is the best target of the group: it needs no column mapping, states its dates unambiguously, and carries a unique ID on every transaction. Import from Banking, then the account, then the gear icon, then Import Statement.
Bank feeds cover the recent past and not much else. The moment you are onboarding a new company file, catching up a neglected quarter, or working with a community bank that Zoho cannot connect to, you are importing statements by hand. That is a routine job, but it goes wrong in two specific ways for US businesses, and both are avoidable.
What file formats does Zoho Books accept for bank statements?
Zoho Books documents seven import formats: CSV, TSV, XLS, OFX, QIF, CAMT.053 and CAMT.054. That is a wider list than most accounting systems offer, and it is unusual in accepting both OFX and QIF.
PDF is not among them. This catches people out constantly, because a PDF is exactly what online banking hands you. Zoho's own error guidance lists an unsupported file format as the first reason an import fails, and a PDF dropped into the import screen is the most common version of that.
| Format | Practical for a US account | What to know |
|---|---|---|
| OFX | Best choice | No column mapping, dates written as YYYYMMDD, unique ID per transaction. |
| QIF | Workable | Accepted, but carries no transaction ID, so a repeated period duplicates. |
| CSV, TSV, XLS | Fallback | Needs field mapping and the right date setting. Most failures start here. |
| CAMT.053, CAMT.054 | Rare in the US | ISO 20022 XML, common in Europe and at the corporate tier. |
| Convert first | Not a documented import format. Convert to OFX, QIF or CSV. |
How do I import a bank statement into Zoho Books?
Go to Banking in the left sidebar, select the bank or credit card account the statement belongs to, click the gear icon at the top right, and choose Import Statement. Upload the file, then work through the Map Fields step, where Zoho auto-selects the best match for each field. Confirm the mapping and finish the import.
Two details on that screen are worth knowing. You can tick the option to save your selections for future imports, which is worth doing the first time you map a particular bank's CSV layout, since you will be repeating it every month. And if the wrong file goes in, or the same statement goes in twice, there is an Undo Last Import option. Use it immediately rather than deleting transactions by hand.
Import into the account the statement actually belongs to. Importing a business checking statement into the wrong account is tedious to unpick, and reconciliation will have nothing sensible to match against.
Why do my dates import wrong in Zoho Books?
This is the one that bites US businesses, and it is worth reading twice. Zoho's import error documentation states that the date must be in DD-MM-YYYY format. US bank statements are written MM/DD/YYYY. Those two are indistinguishable for the first twelve days of any month.
So 03/07/2026 is March 7th on your statement and July 3rd to the importer. No error appears, because both readings are valid dates. The transactions simply land in the wrong month, and you find out at reconciliation when a period will not balance, or worse, at year end.
There are two defenses. The reliable one is to import OFX instead of CSV, because OFX writes dates as YYYYMMDD inside the file, and a date in that form cannot be read two ways. The manual one is to check the date setting during mapping and then verify the earliest and latest transaction dates against the statement before you reconcile. If your first transaction shows up in a month the statement never covered, stop and undo.
Should I import OFX or CSV into Zoho Books?
OFX, whenever you have the choice. Both work, but they fail differently. A CSV import depends on you mapping columns correctly and picking the right date and amount settings every time, and any of those can be wrong in a way that imports cleanly and is still incorrect. An OFX file carries its own structure, so there is nothing to map.
The deeper reason is the transaction ID. Every transaction in an OFX file has a unique identifier assigned by the bank. CSV and QIF have no such field. That identifier is what lets an accounting system recognize a transaction it has already seen, so if you import January through March and later import January through June, the overlap is skipped rather than added twice. With CSV, the overlapping months are simply duplicated, and nothing in the file can prevent it.
If you want the detail on what is actually inside those files, the OFX file format is documented field by field, and the QIF file format page covers the older format Zoho also accepts, including why its dates are ambiguous by design.
Zoho Books bank statement import errors, and what causes them
Zoho documents five specific causes when an import fails. In practice they account for nearly everything:
- Unsupported file format. Accepted formats are CSV, TSV, XLS, OFX, QIF, CAMT.053 and CAMT.054. A PDF is the usual culprit.
- Incorrect date format. The importer expects DD-MM-YYYY, which is not how a US statement is written.
- Incorrect character encoding. Choose the encoding that matches the file. Statements with unusual characters in payee names are the ones that break.
- Incorrect amount column type. Statements come with either a single amount column or separate debit and credit columns, and the setting has to match the file you actually have.
- Negative values in the amount column. With the single or double column settings, Zoho expects a positive value in the amount column rather than a minus sign.
Notice that four of those five are CSV problems. An OFX file has no column type to choose, no encoding question in practice, and no date ambiguity. Converting the statement once, to the right format, removes most of this list.
Importing a backlog into Zoho Books
Migrations and catch-up work are where manual import earns its keep. Bank feeds typically reach back around 90 days on first connection, and sometimes only 30. Your opening balances usually need more than that, and the statement archive in online banking generally goes back years.
The workable approach is to pull the monthly PDF statements for the period you need, convert them in one batch, and import them in order. Up to 50 statements go into a single upload with our bulk bank statement converter, and when they all belong to one account they can be merged before extraction, so twelve monthly PDFs become one continuous file and one import rather than twelve.
Import non-overlapping ranges, and check the transaction count after each one. While you are reviewing a year of categorized activity, it is a good moment to notice how much of it is recurring: a surprising share of the lines in a modern business account are software subscriptions, and seeing what that cloud and SaaS spend actually totals is often more revealing than the bank balance itself.
Can Zoho Books import a PDF bank statement?
Not as a documented import format. The supported list is CSV, TSV, XLS, OFX, QIF, CAMT.053 and CAMT.054, and a PDF has to be converted before it can be imported.
That conversion is the whole job here. Upload the PDF or scanned statement to the bank statement to OFX converter at the top of this page, and the transactions are read out of it, including from image only statements that contain no selectable text. Export OFX, import it into the Banking screen, and the date and mapping problems above never come up.
Frequently asked questions
Does Zoho Books accept OFX files?
Yes. OFX is one of the seven documented import formats, alongside CSV, TSV, XLS, QIF, CAMT.053 and CAMT.054. It is the format worth choosing when you have the option, because it requires no field mapping and carries a unique identifier on each transaction that prevents a repeated period from importing twice.
What date format does Zoho Books require for bank statement imports?
Zoho's import error documentation specifies DD-MM-YYYY. That is the reverse of the US convention, so a US statement imported as CSV can silently place transactions in the wrong month for any date in the first twelve days. OFX avoids the issue because it writes dates as YYYYMMDD.
How do I undo a bank statement import in Zoho Books?
Use the Undo Last Import option, which exists specifically for uploading the wrong statement or uploading the same one twice. Do it before you start categorizing or reconciling, because unpicking a bad import by hand after the transactions have been matched is considerably more work.
Can I import several months of statements into Zoho Books at once?
Convert them as a batch first, then import. Up to 50 statements can be converted in one upload here, and statements from the same account can be merged into a single continuous file before extraction, which turns a year of monthly PDFs into one import instead of twelve.