Please get rid of the pop-message (invoicing) bottom right in Sales - New Service
"Information - Turn on online payments to add a payment schedule"
I do not want or need Online Pyemnts and truned it off and find the pop-up messgaes keeps apprearing over the top of next screen, click the 'x' and it appears again & again & again............ if I do anything else in my invoice - beyond annoying
Same here, very annoying.
Extremely annoying 🤬
THIS IS URGENT - every time I click when competing an invoice despite clicking the 'x' to remove the pop up message - it reappears - so far I have a record of 12 times in 1 invoice. Plus if I don't dlete it before sending it overlaps the bottom buttons to send. This is sending me into FRENZY - surely it can be turned off behind the scenes without needing to go before a 'review committee'?
Hi Eastside,
I’m sorry to hear that the pop-up message is distracting your workflow.
The message you’re seeing is tied to Payment Schedules, which currently only works when Online Payments is turned on for the invoice. So when Online Payments is off, that prompt can still appear.
That said, I completely understand how this affects the way you work, especially if it keeps reappearing while you’re trying to finish the invoice and even covers the Send buttons.
If you’d like, you’re always welcome to share this on our Ideas Exchange board so the team can track the feedback directly.
Regards,
Genreve
pretty sure that's wrong.
I turned on online payments as a test and the pop up kept coming back
This is stupid that is hasn't been resolved yet
I note that it has apparently been resolved for account right users but for business users you are still not even admitting that it is an issue yet.
Genreve
Surely this could be escalated without having to go to yet another 'page' - 'MYOB help & support' is odd title!
Hi Eastside​ , sorry I missed this thread.
There is a second discussion about this same problem which I posted a reply to yesterday here
Thanks, Mike
Hi Eastside​ , I have had confirmation from the team that the correction for this was released in last nights AccountRight version release. This should be resolved now
