MYOB and TrueCommerce integration

What moves between them

The main flow is MYOB to TrueCommerce outbound. MYOB purchase orders are read on a schedule, transformed into X12 850 EDI format, and uploaded to TrueCommerce SFTP for routing to suppliers. Return flow brings TrueCommerce inbound documents (856 Advance Ship Notice and 810 Invoice) back into MYOB as received items, inventory adjustments, and supplier invoice records. The sync runs on a frequency you configure, typically hourly, checking for new or updated records in MYOB since the last poll.

How ml-connector handles it

ml-connector stores MYOB OAuth token and company file credentials encrypted and refreshes the bearer token when calls return 401. For TrueCommerce, it maintains SFTP credentials and connects to integrationftp.truecommerce.com port 22 on each scheduled run. Outbound: MYOB purchase orders are fetched using OData $filter on LastModified, mapped to MYOB supplier contacts, items, and GL accounts, then transformed into X12 850 messages with ISA segments and control numbers for deduplication. Files are uploaded to TrueCommerce SFTP under the configured integration path. Inbound: MYOB polls TrueCommerce SFTP hourly for new 856 and 810 documents, parses the X12 format, extracts line-item detail and supplier references, and creates received-goods records and supplier invoices in MYOB against matching purchase orders. MYOB's RowVersion field on PATCH operations is handled via pre-check with OData $filter; if the version has changed, the update retries on the next sync cycle. TrueCommerce file naming conventions are customer-specific and confirmed during setup.

A real-world example

A mid-sized NZ distributor runs MYOB for accounting and finance, buying from 20+ suppliers globally through a TrueCommerce-managed VAN. Before integration, the procurement team entered purchase orders in MYOB, then manually formatted them as EDI files and uploaded them to TrueCommerce FTP for each supplier. When suppliers shipped, the team downloaded advance ship notices from TrueCommerce, matched them to MYOB POs by hand, and entered received quantities into inventory. With MYOB and TrueCommerce connected, purchase orders flow automatically from MYOB to TrueCommerce, and inbound 856 and 810 messages post back to MYOB as received items and supplier invoices, cutting procurement overhead and cutting the order-to-receipt cycle by one day.

What you can do

• •Transform MYOB purchase orders into X12 850 EDI messages and upload to TrueCommerce SFTP for supplier distribution.
• •Pull TrueCommerce inbound 856 Advance Ship Notices and 810 Invoices back into MYOB as received goods and supplier invoice records.
• •Map MYOB supplier contacts, items, GL accounts, and cost centers to X12 EDI segments with ISA control numbers for deduplication.
• •Refresh MYOB OAuth bearer tokens on 401 and handle RowVersion conflicts on PATCH operations via OData pre-checks.
• •Poll MYOB and TrueCommerce on a schedule you control, with full audit trail and error replay on every EDI transformation.

Questions

Which direction does data move between MYOB and TrueCommerce?

MYOB purchase orders flow outbound to TrueCommerce as X12 850 EDI messages for supplier distribution. Inbound, TrueCommerce 856 Advanced Ship Notices and 810 Invoices flow back into MYOB as received goods and supplier invoice records. The integration is bidirectional but operates on different cadences: outbound on every new or changed MYOB PO, inbound on a scheduled hourly poll.

How does the integration handle MYOB's OAuth token expiry and company file credentials?

ml-connector stores both the OAuth bearer token and the company file username/password encrypted. When an API call returns 401, it refreshes the bearer token using the stored refresh token without re-prompting. The company file credentials are sent with every API call in the x-myobapi-cftoken header and do not require refresh.

What happens if a TrueCommerce EDI file arrives in MYOB format that does not match an existing purchase order?

ml-connector requires an ISA control number in the X12 856 or 810 message to correlate it to the MYOB PO. If no matching PO is found, the record is logged in the audit trail with a cross-reference error. The record is not posted to MYOB; the operator reviews the error and either creates the missing PO or marks the inbound message as a correction in a follow-up sync.