Check a Repaired QuickBooks File Before You Resume Data Entry
Before you resume data entry in a repaired QuickBooks file, confirm it is truly clean on your own computer; this checklist shows what to run and compare.
When a repair engineer returns your QuickBooks company file, the work is not finished the moment you download it. The file verified cleanly on our side, but your computer, your copy of QuickBooks, and your daily use of the data are the real test. This page walks through the checks we ask for before a single new transaction is entered.
Why verify again on your own computer?
A repaired file passes its final inspection on the machine where the repair was performed. Between there and your screen, several things change. The file travels through a download link, gets restored or copied, and opens under your QuickBooks release rather than ours. A fresh Verify run on your machine confirms that the journey reintroduced nothing, and that the copy you will actually work in is the copy that passed.
Before you start
- Keep the backup you sent for repair, or the pre-repair copy you made, within reach. It is your comparison baseline, and it should not be deleted until every check below passes.
- Save the repaired file exactly as delivered before you open it. If anything looks wrong later, this pristine copy is what goes back to us.
- Sign in as the QuickBooks Admin, since verification needs full access to the data.
- Work in single-user mode with the file on a local drive. A copy on a network share can produce false errors.
Restart, then run Verify Data
- Close QuickBooks completely. If it was open when the file arrived, restart the computer as well; that clears any part of the old file still held in memory.
- Reopen QuickBooks and open the repaired company file in single-user mode.
- From the File menu, choose Utilities, then Verify Data.
- Let the utility run to the end. Do not open reports or type anything while it works.
- Read the result. A clean run reports that no problems were found. Any other wording means it found something, and the detail is written to qbwin.log in the same folder as your company file.
Run Verify more than once
One clean pass on a newly repaired file is good news, but two or three are better. Verify inspects lists, transactions, and links in sequence, and a second pass confirms the first was not a fluke. Leave the Rebuild utility alone during these checks: Rebuild changes data, and changing a freshly repaired file before you have compared it against your backup destroys the baseline you need.
Compare reports against the pre-repair backup
Verification proves the file is internally consistent. It does not prove the numbers are the numbers you had before the damage. Only your backup can answer that, so put the two files side by side.
Open the same reports in the repaired file and in the restored backup, set them to the same date range, and compare totals:
- Trial Balance as of your last closed period
- Balance Sheet, in accrual and, if you use it, cash basis
- Profit and Loss for the current year to date
- A/R Aging Summary and A/P Aging Summary
- Inventory Valuation Summary, if you carry stock
- Payroll Liabilities, if payroll runs through this file
Export each report to Excel or PDF from both files so the columns line up. Then spot-check a handful of individual transactions, favouring ones dated close to when the trouble began. A difference of even a few units on a total deserves a note; it may be the only visible trace of what the repair had to reconstruct.
The signs the file passed
- Verify Data reports no problems on repeated runs.
- Every report total matches the pre-repair backup exactly.
- The file opens promptly, with no error codes and no unexpected prompts.
- A fresh backup of the repaired file completes without complaint.
When all four hold, keep the pristine delivered copy and the baseline backup together for a full reporting cycle, then resume data entry.
If Verify still reports damage
Stop before you type anything into the file. New entries written on top of unresolved damage make the next repair harder.
Capture the exact message first. Copy the on-screen text word for word, and note the matching entries in qbwin.log. A precise message tells our engineers which structure failed and where to look; a summary of "it still says errors" does not.
Then return the pristine delivered copy, not the one you have been testing in, so the repair can continue from a known state. Files that keep failing verification after a professional repair often carry damage below what Verify can describe, and that is routine work for our QuickBooks rebuild and verification service.
Where the workaround reaches its limit
These checks confirm health; they cannot surface every fault. A file that verifies today and fails after the next Condense, or damage that returns weeks later, points to something deeper than the repair itself. When damage keeps coming back, the cause usually sits outside the file: a failing drive, an unstable network drop, or a QuickBooks release that writes badly. Fix the environment, or the next repair will not be the last.