MYOB and Cin7 integration

What moves between them

Purchase invoices and suppliers flow from MYOB into Cin7 on a polling schedule. After each sync run, ml-connector reads MYOB's Contacts marked as suppliers and Bills within a date window, maps them to Cin7 supplier and purchase records, and creates or updates them in Cin7. Supplier master data (name, ABN, contact details) aligns in both systems, while purchase invoice line items land as Cin7 purchase records with the correct Approach field to mark them as invoices.

How ml-connector handles it

ml-connector stores MYOB credentials encrypted and builds each API call with three required headers: the OAuth bearer token (refreshing it every 20 minutes before expiry), the API key, and the Base64 company file token. It uses OData $filter on LastModified to detect changes since the last run, working around MYOB's lack of webhooks. Cin7 authentication uses simple custom API key headers with no expiry. MYOB rate limits at 8 requests/second, so ml-connector throttles requests and backs off on 429 responses. RowVersion tracking ensures PATCH operations do not collide with concurrent updates. Supplier and purchase records are mapped by external reference so re-runs do not duplicate. A full audit trail tracks every record created, updated, or skipped due to data mismatches.

A real-world example

A small product business in Australia uses MYOB for accounting and Cin7 Core to manage inventory and purchase orders across two warehouses. Before the integration, purchase invoices received from suppliers in MYOB had to be manually entered into Cin7, delaying stock receipt matching and creating reconciliation work at month-end. With MYOB and Cin7 Core connected, each supplier invoice from MYOB flows into Cin7 automatically, mapped to the matching supplier record. The business confirms stock receipt in Cin7 against the invoice that came from MYOB, and the two systems stay aligned without manual re-keying.

What you can do

• •Sync suppliers from MYOB Contacts into Cin7, keeping name, ABN, and contact details aligned.
• •Flow purchase invoices from MYOB Bills into Cin7 on a schedule you control, mapped to the correct supplier.
• •Detect changes using MYOB's OData LastModified timestamps, handling the lack of webhooks with efficient polling.
• •Authenticate MYOB with OAuth, API key, and company file credentials, and Cin7 with custom API keys.
• •Map MYOB purchase line items to Cin7 purchase records with the correct Approach field to mark them as invoices.

Questions

How does ml-connector handle MYOB's dual authentication requirement?

MYOB requires OAuth bearer token, API key, and Base64-encoded company file credentials on every call. ml-connector stores all three encrypted, refreshes the OAuth token every 20 minutes before expiry, and includes all three headers on each API request. If the company file token is wrong or expires, MYOB returns 401 and ml-connector surfaces the error.

Why does ml-connector poll MYOB instead of waiting for webhooks?

MYOB does not support webhooks on the AccountRight Live API. ml-connector uses OData $filter on LastModified timestamps to detect changes since the last run, polling on a schedule tied to your business cycle. This avoids constant polling of unchanged records and keeps Cin7 up to date without manual intervention.

How are MYOB purchase invoices mapped to Cin7 purchases?

MYOB Bills become Cin7 purchases with Approach set to INVOICE to mark them in the procure-to-pay lifecycle. Supplier references are matched by ABN or external ID so re-runs do not duplicate. Line items from MYOB invoices land as individual Cin7 purchase line records tied to the correct supplier.