ContributionsMost RecentMost LikesSolutionsRe: TPAR report failed to lodge Hi Gavin, Thank you for your suggestion (count back 5 from line listed as error). It worked and I could idently the relevant supplier card. For some reason, when the supplier card was imported into MYOB from our construction software, a tab space was inserted in the middle of the first line of the address, thereby creating a 'gap' in the address. This was strange because the extra spacing is not on the supplier card in our construction software. But, none the less, the extra spacing was removed from the card in MYOB and the new TPAR lodged succesfully. Thanks again! Regards, Heather Re: TPAR report failed to lodge Hi Gavin, Thank you for you reply. I should have explained myself better. I had opened the TPAR report in Notepad and did a search for non ASCII characters and then removed them in MYOB and ran a new TPAR report and lodged it – which still failed. I will try your method and deduct 5 from the line number to try locate the cause. Regards, Heather TPAR report failed to lodge Our 2023 TPAR has failed to lodge. I have opened the report in Notepad to try identify the error. I have removed all visible non ASCII characters (in particular forward slash i.e Unit 1 / 789 Street, which has never been an issue in the past) but teh report is till failing to lodge. Each time I try to re-lodge, a new line is listed as the error by the ATO, and I can't identify the actual line because Notepad sees the entire report as one line. I did email the MYOB Support team asking if they would review our TPAR to try identify the error - and no suprises, I have not had any response. I would like to know if MYOB changed something within their software that now clashes with the ATO's as this is the first time in 9 years that I have had the report fail to lodge and have not changed the way I enter new suppliers in the last year. Is anyone else having issues? Solved