Sage 300 and Zuora integration

What moves between them

Orders and invoices flow from Sage 300 into Zuora. When a new order is created in Sage 300's Order Entry module, ml-connector polls and transforms it into a Zuora subscription tied to the matching customer account. When an order is invoiced in Sage 300, the invoice details are synced to Zuora so the subscription invoice reflects the Sage 300 amounts and line items. In the reverse direction, when Zuora posts an invoice, ml-connector can read the invoice back into Sage 300's general ledger for revenue recognition, mapped to the correct AR accounts and customer dimensions.

How ml-connector handles it

ml-connector stores Sage 300 credentials encrypted and encodes them as HTTP Basic Auth on every request. It polls Sage 300's OEOrders and ARInvoiceBatches endpoints on a schedule using OData date filters and pagination, transforming new records into Zuora API calls authenticated with OAuth2 bearer tokens. For the Zuora direction, ml-connector registers a webhook endpoint and receives invoice notifications from Zuora, validates them with HMAC-SHA256, and posts the invoice data into Sage 300's GLJournalBatches for revenue recognition. If a Zuora API call returns 429 (rate limit), ml-connector backs off and retries after a delay, respecting Zuora's 50,000 RPM production limit. Sage 300 polling uses date/time filters to avoid re-processing the same records, and every transaction carries a full audit trail so records can be replayed if a downstream posting fails.

A real-world example

A mid-market SaaS company runs Sage 300 on-premise for general finance and order management, and uses Zuora for subscription billing and revenue recognition. Before the integration, orders entered in Sage 300 were manually re-keyed into Zuora, creating duplicate entry work and reconciliation gaps between the order system and the billing system. Each month, the revenue team had to chase invoice amounts and line items across both systems to reconcile billings. With Sage 300 and Zuora connected, new orders in Sage 300 automatically become Zuora subscriptions, invoice amounts stay in sync, and the general ledger is updated from Zuora invoices without manual re-entry. Month-end revenue recognition now pulls directly from Zuora data, and duplicate keying is eliminated.

What you can do

• •Poll Sage 300 for new orders and sync them to Zuora subscriptions with customer and product mapping.
• •Sync invoice amounts and line items from Sage 300 orders into Zuora billing records.
• •Receive invoice notifications from Zuora via webhook and post them to Sage 300's general ledger for revenue recognition.
• •Authenticate Sage 300 with HTTP Basic Auth and Zuora with OAuth2 client credentials, handling credential rotation and token refresh.
• •Track every order and invoice transformation with a full audit trail and support replay if a downstream posting fails.

Questions

Which direction does data move between Sage 300 and Zuora?

Orders and invoices flow from Sage 300 into Zuora, so new orders in Sage 300 become Zuora subscriptions and invoices stay in sync. Zuora also pushes invoice notifications back to ml-connector, which posts them into Sage 300's general ledger for revenue recognition. This keeps both systems aligned without duplicate data entry.

How does ml-connector handle Sage 300's HTTP Basic Auth requirement?

ml-connector stores the Sage 300 username and password encrypted, encodes them as HTTP Basic Authentication on every API request, and ensures both credentials are uppercase as required by Sage 300. Because Sage 300 is self-hosted on the customer's IIS server, ml-connector connects to the customer-specific hostname, not a shared Sage-managed endpoint.

Does ml-connector use Zuora webhooks or polling?

ml-connector registers a webhook endpoint with Zuora to receive invoice and subscription notifications in real time, which is more efficient than polling. Webhook payloads carry only the object ID, so ml-connector calls back to Zuora to fetch the full invoice record before posting it to Sage 300. If Zuora's rate limit is hit, ml-connector backs off and retries with exponential delay.