We run Rebuild Data and the same errors come back

What is actually happening

Verify Data (File, Utilities, Verify Data) reads through the company file and checks that its internal structure agrees with itself: that list entries, transactions and the links between them point where they should, and that stored totals match the records behind them. It changes nothing. It tells you whether it found problems and writes the details to a log file called QBWin.log.

Rebuild Data asks you to make a backup, then works through the file and rebuilds the structures it knows how to rebuild: indexes, list references, some links and balances. Anything it cannot repair, it writes to the same log.

Damage keeps returning for two kinds of reason. The first is outside the file and keeps happening: a workstation that drops off the network mid-save, a host computer that sleeps or loses power, a file hosted over Wi-Fi or on a shared desktop, a backup or antivirus scan touching the file while people work in it. A larger file means longer saves, and a longer save is a bigger window for an interruption.

The second is inside the file. A long-lived file has been converted to a new QuickBooks version many times and carries decades of links. Some damage is beyond what Rebuild Data can repair. It leaves it in place, and the next Verify finds it again.

What people try first, and what it costs them

Rebuild Data, again. A second or third pass sometimes clears what the first left. When the same lines are in the log after several runs, more runs will not change them, and each one needs the file in single-user mode.

File Doctor and other repair utilities. Useful for a file that will not open or a damaged installation. They work on the same file and fix the same class of problem.

Intuit's data services. A paid repair where Intuit's team takes a copy of your file and returns it repaired. This is the right call when the file will not open, when damage followed a specific event like a crash, or when Rebuild Data cannot clear an error and you need that same file working again. Ask what they will change or remove. It is not the answer when the real problem is size and age: you get your file back, repaired, with every year still in it.

Condense. Often suggested to shrink a damaged file. On a damaged file it tends to stop partway, which leaves you restoring from the backup.

Starting over. Clean structure, no history, and your team re-keys open orders.

What a line-by-line rebuild does instead

The word "rebuild" means two different things, and buyers often confuse them.

Rebuild Data is a repair pass on your existing file. Same file, same history, same structure, with some damaged pieces fixed in place.

A line-by-line rebuild creates a new company file and enters your data into it fresh: lists, items, the opening position at a cutover date you choose, then every transaction since, line by line, and every open order. Your old file is never changed. It becomes the retired file, read-only, holding every year before the cutover.

The new file has a new internal structure. The links, indexes and stored totals that keep failing Verify in the old file are not copied across; they are created new as each record is entered. What comes over is your data: names, items, documents, amounts.

That is also why the proof is different. A clean Verify only says a file agrees with itself. Before the final payment you get a scorecard comparing the new file to the old one at each tier: trial balance at every month-end, AR and AP by name, inventory by item and site, open sales orders and purchase orders. Any difference is named and explained, and you approve it.