Integrity Report: Interpreting Errors Found by the “Verify Data” Tool

When the QuickBooks “Verify Data” tool completes its check and reports “Your data has lost integrity,” it indicates that the software has detected structural discrepancies, broken transaction links, or orphaned database records. Understanding this diagnostic output allows you to identify whether the issue is a minor display discrepancy or severe database corruption. To interpret these findings accurately, inspect the QBWin.log file, review the error codes recorded under the verify summary, and determine whether the errors can be resolved with an automated rebuild or require targeted manual transaction correction.

Fast-Fix: The 45-Second Solution

Open the QBWin.log file and search for “LVL_ERROR” to view specific integrity failures. After the verify scan reports lost integrity, press F2, then press F3 to open the Tech Help window. Click the Open File tab, highlight QBWin.log, and click Open File. Scroll to the bottom and search upward for LVL_ERROR. The lines following this tag reveal the exact damaged tables, lists, or transactions causing the integrity failure.

Quick Status & Triage Snapshot

  • Data Risk Tier: Moderate to High. The presence of integrity errors means your financial tables or underlying lists contain discrepancies that can cause calculation mistakes or software crashes if left unaddressed.
  • Multi-User Impact: Moderate. While users may still be able to enter transactions, existing damage can spread to newly entered records across all workstations.
  • Common Trigger: Sudden network drops in multi-user mode, improper company file closures during save actions, power surges, or damaged list indexes.
  • Estimated Fix Time: 20 to 60 minutes (depending on whether the automated rebuild repairs the errors or manual intervention is needed).

Diagnostic Flowchart: Interpreting Verify Errors

  1. What did the final screen of the Verify tool state?
    • “QuickBooks detected no problems with your data”: Your database structure is healthy. No action is required.
    • “Your data has lost integrity”: Internal records are damaged. Proceed to Step 2.
  2. What type of error is recorded in the QBWin.log under LVL_ERROR?
    • List / Index Errors (e.g., duplicate names, broken accounts): These are low-risk errors that the automated Rebuild Data tool can typically repair on its own.
    • Transaction Target Errors (e.g., “Target unlinked,” out-of-balance entries): Moderate risk. The rebuild utility may fix them, but you will need to re-verify transactions to confirm accuracy.
    • Structural Database Damage (e.g., damaged link list, negative inventory corruption): High risk. Proceed to targeted repair or professional recovery.
  3. Did running the Rebuild Data tool resolve the error on a second verification scan?
    • Yes: The file is stabilized. Archive your rebuild log.
    • No: The remaining errors require manual transaction editing or database remediation.

Is Your Data at Risk?

The message “Your data has lost integrity” confirms that your database contains inconsistencies, but it does not mean your accounting records are destroyed.

  • Lower Risk (List and Index Corruption): If the errors relate to sorting orders, customer lists, or memorized transactions, your core general ledger balances are typically sound.
  • Higher Risk (Target Discrepancies): If the integrity check reveals errors such as Recalc error in transaction or Link list damaged, balances on your balance sheet or trial balance can deviate from actual ledger entries. Avoid posting major journal entries or closing your accounting period until these discrepancies are resolved.

Technical Anatomy: What This Error Means

QuickBooks stores company information across relational tables using a header-and-target model. For every financial transaction, there is one Header (the primary transaction record, such as Check Number, Total Amount, and Date) and two or more Targets (the specific distributions assigned to expense, asset, or liability accounts).

When Verify Data identifies an integrity failure, it has discovered a break in this architecture:

  1. Orphaned Targets: Target records exist in the database without an associated transaction header.
  2. Link List Damage: The database pointers linking an invoice to its payment record have become de-synchronized.
  3. List Index Failures: An internal ID for a vendor, customer, or inventory item points to a record that was dropped during an incomplete save sequence.

The software flags these conditions with the system alert LVL_ERROR within its background diagnostic logs.

Differential Diagnosis: Don’t Confuse This With…

Step-by-Step Repair Guide

Follow these steps to access, read, and act upon the specific integrity errors found in your report.

Step 1: Open and Isolate the QBWin.log File

The on-screen dialogue only provides a generic warning. The actual diagnostic breakdown is recorded in the application log file. For deeper file path details, refer to Log Files: How to Locate Verify.log and Rebuild.log in Windows.

  1. In QuickBooks, press F2 to display the Product Information window.
  2. Press F3 to launch the Tech Help interface.
  3. Click the Open File tab.
  4. Select QBWin.log from the list of internal documents and click Open File.
  5. Alternatively, open Windows File Explorer and navigate directly to:
    C:\Users\[YourUser]\AppData\Local\Intuit\QuickBooks\log\QBWin.log

Step 2: Search for Diagnostic Tags

Because the log file contains thousands of operational status lines, use targeted search terms to locate the integrity report.

  1. In Notepad, press Ctrl + End to jump to the very end of the document.
  2. Press Ctrl + F to open the Find dialog box.
  3. Type LVL_ERROR into the search field and set the search direction to Up.
  4. Click Find Next.

Step 3: Interpret Common Integrity Error Messages

Evaluate the log lines following LVL_ERROR to determine the proper fix:

  • Error Example 1:LVL_ERROR|Verify Account List: out of balance balance sheet
  • Error Example 2:LVL_ERROR|Error: Verify Target: Target unlinked in Txn #[Number]
  • Error Example 3:LVL_ERROR|Verify Item History: Item [ItemName] has negative asset value
    • Meaning: Inventory values have dropped below zero due to bills being entered with dates later than their corresponding sales invoices, disrupting average-cost tracking.

Step 4: Run the Automated Rebuild Data Tool

For general index and target discrepancies, use the automated rebuild utility as your primary repair tool.

  1. Go to File > Utilities > Rebuild Data.
  2. Click OK to back up your company file (this backup is required before the software will modify database tables).
  3. Let the Rebuild tool process all tables.
  4. When the process finishes, navigate immediately to File > Utilities > Verify Data and run the check again.
  5. If the Verify tool reports “QuickBooks detected no problems with your data,” the errors have been repaired.

Step 5: Address Unresolved Transaction Errors Manually

If the second verification scan shows that the same LVL_ERROR line persists, repair the transaction directly.

  1. Note the transaction date, type, and transaction number (Txn #) from the QBWin.log.
  2. In QuickBooks, open the transaction using Edit > Find or by browsing to the relevant account register.
  3. Make a minor edit to the transaction (such as adding a period to the memo line) and click Save & Close. This forces the database engine to re-index and re-write all header and target pointers for that record.
  4. Run Verify Data once more to confirm the error has cleared.
  5. If broad table damage persists across multiple records, use File Doctor Guide: Using QuickBooks File Doctor to Repair Severe Corruption to scan and repair lower-level database components.

Hard Stop: When to Call an Expert

Stop self-repair procedures and seek professional data recovery services if:

  • The QBWin.log reports LVL_FATAL accompanied by table allocation map errors (TAM error).
  • The Rebuild Data process halts with an unexpected application crash on every attempt.
  • The balance sheet discrepancy worsens or transaction history drops completely out of historical fiscal years after a rebuild attempt.

Closing the Books

Receiving an integrity failure notice from the Verify Data utility is a helpful early warning rather than a sign of irreversible damage. The diagnostic messages stored under LVL_ERROR in your QBWin.log point you directly to the affected tables, accounts, or transactions. By understanding the distinction between simple list issues and transaction discrepancies, running an automated rebuild, and editing broken transactions where needed, you can resolve database errors and keep your accounting records balanced and reliable.