Single Touch Payroll errors in QuickBooks Online: four business-side fixes

Australian QuickBooks Online customers are hitting a familiar wall with their first Single Touch Payroll lodgments: pay events that fail with cryptic codes. One failure arrives with no code at all. We reviewed the accepted guidance, published by Intuit for its Australian payroll users, which divides the failures into business errors and employee-specific errors. The guidance covers four business-side messages in detail, and each has a direct fix.

The split between business and employee errors

The split matters for troubleshooting. Business errors point at employer records: the address, the legal name, the phone number, or the lodgment link itself. Employee-specific errors point at a worker’s record instead. All four failures covered here sit on the business side, which is why the fixes land in payroll settings rather than in an employee profile.

A duplicate the ATO says it already holds

This error has no number. The screen reports that the submission could not be processed because “we already have a submission with this submission ID”. In plain terms, the pay event reached the ATO more than once. A timeout while the first response came back can prompt the software to try again, so the duplicate is often the system’s own doing.

The instinct is to resubmit. Resist it: the ATO already holds the event. If you were resending the original pay event to correct earlier figures, the guidance says to send an update event instead.

1. Leave the original event as it stands.
2. Correct whatever figures or details were wrong.
3. In the payroll area where pay events are lodged, start a new event.
4. Choose Update event as the type rather than a pay event.
5. Lodge it, then confirm the status shows accepted.

An update event refreshes the year-to-date figures without creating a second pay run, so no duplicate submission ID is generated.

Error 200001 is a timeout on the ATO side

Both numbered errors arrive prefixed with the same generic software label, which is why the on-screen text reads oddly. Error 200001 means a timeout inside the ATO’s own system. Nothing in your payroll data caused it. Try the lodgment again, as the guidance recommends. If the failure persists, call the ATO and quote the code, because the block sits on the tax office’s side and only they can clear it.

Which business details block a pay event with no error number?

This one appears simply as “the software”, followed by an element name: “AddressDetailsPostal”, “OrganisationName”, or “ElectronicContact”. Each maps to a field you can fix. The first is the business address, the second the legal name of the business, the third the business phone number. Two address fields, Address Line 1 and Suburb, are compulsory; leaving either blank will block the event.

The guidance routes the fix through three screens, all reached the same way. Select Payroll from the left menu, then open the Payroll Settings tab.

• Details, under the Business settings column: confirm the address, the legal name, and the phone number.
• ATO Settings, in the same column: check the fields held there as well.
• Employing Entities, if you operate more than one entity: repeat the checks for each.

Save each screen after correcting it, then lodge the pay event again.

Error 008 and the missing agent link

Error 008 is an authorisation failure. The screen tells you that you are “not authorised to submit this lodgement on behalf of the client”, then mentions linking the client to your Australian business number and a business appointment. The wording also references AUSkey, a credential retired years ago, which dates the message.

For registered tax and BAS agents, the code means the link between the agent and the business is missing or incomplete. Check Relationship Authorisation Manager, known as RAM, or the tax and BAS agent portal. The business must be listed as your client, and your authorisation must extend to lodging on its behalf. Older notes point to a tool called Access Manager; agent appointments are managed in RAM and the portal today.

Before you lodge again

Three of these four failures end at the same place: your own settings. Verify the business address, legal name, and phone number in every screen listed above, since a mismatch in any one of them can bounce an otherwise clean pay event. Keep the error code on screen when you call the ATO about a timeout. When a correction is the goal, reach for the update event rather than a second copy of the original.