MYOB and Stampli integration

What moves between them

Purchase invoices and orders flow from MYOB into Stampli as CSV files written to the SFTP inbound directory, mapped to Stampli's invoice and PO schema. Supplier records and GL accounts flow in both directions: MYOB suppliers are written as vendor records to Stampli, and Stampli's chart of accounts is read back into MYOB as reference data for PO cost allocation. The sync runs on a polling schedule of your choosing, typically aligned with your daily invoice and approval cycles. Invoices posted in MYOB are detected using LastModified filters and pushed to Stampli in the next polling window. Vendor master data is synchronized bidirectionally every 24 hours to keep both systems aligned.

How ml-connector handles it

ml-connector stores MYOB OAuth2 credentials and company file username/password encrypted, refreshing the access token when it approaches expiry to avoid 401 errors mid-sync. SFTP credentials for Stampli are also encrypted and used to open file connections at sync time. On the MYOB side, ml-connector polls purchase invoices and orders using OData $filter on LastModified and the RowVersion field, batching reads to stay within the 8 requests-per-second rate limit. Each record is validated against MYOB's required fields before transformation. On the Stampli side, invoices and orders are formatted as CSV files and written to the inbound SFTP directory in the format Stampli expects, with dedup logic to avoid reprocessing. Supplier records from MYOB are flattened into a vendor CSV with Stampli's required fields (name, email, address, tax ID where available). MYOB's GL accounts are read as reference data and stored locally so PO lines can be validated before they reach Stampli. If an SFTP write fails, ml-connector retries with exponential backoff, and every record carries an audit log entry with its file hash and timestamp for replay or forensics if a downstream workflow fails.

A real-world example

A mid-sized Australian goods distributor uses MYOB for accounting and order management, and Stampli for invoice processing and three-way matching. Before the integration, the accounts payable team manually exported invoices from MYOB, uploaded them to Stampli in CSV format, and re-keyed the supplier data in Stampli when MYOB contacts changed. With MYOB and Stampli connected, each purchase invoice and order syncs automatically to Stampli on a daily schedule, supplier master data stays aligned, and three-way matching happens against POs that are current in both systems. Invoice processing starts with clean, current data, and the manual re-keying step is gone.

What you can do

• •Sync MYOB purchase invoices and orders to Stampli as CSV files on a polling schedule you control, with automated dedup and retry logic.
• •Keep supplier master data aligned between MYOB contacts and Stampli vendors so invoice matching has current vendor records.
• •Map MYOB general ledger accounts to Stampli for cost allocation and account validation on purchase orders.
• •Authenticate MYOB with OAuth2 and company file credentials, and Stampli with SFTP, storing both credential sets encrypted and refreshing tokens before expiry.
• •Maintain a complete audit trail of every invoice, order, and vendor record synced, with file hashes and timestamps for forensics and replay.

Questions

How does ml-connector bridge the different authentication schemes between MYOB and Stampli?

MYOB requires OAuth2 plus company file username and password in every API request header. Stampli uses only SFTP credentials with no OAuth2 or API keys. ml-connector stores both credential sets encrypted and manages token refresh on the MYOB side while maintaining persistent SFTP connections on the Stampli side. Access tokens are refreshed before they expire at 20 minutes to avoid 401 errors mid-sync.

Why does the integration use file-based SFTP to Stampli instead of a REST API?

Stampli does not publish a public REST API for third-party integrators; SFTP with flat files (CSV or XML) is the only path available without a formal Stampli partnership agreement. ml-connector formats MYOB invoices, orders, and vendors as CSV files and writes them to Stampli's inbound SFTP directory on a polling schedule.

How does the integration handle MYOB's rate limits and Stampli's lack of webhooks?

MYOB enforces 8 requests per second and 1,000,000 requests per day per API key. ml-connector batches reads and respects these limits, returning HTTP 429 if exceeded. Since neither MYOB nor Stampli publish webhooks, ml-connector polls both systems on a schedule you define, typically daily for invoices and every 24 hours for vendor master data, using OData $filter on LastModified in MYOB to detect changes efficiently.