Zoho Books and TrueCommerce integration

What moves between them

Purchase orders and invoices flow bidirectionally. TrueCommerce EDI documents (X12 850 purchase orders, 810 invoices, 856 advance ship notices) are transformed into Zoho Books bills and purchase orders on a scheduled pull from TrueCommerce SFTP. Zoho Books invoices flow back to TrueCommerce for formatting into 810 remittance advice and routing to the EDI network. Vendor payments and customer payment data from Zoho can be mapped to remittance advice (820) documents. The sync frequency is determined by polling intervals configured per customer, typically daily or hourly.

How ml-connector handles it

ml-connector stores Zoho OAuth2 credentials and proactively refreshes access tokens at 55-minute intervals to avoid expiry mid-request. It routes all Zoho calls to the correct regional endpoint determined by the organization's region field from the token response. On the TrueCommerce side, it manages SFTP credentials encrypted in the database and connects to integrationftp.truecommerce.com on a scheduled basis to pull and push files. X12 EDI documents are parsed and normalized into Zoho Books line-item structures, mapping EDI item identifiers to Zoho Items and allocating amounts to Zoho Chart of Accounts entries. Reverse transformation maps Zoho invoices into X12 810 format with segment control numbers for TrueCommerce. ISA control numbers ensure deduplication on the TrueCommerce side. The connector retries failed SFTP connections and Zoho API calls with exponential backoff, and tracks the full audit trail so any failed file can be manually reviewed and replayed.

A real-world example

A mid-sized distributor uses Zoho Books for accounting and invoicing. They source from dozens of suppliers via EDI through TrueCommerce, receiving purchase orders and invoices from an EDI network daily. Before the integration, the operations team downloaded files from TrueCommerce Transaction Manager manually, parsed X12 850 purchase orders with a spreadsheet script, and re-entered bills into Zoho Books by hand, a process that took 2-3 hours per day and introduced frequent data entry errors. With Zoho Books and TrueCommerce connected, EDI purchase orders flow automatically into Zoho as structured bills, matched to the correct vendor and GL account. Invoices posted in Zoho are formatted and routed back through TrueCommerce to confirm receipt with trading partners. The manual file handling step is eliminated, errors drop, and the accounting team gets real-time visibility into incoming EDI transactions.

What you can do

• •Transform X12 850 purchase orders and 856 advance ship notices from TrueCommerce into Zoho Books bills and purchase orders, allocated to the correct vendors and GL accounts.
• •Map Zoho Books invoices to X12 810 remittance advice format for outbound delivery through TrueCommerce to EDI trading partners.
• •Manage Zoho OAuth2 token refresh and regional endpoint routing, and SFTP credential encryption for TrueCommerce.
• •Schedule daily or hourly pulls from TrueCommerce SFTP to keep orders and invoices in sync with Zoho Books.
• •Provide full audit trails and replay capability for any failed EDI document transformation or file transfer.

Questions

Does ml-connector support all X12 document types that TrueCommerce handles?

ml-connector focuses on the core supply chain documents: 850 purchase orders, 856 advance ship notices, and 810 invoices. Other EDI documents (997 functional acknowledgments, 820 remittance advice, 945 warehouse shipping advice) are parsed and logged but transformation to Zoho depends on your use case. Advanced transformation requirements are handled via custom mappers.

How does ml-connector handle TrueCommerce's lack of a public API and customer-specific file paths?

TrueCommerce provisioning is manual. During onboarding, you provide your SFTP credentials and confirm file naming conventions and paths with TrueCommerce support. ml-connector uses those paths to poll SFTP on your configured schedule. The managed Exchange API is an alternative if TrueCommerce configures it for your account, and ml-connector adapts to either transport without code changes.

What happens if Zoho Books regional URLs or TrueCommerce file formats change?

Zoho Books regional URLs are fixed per customer and returned in the OAuth token response - ml-connector stores the region on first authentication and routes all calls accordingly. TrueCommerce file paths and formats are customer-specific and stored in the integration configuration. If a path or format changes, you update the stored configuration and the next scheduled pull uses the new values.