Infor CloudSuite and Zuora integration

What moves between them

The main flow is Zuora into Infor CloudSuite. After a billing period closes or when revenue is recognized in Zuora, ml-connector reads invoices, payment records, and credit memos from Zuora and posts them into Infor CloudSuite's accounts receivable (ARS100MI) and general ledger (CRS630MI / GL posting). Revenue accounts, customer codes, and cost centers are mapped first so every invoice lands on a valid Infor GL account and customer. Payment records from Zuora update applied amounts in Infor CloudSuite. The sync runs on a schedule aligned with your billing calendar; Zuora webhook notifications can trigger immediate reads when payments post in Zuora, reducing polling frequency.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the .ionapi file fields and OAuth client credentials for Infor CloudSuite, and the multi-region base URL and OAuth client credentials for Zuora. On each sync cycle, it refreshes the Infor ION token (proactively before expiry to prevent timeout) and the Zuora token (which expires in 1 hour). It polls Zuora's invoice and payment endpoints using cursor-based pagination (max 40 records per page) and the customer's region-specific base URL. For each Zuora invoice, it looks up the matching Infor CloudSuite customer by code, retrieves the GL account and cost center from a pre-configured mapping, and calls the Infor ARS100MI Add methods to create or update the invoice header and lines. Payment records trigger ARS110MI calls to record cash applications. Infor CloudSuite enforces a CONO (company number) parameter on all operations, which is captured per customer at setup. Rate limits are respected: Infor ION typically allows 100 to 500 requests per minute, and Zuora allows up to 50,000 requests per minute in production. Every record carries a job ID for dedup and idempotency, and if a downstream call fails, the record is retried on the next cycle.

A real-world example

A mid-market SaaS company runs Zuora for subscription management and recurring billing across enterprise and mid-market customer tiers. Finance uses Infor CloudSuite M3 for general ledger, accounts receivable, and cost center tracking across three business units. Before the integration, the finance team exported invoice registers from Zuora weekly and manually entered them into Infor CloudSuite, mapping subscription line items to the correct GL accounts and cost centers. Invoices often posted late or with incorrect allocations, causing reconciliation delays and month-end close friction. With Zuora and Infor CloudSuite connected, invoices flow automatically into AR and GL each time a subscription billing period closes, mapped to the correct customer, cost center, and revenue account. Payment receipts from Zuora post as cash applications in Infor, eliminating manual re-entry and keeping the subsidiary ledgers and general ledger aligned.

What you can do

• •Post Zuora invoices and credit memos into Infor CloudSuite accounts receivable and general ledger, mapped to the correct GL accounts and cost centers.
• •Record Zuora payments and cash applications in Infor CloudSuite as invoice settlements and general journal entries.
• •Align customer codes, cost centers, and GL accounts between Zuora and Infor CloudSuite so revenue lands on valid dimensions.
• •Authenticate Zuora with OAuth 2.0 Client Credentials and Infor CloudSuite with the ION API Gateway service account, handling token expiry and multi-region base URLs.
• •Poll on a billing-driven schedule with support for Zuora webhook notifications to trigger immediate reads, full audit trail, and automatic dedup and retry on failure.

Questions

Which direction does data move between Infor CloudSuite and Zuora?

The main flow is Zuora into Infor CloudSuite. Invoices, payments, and revenue records move from Zuora into Infor CloudSuite's accounts receivable and general ledger. Customer codes, GL accounts, and cost centers are pre-mapped so every Zuora invoice posts to the correct Infor dimension. Infor CloudSuite does not write back to Zuora.

How does ml-connector handle Zuora's multi-region base URLs and Infor's per-customer ION tenant configuration?

ml-connector captures the Zuora region-specific base URL and the .ionapi file fields (which contain the Infor ION base URL, tenant ID, and OAuth endpoints) per customer at setup. It uses the correct region and tenant for every API call. Token endpoints are constructed from the .ionapi file, and Zuora OAuth tokens are refreshed when the 1-hour expiry approaches.

What happens if a Zuora invoice fails to post into Infor CloudSuite?

ml-connector assigns each invoice a job ID for dedup and stores the failed record with its error. On the next poll cycle, it retries the failed record with the same job ID. If the Infor post eventually succeeds, dedup prevents duplicate entries. The full audit trail shows every attempt and error, so you can replay or investigate failures.