Stop Bank Feeds from using cheque numbers - URGENT FIX REQUIRED

[ShellN]

Since the lates upgrade (24th September 2019) in Account Right the bank feeds have now been assigning cheque numbers to transactions and transfers Instead of the EFT code that was previously being assigned.  

This is creating a big mess of the account as we now have cheque numbers being repeated.

i have seen this discussed in another post with the ACCEPTABLE SOLUTION being to go in and manually change the reference number on each transaction before approving?????

NOT ACCEPTABLE - If I have to manually change transactions then i might as well not bother with the Bank feeds and just go back to manually reconciling the accounts.  Using a cheque number should not be an option as cheque numbers are assigned as they are issued where as other transactions are reported as they occur.  If anything we should be able to choose the reference we want on the transaction ie have it as an option within each Bank Feed Rule

File attached show bank feeds now assigning cheque numbers to bank fees.  This is not helpful

This is not a request to be added to  a wish list of improvements ... the fact the Bank feeds are assigning cheque numbers is an issue that needs to fixed ASAP

[katebradfordnz]

I agree - this has been changed since the last upgrade when it was working perfectly fine before that.  We have 6 different companies with upwards of 30 transactions a day in each - manually changing these is not a solution, it's a lazy suggestion.

[Steven_M]

Hi @ShellN  ( @katebradfordnz )

Generally speaking, the original poster on a thread will mark a post as an accepted solution. As such, it is up to that user to indicate that a reply has solved their problem/deemed to their provide information to resolve their situation.

In terms of the bank feeds using the cheque number sequence, this has been something that we have identified with the AccountRight 2019.3 version and will be addressed in our next update AccountRight 2019.4. Although, no ETA has been announced for that version at this stage. A full list of issues and their statuses are located on AccountRight 2019.3: Things you should know

[JackieW]

No ETA is not acceptable.  It worked previously and this issue is causing one of my clients in particular an enormous amount of trouble and wasted time and financial costs. URGENT, URGENT & MORE Urgent

[Rusty59]

I agree, this issue needs to be sorted now.

[JackieW]

It has been two weeks since you responded about the error in Bank Feeds - is there any update as to when the fix and associated update will be available??

[EBS]

I agree, I've just had to google why all of a sudden this was happening and found this page and I think the response from MYOB is unacceptable.  The amount of work to manually change cheque numbers to EFT, Dir Dr or whatever is very cumbersome.

Why do we have to waste time trying to find why suddenly MYOB has stuffed up this process?  Can't they put a message on when we sign in?  They don't seem to have any problems putting their annoying "cross marketing" notifications on.

Please apply a fix urgently as this is a problem for most of us but for those that process many transactions, it would be a nightmare.

No wonder a lot of people are crossing over to Xero.  At least they listen to their customers.

[denise096]

@Steven_M- no ETA is not acceptable!!

I actually really don't care why it happened with the update. The fact is that it did, and your software developers by now would know how unhappy your subscribers and partners are and exactly what went wrong!!

It needs to be fixed............ AND NOW!!! I am not the only one with clients that have been massively impacted by this. It's a huge issue if you're relying on bank feeds and rules to get through transactrions quickly!!

NOT HAPPY!!!!!

[Steven_M]

Hi Everyone

Thank you for your additional feedback with regards to this situation.

As has been indicated with my earlier post on this thread, Spend Money transactions generated from a Bank Feed rule using the cheque number instead of "EFT" is something that will be addressed in our next update AccountRight 2019.4. 

AccountRight 2019.4 is currently still in development and as such we are not able to provide an exact timeframe for when that particular update will be available to all clients. However, we will be releasing In-Product updates and announcements on the AccountRight Blog once the update is available so clients can download and install that update.

[ShellN]

Needs to be fixed with a patch urgently... should not have to wait possibly months for an update.  This is causing erroneous data  and referencing to be recorded in the files which can make searching and reporting on transactions a difficult process as well as creating false audit trails.  This impact of this is significant and I don't think you quite get that.