IMPORTANT NOTICE - Your Empdupe file may be incorrect if you employ Working Holiday Makers

IMPORTANT NOTICE - Your Empdupe file may be incorrect if you employ Working Holiday Makers

Hi everyone,

We have found an issue with the Empdupe file in Reckon Accounts (Desktop) and Hosted 2017 R2, which affects businesses that hire Australian residents and Working Holiday Makers.

If your exported Empdupe file contains a mix of Australian employees and Working Holiday Makers, your Australian employees will be incorrectly flagged as Working Holiday Makers.

Reckon Accounts 2017 R2 (DESKTOP) - To fix this issue, you will need to download an update and create an amended Empdupe file. Please click HERE for more information on the fix and how to apply it. If you have already lodged your Empdupe file with the ATO and it contained Australian employees and Working Holiday Makers, you will need to amend your submission by 14 August 2017. If you haven't lodged your Empdupe file and you employ Working Holiday Makers, you will need to apply the fix before lodgement.

Reckon Accounts HOSTED 2017 R2 - We have now fixed this issue and it will not affect any new Empdupe files created. If you have already lodged your Empdupe file with the ATO and it contained Australian employees and Working Holiday Makers, you will need to amend your submission by 14 August 2017. If you haven't lodged your Empdupe file and you employ Working Holiday Makers, simply create an Empdupe file and it will be correct. For more information on how to amend your Empdupe file, click HERENote: Empdupe files that have been lodged via SBR (GovConnect) are NOT affected by the issue.

Our sincere apologies for the inconvenience this may cause. If you have any questions, please feel free to post a reply below, give us a buzz at 1800 732 566 or send us an email to customerservice@reckon.com

If you don't have any WHM's then your Empdupe will be just fine and there's no need to apply the update. On the flipside, there's no harm in applying it though if you'd like for future. Sorry just realised I had linked to the wrong article, I've now updated the link in my post above to reflect the correct KB article which contains the download to the fix and its here below too -