TPAR Report Error
Hi,
I am currently lodge Fy2022 Tpar report, but there are error message when I lodge.
Test failed for , sent on 29/11/2022 File submitted for test only and is NOT lodged. Go to the...
Forum Discussion
Thank you for the details.
This error is normally caused by an invalid character somewhere in the TPAR file, including extra spaces. Please look up this line number using Notepad++ by following the steps given below:
- Open the TPAR file in notepad ++
- From the Search menu choose Find Characters in Range
- Select Non-ASCII Characters and click Find
Notepad ++ will then display where the invalid character is. - Click on the top of the notepad ++ application and the cursor will flash just after the invalid character. In the example below the invalid character is a SPACE.
- Repeat until all invalid characters are removed.
After this is done, you can fix the data in AccountRight and recreate the TPAR file. If your file is online and you are still having issue, we can run a script to identify which supplier cards contain invalid characters. Please confirm the last 4 digits of your serial number, and the company file ID number so we can assist further.
Hi Clover,
I do not have the notepad++ like yours. I attached the screenshot.
Appreciated it .
Regards,
Wendy
It's a little hard to tell what the TPAR file has failed to upload. However, it generally fails due to unusual characters. I do notice that it appears you have a dollar sign with what I assume is one of the suppliers (Double Story$3500INC, 5 Stages). I would be looking at removing that and also the comma.
Let us know how you get on that TPAR lodgement after making those changes.Hi Steven,
Thanks for your reply. We will upload this in the ATO website through business portal.
Regards,
Wendy
Hi Steven,
Is it possible to fix the problems at your end? Thanks.
Regards,
Wendy
Card names and TPAR generation is a user-enter process. There is nothing we can do on our end to help aid that process - short of providing generalised commentary on potential ways it could be have failed (which I've outlined in my previous post).
