~ CLICK HERE FOR LATEST UPDATE
(Moderator edit: 17/5/2018, 9:08am)
I've now tried again unsuccessfully to submit my BAS and it has come up with the same error.
I'm beginning to wonder why it is that we use Reckon in the first place.
We cant do BAS through Reckon, we can't do TFN declarations. Does Reckon work with anything with the ATO anymore?
I know you have stated that it is an issue with the ATO, but as it's now been over a month with nil resolution or update, it is a bit of a joke. Reckon are still happy to take my monthly payments each month!
I have had the same problem for 2 mths and have been following the above conversation assuming the problem would be solved by now. My program is on a desktop and not hosted so I suspect lot of other uses are having same problem. Those who only lodge BAS quarterly will now find the problem!
Problem Event Name: CLR20r3
Problem Signature 01: govconnectas.exe
Problem Signature 02: 0.0.0.0
Problem Signature 03: 5947537a
Problem Signature 04: PresentationFramework
Problem Signature 05: 22.214.171.124
Problem Signature 06: 55409a7c
Problem Signature 07: 626a
Problem Signature 08: e1
Problem Signature 09: System.Windows.Markup.XamlParse
OS Version: 6.2.9126.96.36.199.16.7
Locale ID: 3081
I presume this is what everyone else gets?
The latest update I have currently is that our teams & Product Manager will again be in contact with the ATO tomorrow to determine what is causing this crash and its ongoing nature.
I'd just like to thank you all for your patience I know that its been frustrating for everyone so far and the team are definitely aware that the current experience is less than ideal and not to the standard we expect.
I will be in touch again as soon as I have further information following the outcome tomorrow. I appreciate that its not a solution and I cant make any guarantees or speculate on ETA's just yet unfortunately. Sincere apologies for the frustration and inconvenience this is causing.
Our Product team has been in discussion with the ATO yesterday afternoon in relation to this issue. They are further investigating on their end and we have suggested monitoring the data flow of a lodgement on the ATO side from an impacted user(s) in order to determine the point of failure.
We are expecting further word from them and I'll advise you all of it as soon as this occurs.
Can you please provide us with another update. This is becoming beyond a joke. I still cant submit my BAS utilising Reckon.
To add salt to the wound, I am advised by email that our Reckon price will increase as of the 1st of January. I think this is quite unreasonable considering Reckon have made no attempt to fix this customer issue. In fact I cant even get a response to an email from Reckon on this matter
For those on this thread who are currently experiencing this issue, the next time you attempt a lodgement which fails can you please send the following details to me at email@example.com
- EXACT time and date of this failed lodgement
- XML file
C:\Users\Username\Documents\Reckon Limited\Reckon GovConnect\Instances
It will be named *username.prefill.request.xml*
If there's a Prefill Response XML in the directory, please include a copy of that also, it will be named *username.prefill.response.xml*
Another aspect is, while there haven't been any changes to the Reckon GovConnect module, we will have a developer investigating code. To be transparent in terms of expectations, this will occur immediately after the Christmas/New Year closure period.
I will update the thread again as soon as I have any further information. Thank you all for your patience and again I sincerely apologise for the frustration.