Vendor reports: operationalResolved · vendor status “resolved”Official status API

Some customers in Australia are unable to lodge BAS directly to ATO from within QBO.

Reported by QuickBooks · HR, Finance & Ops · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Oct 28, 2024, 23:46 UTC
Vendor's clock
Resolved
Oct 30, 2024, 01:22 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 d 1 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • QuickBooks reports operational: "Some customers in Australia are unable to lodge BAS directly to ATO from within QBO.".[E1, E2]
  • The vendor marked it resolved at 2024-10-30 01:22 UTC.[E3, E7]

Affected products and regions

  • Components: APAC.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2024-10-30 01:22 UTC · summary s1, evidence 83f4889b0cc4ed17

Evidence (7)
  1. E1QuickBooks reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Some customers in Australia are unable to lodge BAS directly to ATO from within QBO.". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-10-28 23:46 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: APAC. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-10-30 01:22 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: APAC

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

QuickBooks is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Oct 28, 2024, 23:46 UTCVendor-reported startVendor time
  2. Oct 30, 2024, 01:22 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.