Start with the work your team repeats every week
Ask the accounts team one question: what do you do every week that follows the same steps, using the same reports, where a person only checks the result at the end? That list is where automation pays.
In most businesses on Zoho Books, the same few tasks come up:
- Working out who paid what from UPI and NEFT narrations such as "UPI/412907/SRI MURUGAN TRA/OKSBI".
- Comparing GSTR-2B with the purchase register before the 3B is filed.
- Typing customer purchase orders, received as PDF or Excel, into sales orders.
- Checking a vendor's statement against their ledger, line by line.
- Chasing overdue invoices, one message at a time.
- Preparing the monthly numbers for the owner.
What not to automate: one-off decisions, anything where the rule changes every time, and judgement calls such as whether a disputed bill should be paid. Automation suits work that is boring because it is predictable.
First step, at no running cost: rules inside Zoho Books
Before building anything, use what Zoho Books already has. Most businesses we see have switched on very little of it.
| Rule | What it stops |
|---|---|
| Validation rule: GSTIN and HSN required | An invoice saved without them, found only when the GST return is prepared |
| Approval above an amount, say ₹50,000 | A large bill posted without the owner seeing it |
| Customer credit limit | A fresh order to a customer who already owes more than you allow |
| Automatic payment reminders, e.g. 3, 10 and 20 days after due | Invoices that go overdue because nobody had time to follow up |
| Bank rules | The same rent, salary or EMI line being categorised by hand every month |
These run inside your existing Zoho Books plan. Some need the Professional plan or above, so check your plan before you plan around them.
Worked example: matching bank lines every night
Take a made-up electrical goods distributor with about 1,000 bank lines a month. Bank rules catch the fixed lines. The rest, about 40 a night, are payments from customers and to suppliers with narrations that are hard to read.
A small program runs each night and does four things:
- Reads the day's unmatched bank lines from Zoho Books through its API.
- Looks for an open invoice or bill with the same amount and a similar party name. "IMPS/P2A/VEL TRADERS +1,20,000" matches invoices INV-2240 and INV-2251 for Vel Traders, which add up to ₹1,20,000.
- For lines with no match, checks how the same party was booked before. Krishna Logistics has always gone to freight inward.
- Sends only the leftover narrations to an AI reading service for a suggestion. "UPI/88123/ZOMATO/PAYTM" comes back as a food order, possibly staff welfare, marked for a person to check.
In the morning, someone in accounts goes through the suggestions. On a typical night 34 of the 40 are accepted as they are and 6 need a closer look. Nothing is posted until a person accepts it, and the program keeps a record of what it suggested and what was changed.
Notice the order. Matching against open invoices and past entries is plain logic and costs nearly nothing. The AI service sees only what the cheaper steps could not settle. That keeps both the error rate and the bill down.
Where the program runs: Zoho Catalyst
Catalyst is Zoho's platform for running custom programs. We write the program; Catalyst runs it on a schedule or when a file arrives, and keeps a log of each run. Because it sits in the same Zoho account world as Books, Inventory and WorkDrive, connecting to them is simpler than from an outside cloud.
Every Catalyst account gets a free allowance that renews each month, including 25,000 GB-seconds of program time, 5,000 new database records and 1,000 file uploads. A nightly bank match for one business usually fits inside it, so Catalyst costs ₹0.
Above the allowance there are two ways to pay. Pay as you go charges only for the extra use, with a minimum of $5 (about ₹450) a month per project once it goes over. A monthly plan starts at $25 (about ₹2,200) and suits a CA firm running checks for many clients from one account.
One cost to watch: a web screen that stays on all the time, such as a separate approval page, uses Catalyst's always-on hosting and costs about ₹2,000–2,500 a month on its own. We avoid it by keeping approvals inside Zoho Books.
What the reading service costs
AI providers charge by the amount of text read and written, counted in tokens, roughly three quarters of a word each. A bank narration is about 150 tokens in and 50 out. A one-page purchase order is about 3,000 in and 800 out. The cheaper models (Claude Haiku, Gemini Flash-Lite, OpenAI's nano and mini) are enough for narrations and reminders; the larger ones (Claude Sonnet, Gemini Pro) read messy scans better and cost more.
Indicative monthly cost at typical volumes, at $1 ≈ ₹88:
| Task | Volume a month | Cheaper model | Larger model |
|---|---|---|---|
| Bank lines | 1,000 | ₹3–30 | about ₹75 |
| GSTR-2B mismatches | 50 | ₹1–15 | about ₹35 |
| Customer POs | 300 | ₹15–150 | about ₹390 |
| Vendor statements | 50 | ₹3–30 | about ₹75 |
| Payment reminders | 300 | ₹5–50 | about ₹130 |
These are ballpark figures. Prices change, scanned or multi-page documents cost more to read, and retries add to the bill, which is why they are ranges. The provider account is in your name, so you pay them directly and see every rupee.
The full picture of cost
Running costs are small, but they are not the whole cost. There are three parts:
- Building and setting it up: one time, paid to whoever builds it, and sized to the job. A Zoho Books rule is a small job; connecting an older billing system is a project.
- Running it: Catalyst and the reading service, paid to Zoho and the provider. ₹0 to a few hundred rupees a month for most single businesses.
- Your Zoho plan: what you already pay. Not every rule is on every plan.
If someone quotes only the running cost, ask about the other two. See our finance automation page for the full cost table and an estimator.
Before you automate a task
- The task repeats at least weekly, with the same steps each time
- The data comes from somewhere a program can read: Zoho Books, a bank feed, an export or an email
- You know what a correct result looks like, so a person can check it quickly
- Zoho Books rules and bank rules have been tried first
- Someone on the team owns the morning review
- Catalyst and provider accounts are in the business's name
- Running and build costs are both written down before you start
Questions and answers
Does automation post entries into Zoho Books on its own?
It does not have to, and we do not set it up that way. The program prepares drafts and suggestions; a person in your team accepts or changes each one.
Do I need AI for this?
Not always. Rules inside Zoho Books and plain matching logic handle a large share of the work at no running cost. AI is useful for reading things that do not follow a fixed format, such as narrations, PDFs and emails.
What is Zoho Catalyst?
Zoho's platform for running custom programs: scheduled jobs, programs triggered by events, small databases and file storage. It has a free monthly allowance and pay-as-you-go pricing above it.
Can a CA firm use this across clients?
Yes. Checks such as GSTR-2B matching or a weekly health check can run for each client organisation. A Catalyst monthly plan is usually the better fit at that scale.
Migration support
When to get help
If your team spends a day a week on one of the tasks above, it is worth a conversation. We will tell you which kind of automation it is, whether Zoho Books can already do it, and roughly what it would cost to run.
See the See finance automation page, or run the free migration readiness check.