Good morning,
Is anyone aware of the following? Both Desktop and Browser, since yesterday evening. I have not seen nor can find any correspondence.
and no scheduled maintenance - just the ongoing bank feed issue.
Further concern was caused by the recent “scheduled maintenance” notification issued on 6 June 2026. When checked on 5 June, there was no published maintenance advisory for June.
There is an important operational difference between genuinely scheduled maintenance and what appears to be reactive or late-notified maintenance. Scheduled maintenance implies advance planning, reasonable notice, and the ability for professional practices to appropriately manage operational risk, staff workflows, deadlines, and client expectations.
Where notifications are issued with minimal or no meaningful lead time, confidence in the reliability and stability of the platform is significantly undermined. For accounting and bookkeeping firms operating under strict compliance obligations, this distinction is critical.
The increasing frequency of service interruptions, combined with reduced local control over backups and functionality, is steadily eroding confidence in MYOB as a dependable professional-grade platform.
You were very lucky - we couldn't do 3 x payroll, staff couldn't enter their time billing to be paid this morning and BAS returns couldn't progress. I get maintenance is required but if we'd received an email or notification Wednesday - we could have at least made other plans for payroll. Interestingly we always seem to be in "the small minority affected" as MYOB would say.
OMG I nearly cried when I saw this post - I have 5 BAS's booked in this weekend. Luckly I dont seem to be experiencing any issues so far .....
Hi @NikkiParsons , I don't believe there is any more I can say on this matter sorry.The only point I will make right now is that saying we had a 'system outage for 11 hours' is misleading.We had 10.5 hours of system maintenance, which was reflected on our status page, and was completed outside of business hours. Unfortunately this system maintenance went for an additional period of around 30 minutes, instead finishing at ~7am AU.
This is a compliance risk issue, not a minor inconvenience.
We experienced a complete system outage for approximately 11 hours, with no clear advance notification.
To be precise:
This resulted in a full lockout of client data during a critical processing window. The message said temporary.
For practices managing payroll, superannuation and BAS obligations, this creates real compliance exposure, including:
The current position that:
is not appropriate for software relied upon in a regulated environment.
In-product messaging is not a valid control when users cannot access the system.Status Hub is not a valid control if it does not reflect actual system availability in real time.
Even the ATO provides clear, proactive notification of planned maintenance, recognising the compliance obligations placed on agents and businesses.
Expecting users to discover outages only after systems fail — and then rely on inaccurate status reporting — is not an acceptable standard.
An 11-hour inability to access client data, combined with incorrect system status and no advance notice, represents a failure of both system reliability and compliance-supporting communication.
If MYOB is to be relied upon for payroll and statutory obligations, these controls are not optional.
What specific changes will be implemented to ensure:
Hi @NikkiParsons , This was largely answered in my previous response.But I will note some again for clarity
From your message: The key concerns remain:
There will be no direct process changes as a result of this.I will work with the team performing this maintenance to feedback that maintenance occurring outside of the communicated window has occurred twice now and that we need to work to ensure this does not continue.We make these changes in a way that aims to provide the least disruption to our customers, although everyone is different, it would be fair to say that most people work during business hours which is why we target maintenance overnight (8pm to 6:30am) - this also caters to our NZ customers (10pm - 8:30am for them)
@Mike_MYOB
Thank you for your response. I appreciate the acknowledgement, however the explanation does not address the severity of the impact experienced.
To be clear, this was not a minor overrun or partial disruption.
We were unable to access a single file for approximately 11 hours. This represents a complete service outage, not a limited or “not all customers” scenario.
The key concerns remain:
The statement that direct email communication was “not possible” is particularly concerning. Given MYOB regularly distributes other communications, this suggests a process or prioritisation gap, rather than a technical limitation.
More importantly, the current approach assumes that:
Neither is appropriate for a system relied upon for payroll and compliance functions.
This is now a repeated pattern:
Passing feedback to the team is noted, however this does not provide any assurance of change.
Accordingly, I request confirmation of the following:
An 11-hour inability to access client data is not operationally sustainable for a bookkeeping practice managing payroll and compliance obligations.
I would appreciate a response that clearly outlines what will change in practice, rather than general commentary on process as well as how to lodge a formal complaint. Thank you
Hi @NikkiParsons , I can see this maintenance went past the scheduled time of 6:30 based on your screenshots which is certainly disappointing and would affect the visibility in status hub for this maintenance as well.The maintenance we are completing will not always affect all customers and is being completed in a reasonably agile way.Because of this, we communicated a more blanket statement about upcoming maintenance and disruptions in November and again on the 1st Feb.Based on your previous feedback, I am pleased to see that status hub is being updated and I acknowledge that a direct email inn advance would be the best outcome, 9 times out of 10, this is something we would do, but for this scenario it hasnt been possible.I will pass to the team that there are now at least 2 noted occurrences of our maintenance running past the scheduled time as well and hope that this can be tightened.
So disappointed................
Good morning @Mike_MYOB
We experienced a full service outage last night while performing scheduled work, with no prior awareness that MYOB would be unavailable.
After significant time spent investigating, we eventually located a maintenance notice indicating a “temporary lockdown.” Not totally inaccessible and unusable.
However:
As a result, two staff members were allocated to work and remained on standby, repeatedly checking system access late into the evening and early morning (including after 2am), without any clarity on when services would resume.
This is not a minor inconvenience — it directly impacts payroll processing and compliance obligations, particularly with PayDay Super requirements now in place.
And after the 2026.2 upgrade yesterday morning which removed settings permissions across ever file, and poor stability, it added insult to injury.
For comparison, the ATO publishes clear, forward maintenance schedules. This allows practitioners to plan and avoid exactly this scenario.
At a minimum, we would expect:
Directing users to a community page that is inaccessible during an outage is not an acceptable fallback.
Please advise:
We rely on MYOB to meet time-sensitive payroll and compliance obligations. The current communication approach does not support that.
I look forward to your response.
Hi @Mike_MYOB
This response does not address the core issue.
The problem is not simply whether the outage appeared on the status page after the event. The issue is that customers were not proactively notified in advance of a significant system outage so we could plan accordingly.
For businesses relying on MYOB for payroll processing, STP reporting, BAS preparation and time-critical compliance obligations, unannounced outages create real operational and reputational risk. Advance notice via clear email communication — with outage times specified in the subject line — is not an unreasonable expectation. It is standard practice for critical business software providers.
Receiving frequent promotional communications while not being notified of material service disruptions undermines confidence in MYOB’s communication protocols.
This requires more than “looking into” the status page process. It requires a review of escalation, notification and customer communication procedures for any outage that materially impacts service availability.
I would appreciate confirmation of what concrete changes will be implemented to ensure this does not occur again.
Hi @BooksForBiz , the incident page tends to be used when there are concerns affecting the access to a product or the ability to utilise a feature (eg Payroll)If there was a defect, bug or enhancement impacting a workflow like payroll, but does not stop it from functioning overall, this would not be listed on the status page.
There are still significant payroll issues in AU that are not mentioned on the status page - Really unacceptable.
I have access online but not desktop now. I can process payroll but cannot report STP - I need a work around as the online platform will not let me move on to preparing the bank file. Error message:
Something went wrong. Please try again or refresh the browser. Please try again. If the error persists, get in touch with us. Request ID: 69805562-30b8-4ef8-b8fd-6499cfadb9ed.
Hi there @NikkiParsons and @BooksForBiz Have you both been able to access again?I'm told that the maintenance finished at 9:05am NZT this morning I definitely note that this wasn't listed on our status page and I will look into why
MYOB - Can we please have an update on when you expect software to be functional. Payrolls need to be processed!
Self-help & Learning
Level up your skills and find answers across all MYOB products
Help Guides
MYOB Academy
