AccountRight November 2011 Upgrade

[#1]

I discussed a similar issue to this with customer support a short time ago,  and we hadn't been able to reproduce it... but I am now able to reproduce it....

When I have an item come up in my Reminders List for a sale transaction, if I double-click the item, or click the purple arrow in the first column for it, it brings up the new transaction, using a new sale transaction ID, and when I click Record on the "Sales - New TimeBilling" window (this is a time billing invoice), the Reminder still exists, and the recurring item is not marked as having been recorded.  It also defaults the date of the transaction to today's date.  This is as I would expect based on past MYOB versions and based on my own general expectations.

When I select the item in the Reminders List and explicitly click "Record", it records it - but it does so in the background, I dont get a chance to change it (I have to go into Sales Register and find it), and also it is saved with a default date of the date of the recurring item's scheduled date, rather than today -- and since that is in the future (I ask to be reminded 7 days before), I dont even see it in the register until I change the filter dates.  Very unfriendly and even confusing when you dont realise about the date issue, because it appears as though it hasn't worked.

I would expect the date behaviour to be consistent (and the same as in the past, where it's set to the current day's date), and would expect clicking the purple arrow for the item, double clicking the item and click Record to all behave the same -- and again, the same as in the past.

[#2]

Hi WebAngel

Thank you again for your feedback on the different methods of recording recurring transaction and how they give different results.

I will test this further and will also pass on this feedback to our Product Development team. If there are any users who are experiencing the same behaviours, please feel free to let me know.

Thank you again for your time and patience. 

[#3]

Hi Leeya,

I've continued to have many issues with this, including having some strange dates being used when recording transactions in this day, but I've just had a rather substantial bug occur which needs raising...

I just hit the record button for an item which was due on 24/2/2012, and when it recorded it, I found that the date of the transaction was set to 24/2/2014 -  that's right, 2014!! It took me long enough to find it at all (since obviously it wasn't even coming up in my Sales Register when I set the date range to include up until March 2012.  The transaction is a Quarterly recurring invoice, there is nothing that I can think of at all that would cause it to record in 2014, and I had to go in and change the "next due" date to be 24/5/2012 rather than 24/5/2014.

Can you please raise this bug as an example of the MANY issues I'm experiencing with incorrect dates in recurring transactions?

I often find that after recording a transaction, it actually updates the recurring transaction record to skip the next interval, as if this recurrance AND the next recurrance had both been recorded - have I explained that clearly?!

The inaccuracy of the Recurring Transactions recording mechanism is frightening, I'm currently glad that I dont have more than two or three due at any given time, or I'd be lost with incorrect dates and erroneous recordings.

[#4]

Hi WebAngel

I will pass on your experiences with recurring transactions to the product team. They are currently investigating this function and its behaviour.

I suggest a precautionary step of clicking onto the transaction from the Reminders List window to view the details of the entry before recording. I understand this step should not be required however in light of the behaviour, it will ensure data entry with the correct date. 

On a last note, again just a precaution, please check that your computer date (or the computer date where the file is located) is not set to year 2014. This is because when recording the recurring transaction from the Reminders List, it will be recorded as per the computer date which may not necessarily be the Due Date.

[#5]

For the record, my computer date is NOT set to 2014 - I'll try to only be a *little* bit offended that you think this might be the problem.... especially given that I've said it was just for this particular transaction that it set it to 2014, it's not something that's happening every time (only sometimes)...

[#6]

Hi WebAngel

I apologise if I have offended you as that was not my intention. My last note/precaution was to ensure it was not something that can be easily overlooked that may be causing the incorrect date to be recorded.

As this behaviour is only affecting one particular recurring transaction, I suggest either deleting this one recurring transaction template and creating a new one or clicking onto the arrow to the left of the transaction in the Reminder List to view the details before recording.

Our product team are still working on fixing issues related to the recurring transaction function.

[#7]

This isn't only affecting this one transaction -- as I said, this was just a particularly drastic (and random) date stuff up.  I'm constantly having issues with periods being skipped and incorrect dates being randomly set, as per my original post.

[#8]

i have 300 recurring sales all due end of month they have just rolled over and are on automatic and i have anything from 3 to 5 transactions repeating themselves

any one have a fix on this

jo

[#9]

I feel for you, whybuy, and I don't even have anywhere near 300 transactions to handle each month. I really hope this is prioritised a bit more than I feel it is being done, as I couldn't imagine I was the only one suffering with this (and now you've confirmed that I'm not!).  The notes so far on the upcoming SP3 don't seem to mention Recurring Transactions at all that I can see, so it's extremely frustrating to see that we're likely to have at least another month before we get any action on this.  For many of us, recurring transactions are our main source of income, and if your system doesn't continue to function as it did before this new version, you're going to quickly loose customers to other software/services that DO work.

FYI Leeya, regarding one of your earlier "workarounds", in which you suggested:

I suggest a precautionary step of clicking onto the transaction from the Reminders List window to view the details of the entry before recording. I understand this step should not be required however in light of the behaviour, it will ensure data entry with the correct date. 

This would not work anyway, as if you review my original post, if I double-click the item, or click the purple arrow in the first column for it, it brings up the new transaction, using a new sale transaction ID, and when I click Record on the "Sales - New TimeBilling" window (this is a time billing invoice), the Reminder still exists, and the recurring item is not marked as having been recorded.

[#10]

Hi Webangel,

Can you tell me if the error also occurs in the clearwater sample file.  I have spent some time testing this issue today and currently have not been able to replicate the above scenarios.  This makes be believe that the error is specific to your datafile.