When I went to make monthly Declaration for October on the ATO website,,the new payments of $1200 per fortnight do not appear. Report says zero employees at TIER.
I have just spent an hour and a half on phone to ATO - My employees were all listed twice, half with a dodgy DOB 1/1/0001 with the JK tiers listed but nothing in the Jobkeeper column and the correct list with DOB had nothing beside it.
My input came from Reckon Hosted. I had no trouble with the one that came from Reckon One
I has the double up problem too with the wierd DOB as well. What I found I had done was enter the employee surname as the first, and the first as the surname. Hoping this has fixed that problem, but won't know until I can get JK_TIER1 matter sorted and the Jobkeeper hours showing up as they did in Job Keeper 1.
I did not have that issue and so have no idea why it happened, I do know it has been like that since the beginning of Jobkeeper but it didn’t cause any issues the first time around. Good luck with yours. I did find the ATO very helpful and worked with me to delete the duplicates and merge the missing information
I tried to get on to ATO on Friday, but after a 20 minute wait the guy who answered to phone told me their system was down.
I will try again on Monday, but I temd to think this is a Reckon issue, as well as the ghosts.
I rang at 10 on Saturday as soon as they were open. I agree that it’s possibly a Reckon problem but the ATO were happy to fix it for me,I wasn’t prepared to go looking for things to change when as far as I could see there was nothing wrong
Gee, I didn't know they were open on Saturday! No that that help's me - I help my 70 old sister look after her two twin 2 year old and nine year old granddaughters. She has sole parental custody, so try to give her a bit of a break over the weekends.
That’s a handful, my twin granddaughters are now 19. Must be hard at that age to look after the little ones. I’m that age and happy that my youngest is 17, but not my responsibility.
Just an FYI - The weird default DOB seems to be a standard glitch which the ATO have advised isn't relevant anyway. Not sure if it's a Reckon glitch or on ATO's side but it doesn't affect the process working :)
Shaz Hughes Dip(Fin) ACQ NSW, MICB
0422 886 003
Yes I know the glitch didn’t interfere with Jobkeeper 1, but this time it did as the Tier 1 & 2 allocations went against the names with the wrong DOB and was incomplete as it told me there was missing information and didn’t show the amount of any refund except for the the Business Participant. The names with the correct info had nothing tagged for Jobkeeper . The ATO were also confused
Yes, but that issue is with the double-up of employees appearing (which I've had happen also 😫) so am just reassuring everyone that the displaying of the incorrect DOB itself doesn't matter.
Yes I do appreciate what you are saying, But something caused a glitch when I submitted the Tier 1 submission and I don’t know what
@Kris_Williams Yeah, I've had one client who has had this happen - the double-up of employee name & Tier allocation on the wrong record - seems to be random ? (Although he did do the JK thing himself so not sure if he veered from my instructions on that or not lol)
Just in regard to the issues with DOB's, specifically those showing as 01/01/0001.
We've confirmed that the Standard Business Reporting (SBR) service will not allow us (Reckon) to send a date of birth parameter such as 01/01/0001. The minimum accepted value in the transmission payload is 1800 so if the 01/01/0001 date of birth was being sent by us it would result in an error immediately.
So its an ATO glitch Rav?
Don't want to sound like I'm passing the buck but yes in regard to DOB's appearing as 01/01/0001 it appears to be an ATO side issue.
Maybe that’s why the ATO were happy to take 90 minutes to fix my problem!
Can you address my issue in the first post.
Janine it’s probably quicker to ring the ato if you can find the time. I had lodged 2 STP submissions and neither fixed the problem
Hi @Janine White
One of your posts earlier in this thread mentioned 'JK_TIER1'. I'm guessing this may have just been an oversight on this Community post etc however just in case it wasnt, its super important that the tier items are spelled correctly and in the upper case format. So for the Tier 1 item, it needs to be typed out as JK-TIER1 ie. separated with a hyphen and not an underscore.
Also, has your tier item been setup with the tax tracking type of 'Allowances - Other'?
I have entered all the relevant items and JK-TYier1 correctly (in my post it's a typo). I also have the tax tracking correct. This is for all three companies I process STP and Job Keeper for.
I entered the JK-TIER1 as allowance-other item to every payslip for Jobkeeper 2.0. It did not show up whe i went to ATO business portal to complete the October declaration i had no tiers for Employees, despite having done them in Rickon Accounts. I went back and checked individual paylsips for each week for FN14 and FN15, Jk-TIER1 was definitely there. Just in case, i tried doing a full file replacement......no go. The JK-TIER1 did not show up in details through the Reckon Gov connect STP site. In fact, the only allowance that showed up was the original jobkeeper 1.0 start flag.
I had to ring the ATO and declare the TIERS for each employee verbally in order to complete the declaration.
Reckon needs to fix this issue. the whole reason i upgraded to your product was for STP, and it does not appear to function adequately.
@ianware This is very unusual as it's not a known issue - I would recommend removing the old " ....STARTXX" tag first as this may be causing a conflict ? Also, make sure you are creating/exporting & uploading a NEW STP submission (not the original/previous) after making any changes.
I have had to ring ATO for some Reckon files and, but also had to ring for another software, so problem not unique to Reckon
Kris, as I was running out of time to submit, I rang ATO this morning for 2 clients using Reckon Accounts Desktop, and you were right, they were able to fix the issue. I didn't have shadow files, like you had, but the info wasn't transferring over to the declaration. The ATO fixed whatever the issue was, which showed one client with the crazy DOB and the other client had correct DOB.
Interestingly enough, my third client uses REckon Hosted and that was plain sailing.
Shaz, all my three clients show the STARTXXX tag, so I don't see how that is the issue.
@Janine White It may actually be the ATO's end then as the crazy DOB has definitely been confirmed as an ATO glitch, not on Reckon's side.
As these issues are occurring randomly, my suggestion to remove the START tag is a process of elimination - I've not encountered any of these issues personally (although a couple of my clients have) but I've always NOT added the tag to the employee's default record, so it doesn't appear again after the initial pay run required.
Having 2 tags may be something that's conflicting with it in this one particular file at the ATO end ...?
I will remove the Start tag from one of my Desktop clients and see if it is plain sailing from thereon. One will hav the tag and the other one won't. Let's see what happens in December.
Will keep everyone advised.