If something connected to MYOB stopped syncing around September 2026, the most likely cause is MYOB's change to how outside software gets permission to read and write your data. MYOB's API support centre says that as of 1 September 2026 the legacy "CompanyFile" permission is deprecated for all API keys, and integrations had to be updated by that date. For most off-the-shelf apps the fix is simple: an Administrator user of your MYOB company file reconnects the app. For a custom or in-house integration, a developer has to update how it connects, and then an Administrator approves it again. This guide explains how to tell which situation you're in and what to do.
What changed
Software that connects to MYOB Business (including AccountRight files in the cloud) asks MYOB for permission when you first connect it. For years, many integrations asked for one broad permission covering the whole company file. MYOB replaced that with narrower permissions for each type of data, such as contacts, sales or payroll, and set 1 September 2026 as the date the old broad permission was retired for every API key (MYOB API Support Centre).
MYOB's guidance also says the person approving a connection must be an Administrator user of the MYOB company file. A standard user can't do it.
Step 1: Work out what kind of integration it is
- A marketplace app (listed on the MYOB marketplace, from a software company): the vendor should already have updated it. You usually just need to reconnect it.
- Software your other system came with (a job system, POS or e-commerce platform that "connects to MYOB"): check that vendor's help centre. Most have published reconnect instructions.
- A custom or in-house integration (built for you by a developer or IT provider, or by someone who has since left): this is the one most likely to have broken, because nobody was watching for the change.
Step 2: The quick fix for apps
- Log in to MYOB as an Administrator user of the company file.
- In the app's settings, disconnect MYOB and connect it again, approving the permissions it asks for.
- Repeat for each company file the app uses.
- Check that recent transactions came through, and re-send anything that failed while it was disconnected.
If the app still fails after reconnecting, contact the vendor. The problem is on their side.
Step 3: What a custom integration needs
A custom integration can't simply be reconnected. The code has to change first. In plain terms, the developer needs to:
- Ask for the new, specific permissions instead of the old broad one, in the sign-in step the integration uses.
- Have an Administrator approve the connection again, once for each company file.
- Pick up the company file reference from MYOB's reply when it's approved, rather than looking up a list of files, which the new setup no longer provides.
- Store the new access tokens. The old ones can't be brought back, so an integration that runs in the background needs a one-off approval step to get started again.
Then test it properly: check that new transactions flow, and work out what was missed between 1 September and the fix so it can be caught up without creating duplicates.
Signs it's a bigger job
- Nobody knows who built the integration or where its code lives.
- It connects several company files or several systems, not just one.
- Data has been missing for weeks, so there is a backlog to catch up without creating duplicates.
- It was already unreliable before September: partial syncs, manual fixes, errors nobody looks at.
In that situation, fixing the connection is the first step. It's also a good time to make sure the integration logs its errors, alerts someone when it fails, and is documented so this doesn't happen again. Xero made a similar change in 2026 by introducing paid plans for apps that connect to it, so if you run custom integrations with both, it's worth checking both at once.
That's the kind of work we do. See Xero and MYOB integration repair and MYOB API integration.
Frequently asked questions
Why did my MYOB integration stop working in September 2026?
Most likely because of MYOB's permissions change. As of 1 September 2026, MYOB retired the old broad "CompanyFile" permission for all API keys. Integrations that weren't updated to the newer, more specific permissions were disrupted.
Who can reconnect an app to MYOB?
According to MYOB's guidance, an Administrator user of the MYOB company file. If you log in as a standard user, the approval won't work.
I reconnected the app but it still doesn't sync. What now?
Contact the app vendor first. If it's a custom integration, the code needs updating before reconnecting will work. Reconnecting alone won't fix it.
Will I lose the data that didn't sync?
The data in your other system is still there. It just didn't reach MYOB. Once the integration works again, the missing period needs to be caught up carefully so nothing is entered twice. Some apps can re-send it; custom integrations may need a one-off catch-up run.
If your MYOB integration is custom-built and has stopped, or nobody is sure how it works, book a free initial chat. If it's an app that just needs reconnecting, we'll tell you that too.