How to Import a Bank Statement into Zoho Books
Zoho Books bank statement import: the CSV columns it expects, the field mapping step, and avoiding duplicate transactions.
Zoho Books has one of the more forgiving import flows — it lets you map columns rather than demanding a fixed order — but there are still two things that catch people out.
Zoho remembers your mapping
The first time you import, Zoho asks you to map your CSV columns to its fields. It then saves that mapping and reuses it for subsequent imports of the same account.
That is convenient until your file format changes. If you switch converters, or export with different columns, the saved mapping applies to the wrong columns and imports silently wrong data.
Debit and credit versus a signed amount
Zoho accepts either separate Debit and Credit columns or a single Amount column with a Type field. The two-column form is safer because it preserves the bank's own classification rather than relying on a sign that could be lost.
| Zoho field | Map from |
|---|---|
| Date | Date column |
| Description | Description column |
| Withdrawals | Debit column |
| Deposits | Credit column |
| Reference Number | Reference column |
A CSV from this site keeps your bank's own headings, so the Map from column is whatever your bank calls each one — Withdrawal Amt., Paid out, Debit. Zoho Books also imports OFX, which needs no mapping at all: the PDF to OFX converter writes one.
Avoiding duplicates
If you have a bank feed connected as well as importing files, overlapping date ranges produce duplicates. Zoho does some matching, but it is not reliable enough to depend on.
Import only the periods your feed does not cover, and check the transaction count after importing against the count in your converted file.
Categorisation rules
Zoho lets you define rules that auto-categorise transactions matching a description pattern. How you write the pattern decides whether they work.
A raw card descriptor varies per transaction — store numbers, terminal ids and reference suffixes change every time — so a rule matching the whole string will not match the next one. The merchant name inside it is stable, which means one rule set to contains that name covers every occurrence.
Reconciling
Zoho's reconciliation compares your recorded transactions against a closing balance you enter. Take that figure from the PDF rather than the import, for the same reason as anywhere else: a check against your own data is not a check.
Frequently asked questions
Does Zoho Books accept Excel files?
CSV is the reliable route. Export as CSV rather than .xlsx.
Why do my Zoho categorisation rules keep missing transactions?
Usually because they match the whole bank descriptor, which varies per transaction. A rule set to contains a merchant-name fragment generalises far better.
Can I re-import to fix a bad import?
Delete the imported transactions first, or you will end up with duplicates. Zoho keeps imports grouped, which makes bulk deletion practical.
Related posts
- How to Import a Bank Statement into MYOB
- How to Import a Bank Statement into Wave Accounting
- How to Import a Bank Statement into FreshBooks
Convert a statement now
Bank Statement PDF to CSV, or see every format. More in the guides.