MYOB and Ramp integration

What moves between them

Purchase invoices and bills created in MYOB flow into Ramp on a polling schedule. For each MYOB bill, ml-connector creates a corresponding Ramp bill with the supplier, amount, GL account mapping, and any custom spend dimensions. The integration polls MYOB every 30 minutes for bills with LastModified timestamps newer than the last sync marker, translates MYOB supplier contacts to Ramp vendors using name matching, and maps MYOB GL accounts to Ramp GL Accounts by account code. The flow is one-directional from MYOB into Ramp; Ramp bill updates and payments flow back to Ramp webhooks for audit only.

How ml-connector handles it

ml-connector stores MYOB OAuth credentials and company file username/password encrypted, and refreshes the OAuth token before every sync window when the 20-minute lifetime nears expiry. On each poll it sends the company file credentials as x-myobapi-cftoken and x-myobapi-key headers alongside the bearer token. It uses OData $filter on LastModified to fetch only bills changed since the prior sync, handles the 1000-record page size limit by paging through results, and retries on HTTP 429 rate-limit responses with exponential backoff. For Ramp, it presents OAuth2 Client Credentials tokens valid for 10 days, and every MYOB bill becomes a Ramp bill with GL account and department tags matched by the supplier name and MYOB account code. The RowVersion field on MYOB bills is never updated by ml-connector, so concurrent changes in MYOB do not produce 409 conflicts on read operations. Ramp webhooks on bill.created and bill.updated are registered once and provide real-time notifications for audit and downstream flow triggers.

A real-world example

An Australian SME importing goods and services across multiple departments uses MYOB for accounting and Ramp for corporate cards and bill approval. Before integration, the finance controller received invoices in MYOB from vendors, manually created bill records in Ramp for spend visibility, and cross-checked the two systems monthly to ensure no invoices were missed. The payables team had no real-time visibility into which invoices were approved in Ramp. With MYOB and Ramp connected, each MYOB invoice automatically appears as a Ramp bill tagged with the correct GL account and cost center, and the team approves bills in Ramp while MYOB remains the ledger of record. Reconciliation is instant, and invoices are never re-keyed.

What you can do

• •Sync MYOB purchase invoices and bills into Ramp on a polling schedule, with LastModified timestamp filtering to find only new and changed records.
• •Map MYOB suppliers to Ramp vendors by name matching, creating vendor records implicitly as bills are entered.
• •Allocate MYOB GL accounts and cost centers to Ramp bills using account code and custom dimension matching.
• •Refresh MYOB OAuth tokens and company file credentials automatically, and retry on rate limits and 429 responses with exponential backoff.
• •Track audit events and support bill replay if a downstream Ramp approval or posting fails.

Questions

Does the integration create vendors in Ramp automatically?

Yes. Ramp does not have a direct vendor creation endpoint, so ml-connector creates vendors implicitly when a bill is entered. Each MYOB supplier is matched by name to a Ramp vendor, and if no vendor exists, Ramp creates it during bill creation.

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

ml-connector stores MYOB OAuth credentials and company file username/password encrypted. On every API call it sends three headers: the Authorization Bearer token, the x-myobapi-key API key, and x-myobapi-cftoken with Base64-encoded company file credentials. OAuth tokens expire in 20 minutes, so ml-connector refreshes them before each polling window.

What happens if MYOB and Ramp bill data falls out of sync?

ml-connector tracks every bill sync in an audit log with the MYOB RowVersion and Ramp bill ID. If a Ramp operation fails, the bill can be replayed without re-fetching from MYOB. The polling filter uses LastModified timestamps, so manual changes to MYOB bills will be detected and re-synced on the next polling cycle.