Lost access to Payroll for a shared Reckon One File.

PaulSingh

Hi,

I cannot access the Payroll function anymore for a Reckon One file shared by my client. It gives an error message saying "you don't have access to this book, Please check the account you signed in with"

Rav

Hi @PaulSingh

Do you have access to both the Reckon One book AND the associated STP entity in GovConnect for the ABN? ie. have both been shared to you OR just the Reckon One book?

You'll need access to both with admin or payroll admin level permissions in order to access Reckon Payroll.

OR

Have you been able to access Reckon Payroll for this particular Reckon One book successfully up until now?

PaulSingh

I lodged their 2023 year end STP finalisation in July, so I assume I had permission for GovConnect. That's the last time I accessed their payroll. I can still access the payroll reports but not the actual payroll.

Rav

Hmmm if you've been able to submit STP submissions before then it sounds like you do have the correct access level.

Can I just confirm, is this the error message you're receiving?

If its a different error altogether, can I grab a screenshot of the message when you try to access Reckon Payroll.

Cheers

PaulSingh

Reckon Payroll error message.pdf

Attached is the error message I am getting. The Reckon One is only used for Payroll by the client.

PaulSingh

When I clicked on Settings & users in the client's Reckon One. It only showed one user (The owner) ?

Rav

Hmm right ok.

I'd recommend the owner/admin follows the steps outlined in this help guide as a first step just so you have the correct/relevant permissions.

https://help.reckon.com/article/yk9f3fgrlc-error-you-don-t-have-permission-to-access-reckon-payroll-message

Secondly, ensuring that you have access to the STP entity in your account when you go into GovConnect. If you don't have the STP entity when you go into GovConnect in your account then the owner/admin will need to share it with you.

Give that a go and you should have everything correct. If you still encounter the error after the above is checked off then we'll need to get this over to our dev team for a closer look.