Does every Amazon order create an invoice in MYOB immediately?

No, ml-connector polls Amazon on a schedule you set, typically daily or weekly aligned with your settlement cycle. Each order flows into MYOB as a sales invoice after the next polling run, with the Amazon order ID and marketplace region recorded for reference. If an order is modified or refunded on Amazon before the polling run, the sync detects the change and updates the MYOB invoice accordingly.

How does ml-connector handle MYOB's company file credentials and Amazon's OAuth2 at the same time?

ml-connector stores both credential sets encrypted and refreshes them on separate schedules. It supplies MYOB's company file password and API Key on every request, refreshing the bearer token every 15 minutes. Amazon's token is refreshed hourly. If either side returns a 401 (bad credentials), the sync pauses and alerts you; the fix is to re-authorize the app in both systems and update the stored credentials.

What if Amazon's settlement structure does not match MYOB's GL chart of accounts?

ml-connector uses a configuration table to map Amazon settlement event types (orders, shipping, refunds, fees) to MYOB GL account and tax code pairs. You define the mapping once during setup, and every settlement event posts to the correct account automatically. If your GL structure changes, the mapping is updated in the configuration without redeploying or re-syncing historical data.

MYOBAmazon Seller Central

MYOB and Amazon Seller Central integration

MYOB runs accounting for SMEs across Australia and New Zealand. Amazon Seller Central manages your merchant store, orders, and settlement payouts. When the two are connected, orders placed on Amazon become invoices in MYOB automatically, settlement deposits map to the correct GL accounts and customers, and reconciliation becomes straightforward instead of manual re-entry. ml-connector keeps your P&L accurate and your cash records clean.

How MYOB works

MYOB Business API exposes contacts, purchase and sales documents, invoices, payments, GL accounts, inventory items, and journal entries through REST with OData v3 query parameters. The API requires OAuth2 bearer token, API Key header, and Base64-encoded company file credentials on every call. Access tokens expire in 20 minutes and must be refreshed; company file passwords must be stored and supplied with each request. MYOB does not support webhooks, so changes are detected by polling with OData $filter on LastModified timestamps. The API enforces rate limits of 8 requests per second and 1,000,000 requests per day.

How Amazon Seller Central works

Amazon Seller Central exposes orders, financial events, settlements, inventory, catalog items, and reports through the Selling Partner API, a REST service with regional endpoints for North America, Europe, and Far East. All calls require OAuth2 authorization via Login with Amazon, with access tokens valid for 1 hour. Financial settlement events and invoice results are available only through polling; push notifications via EventBridge or SQS are optional and do not cover all event types. Reports API is asynchronous and requires polling for completion and downloading results from presigned S3 URLs.

What moves between them

Orders and payments flow from Amazon Seller Central into MYOB. Each Amazon order becomes a sales invoice in MYOB, mapped to the customer contact. Settlement deposits, refunds, and fees are posted as sales transactions to the GL account and customer linked in the configuration. Stock levels flow in both directions if inventory is managed in both systems; MYOB item master codes map to Amazon catalog items. All transactions carry the Amazon order reference and marketplace region for auditability.

How ml-connector handles it

ml-connector stores MYOB company file credentials encrypted and presents them on every API call along with the OAuth token and API Key. It refreshes the MYOB token every 15 minutes and the Amazon token at hour boundaries, and gracefully retries on 401 (invalid credentials) by treating it as a sync block rather than a silent failure. On the Amazon side, it polls Orders and Finances APIs on a schedule tied to your settlement cycle, mapping order line items to MYOB invoice line items, and settlement events to GL accounts and tax codes configured per marketplace. MYOB's RowVersion field is tracked to prevent conflicts on updates. Because MYOB has no idempotency key header, ml-connector uses BullMQ jobId deduplication to prevent accidental duplicate invoice creation if a sync job retries.

A real-world example

An online retailer sells home goods through Amazon across Australia and New Zealand. Orders arrive daily, settlements deposit weekly. Before the integration, the accounting team exported settlement reports from Amazon and manually created sales invoices in MYOB, allocating shipping fees and refunds to separate GL accounts, then reconciled bank deposits against invoices by hand. With MYOB and Amazon Seller Central connected, each order creates an invoice within hours, settlement deposits post to the cash GL account with fees and refunds split correctly, and weekly reconciliation is a single click to match bank deposits to invoice totals.

What you can do

Automatically create MYOB sales invoices from Amazon orders, with line items, quantities, and pricing mapped to inventory and tax codes.
Post Amazon settlement deposits and fees to the correct MYOB GL account and tax treatment on a weekly schedule.
Map Amazon customers to MYOB contact records and update them if customer details change in Amazon.
Handle MYOB's three-part authentication and Amazon's OAuth2 token lifecycle with automatic refresh and error replay.
Track all order-to-invoice and settlement-to-GL mappings in a full audit trail for month-end close and dispute resolution.

Questions

Does every Amazon order create an invoice in MYOB immediately?: No, ml-connector polls Amazon on a schedule you set, typically daily or weekly aligned with your settlement cycle. Each order flows into MYOB as a sales invoice after the next polling run, with the Amazon order ID and marketplace region recorded for reference. If an order is modified or refunded on Amazon before the polling run, the sync detects the change and updates the MYOB invoice accordingly.
How does ml-connector handle MYOB's company file credentials and Amazon's OAuth2 at the same time?: ml-connector stores both credential sets encrypted and refreshes them on separate schedules. It supplies MYOB's company file password and API Key on every request, refreshing the bearer token every 15 minutes. Amazon's token is refreshed hourly. If either side returns a 401 (bad credentials), the sync pauses and alerts you; the fix is to re-authorize the app in both systems and update the stored credentials.
What if Amazon's settlement structure does not match MYOB's GL chart of accounts?: ml-connector uses a configuration table to map Amazon settlement event types (orders, shipping, refunds, fees) to MYOB GL account and tax code pairs. You define the mapping once during setup, and every settlement event posts to the correct account automatically. If your GL structure changes, the mapping is updated in the configuration without redeploying or re-syncing historical data.

Connect MYOB and Amazon Seller Central

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started