MYOB and Jira integration

What moves between them

MYOB data flows one way into Jira as workflow triggers. When ml-connector detects a new supplier invoice, a customer payment, or a purchase order in MYOB, it creates or updates a Jira issue in a designated project, labeling it with the invoice number, supplier name, amount, and due date where applicable. Because Jira has no financial state to write back, the integration is read-only on the MYOB side and create/update only on the Jira side. ml-connector polls MYOB on a schedule tied to your accounting cycle (daily or weekly) rather than on push, since MYOB does not offer webhooks.

How ml-connector handles it

ml-connector stores MYOB OAuth2 tokens and company file credentials encrypted, and refreshes the bearer token when calls return 401. MYOB's two-factor requirement (OAuth token plus company file username and password in the x-myobapi-cftoken header) is handled automatically on every request. Polling uses OData $filter on LastModified to fetch only records that have changed since the last sync run, reducing the volume and staying within MYOB's rate limits of 8 requests per second and 1 million per day per API key. When a new invoice, purchase order, or payment is detected in MYOB, ml-connector maps the supplier and amount to Jira custom fields (custom field IDs vary per Jira instance, so mapping is per-tenant), creates a new issue, and tags it for approval workflows. Because Jira has no GL account or invoice entity, the integration uses Jira's issue type and worklog system to capture the financial event and route it to the right team. Every poll and every Jira issue creation carries a full audit trail and can be replayed if downstream processing fails. MYOB's RowVersion field is tracked to prevent stale updates; Jira custom fields are pre-mapped at setup so the integration knows where to land MYOB amounts and supplier names.

A real-world example

A mid-sized professional services firm uses MYOB to manage invoices and expenses, and Jira to track client projects and delivery work. Before the integration, when an unexpected invoice arrived from a supplier or a customer payment cleared, finance had to manually email the project team, leading to duplicate orders or delayed payment reconciliation. With MYOB and Jira connected, each new supplier invoice becomes a Jira issue tagged for purchase review, and each customer payment triggers a Jira task to update project budgets. The team sees finance events in their project board without context switching, and finance gets immediate visibility into which invoices have been acknowledged.

What you can do

• •Create Jira issues automatically when MYOB detects new supplier invoices, customer payments, or purchase orders.
• •Map MYOB supplier names, invoice amounts, and due dates to Jira custom fields so project teams see financial context without diving into accounting software.
• •Poll MYOB on a schedule tied to your accounting cycle, using OData $filter on LastModified to catch only changed records.
• •Handle MYOB's OAuth2 and company file credential requirements, refreshing tokens automatically when they expire.
• •Maintain full audit trail on every MYOB record fetched and every Jira issue created, with replay capability if a downstream step fails.

Questions

Why would we connect an accounting system to a project tracker if Jira has no invoice entities?

Jira issues can represent almost any event, including financial ones. The integration creates issues to notify teams of supplier invoices, purchase orders, and customer payments without requiring custom accounting logic in Jira. Your approval workflows, project leads, and resource managers stay in Jira where they already plan their work.

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

MYOB requires both an OAuth2 bearer token and company file credentials (Base64-encoded username and password) in the x-myobapi-cftoken header on every call. ml-connector stores both encrypted and refreshes the bearer token automatically when a call returns 401. The tokens expire on MYOB's schedule (20-minute bearer, 1-week refresh), so the integration stays in sync without manual re-authentication.

What if an issue in Jira needs to update a record back in MYOB, such as changing an invoice status?

The integration is one-way from MYOB into Jira only. Jira has no financial entity types, so write-back to MYOB would require custom mapping that lies outside Jira's domain. If your workflow requires bidirectional sync, a separate MYOB-to-MYOB process or finance system integration is the right fit.