C=147 and list merges — what happens: When you merge two customers, vendors, or items in QB, the old record is removed but QB's internal list index doesn't always update every transaction that referenced the old record. C=147 appears when Verify finds a transaction with a list reference that points to a record no longer at the expected index position. The fix targets the list records themselves — using the List & Items Condensed report or running a specific rebuild of the affected list section. Also check: QBWin.log's Verify Target for C=147 names the specific list type (e.g., "Customer:John Smith" or "Item:Office Supplies") — this tells you exactly which list to inspect for the orphaned record.

List Record Orphaning After Merge or Delete

C=147-specific cause — merging customers, vendors, or items leaves orphaned transaction references. QB's Verify check finds a transaction split line or header pointing to the old record ID, which no longer exists at that index. The C=147 Verify Target names the specific record involved.

Large File with Many Historical List Records

Files with thousands of customers, items, or vendors accumulate list index fragmentation over years of use. C=147 becomes more frequent as the list grows because more transactions reference older list records that may have been modified, merged, or whose index positions shifted during prior Rebuild operations.

Incomplete Rebuild from Prior C= Error

A previously interrupted or incomplete Rebuild can leave list index records in a state that causes C=147 on subsequent Verify runs. If Rebuild was interrupted (power failure, force-quit, or another error mid-Rebuild), run File Doctor before attempting another Rebuild.

Damaged Company File

General .QBW file corruption can damage list records alongside transaction records. When list record damage accompanies transaction damage, QB may show both C=147 (list) and C=47 or C=224 (transaction) in the same QBWin.log. Address all C= error types present before considering the file repaired.

Inventory Adjustments with Corrupted Item Links

Inventory adjustment transactions that reference items which were subsequently merged or made inactive can produce C=147. The adjustment's item reference becomes orphaned. These are identifiable by looking at the Verify Target in QBWin.log — if it names an inventory item, check that item's full history in QB for merges or deactivations.

Outdated QuickBooks Version

Some QB releases have known issues with list index validation that generate false C=147 errors. Updating to the current release for your QB year version can eliminate version-specific false positives before undertaking more invasive repair steps.

METHOD 1 Identify Affected List + Update QB + Verify/Rebuild Standard C=147 repair

METHOD 2 Run File Doctor + Condense File Large file or C=147 persists after Rebuild

METHOD 3 Restore from Backup Many C=147 errors or LVL_SEVERE_ERROR

Can merging customers or vendors cause C=147?

Yes — merging is one of the most common specific triggers for C=147. When you merge two records, QB removes one and redirects all references to the surviving record. However, if any transactions reference the removed record's internal list index position rather than just its name, those references become orphaned after the merge. QB's Verify check finds these orphaned index references and flags them as C=147. To prevent this: run Verify Data immediately after any major list merge operations (merging customers, vendors, or items) — catching C=147 early when only one or two records are affected is much easier than dealing with accumulated orphans across years of merges.