Why Is My QuickBooks Online Not Working Today?

Start by recording the exact symptom and protecting the accounting record. Then check the live QuickBooks status page and note the affected product and region. This narrows the failure before you change settings or data.

Yes, if the problem is sudden and affects multiple users or features. Check the official QuickBooks status page before assuming your company data or computer is at fault.

For QuickBooks Online browser symptoms, a private-window test is a good first isolation step. Clear cache or Intuit-specific cookies only when the private test points to browser state. For Desktop-only problems, browser cache is usually not relevant.

No. Deleting accounting records is not a safe generic troubleshooting step. First identify the root cause and preserve a backup or control evidence.

Save the exact error text, date/time, product edition, affected company/workflow, and relevant control report or statement. Redact passwords, tax IDs, bank details, and security codes.

Use official Intuit support for account ownership, billing, subscription, security verification, vendor-hosted incidents, payroll filing/funding, payments, or any issue that remains reproducible after safe checks.

Treat the incident as resolved only when the affected workflow works again and any delayed bank, payroll, invoice, or payment activity is reconciled rather than blindly retried.

Only if it preserves accounting integrity and you document it. After the underlying issue is resolved, reconcile any temporary manual entries, imports, payments, or duplicate submissions.

No. AccountingQnA is an independent educational resource and is not affiliated with, endorsed by, or sponsored by Intuit or QuickBooks.

No. Do not share passwords or one-time verification codes. Start support from an Intuit-owned domain or the in-product Help flow and follow Intuit's secure verification process.

Yes. A current Intuit incident or maintenance window. Test this possibility with the smallest reversible check before changing live accounting data.

Yes. Regional latency or a partial feature outage. Test this possibility with the smallest reversible check before changing live accounting data.

Yes. Local browser cache or cookie problems. Test this possibility with the smallest reversible check before changing live accounting data.

Yes. A corporate firewall, DNS, VPN, or network issue. Test this possibility with the smallest reversible check before changing live accounting data.

Yes. A bank, payroll, payments, or other connected service is down while core QBO remains available. Test this possibility with the smallest reversible check before changing live accounting data.

Check the live QuickBooks status page and note the affected product and region.

Ask a second authorized user whether the same company and workflow fails.

Try a private supported browser.

Test a different trusted network if appropriate.

Identify whether the failure affects all of QBO or only banking, payroll, invoices, or another service.

A restart can clear a temporary session or process problem, but first save work and record the exact symptom. For QuickBooks Online, restarting should be a controlled test, not a substitute for checking the underlying cause.

Yes when permissions or user-specific settings may be involved. Compare an authorized user who can safely perform the same workflow and do not broaden permissions permanently just for testing.

Yes as an isolation test when the issue could be local. If the same company and workflow work elsewhere, focus on the original device, browser, network, or local configuration.

Yes. User roles, company access, admin changes, and feature entitlements can make a problem look like a software failure. Compare permissions with a known-working authorized user.

Yes. Banks, payroll services, payments, ecommerce apps, CRMs, and other integrations can fail independently. Check whether the core QuickBooks workflow works without assuming every connected service is healthy.

Record the product and edition, company/region, exact error text, time of failure, affected users, recent changes, what you tested, and the result. Do not include passwords, MFA codes, full bank data, or other secrets.

Screenshots can be useful evidence if sensitive information is redacted. Also keep text versions of error codes and timestamps because screenshots alone may not capture the full diagnostic context.

Yes. Record whether the issue began before or after a browser, operating-system, QuickBooks, bank, payroll, or integration update. Treat timing as evidence, then confirm with a controlled test.

Yes for cloud access and connected services. A password reset, MFA policy change, revoked token, or new security requirement can interrupt sessions and integrations.

It can. Test only through approved security procedures. Do not permanently disable firewalls, antivirus, or company security controls just to make QuickBooks work.

For QuickBooks Online symptoms, a private window can help separate cached browser state and extensions from account or service issues. It is less relevant to purely Desktop company-file problems.

Yes. Privacy, ad-blocking, password, script-control, or security extensions can affect authentication or page behavior. Disable only nonessential extensions for a controlled test.

Search the books before manually re-entering anything, use a defined date range, and reconcile after feeds or integrations recover. Do not assume an item is missing just because it is not visible in the first screen.

No. An adjustment should reflect a known accounting reason, not hide an unexplained difference. Investigate the source first and involve an accountant for material historical corrections.

Use extra caution. Historical changes can alter financial statements, reconciliations, payroll or tax filings. Document the proposed correction and involve the appropriate accountant or payroll/tax professional.

Record timestamps, affected users, network conditions, and the exact workflow each time it happens. Intermittent evidence helps separate local instability from vendor-side incidents.

Compare what changed between the successful and failed attempts. Repeated symptoms usually indicate the underlying cause was not removed or an external dependency is unstable.

For some Desktop files and large Online reports, size and workload can affect performance. Test a smaller report or controlled company-file operation before making data changes.

Use a supported current release, but protect data first and avoid major upgrades during a critical payroll, close, or filing window without a rollback plan.

Usually no. First determine whether the problem is the program, company file, network, or configuration. Reinstallation is more appropriate after evidence points to damaged program files.

Before company-file repair, migration, transfer, major imports, historical transaction edits, payroll corrections, or other changes that could affect balances or audit history.

Keep it until the corrected or migrated environment has been accepted and material reports have been verified. Follow your organization's retention and compliance policy for longer-term storage.

Choose reports tied to the affected workflow: trial balance, bank reconciliation, A/R, A/P, payroll liability, inventory valuation, sales/invoice aging, or migration control totals.

Yes. QuickBooks Online, Desktop, Enterprise, Payroll, and region-specific editions can expose different menus, features, permissions, support channels, and connected services.

Yes. Support options, payroll/tax rules, bank feeds, payments, and product availability can differ by country and subscription. Verify instructions for the correct region.

It can if the product's sign-in or redirect path changed. Start from an official Intuit domain rather than relying on an old bookmark or an unverified search result.

Not automatically. Use the Help option inside QuickBooks or an Intuit-owned support page. AccountingQnA does not present an independent number as an official QuickBooks number.

Not merely because they claim to be support. Independently verify the organization and case, never share passwords or MFA codes, and follow your security policy before allowing remote control.

Escalate through official vendor support and the relevant accounting/payroll professional promptly. Avoid experimental fixes that could create duplicate payments, missed filings, or incorrect tax records.

Record the root cause, the exact fix, product/version, date, evidence used, accounting verification performed, and any preventive control. This makes future incidents faster and safer.