Sending Zoho Books invoices on WhatsApp
Zoho Books can send invoices over WhatsApp natively, which is genuinely convenient. It also makes Zoho your BSP for that phone number, and that is a decision about your whole WhatsApp stack, not just about invoices.
Short answer. The integration is native and it works. But switching it on means Zoho becomes your Business Solution Provider for that number: the number must not be attached to another BSP, you buy Zoho IM credits rather than paying Meta's rate through your own stack, and running a separate WhatsApp programme on the same number becomes difficult.
What it actually sends
Zoho Books' WhatsApp integration covers the finance document set, which is more than most accounting integrations manage:
- Invoices, quotes and retainer invoices
- Sales orders and sales receipts
- Payment receipts and credit notes
- Customer statements — to customers
- Vendor statements — to vendors
All of these are naturally utility messages: they follow a transaction the customer already made. See sending invoices and receipts on WhatsApp for the UAE tax-invoice requirements that the PDF itself still has to satisfy.
The BSP decision, which is the real one
Zoho's own documentation is explicit: once you set up this integration, Zoho becomes your BSP. What that means in practice:
- The phone number must be one you own and that is not already associated with another BSP.
- You need a verified Facebook Business Manager account.
- You buy IM credits from Zoho to send. You are not paying Meta's per-message rate directly through your own account.
- If you later want a broader WhatsApp programme — broadcasts, chatbots, a shared team inbox — on the same number, you are constrained by what Zoho supports.
The clean way out of that tension: use a second number. Finance documents go out on the Zoho-connected number; marketing, support and sales run on your main number through your own stack. Two numbers is mildly inelegant and much cheaper than migrating a number later.
Limits that are tighter than Meta's
Worth knowing before you design a template, because these are Zoho's ceilings, not WhatsApp's:
| Zoho Books integration | Meta Cloud API | |
|---|---|---|
| Call-to-action buttons per template | 2 | 3 |
| Image attachment | JPG / JPEG / PNG up to 5 MB | 5 MB |
| PDF attachment | 10 MB | 100 MB |
The 10MB PDF ceiling is the one that bites. A long statement with embedded logos and a scanned signature page can exceed it. Compress the PDF at generation, or send a link to a hosted document instead of the file.
Template approval and the 24-hour rule
Templates you create go to Meta for approval and can take up to 24 hours. Until your customer replies you can only send predefined templates, and the session expires after 24 hours of inactivity — the standard WhatsApp customer service window.
Practical consequence for finance teams: you cannot improvise. "Just send them a quick note about the overdue balance" is a template that has to exist already. Build the set you will actually need — issued, due tomorrow, overdue, payment received, statement — before you need them.
When Zoho's integration is the right choice
- Your finance operation lives in Zoho Books and you want invoices on WhatsApp with no engineering.
- You do not have a WhatsApp programme yet, and this is your first use case.
- Volume is modest and IM credits are cheaper than the effort of building the same thing.
When it is not
- You already run WhatsApp for marketing or support on the number you want to send invoices from.
- You need the finance messages to sit in the same conversation thread as sales and support, which is what customers actually expect.
- You need routing, assignment or analytics across all your WhatsApp traffic — see one number for a whole team.
- You want to control the per-message rate directly rather than buying credits.
In those cases, drive Zoho Books from your own WhatsApp stack instead: trigger off Zoho Books webhooks, fetch the invoice PDF from the API, and send it through the number you already run. Slightly more work, one number, and no BSP lock-in.
Adjoltz builds these flows for UAE brands on Meta's official Cloud API — correct template categories, the buttons, and the inbox behind them. Messages at Meta's rate with zero markup, from $149/month.
Frequently asked questions
Can Zoho Books send invoices over WhatsApp?
Yes, natively. The integration covers invoices, quotes, retainer invoices, sales orders, sales receipts, payment receipts, credit notes and customer statements to customers, plus vendor statements to vendors. All of these are utility messages because they follow a transaction the customer already made.
What happens when I enable the Zoho Books WhatsApp integration?
Zoho becomes your Business Solution Provider for that phone number. The number must be one you own and that is not already attached to another BSP, you need a verified Facebook Business Manager account, and you buy IM credits from Zoho rather than paying Meta's per-message rate through your own account. Running a broader WhatsApp programme on the same number afterwards is constrained by what Zoho supports.
What are the file size limits for Zoho Books WhatsApp attachments?
JPG, JPEG and PNG images up to 5MB, and PDFs up to 10MB. The PDF ceiling is tighter than Meta's own 100MB document limit, so a long statement with embedded logos and a scanned signature page can exceed it. Compress at generation or send a link to a hosted document instead.
Can I use the same number for Zoho Books invoices and WhatsApp marketing?
Not easily, because the number is tied to Zoho as your BSP. The practical answer is a second number: finance documents on the Zoho-connected number and marketing, sales and support on your main number through your own stack. Alternatively, drive Zoho Books from your own stack by triggering off its webhooks and fetching the invoice PDF from the API.