MYOB and Orderful integration

What moves between them

Purchase orders created in MYOB flow outbound to Orderful as EDI 850 purchase order documents and are routed to the correct supplier based on the contact's ISA identifier. Supplier invoices in MYOB are sent to Orderful as EDI 810 invoices for delivery to trading partners. Incoming EDI 856 shipment notices from trading partners arrive at Orderful, are translated back to MYOB format, and are posted as purchase receipt records so inventory is updated. EDI 855 purchase order acknowledgments from suppliers flow in the same way. Outbound documents are pushed by MYOB whenever an order or invoice is created or modified; inbound documents arrive at Orderful on a webhook or polling cadence and are processed within minutes.

How ml-connector handles it

ml-connector handles MYOB's three-part authentication (Bearer token + API Key + company file credentials) and refreshes the Bearer token automatically before each request when the 20-minute window approaches. On the Orderful side, the static API Key is stored encrypted and appended to every request. Outbound purchases are read from MYOB via OData filtering on LastModified and are transformed into EDI 850 and 810 documents; the supplier contact's ISA identifier determines which trading partner receives the order. Inbound documents arrive at Orderful via webhook or polling and are parsed by transaction type (856 shipment notice, 855 acknowledgment); ml-connector then translates them back to MYOB PurchaseReceipt objects and posts them to the company file with the original supplier reference intact. MYOB's rate limit of 8 requests per second is respected with backoff, and every transaction is logged for audit and replay if a downstream call fails. ISA identifiers must be configured for each supplier contact before the integration can route orders correctly.

A real-world example

A mid-sized SME distributor in Australia runs MYOB for accounting and order management and relies on a network of overseas suppliers who exchange EDI documents. Previously, the purchasing team created orders in MYOB and manually exported them to a CSV, reformatted the data, and emailed or uploaded it to each supplier's EDI inbox. When shipments arrived, they received EDI 856 files via email or SFTP and manually parsed them into MYOB purchase receipts. With MYOB and Orderful connected, orders flow automatically from MYOB to each supplier as properly formatted EDI 850 documents within seconds. Shipment notices flow back from Orderful into MYOB as purchase receipts, so inventory is updated instantly. The purchasing team now spends time on strategy instead of data entry.

What you can do

• •Translate MYOB purchase orders into EDI 850 documents and route them to the correct supplier via Orderful.
• •Post supplier invoices from MYOB as EDI 810 documents for delivery to trading partners.
• •Receive incoming EDI 856 shipment notices and 855 purchase order acknowledgments from Orderful and record them as purchase receipts in MYOB.
• •Authenticate MYOB with OAuth2 and company file credentials, and Orderful with a static API Key, handling token refresh and encryption automatically.
• •Poll MYOB on a configurable schedule with full audit logging and replay capability on every translated document.

Questions

Which direction do purchase orders and invoices flow between MYOB and Orderful?

Outbound documents (purchase orders and invoices) flow from MYOB to Orderful for translation and delivery to suppliers. Inbound documents (shipment notices and purchase order acknowledgments) arrive at Orderful from trading partners and flow back into MYOB as purchase receipts. Reference data such as supplier contacts and their ISA identifiers flow in both directions to keep routing tables aligned.

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

ml-connector stores the OAuth2 Bearer token, API Key, and company file credentials (username and password) encrypted in its database. It refreshes the Bearer token automatically when it approaches its 20-minute expiry, checks the company file credentials on each batch of requests, and includes all three headers on every call to the MYOB API.

Does the integration work with MYOB desktop installations or only cloud?

Only MYOB cloud instances are supported via the MYOB Business API at https://api.myob.com/accountright/. Desktop installations running on localhost cannot be reached by remote connectors. Customers must use MYOB cloud hosting to enable the integration with Orderful.