Quick answer
A QuickBooks validation error means the company file failed one of QuickBooks' internal integrity checks — a transaction link, list entry, or field no longer matches the rules QuickBooks requires. It is not the same as an unrecoverable crash. Back up the file, run Verify Data, note the exact messages, rebuild, and verify again before you consider restoring a backup.
What a QuickBooks validation error means
QuickBooks Desktop validates your data constantly. Every time it reads a transaction, it checks that the supporting records still line up: the customer on the invoice exists, the account on the bill still exists, the payment is still linked to the invoice it pays, and the totals add up. A validation error is what you see when one check fails.
There is no single "validation error" dialog. QuickBooks reports a failed validation in three places:
- Verify Data returns "Your data has lost integrity", or the Verify Results window lists specific errors.
- QBWin.log records lines such as "Verify Target: Invalid Open Balance" or "Verify list. Duplicate name encountered".
- Opening, saving, or rebuilding can produce a message naming the transaction, list, or record that failed.
Most findings are repairable and the transactions remain. Find out what failed, fix it in order, and confirm with a second Verify pass.
Not the same "validation". "The validation code is incorrect or the service is temporarily unavailable" is an activation message, not data damage, and it is fixed from the QuickBooks Tool Hub. This guide covers data validation, which is handled with Verify and Rebuild. For the crash dialog, see QuickBooks unrecoverable error.
Symptoms that point to a validation failure
- Verify Data finishes with "Your data has lost integrity" instead of "QuickBooks detected no problems with your data".
- The results window lists errors with record numbers, or Rebuild finishes but leaves errors behind.
- Reports do not match: an aging total disagrees with the register, or a balance changes with no posted entry — often link damage between transactions.
- A transaction opens with missing lines, a blank name, or an error when you save it.
- Duplicate names appear after an import, or a list entry cannot be edited or deleted.
Common validation messages and what they point to
These examples use the wording Intuit publishes for the most common data damage errors. Your build may add record numbers, so write down the full line before you change anything.
| Message | Damage type | What it points to |
|---|---|---|
| "Your data has lost integrity" | Any | General damage; continue to Rebuild |
| Verify list. Duplicate name encountered | List | Two records share a name; clean up the list |
| Verify Target: Invalid Open Balance | Transaction | A transaction carries an opening balance it should not have |
| Verify Item: Invalid tax agency | List | An item points at a tax agency that no longer exists |
| Verify Account List Item ###: View out of sequence | List | Chart of Accounts ordering is broken |
| GetDecryptedCreditCardNumber: The decryption has failed | List | Encrypted fields such as card numbers or SSNs cannot be read |
An error that names one transaction is usually fixable by editing or re-creating it. An error about a table, a header, or the file itself is more serious and can behave like error 6000, where the file opens inconsistently or refuses to open at all.
Validation error versus unrecoverable error
Both interrupt your work, but they call for different first moves.
| Signal | Validation error | Unrecoverable error |
|---|---|---|
| What QuickBooks does | Finishes the check and reports the problem | Closes unexpectedly, often mid-task |
| What you get | A named error, a Verify result, or a log line | "Unrecoverable Error XXXXX XXXXX" with numeric placeholders |
| File state | Usually still openable and usable | Often locked; needs a clean reopen first |
| First move | Back up, then Verify and review | Back up, then reopen safely before any utility |
Do not run Rebuild on a file that has just crashed QuickBooks. An interrupted write may still be finishing, and rebuilding on top of it can make a recoverable problem worse. Treat a crash as a stop sign: make the copy, restore normal opening, then fix the data.
Common causes, ranked
- Interrupted writes. A power loss or crash while the file is open leaves the company file and its transaction log out of step.
- Duplicate names from imports. Merging lists or transactions from another company file can create two records with the same name, which then fails every list validation.
- Damaged links. A deleted or re-created payment or invoice can orphan the records that pointed to it; reports are usually the first sign.
- Damaged encrypted fields. Card numbers, bank details, and SSNs are stored encrypted; when that encryption breaks, validation fails even though ordinary transactions are fine.
- Structural damage. Intuit classifies errors such as -6000, -301 as structural; they often trace to the file's location, a dropped connection, or failing hardware.
- Version mismatches. Incomplete QuickBooks or Windows updates can leave the program reading a file format it does not fully support.
Before you begin
Back up the whole folder first. Copy the folder that holds the company file — the .QBW, the .TLG transaction log, the .ND network file, and the QuickBooksAutoDataRecovery folder if present — to an external drive. Rebuild and restore write data, and if either goes wrong this copy is what a recovery specialist needs.
- Rights: sign in to Windows with an account that can write to the company-file folder.
- Version: press F2 in QuickBooks to confirm your version and release before following menu instructions.
- Time: Verify takes a few minutes on an average file; Rebuild can run much longer. Do not start one when you need the file back immediately.
How to triage a validation error safely
Copy the company-file folder to safe storage
Close QuickBooks, then copy the entire folder — not only the .QBW — to an external drive or another computer. Name the copy with today's date. Everything that follows becomes reversible with this one step.
Update QuickBooks and close every window
Install the latest release from Help → Update QuickBooks Desktop, then restart the program. Open the file, go to Window → Close All, and leave only the Home page.
Run Verify Data and write down the result
Go to File → Utilities → Verify Data. Verify only reads the file, so it is safe at any point. You will see no problems, an error message, or "Your data has lost integrity". Record the exact wording before moving on.
Read every error in Verify Results and QBWin.log
In the results window, select Expand All, and open See Online Article where it is offered. For log detail, press F2, then F3, open the Open File tab, select QBWin.log, and choose Open File. Search with Ctrl + F for "Begin Verify" to reach the latest run.
Run Rebuild Data and keep the pre-rebuild backup
Go to File → Utilities → Rebuild Data. QuickBooks requires a backup first; save it under a new name and do not overwrite an older backup. Rebuild may look frozen, but as long as the mouse pointer moves it is working. It repairs the file's internal structure without deleting transactions, though custom report layouts and preferences can be lost.
Verify again, and rebuild while the errors change
Run Verify Data after Rebuild. Two or three passes are normal as each unlocks the next repair, and errors should change each round. If the identical error returns, stop rebuilding. If the first rebuild ran more than two hours, contact Intuit support before continuing.
Fix the named list and transaction errors manually
For a duplicate-name error, back up again, open the list named in the log, and edit one duplicate so the records differ. For a transaction error such as an invalid open balance, open the named transaction and correct or re-create it. Re-run Verify after each repair so you know which change fixed what.
Use File Doctor when the errors look structural
If errors name tables, headers, or the file itself, run the QuickBooks File Doctor from the Tool Hub: open Company File Issues, select your file, and choose Check your file. A scan can take 10–15 minutes, and it sometimes reports failure even when it repaired the problem, so try opening the file afterward.
Verify the fix
- Run File → Utilities → Verify Data and confirm it reports no problems.
- Press F2 and select Review last Verify / Rebuild to see the final repair result.
- Open the transactions named in the log and check names, accounts, and amounts.
- Compare a balance sheet and an A/R aging report against a copy from before the error appeared.
- Create a fresh backup, store it off the machine, and then resume normal entry.
When a validation error points to real data damage
Intuit groups data damage into four types: list damage (records), transaction damage (entries), link damage (connections between entries), and structural damage (tables or headers). List and transaction damage usually clears with Rebuild plus a manual edit; link and structural damage is where caution pays off.
Treat it as genuine data damage when any of these are true:
- Verify says "Your data has lost integrity", or the same error survives two rebuilds unchanged.
- The log names a table or header rather than a single transaction.
- Encrypted fields cannot be decrypted, so card, bank, or SSN data is unreadable.
- Transactions are missing, reports disagree, or an entry cannot be opened.
- Rebuild itself crashes with a target-chaining message or an unrecoverable error.
Stop rebuilding the original file at that point. Each run writes to it, and if two clean passes have not fixed it, more will not either.
If validation errors keep coming back
Restore the newest backup that verifies clean, under a new file name, and re-enter work done since that date. Do not restore over the damaged file — it may still be recoverable. If you have no clean backup, the next step is professional company-file repair or Intuit Data Services; send the untouched original.
Prevention
- Back up on a schedule and test a restore quarterly; an untested backup is a guess.
- Shut down cleanly and use a battery backup so a power cut cannot interrupt a file write.
- Keep the company file on a local drive or server share, never in a consumer sync folder.
- Run Verify twice a year, deduplicate before importing lists, and verify the file after each update.
Frequently asked questions
Does a validation error mean my data is lost?
No. It means a rule was broken, not that records were deleted. Most findings clear with Rebuild plus one manual repair, and the transactions remain in the file. Data loss becomes a real risk only if the file is damaged further by repeated forced repairs, which is why the folder copy comes first.
Is Verify Data safe to run?
Yes. Verify is read-only: it reports what it finds without changing anything. Rebuild is the tool that writes repairs, and it asks for a backup first. You can run Verify as often as you like while troubleshooting.
How many rebuilds before I restore a backup?
Two or three passes are normal, as long as the errors change each time. If the same message returns unchanged after two rebuilds, more passes will not help. Run File Doctor, then restore a clean backup to a new name or escalate to professional repair.
Can I keep entering transactions while errors are present?
Avoid it. New entries can attach to damaged links, and they will not exist in your pre-repair backup. Work in a copy if you must keep invoicing, and keep the original untouched until Verify reports clean.