Quick answer
Read the error first. An authorisation / connection error means the ATO link needs attention — check your machine credential, the ABN in your ATO settings, and that your software ID is linked in ATO Access Manager. A validation error means a field on the return needs fixing before it will lodge. If it's a temporary ATO or SBR outage, wait and resubmit later.
WHY IT HAPPENS
Three very different problems, one error box.
HandiTax lodges to the ATO over Standard Business Reporting (SBR), through the Practitioner Lodgment Service (PLS). Failures fall into three buckets. Authorisation errors mean the ATO doesn't recognise or trust your software connection — usually a credential or software-ID issue. Validation errors mean the return itself has a problem the ATO won't accept, like a mismatched name, TFN or missing field. And sometimes it's simply the ATO or SBR having a bad day — a temporary outage that has nothing to do with your setup. Identifying which bucket you're in tells you exactly what to fix.
HOW TO FIX IT
Work through these in order.
- Read the actual error messageNote the exact wording and any code (for example an SBR.GEN.AUTH code points to authorisation, not the return). The message usually tells you whether it's a connection problem, a field on the return, or an ATO-side issue — don't skip straight to resubmitting.
- Check the ATO/SBR isn't downIf lodgements were working earlier and suddenly fail with connection or "try again" messages, check the official SBR system status page (sbr.gov.au) and the ATO's PLS status page. If there's an outage, there's nothing to fix on your end — wait and lodge later.
- Confirm your machine credential is validPLS lodgement relies on a machine credential tied to myGovID and Relationship Authorisation Manager (RAM). If it's expired or was renewed, re-point HandiTax to the current credential (keystore) and enter its password again. An expired credential is one of the most common causes of a sudden authorisation failure.
- Match your ABN and agent details to the ATOCheck the ABN in your HandiTax ATO settings matches exactly what the ATO holds, and that your registered agent number is correct. Small mismatches between your software and the ATO's records block authentication.
- Verify the software ID in Access ManagerYour software ID must be linked to your practice in ATO Access Manager (and, for agents, to your agent number, not a client's ABN). If it isn't listed or was recently changed, add/relink it — the ATO can take up to about 24 hours to propagate the change, so retry after that.
- Fix validation errors on the returnIf the error names a field, section or value, the return itself is the problem — correct the flagged item (name/TFN spelling, missing label, out-of-range figure) and re-run the lodgement. Using SBR pre-lodge/validation before you send can catch these early.
- Resubmit carefully — avoid duplicatesOnce you've addressed the cause, lodge again. Before resubmitting a return that "might have gone through", confirm it wasn't actually accepted (check the client's ATO status) so you don't lodge twice.
- Escalate to the ATO or your providerIf authorisation still fails after credentials, ABN and software ID all check out, contact the ATO on 1300 852 232 about the software ID link, and involve HandiSoft/Access support or your IT provider for the software and network side.
Keep credentials and software IDs documented. Machine credentials expire, staff change, and PLS links quietly break at the worst possible time — usually the last week of a lodgement run. Recording where your keystore lives, which software ID is registered and who the authorised person is in RAM means a lodgement failure becomes a five-minute check, not a scramble. If this keeps happening across the practice, it's worth having your setup reviewed properly.
