MYOB and Airbase integration

What moves between them

Purchase bills flow from MYOB into Airbase based on a polling schedule. Approved purchase orders and vendor payments from Airbase are posted back into MYOB's purchase orders and supplier payments. Vendor and contact records sync bidirectionally so both systems stay aligned on the source of truth for supplier information. GL accounts in Airbase remain read-only; all financial dimension updates originate in MYOB.

How ml-connector handles it

ml-connector stores MYOB OAuth token and company file credentials encrypted, refreshing the short-lived access token when it expires after 20 minutes so authentication never stalls. It polls MYOB bills and purchase orders using OData $filter on LastModified to detect changes since the last sync, respecting MYOB's 8 request per second rate limit and 1,000,000 daily request cap. For Airbase, it presents the static API bearer token on each request. Before posting to either system, ml-connector validates vendor and GL account references exist and maps them between systems. The RowVersion field required by MYOB for updates is tracked to prevent 409 conflicts. Vendor syncs use pre-checks to avoid duplicate posts where MYOB has no idempotency key support. Every record carries a full audit trail and failed records are replayed from the queue.

A real-world example

A regional distribution company manages their AP in MYOB AccountRight and uses Airbase to control spending, approve purchase orders, and issue vendor payments across multiple locations. Before the integration, the finance team entered approved purchase orders from Airbase into MYOB by hand and exported bills from MYOB to reconcile with Airbase each month, creating bottlenecks during month-end close and risking re-entry errors. With MYOB and Airbase connected, purchase bills flow into Airbase automatically, approved orders post into MYOB without re-keying, and vendor master data stays synchronized. Reconciliation is faster and manual data entry is eliminated.

What you can do

• •Poll MYOB bills and purchase orders and post them into Airbase on a schedule, with automatic retries on rate limit and connection failures.
• •Sync vendor records bidirectionally between MYOB and Airbase so both systems stay aligned on supplier master data.
• •Post approved purchase orders and vendor payments from Airbase back into MYOB's purchase orders and supplier payment modules.
• •Authenticate MYOB with OAuth2 and company file credentials, refreshing short-lived access tokens automatically, and Airbase with static bearer tokens.
• •Track the MYOB RowVersion on updates to prevent conflicts and maintain a complete audit trail with replay capability on failed records.

Questions

Which direction does data move between MYOB and Airbase?

Purchase bills and orders flow from MYOB into Airbase. Approved purchase orders and vendor payments flow from Airbase back into MYOB. Vendor records sync bidirectionally in both directions. GL accounts in Airbase remain read-only, so financial dimension changes come from MYOB only.

How does ml-connector handle MYOB's short token expiry and company file authentication?

MYOB access tokens expire after 20 minutes. ml-connector caches the refresh token and automatically fetches a new access token when one expires, preventing authentication stalls. Company file credentials are stored encrypted and supplied with every request in the required headers alongside the OAuth bearer token.

How does the integration detect new or changed records in MYOB if there are no webhooks?

ml-connector polls MYOB using OData $filter on the LastModified timestamp field to detect bills and orders that changed since the last sync. The polling schedule is configurable and respects MYOB's rate limit of 8 requests per second and 1,000,000 requests per day per API key.