Zoho Books and Tipalti integration

What moves between them

Vendor invoices and purchase orders created or updated in Zoho Books flow into Tipalti as new invoice and purchase order records. Zoho Books contacts are mapped to Tipalti payees using a canonical name and email matching. Payment approval and status updates in Tipalti flow back to Zoho Books as notes or custom fields on the original invoice. The flow is bidirectional but asymmetric: Zoho Books is the source of truth for invoice line items and PO structure, while Tipalti owns payment status and approval workflows. Polling occurs on a schedule tied to your approval cadence, typically daily or on-demand.

How ml-connector handles it

ml-connector stores Zoho Books OAuth2 credentials and refreshes the access token at 55-minute intervals before expiry. It routes all Zoho Books API calls to the correct regional base URL determined by the region credential field (US, EU, India, Australia, Japan, Canada, China, or Saudi Arabia). On the Tipalti side, ml-connector builds HMAC-SHA256 signatures by hashing the payer name and API key together, then calls the SOAP PayeeFunctions and PayerFunctions endpoints. Vendor contacts in Zoho Books are matched to Tipalti payees on name and email; if no payee exists, ml-connector creates one as part of the invoice submission. Zoho Books invoices and POs are transformed into Tipalti-compatible SOAP structures, with currency codes resolved via Zoho Books' GET /settings/currencies endpoint. Tipalti's single IPN endpoint is registered once and receives events for all invoice and payment changes; ml-connector verifies each webhook's HMAC-SHA256 signature using the configured secret before processing. Zoho Books rate limits at 100 requests per minute; ml-connector respects those limits and retries with exponential backoff on HTTP 429.

A real-world example

A mid-sized services firm uses Zoho Books to track vendor invoices and purchase orders across multiple cost centers and Tipalti to automate supplier payments and tax compliance for a global vendor base. Before the integration, the accounts payable team exported vendor invoices from Zoho Books, manually entered them into Tipalti, and then re-keyed the payment status back to Zoho Books. The process was error-prone and delayed payment scheduling by 1-2 days. With Zoho Books and Tipalti connected, invoices flow automatically, supplier names are mapped once at setup and then stay in sync, and payment status updates appear in Zoho Books within minutes of approval, eliminating manual re-entry and accelerating payment cycles.

What you can do

• •Push invoices and purchase orders from Zoho Books to Tipalti, with vendor contact mapping and currency conversion.
• •Sync payment status and approval workflows from Tipalti back to Zoho Books to keep your invoice records current.
• •Handle Zoho Books multi-region OAuth2 authentication and token refresh, routing calls to the correct regional API endpoint.
• •Verify Tipalti webhook signatures via HMAC-SHA256 and process payment notifications without manual polling.
• •Create payees in Tipalti on demand if a vendor contact does not already exist, and maintain the mapping across both systems.

Questions

How does ml-connector handle Zoho Books multi-region accounts?

Zoho Books returns the region (US, EU, India, Australia, Japan, Canada, China, or Saudi Arabia) in the OAuth2 token response. ml-connector stores the region as a credential field and routes all API calls to the correct regional base URL. This ensures that organization IDs and entities are looked up in the correct instance.

Does ml-connector create payees in Tipalti if a vendor contact is new?

Yes. When an invoice is pushed from Zoho Books to Tipalti, if the vendor contact does not match any existing Tipalti payee on name and email, ml-connector creates a new payee first. The mapping is stored so future invoices from that vendor route to the same payee without duplication.

How are currencies and exchange rates handled between the two systems?

Zoho Books includes currency_id and exchange_rate fields on every monetary entity. ml-connector resolves currency codes by calling GET /settings/currencies once per session and caches the mapping. Tipalti invoice amounts are submitted in the vendor's local currency as stored in Tipalti, and ml-connector translates Zoho Books amounts using the exchange rate if they differ.