Zoho Books and Procurify integration

What moves between them

The main flow is Procurify into Zoho Books. Purchase orders, requisitions converted to bills, and vendor payments flow from Procurify into Zoho Books on a schedule you define. Vendors are mapped to Zoho contacts by name or external ID. Bill line items are mapped to Zoho chart of accounts based on the account code provided by Procurify. Vendor master data such as contact names, addresses, and currency is synchronized in both directions so Zoho has current vendor information. Bills and POs in Zoho are marked read-only to prevent conflicts since Procurify is the source of truth.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Zoho side it resolves the customer's organization_id immediately after login, caches it, and routes all subsequent calls to the correct regional base URL (US, EU, India, Australia, Japan, Canada, China, or Saudi Arabia) as determined by the token response. Zoho access tokens expire after 1 hour, so ml-connector proactively refreshes at 55 minutes to avoid mid-flow failures. Procurify offers no webhooks, so ml-connector polls purchase orders and bills using the last_modified and po_created_date date-range filters on a configurable schedule. Before creating a bill in Zoho, ml-connector validates that the referenced Procurify vendor exists in Zoho's contact list and maps the account code to a Zoho chart-of-accounts entry. Purchase orders created in Procurify via requisition approval flow into Zoho with their PO number, vendor, line items, and total. Deduplication uses BullMQ job IDs to prevent double-posting if a poll cycle is retried. The integration tracks Procurify API access status and surfaces alerts if access is suspended due to excessive requests.

A real-world example

A mid-market manufacturing and distribution company uses Zoho Books for accounting and Procurify for procurement across three locations. Before the integration, the procurement team approved purchase orders in Procurify, then the accounting team logged into Zoho and manually created matching bills and account entries, leading to mismatches and duplicate bills during month-end close. With Zoho Books and Procurify connected, approved POs flow into Zoho automatically, bills are created from Procurify with the correct line allocations, and vendor master data stays in sync. The accounting team now focuses on reconciliation instead of data re-entry, and the audit trail ties every Zoho entry back to its Procurify source.

What you can do

• •Sync purchase orders from Procurify into Zoho Books with PO number, vendor, line items, and amounts.
• •Create bills in Zoho Books from Procurify requisitions and vendor invoices, mapped to the correct chart of accounts.
• •Map Procurify vendors to Zoho contacts and synchronize vendor master data in both directions.
• •Poll Procurify on a schedule you control with date-range filtering to capture all new and modified POs and bills.
• •Refresh Zoho tokens before expiry and route all calls to the correct regional base URL for your organization.

Questions

How does ml-connector handle Zoho's multiple regional base URLs?

The Zoho OAuth2 token response includes the region (api_domain) where the customer's organization lives. ml-connector caches this value after initial authentication and routes all subsequent API calls to the correct regional base URL for that customer. If a customer is in the EU, all calls use https://www.zohoapis.eu/books/v3; if in Japan, https://www.zohoapis.jp/books/v3, and so on.

Why does Procurify require polling instead of webhooks?

Procurify does not offer webhooks or push notifications. ml-connector polls the purchase-orders and bills endpoints using the last_modified and po_created_date date-range filters on a schedule tied to your procurement cycle. This allows you to control when data is synced and ensures all new and modified records are captured without missing updates.

What happens if a purchase order references a vendor that does not exist in Zoho Books?

ml-connector validates the Procurify vendor against Zoho's contact list before creating a bill. If the vendor is not found, the integration creates an audit log entry with the failure reason and alerts the user. The vendor must be manually added to Zoho, and the bill can then be synced on the next poll cycle.