This has been fixed in the latest version (21.6.44)
However, please read new instructions before importing CSV to SingleTouch website.
Before your first upload, on SingleTouch website, you need to go to View Entities, then click Entity Details on entity you are uploading for and make sure Employee values reported field is set to Period. Not Year-to-date.
@lubos Interesting choice.
Doesn’t that make it harder to correct errors?
Year to date mean just the current data in Manager needs to be accurate to ensure the totals reported to the ATO and employee are correct.
Period means every period uploaded needs to be correct for the year to date reported to the employee and ATO to be correct. An accurate year to date is essential for electronic group certificate submission.
I was referring to that. ATO made STP more complicated than necessary. They are asking for figures they can calculate themselves. And it is a mistake on their part.
They’ve done the same mistake with BAS in the beginning. Over the years they’ve simplified BAS reporting so they do not ask for figures they can calculate themselves. I expect the same will happen to STP eventually.
Until then, SingleTouch.com.au could implement some improvements I have in mind.
This error correction procedure applies and is trivial if YTD is used.
If Manager uses period amounts to communicate to Single touch, which Single Touch then convert those to YTD to transmit to the ATO, then it becomed much more complicated. The user must understand how Single touch calculate values to send to ATO, ensure all period values are correct not just the last YTD, calculate the difference of all prior submissions to adjust the next period value by should any errors occur, and will corrupt reported data if any employee’s data is inadvertently included in 2 pay runs.
Getting this data wrong results in false data reported to the ATO, the ATO publishing false data to the employee, and the employer being liable for a fine.
In contrast I’m not convinced errors in the period W1 and W2 are as significant. Because the ATO can already calculate that and the data is repeated in the BAS submissions. There is also no way of correcting errors in the period W1 and W2 submissions for prior pay periods that I’m aware of.
In summary, it would be really appreciated if a way was found to continue to submit employee YTD quantities to single touch.
Year to date is also used for payslips. If a business parameter specified when the financial year starts, then perhaps it could be used for both.
I just realized the issue was in the localization which contained this hidden character for some reason.
In the latest version (21.6.50), re-import Single Touch Payroll Worksheet. This should fix custom fields and should allow you to select under each employee Payment Basis which won’t have this hidden character.