Zoho Books (Edge)

Last updated on Nov 13, 2026

Zoho Books is an online accounting application that businesses use to manage their invoices, bills, expenses, payments, projects, and taxes, and to track their contacts, items, and chart of accounts.

Hevo uses the Zoho Books API to replicate the accounting data of your Zoho Books organization, such as invoices, bills, credit notes, payments, contacts, items, and journals, to the Destination of your choice. Hevo connects to Zoho Books using OAuth 2.0 with a Zoho API client that you register. To ingest data, you must provide Hevo with the Client ID and Client Secret of the API client, the ID of your Zoho Books organization, and the region of your Zoho account, and then authorize Hevo to read your data.


Supported Features

Feature Name Supported
Capture deletes Yes. For the Contact, Credit Note, Customer Payment, and Invoice objects, deletes are captured only when you resync the object.
History mode No
Custom data (user-configured tables & fields) Yes, for the custom fields of the Bill, Contact, Credit Note, Invoice, Purchase Order, and Sales Order objects
Data blocking (skip objects and fields) Yes
Resync (objects and Pipelines) Yes
API configurable Yes

Handling of Deletes

Hevo marks a record as deleted by setting the value of the metadata column __hevo__marked_deleted to True. Hevo captures deletes as follows:

  • For the objects whose records Hevo ingests in full in each run, Hevo compares the records fetched from Zoho Books with those in the Destination table. Records that are no longer returned by Zoho Books are marked as deleted in the Destination. The Chart of Account Document child object is replaced in full in each run, so the records removed in Zoho Books are removed from the Destination table.

  • For the Contact, Credit Note, Customer Payment, and Invoice objects, Hevo ingests only the new and updated records in the subsequent runs, so it does not capture records that are deleted in Zoho Books. These records remain in the Destination until you resync the object. When you resync the object, Hevo ingests all its records and marks the records that are no longer returned by Zoho Books, and their child records, as deleted.

  • For the child objects of the Contact, Credit Note, Customer Payment, and Invoice objects, when Hevo ingests a new or updated parent record, it replaces the child records of that parent in the Destination. The child records that were removed from the parent record in Zoho Books are marked as deleted.


Source Considerations

  • Hevo ingests data from one Zoho Books organization in a Pipeline. To ingest data from more than one organization, create a Pipeline for each organization.

  • The daily API request limit of your Zoho Books plan is shared by all the applications that use the Zoho Books API of your organization. If your plan has a low daily limit, increase the sync frequency interval of the Pipeline or deselect the objects that you do not need. Read API Request Limits.

  • To ingest the Contact, Credit Note, and Invoice objects and their child objects, Hevo makes one API request for each record in the first run and when you resync the object. If the number of records in such an object is more than your organization’s daily API request limit allows, Hevo cannot ingest the object, and the object fails with an error. In this case, upgrade your Zoho Books plan or buy additional API requests from Zoho, or deselect the object and its child objects. Hevo retries the object in each run, so ingestion resumes once the limit is increased.

  • Hevo ingests the custom fields of the Bill, Purchase Order, and Sales Order objects as separate columns, named custom_cf_ followed by the API name of the field. For the Contact, Credit Note, and Invoice objects, Hevo ingests the custom fields as a JSON array in the custom_custom_fields column.

    Some standard Zoho Books fields are also loaded into columns with the custom_ prefix, for example, custom_currency_code in the Credit Note object. These columns are not custom fields. Your custom fields are always loaded into the custom_cf_* columns or the custom_custom_fields column.

  • If your role in Zoho Books cannot read an object, Hevo marks the object as Inaccessible and displays it in the Needs Attention tab of the Pipeline. The other objects continue to be ingested. To ingest the object, grant your role View access to the corresponding module in Zoho Books, and then resync the object.

  • If your role can access only some records of a module, for example, only the customers assigned to you, Hevo ingests only those records. For the objects that Hevo ingests in full in each run, records that your role can no longer access are marked as deleted in the Destination.

  • Hevo supports Zoho accounts hosted in the US, Europe, India, Australia, and Japan data centers. Accounts hosted in other Zoho data centers, such as Canada, Saudi Arabia, UAE, UK, and China, are not supported. Contact Hevo Support to request support for these data centers.



Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Nov-12-2026 2.54 New document.

Tell us what went wrong