MYOB teams app - no break option showing
Hi I have recently set up my client on MYOB team for their 2 locations to start using timesheets through there and have noticed a few problems - It doesn't pull through their Sat or Sunday rates ...
Forum Discussion
We are also having the same issue with multiple client files unable to added breaks in the app.
As far as we can tell, the app is asking employess to create activities rather than timesheets.
In location settings, we dont get any other option for Time Capture type other than 'Timesheets'. The settings in AccountRight (desktop) are Timesheets (payroll and time billing).
You can access the timesheets settings in AccountRight (desktop). Setup > Preferences > System. The same setting cannot be access in the browser version of MYOB.
If you choose 'I use timesheets for Payroll' you're giving the option in the Teams app to add breaks.
If you choose 'I use timesheets for Time Billing and Payroll' you're not given the option to add breaks. Employees are required by law to have breaks and these breaks MUST be recorded on timesheets. Why are those users who use job costing not able to record their employees breaks?
Hi ALL,
Thanks for reaching out and my apologies for the late response. To record a break in your MYOB Team app, you'll need the Admin or Owner of the business to adjust the time capture type via the MYOB Team Admin Portal. They can switch it to "Clock on/clock off," enabling employees to input their Start and End break times. For more details on this matter, please refer to the Help Articles: "Using the MYOB Team mobile app" and "Getting started with MYOB Team."
Please do let me know how you go on this.
Regards,
Earl
Thanks for the response Earl - problem is, many of us aren't getting that option unless we turn off job-tracking on timesheets....
There appears to have been a glitch somewhere. I had several locations with the same setup but one wasn't allowing breaks. I set up the location a second time and it worked.
Hi shannons,
We're aware of this issue, and for now, the current workaround involves setting up the location again. We've escalated this to the appropriate team for a permanent solution. While we don't have an exact timeframe for the resolution, rest assured that our development team is actively addressing it for inclusion in a future update.
Feel free to post again, we're happy to help!
Regards,
EarlThanks Earl - good to hear.
Unfortunately we have attempted to create a new location and this hasn't resolved the issue for us.
