Verify Your QuickBooks Desktop Company File Before Repair or SuperCondense

Learn how to run QuickBooks Verify to confirm your company file is structurally sound, and what to do when Rebuild cannot resolve the errors Verify reports.

Before scheduling any file repair or SuperCondense, our engineers need to know whether your QuickBooks Desktop company file passes the built-in Verify utility. Verify reads every transaction, list entry, and link inside the file and checks the data structures for damage. A clean Verify means the file is structurally sound enough to proceed with a condense or other service. When Verify reports errors, those errors must be resolved first — either through the Rebuild utility or through professional repair.

Preconditions

Before running Verify, take these steps:

1. Create a verified backup of your company file (File ▸ Create Backup ▸ Local Backup). Do not skip this step; Rebuild can occasionally alter data in ways you do not want if the file is already fragile.
2. Switch to Single-User mode (File ▸ Switch to Single-User Mode). No one else should be working in the file during Verify or Rebuild.
3. Close all open windows inside QuickBooks (Window ▸ Close All).
4. Confirm you are running Verify on the same machine where the company file physically resides. Running it across a network connection can produce misleading results.

Running Verify

1. With the company file open, go to File ▸ Utilities ▸ Verify Data.
2. QuickBooks will display a progress indicator. On large files this can take several minutes.
3. When Verify finishes, one of two messages appears:
   • "QuickBooks detected no problems with your data." — The file passes Verify. No further action is needed before scheduling a condense or other service.
   • "Your data has lost integrity." — Verify found structural damage. A details window or the QBWin.log file will list the specific error codes and affected transactions.

Running Rebuild After a Failed Verify

When Verify reports lost integrity, the next step is Rebuild:

1. Go to File ▸ Utilities ▸ Rebuild Data.
2. QuickBooks will prompt you to create a backup before rebuilding. Allow it to do so.
3. Rebuild will attempt to repair the damage Verify identified. This process can take considerably longer than Verify on large files.
4. When Rebuild finishes, run Verify a second time. Rebuild is not considered successful until a subsequent Verify passes cleanly.

When Rebuild Cannot Fix the Errors

In some cases Rebuild runs to completion but the follow-up Verify still reports errors, or reports the same errors unchanged. Common signs that Rebuild has not resolved the underlying damage include:

• Verify reports the same error codes after Rebuild as before.
• The QBWin.log file shows recurring "LVL_ERROR" entries for specific transactions, vendor records, or target chaining errors.
• QuickBooks crashes or freezes during Rebuild.
• Rebuild reports success, but specific transactions or reports still display incorrect balances.

When this happens, the file has structural damage that the built-in utilities cannot reach. A professional repair targets the corruption at the database level — repairing damaged transaction links, removing unrecoverable records such as corrupted bills with missing vendor names or negative balances, and restoring the file to a state where Verify passes cleanly.

Our engineers frequently see files where damaged transactions cause target chaining errors that Rebuild simply cannot resolve. In those cases the damaged transactions must be identified, removed, and re-entered from source documents. The repair process produces a report of every transaction that was removed so nothing is lost without a record.

Why a Clean Verify Matters Before SuperCondense

A SuperCondense or date-range split cannot be applied to a file that fails Verify. The condense process reads and rewrites large portions of the database; if the underlying structures are damaged, the condense will either fail partway through or produce a file that is itself corrupted. Our engineers require a passing Verify before scheduling any condense work.

If your file cannot pass Verify even after Rebuild, the repair must be completed first. Once the repaired file passes Verify cleanly, the SuperCondense can proceed on the healthy file.

What Verify Does Not Check

Verify checks structural integrity — the internal links, balances, and data relationships inside the file. It does not validate that every transaction is correct, that account balances match your bank statements, or that no user entered a transaction to the wrong account. A file can pass Verify and still contain accounting errors. Verify answers one question: is the database itself structurally sound?