Zoho Books and UKG integration

What moves between them

Expense categories and vendor payment records flow from Zoho Books into UKG. Zoho Books invoices and bills are read to identify business expenses and cost categories, then mapped to matching UKG cost centers and GL account segments. The sync runs on a schedule tied to your expense reporting cycle, typically daily or weekly. Zoho Books is read-only on the ml-connector side; UKG receives the cost-center-mapped expense records via the third-party pay endpoint for GL posting.

How ml-connector handles it

ml-connector stores both credential sets encrypted and handles Zoho Books regional routing by reading the region field from the OAuth token response and directing all calls to the correct regional base URL. It refreshes Zoho Books access tokens proactively before the 1-hour expiry window. For UKG authentication, ml-connector presents HTTP Basic Auth credentials plus the two API key headers on every request, or uses OAuth2 client credentials with token refresh logic. Because Zoho Books supports webhooks, ml-connector can receive push notifications for invoice and expense changes, but also supports polling via the list endpoint with offset pagination to cover any missed events. Expense records are mapped first by vendor to UKG cost centers, ensuring every GL posting references a cost center that already exists in UKG. UKG GL posting is handled via the third-party pay endpoint with GL account segment codes; ml-connector tracks the structure of these segments per tenant and validates them before posting. Rate limits are handled with exponential backoff: Zoho Books enforces 100 requests per minute and daily limits by plan, while UKG limits are tenant-specific. Every record carries an audit trail and can be replayed if a downstream GL posting fails.

A real-world example

A mid-sized services company uses Zoho Books for accounting and UKG for payroll across three offices. Consultants submit expenses monthly, which are coded to projects and cost centers in Zoho Books. Before the integration, the finance team extracted the expense register from Zoho Books at month-end, manually matched each expense to the correct UKG cost center and GL account, and prepared a payroll journal entry for posting. With Zoho Books and UKG connected, expenses flow automatically into UKG's payroll journal as they are approved in Zoho Books, mapped to the correct cost center and GL account for each office. The finance team no longer re-keys expense data, and month-end payroll posting is ready days earlier.

What you can do

• •Sync vendor payment records from Zoho Books and map them to UKG cost centers and GL account segments.
• •Handle Zoho Books regional OAuth2 authentication and token refresh, plus UKG HTTP Basic Auth with API key headers.
• •Read invoices and expense categories from Zoho Books to identify business expenses and match them to UKG cost center dimensions.
• •Post expense-derived GL journal entries into UKG via the third-party pay endpoint with proper GL account segment coding.
• •Receive Zoho Books webhook push events for invoices, bills, and expenses, with fallback polling support for missed events.

Questions

Which direction does data move between Zoho Books and UKG?

The main flow is from Zoho Books into UKG. Expenses, vendor payments, and cost categories from Zoho Books are read and mapped to UKG cost centers and GL account segments, then posted as GL journal entries in UKG's payroll module. Zoho Books is read-only on the ml-connector side; UKG receives the mapped records for GL posting.

How does ml-connector handle Zoho Books regional routing and token expiry?

Zoho Books returns the region (api_domain) in the OAuth token response. ml-connector reads this field and routes all subsequent API calls to the correct regional base URL (e.g., zohoapis.eu for EU customers). Access tokens expire after 1 hour, so ml-connector refreshes tokens proactively at 55 minutes to avoid mid-call failures.

How are expenses mapped to UKG cost centers and GL accounts?

ml-connector reads the vendor and expense category from each Zoho Books invoice or expense record, then matches the vendor to a UKG cost center configuration stored per customer. GL account segments are determined by the cost center and expense category; ml-connector validates these segments exist in UKG before posting the GL journal entry via the third-party pay endpoint.