The specific QBWin.log message: verify: c (392) : CHECKPOINT: ####: Error: Verify Account Balance failed. Account = [Account Name]. Ref = ##. Home - Calc bal = ###.## . List bal = ###.##. The "Calc bal" is what QB calculates by adding up all transactions in the account — "List bal" is what QB's stored balance list shows. When these differ, Error 392 fires. The account name in the message tells you exactly which account has the balance discrepancy. Rebuild recomputes List bal from Calc bal, syncing them. After Rebuild: run the account's register to verify the balance looks correct, then run a Balance Sheet to confirm it matches expectations.

Account Balance List Out of Sync

Primary 392 cause — QB stores account balances in two places: calculated from transactions and stored in a balance list. When a transaction is added, edited, or deleted and the balance list update is interrupted or fails, the two balances diverge. Verify detects the mismatch as Error 392. Rebuild recomputes the list from the transactions.

Power Failure During Transaction Save

A crash while QB was writing a transaction left the transaction in the file but the account balance list wasn't updated to reflect it. Verify finds the Calc bal (including the transaction) doesn't match the List bal (which doesn't include it) → Error 392.

Corrupted Transaction in the Account

A corrupted transaction in the account (one with C=47 or C=224 damage) has an amount that Verify reads as different from what the balance list contains. Error 392 appears alongside the C= error for that transaction. Fix the C= error first (Rebuild/restore) — Error 392 for that account typically clears as well.

Inventory Account Imbalance

The "Verify Account Balance failed. Account = Inventory Asset" variant is specifically caused by inventory adjustments, assembly builds, or cost corrections that weren't fully committed. Inventory accounts are particularly prone to Error 392 because inventory transactions involve multiple account updates simultaneously.

Multi-User Simultaneous Edit

Two users simultaneously editing transactions in the same account can cause a write collision where one user's balance update overwrites or conflicts with the other's, leaving the account balance list in an incorrect state.

Beginning Balance Entry Issues

Incorrect opening balance entries (especially when a new company file was set up with a wrong opening balance that was then partially corrected) can create a persistent Error 392 on the affected account. Reconciling the account and correcting the opening balance entry resolves this variant.