What causes a closed build assembly to unintentionally revert back to pending build status?

There are several reasons why closed build assembly unintentionally reverts to pending build status, Dav.

Yes, one of them is inventory adjustments. Doing this can make changes to the build status. Though, adding a memo doesn't necessarily affect the assembly. However, editing the quantity or removing a component from the build assembly can cause it to revert.

I've listed the other causes of the issue:

• Being out of stock or insufficient quantity can result in the build assembly to update the status.
• System issues or corrupted data within the QuickBooks company file can cause closed build assemblies to revert to pending status.

To avoid this, make sure to have enough items when building assemblies. You can create purchase orders to add new inventories. Also, avoid modifying the transactions once closed.

Meanwhile, if you want to adjust your inventory value, it’s best to consult your accountant to avoid any issues. If you don't have one, you can use our Find-an-Accountant tool to look for an expert near you.

Also, we can use the Verify and Rebuild Data and the File Doctor tools to address and resolve system and data issues.

Please keep in mind that changes in the books are inevitable. Not to worry, we can restore the latest copy of your file to undo everything. If you're not regularly performing a backup, I recommend doing so to avoid data loss.

For more details about using the Inventory Assembly feature, please see this article: Combine your Items to Build Finished Goods.

Furthermore, you can run the  Inventory Valuation Summary report to keep track of your inventory status reports and ensure everything looks good and accurate. I'll show you how:

1. Select Reports and then Inventory.
2. To check your value, select the Inventory Valuation Summary. 
3. To view the quantity, click the Inventory Stock Status by Item.
4. Look for the items you adjusted and make sure everything is correct.

Please keep us posted if you need assistance tracking and managing your inventories and closed builds in QuickBooks Desktop. We always got your back.

In a software development context, a "closed build assembly" typically refers to a version of the software that has been finalized and released for production. When such a closed build assembly reverts back to a "pending build" status unintentionally, it indicates a regression or a deployment issue. Several factors could cause this unexpected behavior:

1. **Deployment or Configuration Issue:** During the deployment process, something might have gone wrong, leading to an incomplete or incorrect deployment of the closed build assembly. This could be due to misconfigurations, missing files, or incorrect settings.

2. **Database Rollback:** If the closed build assembly involves changes to the database schema or data, a rollback of the database to a previous state could cause the build to revert.

3. **Version Control Mishap:** In version control systems like Git, an accidental merge or rebase of code from a previous version could lead to the closed build assembly's source code being overwritten with earlier changes.

4. **Automated Deployment Pipeline:** If the closed build assembly is part of an automated deployment pipeline, a misconfiguration or error in the pipeline could cause the deployment to revert to a pending state.

5. **Rolling Back Deployed Version:** Sometimes, in the event of critical issues or bugs found in the closed build, organizations might roll back the deployment to a previous version, unintentionally undoing the closed status.

6. **Data Corruption:** Data corruption in the deployed system could cause unexpected behavior, leading to a pending build status.

7. **Integration Issues:** If the closed build assembly interacts with other systems or APIs, changes or issues in those external systems might cause the build to revert.

8. **Human Error:** In some cases, human error during release management or deployment processes could cause the unintended revert.

To troubleshoot and fix the issue, the development and operations teams should carefully investigate the deployment process, version control history, deployment logs, and any recent changes that might have impacted the system's behavior. Identifying the root cause will help prevent similar incidents in the future.

Implementing robust deployment and release management practices, including thorough testing, code reviews, and automated testing in the deployment pipeline, can reduce the chances of such issues occurring. Additionally, having proper version control practices and access controls can minimize the risk of accidental changes to closed builds.

Here’s another thing that can cause a closed build to revert back to pending build status:

• On 9/01/23, let’s say you had been out of screws.  You receive in Quickbooks a shipment of screws that are needed for build A.
• On 9/02/23, you close build A that needed those screws.
• On 9/05/23, you enter the bill for the screws, and enter the bill date as 09/05/23 instead of 09/01/23 when the screws were received.

