QuickBooks Verify Error: Build Transaction Target in Bad Pending State
A QBWin.log verify error about assembly builds stuck in pending state traces back to negative inventory and can be cleared with a quantity adjustment.
QuickBooks Desktop users who run file verification on companies with inventory assemblies are hitting a log entry that stops the check cold. The QBWin.log records a failed verification of item history, points at a build transaction stuck in a bad pending state, and names an item by number. A database error coded 185 sits alongside it. We traced the accepted resolution: it is procedural, and it starts with one assembly whose quantity fell below zero.
The error and its symptoms
Verify Data lives under File, then Utilities, and checks the bookkeeping inside a company file. On files that use assemblies, the check can stop and report a build transaction left in a bad pending state. A build usually turns pending when components run short, and a negative on-hand figure can strand it there. The log names the item by reference number, a plain digit string rather than a name. Pro, Premier, and Enterprise are all exposed, since all three support assemblies. Day-to-day work usually continues. The failure surfaces when verification runs.
Can the log tell you which item it is?
Yes. With the company file open, press F2 to bring up the Product Information window, then F3 for Tech Help. On the Open File tab, select QBWIN.LOG and open it. Use Ctrl+F to search for the error wording and note the item number on that line. Keep the number handy. It is the key that unlocks every step that follows.
Turning the number into a name
The number in the log is a reference number, and the Item List holds the translation. From File, choose Utilities, then Export, then Lists to IIF Files. Tick Item List in the export window and save the file where you can find it. Nothing in this export changes your data; it writes a readable copy of the list. Open it in Excel, find the REFNUM column, and match it against the number from the log. The same row carries the item’s name.
Next, go to Reports, choose Inventory, and open Inventory Valuation Detail. Set the Dates dropdown to All so nothing is clipped. Find the item by name and read back to the date its quantity first dropped below zero. That date marks the build that caused the trouble.
The fix that resolved it
The accepted answer treats the cause, not the log line. Deal with the build assembly that drove the quantity negative, then bring the count back above zero. Before you change anything, open the Pending Builds report. Run it again afterward. Reducing an assembly’s quantity can flip affected builds into pending status, and the two reports are how you catch the change.
The count itself is corrected through Adjust Quantity/Value on Hand. In Pro and Premier the command sits under Vendors, then Inventory Activities. In Enterprise it is on the Inventory menu. Choose Quantity as the adjustment type and enter the date. Pick the account that will absorb the change; you can keep one account for everything, or separate accounts for gains and losses. If you are unsure which to use, an accountant can advise.
From there the form asks for the details. Select the inventory site the adjustment applies to. A reference number is optional, as are a customer, job, or class assignment if you track them. Add the item and enter either a new quantity or the difference. Multiple items can go on one adjustment, and you can spread them across different accounts, though each account needs its own separate adjustment.
What changes when you adjust?
Three effects deserve a heads-up. An assembly keeps its bill of materials no matter what you do to its quantity, so reducing the assembly and raising each component is a valid way to rebalance. Quantity adjustments also add or remove serial and lot numbers as the software restates stock; if you track those numbers, assign them before you adjust. Finally, a build that went pending can stay pending after the fix, which is exactly what the before-and-after reports will show you.
A clean pass closes the issue
With the quantity positive and the builds accounted for, run Verify Data again from File, then Utilities. A pass with no error ends the problem. If the same item number returns in the log, the negative came back too, and Inventory Valuation Detail will show the new date to work from. The pattern is consistent: read the log, name the item, fix the count, and the pending state clears with it.