A damaged QuickBooks file needs triage.

Stop and copy before you fix. Make a plain file-system copy of the company file (and any recent backups) somewhere safe before running any repair, because repair tools modify the file and a failed repair on your only copy narrows the options fast. Then run Intuit's built-in sequence — Verify Data to diagnose, Rebuild Data to fix what it can, File Doctor for the network-and-file class of problems — which resolves the problems they were built for. If the built-ins don't clear it, that's the fork in the road, and which branch you take next depends on what the errors actually say — which is exactly what the free review reads.

We triage and repair the operational tier: the built-in tool sequence run properly with backups staged, list damage (broken names, corrupted templates), rebuild-resistant issues that respond to file-management surgery like condensing or re-sorting, and the export-rebuild path when a file is beyond repair but its data is readable. The boundary we state plainly: deep binary corruption — a file even Rebuild and Intuit support can't open — is data-surgery territory for dedicated recovery specialists with proprietary tooling, and pretending otherwise would waste your money. When that's the honest answer, we say so early, and we prepare what makes their work cheaper: the backups inventory, the last-good-copy timeline, and the books plan for whatever comes back.

Mixing the two up is expensive in both directions, so here's the honest test. File damage is technical: error codes on open, Verify reporting damage, crashes on specific operations, lists behaving impossibly. Messy books are human: balances that don't tie, negative undeposited funds, reports you distrust — the file opens fine and faithfully displays wrong bookkeeping. Repair tools can't fix wrong bookkeeping, and a cleanup can't fix a corrupt database. The review sorts which you have — many files have a little of both, and each gets its own fix at its own honest price.

Then the books get rebuilt rather than the file — and it's a solved problem, not a catastrophe. The most recent working backup becomes the base, the gap between backup and failure gets re-entered from bank and card statements, and if no usable backup exists at all, the full rebuild works from the records your bank, processor, and payroll provider still hold — that's financial reconstruction, and we run it as a scoped fixed-fee project. Losing the file never means losing the history; it means re-collecting it from the parties who kept their copies.

Two habits and one honest observation. The habits: real backups on a schedule you verify (a backup you've never test-restored is a hope, not a backup), and for Desktop files, decent hygiene — stable network storage, no force-shutdowns mid-write, file size watched as the years accumulate. The observation: chronic file damage on an aging Desktop company file can be the push toward either a fresh Desktop file or a move to QuickBooks Online, where the file lives in Intuit's infrastructure — a genuine trade-off with its own pros and cons, and our migration page treats it honestly rather than as an automatic upgrade.