Because you entered the screws bill date as 09/05/23, QuickBooks now thinks the screws were received on 09/05/23 instead of 09/01/23. 

 As a result, QuickBooks thinks you didn’t have enough screws on 09/02/23 to close build A, which causes build A to revert back to pending build status.

Hi @CharleneMaeF  and QB Community -

I just posted another reason a closed build could unintentionally revert back to pending status.

Do you know of any other reasons?

Hello Dav,

Thank you for sharing another reason that can cause a closed build assembly to revert to pending status.

As of now, what you, Hansenview, and my colleague shared above are the only factors that cause the mentioned issue.

To prevent the issue, ensure to have enough items when building assemblies.

Moreover, I've added these articles as your guide to managing inventories:

• Combine your inventory items to build finished goods
• Adjust your inventory quantity or value in QuickBooks Desktop
• Understand inventory assets and cost of goods sold tracking

Keep me posted whenever you have inventory concerns. Have a good one.

How can I fix my issue?  I correct an invoice that was dated 10/20/23 and then it made my one part in my build pending.  My build was dated 1/8/24 I believe.  If I change my invoice date from Oct to after 1-8-24 would that let me remove the pending status and finish the build?

How can you fix this issue?  I have a build in pending status that I built using a part on 1/8/23 but I corrected an invoice that removed some of that part from inventory and it was dated 10-20-23?  Can I move the date on the invoice to 1-9-23 and then it will let me remove the pending status and finish my build?

Thanks for joining the thread, @kstoney6. I'm here to help fix the issue with build assembly reverting to pending build status.

First, build assemblies depend on the availability of component items at the time of the build. If there has been an invoice correction related to the raw materials required for building the finished product, the built assembly will revert to pending status. Moreover, when an assembly returns to pending status, it stops affecting the General Ledger and the current on-hand quantity of items. However, it will allocate the parts again against the existing stock on hand, indicating you've not produced the finished good in QuickBooks Desktop's (QBDT) record.

Next, yes, you can change the invoice date from 10/20/23 to 1/9/2023 and make other necessary corrections. However, I recommend making sure that the date change will not affect the inventory levels as of the date of the build assembly. If the change will affect the inventory levels required for the creation of the build assembly, please ensure that you have enough inventory on hand for the assembly that is in pending status.  You can check this information by running the Inventory Stock Status by Item report. Here's how:

1. Go to Reports, then Reports Center.
2. In the search field, type "Inventory Stock Status by Item." Press enter and run the report.
3. Customize the date range of the report.
4. Check the Inventory Part items and the Assembly information from the For Assemblies column.
5. Compare the information to the quantity On hand column.

When everything else checks out, you can proceed with marking the pending build assembly as final:

1. Access the pending build assembly.
2. In your pending build assembly window, go to Edit.
3. Select Mark Build As Final.
4. Hit Build and Close.

For future reference, I'm adding this guide on tracking the products you manufacture. This will help as a reference in managing the products you build using inventory parts.

We're always here in the Community should you need further assistance correcting transactions in QBDT. We'll do our best to assist. Take care.

Hi All -

Here's a third thing that can cause a closed build assembly to revert back to pending status:

1.  If you accidentally close a pending build assembly for a past date, that could remove parts out of QB you needed to close build assemblies following that date.  For example, let's say today (12/3/24) you accidentally closed Build Assembly M on 09/01/24 and Build Assembly M required you to use 4 screws. Let's say you only had a total of 4 screws in stock in Sept. You had closed a similar build, Build Assembly H, on 09/15/24 that also needed those 4 screws.  So, since you accidentally closed Build Assembly M on 09/01/24 before Build Assembly H was closed on 09/15/24, it caused Build Assembly H to revert back to pending status.  Build Assembly H reverted back to pending status because technically you no longer had those 4 screws in stock that are needed to close Build H. Those 4 screws were used up closing Build M on 09/01/24.