MYOB and SPS Commerce integration

What moves between them

The primary flow moves MYOB purchase orders and invoices outbound to SPS Commerce, where they are wrapped in the RSX JSON envelope and routed to the designated retail trading partner. The reverse flow polls SPS Commerce for inbound purchase orders from retail partners and creates them in MYOB as supplier orders. General ledger accounts and supplier contacts are aligned in both directions so PO line items map to valid GL codes and cost centers. Invoices created in MYOB post to SPS Commerce on a cadence tied to your supplier management process.

How ml-connector handles it

ml-connector stores both MYOB company file credentials and SPS Commerce client ID/secret encrypted in the cell's Postgres database. On every MYOB call, it constructs the three required headers (Authorization bearer token refreshed every 20 minutes, x-myobapi-key, and x-myobapi-cftoken with the Base64-encoded company file credentials), and respects MYOB's 8 requests/second and 1,000,000 requests/day rate limits. For SPS Commerce, it obtains a fresh JWT on the first call and reuses it until it expires, then wraps outbound documents in the RSX 7.7.7 JSON envelope format with the retailer's trading partner ID and document type (850 for purchase orders, 810 for invoices). It polls MYOB purchase orders on a configurable schedule using OData $filter on LastModified, and polls SPS Commerce inbound orders at a 5-15 minute interval per SPS best practices. All documents are stored with their row version and SPS cursor tokens to detect duplicate posts and replayed polls.

A real-world example

A small Australian manufacturer sells components to major retail chains through an EDI network. The purchasing team manages supplier orders and invoicing in MYOB, but the retail partners require purchase orders and invoices in EDI format (X12 850 and 810) submitted through SPS Commerce. Before the integration, the operations manager manually exported MYOB purchase orders, hand-keyed them into a CSV, uploaded to SPS Commerce, and then copied in retailer purchase orders from email back into MYOB. With MYOB and SPS Commerce connected, purchase orders post to retailers' systems within minutes of creation, inbound purchase orders from retail partners land in MYOB automatically, and the manual EDI shuffle is eliminated. The finance team now reconciles invoices to POs with zero re-keying.

What you can do

• •Push MYOB purchase orders to retail trading partners via SPS Commerce with automatic RSX JSON envelope wrapping and trading partner routing.
• •Receive retail partner purchase orders from SPS Commerce and create them in MYOB as supplier orders mapped to the correct GL accounts.
• •Sync supplier contact and GL account master data between MYOB and SPS Commerce so all line items reference valid dimensions.
• •Manage MYOB's dual authentication (OAuth2 token refresh every 20 minutes plus company file credentials) and SPS Commerce's client credentials OAuth flow transparently.
• •Poll both MYOB and SPS Commerce on schedules independent of webhooks, with exponential backoff on rate limits and full audit trail on every document.

Questions

Which direction do purchase orders and invoices flow between MYOB and SPS Commerce?

Purchase orders and invoices flow outbound from MYOB to SPS Commerce for transmission to retail trading partners like Walmart and Target. Inbound purchase orders from retail partners flow from SPS Commerce back into MYOB as supplier orders. This two-way sync keeps your supplier orders and retail demand aligned without manual re-entry.

How does ml-connector handle MYOB's two-factor authentication requirement and 20-minute token expiry?

ml-connector stores both the MYOB OAuth token and the company file credentials (username:password) encrypted in the database. On every API call, it constructs all three required headers: the Authorization bearer token (refreshed every 20 minutes before expiry), the API key, and the x-myobapi-cftoken Base64 header. If a call returns 401, it refreshes the token and retries without manual intervention.

What does the RSX JSON envelope format mean, and how is it handled?

RSX 7.7.7 is SPS Commerce's standard JSON wrapper for EDI documents. Instead of raw JSON fields, all outbound documents (purchase orders as 850, invoices as 810) are wrapped in RSX structure with the trading partner ID and document type before posting to SPS. ml-connector handles this wrapping automatically, so your MYOB team never sees the envelope complexity.