QuickBooks disaster readiness: backups, licenses, and bank feeds

Disaster season keeps its own calendar. The failures it exposes in accounting practices do not. After every storm, fire, and extended outage, community threads describe the same gaps. Firms had a plan for the weather. The plan never covered the company file, the license, or the bank feed. We read these threads after each one, and the pattern barely changes.

The plan covers the storm, not the file

Most written plans handle people, premises, and insurance. Fewer address the mechanics of a practice that runs on QuickBooks. The gap shows up quickly. Tax deadlines rarely pause for a local emergency. Federal disaster declarations often bring extended filing dates, while state-level emergencies usually do not, so calendar pressure can outlast the disruption itself.

Does your backup actually restore?

A backup nobody has restored is a hope, not a plan. Desktop users report this failure more than any other after a loss. The file existed. The copy opened with errors, covered only part of the year, or sat on the machine that burned.

QuickBooks Desktop builds its own compressed backup file rather than a plain copy of your books. That file is the one designed to rebuild everything. Test it on a schedule you set in advance: restore the latest backup to a spare computer, open it, and run a report you recognize. Doing this the week after a fire helps nobody.

Set the automatic backup to run daily and to keep several versions rather than one. Keep at least one copy somewhere a single event cannot reach.

Sync folders and live company files do not mix

A second pattern repeats in these reports: firms keeping the company file inside a consumer cloud sync folder. It feels like a backup. It behaves like a corruption risk. Sync tools try to copy a database while it is open, and a partial sync can leave the file unusable.

Work from a local drive. Back up to the cloud on a schedule if you like, but let the backup routine create its compressed file first. If your books currently live in a synced folder, close the program, move the file, reopen it, and immediately run a fresh backup to confirm the move worked.

Desktop licenses live on the machine you lost

QuickBooks Desktop licenses activate against a specific computer. After a theft, fire, or flood, that computer is gone and the activation went with it. Firms then discover the license number lived in an email stored on the same machine.

Keep the product and license numbers, the account sign-in, and any payroll subscription details somewhere outside the office. A password manager survives an office fire; a desk drawer does not. A replacement install will want proof of ownership before it activates, so make sure that proof is reachable when the hardware is not.

QuickBooks Online changes the problem

Online subscribers lose none of their data in a local disaster. The books sit in the vendor’s cloud, not your building. What firms lose is access. Threads describe lockouts after the phone receiving verification codes was destroyed, or after the only administrator was unreachable for days.

Two habits prevent most of this. Keep the recovery email and phone number current on every login, and give a second trusted person administrator access. One unreachable account should never idle an entire practice.

Bank feeds after a disruption

Bank feeds fail quietly while an office is closed. Connections lapse, then re-download weeks of transactions at once when re-established. Duplicates and gaps follow, and they surface exactly when nobody has time to reconcile.

Repair starts with a range check. Compare the earliest transaction in the refreshed feed against the date of your last reconciliation. Clear duplicates before they enter the books, then reconcile the gap period before trusting current balances. Payroll connections deserve the same look, because errors there reach employee pay rather than a report.

A check you can run this week

• Restore your most recent backup to a spare machine and open it.
• Confirm automatic backups run daily and keep several versions.
• Move any company file that lives in a sync folder back to a local drive.
• Store license numbers and sign-ins somewhere off-site and reachable.
• Update recovery contacts on every QuickBooks login and add a second administrator.
• Write down your last reconciliation date so feed repairs have a starting point.

None of this takes long. The threads agree on what does: firms that recovered quickly had tested the boring parts in advance. The ones that struggled had plans on paper and backups no one had ever opened.