Invoice Numbering Issues
Hi, Seems the latest version of AccountRight (AR) has made changes to the way AR allocates invoice numbers. We have another platform which sends invoices into AR and uses a 2 character Alpha ...
Forum Discussion
Hi Tracey_H
MYOB this needs to be rolled back quickly - you fixed something that didn't need fixing or wasn't working as per the original design 20 years ago.
So you fixed it - and severely broke it and created a nightmare.
Original system always added leading zeros onto any number used
So start your invoice at
12 and the system added leading zeros and made it 00000012
And if you used alphanumeric like
A12 - the system didn't inherit or incriment and IT DIDN't RESET The auto invoicing.
Now if you put '12' in MYOB leaves it as 12 and the next number will be auto generated to give 13, 14.
However - here is the worst part of the fix - if you are running 3rd party apps if and invoice comes in as
A12 then this resets the auto counter on the internal numbering to A12 and the next invoice internally becomes A13.
And the API app (designed on the old system) expects the next available number is A13 - and posts it as A13 and because the preference (warn if duplicate invoice numbers) is on - it will reject this invoice!!!!!!!
What a mess MYOB
The ONLY fix that seems to stop this idoitic fix is I add an alphanumeric onto the end of the number.
So if I am sending an invoice from the web called Web0100 - I send it as Web0100A - and this stops MYOB dead in resetting the autonumber ....... but hey MYOB this really is a mess!
The Doc
Just seeking an update on this critical issue... The problem was raised in November 2021 and it's now mid-March 2022 - without any fixes.
This issue is continuing to cause an issue for us every day since we added a CR prefix to our invoice number for a credit note, all auto sequence numbers now have a CR in front and can't be removed. Every invoice now being manually adjusted and it's leading to issues within our systems.
MYOB really need to revert autosequence to the original method now. I'm not sure you understand the impact on your users....
Please update with when this issue will be resolved. Hopefully no later than the end of this month?!
The numbering system was not "updated" - it was broken. It worked perfectly fine before your eager developers tampered with it.
It is time you actually gave us a time frame when this will be fixed!
perkyone wrote:The numbering system was not "updated" - it was broken. It worked perfectly fine before your eager developers tampered with it.
It is time you actually gave us a time frame when this will be fixed!
You can read into this, they are not planning to "fix" it.
MYOB are not considered this as broken
